From: Stephen Oliver (stevie_oliver@xxxxxxxxxxx)
Date: Fri Jan 11 2002 - 12:21:56 GMT-3
Further to this OSPF demand circuit issue.
I've found I can configure my demand circuit without the
no peer neighbor-route command and it doesn't bounce. The /32 does get
installed when the circuit is up, disappears when it goes down but the
circuit does not bounce.
Stevie.
>From: Bryan Ginman <ginmanb@westnet.com>
>Reply-To: Bryan Ginman <ginmanb@westnet.com>
>To: EA Louie <elouie@yahoo.com>
>CC: CCIE <ccielab@groupstudy.com>
>Subject: RE: OSPF Demand Circuit
>Date: Fri, 11 Jan 2002 09:53:33 -0500
>
>Debug ip routing will show which route is being entered into table that is
>generating an LSA. This should be why your link is coming up. Once you
>figure that out you can nail down your access lists and or put in no peer
>neighbor to not add the other end of your bri.
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>EA Louie
>Sent: Friday, January 11, 2002 6:40 AM
>To: ccielab@groupstudy.com
>Subject: Re: OSPF Demand Circuit
>
>
>I guess my question really is... why is it sending hello packets when
>they're supposed to be supressed?
>
> > the bible - page 416
> >
> > " The destination address of OSPF packets on these networks will always
>be
> > the reserved class D address 224.0.0.5, known as AllSPFRouters "
> >
> > The only exception to this is retransmitted LSA's.
> >
> > jaz
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > EA Louie
> > Sent: 11 January 2002 10:58
> > To: ccielab@groupstudy.com
> > Subject: Re: OSPF Demand Circuit
> >
> >
> > it's trying to send a multicast (ospf hello?) packet to the other end of
>the
> > ISDN link - the question is, why a multicast when this is a
>point-to-point
> > ckt?
> >
> > 13:25:46: OSPF: rcv. v:2 t:4 l:100 rid:133.1.3.3
> > aid:0.0.0.0 chk:0 aut:2 keyid:1 seq:0x2B9160F3 from Serial0.235
> > 13:25:46: BR0 DDR: rotor dialout [priority]
> > 13:25:46: BR0 DDR: Dialing cause ip (s=133.1.35.5, d=224.0.0.5)
> > 13:25:46: BR0 DDR: Attempting to dial 5552000
> > 13:25:47: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1,
>changed
> > state
> > to down
> > 13:25:47: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
> > 13:25:47: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
> > R5#
> >
> >
> > R5#sh ip ro
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> > 133.1.0.0/16 is variably subnetted, 17 subnets, 3 masks
> > C 133.1.235.0/24 is directly connected, Serial0.235
> > I 133.1.4.0/24 [100/8976] via 133.1.45.4, 00:00:02, Serial0.1
> > C 133.1.5.0/24 is directly connected, Loopback0
> > O 133.1.6.0/24 [110/65] via 133.1.56.6, 08:42:19, Serial1
> > O E2 133.1.1.0/24 [110/20] via 133.1.235.2, 00:27:14, Serial0.235
> > O 133.1.2.0/24 [110/65] via 133.1.235.2, 00:27:14, Serial0.235
> > O 133.1.3.0/24 [110/65] via 133.1.235.3, 00:27:14, Serial0.235
> > O E2 133.1.12.0/24 [110/20] via 133.1.235.2, 00:27:15, Serial0.235
> > O E2 133.1.22.0/27 [110/20] via 133.1.235.2, 00:27:15, Serial0.235
> > O IA 133.1.23.0/26 [110/70] via 133.1.235.3, 00:27:16, Serial0.235
> > O IA 133.1.23.0/24 [110/70] via 133.1.235.2, 00:27:16, Serial0.235
> > C 133.1.35.0/24 is directly connected, Dialer0
> > I 133.1.44.0/24 [100/8539] via 133.1.45.4, 00:00:03, Serial0.1
> > C 133.1.45.0/24 is directly connected, Serial0.1
> > C 133.1.55.0/24 is directly connected, TokenRing0
> > C 133.1.56.0/24 is directly connected, Serial1
> > O IA 133.1.66.0/24 [110/74] via 133.1.56.6, 00:27:16, Serial1
> > 151.100.0.0/18 is subnetted, 1 subnets
> > O E2 151.100.0.0 [110/100] via 133.1.235.2, 00:27:16, Serial0.235
> > 150.100.0.0/16 is variably subnetted, 2 subnets, 2 masks
> > I 150.100.0.0/16 [100/8576] via 133.1.45.4, 00:00:03, Serial0.1
> > O E2 150.100.1.0/24 [110/20] via 133.1.235.2, 00:27:16, Serial0.235
> > R5#
> >
> > R3#sh ip ro
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> > 133.1.0.0/16 is variably subnetted, 13 subnets, 3 masks
> > C 133.1.235.0/24 is directly connected, Serial0
> > O 133.1.5.0/24 [110/65] via 133.1.235.5, 00:00:07, Serial0
> > O IA 133.1.6.0/24 [110/129] via 133.1.235.5, 00:00:07, Serial0
> > O E2 133.1.1.0/24 [110/20] via 133.1.23.2, 00:00:07, TokenRing0
> > O 133.1.2.0/24 [110/65] via 133.1.235.2, 00:00:07, Serial0
> > C 133.1.3.0/24 is directly connected, Loopback0
> > O E2 133.1.12.0/24 [110/20] via 133.1.23.2, 00:00:07, TokenRing0
> > O E2 133.1.22.0/27 [110/20] via 133.1.23.2, 00:00:08, TokenRing0
> > O IA 133.1.23.0/24 [110/70] via 133.1.235.2, 00:00:08, Serial0
> > C 133.1.23.0/26 is directly connected, TokenRing0
> > C 133.1.35.0/24 is directly connected, Dialer0
> > O IA 133.1.56.0/24 [110/128] via 133.1.235.5, 00:00:08, Serial0
> > O IA 133.1.66.0/24 [110/138] via 133.1.235.5, 00:00:08, Serial0
> > 151.100.0.0/18 is subnetted, 1 subnets
> > O E2 151.100.0.0 [110/100] via 133.1.23.2, 00:00:08, TokenRing0
> > 150.100.0.0/24 is subnetted, 1 subnets
> > O E2 150.100.1.0 [110/20] via 133.1.23.2, 00:00:08, TokenRing0
> > R3#
> >
> > R2#sh ip ro
> > Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
> > E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
> > i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS
>inter
> > area
> > * - candidate default, U - per-user static route, o - ODR
> > P - periodic downloaded static route
> >
> > Gateway of last resort is not set
> >
> > 133.1.0.0/16 is variably subnetted, 13 subnets, 3 masks
> > C 133.1.235.0/24 is directly connected, Serial0
> > O 133.1.5.0/24 [110/65] via 133.1.235.5, 00:00:30, Serial0
> > O IA 133.1.6.0/24 [110/129] via 133.1.235.5, 00:00:30, Serial0
> > D 133.1.1.0/24 [90/2297856] via 133.1.12.1, 12:43:07, Serial1
> > C 133.1.2.0/24 is directly connected, Loopback0
> > O 133.1.3.0/24 [110/65] via 133.1.235.3, 00:00:30, Serial0
> > C 133.1.12.0/24 is directly connected, Serial1
> > C 133.1.22.0/27 is directly connected, TokenRing0
> > O 133.1.23.0/24 is a summary, 12:44:47, Null0
> > C 133.1.23.0/26 is directly connected, TokenRing1
> > O 133.1.35.0/24 [110/1626] via 133.1.235.3, 00:00:31, Serial0
> > O IA 133.1.56.0/24 [110/128] via 133.1.235.5, 00:00:31, Serial0
> > O IA 133.1.66.0/24 [110/138] via 133.1.235.5, 00:00:33, Serial0
> > 151.100.0.0/18 is subnetted, 1 subnets
> > D 151.100.0.0 [90/2297856] via 133.1.12.1, 12:43:10, Serial1
> > 150.100.0.0/24 is subnetted, 1 subnets
> > D EX 150.100.1.0 [170/39896832] via 133.1.12.1, 12:43:10, Serial1
> > R2#
> > ----- Original Message -----
> > From: "Rajeev Siddappa" <raj_lab@yahoo.com>
> > To: "EA Louie" <elouie@yahoo.com>
> > Sent: Friday, January 11, 2002 1:48 AM
> > Subject: Re: OSPF Demand Circuit
> >
> >
> > >
> > > IS it possible to post the o/p of routing table
> > > ofallthe routers and can u also start OSPF debugging
> > > and send the out put when the the circuit come up.
> > >
> > > Try this also. Is it possibel to chage u r acces-list
> > > 142 to /32. Not /24 on all routers.
> > >
> > > Rajeev.
> > >
> > >
> > >
> > > --- EA Louie <elouie@yahoo.com> wrote:
> > > > it's already there, Raj
> > > >
> > > > -e-
> > > >
> > > > ----- Original Message -----
> > > > From: "Rajeev Siddappa" <raj_lab@yahoo.com>
> > > > To: "EA Louie" <elouie@yahoo.com>;
> > > > <ccielab@groupstudy.com>
> > > > Sent: Friday, January 11, 2002 12:56 AM
> > > > Subject: Re: OSPF Demand Circuit
> > > >
> > > >
> > > > >
> > > > > Use the command,
> > > > >
> > > > > No peer neighbor-route
> > > > >
> > > > > on the R5's bri interface.
> > > > >
> > > > > Then it should be ok.
> > > > >
> > > > > Rajeev.
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > --- EA Louie <elouie@yahoo.com> wrote:
> > > > > > Okay... I think I've done everything right, I've
> > > > > > gone through the archives,
> > > > > > and I might just be dealing with a 'feature' of
> > > > > > 12.1, but I can't get ospf
> > > > > > demand circuit to stay quiet. here's the
> > > > topology
> > > > > > in a nutshell:
> > > > > >
> > > > > > R2 ----- R5 ---- R4
> > > > > > /
> > > > > > R3 -/
> > > > > >
> > > > > > With R3 and R2 on the same subinterface as R5 in
> > > > > > Area 0, and R5-R4 running
> > > > > > IGRP
> > > > > > Mutually redistributing OSPF and EIGRP on R2,
> > > > and
> > > > > > OSPF and IGRP on R5. R4
> > > > > > runs IGRP by itself.
> > > > > >
> > > > > > R5 and R3 are both ISDN routers and I'm trying
> > > > to
> > > > > > get demand circuit working
> > > > > > correctly. I have it dialing just fine, but the
> > > > > > doggone connection won't stay
> > > > > > down unless I A) remove redistribution on R5,
> > > > or B)
> > > > > > shut down the dialer
> > > > > > interface.
> > > > > >
> > > > > > Here are the configs of the 3 key routers -
> > > > anyone
> > > > > > have a suggestion as to why
> > > > > > I can't get this thing quiet? I'm willing to
> > > > put an
> > > > > > access-list on R5 to deny
> > > > > > ospf any any, but that just seems to defeat the
> > > > > > purpose, don't you think?
> > > > > > Especially when show ip ospf int dial0 shows
> > > > Hello
> > > > > > suppressed:
> > > > > >
> > > > > > R5#sh ip ospf int dial0
> > > > > > Dialer0 is up, line protocol is up (spoofing)
> > > > > > Internet Address 133.1.35.5/24, Area 0
> > > > > > Process ID 1, Router ID 133.1.5.5, Network Type
> > > > > > POINT_TO_POINT, Cost: 20000
> > > > > > 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
> > > > > > Hello due in 00:00:06
> > > > > > Index 3/3, flood queue length 0
> > > > > > Next 0x0(0)/0x0(0)
> > > > > > Last flood scan length is 1, maximum is 4
> > > > > > Last flood scan time is 0 msec, maximum is 16
> > > > msec
> > > > > > Neighbor Count is 1, Adjacent neighbor count is
> > > > 1
> > > > > > Adjacent with neighbor 133.1.3.3 (Hello
> > > > suppressed)
> > > > > > Suppress hello for 1 neighbor(s)
> > > > > > Message digest authentication enabled
> > > > > > Youngest key id is 1
> > > > > > R5#
> > > > > >
> > > > > >
> > > > > >
> > > > > > thanks
> > > > > > -e-
> > > > > >
> > > > > > R5
> > > > > >
> > > > > > R5#
> > > > > > 10:33:37: %ISDN-6-CONNECT: Interface BRI0:1 is
> > > > now
> > > > > > connected to 5552000
> > > > > > user33
> > > > > > R5#wr t
> > > > > > Building configuration...
> > > > > > Current configuration : 4151 bytes
> > > > > > !
> > > > > > version 12.1
> > > > > > service timestamps debug uptime
> > > > > > service timestamps log uptime
> > > > > > no service password-encryption
> > > > > > !
> > > > > > hostname R5
> > > > > > !
> > > > > > enable password cisco
> > > > > > !
> > > > > > username R3 password 0 cisco
> > > > > > username user33 password 0 cisco
> > > > > > username user55 password 0 cisco
> > > > > > !
> > > > > > !
> > > > > > !
> > > > > > !
> > > > > > ip subnet-zero
> > > > > > ip tcp synwait-time 5
> > > > > > no ip domain-lookup
> > > > > > !
> > > > > > ipx routing 5000.5000.5000
> > > > > > isdn switch-type basic-dms100
> > > > > > !
> > > > > > !
> > > > > > !
> > > > > > !
> > > > > > !
> > > > > > interface Loopback0
> > > > > > ip address 133.1.5.5 255.255.255.0
> > > > > > ip ospf network point-to-point
> > > > > > !
> > > > > > interface Serial0
> > > > > > no ip address
> > > > > > encapsulation frame-relay
> > > > > > no fair-queue
> > > > > > no frame-relay inverse-arp
> > > > > > !
> > > > > > interface Serial0.1 point-to-point
> > > > > > ip address 133.1.45.5 255.255.255.0
> > > > > > ipx network 45
> > > > > > frame-relay interface-dlci 524
> > > > > > !
> > > > > > interface Serial0.235 multipoint
> > > > > > ip address 133.1.235.5 255.255.255.0
> > > > > > ip ospf message-digest-key 1 md5 cisco
> > > > > > ip ospf hello-interval 50
> > > > > > ipx network 235
> > > > > > frame-relay map ipx 235.3000.300
> > > > > > 10:34:04: %SEC-6-IPACCESSLOGRP: list 150
> > > > permitted
> > > > > > ospf 133.1.35.5 ->
> > > > > > 224.0.0.5,
> > > > > > 8 packets0.3000 523 broadcast
> > > > > > frame-relay map ipx 235.2000.2000.2000 522
> > > > broadcast
> > > > > > frame-relay map ip 133.1.235.2 522 broadcast
> > > > > > frame-relay map ip 133.1.235.3 523 broadcast
> > > > > > !
> > > > > > interface Serial1
> > > > > > ip address 133.1.56.5 255.255.255.0
> > > > > > encapsulation frame-relay
> > > > > > ip ospf network point-to-point
> > > > > > ipx network 56
> > > > > > frame-relay map ip 133.1.56.6 526 broadcast
> > > > > > frame-relay map ipx 56.6000.6000.6000 526
> > > > broadcast
> > > > > > no frame-relay inverse-arp
> > > > > > !
> > > > > > interface TokenRing0
> > > > > > description VLAN B
> > > > > > ip address 133.1.55.5 255.255.255.0
> > > > > > ipx network 55
> > > > > > ring-speed 16
> > > > > > !
> > > > > > interface BRI0
> > > > > > no ip address
> > > > > > encapsulation ppp
> > > > > > dialer pool-member 1
> > > > > > isdn switch-type basic-dms100
> > > > > > isdn spid1 0555100001 5551000
> > > > > > isdn spid2 0555300001 5553000
> > > > > > ppp authentication chap
> > > > > > ppp multilink
> > > > > > !
> > > >
> > > === message truncated ===
> > >
> > >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:25 GMT-3