OpsRamp supports uploading MIB (Management Information Base) files to extract SNMP trap definitions. Understanding supported formats, dependencies, and limitations helps ensure successful parsing and onboarding of traps.

Supported file formats

OpsRamp supports MIB files in formats such as: mib, my, txt, dic, zip, tar, tar.gz, tgz, and bz2. Compressed formats (such as .zip or .tar.gz) can be used to upload multiple MIB files together.

File content requirements

The uploaded file must contain valid SNMP MIB definitions.

  • The MIB must follow standard SNMP syntax
  • The file should not be incomplete or partially extracted

Files that do not meet these requirements may be accepted during upload but fail during parsing.

MIB dependencies

Some MIB files reference other MIB modules as dependencies. If these dependent MIBs are not included in the upload, parsing may fail.

  • If dependent MIB modules are not available, parsing may fail
  • Upload all required MIB files together when dependencies exist
  • Use compressed formats (such as .zip) to include multiple related MIB files

Ensuring all dependencies are available improves parsing success.

Parsing behavior

After upload, OpsRamp parses the MIB file to extract trap definitions. Parsing may fail in the following scenarios:

  • Invalid or unsupported MIB syntax
  • Missing dependent MIB modules
  • Unsupported or vendor-specific constructs
  • Incomplete or corrupted MIB files

In such cases, the system displays parsing errors and does not extract traps.

Not all MIB files contain trap definitions. Some MIBs define only objects or metrics, and such files may parse successfully but will not produce any SNMP traps. Ensure that the MIB file includes valid trap definitions before uploading.

Limitations

  • OpsRamp cannot parse MIB files with invalid or unsupported syntax
  • Dependent MIB modules must be included to avoid parsing failures
  • Vendor-specific constructs may not be supported
  • Very large MIB files may impact performance

For better performance, test with smaller MIB files before uploading large files and upload only the required MIB modules when possible.

Best practices

  • Use vendor-provided MIB files for the target device
  • Avoid modifying MIB files unless necessary
  • Ensure all dependencies are included
  • Validate MIB files before uploading
  • Use compressed formats when uploading multiple related MIB files