From: Jeongwoo Park (jpark@wams.com)
Date: Sun May 18 2003 - 19:21:09 GMT-3
Without dialer-group 1, isdn line flaps every 120 seconds.
JP
-----Original Message-----
From: Ram Shummoogum [mailto:rshummoo@ca.ibm.com]
Sent: Sunday, May 18, 2003 2:53 PM
To: jpark@wams.com
Cc: ccielab@groupstudy.com
Subject: RE: Problems with OSPF & Dialer Watch
remove the dialer-group 1
Jeongwoo Park <jpark@wams.com> on 05/18/2003 04:52:49 PM
To: "'Barry'" <reachbarry@cox.net>, "'Tim Fletcher'"
<tim@fletchmail.net>, dwight baldwin <dtstone01@yahoo.com>,
ccielab@groupstudy.com, Ram Shummoogum/Quebec/IBM@IBMCA
cc:
Subject: RE: Problems with OSPF & Dialer Watch
Thanks for your inputs. My dialer wiatch kicked in after the serial went
down.
Now problem is that the backup interface doesn't go down after the serial
interface comes back up.
Here is the config and debug dialer, debug dialer event, and debug dialer
packet.
My dialer debug shows that the route watched by dialer watch is still down.
interface BRI0/0
ip address 172.16.12.2 255.255.255.0
encapsulation ppp
ip ospf message-digest-key 1 md5 cisco
dialer idle-timeout 30
dialer watch-disable 1
dialer map ip 172.16.12.1 name r1 broadcast 8358661
dialer map ip 192.168.1.0 name r1 broadcast 8358663
dialer load-threshold 1 outbound
dialer watch-group 1
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866201 8358662
isdn spid2 0835866401 8358664
no peer neighbor-route
ppp authentication chap
ppp multilink
access-list 101 deny ospf any any
access-list 101 permit ip any any
dialer watch-list 1 ip 192.168.1.0 255.255.255.0
dialer-list 1 protocol ip list 101
==================================
Debug;
1d23h: Vi1 DDR: idle timeout
1d23h: DDR: Dialer Watch: watch-group = 1
1d23h: DDR: network 192.168.1.0/255.255.255.0 DOWN,
1d23h: DDR: primary DOWN
r2#
1d23h: BR0/0 DDR: ip (s=172.16.12.2, d=224.0.0.5), 84 bytes, outgoing
uninteresting (list 101)
1d23h: BR0/0 DDR: sending broadcast to ip 172.16.12.1
1d23h: BR0/0 DDR: sending broadcast to ip 192.168.1.0 -- succeeded
r2#
1d23h: BR0/0 DDR: ip (s=172.16.12.2, d=224.0.0.5), 84 bytes, outgoing
uninteresting (list 101)
1d23h: BR0/0 DDR: sending broadcast to ip 172.16.12.1
1d23h: BR0/0 DDR: sending broadcast to ip 192.168.1.0 -- succeeded
r2#
1d23h: BR0/0 DDR: ip (s=172.16.12.2, d=224.0.0.5), 84 bytes, outgoing
uninteresting (list 101)
1d23h: BR0/0 DDR: sending broadcast to ip 172.16.12.1
1d23h: BR0/0 DDR: sending broadcast to ip 192.168.1.0 -- succeeded
r2#
1d23h: BR0/0 DDR: cdp, 275 bytes, outgoing uninteresting (no list matched)
1d23h: BR0/0 DDR: sending broadcast to ip 172.16.12.1
1d23h: BR0/0 DDR: sending broadcast to ip 192.168.1.0 -- succeeded
r2#
1d23h: Vi1 DDR: idle timeout
1d23h: DDR: Dialer Watch: watch-group = 1
1d23h: DDR: network 192.168.1.0/255.255.255.0 DOWN,
1d23h: DDR: primary DOWN
-----Original Message-----
From: Barry [mailto:reachbarry@cox.net]
Sent: Saturday, May 17, 2003 7:57 PM
To: Jeongwoo Park; 'Tim Fletcher'; dwight baldwin; ccielab@groupstudy.com
Subject: RE: Problems with OSPF & Dialer Watch
You should have a dialer map statement for the route you are watching.
Why don't you have a ospf demand circuit statement?
This should keep you from having to use access-list 101.
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Jeongwoo Park
Sent: Saturday, May 17, 2003 4:56 PM
To: 'Tim Fletcher'; dwight baldwin; ccielab@groupstudy.com
Subject: RE: Problems with OSPF & Dialer Watch
My dialer-watch is not working with/ without dialer-list/dialer-group.
But it works without access-list.
Something weird is happening.
Here is config
<with dialer-group>
interface BRI0/0
ip address 172.16.12.2 255.255.255.0
encapsulation ppp
ip ospf message-digest-key 1 md5 cisco
dialer idle-timeout 30
dialer map ip 172.16.12.1 name r1 broadcast 8358661
dialer map ip 172.16.12.1 name r1 broadcast 8358663
dialer load-threshold 1 outbound
dialer watch-group 1
dialer-group 1
isdn switch-type basic-ni
isdn spid1 0835866201 8358662
isdn spid2 0835866401 8358664
no peer neighbor-route
ppp authentication chap
ppp multilink
access-list 101 deny ospf any any
access-list 101 permit ip any any
dialer watch-list 1 ip 192.168.1.0 255.255.255.0
dialer-list 1 protocol ip list 101
<without dialer-group>
interface BRI0/0
ip address 172.16.12.2 255.255.255.0
encapsulation ppp
ip ospf message-digest-key 1 md5 cisco
dialer idle-timeout 30
dialer map ip 172.16.12.1 name r1 broadcast 8358661
dialer map ip 172.16.12.1 name r1 broadcast 8358663
dialer load-threshold 1 outbound
dialer watch-group 1
isdn switch-type basic-ni
isdn spid1 0835866201 8358662
isdn spid2 0835866401 8358664
no peer neighbor-route
ppp authentication chap
ppp multilink
access-list 101 deny ospf any any
access-list 101 permit ip any any
dialer watch-list 1 ip 192.168.1.0 255.255.255.0
dialer-list 1 protocol ip list 101
<without access-list 101 and with dialer-group 1>
ISDN----kicks in.
r2(config)#no access-list 101
r2(config)#
23:26:165370847584: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to
23:26:38: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
23:26:171798691839: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to
23:26:169671478200: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected
r2(config)#
23:26:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, chang
23:26:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1
23:26:40: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:2, chang
r2(config)#
23:26:45: %ISDN-6-CONNECT: Interface BRI0/0:2 is now connected to 8358661
r2(config)#
23:26:48: %OSPF-5-ADJCHG: Process 1, Nbr 192.168.1.1 on BRI0/0 from LOADI
r2(config)#
It is really weird. I have heard about some bugs on watch-list for a while.
I wonder if it is one of those.
-----Original Message-----
From: Tim Fletcher [mailto:tim@fletchmail.net]
Sent: Saturday, May 17, 2003 7:37 AM
To: dwight baldwin; ccielab@groupstudy.com
Subject: Re: Problems with OSPF & Dialer Watch
Dwight,
The 1st problem is probably caused by the idle timeout on the far side.
Since it is not doing dialer watch, it will time out and drop the
connection. The dialer watch side will then bring it back up immediately.
The result is that every timeout interval, you connection will flap. The
solution is to set the idle timeout on the far side to 0, thereby disabling
it.
As far as demand-circuit and dialer-list, dialer watch doesn't care about
interesting traffic, so you do not need dialer-group or dialer-list. When
dialer watch goes active, it brings the connection up and keeps it up until
there is a route to one of the watched routes through another interface.
Dialer-group and dialer-list can still be used, but the effect they have
will be to bring up the circuit when dialer watch is not active.
-Tim Fletcher #11406
At 04:29 PM 5/16/03 -0700, dwight baldwin wrote:
>Hi All,
>
>I'm having trouble getting dialer watch to work with
>OSPF. Whenever I shutdown the primary path, the ISDN
>dial comes up fine and with the "show dialer" command
>the dialer reason states "Dial reason: Dialing on
>watched route loss". However, the idle timer never
>resets and when it expires, the ISN line goes down.
>Anybody seen this problem or have any ideas about this
>should be fixed? Also, isn't is best practice to use
>this in conjunction with an ospf demand circut & to
>deny ospf with the dialer-list command? Here is may
>relavant config:
>
>interface BRI0
> ip address 133.1.50.5 255.255.255.252
> encapsulation ppp
> shutdown
> dialer idle-timeout 30
> dialer map ip 133.1.50.6 name R6-2503 broadcast
>9082774366
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 90827716440101
> no peer neighbor-route
> no cdp enable
> ppp authentication chap
>
>dialer-list 1 protocol ip list 111
>
>access-list 111 deny ospf any any
>access-list 111 permit ip any any
>
>Dwight
>
>
>__________________________________
>Do you Yahoo!?
>The New Yahoo! Search - Faster. Easier. Bingo.
>http://search.yahoo.com
This archive was generated by hypermail 2.1.4 : Mon Jun 02 2003 - 15:13:44 GMT-3