SNMP Management
60
There are many MIBs in the SNMP realm. Each MIB is defined in a
document called a
Request For Comments
(RFC). The MIB structure is
defined in RFC 1066. Supersets of the MIB are defined in subsequent RFCs.
Some common MIBs are:
❑
MIB I
—This MIB contains a general or core set of variables that are
related to physical network properties such as interface statistics and
IP, TCP and UDP statistics. (RFC 1156)
❑
MIB II
—MIB II supersedes MIB I and contains MIB I variables and
additional variables relating to IP, TCP and UDP statistics for routers
and gateways. (RFC 1213)
❑
REPEATER MIB
—Also known as the Hub MIB; this MIB contains
variables that are specific to managing a repeater or hub, such as
traffic statistics and port management. (RFC 1358)
❑
BRIDGE MIB
—This MIB contains variables that are specific to
managing a Bridge such as Spanning Tree Protocol (STP), link
performance (WAN), link statistics, etc. (RFC 1493)
❑
PRIVATE MIB
—The Private MIB is specific to a particular
vendor’s product. Any special, non-standard variables are included
here. This MIB is provided by the particular vendor.
Other RFCs that apply to AT-3600 Series Repeaters include:
❑
RFC 792—Internet Control Message Protocol (ICMP or PING)
❑
RFC 783—Trivial File Transfer Protocol (TFTP)
❑
RFC 854—Telnet Protocol Specifications
❑
RFC 906—Bootstrap loading using TFTP
❑
RFC 951—Bootstrap Protocol (BootP)
❑
RFC 1084—Bootstrap vendor information extensions
❑
RFC 1157—Simple Network Management Protocol (SNMP)
❑
RFC 1212—Concise MIB Definition (describes ASN.1 mapping)
❑
RFC 1215—SNMP Traps
❑
RFC 1368—Definitions of Managed Objects for IEEE 802.3 Repeater
Devices
AT-3600 Series
Repeaters
AT-3600 Hubs can be managed by an SNMP NMC, provided the NMC
application can manage MIB I or MIB II and the Repeater MIB. If the NMC
only manages MIB II, it cannot perform all the management functions of the
AT-3600 Series Repeaters. A well-designed NMC application enables the user
to import Private MIBs. In this way, the AT-3600 MIB might be imported into
your NMC application. It is not possible to document each vendor’s NMC
application for installing a MIB, but the general procedure is as follows:
1.
Obtain a vendor’s MIB file from the vendor in ASN.1 format.
2.
Compile this file using the utilities provided with the user’s SNMP NMC
application.
3.
Load the newly compiled MIB file into the SNMP NMC application.
4.
Test the new MIB by interrogating the new variables.
Allied Telesyn can provide MIB II and the Repeater MIB for the AT-3600.
Contact Allied Telesyn Technical Support for more information or use the
AT-3600 MIB available in the AT-M0 Manager Kit.