RE: Dialer Watch with Dialer Maps. Why does it only work with

From: Kenneth Wygand (KWygand@customonline.com)
Date: Wed Aug 06 2003 - 12:16:49 GMT-3


John,

Did you remember to update your dialer map statements to include the
route you are watching?

Kenneth E. Wygand
Systems Engineer, Project Services
CISSP #37102, CCNP, CCDP, MCP 2000, CNA 5.1, Network+, A+
Custom Computer Specialists, Inc.
"It's not just about ending up where you want to be, it's about making
the most of the trip there."
-Anonymous

-----Original Message-----
From: John Hopkins [mailto:ccie1234@hotmail.com]
Sent: Wednesday, August 06, 2003 11:15 AM
To: Kenneth Wygand; ccielab@groupstudy.com
Subject: RE: Dialer Watch with Dialer Maps. Why does it only work with
classful watched nets

I don't think that it is a PPP negotiation problem since if I watch a
/24
route, everything works fine. Also, if I replace the dialer maps with
dialer string commands, it works fine as well.

I did a debug dialer event, and this showed me that the Dialer watch
noticed
the missing route, but nothing dialed.

>From: "Kenneth Wygand" <KWygand@customonline.com>
>To: "John Hopkins" <ccie1234@hotmail.com>,<ccielab@groupstudy.com>
>Subject: RE: Dialer Watch with Dialer Maps. Why does it only work with

>classful watched nets
>Date: Wed, 6 Aug 2003 11:06:56 -0400
>
>You mentioned:
>
>"When I try to watch any /32 route, or even the /25 routes (describing
>the
>correct network and mask in the dialer watch-list command), dialer
watch
>
>sees that the network has disappeared from the route table, but the
ISDN
>
>doesn't dial. I'm assuming that this might have something to do with
>the
>dialer map command."
>
>Did you also remember to update your dialer map statements to include
>the route you are watching?
>
>Also, when you say:
>
>"...dialer watch
>sees that the network has disappeared from the route table, but the
ISDN
>
>doesn't dial."
>
>Are you verifying this through a debug command? Can you "debug ppp
>negotiation" at the same time?
>
>Kenneth E. Wygand
>Systems Engineer, Project Services
>CISSP #37102, CCNP, CCDP, MCP 2000, CNA 5.1, Network+, A+
>Custom Computer Specialists, Inc.
>70 Suffolk Court
>Hauppauge, NY 11788
>(631) 864-6699 x1755
>"It's not just about ending up where you want to be, it's about making
>the most of the trip there."
>-Anonymous
>
>-----Original Message-----
>From: John Hopkins [mailto:ccie1234@hotmail.com]
>Sent: Wednesday, August 06, 2003 10:44 AM
>To: ccielab@groupstudy.com
>Subject: Dialer Watch with Dialer Maps. Why does it only work with
>classful watched nets
>
>Here is a route table from my lab topology
>
>R2#sir
>Codes: C - connected, S - static, I - IGRP, 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, E - EGP
> 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
>
> 140.10.0.0/25 is subnetted, 1 subnets
>i L2 140.10.1.0 [115/10] via 151.30.26.6, Ethernet0
>O E1 198.1.3.0/24 [110/100064] via 151.30.124.1, 00:00:06, Serial0.1
> 151.30.0.0/16 is variably subnetted, 23 subnets, 3 masks
>O E1 151.30.135.0/24 [110/84] via 151.30.124.1, 00:00:06, Serial0.1
>O IA 151.30.44.128/25 [110/113] via 151.30.124.1, 00:00:06,
Serial0.1
>O 151.30.200.0/25 [110/123] via 151.30.124.1, 00:00:06, Serial0.1
>O E1 151.30.10.0/24 [110/200122] via 151.30.124.1, 00:00:06,
>Serial0.1
>C 151.30.12.0/24 is directly connected, BRI0
>C 151.30.26.0/24 is directly connected, Ethernet0
>O IA 151.30.20.0/24 [110/123] via 151.30.124.1, 00:00:07, Serial0.1
>O 151.30.43.0/24 [110/176] via 151.30.124.1, 00:00:07, Serial0.1
>O IA 151.30.34.0/24 [110/122] via 151.30.124.1, 00:00:07, Serial0.1
>C 151.30.50.0/24 is directly connected, Tunnel10
>C 151.30.52.0/24 is directly connected, Loopback300
>R 151.30.55.0/24 [120/1] via 151.30.50.5, 00:00:06, Tunnel10
>i L2 151.30.66.0/25 [115/10] via 151.30.26.6, Ethernet0
>O E1 151.30.100.5/32 [110/84] via 151.30.124.1, 00:00:07, Serial0.1
>O 151.30.100.4/32 [110/113] via 151.30.124.1, 00:00:07, Serial0.1
>O IA 151.30.100.7/32 [110/123] via 151.30.124.1, 00:00:07, Serial0.1
>i L2 151.30.100.6/32 [115/20] via 151.30.26.6, Ethernet0
>O 151.30.100.1/32 [110/65] via 151.30.124.1, 00:00:07, Serial0.1
>O 151.30.100.3/32 [110/123] via 151.30.124.1, 00:00:07, Serial0.1
>C 151.30.100.2/32 is directly connected, Loopback102
>O 151.30.124.4/32 [110/112] via 151.30.124.1, 00:00:08, Serial0.1
>O 151.30.124.1/32 [110/64] via 151.30.124.1, 00:00:08, Serial0.1
>C 151.30.124.0/24 is directly connected, Serial0.1
>R2#
>
>
>I configured Dialer Watch as follows:
>
>dialer watch-list 3 ip 151.30.10.0 255.255.255.0
>int bri0
>dialer watch-group 3
>dialer map ip 151.30.10.0 name R1 broad 5552008
>dialer map ip 151.30.10.0 name R1 broad 5552009
>
>plus the usual dialer maps and ISDN config commands on this interface.
>
>This works fine.
>
>When I try to watch any /32 route, or even the /25 routes (describing
>the
>correct network and mask in the dialer watch-list command), dialer
watch
>
>sees that the network has disappeared from the route table, but the
ISDN
>
>doesn't dial. I'm assuming that this might have something to do with
>the
>dialer map command.
>
>Does this mean that you can only watch a route that meets classful
>definitions? Why won't dialer watch work with these routes? I don't
>remember reading any such prohibition (athough I remember reading
>something
>about problems with watching /32 routes).
>
>Thanks
>
>_________________________________________________________________
>Tired of spam? Get advanced junk mail protection with MSN 8.
>http://join.msn.com/?page=features/junkmail
>
>
>_______________________________________________________________________
>You are subscribed to the GroupStudy.com CCIE R&S Discussion Group.
>
>Subscription information may be found at:
>http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Tue Sep 02 2003 - 18:53:54 GMT-3