Nsf Guidelines And Restrictions - Cisco Catalyst 4500 series Administration Manual

Chapter 12 Configuring Cisco NSF with SSO Supervisor Engine Redundancy
If at least one of the peer routers is NSF-aware, the restarting router then receives updates and rebuilds
its database. The restarting router must then find out if it had converged so that it can notify the routing
information base (RIB). Each NSF-aware router is required to send an end of table (EOT) marker in the
last update packet to indicate the end of the table content. The restarting router knows it has converged
when it receives the EOT marker. The restarting router can then begin sending updates.
An NSF-aware peer knows when the restarting router had converged when it receives an EOT indication
from the restarting router. The peer then scans its topology table to search for the routes with the
restarted neighbor as the source. The peer compares the route timestamp with the restart event timestamp
to determine if the route is still available. The peer then goes active to find alternate paths for the routes
that are no longer available through the restarted router.
When the restarting router has received all EOT indications from its neighbors or when the NSF converge
timer expires, EIGRP notifies the RIB of convergence. EIGRP waits for the RIB convergence signal and
then floods its topology table to all awaiting NSF-aware peers.

NSF Guidelines and Restrictions

NSF with SSO has these restrictions:
•
•
•
•
•
•
•
•
Configuring NSF with SSO Supervisor Engine Redundancy
The following sections describe the configuration tasks for the NSF feature:
•
•
•
•
OL_28731-01
With aggressive protocol timers (such as, when the default exceeds the timer value), upon
switchover, the protocol software running on the new active supervisor engine might not initialize
in time to send "hello" packets to its neighboring switches or routers. If the protocol takes longer
time to initialize because of other CPU-demanding tasks, then the protocol encounters state
transitions and causes a loss in traffic on the order of seconds. We recommend that you do not
configure aggressive timers in conjunction with SSO/NSF.
For NSF operation, you must have SSO configured on the device.
NSF with SSO supports IP Version 4 traffic and protocols only; NSF with SSO does not support IPv6
traffic.
The Virtual Redundancy Routing Protocols (VRRP) is not SSO-aware, meaning state information is
not maintained between the active and standby supervisor engine during normal operation. VRRP
and SSO can coexist but both features work independently. Traffic that relies on VRRP may switch
to the VRRP standby in the event of a supervisor engine switchover.
All neighboring devices participating in BGP NSF must be NSF-capable and configured for BGP
graceful restart.
OSPF NSF for virtual links is not supported.
All OSPF networking devices on the same network segment must be NSF-aware (running an NSF
software image).
For IETF IS-IS, all neighboring devices must be running an NSF-aware software image.
Configuring SSO, page 12-10
Configuring CEF NSF, page 12-11
Verifying CEF NSF, page 12-11
Configuring BGP NSF, page 12-11
Configuring NSF with SSO Supervisor Engine Redundancy
Software Configuration Guide—Release IOS XE 3.6.0E and IOS 15.2(2)E
12-9