Symptom

When the WLC lost its peer, the SNMP walk returned the incorrect value; after the lost WLC came back, the returned value would become normal. The issue could be reproduced in my lab. WLC 5520 SW 8.5.135.0 WLC SSO enabled SNMPwalk PI 3.3 (Controller) >show redundancy summary Redundancy Mode = SSO ENABLED Local State = ACTIVE Peer State = UNKNOWN - Communication Down Unit = Secondary (Inherited AP License Count = 1500) Unit ID = B4:DE:31:75:9B:A5 Redundancy State = Non Redundant Mobility MAC = B4:DE:31:75:C3:29 Redundancy Port = UP BulkSync Status = Pending -bash-4.1# snmpwalk -v2c -c test1 10.124.40.58 1.3.6.1.4.1.9.9.176 SNMPv2-SMI::enterprises.9.9.176.1.1.1.0 = INTEGER: 1445493770 SNMPv2-SMI::enterprises.9.9.176.1.1.2.0 = INTEGER: 14 SNMPv2-SMI::enterprises.9.9.176.1.1.3.0 = INTEGER: 0 SNMPv2-SMI::enterprises.9.9.176.1.1.4.0 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.176.1.1.5.0 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.176.1.1.6.0 = INTEGER: 2 SNMPv2-SMI::enterprises.9.9.176.1.1.7.0 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.176.1.1.8.0 = INTEGER: 1 SNMPv2-SMI::enterprises.9.9.176.1.1.9.0 = Timeticks: (9475) 0:01:34.75 SNMPv2-SMI::enterprises.9.9.176.1.1.10.0 = Timeticks: (0) 0:00:00.00 SNMPv2-SMI::enterprises.9.9.176.1.2.14.0 = INTEGER: 8 SNMPv2-SMI::enterprises.9.9.176.1.2.15.0 = STRING: "SSO" SNMPv2-SMI::enterprises.9.9.176.1.2.16.0 = INTEGER: 8 SNMPv2-SMI::enterprises.9.9.176.1.3.1.0 = Gauge32: 0 SNMPv2-SMI::enterprises.9.9.176.1.3.3.0 = Counter32: 0 SNMPv2-SMI::enterprises.9.9.176.1.3.4.0 = INTEGER: 1379616 OID 1.3.6.1.4.1.9.9.176.1.1.4 Object cRFStatusPeerUnitState RFState 1:notKnown 2:disabled 3:initialization 4:negotiation 5:standbyCold 6:standbyColdConfig 7:standbyColdFileSys 8:standbyColdBulk 9:standbyHot 10:activeFast 11:activeDrain 12:activePreconfig 13:activePostconfig 14:active 15:activeExtraload 16:activeHandback OID 1.3.6.1.4.1.9.9.176.1.2.14 Object cRFCfgRedundancyMode MIB same as above RFMode 1:nonRedundant 2:staticLoadShareNonRedundant 3:dynamicLoadShareNonRedundant 4:staticLoadShareRedundant 5:dynamicLoadShareRedundant 6:coldStandbyRedundant 7:warmStandbyRedundant 8:hotStandbyRedundant

Conditions

when the WLC lost its peer, the return value are incorrect. The issue would disappear after the lost WLC came back.

Workaround

n/a

Further Problem Description