Users Manual

As it turns out from this list, there is a one-to-one relationship between events triggering
traps and their notification identifiers. But the trap identifier does not tell whether the
event was to trigger the alarm state or to cancel it. That is the purpose of the severity
identification number in the trap message. The following table lists the severity numbers
used:
SNMP Trap status binding
Severity
Description
StatusID
Trap status
binding
Binding string
CRITICAL
System malfunction comes into effect
1
3
fail
WARNING
System warning comes into effect.
4
2
warning
CLEARED
System malfunction or warning is
canceled.
5
1
ok
UNAVAILABLE
System state cannot be determined
6
99
unavailable
The character string attached to each trap message includes both a short event
description plus a severity description such as “OK” or “FAIL”. As an example, the
following picture shows a snapshot of a trap receiver getting traps from a unit at address
172.18.21.10. The time-stamp shows time since system boot and SNMP Version is '1'.
The severity is set to 'warning'.
SNMP Trap in trap receiver
Example trap capture