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.
Sent from Cisco Technical Support iPhone App
*****Help out other by using the rating system and marking answered questions as "Answered"*****
We are moving! Please use WLCCA Forum for updates and discussions
[toc:faq] Wireless LAN Controller (WLC) Config Analyzer Download Click
here to Download To request access, send an e-mail to
email@example.com. Please include your Cisco.com userna...
[toc:faq] IntroductionHere is the step by step process that we have to
take care of while converting LWAPP to IOS and then vice versa..LWAPP to
IOSThe hardware used = 1141 AP (make sure we are using the right
[toc:faq] Introduction AnyConnect Secure Mobility Client 3.0: Network
Access Manager & Profile Editor on Windows Summary Use the Cisco
AnyConnect Network Access Manager Profile Editor to build custom
profiles for the AnyConnect Secure Mobility Client. App...