User`s guide

6-2
Traps
for one of the debugging attributes; those PDUs must always
provide the
configAnyPass.
• egpNeighborLoss (5) – Not used by the ATX.
• enterpriseSpecific (6) – The ATX is reporting some
interesting information, which is contained in the variable-
bindings portion of the PDU. If the ATX has been configured to
require acknowledgments to its Trap PDUs (
sysTrapAck), then
the SNMP Manager must acknowledge the trap, generally by
issuing a GetRequest for the significant variables involved in
generating the trap.
All enterprise specific traps specify the value of sysObjectID.0,
the object identifier sysID, as the enterprise, and zero as the
specific-trap. The variable-bindings may contain many pairs of
variable names and their values.
Note: These traps are only sent if ConfigAlarmDynamic is set.
The ATX can generate enterprise specific traps in either an
Acknowledge or a Non-Acknowledge mode. In the Non-
Acknowledge mode, a single trap PDU will be sent to the SNMP
Manager. This PDU will contain sufficient information for the
SNMP Manager to determine the cause of the trap in Acknowledge
mode. The ATX resends the PDU occasionally (see sysTrapTime
and sysTrapRetry in the ATX MIB Reference Guide) until it
receives an Acknowledgment from the SNMP Manager. The
Acknowledgment is defined to be a GetRequest for the variables
associated with the Trap's cause. Note that Acknowledge mode is
only applicable for enterprise specific traps; that is, only enterprise
specific traps may be resent.
Many traps include other variable bindings, in addition to the
variable binding which caused the trap to be generated. The
additional variable bindings are not guaranteed to be present,
and/or may be passed in separate trap PDUs.