Laurent Aubert Sat, 11/14/2009 - 19:03

Hi,


I'm not sure if it's expected or not but here are some tips to check everything is working fine:


First you need to be sure your peer is EIGRP NSF aware:


Router# show ip protocols

...

EIGRP NSF-aware route hold timer is 240s

EIGRP NSF enabled

NSF signal timer is 20s

NSF converge timer is 120s

...


"EIGRP NSF enabled" is only for the router which has redundant SUP.


Then you should see this message on the peer facing the restarting router:


*Oct 4 11:39:18.092:%DUAL-5-NBRCHANGE:IP-EIGRP(0) 2:Neighbor

135.100.10.1 (POS3/0) is up:peer NSF restarted


Also a debug eigrp nsf and debug ip eigrp notification are available to follow the process.


HTH


Laurent.



Actions

This Discussion