From: Wang Dehong-DWANG1 (Dehong.Wang@motorola.com)
Date: Fri Jul 09 2004 - 16:32:22 GMT-3
172.16.124.0/24 is in the routing table and is part of directly connected frame-relay networks. After I shut down the interface on frame-relay switch, the route went away.
R2#sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback3
3.0.0.0/24 is subnetted, 1 subnets
O E2 3.3.3.0 [110/20] via 172.16.35.5, 02:21:37, Serial0/1
4.0.0.0/24 is subnetted, 1 subnets
R 4.4.4.0 [100/1] via 172.16.234.4, 00:00:07, Serial0/0.234
O E2 5.0.0.0/8 [110/20] via 172.16.35.5, 02:21:37, Serial0/1
172.16.0.0/16 is variably subnetted, 16 subnets, 3 masks
C 172.16.234.0/24 is directly connected, Serial0/0.234
C 172.16.200.0/22 is directly connected, Loopback1
O IA 172.16.50.0/24 [110/74] via 172.16.35.5, 02:21:38, Serial0/1
C 172.16.35.5/32 is directly connected, Serial0/1
O E2 172.16.35.3/32 [110/20] via 172.16.35.5, 02:21:38, Serial0/1
R 172.16.35.0/24 [100/1] via 172.16.234.3, 00:00:01, Serial0/0.234
D 172.16.16.0/24 [90/2171904] via 172.16.124.1, 00:00:57,
Serial0/0.124
C 172.16.12.0/24 is directly connected, BRI1/0
C 172.16.124.0/24 is directly connected, Serial0/0.124 <----------------
R 172.16.110.0/24 [100/2] via 172.16.234.4, 00:00:00, Serial0/0.234
R 172.16.104.0/24 [100/1] via 172.16.234.4, 00:00:00, Serial0/0.234
O IA 172.16.105.0/24 [110/65] via 172.16.35.5, 02:21:39, Serial0/1
D 172.16.106.0/24 [90/2299904] via 172.16.124.1, 00:00:57,
Serial0/0.124
D 172.16.100.0/22 [90/2297856] via 172.16.124.1, 00:00:57,
Serial0/0.124
C 172.16.102.0/24 is directly connected, Loopback0
R 172.16.64.0/24 [100/1] via 172.16.234.4, 00:00:00, Serial0/0.234
22.0.0.0/24 is subnetted, 1 subnets
C 22.22.22.0 is directly connected, Loopback2
7.0.0.0/24 is subnetted, 3 subnets
O E2 7.7.1.0 [110/20] via 172.16.35.5, 02:21:39, Serial0/1
O IA 7.7.2.0 [110/75] via 172.16.35.5, 02:21:40, Serial0/1
O IA 7.7.3.0 [110/75] via 172.16.35.5, 02:21:40, Serial0/1
44.0.0.0/24 is subnetted, 1 subnets
D 44.44.44.0 [90/2297856] via 172.16.124.4, 00:01:41, Serial0/0.124
R2#
*Mar 1 20:58:05.914: %LINK-3-UPDOWN: Interface Serial0/0, changed state to
down
*Mar 1 20:58:05.934: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
172.16.124.1 (Serial0/0.124) is down: interface down
*Mar 1 20:58:05.938: destroy peer: 172.16.124.1
*Mar 1 20:58:05.938: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 100: Neighbor
172.16.124.4 (Serial0/0.124) is down: interface down
R2#
*Mar 1 20:58:05.942: destroy peer: 172.16.124.4
R2#
*Mar 1 20:58:06.914: %LINEPROTO-5-UPDOWN: Line protocol on Interface
Serial0/0, changed state to down
R2# sh ip route
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
area
* - candidate default, U - per-user static route, o - ODR
P - periodic downloaded static route
Gateway of last resort is not set
2.0.0.0/24 is subnetted, 1 subnets
C 2.2.2.0 is directly connected, Loopback3
3.0.0.0/24 is subnetted, 1 subnets
O E2 3.3.3.0 [110/20] via 172.16.35.5, 02:22:07, Serial0/1
O E2 5.0.0.0/8 [110/20] via 172.16.35.5, 02:22:07, Serial0/1
172.16.0.0/16 is variably subnetted, 9 subnets, 3 masks
O E2 172.16.234.0/24 [110/20] via 172.16.35.5, 00:00:14, Serial0/1
C 172.16.200.0/22 is directly connected, Loopback1
O IA 172.16.50.0/24 [110/74] via 172.16.35.5, 02:22:07, Serial0/1
C 172.16.35.5/32 is directly connected, Serial0/1
O E2 172.16.35.3/32 [110/20] via 172.16.35.5, 02:22:08, Serial0/1
O 172.16.35.0/24 [110/128] via 172.16.35.5, 00:00:18, Serial0/1
C 172.16.12.0/24 is directly connected, BRI1/0
O IA 172.16.105.0/24 [110/65] via 172.16.35.5, 02:22:09, Serial0/1
C 172.16.102.0/24 is directly connected, Loopback0
22.0.0.0/24 is subnetted, 1 subnets
C 22.22.22.0 is directly connected, Loopback2
7.0.0.0/24 is subnetted, 3 subnets
O E2 7.7.1.0 [110/20] via 172.16.35.5, 02:22:09, Serial0/1
O IA 7.7.2.0 [110/75] via 172.16.35.5, 02:22:09, Serial0/1
O IA 7.7.3.0 [110/75] via 172.16.35.5, 02:22:09, Serial0/1
-----Original Message-----
From: Ryan, Jeff [mailto:jryan@wamnetgov.com]
Sent: Friday, July 09, 2004 2:17 PM
To: Wang Dehong-DWANG1; ccielab@groupstudy.com
Subject: RE: dialer watch failed..
Did you verify that the 172.16.124.0/24 network is in your routing
table?
Also, is that network being learned by a routing protocol like EIGRP?
Jeff Ryan
Chief Engineer
Design & Implementation
WAM!NET Government Services, Inc.
13665 Dulles Technology Drive, Herndon, VA 20171
Office: 703-480-2581
Mobile: 301-675-7344
AIM: Jeff Ryan WN Get my pgp key @ http://pgpkeys.mit.edu
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Wang Dehong-DWANG1
Sent: Friday, July 09, 2004 1:12 PM
To: ccielab@groupstudy.com
Subject: dialer watch failed..
Question for the ISDN experts.. I worked on a lab scenario to use dialer
watch, but for some reasons the dialer watch did not get the connections
up. I know the rule of dialer watch is to make sure watched route is in
the routing table.. Dailer watch did take some actions, but failed with
dialer map/string not present, but I do have dialer map string in the
bri.
Any comments? thanks.
- Dehong
R2#sg
*Mar 1 01:56:25: DDR: Dialer Watch: watch-group = 1
*Mar 1 01:56:25: DDR: network 172.16.124.0/255.255.255.0 DOWN,
*Mar 1 01:56:25: DDR: primary DOWN
*Mar 1 01:56:25: DDR: Dialer Watch: Dial Reason: Primary of group 1
DOWN
*Mar 1 01:56:25: DDR: Dialer Watch watch-group 1 -
dialer map/string not present on BR1
R2#
R2#
R2
======
username R1 password 0 cisco
interface BRI1/0
ip address 172.16.12.2 255.255.255.0
encapsulation ppp
dialer map ip 172.16.12.1 name R1 broadcast 8358661
dialer map ip 172.16.12.1 name R1 broadcast 8358663
dialer watch-group 1
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866201
isdn spid2 0835866401
no peer neighbor-route
ppp authentication chap
access-list 107 deny eigrp any any
access-list 107 permit ip any any
dialer watch-list 1 ip 172.16.124.0 255.255.255.0
dialer-list 1 protocol ip list 107
R1
======
username R2 password 0 cisco
interface BRI0/0
ip address 172.16.12.1 255.255.255.0
encapsulation ppp
dialer map ip 172.16.12.2 name R2 broadcast 8358662
isdn switch-type basic-ni
isdn spid1 0835866101
isdn spid2 0835866301
no peer neighbor-route
ppp authentication chap
end
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:51 GMT-3