EIGRP Nonstop Forwarding (NSF) Awareness

Cisco NSF is supported by the BGP, EIGRP, OSPF, and IS-IS protocols for routing and by Cisco Express Forwarding (CEF) for forwarding. Of the routing protocols, BGP, OSPF, and IS-IS have been enhanced with NSF-capability and awareness, which means that routers running these protocols can detect a switchover and take the necessary actions to continue forwarding network traffic and to recover route information from the peer devices. The IS-IS protocol can be configured to use state information that has been synchronized between the active and the standby route processor (RP) to recover route information following a switchover instead of information received from peer devices.

In this document, a networking device that is NSF-aware is running NSF-compatible software. A device that is NSF-capable has been configured to support NSF; therefore, the device rebuilds routing information from NSF-aware or NSF-capable neighbors.

Each protocol depends on CEF to continue forwarding packets during switchover while the routing protocols rebuild the routing information base (RIB) tables. After the routing protocols have converged, CEF updates the forwarding information base (FIB) table and removes stale route entries. CEF, in turn, updates the line cards with the new FIB information.

In a Cisco networking device, CEF provides packet forwarding, a key element of NSF. CEF maintains the FIB and uses the FIB information that was current at the time of a switchover to continue forwarding packets during the switchover. NSF helps to reduce traffic interruption during the switchover.

During normal NSF operation, CEF on the active RP synchronizes its current FIB and adjacency databases with the FIB and adjacency databases on the standby RP. Upon switchover of the active RP, the standby RP initially has FIB and adjacency databases that are mirror images of those that were current on the active RP. For platforms with intelligent line cards, the line cards will maintain the current forwarding information over a switchover; for platforms with forwarding engines, CEF will keep the forwarding engine on the standby RP current with changes that are sent to it by CEF on the active RP. In this way, the line cards or forwarding engines will be able to continue forwarding after a switchover as soon as the interfaces and a data path are available.

As the routing protocols start to repopulate the RIB on a prefix-by-prefix basis, the updates in turn cause prefix-by-prefix updates for CEF, which it uses to update the FIB and adjacency databases. Existing and new entries will receive the new version (“epoch”) number, indicating that they have been refreshed. The forwarding information is updated on the line cards or forwarding engine during convergence. The RP signals when the RIB has converged. The software removes all FIB and adjacency entries that have an epoch older than the current switchover epoch. The FIB now represents the newest routing protocol forwarding information

The routing protocols run only on the active RP, and they receive routing updates from their neighbor routers. Routing protocols do not run on the standby RP. Following a switchover, the routing protocols request that the NSF-aware neighbor devices send state information to help rebuild the routing tables.

Note	For NSF operation, the routing protocols depend on CEF to continue forwarding packets while the routing protocols rebuild the routing information.

NSF awareness allows a router that is running EIGRP to assist NSF-capable neighbors to continue forwarding packets during a switchover operation or well-known failure condition. The EIGRP Nonstop Forwarding Awareness feature provides EIGRP with the capability to detect a neighbor that is undergoing an NSF restart event (RP switchover operation) or well-known failure condition, maintain the peering session with this neighbor, retain known routes, and continue to forward packets for these routes. The deployment of EIGRP NSF awareness can minimize the effects of the following:

• Well-known failure conditions (for example, a stuck-in-active event)
• Unexpected events (for example, an RP switchover operation)
• Scheduled events (for example, a hitless software upgrade)

EIGRP NSF awareness is enabled by default and is transparent to the network operator and EIGRP peers that do not support NSF capabilities.

Note	An NSF-aware router must be up and completely converged with the network before it can assist an NSF-capable router in an NSF restart operation.

EIGRP NSF capabilities are exchanged by EIGRP peers in hello packets. An NSF-capable router notifies its neighbors that an NSF restart operation has started by setting the restart (RS) bit in a hello packet. When an NSF-aware router receives notification from an NSF-capable neighbor that an NSF-restart operation is in progress, both routers immediately exchange their topology tables. The NSF-aware router sends an end-of-table (EOT) update packet when the transmission of its topology table is complete. The NSF-aware router then performs the following actions to assist the NSF-capable router:

