Paradyne Hotwire 7984 manual Enterprise-Specific Traps

Standards Compliance for SNMP Traps

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:

SNMP Trap	Description	Possible Cause
enterprisePrimary	A failure of the currently	The configured clock source
ClockFail(1)	configured primary clock	is no longer operational. If
	source for the unit has	the configured clock source
	been detected.	is the internal clock, the
		possible cause may be due
		to a failure of one or more of
		the unit's hardware
		components.
enterprisePrimary	Clock failure has cleared.	N/A
ClockFailClear(101)
enterpriseSelfTestFail(2)	A hardware failure of the	Failure of one or more of the
	unit is detected during the	unit's hardware components.
	unit's self-test. The trap is
	generated after the unit
	completes initialization.
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.
enterpriseConfig	The configuration changed	Configuration has been
Change(6)	via the user interface. The	changed via the ATI.
	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.
enterpriseTestStop(105)	All tests have been halted.	All tests have been halted on
		an interface.

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 February 1999 B-3