An interesting Dialer-watch question

From: Jaspreet Bhatia (jasbhati@xxxxxxxxx)
Date: Fri Sep 14 2001 - 20:05:34 GMT-3


   
>Folks,
> Howdy !!. I have two routers A and B connected via
> their Tokenring interfaces ( Primary ) .Also they are connected via
> their bri interfaces . They have OSPF running on them . They have the
> dialer-watch feature implemented on them and it is working just fine .
> When A loses the route to B' s ethernet interface ( by shutting down the
> tokenring interface) it dials on the ISDN port and the routing table is
> updated .The moment the Tokenring interface comes back online the dialer
> idle-timeout timer (30 secs) expires and then the dialer-watch-disable
> timer expires ( 15 secs ) and the ISDN link is brought down . Ok , the
> thing with the dialer-watch feature is that it will keep checking the
> primary link after every 30 secs .
>
>Now lets hear the problem .....
>
> Router B which has no dial string in its dialer map statement tries to
> dial out when the primary interface is up .
>
>03:03:24: BR1/0 DDR: Dialing cause ip (s=172.16.3.2, d=224.0.0.5)
>
> As you can see that these updates are OSPF updates sent to the multicast
> address 224.0.0.5 . Now I can do two things here . Make bri 1/0 as
> passive .or have an access-list denying OSPF traffic and then make it
> part of the dialer-list . But the moment I do this the ISDN interface
> on Router A start going down at the end of the dialer idle timeout and
> then dials again and then disconnects and so on .
>
>Please let me know if further clarifications are needed . thanks
Jaspreet
**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:32:18 GMT-3