Suppression on BGP4+ peer flapping allows a device to delay the establishment of a BGP4+ peer relationship that flaps continuously.
BGP4+ peer flapping occurs when BGP4+ peer relationships are disconnected and then immediately re-established in a quick sequence that is repeated. Frequent BGP4+ peer flapping is caused by various factors; for example, a link is unstable, or an interface that carries BGP4+ services is unstable. After a BGP4+ peer relationship is established, the local device and its BGP4+ peer usually exchange all routes in their BGP4+ routing tables with each other. If the BGP4+ peer relationship is disconnected, the local device deletes all the routes learned from the BGP4+ peer. Generally, a large number of BGP4+ routes exist, and in this case, a large number of routes change and a large amount of data is processed when the BGP4+ peer relationship is flapping. As a result, a high volume of resources are consumed, causing high CPU usage. To prevent this issue, a device supports suppression on BGP4+ peer flapping. With this function enabled, the local device suppresses the establishment of the BGP4+ peer relationship if it flaps continuously.
Before configuring suppression on BGP4+ peer flapping, you have completed the following task:
The system view is displayed.
The BGP view is displayed.
BGP4+ is enabled to suppress the establishment of a specified peer relationship that flaps continuously.
To immediately remove the suppression, you can run the peer oscillation-dampening disable command. Alternatively, you can run a reset command or another command that can cause the peer relationship to be disconnected and re-established.
The configuration is committed.
After configuring suppression on BGP4+ peer flapping, verify the configuration.
Run the display bgp ipv6 peer verbose command to check the suppression status of the flapping BGP4+ peer relationship and the remaining time to establish the BGP4+ peer relationship.