From: Rajeev Siddappa (raj_lab@xxxxxxxxx)
Date: Fri Jan 11 2002 - 07:10:10 GMT-3
Stephen,
I do not see that he is redistributing from IGRP to
OSPF. he is only doing it from OSPF to IGRP and I am
surprised to seee that.
Rajeev.
--- Stephen Oliver <stevie_oliver@hotmail.com> wrote:
> He has no peer neighbor-route on the dialers.
>
> Deny the dialer interface ip address being
> redistributed into OSPF with a
> route-map in the redistribution command. I've come
> across this before.
> Even though you have passived the dialer for IGRP
> the /32 address is still
> being redistributed into OSPF.
>
> Because you are running a classful protocol on one
> side of the router and
> OSPF on the other and they use the same major
> network the dialer interface
> ip address is being redistributed into the OSPF
> domain as a /32 external
> route. It dissapears when the circuit goes down so
> thats a change and the
> circuit comes up again. The /32 appears until the
> circuitgoes down then it
> bounces.
>
> This issue would not occur if the isdn circuit was
> on a different major
> network from the IGRP one ie. 133.1.0.0
>
> Stevie.
>
>
>
> >From: Rajeev Siddappa <raj_lab@yahoo.com>
> >Reply-To: Rajeev Siddappa <raj_lab@yahoo.com>
> >To: EA Louie <elouie@yahoo.com>,
> ccielab@groupstudy.com
> >Subject: Re: OSPF Demand Circuit
> >Date: Fri, 11 Jan 2002 00:56:12 -0800 (PST)
> >
> >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
>
=== message truncated ===
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:24 GMT-3