Cisco Cisco 5508 Wireless Controller Referencia técnica
5
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 (SSO) Deployment Guide
High Availability in Release 7.3 and 7.4
Redundancy Port
This interface has a very important role in the new HA architecture. Bulk configuration during boot up and incremental
configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this
port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP
keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure,
the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual
time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone
controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are
picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).
configuration are synced from the Active WLC to the Standby WLC using the Redundant Port. WLCs in a HA setup will use this
port to perform HA role negotiation. The Redundancy Port is also used in order to check peer reachability sending UDP
keep-alive messages every 100 msec (default timer) from the Standby WLC to the Active WLC. Also, in the event of a box failure,
the Active WLC will send notification to the Standby WLC via the Redundant Port. If the NTP server is not configured, a manual
time sync is performed from the Active WLC to the Standby WLC on the Redundant Port. This port in case of standalone
controller and redundancy VLAN in case of WISM-2 will be assigned an auto generated IP Address where last 2 octets are
picked from the last 2 octets of Redundancy Management Interface (the first 2 octets are always 169.254).
Configure HA from the CLI
Complete these steps:
1.
Before you configure HA, it is mandatory to have both the controllers' management interface in the same subnet:
WLC 1:
WLC 2: