Brocade Virtual ADX MIB Reference (Supporting ADX v03.1.00) - Manual (Page 14)

2 Brocade Virtual ADX MIB Reference
53-1003312-01
Standard objects
Downloading the MIB from Brocade FTP site
You can also download the MIB from the Knowledge Portal. Contact Brocade Technical Support for
details. For the latest edition of this document, which contains the most up-to-date information, see
the Product Manuals tab at
https:/kp.foundrynet.com .
Importing MIB into a UNIX environment
You can import the MIB into third-party Network Management Applications, such as HP OpenView.
By default, the MIB files are in DOS ASCII format that uses the following characters:
• CR/LF – Indicates the end of a line
• ^Z - Indicates the end of a file
However, in a UNIX environment, the characters LF are used to indicate the end of a line. No
character indicates the end of a file. Therefore, if you need to import the MIB into a UNIX
environment, you must use a tool that converts the DOS ASCII into UNIX ASCII, such as the
dos2unix tool.
Reloading MIBs into a third-party NMS
Third-part network management system may have problems reloading MIB files. When reloading
the MIBs into third-party Network Management Applications such as HP OpenView, you must:
• Unload the Enterprise MIBs which were installed from the previous upgrade before reloading
any new Enterprise MIB file.
• Unload the Standard MIBs which were installed from the previous upgrade before reloading
any new Standard MIB file.
Standard objects
The ADP MIB supports certain standard MIB objects, which are derived from Request for
Comments (RFCs) documents. Refer to
“Supported Standard MIBs” on page 5 for details on the
supported standard MIBs.
Proprietary objects
Proprietary objects are MIB objects that have been developed specifically to manage ServerIron
ADX and Virtual ADX products. These objects may also be referred to as the private (or enterprise)
MIBs.
In this guide, the MIB objects are presented with their object names and their object identifiers
(OIDs). OIDs are presented in the format brcdIp.x.x.x.x, where:
• “brcdIp” represents the number 1.3.6.1.4.1.1991
• .x.x.x.x is the remainder of the number
For example, the OID for the object snChassis is 1.3.6.1.4.1.1991.1.1.1, but appears as
brcdIp.1.1.1 in this guide.