About Traps

	Concepts		Procedures		More Information

A trap is a user-defined process that monitors a specific occurrence on the filer; for example, a trap that monitors the fans on a filer. A trap can be created to check periodically for an operational failure on the filer and, if a failure is detected, cause the SNMP agent to send a message to the traphosts alerting you to the failure.

The filer has a number of built-in traps for your convenience. Check the bottom of the management information base file (netapp.mib) for a list of all the built-in traps before creating a trap that you might not need.

You use traps to inspect the value of MIB variables periodically and to send an SNMP trap to the network management stations on the traphost list whenever that value meets the conditions you specify. The traphost list specifies network management stations that receive trap information.

You can set traps on any numeric variable in the MIB. You use third-party SNMP applications on your network management station to process the trap information.

Best practice: Do not create traps against OIDs in sub-tables. (OIDs that are not in sub-tables end in 0.) The filer does not preserve the ordering of elements in sub-tables over reboots, and occasionally a trap that was supposed to work against one element will work against another after rebooting.

Traps are persistent. After you create and set a trap, it remains across reboots until you specifically remove it or modify it.

For diagnostic and other network management services, the filer supports the SNMP version 1 compatible agent. This agent supports both MIB-II (RFC 1213) and the Network Appliance custom MIB.