Cisco Cisco 5508 Wireless Controller Referencia técnica
4
High Availability (SSO) Deployment Guide
D r a f t L a b e l — C i s c o C o n f i d e n t i a l
High Availability in Release 7.5
High Availability in Release 7.5
To support High Availability without impacting service, there needs to be support for seamless transition of clients and APs from
the active controller to the standby controller. Release 7.5 supports Client Stateful Switch Over (Client SSO) in Wireless LAN
controllers. Client SSO will be supported for clients which have already completed the authentication and DHCP phase and have
started passing traffic. With Client SSO, a client's information is synced to the Standby WLC when the client associates to the
WLC or the client’s parameters change. Fully authenticated clients, i.e. the ones in Run state, are synced to the Standby and
thus, client re-association is avoided on switchover making the failover seamless for the APs as well as for the clients, resulting
in zero client service downtime and no SSID outage.
the active controller to the standby controller. Release 7.5 supports Client Stateful Switch Over (Client SSO) in Wireless LAN
controllers. Client SSO will be supported for clients which have already completed the authentication and DHCP phase and have
started passing traffic. With Client SSO, a client's information is synced to the Standby WLC when the client associates to the
WLC or the client’s parameters change. Fully authenticated clients, i.e. the ones in Run state, are synced to the Standby and
thus, client re-association is avoided on switchover making the failover seamless for the APs as well as for the clients, resulting
in zero client service downtime and no SSID outage.
Redundancy Port Connectivity in 7.5
In controller release 7.3 and 7.4, back-to-back connectivity through redundancy port restrains the active and standby
controllers to be in different locations. There are two mandatory interfaces for redundancy, redundancy port and
redundancy management interface. Redundancy port uses dedicated physical port eth1 (similar to service port). It is used
for all redundancy communication (AP, Client data, configuration sync, keep-alive messages and role negotiation
messages). Redundancy management interface is used to check for the reachability of the peer and management gateway.
controllers to be in different locations. There are two mandatory interfaces for redundancy, redundancy port and
redundancy management interface. Redundancy port uses dedicated physical port eth1 (similar to service port). It is used
for all redundancy communication (AP, Client data, configuration sync, keep-alive messages and role negotiation
messages). Redundancy management interface is used to check for the reachability of the peer and management gateway.
To support the active and standby WLCs in different data centers, in release 7.5, back-to-back redundancy port
connectivity between peers is no longer mandatory and the redundancy ports can be connected via switches such that
there is L2 adjacency between the two controllers.
connectivity between peers is no longer mandatory and the redundancy ports can be connected via switches such that
there is L2 adjacency between the two controllers.
Backward compatibility for release 7.3/7.4 will be supported, wherein back-to-back redundancy port connectivity is used
for redundancy communication between the WLCs and the redundancy management interface is used to check the
reachability to the peer and to management gateway.
for redundancy communication between the WLCs and the redundancy management interface is used to check the
reachability to the peer and to management gateway.
No additional configuration change is required for redundancy port and the configuration remains the same as in 7.3/7.4
release.
release.
Supported HA Topologies
Supported HA Topologies in Release 7.5
5500/7500/8500 Series Controllers
1.
Back-to-back Redundancy Port (RP) connectivity between the two WLCs, Redundancy Management Interface (RMI)
connectivity to check peer and management gateway reachability.
connectivity to check peer and management gateway reachability.
2.
RP connectivity with L2 adjacency between the two WLCs, RMI connectivity to check peer and management gateway
reachability. This can be within the same or different data centers.
reachability. This can be within the same or different data centers.
3.
Two 5508, 7500 or 8500 connected to a VSS pair. Primary WLC connected to one 6500 and the Stand-by WLC to the other
6500.
6500.