Has anyone managed to get the new HA feature working properly with LAG enabled? Without LAG, I can simulate a failure of the Primary WLC and the Secondary kicks in as active as expected; however, when LAG is enabled the units go active/active and there is no way to get the setup to recover no matter how many times I reboot either WLC as they don't negotiate the correct state on bootup because they can't see each other, even though all links have been reinstated.
Also, why is there a limitation that says I have to directly connect the redundancy ports on each unit? I would prefer to have the WLCs on different sites, connected by a L2 link. It seems like a half-finished feature if you can't split them up.
We are excited to announce the Second refresh of 17.6.2 EFT/Beta Program for PRODUCTION deployments.
This release is the second qualified EFT/Beta Image and is BU supported.
After previous 17.6.1 CCO, this p...
Listen: https://smarturl.it/CCRS8E33 Follow us: https://twitter.com/ciscochampion The goal for stadium and large venue Wi-Fi is to deliver an exceptional, fast, and reliable wireless experiences to tens of thousands of fan...
We are pleased to announce the immediate availability of the IOS-XE release 17.6.1 for the Catalyst Wireless Controllers. The new code is now posted on the CCO and can be found at this link:
This version now introduces experimental new feature, "Upgrade Advisor, targeted to one of common case generators: what are the supported versions and how to upgrade my current controllers and APs
It supports both AireOS and IOS-XE, covering since ...
Thank you for the overwhelming response to the First and Second EFT refresh of 8.10MR6!
We are excited to announce the third refresh of 8.10 MR6 EFT Program for PRODUCTION deployments.
While the CCO release of 8.10MR6 is just a few we...