CT5508 and WLC4404 failover

pcce5w2hlh · ‎11-11-2010

We have an existing AIR-WLC4404-100-K9 wireless controller, but is looking for another unit of controller for redundancy purpose.

The AIR-CT5508-100-K9 controller is the new Cisco wireless controller.

Does the CT5508 and WLC4404 perform failover between each other?

Will there be issue connecting them together and setting failover to each other as they are completely two different WLC model (one is WLC4404, one is CT5508)?

Nicolas Darchis · ‎11-11-2010

No issues at all.

All WLC models are compatible with regards of AP failover. The important is that they run the same software version. And the 5508 either runs a 6.0 or a 7.0.

Meaning if you have an older code on your 4404 you will have to upgrade the 4404. But apart from that : all ok !

Nicolas

===

Don't forget to rate answers that you find useful

wififofum · ‎11-14-2010

Nicolas, Are you saying that a 7.x controller can backup a 6.x controller? Can it be a Mobility Group member with 6.x controllers as well? Thanks for your reply,

Nicolas Darchis · ‎11-14-2010

I was just saying that the 5508 can only run 6.0 code or later.

Any code can backup any other code. However, the failover won't be smooth if the APs have to change softare version when failing over. So it's best practice to have all WLCs running the same code .

But you can have WLCs from different codes in a mobility group, that's no problem.

Nicolas

----

Don't forget to rate answers that you find useful

Leo Laohoo · ‎11-14-2010

As long as you are not using OfficeExtend.

wififofum · ‎11-14-2010

Nicolas and Leo,

Thanks for your replies. The reason I ask is that there have been issues in the past with interop between code releases in a Mobility Group. SInce greater than 250-AP support is only available in 7.x, and 7.x is a little early for production use, the ability to have a Mobility Group backup controller with WiSM capacity on 7.x is a viable option.

Regards,

Nicolas Darchis · ‎11-14-2010

Indeed, but now 4.2 and all 6.0 and later are made to be interoperable in Mobility so this concern should not be appliable in recent and future releases :-)

Nicolas