graceful-restart (Long-Lived for BGP Helper)
Syntax
graceful-restart {
long-lived {
receiver {
enable:
disable;
}
advertise-to-non-llgr-neighbor {
omit-no-export;
}
}
}
Hierarchy Level
[edit logical-systems logical-system-name protocols bgp], [edit logical-systems logical-system-name protocols bgp group group-name], [edit logical-systems logical-system-name protocols bgp group group-name neighbor address], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name], [edit logical-systems logical-system-name routing-instances instance-name protocols bgp group group-name neighbor address], [edit protocols bgp], [edit protocols bgp group group-name], [edit protocols bgp group group-name neighbor address]
Description
Configure the graceful restart capability for long-lived BGP sessions to enable BGP routing details to be retained for a longer period. It in important to retain BGP data for a longer period when the BGP control plane fails for some reason for slowly-restarting routers for a longer duration. Graceful restart allows a routing device undergoing a restart to inform its adjacent neighbors and peers of its condition. Graceful restart is disabled by default.
When nonstop routing (NSR) and long-lived graceful restart (LLGR) are configured together, the router negotiates the LLGR capability in the usual, regular manner, including a long-lived stale time to trigger LLGR receiver mode in its peers. However, full LLGR restarter functionality (delaying the transmission of End of RIB (EoR) markers until EoRs are received from all peers) does not function under NSR. During a full system (both Routing Engines) restart, the routing protocol daemon (rpd) does not wait for EoRs from other peers before sending its own EoR. It transmits the EoR as soon as it has transmitted the current RIB contents. This condition can cause transient outages when the network reconverges. NSR is considered to be adequate to handle all single-Routing Engine restart scenarios. The restarter mode restriction effects only scenarios where both Routing Engines (or both copies of rpd) restart simultaneously. Ordinary restarter mode configuration is not enabled with NSR. Long-lived graceful restart receiver mode is enabled by default, unless ordinary graceful restart receiver mode is disabled.
If you configure graceful restart after a BGP session has been established, the BGP session restarts and the peers negotiate graceful restart capabilities.
Configure graceful restart globally at the [edit routing-options] or [edit routing-instances instance-name routing-options] hierarchy level to enable the feature. You
cannot enable graceful restart for specific protocols unless graceful
restart is also enabled globally. You can, optionally, modify the
global settings at the individual protocol level.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 15.1.