CISCO-LWAPP-AP-MIB :: ciscoLwappApCrash

MIB Reference — IPNetwork Monitor

All MIBsCISCO-LWAPP-AP-MIBciscoLwappApCrash

ciscoLwappApCrash

Module: CISCO-LWAPP-AP-MIB

OID (symbolic): CISCO-LWAPP-AP-MIB::ciscoLwappApCrash

OID (numeric): 1.3.6.1.4.1.9.9.513.0.2

Node type: NOTIFICATION-TYPE

Description:

This notification is generated after an AP rejoins the controller after a crash. Once the AP joins, the controller will get the crash file from the AP and sends this notification.

What is ciscoLwappApCrash?

This OID triggers a system notification sent when a wireless access point unexpectedly restarts after a crash. The notification alerts operators that the AP rejoined the network and diagnostic crash logs are available. A wireless technician uses this alert to identify problematic access points and retrieve crash logs for root-cause analysis.

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' CISCO-LWAPP-AP-MIB::ciscoLwappApCrash
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.9.9.513.0.2

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:59697->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (469712689) 54 days, 8:45:26.89
  SNMPv2-MIB::snmpTrapOID.0 = OID: CISCO-LWAPP-AP-MIB::ciscoLwappApCrash

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.4privateBIANCA-BRICK-PPP-MIB
1.3.6.1.4.1enterprisesANIROOT-MIB
1.3.6.1.4.1.9ciscoCISCO-SMI
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
1.3.6.1.4.1.9.9.513ciscoLwappApMIBCISCO-LWAPP-AP-MIB
1.3.6.1.4.1.9.9.513.0ciscoLwappApMIBNotifsCISCO-LWAPP-AP-MIB
1.3.6.1.4.1.9.9.513.0.2ciscoLwappApCrashCISCO-LWAPP-AP-MIB