From: Yu Kay (kaykkyu@yahoo.com)
Date: Mon May 19 2003 - 03:37:23 GMT-3
try to set the idle-timeout at remote site = 0
(disable it). otherwise it will diable the link by
default 120 seconds.
--- Jeongwoo Park <jpark@wams.com> wrote:
> The flapping results;
>
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface BRI0/0:1, changed
> state to down
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface BRI0/0:2, changed
> state to down
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface Virtual-Access1,
> changed state to down
> 2d00h: %ISDN-6-DISCONNECT: Interface BRI0/0:1
> disconnected from 8358663 r1,
> call lasted 121 seconds
> 2d00h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed
> state to down
> 2d00h: %ISDN-6-DISCONNECT: Interface BRI0/0:2
> disconnected from 8358661 r1,
> call lasted 120 seconds
> --More--
> 2d00h: %LINK-3-UPDOWN: Interface BRI0/0:2, changed
> state to down
> 2d00h: %LINK-3-UPDOWN: Interface BRI0/0:1, changed
> state to up
> 2d00h: %LINK-3-UPDOWN: Interface Virtual-Access1,
> changed state to up
> --More--
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface BRI0/0:1, changed
> state to up
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface Virtual-Access1,
> changed state to up
> --More--
> 2d00h: %LINK-3-UPDOWN: Interface BRI0/0:2, changed
> state to up
> --More--
> 2d00h: %LINEPROTO-5-UPDOWN: Line protocol on
> Interface BRI0/0:2, changed
> state to up
> --More--
> 2d00h: %ISDN-6-CONNECT: Interface BRI0/0:1 is now
> connected to 8358661 r1
> --More--
> 2d00h: %ISDN-6-CONNECT: Interface BRI0/0:2 is now
> connected to 8358661 r1
>
> -----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
>
=== message truncated ===
__________________________________
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:45 GMT-3