Guest

Preview Tool

Cisco Bug: CSCuj96172 - bsnDot11StationAssociate varbinds order is different than whats defined

Last Modified

Jul 01, 2016

Products (1)

  • Cisco 5500 Series Wireless Controllers

Known Affected Releases

7.4(110.0)

Description (partial)

Symptom:
bsnDot11StationAssociate varbinds order is different than whats defined in AIRESPACE-WIRELESS-MIB.

Conditions:
trap received with varbinds in the following order:
{ V2Trap(205) R=92318642
   .1.3.6.1.2.1.1.3.0=211747500 <-- sysUpTime
   .1.3.6.1.6.3.1.1.4.1.0=.1.3.6.1.4.1.14179.2.6.3.53 <--snmpTrapOID
   .1.3.6.1.4.1.14179.2.6.2.35.0=24_b6_57_b4_60_30 <-- bsnStationAPMacAddr
   .1.3.6.1.4.1.14179.2.6.2.36.0=1 <--bsnStationAPIfSlotId
   .1.3.6.1.4.1.14179.2.6.2.34.0=90_72_40_9f_e8_eb <-- bsnStationMacAddress
   .1.3.6.1.4.1.14179.2.6.2.43.0=10.227.145.12 <--bsnUserIpAddress
   .1.3.6.1.4.1.14179.2.2.1.1.3.0="AP1140-6cb147" <--bsnAPName
   .1.3.6.1.4.1.14179.2.6.2.39.0="xxk840" <--bsnStationUserName
   }
}

This is what defined in the MIB:
bsnDot11StationAssociate NOTIFICATION-TYPE
    OBJECTS         {
                        bsnStationAPMacAddr,
                        bsnStationAPIfSlotId,
                        bsnUserIpAddress,
                        bsnStationMacAddress,
                        bsnStationUserName,
                        bsnAPName
                    }

Seems that bsnUserIpAddress, bsnStationMacAddress are in different order, and bsnStationUserName and bsnAPName are in different order
Bug details contain sensitive information and therefore require a Cisco.com 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.