From: Brian Dennis (bdennis@internetworkexpert.com)
Date: Mon Mar 14 2005 - 22:25:37 GMT-3
First off, why do you think this /32 route is causing problems with the
OSPF virtual-link? The virtual-link is not even running across the ISDN
connection. When the Frame Relay link between R3 and R4 is down, the
virtual-link should also be down as R3 and R5 are not OSPF neighbors.
R4 does not need a route to R3's loopback in order for the virtual-link
to come up. R4 will create the virtual-link to the OSPF neighbor with
the router-ID of 150.1.3.3. This is done across the Frame Relay
connection between R3 and R4.
As a side note, task 5.34 is configured incorrectly and R4 should not
have the dialer-list permitting all IP traffic ;-)
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: simon hart [mailto:simon.hart@btinternet.com]
Sent: Monday, March 14, 2005 3:37 PM
To: Brian Dennis; Group Study
Subject: RE: Dialer Watch
Brian,
Please find the configs below.
config for R5
interface Loopback0
ip address 150.1.5.5 255.255.255.0
!
interface Ethernet0/0
ip address 187.1.56.5 255.255.255.0
ip router isis
half-duplex
isis circuit-type level-1
!
interface Serial0/0
ip address 187.1.235.5 255.255.255.0
ip router isis
encapsulation frame-relay
clockrate 64000
no fair-queue
frame-relay map clns 513 broadcast
frame-relay map clns 502 broadcast
frame-relay map ip 187.1.235.2 502 broadcast
frame-relay map ip 187.1.235.3 513 broadcast
no frame-relay inverse-arp
!
interface TokenRing0/0
no ip address
shutdown
ring-speed 16
!
interface BRI0/0
ip address 187.1.45.5 255.255.255.0
encapsulation ppp
ip ospf cost 781
dialer idle-timeout 0
dialer-group 1
isdn switch-type basic-ni
isdn spid1 2122
compress stac
ppp authentication pap callin
ppp pap refuse
ppp multilink
ppp multilink links minimum 2
!
interface Serial0/1
no ip address
shutdown
!
interface FastEthernet1/0
ip address 187.1.5.5 255.255.255.0
duplex auto
speed auto
no keepalive
!
router ospf 100
log-adjacency-changes
area 134 virtual-link 150.1.1.1 authentication authentication-key CISCO
redistribute connected metric 20 subnets route-map CONN2OSPF
network 187.1.45.5 0.0.0.0 area 45
!
router isis
net 49.00eb.0001.0001.0005.00
metric-style wide
redistribute connected metric 4990 route-map CONN2ISIS level-1
passive-interface Loopback0
distance 109 ip
!
ip http server
ip classless
!
!
!
dialer-list 1 protocol ip deny
!
route-map CONN2OSPF permit 10
match interface Loopback0
!
route-map CONN2ISIS permit 10
match interface FastEthernet1/0
!
Config for R4
!
interface Serial8.134 multipoint
ip address 187.1.134.4 255.255.255.0
ip ospf network point-to-multipoint
ip ospf cost 64
frame-relay map ip 187.1.134.1 403
frame-relay map ip 187.1.134.3 403 broadcast
frame-relay map ip 187.1.13.1 403
frame-relay map ip 187.1.13.3 403 broadcast
no frame-relay inverse-arp
!
interface Serial9
no ip address
!
interface TokenRing0
no ip address
shutdown
!
interface BRI0
ip address 187.1.45.4 255.255.255.0
encapsulation ppp
ip ospf cost 781
ip ospf demand-circuit
no ip mroute-cache
dialer idle-timeout 30
dialer map ip 150.1.3.3 name Rack1R5 broadcast 2222
dialer map ip 187.1.45.5 name Rack1R5 broadcast 2222
dialer watch-group 101
dialer-group 1
isdn switch-type basic-ni
isdn spid1 1211
compress stac
ppp authentication pap chap optional
ppp pap sent-username ROUTER4 password 0 C1SC0?2000
ppp multilink
multilink min-links 2
!
router ospf 100
router-id 150.1.4.4
log-adjacency-changes
area 134 virtual-link 150.1.3.3
network 150.1.4.4 0.0.0.0 area 0
network 187.1.4.4 0.0.0.0 area 0
network 187.1.45.4 0.0.0.0 area 45
network 187.1.134.4 0.0.0.0 area 134
!
ip classless
no ip http server
ip http authentication local
ip pim bidir-enable
!
no logging trap
dialer watch-list 102 ip 150.1.2.0 255.255.255.0
dialer watch-list 101 ip 150.1.3.3 255.255.255.255
dialer-list 1 protocol ip permit
!
Copy of debug ip route output on R4
%ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 2222 Rack1R5,
call
lasted 330 seconds
%ISDN-6-DISCONNECT: Interface BRI0:2 disconnected from 2222 Rack1R5,
call
lasted 326 seconds
%LINK-3-UPDOWN: Interface BRI0:1, changed state to down
%LINK-3-UPDOWN: Interface BRI0:2, changed state to down
Mar 1 16:38:53.739: RT: del 150.1.3.3/32 via 0.0.0.0, connected metric
[0/0]
*Mar 1 16:38:53.743: RT: delete subnet route to 150.1.3.3/32
*Mar 1 16:38:53.995: RT: add 150.1.3.3/32 via 187.1.134.3, ospf metric
[110/65]
%LINK-3-UPDOWN: Interface BRI0:1, changed state to up
%LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
*Mar 1 16:38:54.647: RT: closer admin distance for 150.1.3.3, flushing
1
routes
*Mar 1 16:38:54.651: RT: add 150.1.3.3/32 via 0.0.0.0, connected metric
[0/0]
*Mar 1 16:38:54.659: is_up: 1 state: 4 sub state: 1 line: 0
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: 14 March 2005 23:23
To: simon hart; Group Study
Subject: RE: Dialer Watch
Can you post your configuration from R4 and R5?
Also the link should not idle timeout unless you do not have the dialer
idle-timeout set to 0 on the side without the dialer watch
configuration.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: simon hart [mailto:simon.hart@btinternet.com]
Sent: Monday, March 14, 2005 2:44 PM
To: Brian Dennis; Group Study
Subject: RE: Dialer Watch
Hi Brian,
Thanks for pointing this out, however I have tried this command with
little
joy.
It seems that if I have the no peer neighbor-route then R4 will is
never
able to re-establish a virtual link to area 0 (I am assuming you are
familiar with the Lab scenario) as does not know how to get to R3, and
thus
does not have reachability to the rest of the network as a result of the
failure.
If I have a peer neighbor-route then R4 does re-establish the virtual
link
to R3, but als installs a 150.1.3.3 as a directly connected route which
is
now far more favourable than the previously installed route via OSPF.
This
then results in the link flapping
I am pulling my hair out on this one (perhaps it is time to move on)
-----Original Message-----
From: Brian Dennis [mailto:bdennis@internetworkexpert.com]
Sent: 14 March 2005 22:28
To: simon hart; Group Study
Subject: RE: Dialer Watch
Try using the "no peer neighbor-route" command.
Brian Dennis, CCIE #2210 (R&S/ISP-Dial/Security)
bdennis@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987
Direct: 775-745-6404 (Outside the US and Canada)
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
simon hart
Sent: Monday, March 14, 2005 2:14 PM
To: Group Study
Subject: Dialer Watch
Hi Group,
I am going over IE lab 11 (again), and am confused with the Dialer watch
setup.
Within this lab there is a requirement to watch a a number of routes
(150.1.3.3 being one of them) and bring up the ISDN if the routes are
lost.
So far so good, however there is a dialer map statement i.e
dialer map ip 187.1.45.5 name Rack1R5 broadcast xxxxxx
.............(normal
map statement)
dialer map ip 150.1.3.3 name Rack1R5 broadcast
xxxxxx................(additional map statment for dialer watch)
Why is this needed? Does this not cause more problems.
I have found that once the dialer watch is invoked because of the lost
route
the ISDN link starts to flap.
After doing a an ip route debug it appears that the routing table will
install the 150.1.3.3 route as directly connected route because of the
dialer map statement. When the old route comes back on line, it is not
prefered because it is a route known via a routing protocol, however the
link will idle timeout after a set period, but will immediately come up
again because of the loss of the now directly connected route.
Any pointers appreciated
Simon
Simon
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.7.2 - Release Date: 11/03/2005
This archive was generated by hypermail 2.1.4 : Sun Apr 03 2005 - 17:56:45 GMT-3