Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
what shall i do?pls help in this matter to overcome the MTU limitations
Don't set size larger than the end-to-end's MTU.
Normally, you should know what the max MTU is, but if you don't, as Shivlu suggested you can set the don't fragment option. This usually precludes an interface, for which your packet is too big, fragmenting it and forwarding it. Also usually, the interface should try to inform you it needed to fragment your packet. Later versions will actually send their interface max MTU in the notification, but I'm unsure there's an easy way for you to "see" the value. (Note: lack of ping replies may indicate ping request was not forwarded because of don't fragment and packet was too large.)
On later IOS version, believe the don't fragment is a command line option. On older IOSs, you need to invoke extended ping to use it.
What may be tedious is finding the max MTU. However, when using extended ping, there should be an option to ping a range of sizes.
