Event variable discriminator breaks clear event trap functionality.

Products

• Network Observability
• Spectrum

Issue/Introduction

When you add an event variable discriminator to a trap event for AP disassociation from the WLC, it works to create unique events and alarms for each AP.  However  when we add the same discriminator to the Clear event, it is not working and does not clear anything.  Removing the event variable discriminator, the trap will clear all of these alarms for all APs on the WLC, so  the trap  and even are working but the event variable discriminator breaks it.

Cause

The trap used to create the alarms is in the AIRESPACE-WIRELESS-MIB and clear trap was not the supported one but instead one form the CISCO_LWAPP_APP-MIB with different attributes and order of varbinds. 

 

bsnAPDisassociated NOTIFICATION-TYPE

VARIABLES {

   bsnAPMacAddrTrapVariable       1.3.6.1.4.1.14179.2.6.2.20     MacAddress                     

   bsnAPName                      1.3.6.1.4.1.14179.2.2.1.1.3    OCTET STRING                   

}

DESCRIPTION

"When Airespace AP disassociates from Airespace Switch, AP disassociated notification will be sent with dot3 MAC address of Airespace AP management system to remove Airespace AP from this Airespace Switch"

-- 1.3.6.1.4.1.14179.2.6.3.6.8

 

• the alertMap shows

 

# bsnAPDisassociated                                     # bsnAPMacAddrTrapVariable

1.3.6.1.4.1.14179.2.6.3.6.8                0x04b60007    1.3.6.1.4.1.14179.2.6.2.20(1,0)\

                                                         # bsnAPName

                                                         1.3.6.1.4.1.14179.2.2.1.1.3(2,0)

 

• The supported clear event for this is 0x04b60006 as seen in the EventDisp

 

./Airespace/EventDisp:0x04b60006 E 50 C 0x04b60007, 1

 

 

bsnAPAssociated NOTIFICATION-TYPE

VARIABLES {

   bsnAPMacAddrTrapVariable       1.3.6.1.4.1.14179.2.6.2.20     MacAddress                     

   bsnAPPortNumberTrapVariable    1.3.6.1.4.1.14179.2.6.2.32     Integer32                      

   bsnAPName                      1.3.6.1.4.1.14179.2.2.1.1.3    OCTET STRING                   

}

DESCRIPTION

"When Airespace AP Associates to a Airespace Switch, AP associated notification will be sent with dot3 MAC address of Airespace AP.This will help management system to discover Airespace AP and add to system."

-- 1.3.6.1.4.1.14179.2.6.3.6.7

 

 

• configured in the AlertMap as

 

# bsnAPAssociated                                        # bsnAPMacAddrTrapVariable

1.3.6.1.4.1.14179.2.6.3.6.7                0x04b60006    1.3.6.1.4.1.14179.2.6.2.20(1,0)\

                                                         # bsnAPPortNumberTrapVariable

                                                         1.3.6.1.4.1.14179.2.6.2.32(2,0)\

                                                         # bsnAPName

                                                         1.3.6.1.4.1.14179.2.2.1.1.3(3,0)

 

 

• Looking on the APs this clear alarm is not being received and not used in the EventDisp. 

 

1.3.6.1.4.1.9.9.513.1.1.1.1.5(1,2) AP name

Cisco_Router/Cisco_LWAPP_App/AlertMap:1.3.6.1.4.1.14179.2.6.3.6.8                0x04b60007    1.3.6.1.4.1.14179.2.6.2.20(1,0)\

 

 

 

1.3.6.1.4.1.9.9.513.0.4      0x00210e0c 1.3.6.1.4.1.9.9.513.1.1.1.1.5(2,2)\

                                        # cLApLastRebootReason

                                        1.3.6.1.4.1.9.9.513.1.1.1.1.16(3,0)\

                                        # cLApDataEncryptionStatus

                                        1.3.6.1.4.1.9.9.513.1.1.1.1.36(4,0)

 

Resolution

The device owner should turn on the supported trap on the device and not use a trap from a different mib with different attributes and oids.  We were able to work around it by changing the event variable discriminator of the clear event from 2 to 1.