From: Scott Morris (swm@emanon.com)
Date: Fri Sep 19 2003 - 19:12:59 GMT-3
No, no.... I was just thinking as I typed of large-scale solutions. :)
You can apply more than one watch-group to a physical interface. But I
think you have a limit of 10 watch-lists that you can create...
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
CISSP, JNCIS, et al.
IPExpert CCIE Program Manager
IPExpert Sr. Technical Instructor
swm@emanon.com/smorris@ipexpert.net
http://www.ipexpert.net
-----Original Message-----
From: navaid@rogers.com [mailto:navaid@rogers.com]
Sent: Friday, September 19, 2003 6:11 PM
To: Scott Morris; 'Roberts, Larry'; 'seonghui'; EToker@secura.com.tr
Cc: ccielab@groupstudy.com
Subject: Re: RE: question on dialer watch-list
So it mean that if I want to watch 2 routes and dial when either of the
route disappear I have to use dialer profile with two different dialer
watch lists for each profile.
Navaid
>
> From: "Scott Morris" <swm@emanon.com>
> Date: 2003/09/19 Fri PM 02:23:16 EDT
> To: "'Roberts, Larry'" <Larry.Roberts@expanets.com>,
> "'seonghui'"
> <seonghui@vads.com>, <EToker@secura.com.tr>
> CC: <ccielab@groupstudy.com>
> Subject: RE: question on dialer watch-list
>
> Very interesting article... And that does appear to be correct. Even
> though the semi-unrelated routes in my case (both /28's) did not
> disappear from the routing table, when I watched the 'debug dialer'
> output, they were shown as both down and therefore the primary went
> down.
>
> When I added a 1.1.1.1/32 route that I had to the dialer list, and
> made it go away, the dialer watch noted that the specific route was
> down, but showed the primary link as being up still and therefore did
> not react.
>
> Sounds like a bug in watching for routes. But otherwise you are
> correct, it appears to be a logical AND for routes listed on the
> dialer-watch. That makes it a little less fun then for different
> callout to different routers. It only attempted to call out the
> dialer map of the first numeric entry (1.1.1.1) to reestablish a
> connection.
>
> Hmmmm..
>
> Good find on the article, by the way.
>
> Scott
>
>
>
> -----Original Message-----
> From: Roberts, Larry [mailto:Larry.Roberts@expanets.com]
> Sent: Friday, September 19, 2003 1:40 PM
> To: 'Scott Morris'; 'seonghui'; EToker@secura.com.tr
> Cc: ccielab@groupstudy.com
> Subject: RE: question on dialer watch-list
>
>
> Can you try it with 2 completely unrelated routes that don't have a
> summary ( /28 in your case ) that points to those network's.
>
> It should require ALL routes to be gone.
>
> See below...
>
> http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1828/product
> s_
> configuration_guide_chapter09186a00800872ed.html
>
>
>
>
> Thanks
>
> Larry
>
> -----Original Message-----
> From: Scott Morris [mailto:swm@emanon.com]
> Sent: Friday, September 19, 2003 10:47 AM
> To: 'seonghui'; EToker@secura.com.tr
> Cc: ccielab@groupstudy.com
> Subject: RE: question on dialer watch-list
>
>
> The answer is #1. Either route going away will cause it to dial
> immediately. I set it up briefly on a lab router here, so the output
> is a bit long but you'll see what you want...
>
>
> Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
> CISSP, JNCIS, et al. IPExpert CCIE Program Manager IPExpert Sr.
> Technical Instructor swm@emanon.com/smorris@ipexpert.net
> http://www.ipexpert.net
>
> ----------Output--------------
>
> RouterE#sh dialer
>
> BRI1/0 - dialer type = ISDN
>
> Dial String Successes Failures Last DNIS Last status
> 2752002 1 1 22:28:07 successful
> 2752022 30 22 17:55:34 successful
> 0 incoming call(s) have been screened.
> 0 incoming call(s) rejected for callback.
>
> BRI1/0:1 - dialer type = ISDN
> Idle timer (120 secs), Fast idle timer (20 secs)
> Wait for carrier (30 secs), Re-enable (15 secs)
> Dialer state is idle
>
> BRI1/0:2 - dialer type = ISDN
> Idle timer (120 secs), Fast idle timer (20 secs)
> Wait for carrier (30 secs), Re-enable (15 secs)
> Dialer state is idle
>
> RouterE#sh ip ro
> 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 207.49.165.2 to network 0.0.0.0
>
> 1.0.0.0/32 is subnetted, 1 subnets
> O E2 1.1.1.1 [140/0] via 207.49.165.2, 17:54:59, Serial0/1.1
> 10.0.0.0/24 is subnetted, 1 subnets
> O IA 10.4.4.0 [110/65] via 207.49.165.2, 17:54:59, Serial0/1.1
> C 208.158.37.0/24 is directly connected, Ethernet1/0
> 11.0.0.0/24 is subnetted, 1 subnets
> C 11.11.11.0 is directly connected, Loopback0
> 207.49.165.0/24 is variably subnetted, 4 subnets, 2 masks
> C 207.49.165.64/30 is directly connected, BRI1/0
> C 207.49.165.0/30 is directly connected, Serial0/1.1
> O E2 207.49.165.0/28 [110/0] via 207.49.165.2, 17:55:00,
Serial0/1.1
> O IA 207.49.165.128/28 [110/74] via 207.49.165.2, 17:55:00,
> Serial0/1.1
> O*E2 0.0.0.0/0 [110/0] via 207.49.165.2, 17:55:00, Serial0/1.1
> RouterE#
>
> RouterE#conf t
> Enter configuration commands, one per line. End with CNTL/Z.
> RouterE(config)#dialer watch-list 1 ip 207.49.165.128 255.255.255.240
> RouterE(config)#dialer watch-list 1 ip 207.49.165.0 255.255.255.240
> RouterE(config)#int bri 1/0 RouterE(config-if)#dialer map ip
> 207.49.165.0 name RouterF broadcast 2752022 RouterE(config-if)#dialer
> map ip 207.49.165.128 name RouterF broadcast
> 2752022
> RouterE(config-if)#dialer watch-group 1
> RouterE(config-if)#^Z
>
>
> RouterE#sh ip ro
> 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 207.49.165.2 to network 0.0.0.0
>
> 1.0.0.0/32 is subnetted, 1 subnets
> O E2 1.1.1.1 [140/0] via 207.49.165.2, 17:58:32, Serial0/1.1
> 10.0.0.0/24 is subnetted, 1 subnets
> O IA 10.4.4.0 [110/65] via 207.49.165.2, 17:58:32, Serial0/1.1
> C 208.158.37.0/24 is directly connected, Ethernet1/0
> 11.0.0.0/24 is subnetted, 1 subnets
> C 11.11.11.0 is directly connected, Loopback0
> 207.49.165.0/24 is variably subnetted, 4 subnets, 2 masks
> C 207.49.165.64/30 is directly connected, BRI1/0
> C 207.49.165.0/30 is directly connected, Serial0/1.1
> O E2 207.49.165.0/28 [110/0] via 207.49.165.2, 17:58:33,
Serial0/1.1
> O IA 207.49.165.128/28 [110/74] via 207.49.165.2, 17:58:33,
> Serial0/1.1
> O*E2 0.0.0.0/0 [110/0] via 207.49.165.2, 17:58:33, Serial0/1.1
>
> RouterE#
>
> <<<At this point, I made a single route (207.49.165.0/28) go away from
> the other side. It was the second entry from the list. Immediately,
> it dialed up.>>>>
>
> 2d15h: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
> 2d15h: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to 2752022
> RouterF
> 2d15h: %ISDN-6-DISCONNECT: Interface BRI1/0:1 disconnected from
> 2752022 RouterF, call lasted 2 seconds
> 2d15h: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to downsh ip
> ro
>
> <<<< Callback works too. :) >>>>
>
> 2d15h: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to up
> 2d15h: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
> 2d15h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
> changed state to up
> 2d15h: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Virtual-Access1, changed state to up
> 2d15h: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to 2752022
> RouterF RouterE#sh ip ro
> 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 207.49.165.65 to network 0.0.0.0
>
> C 208.158.37.0/24 is directly connected, Ethernet1/0
> 11.0.0.0/24 is subnetted, 1 subnets
> C 11.11.11.0 is directly connected, Loopback0
> 207.49.165.0/24 is variably subnetted, 3 subnets, 2 masks
> C 207.49.165.64/30 is directly connected, BRI1/0
> C 207.49.165.0/30 is directly connected, Serial0/1.1
> O E2 207.49.165.128/28 [110/100] via 207.49.165.2, 00:00:23,
> Serial0/1.1
> S* 0.0.0.0/0 [250/0] via 207.49.165.65
>
>
> <<<Then I just restored the route. S0/1.1 is preferred by metric even
> though BRI is still up for a short while>>>
>
> RouterE#sh ip ro
> 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 207.49.165.2 to network 0.0.0.0
>
> 1.0.0.0/32 is subnetted, 1 subnets
> O E2 1.1.1.1 [140/0] via 207.49.165.2, 00:00:04, Serial0/1.1
> 10.0.0.0/24 is subnetted, 1 subnets
> O IA 10.4.4.0 [110/65] via 207.49.165.2, 00:00:14, Serial0/1.1
> C 208.158.37.0/24 is directly connected, Ethernet1/0
> 11.0.0.0/24 is subnetted, 1 subnets
> C 11.11.11.0 is directly connected, Loopback0
> 207.49.165.0/24 is variably subnetted, 4 subnets, 2 masks
> C 207.49.165.64/30 is directly connected, BRI1/0
> O E2 207.49.165.0/28 [110/0] via 207.49.165.2, 00:00:05,
Serial0/1.1
> C 207.49.165.0/30 is directly connected, Serial0/1.1
> O IA 207.49.165.128/28 [110/74] via 207.49.165.2, 00:00:11,
> Serial0/1.1
> O*E2 0.0.0.0/0 [110/0] via 207.49.165.2, 00:00:05, Serial0/1.1
> RouterE# RouterE#
>
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of seonghui
> Sent: Friday, September 19, 2003 11:17 AM
> To: EToker@secura.com.tr
> Cc: ccielab@groupstudy.com
> Subject: RE: question on dialer watch-list
>
>
> Hi EToker,
>
> Thanks for your feedback. From your 2nd sentence, I can see that you
> choose answer 2. I received quite a number of answers offline, they
> chose answer 1. Has anyone tested this? I would really like to test it
> out on my lab, but my ISDN simulator has not arrived yet. Can anyone
> confirm this? Thanks..
>
>
> -----Original Message-----
> From: EToker@secura.com.tr [mailto:EToker@secura.com.tr]
> Sent: Friday, September 19, 2003 7:52 PM
> To: Seonghui@vads.com; ccielab@groupstudy.com
> Subject: RE: question on dialer watch-list
>
>
> Hi,
> It checks at least one valid route for the watched networks. It will
> not trigger if at least one of the routes is still available.
>
> -----Original Message-----
> From: Seonghui [mailto:Seonghui@vads.com]
> Sent: 19 Eyl|l 2003 Cuma 11:32
> To: ccielab@groupstudy.com
> Subject: question on dialer watch-list
>
>
> Hi Group,
>
> Sorry to ask this question without testing it. I am still waiting for
> my ISDN simulator...
>
> I was going thru a dialer watch-list scenario and suddenly this
> question poped up in my head. If I have more than one network in my
> dialer watch-list to be 'watched' and they are in the same watch-list
> group 1, will the ISDN trigger based on:-
>
> 1) either route lost from the routing table?
> 2) Or both routes must dissappear from the routing table before the
ISDN
> initiate a call?
> 3) or will it based on only the first statement in the dialer
> watch-list? second statement is ignored?
>
> Below is the config:
>
> interface BRI1/0
> ip address 172.16.20.2 255.255.255.0
> encapsulation ppp
> shutdown
> dialer map ip 172.16.200.0 name r5 broadcast 77128888
> dialer map ip 172.16.100.0 name r5 broadcast 77128888
> dialer map ip 172.16.20.5 name r5 broadcast 77128888
> dialer watch-group 1
> isdn switch-type basic-net3
> ppp authentication chap
> !
>
> dialer watch-list 1 ip 172.16.200.0 255.255.255.128
> dialer watch-list 1 ip 172.16.100.0 255.255.255.128
>
> I tried searching the doc cd but the example is only for watching 1
> route.
>
> Thanks and regards - SH
>
> ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> ______________________________________________________________________
> _
> Please help support GroupStudy by purchasing your study materials
from:
> shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> [GroupStudy removed an attachment of type application/ms-tnef which
> had a name of winmail.dat]
>
> ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> ______________________________________________________________________
> _
> Please help support GroupStudy by purchasing your study materials
from:
> shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> ______________________________________________________________________
> _
> Please help support GroupStudy by purchasing your study materials
from:
> shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> ***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
> ______________________________________________________________________
> _
> Please help support GroupStudy by purchasing your study materials
from:
> shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
1
***Get your CCIE and a FREE vacation: Shop.GroupStudy.com***
This archive was generated by hypermail 2.1.4 : Wed Oct 01 2003 - 07:24:32 GMT-3