It is common practice because people do not control all of the MTU sizes on all of the links in their network. If you control all of the links you raise the MTU. Sometimes that isn't an option due to providers or legacy equipment (sometimes equals more often than not). I never said it was good, I said it was common. In a follow up response I compared it to smoking and drinking. Lots of people do it but it doesn't make it healthy. I am suffering in the fourth year of trying to get such a link replaced. Thankfully it is the last one. At least till we make another acquisition.
LR Mack McBride Network Architect From: Aaron [mailto:[email protected]] Sent: Monday, February 11, 2013 2:44 PM To: Mack McBride Cc: Eric A Louie; Cisco NSP Subject: Re: [c-nsp] ip tcp adjust-mss Disagree, it is not a common practice. You should make your MTU large enough. On Mon, Feb 11, 2013 at 3:54 PM, Mack McBride <[email protected]<mailto:[email protected]>> wrote: This is very common practice and practically everyone does it. Usually if you have your own backbone you enlarge the backbone packet size though. Sometimes that isn't an option due to provider switches in the path. LR Mack McBride Network Architect -----Original Message----- From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Eric A Louie Sent: Monday, February 11, 2013 12:56 PM To: Cisco NSP Subject: [c-nsp] ip tcp adjust-mss I just put in this command on my upstream interfaces to help my mpls network pass traffic - that is, my effort to eliminate fragmentation in my backbone. Is anyone else using this method of "mtu control"? I need some support - my CEO is asking why I have to do this, and who else does it, and is it a common practice, etc, so I'm looking for evidence, more than just "The Cisco TAC told me to do it". thanks Much appreciated, Eric _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
