Go CCIE Go!! - A Cisco Certified Internetwork Expert

Hi Group Simple query ..... As I read from doc cd ; I have a confusion in 2 CLIs : 1) timers nsf route-hold and 2) ip hold-time eigrp hold-time (3 time the hello by default) determines that after this interval of not hearing the hellos from neighbor ; routes from the neighbor are held invalid and hence removed from table timers nsf route-hold will also do the same thing ( after this time period ; the routes from inactive peer are removed ) Can someone clearly stae the situation where these 2 should be used . Thnx Gaurav Madan. Blogs and organic groups at http://www.ccie.net ...

Hi, which solution looks appropriate when considering the task of having EIGRP hold routes for an inactive peer for 180 seconds ip hold-time eigrp 100 180 ( Or ) timers nsf route-hold 180 Timers nsf route-hold http://www.cisco.com/en/US/docs/ios/12_2t/12_2t15/feature/guide/ft_ensf.html#wp1027385 IP Hold-Time http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfeigrp.html Blogs and organic groups at http://www.ccie.net ...

While 2 is the standard time to consider something dead, 1 is a special case for NSF. #1 timer activates in case your router is NSF-AWARE and/or NSF-CAPABLE, and neighbor is NSF-CAPABLE router, that has some sort of SSO redundancy, and it's control plane went dead. E.g. ...