Examples of MIB publishing errors

If the publishing was not successful, you might see any of the following messages in the mib2map.out file. Use this section to fix the issue.

• • Unknown variable 'xxxxxxxxxxxx' in OID object
  • Cannot find module (xxxxxxxxxx)
  • Unable to find a matching object identifier for "a"
  • SAX Parse Exception occurred the element type class must be terminated by the matching end-tag
  • Too many textual conventions (INTEGER): At line nn in xxxxxxxxxxxxxxxxxxx.my
  • Unlinked OID / Undefined identifier
  • Did not find 'xxxxxxxx' in module

Unknown variable 'xxxxxxxxxxxx' in OID object

The following error indicates there is no definition for trapGeneralComment in the MIB file.

This can be caused by a typo resulting the variable to be defined under another name such as shown below.

To fix this, update all occurrences of the undefined variable to reference the defined variable.
For example, change trapGeneralComment to trapGenericTrapComment

Another common cause of this error is incorrect letter case used in the definition. For example:

In this example, the variable is defined:

Note the case does not match. In the definition, C is in upper case — trapClsErrorCode
To fix this, use the correct case for the object-type.

Cannot find module (xxxxxxxxxx)

The following error indicates that the netapp_dfm.mib file is looking to import a definition from {{NETWORK-APPLIANCE-MIB,}}but the MIB file was not present in the directory of files you are publishing.

For example: Cannot find module (NETWORK-APPLIANCE-MIB): At line 26 in E:\BMC_Software\MasterCell\server\SNMPAdapter\ucd-snmp-4.2.3\usr\mibs/netapp_dfm.mib.txt

To fix this, locate the missing MIB file and include it with the MIB files being published.

Unable to find a matching object identifier for "a"

MIBs will depend on standard MIB files. This issue is caused when some of the dependent MIBs are not included while compiling.
This can occur when using mib2map and the user has not specified the location of the default MIBs. See Cannot find module (xxxxxxxxxx).

SAX Parse Exception occurred the element type class must be terminated by the matching end-tag

This error occurs if the mcsnmptrapd.map is manually edited and comments have been inserted within a mapping.

To correct this issue, move comments either before or after the mapping in mcsnmptrapd.map.

Too many textual conventions (INTEGER): At line nn in xxxxxxxxxxxxxxxxxxx.my

Snmptranslate has a limit of 256 imports. If you try to import a MIB file that tries to import more than 256 objects, it will fail.

To fix this issue, contact Customer Support.

Unlinked OID / Undefined identifier

The following error is caused by a MIB file (printer-mib in this example) which references the definition mib-2, which is not defined in the MIB or imported from another MIB.

For example:

To correct the issue, locate the missing definition and add an import to the affected MIB. For example, the mib-2 definition is found in RFC1213-MIB. Add the import of mib-2 from RFC1213-MIB in printer-mib.

Did not find 'xxxxxxxx' in module

The following error occurs when a MIB trying to import a definition from another MIB that does not contain that definition.

Below is an example of the Import section from the CLIENT-MIB

In this instance Boolean is not defined in HOST-RESOURCES-MIB.

To resolve the issue, locate the MIB that has the missing definition and add it to the import section of the affected MIB.