Understanding traps in Data ONTAP

About traps

Traps are mechanisms that alert you to significant events on the filer. If SNMP is configured, traps are fired when a defined event, such as a network traffic interruption or line power failure, occurs. Trap information, in the form of MIB Object Identifiers (OIDs), is sent from the filer agent to an SNMP management station.

About built-in traps in Network Appliance MIBs

Built-in traps in Network Appliance MIBs are identified by the string TRAP-TYPE. For example, the following is a complete trap definition from the Network Appliance custom MIB:



upsLinePowerOff         TRAP-TYPE

ENTERPRISE              netapp

DESCRIPTION

     "UPS: Input line power has failed and UPS is now on battery."

::= 142

Traps in the Network Appliance custom MIB are provided in a number of categories, including the following:

Category	Examples of trap messages
Disk Health Monitor	Degraded I/O, disk predictive-failure event
Disks	Disk - failure alert, shutdown, repaired
Fan	Fan - failed, shutdown, warning, repaired
Power supply	Power supply - failed, shutdown, warning, repaired
CPU	CPU busy, OK
NVRAM	Battery discharged, low
Cluster	Node failed, repaired
Volumes	Nearly full, full, repaired
Temperature	Over temperature, shutdown, repaired
Shelf	Fault, repaired
Global	Not recoverable, critical, not critical, OK
Soft quotas	Exceeded, normal
Autosupport	Send error, configuration error, successful send

Note
These categories are examples of the MIB trap contents; it is not an exhaustive list. The most complete listings are provided in the MIBs themselves.

About MIB trap priority

By convention, the right-most digit of a trap ID number indicates its priority (degree of severity), using the same enumeration as syslog entries. For example, trap ID 142 upsLinePowerOff is priority 2, alert.

Trap priorities are listed in the following table.

Trap ID last digit	Priority
1	emergency
2	alert
3	critical
4	error
5	warning
6	notification
7	information
8	debug

For more information, see the NetApp syslog.conf(5) manual page.

Where to get further information

See the following RFCs for more information:

RFC 1157--Defines and describes SNMP.
RFC 1213--Defines and describes the SNMP MIB-II specification.
RFC 1155--Defines and describes the structure and identification of management information for TCP/IP-based internets.
RFC 1215--Defines the convention for defining traps for use with SNMP.
RFC 1212--Gives concise MIB definitions.