From: Rohan Grover (rohang@cisco.com)
Date: Thu Oct 28 2004 - 10:51:48 GMT-3
Hi,
I have following topology
R1 -----serial----R2
-----pri-------
I have configured dialer-watch on R1
==========================================
R1#sh run int s5/0:23
Building configuration...
Current configuration : 470 bytes
!
interface Serial5/0:23
ip address 150.50.9.2 255.255.255.192
encapsulation ppp
ip ospf cost 70
dialer idle-timeout 30
dialer map ip 2.2.2.2 name R2 broadcast 222222
dialer map ip 150.50.9.5 name R2 broadcast 222222
dialer load-threshold 1 outbound
dialer watch-group 1
dialer-group 1
isdn switch-type primary-ni
isdn protocol-emulate network
isdn incoming-voice data
ppp authentication chap
ppp multilink
end
<output ommitted>
access-list 101 deny ospf any any
access-list 101 permit ip any any
dialer watch-list 1 ip 2.2.2.2 255.255.255.255
dialer watch-list 1 delay connect 50
dialer watch-list 1 delay disconnect 15
dialer-list 1 protocol ip list 101
========================================
2.2.2.2/32 is known via ospf across the serial link
When I shut the serial link the pri link comes up because of dialer-watch.
But I don't see 2.2.2.2/32 as an ospf route but rather as a connected route. I don't understand why?
I know the solution is to use 'no peer neighbour-route' under the pri int but the logic is not clear to me.
Also whether or not 'peer neighbour-route' is used, after the idle timeout (30 secs) the pri link is torn down and then immediately
restarted.
==========
22:18:13: Vi1 DDR: idle timeout
22:18:13: DDR: Dialer Watch: watch-group = 1
22:18:13: DDR: network 2.2.2.2/255.255.255.255 UP,
22:18:13: DDR: primary DOWN
22:18:13: Vi1 DDR: disconnecting call
22:18:13: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down
22:18:13: %ISDN-6-DISCONNECT: Interface Serial5/0:0 disconnected from 222222 R2, call lasted 30 seconds
22:18:13: %LINK-3-UPDOWN: Interface Serial5/0:0, changed state to down
22:18:13: DDR: Dialer Watch: watch-group = 1
22:18:13: DDR: network 2.2.2.2/255.255.255.255 UP,
22:18:13: DDR: primary DOWN
22:18:13: DDR: Dialer Watch: Dial Reason: Secondary of group 1 AVAILABLE
22:18:13: DDR: Dialer Watch: watch-group = 1,
22:18:13: DDR: dialing secondary by dialer map 2.2.2.2 on Se5/0:23
22:18:13: Se5/0:23 DDR: Attempting to dial 222222
22:18:13: %LINK-3-UPDOWN: Interface Serial5/0:0, changed state to up
22:18:13: Se5/0:0 DDR: Dialer Watch: resetting call in progress
22:18:13: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 N/A
22:18:14: Se5/0:0 DDR: Remote name for Vofr_Callgen
22:18:14: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up
22:18:14: Vi2 DDR: Dialer statechange to up
22:18:14: Vi2 DDR: Dialer Watch: resetting call in progress
22:18:14: Vi2 DDR: Dialer call has been placed
22:18:14: Vi2 DDR: dialer protocol up
22:18:14: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to down
22:18:15: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to up
22:18:19: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 R2
22:18:19: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 R2
22:18:44: Vi2 DDR: idle timeout
22:18:44: DDR: Dialer Watch: watch-group = 1
22:18:44: DDR: network 2.2.2.2/255.255.255.255 UP,
22:18:44: DDR: primary DOWN
22:18:44: Vi2 DDR: disconnecting call
22:18:44: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down
22:18:44: %ISDN-6-DISCONNECT: Interface Serial5/0:0 disconnected from 222222 R2, call lasted 30 seconds
22:18:44: %LINK-3-UPDOWN: Interface Serial5/0:0, changed state to down
22:18:44: DDR: Dialer Watch: watch-group = 1
22:18:44: DDR: network 2.2.2.2/255.255.255.255 UP,
22:18:44: DDR: primary DOWN
22:18:44: DDR: Dialer Watch: Dial Reason: Secondary of group 1 AVAILABLE
22:18:44: DDR: Dialer Watch: watch-group = 1,
22:18:44: DDR: dialing secondary by dialer map 2.2.2.2 on Se5/0:23
22:18:44: Se5/0:23 DDR: Attempting to dial 222222
22:18:44: %LINK-3-UPDOWN: Interface Serial5/0:0, changed state to up
22:18:44: Se5/0:0 DDR: Dialer Watch: resetting call in progress
22:18:44: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 N/A
22:18:44: Se5/0:0 DDR: Remote name for R2
22:18:44: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to up
22:18:44: Vi1 DDR: Dialer statechange to up
22:18:44: Vi1 DDR: Dialer Watch: resetting call in progress
22:18:44: Vi1 DDR: Dialer call has been placed
22:18:44: Vi1 DDR: dialer protocol up
22:18:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access2, changed state to down
22:18:45: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up
22:18:50: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 R2
22:18:50: %ISDN-6-CONNECT: Interface Serial5/0:0 is now connected to 222222 R2
================
Can someone explain to be whats happening here? I tht that dialer-watch periodically checked the watched route after every
idle-timeout and if primary is still down then rest the idle-timeout.
So why is it tearing down the link?
Thanks!
Rohan
This archive was generated by hypermail 2.1.4 : Sat Nov 06 2004 - 17:11:54 GMT-3