A management information base (MIB) is a table of definitions for managed objects in a network device. SNMP uses MIBs to maintain standard definitions of all of the components and their operating conditions within a network device. Each object in the MIB has an identifying code called an object identifier (OID).
MIBs are either standard or enterprise-specific. Standard MIBs are created by the Internet Engineering Task Force (IETF) and documented in various RFCs. Enterprise-specific MIBs are developed and supported by a specific equipment manufacturer.
The enterprise branch number for Junos OS is 2636. Enterprise branch numbers are used in SNMP MIB configurations, and they are also known as SMI network management private enterprise codes.
For a list of supported standard and enterprise-specific MIBs, click SNMP MIBs and Traps Reference
This article provides answers to the most common questions about Junos OS MIBs.
- Do MIB files reside on the Junos OS devices?
- How do I compile and load the Junos OS MIBs onto an SNMP manager or NMS?
- What is SMI, and which versions does Junos OS support?
- Does Junos OS support MIB II?
- What is the system object identifier (SYSOID) of a device?
- What can I do if the MIB OID query is not responding?
- Which MIB displays the hardware and chassis details on a Juniper Networks device?
- Is the interface index (ifIndex) persistent?
- Which MIB objects support SNMP set operations?
- Can I use SNMP to determine the health of the processes running on the Routing Engine?
- Are the Ping MIBs returned in decimal notation and ASCII?
- Is there an SNMP MIB to show Address Resolution Protocol (ARP) table information?