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:
There are no variable-bindings for enterpriseDeviceFail and
enterpriseConfigChange. The variable-binding for enterpriseSelfTestFail
is devSelfTestResults.
8700-A2-GB25-10
SNMP Trap
enterpriseSelfTestFail(2)
enterpriseDeviceFail(3)
enterpriseTestStart(5)
enterpriseConfigChange(6) The configuration changed
enterpriseFallback
AutoRate(13)
enterpriseFallback
AutoRateclear(113)
enterpriseTestStop(105)
February 2001
B. Standards Compliance for SNMP Traps
Description
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.
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.
The LTU, set to AutoRate
enable, resynched at a
lower rate when the line
was restored after an LOS.
The fallback autorate
condition has cleared and
the units have resynched at
the same rate.
All tests have been halted.
Possible Cause
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.
After a LOS condition the
units trained up at a lower
rate than the previous rate.
The units automatically
retrained at the same rate,
were reset, or placed in fixed
rate.
All tests have been halted on
an interface.
B-3