From: Jason Cash (cash2001@swbell.net)
Date: Wed Jun 11 2003 - 23:22:35 GMT-3
Is it feasible to run ISIS over an ISDN link? I tinkered around and got it
to work, but now when my primary link recovers (S0), the clns neighbor is
not removed.
R5 was configured to 'dialer watch' 172.16.137.0/24, but with my original
config, ISDN connectivity was established but no routes were learned. So I
threw is onto R5:
interface BRI0
ip address 170.1.201.1 255.255.255.252
ip router isis
encapsulation ppp
dialer map ip 172.16.137.0 name User_C broadcast 8358661
dialer map clns 49.0001.1921.6800.2002.00 name User_C broadcast
The problem is that once the ISDN link goes down, ISIS still keeps it's
neighbor over the link. Is there some type of "demand circuit" technology
for ISDN?
I stumbled upon this solution when (from R5) I was unable to ping any IPs on
the watched route:
R5#
interface BRI0
ip address 170.1.201.1 255.255.255.252
ip router isis
encapsulation ppp
dialer map ip 172.16.137.0 name User_C broadcast 8358661
dialer map clns 49.0001.1921.6800.2002.00 name User_C broadcast
dialer map ip 170.1.201.2 name User_C broadcast 8358661
dialer load-threshold 10 outbound
dialer watch-group 1
!
dialer watch-list 1 ip 172.16.137.0 255.255.255.0
dialer watch-list 1 delay route-check initial 60
==============================
r5#ping 172.16.137.1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.137.1, timeout is 2 seconds:
...
Success rate is 0 percent (0/3)
What is the benefit of 'watch groups' if you need an individual map
statement for ewach host on the subnet? Is there a way to do a range for a
dialer map?
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:10:56 GMT-3