MIB Compiler error messages

1

Unresolved OID

Explanation:
While compiling some MIBs, the compiler is unable to resolve the object identifier (OID) of an MIB node. The referenced MIB node is not imported from the MIB that defines that node.

User Response:
Determine the MIB where the unresolved MIB node is defined. Include a line in the IMPORTS statement of the faulty MIB to import the MIB node from the original MIB. Alternatiively, identify the OID value of the reference node in the original MIB, and edit the faulty MIB with the absolute OID value in place of the name of the unresolved MIB node.

2

Syntax error, Unresolved OID for ?.mib-2.ident

Explanation:
The compiler is unable to resolve the OID for mib-2 and other dependent nodes such as ident. These nodes are not defined in this MIB, nor are they imported from any of the dependent MIBs.

User Response:
Correct this error by using either of the following workarounds.

1. In the IMPORTS statement, include a line to import mib-2 from RFC1213-MIB. (mib-2 is defined in RFC1213-MIB), as shown in the following example:

   IMPORTS OBJECT-TYPE FROM RFC-1212
                    tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress,  
                    tcpConnRemPort, mib-2 FROM RFC1213-MIB;

2. In the statement where mib-2 is used in RFC-1414 MIB, replace the mib-2 name with the absolute OID of the mib-2node, as shown in the following example:

             ident   OBJECT IDENTIFIER ::= { 1.3.6.1.2.1.24 }

3

Multiple MIB definitions in a single MIB file

Explanation:
Some MIBs, such as those from extreme network, include multiple MIB definitions in a single file. The Compiler tool cannot compile these MIBs successfully.

User Response:
Copy each of the MIB definitions from the original MIB file into individual files. Compile each of the MIB files according to the dependency sequence.

4

Syntax error, EXTREME-SYSTEM-MIB--error message

Explanation:
This file has many MIB definitions in a single file and the Compiler tool cannot compile MIBs with multiple MIB definitions in a single file.

User Response:
Each MIB definition has the following general format:

Copy the MIB definitions into individual files. Save these files to your desktop and compile each of the MIB files separately.

4

Duplicate MIB compilation

Explanation:
You are trying to compile an MIB that has already been compiled. As a part of the Compiler tool, standard RFC MIBs -- RFC1155, RFC1213, SNMPv2-SMI, SNMPv2-CONF, and SNMPv2-TC -- are precompiled and loaded into memory during compilation of each MIB. You do not need to recompile or overwrite these precompiled MIBs. However, if one or more of the above MIBs are included when compiling an MIB, the MIB that you are trying to compile is incorrect or the nodes from the above, precompiled MIBs were incorrectly imported.

Also, if a duplicate MIB compilation error occurs during incremental compilation of any MIB, it indicates the existence of some wrong import statements in the MIB files that were previously compiled.

User Response:
Ensure that you retrieve the MIBs that you compile from legitimate sources. You must import MIB nodes from the MIB in which they were originally defined. Modify the faulty MIB to import MIB nodes from the correct MIB file.

5

Syntax error--no declaration

Explanation:
During compilation of MIB ADMIN-AUTH-STATS-MIB, the compilation fails with a syntax error. The error is due to the use of MAX, which has no declaration anywhere in the MIB or in the dependent MIBs.

User Response:
Substitute the actual maximum integer value in place of MAX.

6

Syntax error--no definition

Explanation:
During compilation of CISCO-TC MIB, the compiler fails with a syntax error. The SMI is used to define the Unsigned32 textual convention.

User Response:
Remove the SMI statement and define the Unsigned32 textual convention.