The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
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:
This guide contains MIB information of:
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.
|
|
|
|
|
---|---|---|---|---|
The CISCO-DOCS-EXT-MIB is updated with the following MIB tables: |
||||
The CISCO-DOCS-EXT-MIB is updated: |
||||
The CISCO-CABLE-WIDEBAND-MIB is modified:
The Background Synchronization feature is introduced. |
||||
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:
|
||||
|
||||
|
||||
|
||||
– CISCO-CABLE-ADMISSION-CTRL-MIB – DTI-MIB – IF-MIB |
||||
– The updated Firmware version 3.90 resolves the Address Resolution Protocol (ARP) cache handling issue and ensures ARP updates after timeout. – 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. – In version 3.90, the Trivial File Transfer Protocol (TFTP) is enhanced to display the number of bytes as transfer progresses. – 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. – 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. – 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. – Version 3.90 updates real-time operating system (RTOS) kernel to be compatible with new IP stack. |
||||
– Supports point-to-point L2VPN forwarding mode. – Supports up-to 4 VPN IDs per cable modem (CM).
– 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. – Supports Baseline Privacy Interface Plus (BPI+) encryption using primary SecurityAssociation Identifier (SAID) of the CM. – Supports L2VPN encodings in the CM configuration file and CM registration (REG-REQ with L2VPN encoding). – Supports upstream L2VN tunnel in support of per-CM and per-SF forwarding. – Supports synchronization and recovery of the L2VPN database and upstream and downstream SFs during PRE2 NSF/SSO and N+1 line card redundancy switchovers. – Supports Quality of Service (QoS) in upstream and downstream. |
||||
– Supports exclusion of traffic from the L2VPN tunnel for a single Embedded Service/Application Functional Entity (eSAFE) host. – Supports Layer 2 classifier via Cable Modem Interface Mask (CMIM) and priority. – 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. – Supports coexistence of L2VPN and non-L2VPN traffic on the same RF MAC domain, with non-L2VPN traffic isolation from other tunnel traffic.
– Allows multiple law enforcement agencies (LEAs) to run a lawful intercept on the same target without each other’s knowledge. |
||||
– Allows LEAs to perform lawful intercepts without the knowledge of service providers. – 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. – Supports intercepts of Layer 3 and Layer 2 traffic. – Supports Layer 2 intercepts for upstream and downstream traffic. – 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. – 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. – 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. |
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.
This guide contains the following chapters:
|
|
---|---|
Provides background information about SNMP and its implementation on Cisco CMTS routers. |
|
Provides instructions for configuring SNMP management support on the router. |
|
Describes each MIB included in the software image. Each description lists any constraints as to how the MIB is implemented on the router. |
|
Describes the SNMP traps and notifications supported by 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. |
This section discusses conventions and terminology used in this guide.
Note 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.
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.