This document describes Simple Network Management Protocol (SNMP) and issues related to Cisco equipment.
A. In the past, all the objects under the Cisco MIB branch were documented in one large document. This document was updated with each new release of Cisco IOS® software. Therefore, there was a 9.0 Cisco MIB and a 10.0 Cisco MIB, and so forth. Also, in those days, the product line was exclusively routers.
However, as Cisco IOS software matured and the product line grew, this massive MIB model became unscalable. Within one revision level of Cisco IOS software, there were different versions (such as the IP-only image and the IBM feature set version). The product line also included other devices, such as LAN switches that ran completely different software code.
In Cisco IOS Software Release 10.2 and later, the Cisco MIB was broken into individual component MIB documents, each focused on a specific feature, technology, or device type. This structure allows quicker implementation of new features. It also allows users to compile only the parts they need into their network management system (NMS).
A. Use these steps:
A. Use these steps:
A. Under the cisco/cisco-mibs directory, you can find these subdirectories:
At each directory level containing multiple files, all of the files located in that directory are compressed (with tar or gzip) into a single file for easy download. For example, traps.tar.gz contains all of the traps files.
Within the SNMP version directories, you can find all Cisco-specific MIBs in their latest form, along with some other MIBs that can apply to Cisco products. All MIB documents supersede any previous versions of the MIB document, including the monolithic MIB used in Cisco IOS Software Releases 9.x and 10.0.
In order to determine when the MIB document was released, look at the date in the file comments.
A. For the MIBs supported by a specific Cisco IOS software release, go to Cisco IOS MIB Locator.
For the MIBs supported by non-Cisco IOS products, go to SNMP Object Navigator > Download MIBs.
Note: There is an automated email gateway to Cisco IOS MIB Locator. Send an e-mail to mii@external.cisco.com with “help” in the subject line, to learn more about it.
A. In the Cisco IOS MIB Locator, in the Search by section, click the MIBs radio button. In the Search for MIBs drop-down list, choose the correct MIB. Click Submit.
A. Refer to Adding Cisco Traps in NetView and HP OpenView.
A. Refer to MIB Compilers and Loading MIBs.
A. There are several new macros defined for SNMPv2. It is an SNMPv2 MIB if you can find any of these in your MIB:
Another way to tell is that MIB objects defined in an SNMPv1 MIB usually have an ACCESS clause. MIB objects defined in an SNMPv2 MIB usually have a MAX-ACCESS clause.
A. Yes, ipNetToMediaPhysAddress = .1.3.6.1.2.1.4.22.1.2 from the MIB RFC1213-MIB.my:
ipNetToMediaPhysAddress OBJECT-TYPE
-- FROM RFC1213-MIB, IP-MIB
-- TEXTUAL CONVENTION PhysAddress
SYNTAX OCTET STRING
MAX-ACCESS read-write
STATUS Mandatory
DESCRIPTION "The media-dependent `physical' address."
::= { iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) ip(4)
ipNetToMediaTable(22) ipNetToMediaEntry(1) 2 }
A. This is expected (it is not a bug) and is part of a trade-off: the box is allowed to dedicate more resources to actually switching traffic because it is polled less often for interface statistics. The show interfaces command can have the same behavior.
| Revision | Publish Date | Comments |
|---|---|---|
4.0 |
17-Aug-2026
|
Reformatted links. |
3.0 |
30-Nov-2023
|
Recertification |
2.0 |
02-Nov-2022
|
Updated to retrieve MIBS with GitHub. |
1.0 |
19-Nov-2001
|
Initial Release |