5520 WLC 8.10.181.3

[Moudar]

Hi,

8.10.181 has some bugs like CSCwd37092 and CSCwc78435.

What is best, upgrading to 8.10.181.3 or do the workrounds whitch are not enough!

Is there anyone who upgraded 5520 to 8.10.181.3 to solve the problem with APs like 2800 series?

Did it went well?

Any new issues or bugs?

Was it a normal upgarde or was it more ?

[Scott Fella]

Do you have a 5520 in your lab where you can test?  That is really the best way as environments vary and the experience one has will not be the same for all.  If you are on 8.10.181.0 and you are running into issues mentioned in the bug, then you have no choice but to upgrade.  Again, my preference would be to upgrade in a lab and validate everything before you move into production. If your environment is affected and users are complaining, then that is when I would move to production, only testing the upgrade in the lab.  The slower you take to fix the issue that causes user experience issues, the worst it is for your, because users will always complain and remember how bad it was.

Keep in mind that new bugs takes time to get discovered.  A gold code or a preferred code can be deferred at a later time.  

[Arshad Safrulla]

Below is the document which contains TAC recommended codes for any AireOS WLC.

Recommended AireOS Wireless LAN Controller Releases - Cisco

You should stick to this document for Code recommendations, unless Cisco TAC advised you to upgrade to fix a bug or you want to experience a feature available in the new release (which is not the case). 

[Moudar]

We have got all our 9120 APs after september and all of them were VID 07

8.10.171 does not support these, or do i miss something?

[marce1000]

 - That particular problem only relates to being used on the 9800-environment not aireos based controllers.

 M.

[Moudar]

We have the exact explained problem.

2800 AP have 0,5 MB download and 1000 MB uppload

[Leo Laohoo]

Change the TCP MSS value.  Start with a low value, like 800, and see if it improves stuff. 

In our case, we had to go below the recommended "1250" because we have some sites that would not work at that value.  The "best" result we got was TCP MSS size of 896.  

[Scott Fella]

Follow the workaround in the bug like Leo mentioned and see.  You don't have many options here, workaround or upgrade to TAC escalation image.

[Rich R]

That's incorrect @marce1000 - new AireOS code is required same as IOS-XE to support the new AP hardware.

[marce1000]

 - The special release is summarized here : https://community.cisco.com/t5/wireless-mobility-knowledge-base/aireos-8-10mr8-escalation-special/ta-p/4715772 , as stated upgrade IF you experience the problem within your wireless environment and or in that case there is no turning back (normally)

 M.

[Moudar]

Do you mean that if we upgrade to 8.10.181.3 and then we needed to downgrade back to 8.10.181 for some reason, is the downgrade process not possible?

[Rich R]

@Moudar I've already answered your question on a separate thread - pretty similar to what @Scott Fella said.
Downgrade is possible but then you will have the bugs again.

So with new APs, and if you see either of the bugs, then you will need to apply the TCP MSS workaround (only valid for the TCP throughput issue) or upgrade (the only way to fix the 802.1x issue).

[Leo Laohoo]

8.10.182.0 is now out. 

• 3504
• 5520
• 8540

[Moudar]

No release notes!!

[Leo Laohoo]

---

@Moudar wrote:

No release notes!!

---

Release Notes will be out in the next few months.