Preface

Preface

This guide describes the implementation of the Simple Network Management Protocol (SNMP) for the Cisco Cable Modem Termination System (CMTS) routers.

SNMP provides a set of commands for setting and retrieving the values of operating parameters on the router. Router information is stored in a virtual storage area called a Management Information Base (MIB). The MIB contains objects that describe router components and provides information about the status of these components.

This preface provides an overview of this guide with the following sections:

Document Revision History

This guide contains MIB information of:

  • Cisco IOS Release 12.2(33)SCI
  • Cisco IOS Release 12.2(33)CX
  • All earlier releases

For MIB information of later releases, use the Cisco MIB Locater tool.

The following Revision History tables record technical changes, additions, and corrections to this document.

 

Cisco IOS Release
Cisco RF Switch Firmware Version
Part Number
Publication Date
Change Summary

12.2(33)CX

3.92

OL-15724-12

June 2014

The following MIBs are added:

12.2(33)SCG5

3.92

OL-15724-11

June 2013

The CISCO-DOCS-EXT-MIB is updated with the following MIB tables:

  • cdxCmtsMtcCmTable
  • cdxCmtsUscbSflowTable

12.2(33)SCH

3.92

OL-15724-10

May 2013

Updated the following MIBs:

12.2(33)SCG2

3.92

OL-15724-09

January 2013

The CISCO-DOCS-EXT-MIB is updated:

  • MIB objects and traps added for wideband resiliency feature to represent the threshold values configuration.
  • MIB objects added for information about the physical channel interface and the primary channel interface.
  • Four 64 counter additional counter added to the cdxCmtsServiceExtTable.

12.2(33)SCG

3.92

OL-15724-08

July 2012

The CISCO-CABLE-WIDEBAND-MIB is modified:

  • Added the ccwbRFChannelTable.
  • Added the SFP Link Status changes for the CISCO-CABLE-WIBEBAND MIB in Cable MIB Notifications.

The Background Synchronization feature is introduced.

12.2(33)SCF

3.92

OL-15724-07

June 2011

The ifIndex object of MIB objects that pointed to the modular or the integrated interfaces now points to the cable interface and RF channels SNMP IF Index of the uBR-MC3GX60V, UBR-MC20X20V and uBR-MC88V line cards, and SPAs. Following are the MIBs and their tables where the ifIndex object points to the RF channel SNMP IF index:

  • DOCS-IF-MIB—docsIfDownstreamChannelTable, docsIfCmtsChannelUtilizationTable, and docsIfCmtsDownChannelCounterTable
  • CLAB-TOPO-MIB—clabTopoChFnCfgTable
  • CISCO-CABLE-WIDEBAND-MIB—CcwbFiberNodeTableDOCS-DRF-MIB—docsDrfDownstreamTable, docsDrfDownstreamCapabilitiesTable, and docsDrfChannelBlockTable
  • ENTITY-MIB—The ifIndex object in addition to pointing to the interfaces, now points to the RF channel SNMP IF Index in table EntAliasMappingTable
  • IF-MIB—Attributes are added to point to the RF channel interfaces in the tables ifTable and ifXtable

12.2(33)SCE

3.92

OL-15724-06

November 2010

  • Updated ENTITY-MIB to include MIB attributes for uBR-MC3GX60V line card, ports, controller, and SFP.
  • Updated CISCO-DOCS-EXT-MIB to include cdxCmCpeDeleteNow object in cdxCmCpeTable.

12.2(33)SCD2

3.92

OL-15724-05

May 2010

12.2(33)SCD

3.92

OL-15724-04

March 2010

  • Added a new table, docsIf3CmtsCmUsStatusTable, under DOCS-QOS3-MIB that defines attributes to support multiple upstream channel.

12.2(33)SCC

3.90

OL-15724-03

November 2009

  • Added the following MIBs in this release:

blank.gif CISCO-CABLE-L2VPN-MIB

blank.gif CISCO-IETF-PW-MIB

blank.gif CISCO-IETF-PW-MPLS-MIB

blank.gif DOCS-IF-M-CMTS-MIB

blank.gif DOCS-LOADBAL3-MIB

blank.gif DOCS-LOADBALANCING-MIB

blank.gif DOCS-MCAST-AUTH-MIB

blank.gif DOCS-SEC-MIB

blank.gif DOCS-SUBMGT3-MIB

blank.gif ENTITY-SENSOR-MIB

blank.gif MPLS-LSR-MIB

blank.gif MPLS-LDP-MIB

blank.gif MPLS-TE-MIB

blank.gif MPLS-TE-STD-MIB

  • Updated the following MIBs in this release:

blank.gif CISCO-CABLE-ADMISSION-CTRL-MIB

blank.gif CISCO-CABLE-SPECTRUM-MIB

blank.gif CISCO-CABLE-WIDEBAND-MIB

blank.gif CISCO-ENTITY-SENSOR-MIB

blank.gif DOCS-BPI-PLUS-MIB

blank.gif DOCS-CABLE-DEVICE-MIB

blank.gif DOCS-QOS-MIB

blank.gif DOCS-IF-MIB

