From: Raphael Gallegos (raphaeljg@xxxxxxxxxxx)
Date: Mon Feb 04 2002 - 06:31:32 GMT-3
Maybe you can try to configure one side to do the dialing only (Why have
both capable of dialing each other, an lsa change will trigger a dial
regardless), you don't need two "ip ospf demand-circuit" commands on both
sides.
This is just a suggestion. Please send updated configs, your previous
configs show everything is in area0 and now you are mentioning area1.
Raphael
>From: Manny Gonzalez <manny@nyp.org>
>Reply-To: Manny Gonzalez <manny@nyp.org>
>To: ccielab@groupstudy.com
>Subject: Re: OSPF keeps ISDN up
>Date: Mon, 04 Feb 2002 00:51:35 -0500
>
>Unfortunately, this problem continues. I have the following config just
>to clarify the fact that I DO NOT HAVE REDISTRIBUTION anywhere.. small
>test setup
>
>loopback1\
>/loopback1
> \ /
> r3--bri0/0--dial0---------isdn cloud-------dial0--bri--r5
>
>Loopback 1 in R3 is the Area 0 interface
>
>All other interfaces are area 1
>
>I have tried all ... no peer-neighbor, ip ospf point to point, ospf area
>1 stub, stub no summary, nssa, nssa no summary... nothing makes the damn
>thing shut up...
>
>I do thank you for your help though. Any further thoughts?
>
>Manny
>
>
>
>"McCallum, Robert" wrote:
> >
> > Alavalapati has already told you how to fix it.
> >
> > It's one of the gotchas. Put no peer neighbor-route on each side of the
>ISDN line and you will solve your problem. What happens is simple.
> >
> > PPP connection when it comes up it does what ?? It installs a /32 route
>in your OSPF area 0 (ouch).
> >
> > Rules of demand circuit in OSPF - refresh after 30 minutes or when there
>is a flood of TYPE 5 LSA's.
> >
> > What happens when the ISDN has exchanged its routes etc - demand circuit
>will bring the ISDN line down.
> >
> > What happens to the 2 * /32 routes that ARE in the OSPF database.......
>They become extinct ----
> > OH DEAR TOPOLOGY CHANGE BRING THE LINE BACK UP PLEASE!!!! And so the
>story goes on and on and on and on.
> >
> > If you do this and you still have problems check the rest of your
>network (namely and points of redistribution).
> >
> > -----Original Message-----
> > From: Duy Nguyen [mailto:net_port@hotmail.com]
> > Sent: 30 January 2002 08:10
> > To: manny@nyp.org; groupstudy@x263.net
> > Cc: ccielab@groupstudy.com
> > Subject: Re: OSPF keeps ISDN up
> >
> > Could you do totally stubby, then have a virtual-link to area 0?
> >
> > >From: Manny Gonzalez <manny@nyp.org>
> > >Reply-To: Manny Gonzalez <manny@nyp.org>
> > >To: Alan <groupstudy@x263.net>
> > >CC: ccielab@groupstudy.com
> > >Subject: Re: OSPF keeps ISDN up
> > >Date: Wed, 30 Jan 2002 02:17:08 -0500
> > >
> > >Well, I nailed it.. now how do I solve it... There is an LSA refresh
> > >going on... Why I don't know. It happens on boths sides of the link. On
> > >R3, it thinks it needs to refresh the lSA for net 12.12.12.12 which is
>a
> > >loopback on R5... The opposite happens on R5. Now, Cisco recommends
> > >using the TOTALLY STUBBY AREA as a solution, but, this is area 0 we are
> > >talking about.. All routers are in area 0. So... what to do. This is
>one
> > >interesting scenario. I am gonna play with Totally Stubby for a bit...
> > >be right back... Thanks to all for all the heads helpful info. Can we
> > >all take the test together? :-))
> > >
> > >Here is the output of the MONITOR in OSPF debug
> > >
> > >R5
> > >*Mar 1 05:44:18.086: OSPF: Schedule SPF in area 0
> > > Change in LS ID 11.11.11.11, LSA type R,
> > >r5#
> > >*Mar 1 05:44:22.518: OSPF: Begin SPF at 20662.520ms, process time
>304ms
> > >*Mar 1 05:44:22.518: spf_time 05:44:12.520, wait_interval 10s
> > >*Mar 1 05:44:22.518: OSPF: End SPF at 20662.520ms, Total elapsed time
> > >0ms
> > >*Mar 1 05:44:22.518: Intra: 0ms, Inter: 0ms, External: 0ms
> > >*Mar 1 05:44:22.518: R: 2, N: 0, Stubs: 4
> > >*Mar 1 05:44:22.518: SN: 0, SA: 0, X5: 0, X7: 0
> > >*Mar 1 05:44:22.518: SPF suspends: 0 intra, 0 total
> > >
> > >R3
> > >r3#
> > >*Mar 1 05:46:19.378: OSPF: Schedule SPF in area 0
> > > Change in LS ID 12.12.12.12, LSA type R,
> > >*Mar 1 05:46:19.574: OSPF: Begin SPF at 20779.576ms, process time
>324ms
> > >*Mar 1 05:46:19.574: spf_time 05:46:14.576, wait_interval 5s
> > >*Mar 1 05:46:19.574: OSPF: End SPF at 20779.576ms, Total elapsed time
> > >0ms
> > >*Mar 1 05:46:19.574: Intra: 0ms, Inter: 0ms, External: 0ms
> > >*Mar 1 05:46:19.574: R: 2, N: 0, Stubs: 4
> > >*Mar 1 05:46:19.574: SN: 0, SA: 0, X5: 0, X7: 0
> > >*Mar 1 05:46:19.574: SPF suspends: 0 intra, 0 total
> > >*Mar 1 05:46:19.966: OSPF: Schedule SPF in area 0
> > >
> > >
> > >Alan wrote:
> > > >
> > > > once topology changes, demand circirt will come up.
> > > > add 'ip ospf network point-to-point' to ensure the proper network
>type,
> > >otherwise ospf may continue send hello.
> > > >
> > > > read this. it helped me a lot.
> > > > http://www.cisco.com/warp/customer/104/dcprob.html
> > > >
> > > > ----- Original Message -----
> > > > From: "Manny Gonzalez" <manny@nyp.org>
> > > > To: "Michael Popovich" <m.popovich@home.com>
> > > > Cc: "Manny Gonzalez" <gonzalu@nyp.org>; <ccielab@groupstudy.com>
> > > > Sent: Wednesday, January 30, 2002 12:57 PM
> > > > Subject: Re: OSPF keeps ISDN up
> > > >
> > > > > Hmm, I thought the fact that it is set as a demand circuit will
> > >suppress
> > > > > the hellos. As a matter of fact,
> > > > >
> > > > > SH IP OSPF IN
> > > > >
> > > > > tells me it is suppressing those hellos. I know I have put this in
> > > > > before and after a few minutes, it settles down and does not dial
>at
> > > > > all... with a nice open dialer-list. I mean, I know I could block
> > >those
> > > > > hellos, but, that would then make the adjancency go away since the
> > > > > router will not ever open it even if there is a topology change in
> > >which
> > > > > case you want it to open the link to tell the other side something
> > > > > changed.
> > > > >
> > > > > What do you think?
> > > > >
> > > > > Michael Popovich wrote:
> > > > > >
> > > > > > I think it is in your dialer list.
> > > > > >
> > > > > > Looks like you have it configured for "ip permit"
> > > > > >
> > > > > > you should use an access-list as follows:
> > > > > >
> > > > > > access-list 100 deny ospf any any
> > > > > > access-list 100 permit ip any any
> > > > > >
> > > > > > dialer-list 1 protocol list 100
> > > > > >
> > > > > > That should tag OSPF as uninteresting traffic and everything
>else as
> > > > > > interesting so OSPF won't cause the ISDN so dial the remote
>router.
> > > > > >
> > > > > > MP
> > > > > > ----- Original Message -----
> > > > > > From: "Manny Gonzalez" <gonzalu@nyp.org>
> > > > > > To: <ccielab@groupstudy.com>
> > > > > > Sent: Tuesday, January 29, 2002 7:53 PM
> > > > > > Subject: OSPF keeps ISDN up
> > > > > >
> > > > > > > Hmm, maybe I was too confident and I just simply forgot a
>thing or
> > >two
> > > > > > > about OSPF over ISDN ;-)
> > > > > > >
> > > > > > > With the following setup, the ISDN link is still brought up
> > >regularly by
> > > > > > > OSPF hellos. I have done this setup before and it worked. The
>only
> > > > > > > difference was that the AREA 0 had another link between
>routers
> > >via
> > > > > > > Ethernet links.
> > > > > > >
> > > > > > > Any suggestions on what I am doing wrong?
> > > > > > >
> > > > > > > TIA
> > > > > > > ---------
> > > > > > > r5#sh run
> > > > > > > !
> > > > > > > version 12.1
> > > > > > > service nagle
> > > > > > > service timestamps debug datetime msec localtime
> > > > > > > service timestamps log datetime msec localtime
> > > > > > > no service password-encryption
> > > > > > > !
> > > > > > > hostname r5
> > > > > > > !
> > > > > > > logging buffered 32000 debugging
> > > > > > > no logging console
> > > > > > > !
> > > > > > > username r3 password 0 cisco
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > ip subnet-zero
> > > > > > > ip tcp synwait-time 5
> > > > > > > no ip domain-lookup
> > > > > > > !
> > > > > > > isdn switch-type basic-ni
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > voice-port 1/0/0
> > > > > > > !
> > > > > > > voice-port 1/0/1
> > > > > > > !
> > > > > > > voice-port 1/1/0
> > > > > > > !
> > > > > > > voice-port 1/1/1
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 12.12.12.12 255.255.255.0
> > > > > > > ip ospf network point-to-point
> > > > > > > !
> > > > > > > interface BRI0/0
> > > > > > > no ip address
> > > > > > > encapsulation ppp
> > > > > > > dialer pool-member 1
> > > > > > > isdn switch-type basic-ni
> > > > > > > isdn spid1 212543011301 5430113
> > > > > > > isdn spid2 212543011401 5430114
> > > > > > > ppp authentication chap
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > interface Dialer0
> > > > > > > ip address 10.10.10.1 255.255.255.0
> > > > > > > encapsulation ppp
> > > > > > > ip ospf demand-circuit
> > > > > > > dialer pool 1
> > > > > > > dialer remote-name r3
> > > > > > > dialer fast-idle 30
> > > > > > > dialer string 40110
> > > > > > > dialer load-threshold 1 either
> > > > > > > dialer-group 1
> > > > > > > no peer neighbor-route
> > > > > > > ppp authentication chap
> > > > > > > ppp chap hostname r5
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > router ospf 1
> > > > > > > log-adjacency-changes
> > > > > > > network 10.0.0.0 0.255.255.255 area 0
> > > > > > > network 12.12.12.12 0.0.0.0 area 0
> > > > > > > !
> > > > > > > ip classless
> > > > > > > ip http server
> > > > > > > !
> > > > > > > dialer-list 1 protocol ip permit
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sib sh ip bgp
> > > > > > > alias exec sir sh ip route
> > > > > > > alias exec siib sh ip int brief
> > > > > > > alias exec sip sh ip protocols
> > > > > > > !
> > > > > > > line con 0
> > > > > > > exec-timeout 0 0
> > > > > > > logging synchronous
> > > > > > > history size 50
> > > > > > > line aux 0
> > > > > > > password cisco
> > > > > > > login
> > > > > > > line vty 0 4
> > > > > > > exec-timeout 0 0
> > > > > > > password cisco
> > > > > > > logging synchronous
> > > > > > > login
> > > > > > > history size 50
> > > > > > > !
> > > > > > > ======================================
> > > > > > >
> > > > > > > r3#sh run
> > > > > > > !
> > > > > > > version 12.1
> > > > > > > service nagle
> > > > > > > service timestamps debug datetime msec localtime
> > > > > > > service timestamps log datetime msec localtime
> > > > > > > no service password-encryption
> > > > > > > !
> > > > > > > hostname r3
> > > > > > > !
> > > > > > > logging buffered 32000 debugging
> > > > > > > no logging console
> > > > > > > !
> > > > > > > username r5 password 0 cisco
> > > > > > > !
> > > > > > > !
> > > > > > > memory-size iomem 10
> > > > > > > ip subnet-zero
> > > > > > > ip tcp synwait-time 5
> > > > > > > no ip domain-lookup
> > > > > > > !
> > > > > > > ip audit notify log
> > > > > > > ip audit po max-events 100
> > > > > > > isdn switch-type basic-ni
> > > > > > > !
> > > > > > > !
> > > > > > > interface Loopback0
> > > > > > > ip address 11.11.11.11 255.255.255.0
> > > > > > > ip ospf network point-to-point
> > > > > > > !
> > > > > > > interface BRI0/0
> > > > > > > no ip address
> > > > > > > encapsulation ppp
> > > > > > > dialer pool-member 1
> > > > > > > isdn switch-type basic-ni
> > > > > > > isdn spid1 212543010901 5430109
> > > > > > > isdn spid2 212543011001 5430110
> > > > > > > ppp authentication chap
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > interface Dialer0
> > > > > > > ip address 10.10.10.3 255.255.255.0
> > > > > > > encapsulation ppp
> > > > > > > ip ospf demand-circuit
> > > > > > > dialer pool 1
> > > > > > > dialer remote-name r5
> > > > > > > dialer fast-idle 30
> > > > > > > dialer string 40114
> > > > > > > dialer load-threshold 1 either
> > > > > > > dialer-group 1
> > > > > > > no peer neighbor-route
> > > > > > > ppp authentication chap
> > > > > > > ppp chap hostname r3
> > > > > > > ppp multilink
> > > > > > > !
> > > > > > > router ospf 1
> > > > > > > log-adjacency-changes
> > > > > > > network 10.0.0.0 0.255.255.255 area 0
> > > > > > > network 11.11.11.11 0.0.0.0 area 0
> > > > > > > !
> > > > > > > ip classless
> > > > > > > ip http server
> > > > > > > !
> > > > > > > dialer-list 1 protocol ip permit
> > > > > > > !
> > > > > > > !
> > > > > > > alias exec sir sh ip route
> > > > > > > alias exec sio sh ip ospf
> > > > > > > alias exec sip sh ip protocols
> > > > > > > alias exec siib sh ip int brief
> > > > > > > alias exec sib sh ip bgp
> > > > > > > alias exec cir clea ip route *
> > > > > > > !
> > > > > > > line con 0
> > > > > > > exec-timeout 0 0
> > > > > > > logging synchronous
> > > > > > > history size 50
> > > > > > > line aux 0
> > > > > > > password cisco
> > > > > > > login
> > > > > > > line vty 0 4
> > > > > > > exec-timeout 0 0
> > > > > > > password cisco
> > > > > > > logging synchronous
> > > > > > > login
> > > > > > > history size 50
> > > > > > >
This archive was generated by hypermail 2.1.4 : Thu Jun 20 2002 - 13:46:11 GMT-3