Generally it is recommended for all controllers in a mobilty domain to be running the same version code. To support the new 3602 AP we need to run a Wism2 in ver 7.2 but our Wism1 controllers only go as far as 7.0. Is anyone running this mix in a mobility domain? Does Cisco document this as an acceptible combination? Otherwise we will need to forklift all the Wism1 controllers to support the few 3602 AP's we have at this point.
Haven't seen a mix like what you have. The major thing is APs moving to the other wlc. The 3600 will may try to join WiSM1 but will fail to join the WiSM1 but you existing APs might join and will upgrade to 7.2. If you require mobility between the wism1 and the wism2 then that should be fine, just be aware in case you have APs that flap. If you don't need mobility between the two, then you should have them in a different mobility group.
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...
Greetings!Thank you for the overwhelming response and feedback for the first 17.3.4 EFT/Beta release.
Now we are excited to announce the second refresh of 17.3.4 EFT/Beta Program for PRODUCTION deployments.
This release is the s...