Enterprise-Specific Traps - Paradyne HOTWIREt 7984 User Manual

Enterprise-Specific Traps

EnterpriseSpecific traps 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:
There are no variable-bindings for enterpriseDeviceFail, enterprisePrimary
ClockFail, enterpriseSecondaryClockFail, enterprisePrimaryClockFailClear,
enterpriseSecondaryClockFailClear, and enterpriseConfigChange. The
variable-binding for enterpriseSelfTestFail is devSelfTestResults.
7984-A2-GB20-10
SNMP Trap
enterprisePrimary
ClockFail(1)
enterprisePrimary
ClockFailClear(101)
enterpriseSelfTestFail(2)
enterpriseDeviceFail(3)
enterpriseTestStart(5)
enterpriseConfig
Change(6)
enterpriseTestStop(105)
February 1999
Standards Compliance for SNMP Traps
Description
A failure of the currently
configured primary clock
source for the unit has
been detected.
Clock failure has cleared.
A hardware failure of the
unit is detected during the
unit's self-test. The trap is
generated after the unit
completes initialization.
An internal device failure.
A test is running.
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.
All tests have been halted.
Possible Cause
The configured clock source
is no longer operational. If
the configured clock source
is the internal clock, the
possible cause may be due
to a failure of one or more of
the unit's hardware
components.
N/A
Failure of one or more of the
unit's hardware components.
Operating software has
detected an internal device
failure.
At least one test has been
started on an interface.
Configuration has been
changed via the ATI.
All tests have been halted on
an interface.
B-3