|
Dual Routing Engines only (no features enabled)
|
When the switchover to the new master Routing Engine is complete,
routing convergence takes place and traffic is resumed.
|
All physical interfaces are taken offline, Packet Forwarding
Engines restart, the standby Routing Engine restarts the routing protocol
process (rpd), and all hardware and interfaces are discovered by the
new master Routing Engine. The switchover takes several minutes and
all of the router's adjacencies are aware of the physical (interface
alarms) and routing (topology) change.
|
|
Graceful Routing Engine switchover enabled
|
During the switchover, interface and kernel information is preserved.
The switchover is faster because the Packet Forwarding Engines are
not restarted.
|
The new master Routing Engine restarts the routing protocol
process (rpd). All hardware and interfaces are acquired by a process
that is similar to a warm restart. All adjacencies are aware of the
router's change in state.
|
|
Graceful Routing Engine switchover and nonstop active routing
enabled
|
Traffic is not interrupted during the switchover. Interface,
kernel, and routing protocol information is preserved.
|
Unsupported protocols must be refreshed using the normal recovery
mechanisms inherent in each protocol.
|
|
Graceful Routing Engine switchover and graceful restart enabled
|
Traffic is not interrupted during the switchover. Interface
and kernel information is preserved. Graceful restart protocol extensions
quickly collect and restore routing information from the neighboring
routers.
|
Neighbors are required to support graceful restart and a wait
interval is required. The routing protocol process (rpd) restarts.
For certain protocols, a significant change in the network can cause
graceful restart to stop.
|
