Paradyne 8779, U8777 manual Enterprise-Specific Traps

B. Standards Compliance for SNMP Traps

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
enterprisePrimaryClock	he unit has lost its primary		Hardware failure in the unit
Fail(1)	clock source.		or the clock source.
	No variable bindings.
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.
	VariableT	bindings:
	devSelfTestResults
enterpriseDeviceFail(3)	An internal device failure.		Operating software has
	No variable bindings.		detected an internal device
			failure.
enterpriseSecondaryClock	he unit has lost its		Hardware failure in the unit
Fail(4)	secondary clock source.		or the clock source.
	No variable bindings.
enterpriseTestStart(5)	A test is running.		At least one test has been
	Variable bindings:		started on an interface.
	devSelfTestResults
	ifIndex (RFC 2863)
	ifAdminStatus
	(RFC 2863)
	ifOperStatus (RFC 2863)
	TifType (RFC 2863)
	ifTestType (RFC 2863)
enterpriseConfigChange(6)	The configuration changed		Configuration has been
	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.
	No variable bindings.

B-4 May 2002 8700-A2-GB20-40