Table 1 lists the generic trap types that can be received by SNMP.
| Value | Type | Description |
|---|---|---|
| 0 | coldStart | A coldStart trap signifies that the sending protocol entity is reinitializing itself so that the agent’s configuration or the protocol entity implementation can be altered. |
| 1 | warmStart | A warmStart trap signifies that the sending protocol entity is reinitializing itself so that neither the agent configuration nor the protocol entity implementation can be altered. |
| 2 | linkDown | A linkDown trap signifies that
the sending protocol entity recognizes a failure in one of the communication
links represented in the agent’s configuration.
A Trap-PDU of type linkDown contains, as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface. |
| 3 | linkUp | A linkUp trap signifies that
the sending protocol entity recognizes that one of the communication
links represented in the agent’s configuration has come up.
A Trap-PDU of type linkUp contains, as the first element of its variable-bindings, the name and value of the ifIndex instance for the affected interface. |
| 4 | authenticationFailure | An authenticationFailure trap signifies that the sending protocol entity is the addressee of a protocol message that is not properly authenticated. |
| 5 | egpNeighborLoss | An egpNeighborLoss trap signifies
that an EGP neighbor for whom the sending protocol entity was an EGP
peer has been marked down and the peer relationship no longer exists.
The Trap-PDU of the egpNeighborLoss contains, as the first element of its variable-bindings, the name and value of the egpNeighAddr instance for the affected neighbor. |
| 6 | enterpriseSpecific | An enterpriseSpecific trap signifies that the sending protocol entity recognizes that some Enterprise-specific event has occurred. The specific-trap field identifies the particular trap that occurred. |