[155950] in North American Network Operators' Group
Re: MTU mismatch on one link
daemon@ATHENA.MIT.EDU (Scott Helms)
Fri Aug 31 11:22:46 2012
Date: Fri, 31 Aug 2012 11:21:56 -0400
From: Scott Helms <khelms@ispalliance.net>
To: nanog@nanog.org
In-Reply-To: <5040CD54.4080509@vianet.ca>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
If you don't exceed the MTU ever then it shouldn't matter, but unless
the MTUs are above what the protocol can handle on a specific link you
probably will. Most commonly this happens on DSL links using PPPoE (the
MTU needs to be at 1492 for the overhead) and it causes all kinds of odd
behavior for clients.
On 8/31/2012 10:42 AM, Andrew K. wrote:
> Besides routing protocol convergence is there any service issues with
> running mismatched MTU? Assuming the packet flow does not exceed the
> smallest MTU value.
>
>
> On 8/31/2012 10:28 AM, Dan White wrote:
>> On 08/31/12 09:30 -0400, Tom Taylor wrote:
>>> Has anyone run into a situation where the MTU at one end of a link
>>> was configured differently from the MTU at the other end? How did
>>> you catch it?
>>>
>>> In general, do you see any need for a debugging tool to be
>>> standardized to find such mismatches?
>>
>> Performing a ping with a large packet size '-s', and/or with packet
>> fragmentation turned off '-M do' have been our primary tools for finding
>> MTU (layer 2 and layer 3) mismatches.
>>
>
--
Scott Helms
Vice President of Technology
ZCorum
(678) 507-5000
--------------------------------
http://twitter.com/kscotthelms
--------------------------------
