User`s guide

SNMP Agent
8-3
8000-A2-GB21-10
June 1997
 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 supported traps, which can be found in the Paradyne DSL
Enterprise MIBs. See the MIBs for a complete list of traps.
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. In
other words, each community can give all trap messages (either enabled or
disabled). 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.
As a minimum configuration, you must do the following on the SNMP
Communities/Traps screen:
 Assign an SNMP NMS manager to a community by specifying the SNMP
NMS manager’s IP address to a specific community name. (Ensure that the
SNMP NMS manager uses the same community name configured in the
HotWire DSLAM.) You can specify up to three SNMP NMS managers for
each community name.
 Configure the generation of trap messages.
 Enable/Disable the generation of authenticationFailure trap messages.
Additionally, you can configure logical entities. Logical entities can be used to
provide various management populations with different levels of management
access to the HotWire DSLAM SNMP agent. These configurations provide a
system-wide view of the SNMP agent. Use the Configure SNMP Logical Entity
Table screens to configure access logical entities.
For detailed information about the various SNMP Agent screens mentioned in this
chapter, see Chapters 5 and 6 of the
HotWire Digital Subscriber Line Access
Multiplexer (DSLAM) User’s Guide
. Also Appendix C, SNMP Configuration
Worksheets
, provides worksheets to help you plan and record your SNMP
configurations.