Configuring BGP NSR
To use BGP nonstop routing (NSR), the system must have a minimum of two MPUs.
NSR ensures nonstop services when BGP has redundant processes on multiple MPUs. In contrast to GR, NSR does not require a neighbor device to recover routing information.
BGP NSR backs up BGP state and data information from the active BGP process to the standby BGP process. The standby BGP process takes over when any of the following events occurs:
The active BGP process restarts.
The MPU that runs the active BGP process fails.
An ISSU starts on the MPU that runs the active BGP process.
When both GR and NSR are configured for BGP, NSR has a higher priority than GR. The device will not act as the GR restarter. If the device acts as a GR helper, it cannot help the restarter to complete GR.
To use BGP NSR in MPLS L3VPN, you must enable RIB NSR. For information about RIB NSR, see "Configuring basic IP routing."
To configure BGP NSR:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Enter BGP instance view. | bgp as-number [ instance instance-name ] | N/A |
3. Enable BGP NSR. | non-stop-routing | By default, BGP NSR is disabled. |