[an error occurred while processing this directive][an error occurred while processing this directive]

Loading MIB Files to a Network Management System

For your network management system (NMS) to identify and understand the MIB objects used by JUNOS Software, you must first load the MIB files to your NMS using a MIB compiler. A MIB compiler is a utility that parses the MIB information such as MIB object name, IDs, and data type for the NMS.

You can download the JUNOS MIB package from the Enterprise-Specific MIBs and Traps section of the JUNOS Software Technical Publications index page at https://www.juniper.net/techpubs/software/junos/index.html. The JUNOS MIB package is available in .zip and .tar packages; you can download the appropriate format based on your requirements.

The JUNOS MIB package contains two folders, namely StandardMibs and JuniperMibs. The StandardMibs folder contains the standard MIBs and RFCs that are supported on devices running JUNOS Software, whereas the JuniperMibs folder contains the Juniper Networks enterprise-specific MIBs.

To load MIB files that are required for managing and monitoring devices running JUNOS Software:

  1. Go to the JUNOS Software Technical Publications index page (https://www.juniper.net/techpubs/software/junos/index.html).
  2. Click the tab that corresponds to the JUNOS Software release for which you want to download the MIB files.
  3. On the selected tab, click the + (plus) sign that corresponds to the Enterprise-Specific MIBs and Traps section to expand the section.
  4. Click the TAR or ZIP link that corresponds to the Enterprise MIBs link under the Enterprise-Specific MIBs and Traps section to download the JUNOS MIB package.
  5. Decompress the file (.tar or .zip) using an appropriate utility.
  6. Load the standard MIB files (from the StandardMibs folder) in the following order:

    Note: Some of the MIB compilers that are commonly used have the standard MIBs preloaded on them. If the standard MIBs are already loaded on the MIB compiler that you are using, skip this step and the next, and proceed to Step 7.

    1. mib-SNMPv2-SMI.txt
    2. mib-SNMPv2-TC.txt
    3. mib-IANAifType-MIB.txt
    4. mib-IANA-RTPROTO-MIB.txt
    5. mib-rfc1907.txt
    6. mib-rfc2011a.txt
    7. mib-rfc2012a.txt
    8. mib-rfc2013a.txt
    9. mib-rfc2863a.txt
  7. Load the remaining standard MIB files.

    Note: You must follow the order specified in this procedure, and ensure that all standard MIBs are loaded before you load the enterprise-specific MIBs. There may be dependencies that require a particular MIB to be present on the compiler before loading some other MIB. You can find such dependencies listed in the IMPORT section of the MIB file.

  8. After loading the standard MIBs, load the Juniper Networks enterprise-specific SMI MIB, mib-jnx-smi.txt and the following optional SMI MIBs based on your requirements.
    • mib-jnx-js-smi.txt—(Optional) For Juniper Security MIB tree objects
    • mib-jnx-ex-smi.txt—(Optional) For EX Series Ethernet Switches
    • mib-jnx-exp.txt—(Recommended) For Juniper Networks experimental MIB objects
  9. Load the remaining enterprise-specific MIBs from the JuniperMibs folder.

Tip: While loading a MIB file, if the compiler returns an error message saying that any of the objects is undefined, open the MIB file using a text editor and ensure that all the MIB files listed in the IMPORT section are loaded on the compiler. If any of the MIB files listed in the IMPORT section is not loaded on the compiler, load that MIB file, and then try to load the MIB file that failed to load.

For example, the enterprise-specific PING MIB, mib-jnx-ping.txt, has dependencies on RFC 2925, DiSMAN-PING-MIB, mib-rfc2925a.txt. If you try to load mib-jnx-ping.txt before loading mib-rfc2925a.txt, the compiler returns an error message saying that certain objects in mib-jnx-ping.txt are undefined. Load mib-rfc2925a.txt, and then try to load mib-jnx-ping.txt. The enterprise-specific PING MIB, mib-jnx-ping.txt, then loads without any issue.


Published: 2010-04-27

[an error occurred while processing this directive]