blank.gif DOCS-DRF-MIB

blank.gif DOCS-DSG-IF-MIB

blank.gif DOCS-QOS3-MIB

blank.gif DTI-MIB

blank.gif ENTITY-MIB

blank.gif IF-MIB

12.2(33)SCB

3.90

OL-15724-02

December 2008

  • Added the following MIBs to support DOCSIS 3.0:

blank.gif CLAB-TOPO-MIB

blank.gif DOCS-QOS-MIB

blank.gif DOCS-QOS3-MIB

blank.gif DOCS-DRF-MIB

blank.gif DOCS-QOS3-MIB

blank.gif DOCS-IETF-CABLE-DEVICE-NOTIFICATION-MIB

blank.gif DOCS-IETF-BPI2-MIB

blank.gif DOCS-IETF-QOS-MIB

  • Added the following MIBs to support DOCSIS 2.0:

blank.gif DOCS-IFEXT2-MIB

blank.gif DOCS-TEST-MIB

12.2(33)SCA

3.90

OL-15724-01

February 2008

  • Cisco RF Switch Firmware Version 3.90, installed on Cisco RF Switch, provides the following changes or enhancements to be used with Cisco IOS release 12.3(21)BC through Cisco IOS release 12.2(33)SCA:

blank.gif The updated Firmware version 3.90 resolves the Address Resolution Protocol (ARP) cache handling issue and ensures ARP updates after timeout.

blank.gif Version 3.90 provides enhancement in the telnet server to negotiate with the client regarding the desired settings of the echo mode. The user can set the initial state of the local echoing using the set telnet echo command. However, the telnet server can bypass this and use the client settings if the echo options negotiation is supported.

blank.gif In version 3.90, the Trivial File Transfer Protocol (TFTP) is enhanced to display the number of bytes as transfer progresses.

blank.gif In version 3.90, the command-line interface (CLI) task priority is pushed below that of the network task. From this release, ping command has higher priority than an interface command.

blank.gif In version 3.90, the command show version is modified so that the full cyclic redundancy check (CRC) validation is not done on the flash contents. It now validates only the file header contents. To perform a full CRC check, use the command show files.

blank.gif Version 3.90 allows RF Switch to accept passwords that match CLI keywords. In version 3.80, they were not accepted and shown as Invalid Syntax.

blank.gif Version 3.90 updates real-time operating system (RTOS) kernel to be compatible with new IP stack.

 

 

 

 

  • Added a new MIB, DOCS-L2VPN-MIB, in Chapter 3, “MIB Specifications” to support L2VPN support over Cable. The Layer 2 VPN (L2VPN) Support over Cable feature on the Cisco CMTS provides point-to-point Transparent LAN Service (TLS) to support the Business Services over DOCSIS (BSOD) CableLabs specification. Key features of L2VPN support are:

blank.gif Supports point-to-point L2VPN forwarding mode.

blank.gif Supports up-to 4 VPN IDs per cable modem (CM).

  • Supports multiple upstream service flows (SFs) per CM, with one or more SFs belonging to the same VPN ID.

blank.gif Supports a single Ethernet Network System Interface (NSI) that serves as a trunking port for one or more L2VPN tunnels on the Cisco CMTS router.

blank.gif Supports Baseline Privacy Interface Plus (BPI+) encryption using primary SecurityAssociation Identifier (SAID) of the CM.

blank.gif Supports L2VPN encodings in the CM configuration file and CM registration (REG-REQ with L2VPN encoding).

blank.gif Supports upstream L2VN tunnel in support of per-CM and per-SF forwarding.

blank.gif Supports synchronization and recovery of the L2VPN database and upstream and downstream SFs during PRE2 NSF/SSO and N+1 line card redundancy switchovers.

blank.gif Supports Quality of Service (QoS) in upstream and downstream.

blank.gif Supports stacked IEEE 802.1q tags.

 

 

 

 

blank.gif Supports exclusion of traffic from the L2VPN tunnel for a single Embedded Service/Application Functional Entity (eSAFE) host.

blank.gif Supports Layer 2 classifier via Cable Modem Interface Mask (CMIM) and priority.

blank.gif Supports detection of provisioning errors such as duplicate VLAN IDs across CMs or existing VLAN IDs in use and moves a CM offline with a corresponding error message.

blank.gif Supports coexistence of L2VPN and non-L2VPN traffic on the same RF MAC domain, with non-L2VPN traffic isolation from other tunnel traffic.

  • Added three new MIBs (CISCO-TAP2-MIB, CISCO-IP-TAP-MIB, and CISCO-802-TAP-MIB) in Chapter 3, “MIB Specifications” to support Service Independent Intercept (SII) on the Cisco CMTS. The SII feature enhances the current Lawful Intercept (LI) capability for the Cisco uBR7246VXR and Cisco uBR10012 Universal Broadband Routers using Simple Network Management Protocol Version 3 (SNMPv3). SII extends this LI capability in Cisco IOS Release 12.2(33)SCA by adding support for CPE-based and CM-based MAC intercepts using SNMPv3. SII is designed to provide data intercepts via SNMPv3, while PacketCable intercepts are designed for voice IP intercepts using a Common Open Policy Service (COPS) interface. Key features of SII feature are:

