SNMP Agent
8-3
8000-A2-GB21-20
November 1997
Supported Traps
SNMP defines six basic or standard traps. These messages are identified with a
value of 0 through 5 within the generic-trap field of the trap message. (Note that
the HotWire DSLAM SNMP agent does not support trap messages with a value
of 5.) The specific-trap field of standard trap messages is set to 0 (zero). The
specific-trap field of enterprise-specific messages defines the trap.
The HotWire DSLAM SNMP agent supports generation of the following standard
trap messages (specific-trap=0):
coldStart(0). The sending SNMP agent reinitializes itself such that the
agent’s configuration may be altered.
warmstart(1). The sending SNMP agent is reinitialized without altering the
agent’s configuration.
linkDown(2). A link on the sending SNMP agent is no longer operational.
linkUp(3). A link on the sending SNMP agent has become operational.
authenticationFailure(4). The sending SNMP agent has received an SNMP
message specifying a community name which it does not recognize, or
requesting an action not permitted for the specified community.
There are additional HotWire Enterprise supported traps, which can be found in
the Paradyne DSL Enterprise MIBs. See the MIBs for a complete list of traps.
MIBs can be accessed through the Paradyne Power Pages (
www.paradyne.com).
The generation of SNMP trap messages can be selectively enabled per
configured community. Additionally, the authenticationFailure trap can be
selectively enabled for all configured communities that have traps enabled. If any
communities have the generation of trap messages enabled, then the generation
of authenticationFailure traps is determined by the state of the global
authenticationFailure switch.
General SNMP Agent Configuration
Depending on your specific network configuration, various aspects of the HotWire
DSLAM SNMP agent may need to be configured. For example, you may want to
set up your system to send SNMP traps to a specific SNMP NMS manager. The
HotWire DSLAM system provides four default community names (two read/write
community names and two read-only community names) per MCC or DSL card.
These community names are similar to passwords.
Make sure that the SNMP NMS manager that will receive SNMP trap messages
knows and uses the correct community name, as specified on the HotWire
DSLAM. You can change the default community names to match the name of the
SNMP NMS manager. Without the correct community name, the NMS manager
will not be able to communicate with the DSLAM.
