Preview Tool

Cisco Bug: CSCul34943 - the unusual format of SNMP data was sent by WLC

Last Modified

Jul 01, 2016

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases


Description (partial)

The customer found the following log message from SNMP sever.
  UDP: []:32768->[]
  DISMAN-EVENT-MIB::sysUpTimeInstance 155:20:29:39.00
  CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientMacAddress.0 0:22:cf:94:97:ba
  CISCO-LWAPP-AP-MIB::cLApName.0 tnwap-w601
  CISCO-LWAPP-DOT11-CLIENT-MIB::cldcApMacAddress.0 f0:29:29:eb:aa:0
★CISCO-LWAPP-AP-MIB::cLApDot11IfSlotId.0 Wrong Type (should be Gauge32
  or Unsigned32): 1
  CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientUsername.0 MIC3\012632
  CISCO-LWAPP-DOT11-CLIENT-MIB::cldcClientSSID.0 svwlcWLAN1009

From the following link, 
We can find that the format for object cLApDot11IfSlotId who OID is is "Unsigned32".

However, we find out that the format of cLApDot11IfSlotId change to "integer32" 
in "wireshark" and "Microsoft Network Monitor".

Furthermore, We found the following information from internet.
SMIv2 data type       tag
integer                    0x02
Octet String             0x04
Gauge32                  0x42

According to this information, we know that when packet capture application sees "0x02", it will interpret this object's type into integer.
We consider that is the reason why cLApDot11IfSlotId's type is interpreted into integer not uint32.

H/W : WLC5508
S/W :
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.