Table Of Contents
Cisco 10000 Series Router MIB Categories
Unsupported and Not Tested MIBs
CISCO-ENTITY-VENDORTYPE-OID-MIB
CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN
MIB Specifications
This chapter describes each Management Information Base (MIB) on the Cisco 10000 Series. Each description lists any constraints on how the MIB is implemented on the router. Unless noted otherwise, the Cisco 10000 Series router implementation of a MIB follows the standard. For detailed MIB descriptions, see the MIB.
Note
For information about how to avoid performance problems when you use SNMP to poll the router for routing table entries, see the "Cisco SNMP Support" section. To determine which MIBs are included in other releases, see the "Determining MIB Support for Cisco IOS Releases" section.
Cisco 10000 Series Router MIB Categories
Not all MIBs included in a Cisco IOS release are fully supported by the router. Some MIBs are not supported at all. Other MIBs might work, but they have not been tested on the router. In addition, some MIBs are deprecated but cannot be removed from the software.
The following tables list the categories of MIBs in the c10k Image for Cisco IOS Release 12.2SB REL4. for configurations on the Cisco 10000 Series:
•
•
•
Note
Supported and Tested MIBs
Table 3-1 lists the MIBs included in Cisco IOS EFT software release 12.2SB REL4 that are supported and tested for configurations on the Cisco 10000 Series. To determine which MIBs are included in other releases, see the "Determining MIB Support for Cisco IOS Releases" section.
Supoorted and Not Tested MIBs
Table 3-2 lists the MIBs included in Cisco IOS EFT software release 12.2SB REL4 that are supported but not tested for configurations on the Cisco 10000 Series router.
Unsupported and Not Tested MIBs
Table 3-3 lists MIBs that are unsupported or not tested.
Note
ATM-FORUM-ADDR-REG-MIB
The ATM-FORUM-ADDR-REG-MIB contains information about ATM user-network interface (UNI) addresses and ports. The MIB also contains ATM address registration administration information.
There are no constraints on this MIB.
ATM-FORUM-MIB
The ATM-FORUM-MIB contains ATM object definitions and object identifiers (OIDs).
There are no constraints on this MIB.
ATM-MIB
The ATM-MIB contains the ATM and ATM adaptation layer 5 (AAL5) objects used to manage ATM interfaces, virtual links, cross connects, and AAL5 entities and connections.
MIB Constraints
Table 3-4 lists the constraints that the router places on objects in the ATM-MIB. For detailed definitions of MIB objects, see the MIB.
BGP4-MIB
The BGP4-MIB provides access to information related to the implementation of the Border Gateway Protocol (BGP). The MIB provides:
•
•
•
•
•
•
•
There are no constraints on this MIB.
CISCO-CEF-MIB
The CISCO-CEF-MIB (Cisco Express Forwarding) contains objects that manage Cisco Express Forwarding (CEF) technology. CEF is the key data plane forwarding path for layer 3 IP switching technology. The CISCO-CEF-MIB monitorS CEF operational data and provideS notification when encountering errors in CEF, through SNMP.
Note
CISCO-AAA-SERVER-MIB
The CISCO-AAA-SERVER-MIB contains information about authentication, authorization, and accounting (AAA) servers within the router and external to the router. The MIB provides:
•
•
•
MIB Constraints
The configuration objects in the MIB are read-only. To configure AAA servers, use the CLI commands aaa new-model, aaa authentication ppp, aaa authorization, aaa accounting, and radius-server host. Table 3-5 lists the constraints that the router places on objects in the CISCO-AAA-SERVER-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-AAA-SESSION-MIB
The CISCO-AAA-SESSION-MIB contains information about accounting sessions based on authentication, authorization, and accounting (AAA) protocols.
MIB Constraints
Table 3-6 lists the constraints that the router places on objects in the CISCO-AAA-SESSION-MIB. For detailed definitions of MIB objects, see the MIB.
Note
CISCO-AAL5-MIB
The CISCO-AAL5-MIB contains performance statistics for ATM adaptation layer 5 (AAL5) virtual channel connections (VCCs). This MIB provides statistics not found in the aal5VccTable in RFC 1695 (for example, packets and octets received and transmitted on the VCC).
There are no constraints on this MIB.
CISCO-ACCESS-ENVMON-MIB
The CISCO-ACCESS-ENVMON-MIB indicates the reason for a power supply failure, which is information not found in the ciscoEnvMonSupplyStatusTable in the CISCO-ENVMON-MIB. The CISCO-ACCESS-ENVMON-MIB also defines temperature and voltage notifications to replace those in CISCO-ENVMON-MIB. This MIB is deprecated.
CISCO-ATM-EXT-MIB
The CISCO-ATM-EXT-MIB contains extensions to the Cisco ATM module that are used to manage ATM entities. It provides additional AAL5 performance statistics for a virtual channel connection (VCC) on an ATM interface. There are no constraints on this MIB.
CISCO-CBP-TARGET-MIB
The CISCO-CBP-TARGET-MIB (common class-based policy) contains objects that provide a mapping of targets to which class-based features, such as QoS are applied. These features can be enabled in a feature specific manner or through the Class-based Policy Language (CPL).
The CISCO-CBP-TARGET-MIB abstracts the knowledge of the specific types of targets from the class-based policy feature specific MIB definitions.
MIB Constraints
Table 3-7 lists the constraints that the router places on objects in the CISCO-CBP-TARGET-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-BGP4-MIB
The CISCO-BGP4-MIB contains Cisco defined extensions to the BGP4-MIB.
There are no constraints on this MIB.
CISCO-BULK-FILE-MIB
The CISCO-BULK-FILE-MIB contains objects to create and delete files of SNMP data for bulk-file transfer.
MIB Constraints
Table 3-8 lists the constraints that the router places on objects in the CISCO-BULK-FILE-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-8 CISCO-BULK-FILE-MIB Constraints
•
Only ephemeral(1) supported.
•
Data format standardBER(1) not supported.
CISCO-CDP-MIB
The CISCO-CDP-MIB contains objects to manage the Cisco Discovery Protocol (CDP) on the router.
There are no constraints on this MIB.
CISCO-CLASS-BASED-QOS-MIB
The Class-Based Quality of Service Management Information Base (CBQoS- MIB) provides access to quality of service (QoS) configuration information and statistics. The CBQoS-MIB allows service providers to monitor their QoS offerings. This MIB gives QoS configuration done in the router such as ClassMap, PolicyMap, Match Statements and Feature Actions configuration parameters.
The MIB contains counter objects which provides statistic information such as the number of packets traversed conforming to a policing feature. The MIB uses several indexes to identify QoS features and to distinguish among instances of those features. The MIB provides information about marking and policing done using IP precedence and Differentiated Services Code Point (DSCP).
The MIB uses several indexes to identify QoS features and distinguish among instances of those features:
•
•
•
•
The indexes cbQosPolicyIndex and cbQosObjectsIndex are assigned by the system to uniquely identify each instance of a QoS feature. These indexes are never reused between router reboots, even if the QoS configuration changes.
QoS information is stored in:
•
•
For detailed information about QoS, see its feature description at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/aggr/10000/10kftmap/map.htm
MIB Constraints
Table 3-9 lists the constraints that the router places on objects in the CISCO-CLASS-BASED-QOS-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-CONFIG-COPY-MIB
The CISCO-CONFIG-COPY-MIB contains objects to copy configuration files on the router. For example, the MIB enables the SNMP agent to:
•
•
•
MIB Constraints
You can use a Trivial File Transfer Protocol (TFTP) server to copy configuration files to and from the network.
Table 3-10 lists the constraints that the router places on objects in the CISCO-CONFIG-COPY-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-CONFIG-MAN-MIB
The CISCO-CONFIG-MAN-MIB contains objects to track and save changes to the router configuration. The MIB represents a model of the configuration data that exists elsewhere in the router and in peripheral devices. Its main purpose is to report changes to the running configuration through the SNMP notification ciscoConfigManEvent.
There are no constraints on this MIB.
CISCO-ENTITY-ALARM-MIB
The CISCO-ENTITY-ALARM-MIB enables the router to monitor alarms generated by system components, such as the chassis, slots, modules, power supplies, fans, and module ports. For information about alarms and corrective actions, see the Cisco 10000 Series Router Troubleshooting Guide (which is listed below the Cisco 10000 Series Router Technical Reference documentation).
For a component's alarms to be monitored, the component must be defined by a row in the entPhysicalTable of the ENTITY-MIB.
Note
MIB Constraints
Table 3-11 lists the constraints that the router places on objects in the CISCO-ENTITY-ALARM-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-ENTITY-ASSET-MIB
The CISCO-ENTITY-ASSET-MIB provides asset tracking information for the physical components in the ENTITY-MIB entPhysicalTable.
The ceAssetTable contains an entry (ceAssetEntry) for each physical component on the router. Each entry provides information about the component, such as its orderable part number, serial number, hardware revision, manufacturing assembly number and manufacturing revision.
Most physical components are programmed with a standard Cisco generic ID PROM value that specifies asset information for the component. If possible, the CISCO-ENTITY-ASSET-MIB accesses the component's ID PROM information. However, if no ID PROM information is available, the MIB returns the values listed in Table 3-13.
MIB Constraints
Table 3-12 lists the constraints that the router places on objects in the CISCO-ENTITY-ASSET-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-13 lists the values that SNMP returns for ceAssetEntry objects if no ID PROM information exists for a component. The definition of ceAssetEntry is as follows:
CeAssetEntry ::= SEQUENCE { ceAssetOEMString SnmpAdminString, ceAssetSerialNumber SnmpAdminString, ceAssetOrderablePartNumber SnmpAdminString, ceAssetHardwareRevision SnmpAdminString, ceAssetMfgAssyNumber SnmpAdminString, ceAssetMfgAssyRevision SnmpAdminString, ceAssetFirmwareID SnmpAdminString, ceAssetFirmwareRevision SnmpAdminString, ceAssetSoftwareID SnmpAdminString, ceAssetSoftwareRevision SnmpAdminString, ceAssetCLEI SnmpAdminString, ceAssetTag SnmpAdminString, ceAssetIsFRU TruthValue }Not all ceAssetEntry objects are used by all router components, and ceAssetAlias is not implemented for the Cisco 10000 Series.
CISCO-ENTITY-EXT-MIB
The CISCO-ENTITY-EXT-MIB contains extensions for active and standby Performance Routing Engines (PREs) listed in the ENTITY-MIB entPhysicalTable. These extensions provide information such as RAM and NVRAM sizes, configuration register settings, and bootload image name for each PRE.
MIB Constraints
Table 3-14 lists the constraints that the router places on objects in the CISCO-ENTITY-EXT-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-ENTITY-FRU-CONTROL-MIB
The CISCO-ENTITY-FRU-CONTROL-MIB contains objects to configure and monitor the status of field replaceable units (FRUs) on the Cisco 10000 Series. An FRU is a hardware component (such as a line card, power supply, or fan) that can be replaced on site.
MIB Constraints
Table 3-15 lists the constraints that the router places on objects in the CISCO-ENTITY-FRU-CONTROL-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-ENTITY-PFE-MIB
The CISCO-ENTITY-PFE-MIB contains objects to monitor the performance of the packet forwarding engine (PFE). PFE technology accelerates certain IP features in order to improve network performance. On the Cisco 10000 Series, the PFE is the parallel express forwarding network processor (PXF), which is part of the performance routing engine (PRE). This is the processor listed in the ENTITY-MIB entPhysicalTable.
There are no constraints on this MIB.
The CISCO-ENTITY-PFE-MIB maintains information about performance, performance trends, and PFE-related events. The MIB also summarizes the utilization and efficiency information provided by the show hardware pxf cpu context command. You can also use the MIB to set thresholds for utilization and efficiency, and monitor when those thresholds are exceeded. For instructions, see the "Monitoring PXF Utilization" section.
The following CISCO-ENTITY-PFE-MIB tables contain information about processor performance:
•
•
The start of each 15-minute interval is based on the time that the PXF was last started or restarted, which may not match the start of a quarter-hour increment in real time (for example, 10:45 or 11:15). For example, if the PXF was started at 10:20, subsequent 15-minute intervals start at 10:35, 10:50, and so on.
•
Several other MIB tables and objects are used to monitor PXF restarts and threshold-exceeded events:
•
•
•
•
•
CISCO-ENTITY-VENDORTYPE-OID-MIB
The CISCO-ENTITY-VENDORTYPE-OID-MIB defines the object identifiers (OIDs) assigned to Cisco 10000 Series components. The OIDs in this MIB are used in the ENTITY-MIB as values for the entPhysicalVendorType field in entPhysicalTable. Each OID uniquely identifies a type of physical entity (for example, a fan tray, power supply, or line card).
MIB Constraints
Table 3-16 lists the objects and OIDs in the CISCO-ENTITY-VENDORTYPE-OID-MIB that describe router entities. For detailed definitions of MIB objects, see the MIB.
CISCO-ENVMON-MIB
The CISCO-ENVMON-MIB contains information about the status of environmental sensors (for voltage, temperature, fans, and power supplies). It also contains MIB objects to enable and disable notifications for changes to the status of these sensors.
When a router temperature test point reaches a critical state, the environmental monitor initiates a shutdown and sends a ciscoEnvMonShutdownNotification if it has been configured to do so (see the "Enabling Notifications" section).
MIB Constraints
Table 3-17 lists the constraints that the router places on objects in the CISCO-ENVMON-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-FLASH-MIB
The CISCO-FLASH-MIB contains objects to manage flash cards and flash-card operations.
There are no constraints on this MIB.
CISCO-FRAME-RELAY-MIB
The CISCO-FRAME-RELAY-MIB contains Frame Relay information that is specific to Cisco products or that is missing from RFC 1315.
The Cisco Frame Relay Management Information Base (MIB) describes managed objects that let you monitor Frame Relay operations remotely by using Simple Network Management Protocol (SNMP). The Frame Relay MIB Enhancements feature extends the Cisco Frame Relay MIB by adding MIB objects that monitor the following Frame Relay functionality:
•
•
•
•
•
There are no constraints on this MIB.
CISCO-FTP-CLIENT-MIB
The CISCO-FTP-CLIENT-MIB contains objects to invoke File Transfer Protocol (FTP) operations for network management.
There are no constraints on this MIB.
CISCO-HSRP-EXT-MIB
The CISCO-HSRP-EXT-MIB provides an extension to the CISCO-HSRP-MIB. It contains objects to perform functions such as assigning secondary HSRP IP addresses, monitoring the operational status of interfaces, and modifying an HSRP group's priority.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-HSRP-MIB
The CISCO-HSRP-MIB contains objects to configure and manage the Cisco Hot Standby Router Protocol (HSRP), which is defined in RFC 2281.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-IETF-ATM2-PVCTRAP-MIB
The CISCO-IETF-ATM2-PVCTRAP-MIB supplements the ATM-MIB. It implements the virtual channel link (VCL) section of the IETF document "draft-ietf-atommib-atm2-11.txt," Section 9 ATM Related Trap Support.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN
The CISCO-IETF-ATM2-PVCTRAP-MIB-EXTN contains information for monitoring ATM interfaces that is not defined in the ATM-MIB or the CISCO-IETF-ATM2-PVCTRAP-MIB.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-IF-EXTENSION-MIB
CISCO-IF-EXTENSION-MIB contains objects which provide additional information about interfaces not available in other MIBS. This MIB extends the IF-MIB (RFC2863).
There are no constraints on this MIB.
CISCO-IMAGE-MIB
The CISCO-IMAGE-MIB identifies the characteristics and capabilities of the Cisco IOS software image running on the router.
There are no constraints on this MIB.
CISCO-IPMROUTE-MIB
The CISCO-IPMROUTE-MIB contains objects to manage IP multicast routing on the router.
There are no constraints on this MIB.
CISCO-IP-LOCAL-POOL-MIB
The CISCO-IP-LOCAL-POOL-MIB contains objects that provide a network manager with information related to the local IP address pools. This MIB provides configuration and statistics reflecting the allocation of Local IP Pools. Each entry provides information about a particular IP local pool, including the number of free and used addresses.
The SNMP agent does not have to be configured in any special way for CISCO-IP-LOCAL-POOL-MIB objects to be available to the network management system. You can configure the SNMP agent to send the ciscoIpLocalPoolInUseAddrNoti notification to a particular host using the following command:
router(config)#snmp-server host <ip-address> <community-name> iplocalpool
The ciscoIpLocalPoolInUseAddrNoti notification is enabled:
•
•
router(config)#snmp-server enable traps ip local pool
For detailed information about this MIB, see its feature module description at the following URL:
CISCO-IP-STAT-MIB
The CISCO-IP-STAT-MIB contains objects to manage the collection and display of IP statistics, categorized by IP precedence and the Media Access Control (MAC) address associated with IP packets. To use the MIB to access additional IP statistics, you can issue the ip accounting mac-address and ip accounting precedence commands at the CLI.
There are no constraints on this MIB.
CISCO-IP-TAB-MIB
The CISCO-IP-TAB-MIB contains objects to manage the collection and display of IP statistics, categorized by IP precedence and the MediA.
CISCO-IP-URPF-MIB
The CISCO-IP-URPF-MIB(Unicast Reverse Path Forwarding ) contains objects that allows users to specify a URPF drop-rate threshold on interfaces of a managed device, which when exceeded, a SNMP notification is sent. It includes objects specifying global (to a managed device as a whole) and per-interface drop counts and drop rates, and also generates traps based on the drop rate exceeding a configureable per-interface threshold.
MIB Constraints
Table 3-18 lists constraints in the CISCO-IP-URPF-MIB.
CISCO-MEMORY-POOL-MIB
The CISCO-MEMORY-POOL-MIB contains objects to monitor memory pools on the router.
There are no constraints on this MIB.
CISCO-NETFLOW-MIB
The CISCO-NETFLOW-MIB contains objects that remotely obtains and manages cache flow information, current NetFlow configuration, and statistics.
The Netlow MIB provides a simple and easy method to get NetFlow cache information, current NetFlow configuration and statistics.The MIB provides Netflow information in these areas:
•
•
•
•
•
Table 3-19 lists object groups supported in the CISCO-NETFLOW-MIB in order to to manage informative and configurable parameters.
SNMP is used to collect network information. SNMP permits retrieval of critical information from network elements such as routers, switches, and workstations. The CISCO-NETFLOW-MIB feature uses SNMP to configure NetFlow and to gather NetFlow statistics.
The CISCO-NETFLOW-MIB contains objects that allow NetFlow statistics and other NetFlow data for the managed devices on your system to be retrieved by SNMP. You can specify retrieval of NetFlow information from a managed device (for example, a router) either by entering commands on that managed device or by entering SNMP commands from the NMS workstation to configure the router through the MIB.
If the NetFlow information is configured from the NMS workstation, no access to the router is required and all configuration can be performed through SNMP. The CISCO-NETFLOW-MIB request for information is sent from an NMS workstation through SNMP to the router and is retrieved from the router. This information is stored or viewed, thus allowing NetFlow information to be easily accessed and transported across a multivendor programming environment.
The CISCO-NETFLOW-MIB feature defines managed objects that enable a network administrator to remotely monitor the following NetFlow information:
•
•
•
Note
CISCO-OAM-MIB
The CISCO-OAM-MIB contains objects to configure cell-based Operations, Administration, and Maintenance (OAM) loopback ping tests on ATM connections. The MIB also contains information about test results.
The Cisco 10000 Series can run 100 ping tests at one time. If you attempt to run more than 100 ping tests, the router queues excess tests and runs them as other tests finish.
MIB Constraints
Table 3-20 lists the constraints that the router places on objects in the CISCO-OAM-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-20 CISCO-OAM-MIB Constraints
•
Maximum octet string size is 12 bytes, not 16 bytes.
CISCO-PIM-MIB
The CISCO-PIM-MIB defines Cisco specific objects and variables for managing Protocol Independent Multicast (PIM) on the router. These MIB definitions are an extension of those in RFC 2934, which is the IETF PIM MIB. There are no constraints on this MIB.
CISCO-PING-MIB
The CISCO-PING-MIB contains objects to manage ping requests on the router.
There are no constraints on this MIB.
CISCO-PPPOE-MIB
The CISCO-PPPOE-MIB contains objects to manage Point-to-Point Protocol over Ethernet (PPPoE) sessions. These objects represent PPPoE sessions at the system and virtual channel (VC) level.
MIB Constraints
Table 3-21 lists the constraints that the router places on objects in the CISCO-PPPOE-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-PROCESS-MIB
The CISCO-PROCESS-MIB displays memory and CPU usage on the router, and describes active system processes.
MIB Constraints
The router places the following constraint on the CISCO-PROCESS-MIB:
•
This means that cpmCPUTotalPhysicalIndex is always the index of the active PRE.
CISCO-PRODUCTS-MIB
The CISCO-PRODUCTS-MIB lists the object identifiers (OIDs) assigned to Cisco hardware platforms.
There are no constraints on this MIB.
Table 3-22 lists the MIB objects added to the CISCO-PRODUCTS-MIB to support the Cisco 10000 Series. The MIB includes an OID definition for c10400. However, the OID definition is meaningless because c10400 is not a valid product ID. For detailed definitions of MIB objects, see the MIB.
Table 3-22 CISCO-PRODUCTS-MIB New OID Assignments
cisco10008
(1.3.6.1.4.1.9.1.438)New object for Cisco 10008 Internet Router.
CISCO-QINQ-VLAN-MIB
The CISCO-QINQ-VLAN-MIB defines configuration and monitoring capabilities relating to 802.1 QinQ interfaces. QinQ interfaces terminate QinQ traffic and translate QinQ tags. The IEEE 802.1Q VLAN specification provides for an option to tag Ethernet frames with two VLAN tags:
•
•
The combination of inner and outer VLAN tags is used to uniquely identify a particular customer's service flow.
MIB Constraints
Table 3-23 lists the constraints that the Cisco 10000 Series places on objects in the CISCO-QINQ-VLAN-MIB. Unless noted otherwise, the Cisco 10000 series implementation of a MIB follows the standard. Any objects not listed in a table are implemented as defined in the MIB.
Table 3-23 CISCO-QINQ-VLAN-MIB Constraints
cqvTerminationRowStatus
Read only.
cqvTerminationPeEncap
Read only
CISCO-QUEUE-MIB
The CISCO-QUEUE-MIB contains objects to manage interface queues on the router.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-RTTMON-MIB
The CISCO-RTTMON-MIB contains objects to monitor network performance. The MIB provides information about the response times of network resources and applications. Each conceptual round-trip time (RTT) control row in the MIB represents a single probe, which is used to determine an entity's response time. The probe defines an RTT operation to perform (for example, an FTP or HTTP get request), and the results indicate whether the operation succeeded or failed, and how long it took to complete.
If you plan to schedule an RTT operation, see Table 3-24 for information about rttMonScheduleAdminRttStartTime in the rttMonScheduleAdminTable.
Note
MIB Constraints
Table 3-24 lists the constraints that the router places on objects in the CISCO-RTTMON-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-SNAPSHOT-MIB
The CISCO-SNAPSHOT-MIB contains objects to manage snapshot routing, which helps improve the use of system resources for static routing and routing for dedicated serial lines.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-SYSLOG-MIB
The CISCO-SYSLOG-MIB contains all system log messages generated by the Cisco IOS software. The MIB provides a way to access these syslog messages through SNMP. All Cisco IOS syslog messages contain the message name and its severity, message text, the name of the entity generating the message, and an optional time stamp. The MIB also contains a history of syslog messages and counts related to syslog messages.
Note
MIB Constraints
The MIB does not keep track of messages generated from debug commands entered through the CLI.
CISCO-SSG-MIB
The CISCO-SSG-MIB contains objects to manage the Service Selection Gateway (SSG) product on the router. SSG enables service providers to offer subscribers access to the Internet, corporate networks, and value-added services through broadband access technology such as digital subscriber lines (DSL), cable modems, and wireless access.
SSG works in conjunction with the Cisco Service Selection Dashboard (SSD) or its successor product, the Cisco Subscriber Edge Services Manager (SESM), to:
•
•
•
Subscribers can:
•
•
SSG communicates with the authentication, authorization, and accounting (AAA) management network where RADIUS, Dynamic Host Configuration Protocol (DHCP), and Simple Network Management Protocol (SNMP) servers reside. SSG also communicates with the Internet service provider (ISP) network, which may connect to the Internet, corporate networks, and value-added services.
MIB Constraints
Table 3-25 lists the constraints that the router places on objects in the CISCO-SSG-MIB. For detailed definitions of MIB objects, see the MIB.
CISCO-TAP2-MIB
The CISCO-TAP2-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router. This MIB is an extension to the IEisco IOS software image.
CISCO-TCP-MIB
The CISCO-TCP-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router. This MIB is an extension to the IETF TCP MIB.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
CISCO-VPDN-MGMT-EXT-MIB
The CISCO-VPDN-MGMT-EXT-MIB supplements the CISCO-VPDN-MGMT-MIB with additional information about VPDN tunnels and sessions. The MIB contains the following tables, which provide read-only information not found in the CISCO-VPDN-MGMT-MIB:
•
•
MIB Constraints
Table 3-26 lists the constraints that the router places on objects in the CISCO-VPDN-MGMT-EXT-MIB. In addition, the MIB is read-only, which means that you cannot use the MIB to configure VPDN on the router.
CISCO-VPDN-MGMT-MIB
The CISCO-VPDN-MGMT-MIB provides operational information about the Virtual Private Dialup Network (VPDN) feature on the router. You can use the MIB to monitor VPDN tunnel information on the router, but you cannot use the MIB to configure VPDN.
VPDN enables the router to forward Point-to-Point Protocol (PPP) traffic between an Internet service provider (ISP) and a home gateway. The CISCO-VPDN-MGMT-MIB includes several tables that contain VPDN tunneling information:
•
•
•
•
•
MIB Constraints
The CISCO-VPDN-MGMT-MIB contains read-only information. In addition, the MIB objects in Table 3-27 have been deprecated. Although currently supported, their use is being phased out and we recommend that you use the replacement object instead. For detailed definitions of MIB objects, see the MIB.
DS1-MIB
The DS1-MIB provides access to configuration and performance monitoring information for DS1 controllers and interfaces on the router.
MIB Constraints
Table 3-28 lists the constraints that the router places on objects in the DS1-MIB. For detailed definitions of MIB objects, see the MIB.
DS3-MIB
The DS3-MIB provides access to configuration and performance monitoring information for DS1 controllers and interfaces. The Cisco 10000 Series supports the version of the MIB based on RFC 2496.
MIB Constraints
Table 3-29 lists the constraints that the router places on objects in the DS3-MIB. For detailed definitions of MIB objects, see the MIB.
ENTITY-MIB
The ENTITY-MIB contains objects that represent only physical entities (components) in the router and allows SNMP management of those entities. The current software release supports the RFC 2037 version of this MIB.
The MIB table entPhysicalTable identifies the physical entities in the router. The entPhysicalTable contains a single row for the Cisco 10000 chassis and a row for each entity in the chassis. A physical entity may contain other entities (for example, a fan-tray bay may contain a fan-tray module, which may contain one or more fans). The physical hierarchy of system components is determined at runtime, based on the actual router configuration.
MIB Constraints
Table 3-30 lists the constraints that the router places on objects in the ENTITY-MIB. For detailed definitions of MIB objects, see the MIB. Any MIB table or object not listed in a constraint table is implemented as defined in the MIB.
Table 3-30 ENTITY-MIB Constraints
•
•
Not implemented.
Not implemented.
Not implemented.
ENTITY-MIB UDI Support
The ENTITY-MIB supports the Cisco compliance effort for a Cisco unique device identifier (UDI) standard which is stored in IDPROM.
The Cisco UDI provides a unique identity for every Cisco product. The unique device identifier is comprised of an orderable product identifier (PID), the version identifier (VID), and the hardware Serial Number (SN). The UDI is stored in IDPROM. The PID, VID, and SN must be stored in the entPhysicalTable:
•
•
•
Note
Each product that is capable of MIB support is required to populate ENTITY-MIB v2 or later with PID, VID, and SN. This compliance is also a requirement of the Consistent Network Element Manageability initiative. If the product uses both ENTITY-MIB and CISCO-ENTITY-ASSET-MIB, then the data in the following fields should be identical.
ENTITY-MIB v2 (RFC-2737) fields to be populated are:
•
•
•
•
•
ENTITY-MIB Usage
The following MIB entities are dependent on each user's configuration:
•
•
•
•
ETHERLIKE-MIB
The ETHERLIKE-MIB contains objects to manage Ethernet-like interfaces on the router.
MIB Constraints
Table 3-31 lists the constraints that the router places on objects in the ETHERLIKE-MIB. For detailed definitions of MIB objects, see the MIB.
EVENT-MIB
The EVENT-MIB contains objects to define event triggers and actions for network management purposes.
There are no constraints on this MIB.
EXPRESSION-MIB
The EXPRESSION-MIB contains objects to define expressions of MIB objects for network management purposes.
There are no constraints on this MIB.
IF-MIB
The IF-MIB contains objects to manage physical and logical interfaces. The Cisco 10000 Series supports the ifGeneralInformationGroup of MIB objects for all layers.
The IF-MIB provides index, statistics, and stacking information for physical interfaces, subinterfaces, and Layer 2 protocols on the Cisco 10000 Series. The ifStackTable shows the relationship between protocol layers and their underlying physical or virtual interfaces, with each layer and sublayer represented in the ifTable.
For example, an MPLS-layer interface is stacked above the physical or virtual interface passing MPLS traffic, and MPLS traffic-engineered tunnels are stacked above the MPLS-layer interface.
MIB Constraints
The router fully supports the MIB as it is defined in RFC 2233, with the specifications described in Table 3-32.
IGMP-MIB
The IGMP-MIB contains objects to manage the Internet Group Management Protocol (IGMP) on the router.
There are no constraints on this MIB.
INT-SERV-GUARANTEED-MIB
The INT-SERV-GUARANTEED-MIB describes the guaranteed service of the Integrated Services Protocol (ISP).
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
INT-SERV-MIB
The INT-SERV-MIB describes the Integrated Services Protocol (ISP).
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
IP-MIB
The IP-MIB contains objects to manage physical and logical interfaces. The Cisco 10000 Series supports the ifGeneralInformationGroup of MIB objects for all layers.
The IP-MIB provides index, statistics, and stacking information for physical interfaces, subinterfaces, and Layer 2 protocols on the Cisco 10000 Series. The ifStackTable shows the relationship between protocol layers and their underlying physical or virtual interfaces, with each layer and sublayer represented in the ifTable..
IP-FORWARD-MIB
The IP-FORWARD-MIB contains objects to display classless interdomain routing (CIDR) multipath IP routes.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
IPMROUTE-MIB
The IPMROUTE-MIB contains objects to manage IP multicast routing on the router, independent of the actual multicast routing protocol in use.
There are no constraints on this MIB.
MPLS-LDP-MIB
The MPLS-LDP-MIB provides management information for the Multiprotocol Label Switching (MPLS) Label Distribution Protocol (LDP), which is used by label switching routers (LSRs) to communicate the definitions of labels that each router is using. The router supports the IETF draft version of this MIB (draft-ietf-mpls-ldp-mib-08.txt).
For detailed information about this MIB, see its feature module description at the following URL:
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
MPLS-LSR-MIB
The MPLS-LSR-MIB provides configuration and performance monitoring information to manage label switched paths (LSPs) through a label switching router (LSR) remotely. The MPLS-LSR-MIB enables you to display the contents of the the Label Forwarding Information Base (LFIB).
For detailed information about this MIB, see its feature module description at the following URL:
MIB Constraints
Table 3-33 lists the constraints that the router places on objects in the MPLS-LSR-MIB. For detailed definitions of MIB objects, see the MIB.
MPLS-TE-MIB
The MPLS-TE-MIB enables the Cisco 10000 Series to perform traffic engineering for MPLS tunnels. The Cisco 10000 Series supports the IETF draft version of this MIB (draft-ietf-mpls-te-mib-05.txt).
For detailed information about this MIB, see its feature module description at the following URL:
MIB Constraints
Table 3-34 lists the constraints that the router places on objects in the MPLS-TE-MIB. For detailed definitions of MIB objects, see the MIB.
MPLS-VPN-MIB
The MPLS VPN technology allows service providers to offer intranet and extranet VPN services that directly connect their customers' remote offices to a public network with the same security and service levels that a private network offers.
The MPLS-VPN-MIB contains objects that are used to:
•
•
•
•
For detailed information about this MIB, see its feature module description at the following URL:
MIB Constraints
Table 3-35 lists the constraints that the router places on objects in the MPLS-VPN-MIB. For detailed definitions of MIB objects, see the MIB.
MSDP-MIB
The MSDP-MIB contains objects to monitor the Multicast Source Discovery Protocol (MSDP). The MIB can be used with SNMPv3 to remotely monitor MSDP speakers.
For more information about this MIB, see its feature module description at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5
/dt5msdp.htmMIB Constraints
Table 3-36 lists the constraints that the router places on objects in the MSDP-MIB. For detailed definitions of MIB objects, see the MIB.
Table 3-36 MSDP-MIB Constraints
Not supported.
•
Not supported.
All other MIB objects
Read-only.
NOTIFICATION-LOG-MIB
The NOTIFICATION-LOG-MIB contains information about SNMP notifications (traps and informs).
MIB Constraints
The objects in this MIB are read-only. You must configure SNMP notification log functionality through CLI commands such as snmp mib notification-log default, snmp mib notification-log default disable, snmp mib notification-log globalageout, and snmp mib notification-log globalsize.
You can view the contents of a notification log through SNMP by reading the nlmLogTable; or, you can use the CLI command show snmp mib-notification log.
Table 3-37 lists the constraints that the router places on objects in the NOTIFICATION-LOG-MIB. For detailed definitions of MIB objects, see the MIB.
OLD-CISCO-CHASSIS-MIB
The OLD-CISCO-CHASSIS-MIB describes chassis objects in devices running an older implementation of the Cisco IOS operating system. Those objects are now described in the ENTITY-MIB. This MIB is deprecated.
OLD-CISCO-CPU-MIB
The OLD-CISCO-CPU-MIB describes CPU usage and active system processes on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-INTERFACES-MIB
The OLD-CISCO-INTERFACES-MIB contains objects to manage interfaces on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-IP-MIB
The OLD-CISCO-IP-MIB contains objects to manage IP on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-MEMORY-MIB
The OLD-CISCO-MEMORY-MIB contains objects that describe memory pools on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-SYSTEM-MIB
The OLD-CISCO-SYSTEM-MIB provides information about system resources on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-TCP-MIB
The OLD-CISCO-TCP-MIB contains information about the TCP implementation on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OLD-CISCO-TS-MIB
The OLD-CISCO-TS-MIB contains objects to manage terminals and terminal lines on devices running an older implementation of the Cisco IOS operating system. This MIB is deprecated.
OSPF-MIB
The OSPFM-MIB contains objects to manage Protocol Independent Multicast (PIM) on the router. The OSPF-MIB supports the latest RFC 1850 and adds the latest draft extensions.
PIM-MIB
The PIM-MIB contains objects to manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.
There are no constraints on this MIB.
QINQ-VLAN-MIB
The QINQ-VALN-MIB contains objects to manage Protocol Independent Multicast (PIM) on the router. The MIB is extracted from RFC 2934.
There are no constraints on this MIB.
RFC1213-MIB
The RFC1213-MIB defines the second version of the Management Information Base (MIB-II) for use with network-management protocols in TCP-based internets. Theis platform supports the IP part of RFC1213 and a draft of RFC2011 (draft-ietf-ipngwg-rfc2011-update-00), the CISCO-IETF-IP-MIB.
There are no constraints on this MIB.
RFC1253-MIB
The RFC1253-MIB contains objects to manage version 2 of the Open Shortest Path First (OSPF) protocol.
There are no constraints on this MIB.
RFC1315-MIB
The RFC1315-MIB contains objects to manage a Frame Relay data terminal equipment (DTE) interface, which consists of a single physical connection to the network with many virtual connections to other destinations and neighbors. The MIB contains the objects used to manage:
•
•
•
MIB Constraints
Table 3-38 lists the constraints that the router places on objects in the RFC1315-MIB. For detailed definitions of MIB objects, see the MIB.
RMON-MIB
The RMON-MIB contains objects to remotely monitor devices in the network.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
RS-232-MIB
The RS232-MIB contains objects to manage RS-232-like hardware interfaces and devices.
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
RSVP-MIB
The RSVP-MIB contains objects to manage the Resource Reservation Protocol (RSVP).
Although this MIB is included in the Cisco IOS software image, the MIB is currently not supported for broadband configurations.
SNMP-FRAMEWORK-MIB
The SNMP-FRAMEWORK-MIB contains objects that describe the SNMP management architecture.
There are no constraints on this MIB.
SNMP-MPD-MIB
The SNMP-MPD-MIB contains statistics for SNMP message processing and dispatching processes on the router.
There are no constraints on this MIB.
SNMP-NOTIFICATION-MIB
The SNMP-NOTIFICATION-MIB contains managed objects for SNMP v3 notifications. The MIB also defines a set of filters that limit the number of notifications generated by a particular entity (snmpNotifyFilterProfileTable and snmpNotifyFilterTable).
Objects in the snmpNotifyTable are used to select entities in the SNMP-TARGET-MIB snmpTargetAddrTable and specify the types of SNMP notifications those entities are to receive.
There are no constraints on this MIB.
SNMP-PROXY-MIB
The SNMP-PROXY-MIB contains managed objects to remotely configure the parameters used by an SNMP entity for proxy forwarding operations. The MIB contains a single table, snmpProxyTable, which defines the translations to use to forward messages between management targets.
There are no constraints on this MIB.
SNMP-TARGET-MIB
The SNMP-TARGET-MIB contains objects to remotely configure the parameters used by an entity to generate SNMP notifications. The MIB defines the addresses of entities to send SNMP notifications to, and contains a list of tag values that are used to filter the notifications sent to these entities (see the SNMP-NOTIFICATION-MIB).
There are no constraints on this MIB.
SNMP-USM-MIB
The SNMP-USM-MIB contains objects that describe the SNMP User-based Security Model.
There are no constraints on this MIB.
SNMPv2-MIB
The SNMPv2-MIB contains objects to manage SNMP v2 entities on the router.
There are no constraints on this MIB.
SNMP-VACM-MIB
The SNMP-VACM-MIB contains objects that describe the view-based access control model for SNMP.
Note
Router(config)# snmp-server view abcview internet included
Router(config)# snmp-server group abcgroup v3 noauth read abcview write abcview
notify abcview
Router(config)# snmp-server user abcuser abcgroup v3There are no constraints on this MIB.
SONET-MIB
The SONET-MIB contains objects to manage SONET/SDH interfaces on the router.
There are no constraints on this MIB.
TCP-MIB
The TCP-MIB contains objects to manage the Transmission Control Protocol (TCP) on the router.
There are no constraints on this MIB.
UDP-MIB
The UDP-MIB contains objects to manage the User Datagram Protocol (UDP) on the router.
There are no constraints on this MIB.
