Cisco CMTS Router MIB Overview
This chapter provides an overview of the Cisco Cable Modem Termination System (CMTS) router. This chapter contains the following topics:
A MIB is a database of objects managed on a device using the SNMP manager. The managed objects or variables can be set or read to provide information on the network devices and interfacesand are organized hierarchically. The objects in a MIB are organized hierarchically, which are identified by object identifiers (OID) defined by IETF and other organizations. Our implementation of SNMP uses MIBs that conform to the MIB II definition that is described in RFC 1213.
Objects can refer to a physical device (such as a line card or clock card or shared port adapter), a software parameter (such as an IP address or operation mode), or a run-time statistic (such as number of packets passed or temperature). When the device contains multiple objects of the same type, it appends a unique instance number to the end of the OID, so that the SNMP manager and agent can distinguish between the different objects.
MIBs can contain two types of managed objects:
- Scalar objects—Define a single object instance (for example, ifNumber in the IF-MIB and bgpVersion in the BGP4-MIB).
- Tabular objects—Define multiple related object instances that are grouped together in MIB tables (for example, ifTable in the IF-MIB defines the interfaces on the router). Each row in a MIB table describes all of the parameters for a particular object (such as IP address, clock speed, number of ports, and so forth). SNMP managers can read or set all of the information in a row with one request.
Typically, each row in a table is identified by a unique index number. Depending on the table, this index either could reflect a physical attribute (such as the slot number in a chassis or port number on a card) or it could be an arbitrary number (such as is used for tables that list error messages or packet statistics).
Each row also has a status object that shows whether the row is created, activated, deactivated, or deleted. When an SNMP manager creates a new row, it typically sets the row’s status to create and then populates the row with the desired parameters. The SNMP agent does not use the objects in a row until the SNMP manager sets the row’s status to activate. This ensures that the SNMP agent does not try to use a row’s parameters until the SNMP manager has finished creating the row and entered all of the row’s required parameters.
Benefits of MIB Enhancements
The Cisco CMTS uBR router enhanced management feature allows the router to be managed through the Simple Network Management Protocol (SNMP). The feature also expands the number of Management Information Bases (MIBs) included with the router.
Using the Cisco CMTS uBR router enhanced management feature, you can:
- Manage and monitor Cisco CMTS router resources through an SNMP-based network management system (NMS)
- Use SNMP set and get requests to access information in Cisco CMTS uBR router MIBs
- Reduce the amount of time and system resources required to perform functions such as inventory management
Other benefits include:
- A standards-based technology (SNMP) for monitoring faults and performance on the router
- Support for all SNMP versions (SNMPv1, SNMPv2c, and SNMPv3)
- Notification of faults, alarms, and conditions that might affect services
- A way to access router information other than through the command line interface (CLI)
The SNMP specifications define MIBs in a highly structured hierarchical format, in which MIBs that are lower in the hierarchy use objects that are defined by MIBs higher up in the hierarchy. Each MIB includes a section titled “IMPORTS” that lists the objects it uses that are defined by other MIBs.
For example, the IF-MIB, which defines standard objects for router interfaces, uses the following IMPORT block:
MODULE-IDENTITY, OBJECT-TYPE, Counter32, Gauge32, Counter64,
Integer32, TimeTicks, mib-2,
NOTIFICATION-TYPE FROM SNMPv2-SMI
PhysAddress, TruthValue, RowStatus,
TimeStamp, AutonomousType, TestAndIncr FROM SNMPv2-TC
NOTIFICATION-GROUP FROM SNMPv2-CONF
snmpTraps FROM SNMPv2-MIB
IANAifType FROM IANAifType-MIB;
This section shows that the IF-MIB uses objects that are defined by the SNMPv2-SMI, SNMPv2-TC, SNMPv2-CONF, SNMPv2-MIB, and IANAifType-MIB MIBs. To use the IF-MIB with your SNMP management software, you must load these other MIBs as well.
Typically, most SNMP managers use the IMPORT blocks in the MIBs to automatically determine the order in which the MIBs must be loaded. However, if you are manually loading MIBs, you must do so in the proper order.
To determine the dependencies among MIBs, you can use the “View and Download MIBs” tool, which is part of the SNMP Object Navigator on the Cisco IOS MIB Tools page. This URL takes you to the MIB Locator:
MIBs on the Cisco CMTS can be arranged in the following categories:
- SNMP standard MIBs—Part of the SNMPv1, SNMPv2c, and SNMPv3 specifications and must be supported by any agent supporting SNMP network management. These MIBs provide the framework for SNMP management, defining common objects and interfaces.
- Internet standard MIBs—Provide generic definitions for objects that provide information about commonly used protocols, such as IP, TCP, and Internet Control Message Protocol (ICMP). These MIBs are typically defined by the IETF as Internet-Drafts and Request for Comments (RFCs).
- Cisco platform and network-layer enterprise MIBs—Provide information that is specific to Cisco platforms. These MIBs can extend standard MIBs by providing additional related information, or they can provide information about features that are specific to Cisco platforms. Typically, the same Cisco-specific MIB is used on all Cisco platforms that implement the MIB’s particular feature. These MIBs are also typically updated whenever the related feature is updated in the Cisco IOS software.
- Cable-specific MIBs—Provide information about the cable interfaces and related information on the Cisco CMTS platforms. These MIBs can be divided into the following subcategories:
– DOCSIS-specified MIBs—Defined by CableLabs, which created and maintains the DOCSIS specification. When the DOCSIS specifications have been finalized, these MIBs are also submitted to the IETF and are eventually released as RFCs. These MIBs can also include other services, such as DOCSIS Set-Top Gateway (DSG), as CableLabs continues to develop specifications for these additional cable services.
– Cisco-specific cable MIBs—Provide extensions to the DOCSIS MIBs for features that are specific to Cisco platforms.
- Deprecated MIBs—Supported in earlier releases of Cisco IOS software but have been replaced by more standardized, scalable MIBs. Network management applications and scripts should convert to the replacement MIBs as soon as possible, because deprecated MIBs could be removed without notice.
An object identifier (OID) uniquely identifies a MIB object on a managed router or other network device. All OIDs are arranged in a hierarchical order, with top-level OIDs assigned by standards organizations such as IETF, ISO, and ITU. Lower-level OIDs are assigned by individual vendor organizations.
Each level in an OID is assigned both a number and a name. The hierarchical structure of the OIDs allow for easy translation between the number and name forms of an OID.
For example, SNMP standard MIBs that are intended for use by all vendors typically start with “220.127.116.11.2.1”, which translates as follows:
Typically, vendor-specific MIBs have OIDs that start with “18.104.22.168.4.1”, which translates as follows:
Cisco Systems was assigned the next OID of “9”, so most OIDs for items that are specific to Cisco platforms start with “22.214.171.124.4.1.9”:
For illustrative purposes, the OIDs above are shown with both number and name forms combined. Typically, only the name or number for a level is used. However, names and numbers can be mixed in the same OID. For example, the top-most Cisco-specific OID could also be given as either “126.96.36.199.4.1.cisco” or “iso.org.dod.internet.private.enterprises.9”.
To translate OIDs between their name and number format, and to display the location of any OID in the OID tree, you can use the SNMP Object Navigator on the Cisco IOS MIB Tools page. This URL takes you to the MIB Locator:
For a listing of all of the objects and OIDs that are included in any particular MIB, you can download the text files at the following URL:
The Cisco CMTS routers can be managed through SNMP, which is an application-layer protocol that provides a standardized framework and a common language for monitoring and managing devices in a network. The SNMP framework has the following main parts:
- An SNMP manager—A system used to control and monitor the activities of network hosts by using SNMP commands. The most common managing system is called a network management system (NMS), which can be either a standalone device that is dedicated to network management, or a workstation that is running network management applications. Many network management applications are available and range from simple, freely available command-line applications to feature-rich, commercial products with sophisticated graphical user interfaces.
- An SNMP agent—A software component in a managed device that maintains the SNMP data and communicates with the SNMP manager. Typically, the agent is configured to respond only to one or more specific SNMP managers, so that unauthorized parties do not have access to the device. On the Cisco CMTS, the Cisco IOS software runs the SNMP agent software, but it does not become active until it is enabled using the command-line interface (CLI).
- Management Information Base (MIB)—Objects that can be managed by SNMP are defined in MIBs, which are ASCII text files in a structured format. MIBs that are standardized for use industry-wide among multiple vendors are created and maintained by organizations such as the Internet Engineering Task Force (IETF) and CableLabs. Vendors, such as Cisco, also create vendor-specific MIBs to manage vendor-specific platforms and features. On the Cisco CMTS, MIBs are part of the Cisco IOS software image. Typically, each new Cisco IOS software release includes MIBs that are new or have been modified.
The SNMP manager communicates with the SNMP agent in the following ways:
- GET requests—The SNMP manager obtains information from the device by sending GET requests to the agent. The manager can obtain this information one object at a time using single GET requests.
- SET requests—The SNMP manager configures the device by sending SET requests to the agent. The manager can configure one item at a time using single SET requests, or it can configure multiple parameters using a BULK-SET request.
- Notifications—The SNMP agent asynchronously informs the manager that specific events have occurred by using a trap or inform message (depending on the version of SNMP being used). The network administrator configures the agent for the types of traps and informs it should send. These can range from purely informational messages, such as traffic statistics, to important messages that warn of critical situations and errors, such as a card failure.
An SNMP agent can notify the SNMP manager when important system events occur, such as the following:
- An interface or card starts or stops running
- Temperature thresholds are crossed
- Authentication failures occur
When an agent detects an alarm condition, the agent:
- Logs information about the time, type, and severity of the condition
- Generates a notification message, which it then sends to a designated IP host
SNMP notifications are sent as either:
- Traps—Unreliable messages, which do not require receipt acknowledgment from the SNMP manager.
- Informs—Reliable messages, which are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps.
The Cisco implementation of SNMP uses the definitions of SNMP traps described in RFC 1215.
When an agent detects an alarm condition, it logs information about the time, type, and severity of the condition and generates a notification message, which it then sends to a designated IP host. SNMP notifications can be sent as either traps or informs. See Chapter 4, “Enabling Notifications”, for instructions on how to enable traps on the Cisco CMTS Universal Broadband Series Router. Use the snmp-server host command to specify whether to send SNMP notifications as traps or informs. See “Monitoring Notifications,” for information about Cisco CMTS uBR router notifications.
Cisco IOS software supports the following versions of SNMP:
- SNMPv1—The Simple Network Management Protocol: A full Internet standard, defined in RFC 1157. Security is based on community strings.
- SNMPv2c—The community-string-based administrative framework for SNMPv2. SNMPv2c is an update of the protocol operations and data types of SNMPv2c (SNMPv2 classic), and uses the community-based security model of SNMPv1. In particular, SNMPv2c adds support for 64-bit counters.
- SNMPv3—Version 3 of SNMP. SNMPv3 uses the following security features to provide secure access to devices:
– Message integrity—Ensuring that a packet has not been tampered with in transit.
– Authentication—Determining that the message is from a valid source.
– Encryption—Scrambling the contents of a packet to prevent it from being learned by an unauthorized source.
Tip We recommend using SNMPv3 wherever possible because of its superior security features.
SNMPv1 and SNMPv2c
Both SNMPv1 and SNMPv2c use a community-based form of security. The community of managers who are able to access the agent MIB is defined by an IP address access control list (ACL) and password.
SNMPv2c support includes a retrieval mechanism and more detailed error message reporting to management stations. The retrieval mechanism supports the retrieval of tables and large quantities of information, minimizing the number of round-trip transmissions required.
SNMPv2c improved error handling support. SNMPv1 reported all error conditions using a single error code, but SNMPv2c includes a number of expanded error codes that use different error types to distinguish between different kinds of error conditions.
SNMPv2 also reports three different types of exceptions:
- No such object exceptions
- No such instance exceptions
- End of MIB view exceptions
SNMPv3 improves security for SNMP communications by using encryption and by defining security models and security levels:
- Encryption—SNMPv3 supports several industry-standard encryption standards, including the Data Encryption Standard (DES).
- Security Model—An authentication strategy for a user and for the group in which the user resides. Different users can be assigned a different security model, depending on the organization’s security structure and needs.
- Security Level—Permitted level of security within a security model. SNMPv1 and SNMPv2c used only a two-stage security level: read-only and read-write. SNMPv3 provides a much greater ability to customize the permission levels for different users.
A combination of a security model and a security level determines which security mechanism is employed when handling an SNMP packet.
SNMP Security Models and Levels
Table 1-1 describes the security models and levels provided by the different SNMP versions.
Table 1-1 SNMP Security Models and Levels
Uses match on community string for authentication.
Uses match on community string for authentication.
Uses match on username for authentication.
MD5 or SHA
Provides authentication based on HMAC-MD5 or HMAC-SHA algorithm.
MD5 or SHA
Provides authentication based on HMAC-MD5 or HMAC-SHA algorithm. Also provides DES 56-bit encryption based on CBC-DES (DES-56) standard.
You must configure the SNMP agent to use the version of SNMP supported by the management station. An agent can communicate with multiple managers; for this reason, you can configure the Cisco IOS software to support communications with one management station using the SNMPv1 protocol, one using the SNMPv2c protocol, and another using SNMPv3.
Note We recommend using SNMPv3 for all SNMP applications, because of its significant security improvements. In addition, SNMPv3 supports 64-bit counters, which are not supported in SNMPv1. If you use SNMPv1, you can not view any objects that are defined as 64-bit counters.
Requests for Comments
MIB modules are typically defined in Request for Comments (RFC) documents that have been submitted to the Internet Engineering Task Force (IETF) for formal discussion and approval. RFCs are written by individuals or groups for consideration by the Internet Society and the Internet community as a whole.
Before being given RFC status, recommendations are first published as Internet Draft (I-D) documents. RFCs that have become recommended standards are also labeled as standards (STD) documents. For more information, see the Internet Society and IETF websites ( http://www.internetsociety.org/ and http://www.ietf.org).
We provide private MIB extensions with each Cisco system. Cisco enterprise MIBs comply with the guidelines described in the relevant RFCs unless otherwise noted in the documentation.
Related Information and Useful Links
The following URLs provide access to general information about Cisco MIBs. Use these links to access MIBs for download, and to access related information (such as application notes and OID listings).
Cisco Technical Support Information and FAQs
The following URLs provide access to SNMP information developed by the Cisco Technical Assistance Center (TAC):
Cisco CMTS Documentation
The following Cisco documents provide information about configuring the cable-specific parameters on the Cisco CMTS router:
Specifications and Standards
The following are standards and specifications that are used on DOCSIS cable networks. Some of these standards define the MIBs and other aspects of network management that are required for DOCSIS networks.
Note Many of these standards do not directly affect SNMP operations, but they define operational modes and parameters that must be understood to be able to interpret many of the tables and objects that are monitored and managed through SNMP.