Carrier Access Access Bank II SNMP - Manual (Page 150)

SNMP Management
9/24/01 14-5
• T1 interface statistics, per RFC 1406
14.3.7 Traps
The Access Bank II SNMP agent supports the following standard SNMPv2 defined traps. In the
future, enterprise specific traps will be added. Interpretations of the trap values are:
coldStart Trap
A coldStart(0) trap signifies that the sending protocol entity is reinitializing itself such that the
agent's configuration or the protocol entity implementation may be altered.
warmStart Trap
A warmStart(1) trap signifies that the sending protocol entity is reinitializing itself such that
neither the agent configuration nor the protocol entity implementation is altered.
linkDown Trap
A linkDown(2) trap signifies that the sending protocol entity recognizes a failure in one of the
communication links represented in the agent's configuration. The 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.
linkUp Trap
A linkUp(3) trap signifies that the sending protocol entity recognizes that one of the communi-
cation links represented in the agent's configuration has come up. The 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.
authenticationFailure Trap
An authenticationFailure(4) trap signifies that the sending protocol entity is the addressee of a
protocol message that is not properly authenticated. While implementations of the SNMP must
be capable of generating this trap, they must also be capable of suppressing the emission of such
traps via an implementation-specific mechanism.
egpNeighborLoss Trap
not supported
enterpriseSpecific Trap
A enterpriseSpecific(6) trap signifies that the sending protocol entity recognizes that some
enterprise-specific event has occurred. The specific-trap field identifies the particular trap,
which occurred. (to be implemented in the future)