Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

ovt Bronze
Bronze

OSPF demand-circuit over Dialer profiles

Hi!

It is well known that IPSec over Legacy DDR may not work due to the Bug CSCin50999 ("Kicking the dialer interface" problem).

This means that Dialer profile is required on the calling side. Suppose we have dial backup scenario. It seems that the easyest way to configure it is OSPF demand-circuit. OSPF should bring the ISDN line up in case of any change in the OSPF cloud (OSPF is defined as "interesting"). The problem is that demand-circuit doesn't work:

R4#sh ip ospf int dialer 1

Dialer1 is up, line protocol is up (spoofing)

Internet Address 110.50.46.4/24, Area 0

Process ID 1, Router ID 144.144.144.144, Network Type POINT_TO_POINT, Cost: 1562

Configured as demand circuit.

Run as demand circuit.

DoNotAge LSA allowed.

Transmit Delay is 1 sec, State POINT_TO_POINT,

Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5

oob-resync timeout 40

Hello due in 00:00:06

Index 1/1, flood queue length 0

Next 0x0(0)/0x0(0)

Last flood scan length is 1, maximum is 1

Last flood scan time is 0 msec, maximum is 4 msec

Neighbor Count is 1, Adjacent neighbor count is 1

Adjacent with neighbor 16.16.16.16 (Hello suppressed)

Suppress hello for 1 neighbor(s)

Message digest authentication enabled

Youngest key id is 1

Demand circuit configured, but OSPF sends HELLO packets from time to time. I've never see this for Legacy DDR. The debug is from the router that has OSPF configured on the dialer interface *only*.

*Mar 2 23:51:18.780 MSK: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to 0003 LAB2

*Mar 2 23:51:20.042 MSK: IP: s=110.50.46.6 (Dialer1), d=224.0.0.5, len 80, rcvd 0

*Mar 2 23:51:23.107 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (Dialer1), len 112, sending broad/multicast

*Mar 2 23:51:25.639 MSK: IP: s=110.50.46.6 (Dialer1), d=224.0.0.5, len 80, rcvd 0

*Mar 2 23:51:43.657 MSK: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to up

*Mar 2 23:51:43.657 MSK: %DIALER-6-BIND: Interface BR0/0:2 bound to profile Di1

*Mar 2 23:51:44.226 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (Dialer1), len 112, sending broad/multicast

*Mar 2 23:51:44.723 MSK: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:2, changed state to up

*Mar 2 23:51:46.754 MSK: IP: s=110.50.46.6 (Dialer1), d=224.0.0.5, len 80, rcvd 0

*Mar 2 23:51:49.663 MSK: %ISDN-6-CONNECT: Interface BRI0/0:2 is now connected to 0003 LAB2

*Mar 2 23:53:12.923 MSK: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from 0003 LAB2, call lasted 120 seconds

*Mar 2 23:53:12.923 MSK: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

*Mar 2 23:53:12.923 MSK: %DIALER-6-UNBIND: Interface BR0/0:1 unbound from profile Di1

*Mar 2 23:53:12.947 MSK: %ISDN-6-DISCONNECT: Interface BRI0/0:2 disconnected from 0003 LAB2, call lasted 89 seconds

*Mar 2 23:53:12.947 MSK: %LINK-3-UPDOWN: Interface BRI0/0:2, changed state to down

*Mar 2 23:53:12.951 MSK: %DIALER-6-UNBIND: Interface BR0/0:2 unbound from profile Di1

*Mar 2 23:53:13.352 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (Dialer1), len 112, sending broad/multicast

*Mar 2 23:53:13.352 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (BRI0/0), len 112, encapsulation failed

*Mar 2 23:53:13.496 MSK: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up

*Mar 2 23:53:13.496 MSK: %DIALER-6-BIND: Interface BR0/0:1 bound to profile Di1

*Mar 2 23:53:13.857 MSK: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:2, changed state to down

*Mar 2 23:53:18.316 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (Dialer1), len 112, sending broad/multicast

*Mar 2 23:53:19.069 MSK: IP: s=110.50.46.4 (local), d=224.0.0.5 (Dialer1), len 112, sending broad/multicast

The question is: what is the difference between Legacy DDR and Dialer profiles from OSPF point of view?

2 REPLIES
Silver

Re: OSPF demand-circuit over Dialer profiles

Legacy DDR uses dialer maps and dialer profile uses interface dailer to do the same DDR activity.

When using dialer maps you can use snapshot routing to suppress the hello updates, still OSPF working.

For more information

http://www.cisco.com/en/US/tech/tk801/tk133/technologies_configuration_example09186a008009454e.shtml

Configuring DDR with dialer profile is explianed here

http://www.cisco.com/warp/public/793/access_dial/ddr_dialer_profile.html

VIP Purple

Re: OSPF demand-circuit over Dialer profiles

Hello,

can you enable debugging with the command:

debug ip ospf monitor

to check if and which LSA might be changing and bringing up the link ?

Not sure if you have checked this document, it gives various reasons for why the OSPF demand circuit can bring up the link:

Why OSPF Demand Circuit Keeps Bringing Up the Link

http://www.cisco.com/en/US/partner/tech/tk365/tk480/technologies_tech_note09186a008009481b.shtml

Regards,

GP

299
Views
0
Helpful
2
Replies