Guest

Preview Tool

Cisco Bug: CSCuq48216 - PI traps not conforming OID structure of CISCO-WIRELESS-NOTIFICATION-MIB

Last Modified

Sep 12, 2019

Products (1)

  • Cisco Prime Infrastructure

Known Affected Releases

2.2(0.0.61)

Description (partial)

Symptom:
The problem is with PI, (Prime Infrastructure) 2.1 and before that.  PI sends traps "Northbound" based upon events determined in PI.  The traps that PI sends are not conforming in their OID structure of CISCO-WIRELESS-NOTIFICATION-MIB

We can forward the alarms as trap, the alarm format is recognized for the notification which are starting with object 1.3.6.1.4.1.9.9.712   (ciscomgmt.712) and we can also see the results but in tool like wireshark we can see the unwanted warnings like "index sub-oid shorter than expected".

Reason is:-

Scalar entries in a MIB should have a .0 appended to their OID to reflect the instance but here in this case .0 was not appended to respective OID of Scalar entries in a MIB.

Example:- Updating the code and adjusting "cWNotificationDescription" to set it to cWNotificationDescription.0 in the varbind of the trap resolves the issue. 

Note -  Strictly speaking this is applicable to all the all the Scalar entries in a MIB which ideally should have a .0 appended to their OID to reflect the instance. Although it may be possible that "Since it's a trap that we send, there are a myriad of ways/applications that a client can consume/parse that trap.  If the client is extracting a varbind by an exact OID match, then adding the .0 would break their code."

Conditions:
We can forward the alarms as trap, the alarm format is recognized for the notification which are starting with object 1.3.6.1.4.1.9.9.712   (ciscomgmt.712) and we can also see the results but in tool like wireshark we can see the unwanted warnings like "index sub-oid shorter than expected".

Reason is:-

Scalar entries in a MIB should have a .0 appended to their OID to reflect the instance but here in this case .0 was not appended to respective OID of Scalar entries in a MIB.

Example:- Updating the code and adjusting "cWNotificationDescription" to set it to cWNotificationDescription.0 in the varbind of the trap resolves the issue. 

Note - This is applicable to all the all the Scalar entries in a MIB which ideally should have a .0 appended to their OID to reflect the instance.
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.