We have two WLC5520's configured in a HA redundancy pair (connected via RP). On the primary and secondary controllers it appears redundancy is working correctly via the following commands:
Primary:
(WLC-SE-1) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = ACTIVE
Peer State = STANDBY HOT
Unit = Primary
Unit ID = 00:C8:8B:99:F8:13
Redundancy State = SSO
Mobility MAC = 00:C8:8B:99:F8:13
BulkSync Status = Complete
Average Redundancy Peer Reachability Latency = 161 Micro Seconds
Average Management Gateway Reachability Latency = 426 Micro Seconds
Secondary:
(WLC-SE-1-Standby) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = STANDBY HOT
Peer State = ACTIVE
Unit = Secondary (Inherited AP License Count = 100)
Unit ID = 00:C8:8B:9A:23:99
Redundancy State = SSO
Mobility MAC = 00:C8:8B:99:F8:13
Average Redundancy Peer Reachability Latency = 166 Micro Seconds
Average Management Gateway Reachability Latency = 345 Micro Seconds
Additionally, On the secondary controller, I see both the AP tables populating correctly from the primary:
Primary:
(WLC-SE-1) >show ap summary
Number of APs.................................... 2
Global AP User Name.............................. admin
Global AP Dot1x User Name........................ Not Configured
AP Name Slots AP Model Ethernet MAC Location Country IP Address Clients DSE Location
------------------ ----- -------------------- ----------------- ------------ ---- ---------- --------------- -------- --------------
wap-regstcvn1 3 AIR-CAP3702I-A-K9 00:78:88:61:1c:64 Regina Stora ge C CA 10.30.0.253 2 [0 ,0 ,0 ]
wap-psc1 3 AIR-CAP3702I-A-K9 00:42:68:11:2a:d8 PSC CA 10.3.0.253 0 [0 ,0 ,0 ]
Secondary:
(WLC-SE-1-Standby) >show ap summary
Number of APs.................................... 2
Global AP User Name.............................. admin
Global AP Dot1x User Name........................ Not Configured
AP Name Slots AP Model Ethernet MAC Location Country IP Address Clients DSE Location
------------------ ----- -------------------- ----------------- ---------------- ---------- --------------- -------- --------------
wap-regstcvn1 3 AIR-CAP3702I-A-K9 00:78:88:61:1c:64 Regina Storage C CA 10.30.0.253 2 [0 ,0 ,0 ]
wap-psc1 3 AIR-CAP3702I-A-K9 00:42:68:11:2a:d8 PSC CA 10.3.0.253 0 [0 ,0 ,0 ]
However, it appears when it comes to clients some are not populated to the secondary:
Primary:
(WLC-SE-1) >show client summary
Number of Clients................................ 2
Number of PMIPV6 Clients......................... 0
Number of EoGRE Clients.......................... 0
GLAN/
RLAN/
MAC Address AP Name Slot Status WLAN Auth Protocol Port Wired Tunnel Role
----------------- ----------------- ---- ------------- ----- ---- ---------------- ---- ----- ------- ----------------
4c:34:88:ae:3f:99 wap-regstcvn1 0 Associated 1 Yes 802.11n(2.4 GHz) 8 No No Local
64:bc:0c:2e:be:7e wap-regstcvn1 1 Associated 2 No 802.11ac(5 GHz) 8 No No Local
Secondary:
(WLC-SE-1-Standby) >show client summary
Number of Clients................................ 2
Number of PMIPV6 Clients......................... 0
Number of EoGRE Clients.......................... 0
GLAN/
RLAN/
MAC Address AP Name Slot Status WLAN Auth Protocol Port Wired Tunnel Role
----------------- ----------------- ---- ------------- ----- ---- ---------------- ---- ----- ------- ----------------
4c:34:88:ae:3f:99 wap-regstcvn1 0 Associated 1 Yes 802.11n(2.4 GHz) 8 No No Local
Also, according to the documentation, the Redundancy State should state AP and Client SSO however it does not (only states SSO). A larger issue though is that when I use the command "redundancy force-switchover" on the primary I see the following behavior.
- Controller WebUI is no longer accessible (even though the Management IP is pingable)
- AP summary table is cleared on standby and AP's do not failover.
- Client table is cleared on standby and client's do not failover.
Essentially, the system is down until I issue the "redundancy force-switchover again on the secondary. Once that is issued, AP's associate to the primary controller correctly and clients can connect. Obviously this is a big issue as in the event of actual hardware failure of the primary.
Anyone have any thoughts as to why this would be happening even though it appears all is setup correctly? Both controllers are running code 8.2.100.0.
