SNMP MIB Compiler

Management Information Base (MIB) files are text files written in Abstract Syntax Notation. They describe Simple Network Management Protocol (SNMP) elements for specific devices. By default, Horizon includes an extensive list of MIB definitions from a number of vendors. You will only need to import MIB files for unformatted events as part of configuring SNMP traps and collection.

You can parse SNMP MIB definitions and create Horizon event definitions from any TRAP-TYPE and/or NOTIFICATION-TYPE macros they contain through the UI. You can also generate data collection definitions from OBJECT-TYPE symbols defined in a MIB file.

You can also use the mib2opennms command line utility to help create event definitions from MIB definitions. Using the UI editor achieves similar results to using mib2events. We do not recommend using using mib2opennms, as it produces more bus errors than event definitions.

To import a MIB file and create event definitions, follow these steps:

  1. Save the vendor MIB file to a location available to your local workstation. The MIB file does not need to be accessible by the server.

  2. In Horizon, click the gears icon and select Additional Tools → SNMP MIB Compiler.

  3. Click Upload MIB.

  4. Select the MIB file and click Open.

  5. Right-click the file and choose Compile MIB.

  6. If the log area displays an error (usually a missing dependency), you need to correct the error to compile the MIB file successfully.

    1. Determine the type of error (dependency, file syntax).

    2. Google the name of the missing content, save it as a text file, upload it, and compile again.

      AND/OR

    3. Right-click the file and choose Edit MIB.

    4. Edit the file to address the error, click Save, and compile it again.

  7. Continue to edit the file until it compiles successfully.

  8. Right-click on the MIB from which you want to generate an event and choose Generate Events or Generate Data Collection, as appropriate.

  9. If desired, modify the name of the UEI base with the vendor name for easier troubleshooting and click Configure.

  10. Click Save Events File to save them to the event.conf file.

If you were getting unformatted events, they will now be formatted.