Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

Reposting: Static routes to dialer interfaces

I originally posted this on the Remote Access section, but I still have not resolved the issue.

Suppose I have an ISDN primary rate interface with 30 channels, which provides a dialer pool. I then have several dialer profile interfaces that use that pool. I then make a static route to one of those dialer interfaces, say ip route 192.168.42.0 255.255.255.0 Dialer 6. So far so good ... pretty standard stuff.

I then want to redistribute that static route into, say, OSPF. But I want to arrange it so that if there are no channels in the dialer pool, for example if the ISDN primary rate connection is down, then the route is not redistributed, or even better if it disappears from the access router altogether?

What I am saying is: how can I arrange for a dialer interface to be effectively down whenever the physical interfaces in its dialer pool are down?

If the static route was to a serial interface, and that serial interface was down, then the router would remove the route from its table and not inject it into OSPF. But in this case, the static route is to a dialer interface that always looks to be up. I don't want that. If the ISDN dialer pool is down, I don't want the router to advertise the route, so that a backup router (and line) can take the traffic.

Someone suggested object tracking, but this is through a dialer, and it would be a bit expensive to ping a remote object every few seconds just to check the availability of the ISDN.

Thanks in advance.

Kevin Dorrell

Luxembourg

1 REPLY

Re: Reposting: Static routes to dialer interfaces

You can do Object tracking by other means too (not just pinging).

Like:

Tracking the Line-Protocol State of an Interface

Tracking the IP-Routing State of an Interface

Tracking IP-Route Reachability

Tracking the Threshold of IP-Route Metrics

Tracking IP SLAs Operations

Check the following like, it might help (if object tracking is indeed a solution for you).

HTH,

if it does, please rate this post.

http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a008049b758.html

vlad

91
Views
5
Helpful
1
Replies