[j-nsp] OSPF route flapping
Harry Reynolds
harry at juniper.net
Fri Jun 17 17:22:23 EDT 2005
It appears that a router, ostensibly the LSA originator, has opted to purge them. This is done by re-flooding with max age to flush them from the area's LSDB. In JUNOS software, a clear ospf database purge will cause that router to re-flood all LSAs, not just those that are self originated, with max age.
I think you mentioned these were static routes. Any chance they may point to an interface/next-hop that is bouncing on the router the ASBR? Otherwise, need to locate the router that is flooding with max age (may not be the LSA originator, but should be) and go from there.
Cheers
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of
> Javier Gallardo (DF/TEM)
> Sent: Friday, June 17, 2005 2:15 PM
> To: Javier Gallardo Córdova
> Cc: juniper-nsp at puck.nether.net
> Subject: RE: [j-nsp] OSPF route flapping
>
> Hi Erdem,
>
> I made a revison for physical link and it doesn´t flap. I
> check with ping to Summmit interfase.
>
> No, I activate the traceoptions with "flag packets detail"
> and the output is in the attached file.
>
> Do you know why appears the states QUIET->QUIET ,
> QUIET->PURGE_PENDING.
>
> Too, from the next printouts (taken with brief difference
> time), I saw the Age changes abruptly to 3600 from a value
> lower to 7.
>
> M20# show ospf database advertising-router 0.164.219.227 extern
> Type ID Adv Rtr Seq Age
> Opt Cksum Len
> Extern 13.52.120.64 0.164.219.227 0x802ec970 2
> 0x2 0xe7bc 36
>
> Extern 13.52.120.64 0.164.219.227 0x802ec96e 3600
> 0x2 0xebba 36
>
> I´ll appreciate your comments.
>
> Thanks and regards.
>
> //Javier
>
> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net]
> Sent: Viernes, 17 de Junio de 2005 02:54 p.m.
> To: Javier Gallardo Córdova
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] OSPF route flapping
>
>
> Hi,
>
> I might be re-stating the obvious but are you sure the
> physical links don't flap?
> Otherwise, it might be an MTU issue, maybe.
>
> You can turn on ospf traceoptions with something like;
>
> traceoptions {
> flag packets detail;
> flag database-description detail;
> flag error detail;
> }
>
> Cheers,
> Erdem
> On 6/17/05, Javier Gallardo Córdova <jagc64 at yahoo.com> wrote:
> > Hi,
> >
> > I have the next behavior at M20 route table for several
> statics routes announced by a Summit48si via OSPF.
> > Jun 17 12:42:33 RELEASE 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Release Int Ext>
> > Jun 17 12:42:33 ADD 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Int Ext>
> > Jun 17 12:42:43 RELEASE 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Release Int Ext>
> > Jun 17 12:42:43 ADD 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Int Ext>
> > Jun 17 12:42:53 RELEASE 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Release Int Ext>
> > Jun 17 12:42:53 ADD 13.52.120.64/30 gw 192.168.2.50
> OSPF pref 150/0 metric 7/0 fe-0/1/2.0 <Int Ext>
> >
> > Someone know why is the route flapping with 10 seconds period?.
> >
> > Thanks and regards.
> > //Javier
> >
> > __________________________________________________
> > Correo Yahoo!
> > Espacio para todos tus mensajes, antivirus y antispam ¡gratis!
> > Regístrate ya - http://correo.espanol.yahoo.com/
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list