Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I was previously running 8.5.131 with FRA and DCA with "best" channel width, using 2700 series AP's. With .131 the DCA selects an 80MHz bandwidth for the 5GHz band on all three AP's. With .135, it reverts back to 20 MHz. To me this seems like a bug. ...
We already know that ASA 9.0 supports site-to-site VPN in multiple context mode. But remote access VPN isn't supported. Obviously, SSL-VPN is a very important feature for most multi-tenant deployment scenarios where each context acts as a border fire...
Interesting! The consequence is that many devices won't use that AP at all as they usually prefer AP's that have a higher channel width. So effectively, event-driven RRM disables that AP for many clients because they choose to roam to another AP with...
I noticed this too, but on 9800 WLC with 17.9.5 . It seems like this happens when event driven RRM is enabled. Then that "emergency" channel change doesn't seem to respect the usual configuration when it comes to channel width. If someone can test an...
Did you ever resolve this on 17.9.5 in the end? Also, it seems like the affected AP's (given that I'm hitting the same bug as you) look like the image below - 0 associated client but apparent high rx/tx utilization:
The share is missing the two newest versions for me. I see that there has been an upload of the release notes for .73, but the actual images there are still at version .51 . How come?
UPDATE: It seems to also apply when you reboot your WLC. So this is a more severe issue than I initially thought - meaning it only happens after upgrade.
