[j-nsp] OSPF problem

[José Esteves]

I have also these routers connected to a PP8600.
I'm not assuming the problem is the PP8600 because it's only one connection
in L2 to the rest of the Vlan. I have OSPF running there in different area
from the backbone, to route my management network.

JE
+----------------------------------------------------------------------+
|             |||||                 | Edifício Sede                    |
|            |||                    | Lugar de Poços                   |
|           |||  .::::.             | 2950 Palmela                     |
|           ||| ::::V:::            | Portugal                         |
|           ||| ::::::::            |----------------------------------|
|           |||  '::::'             | José Esteves                     |
|            |||                    | Noc IP Coordenador               |
|             |||||||||             | e-mail: jose.esteves at cabovisao.pt|
|                                   | Tel.  : +351 21 080 02 65        |
| CABOVISÃO- TELEVISÃO POR CABO, SA | Fax   : +351 21 080 10 01        |
+----------------------------------------------------------------------+

-----Original Message-----
From: Roberts, Michael J. (IATS) [mailto:RobertsMJ at missouri.edu] 
Sent: sexta-feira, 18 de Junho de 2004 17:00
To: José Esteves; Charles R. Anderson; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] OSPF problem

Something fishy is going on.  I have almost the same setup as Chuck, only in
our lab environment.  I had a similar event happen a couple days ago, so I
wanted to enable the OSPF trace options to get some more detail in case it
happened again.  When I committed the change, the adjacency between the M20
and my Passport 8600 flapped.  I am going to contact Nortel/JTAC after
lunch.  I am running 6.3R1 in the lab on the M20 and 3.7 on the Passport.

-mike

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of José Esteves
Sent: Friday, June 18, 2004 9:10 AM
To: Charles R. Anderson; juniper-nsp at puck.nether.net
Subject: RE: [j-nsp] OSPF problem

Curious or not, I have CIC (Cisco Info Center) to receive the erros, and now
the best part, this only happens between 8:00 AM and 11:30 PM.

This only happens on routers over the same LAN (Same Netmask).

At least I'm not only the only one with this behavior, could this be a BUG
on 6.3R1.3 release?

+----------------------------------------------------------------------+
|             |||||                 | Edifício Sede                    |
|            |||                    | Lugar de Poços                   |
|           |||  .::::.             | 2950 Palmela                     |
|           ||| ::::V:::            | Portugal                         |
|           ||| ::::::::            |----------------------------------|
|           |||  '::::'             | José Esteves                     |
|            |||                    | Noc IP Coordenador               |
|             |||||||||             | e-mail: jose.esteves at cabovisao.pt|
|                                   | Tel.  : +351 21 080 02 65        |
| CABOVISÃO- TELEVISÃO POR CABO, SA | Fax   : +351 21 080 10 01        |
+----------------------------------------------------------------------+

-----Original Message-----
From: Charles R. Anderson [mailto:cra at wpi.edu] 
Sent: sexta-feira, 18 de Junho de 2004 15:02
To: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] OSPF problem

On Fri, Jun 18, 2004 at 12:58:26PM +0100, José Esteves wrote:
> Since I upgrade the Junos to the JunoOS 6.3R1.3, my OSPF are very
instable.
> On the BDR I've got the following messages:
> RPD_OSPF_NBRUP: OSPF neighbor (ge-1/2/0.0) state changed from Exchange to
> Full due to DBD exchange complete
> RPD_OSPF_NBRUP: OSPF neighbor (ge-1/2/0.0) state changed from Init to
> ExStart due to Two way communication established
> RPD_OSPF_NBRDOWN: OSPF neighbor (ge-1/2/0.0) state changed from Full to
Down
> due to NBR declared dead on inactivity

Interesting, I saw this continually happen every few minutes for just
over an hour about a week ago for no explainable reason, and I too
just recently upgraded to 6.3R1.3.  The DR is an M10, and there are
two Nortel Passport 8600 routers, one of which is the BDR.  There were
no link status changes or errors on the links.  All the routers logged
the same error messages "NBR declared dead on inactivity".

_______________________________________________
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