• Expires the EIGRP hello hold timer to reduce the time interval set for hello packet generation and transmission. This allows the NSF-aware router to reply to the NSF-capable router more quickly and reduces the amount of time required for the NSF-capable router to rediscover neighbors and rebuild the topology table.
• Starts the route-hold timer. This timer is used to set the period of time that the NSF-aware router will hold known routes for the NSF-capable neighbor. This timer is configured with the timers graceful-restart purge-timecommand. The default time period is 240 seconds.
• Notes in the peer list that the NSF-capable neighbor is restarting, maintains adjacency, and holds known routes for the NSF-capable neighbor until the neighbor signals that it is ready for the NSF-aware router to send its topology table or the route-hold timer expires. If the route-hold timer expires on the NSF-aware router, it discards held routes and treats the NSF-capable router as a new router joining the network and reestablishing adjacency accordingly.

When the switchover operation is complete, the NSF-capable router notifies its neighbors that it has reconverged and has received all of their topology tables by sending an EOT update packet to the assisting routers. The NSF-capable router then returns to normal operation. The NSF-aware router looks for alternate paths (go active) for any routes that are not refreshed by the NSF-capable (restarting) router. The NSF-aware router returns to normal operation. If all paths are refreshed by the NSF-capable router, the NSF-aware router immediately returns to normal operation.

NSF-aware routers are completely compatible with non-NSF aware or non-NSF capable neighbors in an EIGRP network. A non-NSF aware neighbor ignores NSF capabilities and resets the adjacency when they are received.

The NSF-capable router drops any queries that are received while converging to minimize the number of transient routes that are sent to neighbors. The NSF-capable router, however, still acknowledges these queries to prevent these neighbors from resetting adjacency.

Note	An NSF-aware router continues to send queries to an NSF-capable router that is converging after a switchover, effectively extending the time before a stuck-in-active (SIA) condition can occur.

The route-hold timer is configurable, which allows you to tune network performance and avoid undesired conditions such as “black holing” routes if the switchover operation is lengthy. When the timer expires, the NSF-aware router scans the topology table and discards stale routes, allowing EIGRP peers to find alternate routes instead of waiting during a long switchover operation.

The route-hold timer is configured with the timers graceful-restart purge-time router configuration command. The default time period for the route-hold timer is 240 seconds. The configurable range is from 10 to 300 seconds.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    router eigrp {autonomous-system-number | virtual-instance-name}

4.    address-family ipv4 [multicast][unicast][vrf vrf-name] autonomous-system autonomous-system-number

5.    timers graceful-restart purge-time seconds

6.    exit

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables higher privilege levels, such as privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	router eigrp {autonomous-system-number | virtual-instance-name} Example: Router(config)# router eigrp 101	Enters router configuration mode and creates an EIGRP routing process.
Step 4	address-family ipv4 [multicast][unicast][vrf vrf-name] autonomous-system autonomous-system-number Example: Router(config-router)# address-family ipv4 vrf vrf1	(Optional) Enters address family configuration mode and creates a session for the VRF.
Step 5	timers graceful-restart purge-time seconds Example: Router(config-router)# timers graceful-restart purge-time 120	Sets the route-hold timer to determine how long an NSF-aware router that is running EIGRP will hold routes for an inactive peer. Note    The timers nsf route-holdcommand was replaced with the timers graceful-restart purge-time command in Cisco IOS Release 15.0(1)M and 12.2(33)SRE.
Step 6	exit Example: Router(config-router)# exit Example: Router(config)#	Exits router configuration mode and enters global configuration mode.

• Troubleshooting Tips
  

SUMMARY STEPS

1.    enable

2.    debug eigrp nsf

3.    debug ip eigrp notifications

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables higher privilege levels, such as privileged EXEC mode. Enter your password if prompted.
Step 2	debug eigrp nsf Example: Router# debug eigrp nsf	Displays NSF notifications and information about NSF events in an EIGRP network on the console of the router.
Step 3	debug ip eigrp notifications Example: Router# debug ip eigrp notifications	Displays EIGRP events and notifications in the console of the router. The output from this command also includes NSF notifications and information about NSF events.

SUMMARY STEPS

1.    enable

2.    show ip protocols

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables higher privilege levels, such as privileged EXEC mode. Enter your password if prompted.
Step 2	show ip protocols Example: Router# show ip protocols	Displays the parameters and current state of the active routing protocol process. The output of this command can be used to verify EIGRP NSF-awareness.