Most SNMPv1 messages follow a model where a client (Network Management System) makes a request and a server (agent) responds to that request. Traps are the exception. An SNMP agent will transmit a trap to the NMS when it has a condition to report that is deemed too important to wait until asked. A common example of this is the failure of a communications link.
With most traps, the agent will include something called “‘Interesting’ variable bindings,” which are the OID(s) and value(s)of MIB variable(s) that provide more information about the condition. So, for example, when a communcations channel fails, the agent will send a pSError trap, which will have the OID of the “Link” or “Signal Detect” variable for that channel, and the value “down.”
This table contains Transition enterprise specific traps that are generated only by the Point System product.
|Trap(enterprise trap number)||Description|
|A monitored MIB variable has changed from its ‘operational’ state to its ‘error’ state.|
|A monitored MIB variable has changed from its ‘error’ state to its ‘operational’ state.|
|A new slide-in device (this includes some power supplies) was detected on the bus.|
|A slide-in device that had previously been detected on the bus has not been heard from in a long time, and is presumed to have been physically removed.|
|A slide-in device has indicated that it has rebooted. This is most common when the device is initially powered up, but in some cases this trap indicates a warm start.|
|The cabinet into which this management module is installed has lost power and is running on capacitors. Both the cabinet and the management module must support the Last Gasp feature for this trap to be sent. See also |
|A new cabinet was detected.|
|A cabinet that had previously been detected has not been heard from in a long time, and is presumed to have been physically removed.|
The Point System agent also transmits an industry-standard MIB-2 “coldStart” trap each it reboots.