User`s guide

SNMP Agent
8-2
8000-A2-GB21-10
June 1997
The HotWire DSLAM supports the following MIBs:
 MIB II — System Group (described in RFC 1213)
 MIB II — ICMP Group (described in RFC 1213)
 MIB II — UDP Group (described in RFC 1213)
 MIB II — Transmission Group (described in RFC 1213)
 MIB II — SNMP Group (described in RFC 1213)
 MIB II — Definitions of Managed Objects for the Ethernet-like Interface Types
(described in RFC 1398)
 MIB II — Definitions of Managed Objects for the Link Control Protocol of the
Point-to-Point Protocol (described in RFC 1471)
 MIB II — Definitions of Managed Objects for the IP Network Control Protocol
of the Point-to-Point Protocol (described in RFC 1473)
 MIB II — Evolution of Interfaces Group (described in RFC 1573)
 MIB II — Ethernet Interface MIB (described in RFC 1643)
 Entity MIB (described in RFC 2037)
 Paradyne DSL Enterprise MIBs:
— HotWire System MIB (hot_sys.mib)
— HotWire xDSL MIB (hot_xdsl.mib)
— Security MIB (devSecurity.mib)
— Device Health and Status MIB (devHealthAndStatus.mib)
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.