Upgrading to NerveCenter^TM 3.8 - Upgrading MibComp.txt - New Requirements -
Upgrading MibComp.txt      Upgrading MibComp.txt

New Requirements

The new MIB compiler has two new requirements to compile the MibComp.txt file:

1. If a MIB module depends on information in another MIB module you must reference it before the module that requires the information in mibcomp.txt. That is, if mymibA depends on mymibB, you must include mymibB before mymibA in mibcomp.txt.
2. All SMIv1 compliant MIB modules must be included in mibcomp.txt before the line
   # * * * End of SMIv1 / SNMPv1 MIB Modules * * *
   All SMIv2 compliant MIB modules must be referenced after this line.

Dependencies

If dependant MIB module references are out of order, you receive an error similar to the following:

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:

Now you can name the file that contains this line, in this case rfc1213.asn1, before rfc1573b.asn1.

Finding SMIv2 compliant MIB modules

You can tell the difference between a SMIv1 module and an SMIv2 module by searching the MIB file for "MAX-ACCESS".

Sample SMIv1 SysUpTime definition	Sample SMIv2 SysUpTime definition
sysUpTime OBJECT-TYPE SYNTAX TimeTicks ACCESS read-only STATUS mandatory DESCRIPTION "The time (in hundredths of a second) since the network management portion of the system was last re-initialized." ::= { system 3 }	sysUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The time (in hundredths of a second) since the network management portion of the system was last re-initialized." ::= { system 3 }

Any use of ACCESS within a MIB file named in the SMIv2 area of mibcomp.txt causes an error. Any use of MAX-ACCESS within a MIB file named in the SMIv1 area of mibcomp.txt causes an error.