Moogsoft Docs

Parse MIBs for Trap Integration

You can use the Mibparser command-line utility in Moogsoft AIOps to parse MIB (management information base) files for the Trapd LAM integration. This utility can help identify issues and conflicts between your provided set of MIBs. For more information on the checks see MIBs.

You can also export the parsed MIBs specified in the Trapd LAM to a JSON file. Parsing to the JSON file lets you inspect the output for sanity checks and warnings. It also speeds startup because the Trapd LAM doesn't need to parse when it launches.

How the Trap Integration identifies MIBs

If the Trap LAM integration doesn't find any pre-compiled MIBs, it automatically parses any MIBs in $MOOGSOFT_HOME/etc/mibs upon launch.

If you have pre-parsed MIBs using Mibparser, you can configure the Trap LAM to find the file by specifying it in$MOOGSOFT_HOME/config/trapd_lam.conf.

Configure Trap Integration to use Parsed MIBS

Configure the Trap Integration to use parsed MIBs following these steps:

  1. Launch the Mibparser utility from $MOOGSOFT/bin/utils and use -i argument to define the location it parses the MIBs from:

    ./mibparser -i <MIB_directory_filepath>

    Define the output of the Mibparser using -o. See Mibparser Command Reference.

  2. Configure the Trap LAM to find the file under mib_db_file in $MOOGSOFT_HOME/config/trapd_lam.conf.

If you specify a file, the Trap integration does not parse any MIBs in $MOOGSOFT_HOME/etc/mibs. Instead it loads in the MIBs and the objects defined in the file.

Parsed MIBs Reference

There might be naming conflicts and other issues when you import parsed MIBs.

For more information on MIB sanity checks, error messages, and the base set of MIBs see MIBs.