Hello,
Remember, Traps from APs don't get sent to WLSE but directly to your Trap Receiver. WLSE does poll devices using SNMP for various parameters and can send a north bound SNMP Trap to your Trap Receive when it sees a problem (i.e. fault). The format of the trap is defined in CISCO-DEVICE-EXCEPTION-REPORTING-MIB.
I have also found it quite anoying that the MIB does not differentiate the different kinds of traps that WLSE can send. The MIB only has 7 fields. Each field means something different (check the MIB for details). One of which contains the Trap details:
-----------------------
cderExcepData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..1024))
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"More information about the exception that
the reporting service(s) want to convey to
the NMS.
The receiving NMS should understand the
meaning of this object value in order to
use it."
::= { cderExceptionEntry 7 }
------------------------------
A typical trap would look like:
-----------------------------
13 ipv4 10.100.1.10 P1 479610994 FaultId 13DeviceId 227DeviceIP 10.100.1.10DeviceName 10.100.1.10MO RF Port Dot11Radio0Change Broadcast SSID is enabledChangeSeverity P1StateChange BroadcastSSID is ViolatingPolicyAlarmState ActiveOverallSeverity P1DeviceType IOSAccessPoint FaultNotifier@LabWLSE.blah.net
-----------------------------
If you find the 7th field you can tell that this Trap was sent to advise that the Broadcast SSID has been enabled.
What sucks is if you want your Trap Receiver to act on a specific fault within this MIB, it has to be smart enough to parse the different fields and find text relevant to the Trap. We use HPOV as our Trap Receiver and from what I can tell this means a custom script. How I wish they had coded each WLSE Fault with it's own OID then this wouldn't be necessary!!
Serge
