From: Narvaez, Pablo (Pablo.Narvaez@xxxxxxxxxxxxx)
Date: Sat Apr 06 2002 - 15:12:30 GMT-3
Nicolai, I think you're doing the right thing and that's how dialer-watch is su
pposed to work ... the issue here is that, as far as I know, dialer-watch works
only with OSPF and EIGRP. You may use want to use snapshot with RIP, floating
routes or backup command, but documentacion says dialer-watch with RIP does not
work yet have to test it.
cheers,
hockito
-----Original Message-----
From: Nicolai Gersbo Solling [mailto:nicolai@cisco.com]
Sent: Sabado, 06 de Abril de 2002 11:30 a.m.
To: CCIE
Subject: Dialer Watch-list
Hi there...
Just a short question regarding dialer watch lists...
R1----ETH----R2 - ISDN is acting as backup.
I am running Rip v1 and routes for the following networks...
192.168.3.0 (Ethernet)
192.168.4.0 (ISDN - RIP can not trigger the link)
192.168.1.0 (Loopback on R1)
192.168.2.0 (Loopback on R2)
I got the dialer-watch list to watch 192.168.2.0...
The only way I can make it work is to have a:
map ip 192.168.2.0 name R2 broadcast 2222
When I kill the ethernet 0 the disappearing route in R1 trigger the ISDN and
make a connection to R2...
This makes RIP get information about the networks on R2, but RIP will not
install the 192.168.2.0 in the routing table.
After having inspected the routing table everything makes sence...
Since I have a map statement for 192.168.2.0 pointing to R2 the routing
table states that 192.168.2.0 is directly connected to BRI0:1...When RIP
gets information about 192.168.2.0 being on the loopback of R2 it just
discards this information!
Anyone else out there that has experienced the same as I?
Btw...do you also find yourself pressing the TAB-bar when you type commands
in e-mails? ;-)
Nic
1st lab attempt on the 25th of April, but who is counting...
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:57 GMT-3