Cisco Blogs


Cisco Blog > Mobility

Non-Stop Wireless Network at John Muir Health

April 15, 2014 at 8:12 am PST

Previously I have blogged about No SSID Outage and No Client Reauthentication whereby even if your Cisco Wireless Controllers were to fail due to any reason, the clients will NOT experience any downtime due to Stateful Failover functionality to a Standby Controller. What could be better than that? Controllers that never go down! 

muir1

A picture is worth a thousand words! As you can see the above the WEBGUI on a 5508 series wireless controller shows that, it is running 7.0 code which was an MD release, has been operational for over a thousand days or over three years! Read More »

Tags: , , , , , , , , , , , , , , , , , , , , , , ,

Wireless Controller Redundancy with No Client Reauthentication Needed

July 12, 2013 at 5:00 am PST

Last fall, I blogged about No SSID Outage or Access Point Stateful Switchover introduced with the AireOS 7.3 release whereby if your wireless LAN Controller fails due to some hardware failure, thousands of Access Points fail over sub-second to the standby controller! This is possible due to continuous synchronization of CAPWAP states, Configuration Changes, Radio Channel and Power, Roaming Keys and Access Point licenses between the two Controllers. This means even if the administrator changes the configuration, channel plans or the clients roam and the primary controller fails; the Access Points will simply fail over in a stateful fashion to the secondary. In this blog, I will share details on the upcoming enhancements to High Availabilty with the 7.5 release.

In the upcoming AireOS 7.5 release, we take High Availability to the next level with two critical enhancements.

1. Today, after Access Points fail over from the primary to the standby controller, each client tries to re-authenticate and the standby controller then checks against its CCKM database whether the client has already authenticated. At the rate of several tens of authentications per second, it can take anywhere from zero to a few hundred seconds for the tens of thousands of clients that are connected to a controller to re-authenticate. The client stateful essentially eliminates this downtime with sub-second failover. Thus the total downtime that any user running a voice-call or Citrix session experiences is 2-3 seconds that the application requires to reconnect.

sso1 Read More »

Tags: , , , , , , , , , , , , , , ,