After some more investigation following has been found:
Mastership mismatch is not the cause of the JNPR sending MS
bit on. It is
done to signal the master to reset the state machine to
ExStart. JNPR does
this because state machine went to BadLSReq and restarted negotiation.
Dec 4
]
Sent: dinsdag 4 december 2007 18:19
To: Stefan Fouant; Jeff Tantsura
Cc: juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] OSPFv3 interoperability with another vendor
H... it appears from the trace output that both routers
are indicating
that they are the master. Can you provide
Hi,
I'm testing OSPFv3 with another vendor and unable to get it UP, the session
is stuck in ExStart. (no MTU mismatch)
On another vendor router I see following error :
%OSPF3-7-NBR: OSPF3-1: 192.168.1.4 EVENT:
Sequence Mismatch STATE:*
%OSPF3-7-PKT_ERRORS: OSPF3-1
STATE: Exchange NBR
H... it appears from the trace output that both routers are indicating
that they are the master. Can you provide the config for the neighboring
router?
Stefan Fouant
On 12/4/07, Jeff Tantsura [EMAIL PROTECTED] wrote:
Hi,
I'm testing OSPFv3 with another vendor and unable to get it UP,
in advance,
Jeff
_
From: Stefan Fouant [mailto:[EMAIL PROTECTED]
Sent: dinsdag 4 december 2007 18:04
To: Jeff Tantsura
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] OSPFv3 interoperability with another vendor
H... it appears from the trace output that both routers
Hi Paul,
Thanks a lot, will give it a try.
Regards,
Jeff
-Original Message-
From: Paul Goyette [mailto:[EMAIL PROTECTED]
Sent: dinsdag 4 december 2007 18:19
To: Stefan Fouant; Jeff Tantsura
Cc: juniper-nsp@puck.nether.net
Subject: RE: [j-nsp] OSPFv3 interoperability with another
6 matches
Mail list logo
