Both MTUs are consistent and always have been. I started out with 9216 physical MTU and 1500 inet MTU, but have since just deleted the custom MTU and went with the defaults. I am quite sure now that this is not an MTU issue, but rather a deficiency with the EX2500. I've opened up a JTAC case and will let the list know what the problem turns out to be.
-evt From: Jonathan Looney [mailto:jonloo...@gmail.com] Sent: Monday, March 08, 2010 10:57 AM To: Eric Van Tol Cc: Juniper-Nsp Subject: Re: [j-nsp] Strange IS-IS Problem On Sun, Mar 7, 2010 at 8:04 AM, Stefan Fouant <sfou...@shortestpathfirst.net<mailto:sfou...@shortestpathfirst.net>> wrote: I could be wrong but if I recall correctly the Hello PDU uses a padding TLV to pad the initial hello to the maximum MTU size. I don't believe these packets are fragmentable if I recall considering it's a CLNS frame, i.e. no IP header and thus no fragment options. This is also my understanding. And, this makes me think that you really should make the MTUs on both sides consistent before you try to troubleshoot anything else. -Jon _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
