[j-nsp] OSPF neighbor Down :: without reason

Farhan Jaffer bandhani at gmail.com
Fri Mar 28 12:04:09 EDT 2008


Thanks for all comments.

But these logs are valuable if it happens again. I am running this n/w
more than 2 yrs now. And this is first time OSPF neighbor failed
without any apparent reason.

My question is, Is there any other reasons other than media to flapped
neighbor relationship?

Thanks again for all feedback.

Regards
Farhan Jaffer

On Mon, Mar 24, 2008 at 4:47 PM, Stefan Fouant <sfouant at gmail.com> wrote:
> Can you 'set flag event detail' on the traceoptions within 'protocols ospf'?
> You should be able to get a little more detailed information as to what is
> causing this problem.
>
> Stefan Fouant
>
>
> On 3/24/08, Farhan Jaffer <bandhani at gmail.com> wrote:
> >
> >
> >
> > Hi,
> >
> > I am running OSPF in my n/w. Yesterday one neighbor got down & up
> > after few seconds, i couldn't get any idea from logs.
> >
> > One side:
> > rpd[3120]: RPD_OSPF_NBRDOWN: OSPF neighbor a.b.c.d state changed from
> > Full to Down due to InActiveTimer (event reason: neighbor was inactive
> > and declared dead)
> >
> > Other side:
> > rpd[3055]: RPD_OSPF_NBRDOWN: OSPF neighbor e.f.g.h state changed from
> > Full to Init due to 1WayRcvd (event reason: neighbor is in one-way
> > mode)
> >
> > There was no media flapping, errors on media, router malfunctioning, etc,
> etc.
> >
> > Any idea?
> >
> > Thanks in advance.
> > _______________________________________________
> > juniper-nsp mailing list juniper-nsp at puck.nether.net
> > https://puck.nether.net/mailman/listinfo/juniper-nsp
> >
>
>


More information about the juniper-nsp mailing list