From: Nathan Kleven (nkleven@intellinet.ws)
Date: Mon Nov 11 2002 - 13:16:42 GMT-3
Are you using a static route with a high metric to trigger the BRI in a
failed condition, it looks like you are using RIP. The RIP traffic maybe
keeping the link up. What have you listed as interesting traffic? Can you
paste in your configuration?
__________
Nate Kleven
Senior Network Engineer, CCNP Voice Access, MCSE
Expanets
6020 So 190th ST
Kent, WA 98032
(206)219.6135
"Experienced at Networked Solutions"
-----Original Message-----
From: Nathan Chessin [mailto:nchessin@cisco.com]
Sent: Monday, November 11, 2002 12:22 AM
To: ccielab@groupstudy.com
Subject: Dialer Watch Issues
Hi All,
I am having trouble with dialer watch. The backup (bri) interface comes up
all right, but it doesn't go down when the primary comes back up.
My routing table looks like:
Gateway of last resort is not set
R 3.0.0.0/8 [120/1] via 10.1.1.3, 00:00:27, BRI1/0
[120/1] via 20.1.1.3, 00:00:27, Serial0/2
R 4.0.0.0/8 [120/1] via 10.1.1.3, 00:00:27, BRI1/0
[120/1] via 20.1.1.3, 00:00:27, Serial0/2
20.0.0.0/24 is subnetted, 1 subnets
C 20.1.1.0 is directly connected, Serial0/2
R 5.0.0.0/8 [120/1] via 10.1.1.3, 00:00:27, BRI1/0
[120/1] via 20.1.1.3, 00:00:27, Serial0/2
10.0.0.0/24 is subnetted, 1 subnets
C 10.1.1.0 is directly connected, BRI1/0
What are the issues with the serial interface coming back up, and not being
able to get the dialer watch bri down?
Nate
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:22:56 GMT-3