Downtime when Enabling TCP-MSS Gloablly?

[Matthew Martin]

Hello All,

When enabling TCP MSS under Wireless > Access Points > Global Configuration, will the APs reboot when I click apply?

Also, under Cisco's WLC Configuration Best Practices, it says: "In general, a 1300 bytes value is a good average, although it can be further optimized depending on your setup.".

Does that still hold true, should I set it to 1300?

Thanks in Advance,
Matt

[balaji.bandi]

good documetnt for reference :

https://mrncciew.com/2013/04/07/configuring-tcp-mss/

[Matthew Martin]

Thanks for the doc.

It doesn't specifically mention downtime. But, when it gives the CLI instructions, it states: "Here is the CLI command how you can configure it. You have to reset the controller to take effect of this command."

I just checked the checkbox on a spare/backup WLC that we have (*which doesn't have any APs associated to it at the moment), under the Access Points > Global Configuration page, and set it to 1300. Then, I clicked Apply. I didn't see any type of pop-up that says I need to restart the controller to take affect.

Any idea, if its instantly active, or does the WLC need to reboot? Is there anyway to confirm if its active?

-Matt

[d.friday]

when you enable TCP-MSS Globally, a reboot is required

I believe the command to show the TCP-MSS is >  show AP tcp-mss- adjust all 

I hope this helps

[Matthew Martin]

Thanks for the comnmand. All APs currently showing as disabled for TCP MSS.

So you're probably correct about needing to reload the WLC. Thanks!

-Matt

[balaji.bandi · Accepted solution]

Any changes in related  MTU to take effective of new MTU it required reboot.