Preventing Flapping Routes from being Advertised in BGP using Dampening Profiles
59499
Created On 09/25/18 17:42 PM - Last Modified 06/02/22 21:12 PM
Symptom
- In an unstable network, the routes can flap.
- If these routes are advertised in BGP, the BGP routes also flap which can result in the active re-convergence of other stable networks advertised in BGP.
- It is not a good practice to advertise flapping route to neighbor as it sacrifices the route convergence time for generally well behaved and stable routes.
- Flapping may cause the peering to be lost and creates unwanted outage and traffic drops.
- Flapping may also cause serious performance degradation as it consumes valuable CPU cycles.
Environment
- Palo Alto Firewall.
- Supported PAN-OS
- BGP configured
Cause
- Dampening Profiles have not been configured on the firewall
- No optimal connection options
Resolution
Additional Information
To check if optimal connection options are specified on the firewall, go to
GUI: Network > Virtual Routers > Peer Group.
Click Add > (name) > Add > Connection Options
- The Keep Alive Interval specifies an interval after which routes from a peer are suppressed according to the hold time setting.
- The Open Delay Time specifies the delay time between opening the peer TCP connection and sending the first BGP open message.
- The Hold Time specifies the period of time that may elapse between successive KEEPALIVE or UPDATE messages from a peer before the peer connection is closed.
- Idle Hold Time specifies the time to wait in the idle state before retrying connection to the peer.
See also: Unable to Achive Subsecond failover with BGP in Active Passive Configuration