blank.gif Allows multiple law enforcement agencies (LEAs) to run a lawful intercept on the same target without each other’s knowledge.

blank.gif Does not affect subscriber services on the router.

blank.gif Cannot be detected by the target.

 

 

 

 

blank.gif Allows LEAs to perform lawful intercepts without the knowledge of service providers.

blank.gif Uses SNMPv3 and security features like the View-based Access Control Model (SNMP-VACM-MIB) and User-based Security Model (SNMP-USM-MIB) to restrict access to lawful intercept information and components.

blank.gif Supports intercepts of Layer 3 and Layer 2 traffic.

blank.gif Supports Layer 2 intercepts for upstream and downstream traffic.

blank.gif Hides information about lawful intercepts from all but the most privileged users. An administrator must set up access rights to enable privileged users to access lawful intercept information.

blank.gif Provides two secure interfaces for performing an intercept: one for setting up the wiretap and another for sending the intercepted traffic to the mediation device.

blank.gif Coexists with Packet Intercept (PI). To support Packet Intercept (PI) in a PacketCable environment for voice intercepts, you must enable PacketCable operation on the CMTS and perform any other related PacketCable configurations as required.

Audience

This guide is intended for system and network administrators who must configure the Cisco CMTS Router for operation and monitor its performance in the network.

This guide may also be useful for application developers who are developing management applications for the router.

Organization

This guide contains the following chapters:

 

Chapter
Description

Chapter 1, “Cisco CMTS Router MIB Overview”

Provides background information about SNMP and its implementation on Cisco CMTS routers.

Chapter 2, “Configuring SNMP and MIB Support”

Provides instructions for configuring SNMP management support on the router.

Chapter 3, “MIB Specifications”

Describes each MIB included in the software image. Each description lists any constraints as to how the MIB is implemented on the router.

Chapter 4, “Monitoring Notifications”

Describes the SNMP traps and notifications supported by the router.

Appendix A, “Using Cisco CMTS MIBs”

Describes how to perform common tasks on the router.

Chapter B, “Relationship Between MIB Objects and CLI Show Commands”

Provides a cross-reference between commonly used objects in the MIBs and the related cable-related show commands.

Terminology and Definitions

This section discusses conventions and terminology used in this guide.

  • Alarm—In SNMP, the word alarm is commonly misused to mean the same as a trap (see the Trap definition below). Alarm represents a condition which causes an SNMP trap to be generated.
note.gif

Noteblank.gif Many commands use the word traps in the command syntax. Unless there is an option in the command to select either traps or informs, the keyword traps refers to traps, informs, or both. Use the snmp-server host and snmp-server enable notification command to specify whether to send SNMP notifications as traps or informs.


  • Element Management System (EMS)—An EMS manages a specific portion of the network. For example, the SunNet Manager, an SNMP management application, is used to manage SNMP-manageable elements. Element Managers may manage asynchronous lines, multiplexers, Private Automatic Branch Exchange (PABX), proprietary systems, or an application.
  • Inform—Reliable SNMP notifications that are stored in memory until the SNMP manager issues a response. Informs use more system resources than traps. The SNMP Inform mechanism can be used when a reliable fault reporting system is required.
  • Lawful Intercept (LI)—The term used to describe the process by which law enforcement agencies conduct electronic surveillance as authorized by judicial or administrative order. Legislation and regulations are increasingly being adopted that require service providers (SPs) to design and implement their networks to explicitly support authorized electronic surveillance.
  • Management Information Base (MIB)—The objects that are available in an SNMP-managed device. The information is represented in Abstract Syntax Notation 1 (ASN.1). This is a way of logically grouping data so that it is easily understood by all.
  • MIB-II—The successor to MIB-I, which was the original standard SNMP MIB.
  • Multiprotocol Label Switching (MPLS)—MPLS is the standardized version of the Cisco original tag-switching proposal. It uses a label-forwarding paradigm (forward packets based on labels).
  • Remote Network Monitoring (RMON) MIB—SNMP MIB for remote management of networks. While other MIBs are usually created to support a network device with primary function other than management, RMON was created to provide management of a network. RMON is one of the many SNMP-based MIBs that are of IETF Standards.
  • Simple Network Management Protocol (SNMP)—An application layer protocol that allows you to remotely manage networked devices. The simple in SNMP is only in contrast to protocols that are thought to be even more complex than SNMP. SNMP consists of the following components: a management protocol, a definition of management information and events, a core set of management information and events, and a mechanism and approach used to manage the use of the protocol including security and access control.
  • Synchronous Optical Network (SONET)—A physical layer interface standard for fiber-optic transmission.
  • Trap—A device-initiated SNMP notification message. The contents of the message might be simply informational, but it is mostly used to report real-time trap information. Traps can be used in conjunction with other SNMP mechanisms, as in trap-directed polling.
  • User Datagram Protocol (UDP)—A connectionless, non-reliable IP-based transport protocol.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.