From: ccie2be (ccie2be@nyc.rr.com)
Date: Mon Jul 19 2004 - 23:46:37 GMT-3
The only situation I'm aware of where this is a potential issue assuming the
default mtu size hasn't been changed is if you're running 802.1q tunneling
because that requires the mtu to be larger by 4 bytes. This is a 3550
feature, so if you're not doing this tunneling, it shouldn't be a problem.
I also vaguely recall the possibility of a mtu mismatch with isis. I don't
recall the details but I believe the problem can be solved with the command,
no hello padding. A while back I recall reading a tech note on this but I
don't have the link. I wold check the isis support page for more info.
HTH at least a little.
----- Original Message -----
From: "CCIE" <ccie@gmx.net>
To: <ccielab@groupstudy.com>
Sent: Monday, July 19, 2004 2:17 PM
Subject: Troubleshoot MTU mismatch?
> Hi Group,
>
> I search for a solution to successfully troubleshoot MTU mismatch between
> devices (Serial link, Atm etc). Assume for example a BGP Peering is
flapping
> and you want to know if the Layer 2 connectivity is correct how you can
> debug or troubleshoot types of MTU mismatch and correct them?
>
> Regards
>
> Carlos
>
> _______________________________________________________________________
> Please help support GroupStudy by purchasing your study materials from:
> http://shop.groupstudy.com
>
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sun Aug 01 2004 - 10:11:59 GMT-3