All MIBs › BLACKBERRYSERVER-MIB › besCriticalEvent
besCriticalEvent
Module: BLACKBERRYSERVER-MIB
OID (symbolic): BLACKBERRYSERVER-MIB::besCriticalEvent
OID (numeric): 1.3.6.1.4.1.3530.5.0.21
Node type: NOTIFICATION-TYPE
Description: Critical event has happened. These are the events normally logged with 1xxxx and 5xxxx event IDs.
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> '' BLACKBERRYSERVER-MIB::besCriticalEvent snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.3530.5.0.21
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]:55565->[192.168.30.10]:162]: DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (186284301) 21 days, 13:27:23.01 SNMPv2-MIB::snmpTrapOID.0 = OID: BLACKBERRYSERVER-MIB::besCriticalEvent
Start monitoring Windows servers running BlackBerry Enterprise Server (BES) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the BLACKBERRYSERVER-MIB::besCriticalEvent OID value, configure state conditions and alerts, and monitor any Windows servers running BlackBerry Enterprise Server (BES) from a single console.
OID Breakdown
Upper-level ancestors (6 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.3530 | rim | BLACKBERRYSERVER-MIB |
| 1.3.6.1.4.1.3530.5 | blackBerryServer | BLACKBERRYSERVER-MIB |
| 1.3.6.1.4.1.3530.5.0.21 | besCriticalEvent | BLACKBERRYSERVER-MIB |