[c-nsp] ip tcp adjust-mss

Eric A Louie elouie at yahoo.com
Mon Feb 11 16:00:21 EST 2013


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 <mack.mcbride at viawest.com>
To: Eric A Louie <elouie at yahoo.com>; Cisco NSP <cisco-nsp at puck.nether.net>
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: cisco-nsp-bounces at puck.nether.net 
[mailto:cisco-nsp-bounces at puck.nether.net] 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  cisco-nsp at puck.nether.net 
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


More information about the cisco-nsp mailing list