"How To: Load and Compile SNMP MIBs on T/Mon..."

Problem: Unable to Load and Compile SNMP MIBs
Platform: T/Mon - IAM

Configuring your T/Mon - IAM to receive and process SNMP traps can enhance your monitoring considerably. The SNMP setup process requires loading and compiling of SNMP MIBs (Management Information Bases) onto the T/Mon. Use the following "techno knowledge" paper to load and compile SNMP MIBs on the T/Mon - IAM for the first time, or to troubleshoot common issues.

This "techno knowledge" paper can help you if:

• You are unable to load and compile SNMP MIBs onto your T/Mon or IAM.

Quick Reference Chart

(for more details, review the troubleshooting checklist below...)

Troubleshooting Checklist

1. Confirm that T/Mon has latest software installed
• Because several MIB compiler issues are solved in newer firmware versions, we recommend that you upgrade to version 4.7 of the T/Mon firmware.
2. Confirm T/Mon has trap processor module installed
• If you have already processed SNMP traps and are simply adding a new MIB, you may skip this step.
• If this is your first time setting up SNMP, however, please note that in order to receive and process traps, the SNMP Trap Processor module (DPS Part # D-SK-490-10A-00) must be loaded on the T/Mon.
• To verify you have this module installed, navigate to "Diagnostics --> Installable Modules --> Installation Status". Look for SNMP Trap Processor, and the phrase "Installed" to the left of it. If the SNMP Trap Processor module is not on your system, contact Sales at (800) 622-3314.

Navigate to the following listing of installed and installable modules to verify that you have the SNMP Trap Processor module installed on your T/Mon system.

3. Acquire the main MIB for your device
• This can generally be found in a user manual, product CD, or manufacturer's website.
4. Acquire any referenced MIBs
• Open the MIB in a text editor such as notepad.
• You should see a section labeled "imports" toward the beginning of the file. See below:
  



In this example, the "imports" section indicates that you need the RFC1213-MIB, RFC1212, and RFC1155-SMI MIBs in order to correctly compile the DPS-MIB-V38 MIB. There are a number of resources available on the internet to search for MIBs. (notably, www.mibdepot.com)

• NOTE: The T/Mon-IAM will only parse MIBs with a .mib extension. If you were provided with MIBs that have a .my or .txt extension this will need to be changed to .mib before transferring the files.
5. Ensure all MIBs are raw ASN.1 text format
• Avoid any "pre-compiled" .mib files
• Avoid UNIX MIBs. Use DOS MIBs only.
• ASN.1 files are readable in any standard text editor (ex. Notepad)
6. Identify the types of traps the device will send
• While you have the MIB open in a text editor, search for the following pieces of text (the T/Mon can handle these types of traps):




7. Transfer the MIBs to the T/Mon. Multiple methods are available:
   
• Transfer MIBs via FTP (If you have not set up your T/Mon for FTP, please refer to the "Unable to Setup FTP Server on T/Mon" techno knowledge paper). When you make an FTP connection to the T/Mon-IAM, you will be in the working directory. If there is not already a folder named MIBS, create this folder, and drop your MIB files inside.
• "Sneaker Net": You can put the MIBs on a floppy, or CD (If your master is equipped with a CD-ROM drive).
  Place the media in the T/Mon
  Navigate to Files --> Utilities --> MIB File Manager
  Choose Import MIB
  Enter the source drive (A = Floppy, D = CD on IAM, E = CD on T/MonNOC).
  You will be given a list of MIBs on the source disk to choose from. Use the TAB key to enter the list and choose the MIB you'd like to import. This must be done once for each MIB.
  



Navigate to the MIB File Manager





As an alternative to FTP, you may use the MIB File Manager to import MIBs one at a time.





After selecting the MIB disk, select a .mib file to import.



8. Compile the MIBs
• Choose 'Compile' from the MIB Manager menu. This will compile all MIBs with the .mib extension in the MIBs directory.
• If there are no errors during compilation, you will see a “No errors!” message. This message indicates that you have successfully loaded and compiled SNMP MIBs onto your T/Mon. You have solved the problem and need not complete the remainder of this checklist.



A completed MIB compilation with no errors.

9. Correct any errors that occur
• If errors are found during compilation, you will see an "Errors found:" message:
  



An MIB compilation with errors found.

• The most common error (95% of time) is an import error.
  This means that an MIB file that needs to be compiled is missing.
  Open the MIB Manager log from the Report Viewer.
  (from master menu) 'Reports' -->'View Report File' --> 'MIB Manager Logs'
  Look for "Imported" to see the MIB that was missing:
  Refer back to the earlier steps in this checklist to identify, locate, and import the missing MIB(s).
  



This log is where you'll find the most common errors: missing MIBs. In this log example, the "RFC115-SMI" MIB is missing.

If you continue to have issues while loading and compiling SNMP MIBs, please contact DPS Telecom Tech Support.