User`s guide

B. Standards Compliance for SNMP Traps
7990-A2-GB20-00 May 2002
B-5
Enterprise-Specific Traps
The enterpriseSpecific trap indicates that an enterprise-specific event has
occurred. The Specific-trap field identifies the particular trap that occurred.
Table B-5, Enterprise-Specific Traps, lists the enterprise-specific traps supported
by the unit.
Table B-5. Enterprise-Specific Traps (1 of 2)
SNMP Trap Description Possible Cause
enterprisePrimary-
ClockFail(1)
The unit has lost its primary
clock source.
No variable bindings.
Hardware failure in the unit or
the clock source.
enterpriseSelfTest-
Fail(2)
A hardware failure of the unit
is detected during the unit’s
self-test. The trap is
generated after the unit
completes initialization.
Variable bindings:
devSelfTestResults
Failure of one or more of the
unit’s hardware components.
enterpriseDevice-
Fail(3)
An internal device failure.
No variable bindings.
Operating software has
detected an internal device
failure.
enterpriseSecondary-
ClockFail(4)
The unit has lost its
secondary clock source.
No variable bindings.
Hardware failure in the unit or
the clock source.
enterpriseTestStart(5) A test is running.
Variable bindings:
devSelfTestResults
ifIndex (RFC 2863)
ifAdminStatus
(RFC 2863)
ifOperStatus (RFC 2863)
ifType (RFC 1573)
ifTestType (RFC 2863)
At least one test has been
started on an interface.
enterpriseConfig-
Change(6)
The configuration changed
via the user interface. The
trap is sent after
60 seconds have elapsed
without another change. This
suppresses the sending of
numerous traps when
multiple changes are made in
a short period of time, as is
typically the case when
changing configuration
options.
No variable bindings.
Configuration has been
changed via the ATI.