Single Page

Top Document: comp.dcom.sys.cisco Frequently Asked Questions (FAQ)
Previous Document: When are static routes redistributed?
Next Document: How do name and phone number of ``dialer map'' interfere?


[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]

When is the next hop of a route considered ``reachable''?


When a static route is added, or during an important event (eg:
interface up/down transition), the next hop for a route is looked up
from the routing table (i.e. recursive routing).

As a consequence, if a route which is depended upon for evaluation
of the next hop of a static route goes away, a mechanism is required
to remove that (now-invalid) static route.

Scanning all static routes each time the routing table changes is
too expensive, so instead, a period timer is used. One a minute, static
routes are added and removed from the routing table based on the routes
they depend upon.

It should be noted that a particular static route will be reevaluated
when its interface transitions up or down.



Top Document: comp.dcom.sys.cisco Frequently Asked Questions (FAQ)
Previous Document: When are static routes redistributed?
Next Document: How do name and phone number of ``dialer map'' interfere?

Single Page


[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
cisco-faq@panix.com (comp.dcom.sys.cisco FAQ responses)

Last Update May 13 2007 @ 00:22 AM