Enterprise-Specific Traps - Paradyne 7974 User Manual

Enterprise-Specific Traps

The enterpriseSpecific trap indicates that an enterprise-specific event has
occurred. The Specific-trap field identifies the particular trap that occurred.
The following table lists the enterprise-specific traps supported by the unit:
7900-A2-GB21-20
SNMP Trap Description
enterprisePrimary- The unit has lost its primary
ClockFail(1) clock source.
No variable bindings.
enterpriseSelfTest- A hardware failure of the unit
Fail(2) is detected during the unit's
self-test. The trap is
generated after the unit
completes initialization.
Variable bindings:
T
enterpriseDevice- An internal device failure.
Fail(3)
No variable bindings.
enterpriseSecondary- The unit has lost its
ClockFail(4) secondary clock source.
No variable bindings.
enterpriseTestStart(5) A test is running.
Variable bindings:
T
T
T
T
T
T
enterpriseConfig- The configuration changed
Change(6) 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.
December 2001
B. Standards Compliance for SNMP Traps
devSelfTestResults
devSelfTestResults
ifIndex (RFC 1573)
ifAdminStatus
(RFC 1573)
ifOperStatus (RFC 1573)
ifType (RFC 1573)
ifTestType (RFC 1573)
Possible Cause
Hardware failure in the unit or
the clock source.
Failure of one or more of the
unit's hardware components.
Operating software has
detected an internal device
failure.
Hardware failure in the unit or
the clock source.
At least one test has been
started on an interface.
Configuration has been
changed via the ATI.
B-5