From: Lab Candidate (labccie@xxxxxxxxx)
Date: Tue Jun 18 2002 - 02:26:06 GMT-3
Lance,
You left out ospf config, which might be critical too to troubleshoo your flapp
ing problem.
The ospf demand-circuit will not settle down until you have your ospf neighbor
formed first.
Use show ip ospf database cmd to check to see routes from remote router in DNA
states.
Here are the configs on both routers:
R3 config
interface BRI0/0
ip address 100.1.15.3 255.255.255.0
no ip directed-broadcast
encapsulation ppp
ip ospf message-digest-key 1 md5 cisco
ip ospf network point-to-point
ip ospf demand-circuit
dialer map ip 100.1.15.5 name R5 broadcast
isdn switch-type basic-ni
isdn spid1 770794xxxx0101 794xxxx
isdn spid2 770794xxxx0101 794xxxx
no peer neighbor-route
ppp authentication chap
!
R5 Config
interface BRI0/0
ip address 100.1.15.5 255.255.255.0
encapsulation ppp
ip ospf message-digest-key 1 md5 cisco
ip ospf demand-circuit
dialer map ip 100.1.15.3 name r3 broadcast 770794xxxx
dialer load-threshold 128 either
dialer-group 1
isdn spid1 770422xxxx0101 422xxxx
isdn spid2 770422xxxx0101 422xxxx
no peer neighbor-route
ppp authentication chap callin
ppp multilink
!
----- Original Message -----
From: <kris.keen@aon.com.au>
To: "Lance" <Lance@advnetech.com>
Cc: <ccielab@groupstudy.com>; <nobody@groupstudy.com>
Sent: Monday, June 17, 2002 11:50 PM
Subject: Re: OSPF Demand Circuit issues
>
> debug ppp authentication and show us your config
>
> -----------------------------------------------------------------
> Kris Keen - CCNP, CCDP, CNE
> Network Support Specialist - Network Systems
> Aon Risk Services Australia Limited
> (612) 9253 7272
> 0404862970
> E: Kris.Keen@aon.com.au
>
>
>
>
>
> "Lance"
> <Lance@advnete To: <ccielab@groupstudy.com>
> ch.com> cc:
> Sent by: bcc:
> nobody@groupst Subject: OSPF Demand Circuit
issues
> udy.com
>
>
> 18/06/2002
> 01:14 PM
> Please respond
> to "Lance"
>
>
>
>
>
>
> My demand circuit is bouncing up and down.
> R5 is connecting to R3 via ISDN. Both routers have the command no
> peer-neighbor routes entered as well as both having the ip ospf
> damand-circut
> command. I dont understand why it is not working. Anyone have any ideas?
> Also what command do I use to show if all my routers understand the DNA
> bit?
> Also R5 never shows R3 as a neighbor when the ISDN line is up. R3 shows
R5
> as
> a neighbor in the INIT state, never full ?
>
> Any guru's out there want to tackle this one? BTW the search
functionality
> on
> the site is down.
>
>
>
>
> R5#show dialer
>
> BRI0/0 - dialer type = ISDN
>
> Dial String Successes Failures Last called Last status
> 770794XXXX 5 4 00:00:05 successful
> 0 incoming call(s) have been screened.
> 0 incoming call(s) rejected for callback.
>
> BRI0/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 data link layer up
> Dial reason: ip (s=133.6.65.5, d=224.0.0.5)
> Time until disconnect 115 secs
> Connected to 770794xxxx (r3)
>
> R5 is connecting to R3 via ISDN. Both routers have the command no
> peer-neighbor routes entered as well as both having the ip ospf
> damand-circut
> command. I dont understand why it is not working. Anyone have any ideas?
> Also what command do I use to show if all my routers understand the DNA
> bit?
>
>
>
> R5#
> 00:08:00: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from
> 770794xxxx
> r3, call lasted 120 seconds
> 00:08:00: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down
> R5#
> 00:08:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1,
changed
> state to down
> R5#
> 00:08:10: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up
> R5#
> 00:08:10: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1,
changed
> state to up
> R5#
> 00:08:16: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to
> 770794xxxx
> r3
> R5#
This archive was generated by hypermail 2.1.4 : Tue Jul 02 2002 - 08:12:36 GMT-3