Paradyne 7112 manual Traps enterpriseSpecific, Trap What It Indicates Possible Cause

Standards Compliance for SNMP Traps

Traps: enterpriseSpecific

The enterpriseSpecific trap indicates that an enterprise-specific event has occurred. The Specific-trap field in the Trap PDU identifies the particular trap that occurred. The following table lists the enterprise specific traps supported by the unit:

Trap

What It Indicates

Possible Cause

enterprisePrimaryClockFail	The currently configured
(1)	primary clock source has
	failed.

The T1 network is down.

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.
enterpriseConfigChange(6)	The configuration changed	Configuration has been
	via the user interface or an	changed via the user
	SNMP manager. The trap is	interface or an SNMP
	sent after 60 seconds have	manager.
	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 enterprisePrimaryClockFail, enterpriseDeviceFail, and enterpriseConfigChange. The variable-binding for enterpriseSelfTestFail is devSelfTestResults.

D-4 March 1998 7112-A2-GB20-10