I wouldn't say it is good news. Lots of people smoke and drink too, it doesn't make it healthy. Long term you want to stop fragmenting.
LR Mack McBride Network Architect From: Eric A Louie [mailto:[email protected]] Sent: Monday, February 11, 2013 2:00 PM To: Mack McBride; Cisco NSP Subject: Re: [c-nsp] ip tcp adjust-mss the good news is, I'm the provider network and it's my backbone. the bad news is, I have a mixed environment, Foundry/Brocade and Cisco. Much appreciated, Eric ________________________________ From: Mack McBride <[email protected]<mailto:[email protected]>> To: Eric A Louie <[email protected]<mailto:[email protected]>>; Cisco NSP <[email protected]<mailto:[email protected]>> Sent: Mon, February 11, 2013 12:54:50 PM Subject: RE: [c-nsp] ip tcp adjust-mss 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] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
