Troubleshooting: Managing Management Information Bases (MIBs)

The following list contains some common problems that users encounter when updating the NerveCenter MIBs.

A MIB won't compile

Problem: The vendor ASN1 definitions that you added are not formatted correctly.

Solution: Check for spelling and format.

Problem: The mibcomp.txt file is not formatted correctly.

Solution: Check to make sure the appropriate lines are included in the file and are not commented out.

See .

Problem: The ASN1 file does not exist in the directory referenced in the mibcomp.txt file.

Solution: Move the file to the specified directory or correct the path in the mibcomp.txt file.

Problem: You must run the command from the mib directory (mibs on UNIX).

Solution: Change to the correct directory and run the mibcomp command again.

See .

Problem: User or file permissions are not set correctly, so mibcomp cannot create or update the MIB file.

Solution: Check user or file permissions and correct them, if necessary. See your operating system documentation.

Problem: You must be a member of ncadmins on UNIX or NerveCenter Admins on Windows NT to load a MIB.

Solution: Make sure you have appropriate group membership.

Problem: The MIB must be located on the server machine.

Solution: Copy the MIB to the server machine and try loading it again.

See .

Problem: The name or location of the MIB has changed.

Solution: Update the name and location of the MIB and try loading it again.

Previous: Managing Management Information Bases (MIBs)	Next: Appendix: Error Messages
Please send comments or corrections to Information Development	This file was last updated on 10 October 2000