Snmp Traps - Paradyne 3350 User Manual

SNMP Traps

A trap is an unsolicited message that is sent from the
E1 NTU to an SNMP manager when the device detects
certain, pre-specified conditions. These traps enable the
SNMP manager to monitor the state of the network.
The SNMP Trap configuration option must be enabled
for trap messages to be sent over the communications
link. You must specify the number of SNMP managers
that are to receive traps from this device, an IP address for
each SNMP manager specified, and the type of traps to be
sent from this device. For more information, refer to
Appendix C, Configuration Options, and the Configuring
SNMP Traps section in Chapter 3, Operation.
Trap types consist of the following:
General traps – include warmStart and
authenticationFailure. The device sends a
warmStart trap after it has been reset to indicate
that it has just reinitialized itself. The device sends
an authenticationFailure trap when it has received
an SNMP protocol message that has not been
properly authenticated. These traps are set by the
Gen Trap configuration option.
Enterprise Specific traps – signify that the device
has recognized an enterprise-specific event. See
Table 4-5 for enterprise-specific traps. These traps
are set by the Entp Trap configuration option.
Link Traps – identify the condition of the
communications interface, either linkDown (one of
the communications interfaces has failed) or linkUp
(one of the communications interfaces has just
come up). These traps are set by the Link Trap
configuration option. The communications
interfaces for which these traps can be generated
are specified by the Trap I/F configuration option.
Table 4-6 defines traps for each interface.
3350-A2-GB20-10
Enterprise-Specific Trap Definitions
Trap Value
enterpriseClockFail(1)
enterpriseSelfTestFail(2)
enterpriseDeviceFail(3)
enterpriseSecClockFail(4)
enterpriseTestStart(5)
enterpriseTestClear(105)
SNMP Trap per Interface
Interface
HDSL Network
G.703 DTE
June 1996
Maintenance
Table 4-5
Event
The currently configured
primary clock source has
failed.
A device hardware failure
is detected at self-test.
This trap is generated after
device initialization.
An internal device failure is
detected by the operating
software.
The currently configured
secondary clock source
has failed.
A test is initiated.
A test is concluded.
Table 4-6
Trap Meaning
Up = No alarm or test
conditions.
Down = Alarm or test
conditions.
Up = No alarm or test
conditions, and the
interface is enabled.
Down = Alarm or test
conditions, or the interface
is disabled.
4-11