User's Manual Part 1

05-4446A01, Rev. D Mercury Reference Manual 57
• Bridge Forward Delay—View/set spanning tree forwarding delay.
Affects how long the bridge spends listening and learning after
initialization. [
4-30 seconds; 5 seconds].
3.4.4 SNMP Agent Configuration
The transceiver contains over 100 custom SNMP-manageable objects as
well as the IETF standard RFC1213 for protocol statistics, also known
as MIB II. You can use off-the-shelf SNMP managers to access the
transceiver’s SNMP Agent’s MIB, such as Castle Rock Computing
SNMPc™ and Hewlett Packard OpenView™. The transceiver’s SNMP
agent supports SNMPv1, v2, and v3.
The objects are split into nine MIB files for use with your SNMP man-
ager. There are textual conventions, common files, and specific files.
This allows the flexibility to change areas of the MIB and not affect
other existing installations or customers.
•
msdreg.mib—MDS sub-tree registrations
• mds_comm.mib—MDS Common MIB definitions for objects
and events common to the entire product family
• mercury_reg.mib—MDS sub-tree registrations
• mercurytrv1.mib—SNMPv1 enterprise-specific traps
• mercurytrv2.mib—SNMPv2 enterprise-specific traps
• mercury_comm.mib— MIB definitions for objects and events
common to the entire Mercury Series
• mercury_ap.mib—MIB definitions for objects and events for an
Access Point transceiver
• mercury_rem.mib—Definitions for objects and events for a
Remote radio
• mercury_sec.mib—For security management of the radio system
NOTE: SNMP management requires that the proper IP address,
network, and gateway addresses are configured in each associ-
ated network transceiver.
In addition, some management systems might require that you
compile the MIB files in the order shown above.