Managing NerveCenter - Managing Management Information Bases (MIBs) - Definitions from other sources -
Definitions Not Compiled into the NerveCenter MIB      Adding or Removing MIB Definitions

Definitions from other sources

You might want to add other MIB definitions to manage devices that are not supported by the MIBs shipped with NerveCenter. You can add MIB definitions from other sources as long as each one:

• Is a complete ASN.1 module definition that conforms to the standards specifications in RFC1902, Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2), RFC1903, Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2), and RFC1904, Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2). You can find these RFCs and others on the Web.

  ---

     Before NerveCenter can compile a mib it must conform to the ASN.1 module definition standard. See the section Troubleshooting ASN.1 files on page 223.

  ---

• Does not have the same name as a MIB definition already compiled into your NerveCenter MIB.

Also, remember that your devices must run SNMP agents from your vendor that support the new MIB definitions.

We recommend that you store additional definitions in the mib\user directory (you can create a user directory in the mibs directory on UNIX). Then, when you install a new version of NerveCenter, you can make a copy of this directory to preserve your additional third-party MIBs.