Managing NerveCenter
-
Managing Management Information Bases (MIBs) - Adding or Removing MIB Definitions -
The MIB compiler (mibcomp) compiles the MIB definitions referenced in a text file. You can add references to or remove them from this file to control what definitions are compiled into the NerveCenter MIB.
Add MIB definitions if you want to monitor additional devices. Remove MIB definitions if you are no longer monitoring the devices supported by those definitions. (Removing the definitions is not required; however, the NerveCenter MIB will be smaller, which can improve client performance and will make managing the MIB easier.)
If you are using NerveCenter with a network management platform and both applications are monitoring the same agents, make sure both applications are using the correct MIBs for those agents.
See Sources of MIB Definitions for a list of MIB definitions that are shipped with NerveCenter and what standards MIB definitions are not shipped with NerveCenter must follow.
nervectr38.mib and mibcomp38.txt
. These are copies of the default nervectr.mib
and mibcomp.txt
in case you need to revert to an unchanged MIB definitions.The MIB compiler (mibcomp) compiles the MIB definitions referenced in a text file. You can add references to this file to control what definitions are compiled into the NerveCenter MIB.
If dependant MIB module references are out of order, you recieve an error similar to the following:
8: standard-v2/rfc1573b.asn1 mgrtool.exe: process_data(), Couldn't
find parent: interfaces
mibcomp: unable to compile and resolve standard-v2/rfc1573b.asn1
In this example, rfc1573b.asn1 depends upon another mib to define interfaces. You must find the mib that defines interfaces and include it before rfc1573b.asn1 in mibcomp.txt. To find a MIB that defines interfaces, you search the other MIB modules looking for the following:
interfaces OBJECT IDENTIFIER ::= { mib-2 2 }
Now you can name the file that contains this line, in this case rfc1213.asn1, before rfc1573b.asn1.
You can tell the difference between a SMIv1 module and an SMIv2 module by searching the *.asn1 file for "MAX-ACCESS.
Any use of ACCESS within a *.asn1 named in the SMIv2 area of mibcomp.txt causes an error. Any use of MAX-ACCESS within a *.asn1 named in the SMIv1 area of mibcomp.txt causes an error.
To modify the mibcomp text file:
mibcomp.txt
or nervectr.mib
, make back-up copies of them in case you want to recover your changes.
You have updated the file that includes references to the MIB definitions you need. Now, you must compile the NerveCenter MIB using the file you just created. See Compiling the NerveCenter MIB.
Definitions from other sources | Compiling the NerveCenter MIB |
29 July 2003 |