B. Standards Compliance for SNMP Traps
8776-A2-GB20-40
February 2001
B-3
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:
SNMP Trap
Description
Possible Cause
enterprisePrimary
ClockFail(1)
A failure of the currently
configured primary clock
source for the unit has been
detected.
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.
enterprisePrimary
ClockFailClear(101)
The Clock Fail condition has
cleared.
—
enterpriseSelfTestFail(2)
A hardware failure of the
unit is detected during the
unit’s self-test. The trap is
generated after the unit
completes initialization.
Failure of one or more of the
unit’s hardware components.
enterpriseDeviceFail(3)
An internal device failure.
Operating software has
detected an internal device
failure.
enterpriseTestStart(5)
A test is running.
At least one test has been
started on an interface.
enterpriseConfigChange(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.
Configuration has been
changed via the ATI.
enterpriseFallback
AutoRate(13)
The LTU, set to AutoRate
enable, resynched at a
lower rate when the line
was restored after an LOS.
After a LOS condition the
units trained up at a lower
rate than the previous rate.
enterpriseFallback
AutoRateClear(113)
The fallback autorate
condition has cleared and
the units have resynched at
the same rate.
The units automatically
retrained at the same rate,
were reset, or placed in fixed
rate.
enterpriseTestStop(105)
All tests have been halted.
All tests have been halted on
an interface.
Summary of Contents for Hotwire 8776
Page 24: ...2 Using the Asynchronous Terminal Interface 2 10 February 2001 8776 A2 GB20 40...
Page 52: ...4 Monitoring the Unit 4 16 February 2001 8776 A2 GB20 40...
Page 62: ...5 Testing 5 10 February 2001 8776 A2 GB20 40...
Page 68: ...6 Messages and Troubleshooting 6 6 February 2001 8776 A2 GB20 40...
Page 98: ...B Standards Compliance for SNMP Traps B 6 February 2001 8776 A2 GB20 40...
Page 102: ...D Technical Specifications D 2 February 2001 8776 A2 GB20 40...
