Filter
Top Products
Standards Compliance for SNMP Traps
B-5
8700-A2-GB20-00
April 2000
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
enterprisePrimaryClockFail
(1)
The unit has lost its primary
clock source.
No variable bindings.
Hardware failure in the unit
or the clock source.
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.
Variable bindings:
H devSelfTestResults
Failure of one or more of the
unit’s hardware components.
enterpriseDeviceFail(3) An internal device failure.
No variable bindings.
Operating software has
detected an internal device
failure.
enterpriseSecondaryClock
Fail(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:
H devSelfTestResults
H ifIndex (RFC 1573)
H ifAdminStatus
(RFC 1573)
H ifOperStatus (RFC 1573)
H ifType (RFC 1573)
H ifTestType (RFC 1573)
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.
No variable bindings.
Configuration has been
changed via the ATI.