A BGP restart causes reestablishment of peer relationships and a traffic interruption. To prevent the traffic interruption, run the graceful-restart command to enable GR.
Currently, BGP does not support dynamic capability negotiation. As a result, each time the BGP capability changes, the BGP peer relationship is re-established. For example, a BGP IPv4 unicast peer relationship is established and IPv4 services are running; if the BGP capability changes, the BGP IPv4 unicast peer relationship will be re-established, which interrupts ongoing IPv4 services. To prevent the service interruptions, run the graceful-restart peer-reset command to enable the router to reset a BGP session in GR mode.
If the GR reset function and a new BGP capability are enabled on a BGP speaker, the BGP speaker enters the GR state, resets the BGP session (without deleting the routing entries for the session), and renegotiates BGP capabilities with its peer. Therefore, existing services are not interrupted.
Enable the device to reset a BGP connection in GR mode when establishing BGP peer relationships.
In this project we need to enable the BGP GR to prevent the traffic interruption.
The configuration template is as below:
Table 1-1 BGP GR Configuration Template
# bgp 65000 graceful-restart graceful-restart peer-reset # commit # |
