Re: [j-nsp] ospf on trunk interface

From: Dave Katz (dkatz@juniper.net)
Date: Thu May 31 2001 - 00:47:19 EDT


The most common cause of stuck-in-exstart is an MTU mismatch. If not,
turn on some tracing and see what OSPF has to say about it.

   X-JNPR-Received-From: outside
   Date: Thu, 31 May 2001 00:07:30 -0400
   X-From_: dave_murphy_1@excite.com Thu May 31 00:07:29 2001
   Received-Date: Thu, 31 May 2001 00:07:29 -0400
   Old-Date: Wed, 30 May 2001 21:07:18 -0700 (PDT)
   From: David Murphy <dave_murphy_1@excite.com>
   Mime-Version: 1.0
   Content-Type: text/plain; charset=us-ascii
   Content-Transfer-Encoding: 7bit
   X-Mailer: Excite Inbox
   X-Sender-Ip: 156.153.255.196
   Old-X-Envelope-To: juniper-nsp
   Resent-From: jared@puck.nether.net
   Resent-To: juniper-nsp@puck.nether.net
   X-Mailing-List: <juniper-nsp@puck.nether.net> archive/latest/518
   X-Loop: juniper-nsp@puck.nether.net
   Precedence: list
   Resent-Sender: juniper-nsp-request@puck.nether.net

   Hi, all,

   I am a newbie for juniper, when I want to configure ospf on trunk
   subinterface encapsulated with 802.1q, the neighbor status is always
   ExStart, and can never reach full, what is the matter?

   thanks in advance.

   _______________________________________________________
   Send a cool gift with your E-Card
   http://www.bluemountain.com/giftcenter/



This archive was generated by hypermail 2b29 : Mon Aug 05 2002 - 10:42:42 EDT