WLC - Different IOS

Unanswered Question
May 12th, 2009

Hello All


What would be the impact of having different IOS on the WLCs ? Is it only that when the AP's shift from one WLC to another, they would be re-imaged, and will be booted back ? are there any oter noted issues ? one wlc runs 5.1.163 and another 4.0.62...



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
George Stefanick Tue, 05/12/2009 - 06:05

As you mentioned the image impact when the ap moves from one controller to another is one.


When you have mismatches like this and should you call TAC for any issues they will inform you to upgrade to a common level.


Ita hard to say exactly what you might see but you need to consider if you do. Assume for a moment you start to have issues with client association, roaming, mobility issues, etc ... You will have a hard time weeding out what is a code issue and what is not.


4.0 code is a few years old now, and there has been great improvements since then.


Is there a reason that requires you to have 2 versions ?


sblavanya Tue, 05/12/2009 - 06:36

There is basically no reason.. WLCs are on a migration phase and for a short period of time, the WLCs would have different Image.. 4.0 would be upgraded to 5.1.163 within 2-3 weeks, but i just wanted to be sure that it would work fine till the transition period..

George Stefanick Tue, 05/12/2009 - 07:48

You shoud be ok for that short period of time. If i were you i may move ~ say a group of APs on the first floor (for example) to the controller on 4.0 code.


If you pepper the APs between controller on different codes you may see some problems.


if you find this post helpful please rate it ... Thanks!

sblavanya Tue, 05/12/2009 - 08:04

Thanks.. I wouldnt manually move the APs to a particular controller due to administrative overheads in future.. Will leave it the same way till we upgrade.



Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode