Release Notes for the Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC
Available Languages
Table Of Contents
Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC
DOCSIS System Interoperability on the Cisco uBR10012 CMTS
Cisco IOS Release 12.3(13a)BC and DOCSIS 1.1 System Interoperability
DOCSIS 1.0 and 1.0+ Extensions
Determining the Software Version
Upgrading to a New Software Release
New Hardware Features in Cisco IOS Release 12.3(23)BC10
New Software Features in Cisco IOS Release 12.3(23)BC10
New Hardware Features in Cisco IOS Release 12.3(23)BC9
New Software Features in Cisco IOS Release 12.3(23)BC9
Open Source Software Licenses for Cisco Universal Broadband Routers
New Hardware Features in Cisco IOS Release 12.3(21a)BC9
New Software Features in Cisco IOS Release 12.3(21a)BC9
New Hardware Features in Cisco IOS Release 12.3(23)BC8
New Software Features in Cisco IOS Release 12.3(23)BC8
New Hardware Features in Cisco IOS Release 12.3(23)BC7
New Software Features in Cisco IOS Release 12.3(23)BC7
SAMIS CLC-RP Traffic Throttling
New Hardware Features in Cisco IOS Release 12.3(23)BC6
New Software Features in Cisco IOS Release 12.3(23)BC6
New Hardware Features in Cisco IOS Release 12.3(23)BC5
New Software Features in Cisco IOS Release 12.3(23)BC5
New Hardware Features in Cisco IOS Release 12.3(23)BC4
New Software Features in Cisco IOS Release 12.3(23)BC4
New Hardware Features in Cisco IOS Release 12.3(21a)BC8
New Software Features in Cisco IOS Release 12.3(21a)BC8
New Hardware Features in Cisco IOS Release 12.3(23)BC3
New Software Features in Cisco IOS Release 12.3(23)BC3
New Hardware Features in Cisco IOS Release 12.3(23)BC2
New Software Features in Cisco IOS Release 12.3(23)BC2
Subscriber Traffic Management (STM) Version 1.2
Upstream Utilization Optimization
New Hardware Features in Cisco IOS Release 12.3(21a)BC7
New Software Features in Cisco IOS Release 12.3(21a)BC7
New Hardware Features in Cisco IOS Release 12.3(23)BC1
New Software Features in Cisco IOS Release 12.3(23)BC1
PacketCable Subscriber ID Support
MxN MAC Domain DS Load Balancing
Line Card High Availability (HA) Support for WB Cable Modems
Bypass the 24 Hour Timer for WB CM Use of Failed RF Channels
Dynamic Bandwidth Sharing for Wideband and Modular Cable Interfaces
New Hardware Features in Cisco IOS Release 12.3(21a)BC6
New Software Features in Cisco IOS Release 12.3(21a)BC6
New Hardware Features in Cisco IOS Release 12.3(21a)BC5
New Software Features in Cisco IOS Release 12.3(21a)BC5
New Hardware Features in Cisco IOS Release 12.3(23)BC
DOCSIS Timing & Control Card (DTCC)
New Software Features in Cisco IOS Release 12.3(23)BC
DOCSIS 3.0 Downstream Solution
New Hardware Features in Cisco IOS Release 12.3(21a)BC4
New Software Features in Cisco IOS Release 12.3(21a)BC4
New Hardware Features in Cisco IOS Release 12.3(17b)BC9
New Software Features in Cisco IOS Release 12.3(17b)BC9
New Hardware Features in Cisco IOS Release 12.3(21a)BC3
New Software Features in Cisco IOS Release 12.3(21a)BC3
New Hardware Features in Cisco IOS Release 12.3(21a)BC2
New Software Features in Cisco IOS Release 12.3(21a)BC2
New Hardware Features in Cisco IOS Release 12.3(21a)BC1
New Software Features in Cisco IOS Release 12.3(21a)BC1
New Hardware Features in Cisco IOS Release 12.3(21)BC
New Software Features in Cisco IOS Release 12.3(21)BC
Automatic Virtual Interface Bundles
Cable Duplicate MAC Address Reject
DOCSIS 3.0 Downstream Channel Bonding
Enhanced Rate Bandwidth Allocation (ERBA) on the Cisco uBR10012 Router
PacketCable Client Accept Timeout
Per Downstream Static Multicast
RF Switch Firmware Version 3.60
SAMIS Source Address Management
Service Flow Admission Control
Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia
New Hardware Features in Cisco IOS Release 12.3(17b)BC8
New Software Features in Cisco IOS Release 12.3(17b)BC8
New Hardware Features in Cisco IOS Release 12.3(17b)BC7
New Software Features in Cisco IOS Release 12.3(17b)BC7
New Hardware Features in Cisco IOS Release 12.3(17b)BC6
New Software Features in Cisco IOS Release 12.3(17b)BC6
New Hardware Features in Cisco IOS Release 12.3(17b)BC5
New Software Features in Cisco IOS Release 12.3(17b)BC5
New Hardware Features in Cisco IOS Release 12.3(17b)BC4
Cisco uBR10-MC5X20H Interface Line Card
New Software Features in Cisco IOS Release 12.3(17b)BC4
Downstream Load Balancing Distribution with Upstream Load Balancing
New Hardware Features in Cisco IOS Release 12.3(17b)BC3
New Software Features in Cisco IOS Release 12.3(17b)BC3
New Hardware Features in Cisco IOS Release 12.3(17a)BC2
New Software Features in Cisco IOS Release 12.3(17a)BC2
Cisco Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS
New Hardware Features in Cisco IOS Release 12.3(17a)BC1
New Software Features in Cisco IOS Release 12.3(17a)BC1
New Hardware Features in Cisco IOS Release 12.3(17a)BC
New Software Features in Cisco IOS Release 12.3(17a)BC
DSX Messages and Synchronized PHS Information
Dynamic Channel Change (DCC) for Load Balancing
Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012
Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router
High Availability Support for Encrypted IP Multicast
Management Information Base (MIB) Changes and Enhancements
Pre-equalization Control for Cable Modems
show cable modem Command Changes
Secure Socket Layer Server for Usage-Based Billing
New Hardware Features in Cisco IOS Release 12.3(13a)BC6
New Software Features in Cisco IOS Release 12.3(13a)BC6
New Hardware Features in Cisco IOS Release 12.3(13a)BC5
New Software Features in Cisco IOS Release 12.3(13a)BC5
New Hardware Features in Cisco IOS Release 12.3(13a)BC4
New Software Features in Cisco IOS Release 12.3(13a)BC4
New Hardware Features in Cisco IOS Release 12.3(13a)BC3
New Software Features in Cisco IOS Release 12.3(13a)BC3
New Hardware Features in Cisco IOS Release 12.3(13a)BC2
New Software Features in Cisco IOS Release 12.3(13a)BC2
New Hardware Features in Cisco IOS Release 12.3(13a)BC1
New Software Features in Cisco IOS Release 12.3(13a)BC1
New Hardware Features in Cisco IOS Release 12.3(13a)BC
Cisco Half-Height Gigabit Ethernet Line Card
Processor/IO Memory for the PRE1 Route Processor Module
Cisco uBR10-MC5X20S/U Broadband Processing Engine
Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
New Software Features for Cisco IOS Release 12.3(13a)BC
Access Control List Support for COPS Intercept
Admission Control for the Cisco CMTS
Advanced-mode DOCSIS Set-Top Gateway Issue 1.1
Advanced Spectrum Management Support on the Cisco uBR10012 CMTS
Backup Path Testing for the Cisco RF Switch
Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines
COPS TCP Support for the Cisco Cable Modem Termination System
DHCP MAC Address Exclusion List for cable-source verify dhcp Command
DOCSIS 1.0 Concatenation Override
DOCSIS BPI+ Multiple Root Certificate Support
Dynamic SID/VRF Mapping Support
Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems
Multicast QoS Support on the Cisco uBR10012 CMTS
Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router
Optional Upstream Scheduler Modes
PacketCable Emergency 911 Cable Interface Line Card Prioritization
PacketCable Emergency 911 Services Listing and History
PacketCable Multimedia for the Cisco CMTS
Service Independent Intercept (SII) Support
Transparent LAN Service and Layer 2 Virtual Private Networks
Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE
New Hardware Features in Cisco IOS Release 12.3(9a)BC9
New Software Features in Cisco IOS Release 12.3(9a)BC9
New Hardware Features in Cisco IOS Release 12.3(9a)BC8
New Software Features in Cisco IOS Release 12.3(9a)BC8
New Hardware Features in Cisco IOS Release 12.3(9a)BC7
New Software Features in Cisco IOS Release 12.3(9a)BC7
New Hardware Features in Cisco IOS Release 12.3(9a)BC6
New Software Features in Cisco IOS Release 12.3(9a)BC6
New Hardware Features in Cisco IOS Release 12.3(9a)BC5
New Software Features in Cisco IOS Release 12.3(9a)BC5
New Hardware Features in Cisco IOS Release 12.3(9a)BC4
New Software Features in Cisco IOS Release 12.3(9a)BC4
New Hardware Features in Cisco IOS Release 12.3(9a)BC3
New Software Features in Cisco IOS Release 12.3(9a)BC3
New Hardware Features in Cisco IOS Release 12.3(9a)BC2
New Software Features in Cisco IOS Release 12.3(9a)BC2
New Hardware Features in Cisco IOS Release 12.3(9a)BC1
New Software Features in Cisco IOS Release 12.3(9a)BC1
New Hardware Features in Cisco IOS Release 12.3(9a)BC
Cisco uBR10-MC5X20S/U Broadband Processing Engine
Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
DOCSIS System Interoperability on the Cisco uBR10012 CMTS
New Software Features for Cisco IOS Release 12.3(9a)BC
Cisco Broadband Troubleshooter 3.2
Cisco CMTS Static CPE Override
Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements
DOCSIS Set-Top Gateway Issue 1.0
Dynamic Shared Secret (DMIC) with OUI Exclusion
EtherChannel Support on the Cisco uBR10012 Universal Broadband Router
MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC
NetFlow Accounting Versions 5 and 8 Support
NetFlow Version 5 Features and Format
NetFlow Version 8 Features and Format
Additional Information about NetFlow on the Cisco CMTS
SFID Support for Multicast and Cable Interface Bundling
CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE
Subscriber Traffic Management (STM) Version 1.1
Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q
Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE
Virtual Interface Support for HCCP N+1 Redundancy
MIB Changes and Enhancements for Cisco IOS Release 12.3(21)BC:
MIB Changes and Enhancements for Cisco IOS Release 12.3(17a)BC:
How to Upgrade to Cisco IOS Release 12.3(21)BC
New Command Information for Cisco IOS Release 12.3(21)BC
Restrictions for Cisco IOS Release 12.3(17a)BC
New Command Information for Cisco IOS Release 12.3(13a)BC3
New Command Information for Cisco IOS Release 12.3(13a)BC2
cable service flow activity-timeout
Restrictions for Cisco IOS Release 12.3(13a)BC
Restrictions for Cisco IOS Release 12.3(9a)BC
New and Changed Command Reference for Cisco IOS Release 12.3(9a)BC
Caveats for Cisco IOS Release 12.3 BC
Open Caveats for Release 12.3(23)BC10
Resolved Caveats for Release 12.3(23)BC10
Open Caveats for Release 12.3(23)BC9
Resolved Caveats for Release 12.3(23)BC9
Open Caveats for Release 12.3(21a)BC9
Resolved Caveats for Cisco 12.3(21a)BC9
Open Caveats for Release 12.3(23)BC8
Resolved Caveats for Release 12.3(23)BC8
Open Caveats for Release 12.3(23)BC7
Resolved Caveats for Release 12.3(23)BC7
Open Caveats for Release 12.3(23)BC6
Resolved Caveats for Release 12.3(23)BC6
Open Caveats for Release 12.3(23)BC5
Resolved Caveats for Release 12.3(23)BC5
Open Caveats for Release 12.3(23)BC4
Resolved Caveats for Release 12.3(23)BC4
Open Caveats for Release 12.3(21a)BC8
Resolved Caveats for Release 12.3(21a)BC8
Open Caveats for Release 12.3(23)BC3
Resolved Caveats for Release 12.3(23)BC3
Open Caveats for Release 12.3(23)BC2
Resolved Caveats for Release 12.3(23)BC2
Open Caveats for Release 12.3(21a)BC7
Resolved Caveats for Release 12.3(21a)BC7
Open Caveats for Release 12.3(23)BC1
Resolved Caveats for Release 12.3(23)BC1
Open Caveats for Release 12.3(21a)BC6
Resolved Caveats for Release 12.3(21a)BC6
Open Caveats for Release 12.3(21a)BC5
Resolved Caveats for Release 12.3(21a)BC5
Open Caveats for Release 12.3(23)BC
Resolved Caveats for Release 12.3(23)BC
Open Caveats for Release 12.3(21a)BC4
Resolved Caveats for Release 12.3(21a)BC4
Open Caveats for Release 12.3(17b)BC9
Resolved Caveats for Release 12.3(17b)BC9
Open Caveats for Release 12.3(21a)BC3
Resolved Caveats for Release 12.3(21a)BC3
Open Caveats for Release 12.3(21a)BC2
Resolved Caveats for Release 12.3(21a)BC2
Open Caveats for Release 12.3(21a)BC1
Resolved Caveats for Release 12.3(21a)BC1
Open Caveats for Release 12.3(21)BC
Resolved Caveats for Release 12.3(21)BC
Open Caveats for Release 12.3(17b)BC8
Resolved Caveats for Release 12.3(17b)BC8
Open Caveats for Release 12.3(17b)BC7
Resolved Caveats for Release 12.3(17b)BC7
Open Caveats for Release 12.3(17b)BC6
Resolved Caveats for Release 12.3(17b)BC6
Open Caveats for Release 12.3(17b)BC5
Resolved Caveats for Release 12.3(17b)BC5
Open Caveats for Release 12.3(17b)BC4
Resolved Caveats for Release 12.3(17b)BC4
Open Caveats for Release 12.3(17b)BC3
Resolved Caveats for Release 12.3(17b)BC3
Open Caveats for Release 12.3(17a)BC2
Resolved Caveats for Release 12.3(17a)BC2
Open Caveats for Release 12.3(17a)BC1
Resolved Caveats for Release 12.3(17a)BC1
Open Caveats for Release 12.3(17a)BC
Resolved Caveats for Release 12.3(17a)BC
Open Caveats for Release 12.3(13a)BC6
Resolved Caveats for Release 12.3(13a)BC6
Open Caveats for Release 12.3(13a)BC5
Resolved Caveats for Release 12.3(13a)BC5
Open Caveats for Release 12.3(13a)BC4
Resolved Caveats for Release 12.3(13a)BC4
Open Caveats for Release 12.3(13a)BC3
Resolved Caveats for Release 12.3(13a)BC3
Open Caveats for Release 12.3(13a)BC2
Resolved Caveats for Release 12.3(13a)BC2
Open Caveats for Release 12.3(13a)BC1
Resolved Caveats for Release 12.3(13a)BC1
Open Caveats for Release 12.3(13a)BC
Resolved Caveats for Release 12.3(13a)BC
Open Caveats for Release 12.3(9a)BC9
Resolved Caveats for Release 12.3(9a)BC9
Open Caveats for Release 12.3(9a)BC8
Resolved Caveats for Release 12.3(9a)BC8
Open Caveats for Release 12.3(9a)BC7
Resolved Caveats for Release 12.3(9a)BC7
Open Caveats for Release 12.3(9a)BC6
Resolved Caveats for Release 12.3(9a)BC6
Open Caveats for Release 12.3(9a)BC5
Resolved Caveats for Release 12.3(9a)BC5
Open Caveats for Release 12.3(9a)BC4
Resolved Caveats for Release 12.3(9a)BC4
Open Caveats for Release 12.3(9a)BC3
Resolved Caveats for Release 12.3(9a)BC3
Open Caveats for Release 12.3(9a)BC2
Resolved Caveats for Release 12.3(9a)BC2
Open Caveats for Release 12.3(9a)BC1
Resolved Caveats for Release 12.3(9a)BC1
Open Caveats for Release 12.3(9a)BC
Resolved Caveats for Release 12.3(9a)BC
Cisco IOS Software Documentation Set
Release 12.3 Documentation Set
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC
Revised: February 28, 2011, OL-6760-49
The release notes for Cisco IOS Release 12.3BC for the Cisco uBR10012 universal broadband routers describe the enhancements and caveats for all releases in the cable-specific, early deployment, 12.3BC release trains. Some of the most recent releases in 12.3BC include 12.3(17b)BCx-, 12.3(21a)BCx-, and 12.3(23)BCx-based releases.
These release notes are updated with each release in the train. For a list of the software caveats that apply to Cisco IOS Release 12.3(23)BC8, see the "Caveats for Cisco IOS Release 12.3 BC" section and Caveats for Cisco IOS Release 12.3 T. Use these release notes in conjunction with the cross-platform Release Notes for Cisco IOS Release 12.3T located on Cisco.com and the Documentation CD-ROM.
Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.3 T located on Cisco.com.
Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/en/US/customer/support/tsd_products_field_notice_summary.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/en/US/support/tsd_products_field_notice_summary.html.
Contents
These release notes describe the following topics:
•
DOCSIS System Interoperability on the Cisco uBR10012 CMTS
•
•
•
Early Deployment Releases
These release notes describe the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.3(21a)BC9, which is an early deployment (ED) release based on Cisco IOS Release 12.3 T. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.
Table 1 shows recent early deployment releases for the CiscouBR10012 universal broadband router.
System Requirements
This section describes the system requirements for Cisco IOS Release upto 12.3(23)BC8 and includes the following sections:
•
•
•
Memory Recommendations
Supported Hardware
This section describes the hardware supported by the Cisco uBR10012 Universal Broadband Router in Cisco IOS Release 12.3(21a)BC9.
For detailed descriptions of the new hardware features, see the "New and Changed Information" section.
Table 3 provides the list of hardware supported by the Cisco uBR10012 Universal Broadband Router.
Note
DOCSIS System Interoperability on the Cisco uBR10012 CMTS
This section describes the operation of primary interoperability features in the Cisco uBR10012 router. For additional DOCSIS information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
Cisco IOS Release 12.3(13a)BC and DOCSIS 1.1 System Interoperability
Cisco IOS Release 12.3(13a)BC and earlier releases in this release train support several powerful new features for the Cisco uBR10012 CMTS. In addition to maintaining DOCSIS support from earlier Cisco IOS releases, Cisco IOS Release 12.3(13a)BC enhances DOCSIS support in these general categories:
•
http://www.cablemodem.com/specifications/specifications20.html
•
http://www.cablelabs.com/cablemodem/specifications/gateway.html
•
http://www.cablelabs.com/packetcable/specifications/
•
–
http://www.cablelabs.com/packetcable/specifications/multimedia.html
Additional High Availability and Security features as described elsewhere in this document.
DOCSIS 1.0 Baseline Privacy
DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and cable modem. BPI ensures that a cable modem, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for services only it is authorized to access.
To enable BPI, choose software at both the CMTS and cable modem that support this mode of operation. Select a Cisco IOS image that supports BPI. BPI must be enabled using the DOCSIS configuration file.
The cable modem must also support BPI. Cable modems must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment.
Note
Cable Modem Interoperability
•
•
DOCSIS 1.0 and 1.0+ Extensions
Earlier releases of Cisco IOS software for the uBR10012 router provide support for the original DOCSIS 1.0 standard, featuring basic best-effort data traffic and Internet access over the coaxial cable network. The DOCSIS 1.0+ extensions provides Quality of Service (QoS) enhancements for real-time traffic, such as voice calls, in anticipation of full DOCSIS 1.1 support.
Note
DOCSIS 1.1 Extensions
The DOCSIS 1.1 specification provides the following functional enhancements over DOCSIS 1.0 coaxial cable networks:
•
–
–
–
–
–
•
–
–
–
–
–
•
•
•
•
•
DOCSIS 1.1 Quality of Service
The DOCSIS 1.1 QoS framework is based on the following objects:
•
•
•
•
In DOCSIS 1.1, the basic unit of QoS is the service flow, which is a unidirectional sequence of packets transported across the RF interface between the cable modem and CMTS. A service flow is characterized by a set of QoS parameters such as latency, jitter, and throughput assurances.
Every cable modem establishes a primary service flow in both the upstream and downstream directions. The primary flows maintain connectivity between the cable modem and CMTS at all times.
In addition, a DOCSIS 1.1 cable modem can establish multiple secondary service flows. The secondary service flows can either be permanently created (they persist until the cable modem is reset or powered off) or they can be created dynamically to meet the needs of the on demand traffic being transmitted.
Each service flow has a set of QoS attributes associated with it. These QoS attributes define a particular class of service and determine characteristics such as the maximum bandwidth for the service flow and the priority of its traffic. The class of service attributes can be inherited from a preconfigured CMTS local service class (class-based flows), or they can be individually specified at the time of the creation of the service flow.
Each service flow has multiple packet classifiers associated with it, which determine the type of application traffic allowed to be sent on that service flow. Each service flow can also have a Payload header suppression (PHS) rule associated with it to determine which portion of the packet header will be suppressed when packets are transmitted on the flow.
Determining the Software Version
To determine the version of Cisco IOS software running on your Cisco uBR10012 universal broadband router, log in to the Cisco uBR10012 universal broadband router and enter the show version EXEC command:
Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) Software (uBR10k-k8p6-mz), Version 12.3(17b)BC9, EARLY DEPLOYMENT RELEASE SOFTWAREUpgrading to a New Software Release
For information about selecting a new Cisco IOS software release, please refer to How to Choose a Cisco IOS Software Release at:
http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1834/products_tech_note09186a00800fb9d9.shtml
For information about upgrading to a new software release, refer to the appropriate platform-specific document:
•
•
http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm
To choose a new Cisco IOS software release by comparing feature support or memory requirements, use Cisco Feature Navigator. Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS and Catalyst OS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
To choose a new Cisco IOS software release based on information about defects that affect that software, use Bug Toolkit at:
http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs
Feature Set Tables
Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.
Caution
The feature set tables have been removed from the Cisco IOS Release 12.3 release notes to improve the usability of the release notes documentation. The feature-to-image mapping that was provided by the feature set tables is available through Cisco Feature Navigator.
Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.
To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
http://www.cisco.com/web/siteassets/account/index.html
Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:
For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:
http://www.cisco.com/support/FeatureNav/FNFAQ.html
Determining Which Software Images (Feature Sets) Support a Specific Feature
To determine which software images (feature sets) in Cisco IOS Release 12.3 support a specific feature, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1
Step 2
Step 3
Note
Repeat this step to add additional features. A maximum of 20 features can be chosen for a single search.
Step 4
Step 5
Step 6
Step 7
Determining Which Features Are Supported in a Specific Software Image (Feature Set)
To determine which features are supported in a specific software image (feature set) in Cisco IOS Release 12.3, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
New and Changed Information
The following sections list the new hardware and software features supported by the Cisco uBR10012 router for Cisco IOS Release 12.3(21a)BC9:
For more information about these features, refer to the documents listed in the "Related Documentation" section.
New Hardware Features in Cisco IOS Release 12.3(23)BC10
There are no new hardware features in Cisco IOS Release 12.3(23)BC10.
New Software Features in Cisco IOS Release 12.3(23)BC10
There are no new software features in Cisco IOS Release 12.3(23)BC10.
New Hardware Features in Cisco IOS Release 12.3(23)BC9
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC9.
New Software Features in Cisco IOS Release 12.3(23)BC9
There are no new software features supported in Cisco IOS Release 12.3(23)BC9.
Open Source Software Licenses for Cisco Universal Broadband Routers
For information on Open Source Software License MPL 1.1, refer to the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/license/cable_licensing.html
New Hardware Features in Cisco IOS Release 12.3(21a)BC9
There is no new hardware feature supported in Cisco IOS Release 12.3(21a)BC9.
New Software Features in Cisco IOS Release 12.3(21a)BC9
There is no new software feature supported in Cisco IOS Release 12.3(21a)BC9.
New Hardware Features in Cisco IOS Release 12.3(23)BC8
There is no new hardware feature supported in Cisco IOS Release 12.3(23)BC8.
New Software Features in Cisco IOS Release 12.3(23)BC8
There is no new software feature supported in Cisco IOS Release 12.3(23)BC8.
New Hardware Features in Cisco IOS Release 12.3(23)BC7
There is no new hardware feature supported in Cisco IOS Release 12.3(23)BC7.
New Software Features in Cisco IOS Release 12.3(23)BC7
The following software features are new in Cisco IOS Release 12.3(23)BC7.
SAMIS CLC-RP Traffic Throttling
The SAMIS CLC-RP traffic throttling feature limits or throttles the data collection between the cable line card and the route processor. This functionality is achieved using the new cable metering data-per-session command. This feature also reduces the congestion in the Broadband Processing Engine (BPE) due to the SAMIS data collection from CLC to RP.
The following commands are new or modified:
•
•
•
M-CMTS Enhancement
The following commands are modified in Cisco IOS Release 12.3(23)BC7. The commands are upgraded to provide better display of the route processor service flow and queue information.
•
•
Three Step Dynamic Modulation
Cisco IOS Release 12.3(33)BC7 introduces Three Step Dynamic Modulation, which allows you to create and use a third modulation profile in the Dynamic Upstream Modulation feature, as against the existing 16-QAM and quadrature phase-shift keying (QPSK) modulation profiles. The feature now permits 64-QAM based modulation profile to increase the upstream throughput and to satisfy the demand for new spectrum management.
The 64-QAM modulation profile is a more bandwidth-efficient modulation scheme and has a higher throughput than the other two modulation profiles.
For more details on Three Step Dynamic Modulation and the Dynamic Upstream Modulation feature, refer to Spectrum Management and Advanced Spectrum Management for the Cisco CMTS guide at the following location: http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html.
The Cisco IOS Release 12.3(23)BC7 introduces or modifies the following commands:
The cable upstream threshold hysteresis command was introduced to allow configurable hysteresis values for spectrum management channel upgrade thresholds.
The cable upstream modulation command was enhanced to accept up to three profiles, instead of the existing two.
The show cable hop history command was enhanced to display the modulation profile number when a change occurs.
Enhanced Show Tech
A new keyword, cmts, has been added to the show tech-support command to provide debugging information specific to a cable interface or a modem for the following universal broadband routers:
•
•
•
For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_16_show_cable_m_to_show_cable_u.html
Cable Modem QoS Information
A new command, show cable modem service-flow, is introduced to provide information about all service flows associated with a particular modem.
For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_16_show_cable_m_to_show_cable_u.html
Direct Load for Cable Modems
A new command, cable upstream equalization-error-recovery, is introduced to enable the CMTS to send Type-Length-Value (TLV) Type 9 in the DOCSIS RNG-RSP MAC management messages. The TLV Type 9 helps CMs come online if the TLV Type 4 convolved method causes CMs to go offline.
For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_10_cable_u_to_cable_w.html
New Hardware Features in Cisco IOS Release 12.3(23)BC6
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC6.
New Software Features in Cisco IOS Release 12.3(23)BC6
The following command is modified in Cisco IOS Release 12.3(23)BC6:
•
The command output was modified to capture the SPA sensor temperature readings and error packet information.
The error information contains details about the:
•
•
•
•
For additional information about this or other commands, refer to the Cisco IOS CMTS Cable Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
New Hardware Features in Cisco IOS Release 12.3(23)BC5
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC5.
New Software Features in Cisco IOS Release 12.3(23)BC5
The following command is modified in Cisco IOS Release 12.3(23)BC5:
•
The command output was modified to capture the SPA sensor temperature readings and error packet information.
The error information contains details about the:
•
•
•
•
New Hardware Features in Cisco IOS Release 12.3(23)BC4
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC4.
New Software Features in Cisco IOS Release 12.3(23)BC4
There are no new software features supported in Cisco IOS Release 12.3(23)BC4.
New Hardware Features in Cisco IOS Release 12.3(21a)BC8
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC8.
New Software Features in Cisco IOS Release 12.3(21a)BC8
There are no new software features supported in Cisco IOS Release 12.3(21a)BC8.
New Hardware Features in Cisco IOS Release 12.3(23)BC3
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC3.
New Software Features in Cisco IOS Release 12.3(23)BC3
There are no new software features supported in Cisco IOS Release 12.3(23)BC3.
New Hardware Features in Cisco IOS Release 12.3(23)BC2
There are no new hardware features supported in Cisco IOS Release 12.3(23)BC2.
New Software Features in Cisco IOS Release 12.3(23)BC2
The following software features are new in Cisco IOS Release 12.3(23)BC2.
Subscriber Traffic Management (STM) Version 1.2
The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM is a simple bandwidth management tool which works as a low CPU alternative to Network-Based Application Recognition (NBAR) and access control lists (ACLs), however, using STM does not mean that NBAR and ACLs have to be turned off; STM can be applied along with NBAR and ACLs. STM also works in conjunction with the Cisco Broadband Troubleshooter to support additional network management and troubleshooting functions in the Cisco CMTS.
The STM Version 1.2 feature is enhanced in Cisco IOS Release 12.3(23)BC2 with the following support on the Cisco uBR7246VXR and Cisco uBR10012 Universal Broadband Routers:
•
•
•
•
•
Addition of the following SNMP objects to the CISCO-CABLE-QOS-MONITOR-MIB:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The following commands are new or modified:
•
•
•
•
•
•
For detailed information about this feature, see the Subscriber Traffic Management on the Cisco CMTS Routers document at:
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_sbsbr_tfmgt.html
Upstream Utilization Optimization
The Upstream (US) Utilization Optimization feature on the Cisco Cable Modem Termination System (CMTS) routers provides higher upstream throughput. It provides the following benefits and functions on a Cisco CMTS router:
•
•
The following commands are new or modified:
•
•
•
•
•
For detailed information about this feature, see the Upstream Utilization Optimization on the Cisco CMTS Routers document at:
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_upstream_rate_adapt.html
New Hardware Features in Cisco IOS Release 12.3(21a)BC7
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC7.
New Software Features in Cisco IOS Release 12.3(21a)BC7
There are no new software features supported in Cisco IOS Release 12.3(21a)BC7.
New Hardware Features in Cisco IOS Release 12.3(23)BC1
The Cisco 1000BASE-T SFP module is introduced in Cisco IOS Release 12.3(23)BC1.
Cisco 1000BASE-T SFP Module
The Cisco 1000BASE-T SFP (Small Form-Factor Pluggable) module support for the Half-Height Gigabit Ethernet Line Card is introduced in Cisco IOS Release 12.3(23)BC1. SFP modules are input/output devices that plug into a Gigabit Ethernet (GE) port to interface with a fiber-optic or copper Ethernet media. The modules are used on Cisco platforms that have Gigabit Ethernet interfaces.The product ID of the Cisco 1000BASE-T SFP module is GLC-T.
The Cisco 1000BASE-T SFP connects a Cisco Gigabit Interface Converter (GBIC) port to Category 5, Category 5e and Category 6 wiring via a standard RJ-45 interface. The maximum Category 5 wiring distance is 100m. The module provides with an option of connecting to a backhaul network interface.
The SFP-GE-T is a Copper SFP supported on the Cisco Wideband SPA.The SFP-GE-T provides full-duplex Gigabit Ethernet connectivity to high-end workstations and between wiring closets over an existing copper network infrastructure. The SFP-GE-T maximum cabling distance is 328 feet (100 m).
For more information on the Cisco 1000BASE-T SFP, see http://www.cisco.com/en/US/docs/routers/7200/install_and_upgrade/gbic_sfp_modules_install/5067g.html
For more information on the Cisco 1000 BASE-T SFP-GE-T, see
New Software Features in Cisco IOS Release 12.3(23)BC1
The following software features are new in Cisco IOS Release 12.3(23)BC1.
PacketCable Subscriber ID Support
Subscriber ID is added to all Gate Control messages and enhances error codes returned from the Cable Modem Termination System (CMTS).
Previously, the Gate ID was unique only to individual CMTS systems, with the CMTS proxying all CMS (Call Management Server) Gate control messaging through a central device which manages the CMTS connections on the behalf of the CMS. The CMS had a single Common Open Policy Service (COPS) association to the proxy device. Therefore, the Gate IDs could be duplicated when using multiple CMTS systems.
The new PacketCable Subscriber ID feature adds a Subscriber ID to each Gate Control message to disambiguate the Gate IDs between the CMS and proxy device. The Subscriber ID parameter is added to the following COPS messages:
•
•
•
•
The Subscriber ID is available at the CMS and is used in the Gate-Set messages. Additionally, the error codes returned from CMTS or its proxy are enhanced to include more specific information about gate operation failures.
To enable this feature, a new command is introduced: packetcable gate send-subscriberID used in global configuration mode. For more information, see the Cisco IOS CMTS Cable Command Reference Guide.
MxN MAC Domain DS Load Balancing
Prior to the introduction of this new feature, load balancing configuration using the cable load-balance group policy (us-groups-across-ds) command only considered upstream (US) load balancing across different downstream (DS) channels. This was sufficient if an US channel was not associated to more than one DS channel. However, for an MxN MAC domain, it is possible to have one US channel associated to multiple DS channels. In this case, it is necessary to further balance the DS load, once the US load is sufficiently balanced.
With the new feature, once the us-groups-across-ds policy is configured, CMTS attempts to balance the DS load on top of the balanced US load and among DS channels associated to the same US. The method and policy used for DS load balancing are based on the configuration in the DS load balancing group associated to the corresponding DS channels.
There are no new or modified commands for this feature.
Line Card High Availability (HA) Support for WB Cable Modems
Wideband cable modems remain online whenever there is a failure or switchover of a 520 MD host line card, 520 guardian line card, 520 host or 520 guardian on the same line card, or a performance routing engine (PRE).
There are no new or modified commands for this feature.
Bypass the 24 Hour Timer for WB CM Use of Failed RF Channels
When the CM sends a request to the CMTS for bonded service, the CMTS assigns the best available bonding group that is compatible with the CM. The CM then attempts to acquire the non-primary DS RF channels that are members of that bonding group. If the CM is unable to acquire one or more of the channels, it returns an error code causing the CMTS to mark all of the assigned RF channels as unacceptable for that CM. In prior versions, the channels so marked could not be reassigned to the same CM for up to 24 hours.
The new feature has removed the 24 hour timer required to clear these channels. Once the CM successfully completes registration, the list of failed RF channels for that CM is cleared. If the RF impairment has been eliminated when the CM re-registers, that channel can be reused immediately.
There are no new or modified commands for this feature.
Voice Support on WB Modems
CMTS supports voice services on voice-enabled wideband (WB) cable modems. Committed information rate (CIR) downstream service flows on WB interfaces are supported. You can reserve up to 90% of the wideband interface bandwidth. If multiple MAC domains (MDs) are sharing a WB interface, the available link rate is distributed evenly between all MDs that share the WB interface. If the MDs that share the WB interface are on the same line card, they share the CIR pool.
To display the reserved and available bandwidth, you can use the show-module bay all association wideband command. To display the reserved and available bandwidth for wideband interfaces, you can use the show interface wideband-cable command. For more information, see the Cisco IOS CMTS Cable Command Reference Guide.
There are no new commands introduced for this feature. However, the user must first enable packet cable or multimedia packet cable to enable the voice support feature.
Dynamic Bandwidth Sharing for Wideband and Modular Cable Interfaces
Dynamic bandwidth sharing (DBS) is the dynamic allocation of bandwidth for wideband (WB) and modular cable (MC) interfaces sharing the same downstream channel. The bandwidth available to each WB, MC, or narrowband channel is not a fixed value-it depends on the configuration and the traffic load on the WB or MC.
DBS is achieved using a new type of modality called a link queue. Link queues represent a specific share of bandwidth on a particular channel. Link queues are only used to calculate the effective bandwidth of a channel, and such link queues are activated and deactivated according to the state of activity on a specific channel. DBS and static bandwidth allocations are configured at the WB or MC interface level. By default, bandwidth for a WB or MC channel is statically allocated. When DBS is enabled on an interface, the static bandwidth percentage is converted to a committed information rate (CIR) value for the corresponding link queue. The interface CIR value represents the guaranteed portion of the interface bandwidth and is used for admission control of the service flows with minimum reserved rate. When DBS is enabled, you can also specify the remaining ratio value of the excess bandwidth for the link queue. If DBS is enabled and no bandwidth percentage is specified, no bandwidth is reserved for the WB or MC interface and the interface is effectively in protocol down state where link queues are not created.
Dynamic bandwidth sharing does not preclude static bandwidth configuration. If a static portion of bandwidth is configured on any radio frequency (RF) channel that one or more DBS-enabled channel utilizes, that portion is subtracted from the RF link's CIR. Therefore, such a portion is always reserved and is not available to dynamic WB or MC interfaces. The DBS feature continues working across line card and performance routing engine (PRE) switchovers with no loss of functionality.
For more information on the DBS please see http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_dyn_bw_sharing.html
The following commands are new in Cisco IOS Release 12.3(23)BC1.
•
•
•
The following commands are modified in Cisco IOS Release 12.3(23)BC1.
•
•
•
For a detailed description of the commands please refer the Cisco IOS CMTS Cable Command Reference.
New Hardware Features in Cisco IOS Release 12.3(21a)BC6
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC6.
New Software Features in Cisco IOS Release 12.3(21a)BC6
There are no new software features supported in Cisco IOS Release 12.3(21a)BC6.
New Hardware Features in Cisco IOS Release 12.3(21a)BC5
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC5.
New Software Features in Cisco IOS Release 12.3(21a)BC5
There are no new software features supported in Cisco IOS Release 12.3(21a)BC5.
New Hardware Features in Cisco IOS Release 12.3(23)BC
The DOCSIS Timing & Control Card (DTCC) is introduced in Cisco IOS Release 12.3(23)BC.
DOCSIS Timing & Control Card (DTCC)
On the Cisco uBR10012 universal broadband router, the DOCSIS Timing & Control Card (DTCC) acts as a secondary processor that performs the following functions:
•
•
•
•
•
When two DTCC cards are installed, they are configured as active (primary) and backup (redundant). If the DTCC card in the first slot is working at system power-up, it automatically becomes the active card and the DTCC card in the second slot becomes the backup card. The DTCC cards monitor each other's priority information, so that if the active card fails, the active card role is transferred to the redundant backup card without loss of data.
Each DTCC card contains two RJ-45 connectors labeled Primary and Secondary, on the front panel. See Xref_Colorparanum[FC_FigureCap,FCW_FigureCapW]on page *. These connectors are for a primary and secondary (redundant) Stratum 3 external clock reference source that is traceable to a Stratum 1 clock source. The external reference source allows the Cisco uBR10012 router's reference clock to be synchronized to the Stratum 1 clock source, providing a free-running DOCSIS-quality clock reference and time stamp to the cable interface line cards.
If present, the primary DTI link is used. If it is lost, the secondary DTI link (if present) on the active DTCC card is used. If the active DTCC card stops functioning, control is transferred to the backup DTCC card, which then uses its primary and secondary clock reference sources. If neither card has a valid clock reference source, In DTI mode, all M-CMTS elements should have common timing source. The internal clock of DTI client cannot be used to provide DOCSIS clock and timestamp. High availability strategies (active/backup card, active/backup ports) should be used to prevent loss of common timing source.
New Software Features in Cisco IOS Release 12.3(23)BC
The following software features are new in Cisco IOS Release 12.3(23)BC:
DOCSIS 3.0 Downstream Solution
The DOCSIS 3.0 Downstream Solution, Release 2.0, provides the following capabilities:
Primary-capable downstream channels from the SPA
Primary-capable channels are SPA DS channels (also known as SPA RF channels) associated with the upstream channels from the Cisco uBR10-MC5X20 line card. A SPA downstream channel is made primary-capable via Channel Grouping Domain (CGD) configuration. A primary-capable downstream channel can carry narrowband traffic as well as wideband traffic. An RF channel is considered primary-capable when it has been associated with one or more upstream channels from a Cisco uBR10-MC5X20 cable interface and this RF channel can carry DOCSIS MAC management messages (MMM) including SYNC messages, Mini-slot Allocation Packet (MAP) messages, and Upstream Channel Descriptors (UCD). They may also carry primary MAC Domain Descriptor (MDD) messages for DOCSIS 3.0 modems.Such an RF channel downstream is referred to as a primary-capable downstream. A DOCSIS Timing Interface (DTI) server which interfaces with the EQAM device and the Cisco uBR10k DTCC is used to synchronize DOCSIS MAC-layer messages. The interface represented by a single primary-capable downstream represents the narrowband portion of the RF channel.
A SPA downstream channel, whether primary-capable or not, can always be part of a bonded channel that carries bonded data traffic.
An RF channel can be shared by the associated modular-cable interface and by the wideband interfaces. The bandwidth of each RF channel can be configured to be statically divided between the modular-cable and wideband interfaces. Each RF channel's bandwidth can be used for wideband channels or narrowband channels or for a combination of the two.
A primary downstream channel is a primary-capable channel that is being used as a narrowband channel or as part of a wideband channel. A SPA downstream channel may only be a primary-capable downstream channel for a single MAC domain. However, the same SPA downstream channel may be part of one or more bonded channels (wideband interface) that serve multiple MAC domains. A primary downstream channel of one MAC domain can serve as non-primary downstream channel of another MAC domain. The total available bandwidth of a primary downstream channel, which is 96 percent, is split between the primary-capable downstream and non-primary-capable downstream channels. The remaining 4 percent is reserved for DOCSIS MAP and SYNC bandwidth.
This capability:
•
•
•
Extensible MAC domain support via Channel Grouping Domain
A Channel Grouping Domain (CGD) is a collection of primary-capable downstream channels that are associated with a common set of upstream channels. A CGD is always specified within the context of a MAC domain to which all the downstream and upstream channels belong. The downstream channel local to the MAC domain on the Cisco uBR10-MC5X20 line card is always primary-capable, but a SPA downstream channel has to be made primary-capable by explicit CGD configuration. A CGD provides the additional flexibilty of associating a subset of the upstream channels within a MAC domain to any of the primary-capable downstream channels, including the local downstream channels. When an upstream channel is associated with a downstream channel, its information is included in the MAP and UCD messages sent through that downstream channel. Multiple CGD configurations may be included in the same MAC domain, allowing the flexibility of the MAC domain to include various primary-capable downstream channels associated with common or different sets of upstream channels.
This capability:
•
•
•
Primary-capable downstream channel selection
Provides primary-capable downstream channel selection to facilitate channel bonding and reliability of voice-enabled modems.
Primary Downstream Channel Selection for Bonding Capable Modems
In order to fully utilize downstream bonding capacity, it is desired to force downstream bonding (wideband) capable modems to register on a primary-capable channel that is part of an operational downstream bonding group.
A downstream bonding capable modem is identified upon cable modem registration. A modem is downstream bonding capable if the modem reports a multiple-tuner receive capacity and a Remote Copy Protocol (RCP) known by the CMTS in REG-REQ. A wideband media terminal adapter (MTA) will be treated also as DS bonding-capable modems, therefore subject to the same primary channel selection policy.
The primary channel selection for bonding capable modems can be enabled through the global DS channel selection configuration. By default, if such configuration is not present, downstream bonding capable modems will be allowed to operate on a primary channel even it is not included in any load balancing group.
At any time after the system is up, enabling the primary channel selection for bonding capable modems will not affect existing modems in the system. The operator has to manually reset the bonding capable modems through the clear cable modem command either globally or at the per-MAC domain level.
Primary Downstream Channel Selection for Narrowband Modems
The primary downstream channel selection for narrowband modems is intended to provide the operator the flexibility to segregate non-bonding capable modems to specific types of DS channels with the following two options:
Redirecting Modems that Access a CMTS with Legacy DOCSIS INIT-RNG-REQ at Initialization
Moving Non-Bonding Capable Modems to Bonding-Disabled Primary Channels
Downstream Channel Selection for Voice-Enabled Cable Modems
This downstream channel selection option provides the operator the ability to provide high-availability for voice services by restricting voice-enabled modems to Cisco uBR10-MC5X20 downstream channels.
High availability
Provides high availability support for modems on SPA DS channels. The Cisco DOCSIS 3.0 Downstream Solution, Release 2.0 provides higher system availability for voice services by providing the ability to restrict voice services only to Cisco uBR10-MC5X20 line cards. This allows the CMTS to make an attempt to move the voice modems to the hosting Cisco uBR10-MC5X20 line cards of Cisco uBR10-MC5X20 downstream channels in the same load balancing group.
DOCSIS 1.x/2.0 and legacy feature support on SPA DS channels
Provides support for DOCSIS 1.x/2.0 modems on SPA downstream channels. The following legacy features are supported on the SPA downstream channels:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
DOCSIS 3.0 support on SPA DS channels
The Cisco DOCSIS 3.0 Downstream Solution is an industry-standard DOCSIS 3.0 implementation of channel bonding. With channel bonding, bandwidth is increased by combining or bonding multiple RF channels to create a wideband channel. The Cisco DOCSIS 3.0 Downstream Solution extensions affect the CMTS and the cable modem as well as the provisioning and network management systems. A 3-channel cable modem that performs 3-channel bonding must be able to access three SPA RF channels of which at least one RF channel must be a primary-capable channel that is used for modem registration.
The core of the Downstream 3.0 downstream solution is the sending of DOCSIS packets for a given service flow across multiple RF channels, offering significant increases in the peak downstream data rate that can be provided to a single cable modem. The transmit framer in the Cisco Wideband SPA "stripes" the DOCSIS packets for a given flow and transmits them across the multiple RF channels of the wideband channel. When the packets are received at the wideband cable modem, the modem's receiver framer uses a sequence number embedded in each DOCSIS packet to reassemble the packets into the original flow.
The Cisco DOCSIS 3.0 Downstream Solution defines a wideband channel as a unique combination of downstream RF channels from the same SPA. The wideband CMTS manages up to 64 wideband channels (32 wideband channels per Wideband SPA). A wideband cable modem uses a wideband channel. Many wideband cable modems can share the same wideband channel.
The Cisco Wideband SPA on the Cisco uBR10012 router provides DOCSIS 3.0 channel bonding for DOCSIS Network processing. In the Cisco DOCSIS 3.0 Downstream Solution, Release 2.0, for the wideband downstream channel, the Wideband SPA uses its Gigabit Ethernet port to send data traffic to the EQAM device. This EQAM device uses one or more QAM output channels, depending on how the wideband channel is configured, to send striped packets to the wideband cable modem. In Cisco DOCSIS 3.0 Downstream Solution Release 2.0, channel bonding is used for downstream wideband channels only. A downstream wideband channel can combine up to three RF channels for a total bandwidth of over hundreds of megabits to gigabits per second with bonded modems supporting data rates of up to 292 Mbps.
In Release 2.0, channel bonding is used for downstream wideband channels only.
With the Linksys WCM300-NA modem, a downstream wideband channel can combine up to eight RF channels for a total bandwidth of up to approximately 292 Mbps (at 6 MHz and 256 QAM).
With the Scientific Atlanta DPC2505 modem, a downstream wideband channel can combine up to three RF channels for a total bandwidth of over 100 Mbps (at 6 MHz and 256 QAM).
New Hardware Features in Cisco IOS Release 12.3(21a)BC4
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC4.
New Software Features in Cisco IOS Release 12.3(21a)BC4
There are no new software features supported in Cisco IOS Release 12.3(21a)BC4.
New Hardware Features in Cisco IOS Release 12.3(17b)BC9
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC9.
New Software Features in Cisco IOS Release 12.3(17b)BC9
There are no new software features supported in Cisco IOS Release 12.3(17b)BC9.
New Hardware Features in Cisco IOS Release 12.3(21a)BC3
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC3.
New Software Features in Cisco IOS Release 12.3(21a)BC3
The following software features are new in Cisco IOS Release 12.3(21a)BC3:
Control Point Discovery (CPD)
The Control Point Discovery (CPD) can be used to discover the IP address of a control point between the requestor and a media endpoint. It can be used by CMS (call management server), DF (delivery function for CALEA), or PS (policy server for Packetcable multimedia) to discover the IP address of the CMTS connected to the media endpoint. The CMTS needs to interpret and respond to the CPD messages.
New Hardware Features in Cisco IOS Release 12.3(21a)BC2
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC2.
New Software Features in Cisco IOS Release 12.3(21a)BC2
There are no new software features supported in Cisco IOS Release 12.3(21a)BC2.
New Hardware Features in Cisco IOS Release 12.3(21a)BC1
There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC1.
New Software Features in Cisco IOS Release 12.3(21a)BC1
There are no new software features supported in Cisco IOS Release 12.3(21a)BC1.
New Hardware Features in Cisco IOS Release 12.3(21)BC
The following hardware features are new in Cisco IOS Release 12.3(21)BC:
Cisco Wideband SIP
The Cisco Wideband SPA interface processor (SIP) is a carrier card that inserts into a Cisco uBR10012 router slot like a line card. Each Wideband SIP supports two Cisco Wideband SPAs. The Wideband SIP provides no network connectivity on its own.
The Cisco Wideband SIP occupies two full height slots on the uBR10012 router. When the uBR1012 router is used as a wideband CMTS, slots 1/0 and 2/0 are used for the Wideband SIP. Online insertion and removal (OIR) is supported for both the Wideband SIP and the individual Wideband SPAs.
The Cisco Wideband SIP requires the Cisco uBR10012 Performance Routing Engine 2 (PRE-2).
For more information on the Cisco Wideband SIP, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide .
Cisco Wideband SPA
The Cisco Wideband shared port adapter (SPA) is a single-wide, half-height SPA that implements the DOCSIS 3.0 Downstream Channel Bonding feature. The Wideband SPA is used for downstream data traffic only. It has one active and one redundant Gigabit Ethernet port. The active port sends downstream data traffic to one or more external edge QAM devices.
The Cisco uBR10012 router can support up to two Wideband SPAs. Each Wideband SPA can support up to 12 logical wideband channels (bonding groups). Depending on how it is configured, each Wideband SPA allows up to 24 RF channels. Each logical wideband channel consists of multiple RF channels. The Cisco IOS CLI includes a set of commands to configure the Wideband SPA on the Cisco uBR10012 router.
The two Gigabit Ethernet ports on the Wideband SPA use small form-factor (SFP) modules. The SFP module is an input/output (I/O) device that plugs into a Gigabit Ethernet SFP port on the Wideband SPA, linking the port with an edge QAM device through a fiber-optic network.
For more information on the Cisco Wideband SPA, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide .
New Software Features in Cisco IOS Release 12.3(21)BC
The following software features are new in Cisco IOS Release 12.3(21)BC:
Automatic Virtual Interface Bundles
All cable bundles are now automatically converted and configured to be in a virtual bundle, and standalone cable interfaces must be manually configured to be in a virtual bundle to operate properly.
Previously, new virtual interface bundles and bundle members required reconfiguration, and there could also be standalone interfaces not part of a bundle at all.
The following guidelines describe the automatic virtual interface bundling:
•
•
•
•
•
•
•
•
•
•
For more information, see the Cable Interface Bundling and Virtual Interface Bundling for the Cisco CMTS chapter in the Cisco CMTS Feature Guide.
Cable DHCP Enhancements
When using an external DHCP server, the Cisco CMTS supports a number of options that can enhance operation of the cable network in certain applications.
Dynamic Cable Helper Address Selection
The cable helper-address command has been expanded to further specify where to forward DHCP packets based on origin: from a cable modem, MTA, STB, or other cable devices:
cable helper-address address [ cable-modem | host | mta | stb ]
This enables load-balancing of DHCP requests from cable modems and CPE devices by specifying different DHCP servers according to the cable interface or subinterface. You can also specify separate servers for cable modems and CPE devices.
When the mta or stb option is used, you must also use the cable dhcp-parse option-optnum command to parse the DHCP options.
If you specify only one option, the other types of devices (cable modem, host, mta, or stb) will not be able to connect with a DHCP server. You must specify each desired option in a separate command.
You may specify more than one helper address on each cable interface by repeating the command. You can specify more than 16 helper addresses, but the Cisco IOS software uses only the first 16 valid addresses.
If you do not specify an option, the helper-address will support all cable devices, and the associated DHCP server will accept DHCP packets from all cable device classes.
Cable Node Location Reporting
The DHCP Relay Agent can now be used to identify cloned modems or gather geographical information for E911 and other applications. Using the cable dhcp-insert command, users configure the CMTS to insert downstream, upstream, or hostname descriptors into DHCP packets:
cable dhcp-insert {downstream-description | hostname | upstream-description}
A DHCP server can then utilize such information to detect cloned modems or extract geographical information. Multiple types of strings can be configured as long as the maximum relay information option size is not exceeded.
Multiple types of descriptor strings can be configured as long as the maximum relay information option size is not exceeded.
show cable modem docsis device-class
The show cable modem docsis device-class command is now supported.
For more information on these enhancements and related commands, see the Cisco Broadband Cable Command Reference Guide and the "DHCP, ToD, and TFTP Services for the Cisco Cable Modem Termination System" chapter in the Cisco CMTS Feature Guide.
Cable Duplicate MAC Address Reject
Cisco IOS Release 12.3(21)BC introduces a DOCSIS 1.1-compliant and above security enhancement that helps to eliminate denial-of-service (DOS) attacks that are caused by cloned cable modems. A clone is presumed to be one of two physical cable modems on the same Cisco CMTS chassis with the same HFC interface MAC address. The cloned cable modem may be DOCSIS 1.0 or greater, and may be semi-compliant or non-compliant with portions of the DOCSIS specifications.
This feature is enabled by default on the Cisco CMTS, and has no associated command-line interface (CLI) configuration commands. This feature creates a new log message. By default, this message appears in the syslog, but may be moved into the cable layer2 event log using the configuration command cable logging layer2events.
For additional information about this feature, its causes, and the introduction of the new cable privacy bpi-plus-enforce command, which enforces DOCSIS 1.1 BPI+ on the cable network, refer to the following documents on Cisco.com and the Internet:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_ccmd.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
DOCSIS 3.0 Downstream Channel Bonding
Cisco IOS Release 12.3(21)BC introduces the DOCSIS 3.0 Downstream Channel Bonding feature, which is the key feature of the Cisco Cable Wideband Solution, Release 1.0. This feature and the Cisco Cable Wideband Solution require the following components:
•
•
•
The Cisco Cable Wideband Solution, Release 1.0, also requires these major components: edge QAM (EQAM) device and wideband cable modem.
In the Cisco Cable Wideband Solution, Release 1.0, the DOCSIS 3.0 Downstream Channel Bonding feature supports downstream wideband channels consisting of multiple bonded RF channels. The solution provides wideband data services over existing hybrid fiber coax (HFC) networks. With wideband data services, multiple RF channels are aggregated into a single logical wideband channel (bonding group) that delivers higher bandwidth to the wideband cable modem than was previously possible with DOCSIS 2.0 technology. This aggregation of RF channels is referred to generically as "channel bonding."
The Cisco Cable Wideband Solution, Release 1.0, can be deployed in parallel with DOCSIS 1.X/2.0 technology. The CMTS supports DOCSIS 1.X/ 2.0 modems on non-wideband ports while wideband cable modems deliver higher-speed throughput on the wideband ports.
For more information on the Cisco Cable Wideband Solution, Release 1.0, and the Cisco Wideband SIP and Cisco Wideband SPA, see these documents:
•
http://www.cisco.com/en/US/docs/cable/cmts/wideband/solution/guide/release_1.0/wb_solu.html
•
•
Enhanced Rate Bandwidth Allocation (ERBA) on the Cisco uBR10012 Router
Cisco IOS Release 12.3(21)BC introduces the ERBA feature on the Cisco uBR10012 CMTS with Performance Routing Engine 2 (PRE2) modules.
For additional information about ERBA in Cisco IOS Release 12.3(21)BC, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
HCCP Switchover Enhancements
Beginning in Cisco IOS Release 12.3(21)BC, the Cisco uBR10012 universal broadband router supports the HCCP Switchover Enhancements feature, with the following new support:
•
–
–
•
•
The HCCP Switchover Enhancements feature in Cisco IOS Release 12.3(21)BC has the following restrictions:
•
•
•
•
•
•
•
•
For more information refer to the Cisco CMTS Feature Guide at:
N+1 Redundancy for the Cisco Cable Modem Termination System
NSF Lite
The NSF Lite features RPR+ scaling and switchover performance enhancements. These enhancements will improve switchover times by keeping the Standby RP link state & Docsis(modem database) in full-sync with the Primary RP thus, enabling the Standby RP to begin forwarding traffic immediately after a switchover.
NSF Lite also provides routing enhancments for the OSPF NSF to minimize traffic outage during switchover.IDB-State Sync.
For additional information about Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router, refer to the following documents on Cisco.com:
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html
PacketCable Client Accept Timeout
Cisco IOS Release 12.3(21)BC introduces support for setting timeout values for COPS Telnet connections on the Cisco CMTS, and for clearing COPS telnet sessions.
Network or Cisco CMTS telnet errors can cause incomplete COPS sessions to be created. This new timeout timer enables the clearing and cleaning of allocated resources for the stale COPS Telnet sessions on the Cisco CMTS. This feature supports COPS for PacketCable on the Cisco CMTS.
If the Connection between a PacketCable CMS and the Cisco CMTS is not completely established, and the PacketCable CMS does not correctly terminate the session by sending a TCP FIN message, the connection otherwise shows a COPS server in the output of the show cops server command.
The timeout timer applies to each COPS Telnet connection on the Cisco CMTS, and expiration of this timeout setting triggers the termination of the Telnet session and clears supporting resources on the Cisco CMTS.
To set the timeout timer for Telnet COPS sessions on the Cisco CMTS, use the following command in global configuration mode. To remove this timeout timer, use the no form of this command.
packetcable timer client-accept seconds
no packetcable timer client-accept seconds
Syntax Description
To clear all COPS Telnet sessions and associated resources on the Cisco CMTS, use the following command in global configuration mode:
clear cops connection
For additional information, refer to the following documents on Cisco.com:
•
•
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Per Downstream Static Multicast
The IOS IGMP Static-Group feature was first introduced back in Release 11.2, while the Source Specific Multicast (SSM) extension was added in Release 12.0(6)T. This allows network administrators to configure the router to be a statically connected member of the specified group on the interface. All multicast traffic destined to that particular group will be forwarded out on that configured interface.
Beginning in Cisco IOS Release 12.3(21)B, the Cisco uBR10012 universal broadband router supports the Per Downstream Static Multicast feature. This feature provides several multicast enhancements and makes it possible to control the replication of static IP multicast streams within a cable bundle using the cable igmp static-group command on the physical cable downstream interface.
For additional information, refer to the following documents on Cisco.com:
Advanced-mode DOCSIS Set-Top Gateway 1.1 for the Cisco CMTS
RF Switch Firmware Version 3.60
Cisco RF Switch Firmware 3.60 is available to support N+1 Redundancy on the Cisco uBR10012 router. This Firmware version must be used with Cisco IOS Release 12.3(21)BC. Cisco RF Switch Firmware Version 3.60 provides the following changes, resolutions, enhancements, and updates:
•
•
•
•
•
For additional information about Cisco RF Switch Firmware Version 3.60, refer to the following documents on Cisco.com:
•
https://www.cisco.com/en/US/products/hw/cable/ps2929/prod_release_notes_list.html
•
•
https://www.cisco.com/en/US/docs/cable/rfswitch/ubr3x10/command/reference/rfswcr36.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
SAMIS Source Address Management
Cisco IOS Release 12.3(21)BC introduces Subscriber Account Management Interface Specification (SAMIS) enhancements which will provide the ability to set the source of the usage based billing packets originated by the router using the cable metering command. This enables the ip address to be set as the source of the loopback interface, similar to what is done for telnet or ftp (ip ftp source-interfacelo0).
For additional information about Subscriber Account Management Interface Specification (SAMIS), refer to the following document on Cisco.com:
Service Flow Admission Control
Cisco IOS Release 12.3(21)BC introduces Service Flow Admission Control (SFAC) on the Cisco Cable Modem Termination System.
SFAC on the Cisco CMTS is a mechanism that gracefully manages service flow admission requests when one or more resources are not available to process and support the incoming service request. Lack of such a mechanism not only causes the new request to fail with unexpected behavior but could potentially cause the flows that are in progress to have quality related problems. SFAC monitors such resources constantly, and accepts or denies requests depending on the resource availability.
SFAC enables you to provide a reasonable guarantee about the Quality of Service (QoS) to subscribers at the time of call admission, and to enable graceful degradation of services when resource consumption approaches critical levels. SFAC reduces the impact of unpredictable traffic demands in circumstances that would otherwise produce degraded QoS for subscribers.
SFAC uses two event types for resource monitoring and management—cable modem registration and dynamic service (voice call) requests. When either of these two events occurs on the Cisco CMTS, SFAC verifies that the associated resources conform to the configured limits prior to admitting and supporting the service call request.
SFAC is not a mechanism to apply QOS to the traffic flows. Scheduling and queuing are some of the mechanisms used for implementing the QOS. The QOS is applied on per packet basis. SFAC checks are performed before the flow is admitted.
SFAC in Cisco IOS Release 12.3(21)BC monitors the following resources on the Cisco CMTS.
•
•
•
For complete configuration and operation information, refer to the following documents on Cisco.com:
•
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_technical_reference_list.html
Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia
Cisco IOS Release 12.3(21)BC enhances high availability support that enables the synchronization of PacketCable and PacketCable MultiMedia (PCMM) gates during switchover events on the Cisco CMTS. This enhancement is enabled by default with Cisco IOS Release 12.3(21)BC and later supporting releases on the Cisco uBR10012 router and Cisco uBR7246VXR router.
This enhancement requires no additional configuration commands for line card redundancy in the Cisco N+1 Redundancy feature, nor the RPR+ Redundancy feature on the Cisco uBR10012 router. However, this functionality uses the existing per-interface HCCP commands that are used to associate the Working and Protect interfaces in the case of N+1 Redundancy.
This feature introduces the new debug packetcable hccp command to troubleshoot HCCP information specific to PacketCable and PCMM gates.
For additional information, refer to the following documents on Cisco.com:
•
•
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
New Hardware Features in Cisco IOS Release 12.3(17b)BC8
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC8.
New Software Features in Cisco IOS Release 12.3(17b)BC8
There are no new software features supported in Cisco IOS Release 12.3(17b)BC8.
New Hardware Features in Cisco IOS Release 12.3(17b)BC7
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC7.
New Software Features in Cisco IOS Release 12.3(17b)BC7
There are no new software features supported in Cisco IOS Release 12.3(17b)BC7.
New Hardware Features in Cisco IOS Release 12.3(17b)BC6
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC6.
New Software Features in Cisco IOS Release 12.3(17b)BC6
There are no new software features supported in Cisco IOS Release 12.3(17b)BC6.
New Hardware Features in Cisco IOS Release 12.3(17b)BC5
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC5.
New Software Features in Cisco IOS Release 12.3(17b)BC5
There are no new software features supported in Cisco IOS Release 12.3(17b)BC5.
New Hardware Features in Cisco IOS Release 12.3(17b)BC4
The following hardware feature is new in Cisco IOS Release 12.3(17b)BC4:
Cisco uBR10-MC5X20H Interface Line Card
Similar to the Cisco uBR10-MC5X20S and U cable interface line cards, the Cisco uBR10-MC5X20H line card is a 20 by 16 inch cards designed specifically for the Cisco uBR10012 router. It transmits and receives RF signals between the subscriber and the headend over hybrid fiber-coaxial (HFC) system.
Upstream data, from the subscriber, comes through the upstream ports (US0-US19), which the line card processes, configures and sends across the backplane to the WAN/backhaul card and out to the Internet.
Downstream data, to the subscriber, comes from the Internet through the WAN/backhaul card, and across the backplane to the cable interface line card, which processes, configures, and sends the data out through the appropriate downstream port (DS0-DS4) to be combined with the rest of the downstream signals in the headend.
The Cisco uBR10-MC5X20H line card supports both DOCSIS and EuroDOCSIS cable modem networks, in addition to downstream channels in the 70 to 860 MHz range, and upstream channels in the 5 to 65 MHz range. Each downstream port includes an onboard integrated upconverter. The cable interface line card supports Annex B and Annex A radio frequency (RF) data rates, channel widths, and modulation schemes and has DOCSIS MAC management and spectrum management capabilities. DOCSIS 2.0, A-TDMA rates are also supported.
The Cisco uBR10-MC5X20H has double the line card CPU speed, memory, and flash memory as the Cisco uBR10-MC5X20U, allowing support of Voice over IP (VoIP) at much higher call loads and a higher percentage of modems running advanced DOCSIS features that typically consume line card CPU resources.
New Software Features in Cisco IOS Release 12.3(17b)BC4
The following software features are new in Cisco IOS Release 12.3(17b)BC4:
Downstream Load Balancing Distribution with Upstream Load Balancing
Cisco IOS Release 12.3(17b)BC4 introduces further enhancements to downstream load balancing, resulting in equalized upstream load balancing group members. This enhancement synchronizes the pending statistic between different cable interface line cards in the load balancing group.
This enhancement performs downstream load balancing that accounts for loads on upstream channels in the same upstream load balancing group, rather than on the basis of the entire downstream channel load. Prior Cisco IOS releases may not have distributed cable modems evenly over individual upstream channels, nor in a way that accounted for downstream and upstream segment loads that account for one another.
This enhancement applies when downstream load balancing occurs on a headend system with separate upstream load balancing segments; the upstream segments are spread over multiple downstreams segments. This enhancement provides an alternative downstream load balancing scheme that accounts and makes use of per-upstream loads rather than total downstream loads.
For additional information about Load Balancing on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/ubr_load-bal_dcc.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
New Hardware Features in Cisco IOS Release 12.3(17b)BC3
There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC3.
New Software Features in Cisco IOS Release 12.3(17b)BC3
There are no new software features supported in Cisco IOS Release 12.3(17b)BC3.
New Hardware Features in Cisco IOS Release 12.3(17a)BC2
There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC2.
New Software Features in Cisco IOS Release 12.3(17a)BC2
The following software features are new in Cisco IOS Release 12.3(17a)BC2:
Cisco Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS
Cisco IOS Release 12.3(17a)BC2 introduces certified support for advanced-mode DOCSIS Set-Top Gateway (DSG) Issue 1.2. DSG Issue 1.2 introduces support for the latest DOCSIS Set-Top specification from CableLabs™:
•
Cisco Advanced-mode DSG 1.2 is certified by CableLabs™, and is a powerful tool in support of latest industry innovations. Advanced-mode DSG 1.2 offers substantial support for enhanced DOCSIS implementation in the Broadband Cable environment. The set-top box dynamically learns the overall environment from the Cisco Cable Modem Termination System (CMTS), to include MAC address, traffic management rules, and classifiers. DSG 1.2 supports the DOCS-DSG-IF-MIB as one component of this functionality:
For additional information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdsg12.html
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
DOCSIS1.0 TOS Overwrite
Currently, ToS overwrite requires the creation of static cable QoS profiles, which are then assigned to the ToS fields. This implementation works well if only a few different service types are offered. However, scalability issues arise when large numbers of service types are presented; each requiring a static QoS profile in order to perform ToS overwrite.
The Default DOCSIS 1.0 ToS Overwrite feature eliminates the need to create multiple QoS profiles in order to perform type-of-service (ToS) overwrite by automatically bounding all DOCSIS 1.0 Cable Modem (CM) created profiles to a default ToS overwrite.
New Hardware Features in Cisco IOS Release 12.3(17a)BC1
There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC1:
New Software Features in Cisco IOS Release 12.3(17a)BC1
There are no new software features supported in Cisco IOS Release 12.3(17a)BC1.
New Hardware Features in Cisco IOS Release 12.3(17a)BC
There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC.
New Software Features in Cisco IOS Release 12.3(17a)BC
The following software features are new in Cisco IOS Release 12.3(17a)BC:
•
•
•
•
•
•
•
•
•
Cable Monitor Enhancements
Cisco IOS Release 12.3(17a)BC introduces the following enhancements to the cable monitor feature:
•
•
For additional information about this enhancements to the cable monitor feature, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
CNEM Compliance
The Consistent Network Element Manageability (CNEM) Compliance feature enhances the network management capability of the CMTS platform by enabling the CMTS platform to be compliant with CNEM 1.3 requirements.
CNEM 1.3 requirements are designed to enable element management systems, with a minimum amount of effort, to maximize their coverage across the Cisco product line of network elements.
For additional information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
DOCSIS 2.0 SAMIS ECR Data Set
The Usage-Based Billing feature for the Cisco Cable Modem Termination System (CMTS) provides subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. The SAMIS format is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.
Release 12.3(17a)BC provides enhancements to the OSSI specifications, and billing reports (billing record format), added support to the CISCO-CABLE-METERING-MIB, which contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, added support for DCC and DCC for Load balancing and Downstream LLQ.
For additional information, refer to the following document on Cisco.com:
•
DSX Messages and Synchronized PHS Information
Cisco IOS Release 12.3(17a)BC introduces support for PHS rules in a High Availability environment. In this release, and later releases, PHS rules synchronize and are supported during a switchover event of these types:
•
•
For additional information about these enhancements, and related High Availability features, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html
Dynamic Channel Change (DCC) for Load Balancing
Cisco IOS Release 12.3(17a)BC introduces Dynamic Channel Change (DCC) and DCC for Load Balancing on the Cisco CMTS.
DCC in DOCSIS 1.1 dynamically changes cable modem upstream or downstream channels without forcing a cable modem to go offline, and without re-registration after the change. DCC supports four different initializations, instead of one, as in earlier DOCSIS support.
DCC and DCC for load balancing is supported on the Cisco uBR7246VXR router and the Cisco uBR10012 router with distributed cable interface line cards, including the Cisco MC28U and the Cisco MC5X20S/U/H.
•
•
•
•
Dynamic Channel Change for Load Balancing entails the following new or enhanced commands in Cisco IOS Release 12.3(17a)BC, and later releases:
Global Configuration Commands
•
•
•
•
•
Testing Command
•
For configuration, command reference, testing, and examples for DCC on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012
Cisco IOS Release 12.3(17a)BC introduces Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012.
Generic Route Encapsulation (GRE) is a tunneling protocol that can encapsulate a variety of packet types inside IP tunnels, creating a virtual point-to-point link to Cisco routers at remote points over an IP internetwork.
Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router
Cisco IOS Release 12.3(17a)BC introduces support for globally-configured HCCP N+1 Redundancy on the Cisco uBR10012 router. Cisco IOS Release 12.3(17a)BC supports both 4+1 and 7+1 Redundancy, in these High Availability configurations:
•
In this configuration, seven Working cable interface line cards are supported by one Protect cable interface line card. Two Cisco RF Switches are connected to seven MC5X20U/D cable interface line cards. Switchover events apply to an entire line card, rather than on an interface level, as in previous Cisco IOS releases supporting 7+1 Redundancy. Global configuration makes this High Availability feature easier to configure and use. 7+1 Redundancy is the default redundancy scheme for the Cisco uBR10012 router in Cisco IOS Release 12.3(17a)BC.
•
In this configuration, four Working cable interface line cards are supported by one Protect line card. One Cisco RF Switch is connected to five cable interface line cards. Switchover events apply to an entire line card.
Either form of N+1 Redundancy supports the Cisco uBR-MC5X20U/D broadband processing engine (BPE) on the Cisco uBR10012 router.
Note
Note
For additional information about HCCP 4+1 Redundancy, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
High Availability Support for Encrypted IP Multicast
Cisco IOS Release 12.3(17a)BC introduces support for IP Multicast streams during switchover events in a High Availability environment. This feature is supported for Route Processor Redundancy Plus (RPR+), N+1 Redundancy, and encrypted BPI+ streams.
For additional information about IP Multicast and High Availability, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
•
•
http://www.cisco.com/en/US/technologies/tk648/tk828/technologies_case_study0900aecd802e2ce2.html
•
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html
IPv6 over L2VPN
Beginning with Cisco IOS Release 12.3(17a)BC, the Cisco uBR10012 router now supports IPv6 using Layer 2 VPNs based on SID to 802.1q mapping. The Cisco uBR10012 router already supported Transparent LAN service with Layer 2 VPNs in Cisco IOS Release 12.3(13a)BC and later releases. As more Internet users switch to IPv6, the Cisco IPv6 protocol support helps enable the transition. IPv6 fixes a number of limitations in IPv4, such as limited numbers of available IPv4 addresses in addition to improved routing and network auto-configuration. This feature allows customers to introduce IPv6 into their network with minimal operational impact.
For additional information about this feature, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/tech/tk872/tsd_technology_support_protocol_home.html
Management Information Base (MIB) Changes and Enhancements
MIB enhancements in Cisco IOS Release 12.3(17a)BC provide enhanced management features that enable the Cisco uBR 7200 Series router and the Cisco uBR10012 router to be managed through the Simple Network Management Protocol (SNMP). These enhanced management features allow you to:
•
•
•
•
•
For additional information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
Pre-equalization Control for Cable Modems
Cisco IOS Release 12.3(17a)BC introduces pre-equalization control for cable modems on a per-modem basis. This feature enhances support for pre-equalization control on an interface basis, using the Organizational Unique Identifier (OUI), which is also supported.
When pre-equalization is enabled on an upstream interface, this feature allows you to disable pre-equalization adjustment selectively, for a specific cable modem or a group of cable modems. This feature prevents cable modems from flapping when processing pre-equalization requests sent from the Cisco CMTS.
Restrictions
This feature observes the following restrictions in Cisco IOS Release 12.3(17a)BC:
•
•
able pre-equalization exclude
To exclude a cable modem from pre-equalization during registration with the Cisco CMTS, use the cable pre-equalization exclude command in global configuration mode. Exclusion is supported for a specified cable modem, or for a specified OUI value for the entire interface. To remove exclusion for the specified cable modem or interface, use the no form of this command. Removing this configuration returns the cable modem or interface to normal pre-equalization processes during cable modem registration.
cable pre-equalization exclude {oui | modem} mac-addr
no cable pre-equalization exclude {oui | modem} mac-addr
Syntax Description
Command Default
Pre-equalization is enabled by default on the Cisco router, and for cable modems that have a valid and operational DOCSIS configuration file. When enabled, pre-equalization sends ranging messages for the respective cable modems. When disabled with the new exclude command, pre-equalization is excluded for the respective cable modems.
Command Modes
Global configuration mode
Command History
12.3(17a)BC
This command was introduced to the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
The pre-equalization exclusion feature should be configured for the running configuration of the Network Processing Engine (NPE), the Performance Routing Engine (PRE), and the line card console.
Examples
The following example configures pre-equalization to be excluded for the specified cable modem. Pre-equalization data is not sent for the corresponding cable modem:
Router(config)# cable pre-equalization exclude modem mac-addThe following example configures pre-equalization to be excluded for the specified OUI value of the entire interface. Pre-equalization data is not sent for the corresponding OUI value of the entire interface:
Router(config)# cable pre-equalization exclude oui mac-addrThe following series of commands configures pre-equalization on the Cisco uBR10012 router with MC5X20U BPEs. On the PRE Console, configure the following commands.
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# cable pre-equalization exclude oui 00.09.04Router(config)# endRouter# show runRouter# show running-config | inc ouicable pre-equalization exclude oui 00.09.04On the line card console for the same Cisco uBR10012 router, verify the configuration with the following command:
Router# show running-config | inc ouicable pre-equalization exclude oui 00.09.04The following series of commands configures pre-equalization on the Cisco uBR72436VXR router with MC28U cable interface line cards. On the Network Processing Engine (NPE) console, configure and verify with the following commands.
Router# conf tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# cable pre-equalization exclude oui 00.09.24Router(config)# endRouter# show run02:58:10: %SYS-5-CONFIG_I: Configured from console by consolenRouter# show running-config | inc ouicable pre-equalization exclude oui 00.09.24On the line card console for the same Cisco uBR7246VXR router, verify the configuration with the following command:
Router# show running-config | inc ouicable pre-equalization exclude oui 00.09.24After either of these exclusion methods for pre-equalization are configured, you can verify that all ranging messages do not include pre-equalization data. Use the following debug commands in global configuration mode:
•
•
Verify the ranging message for the non-excluded cable modems include pre-equalization data, and for the excluded cable modems, the ranging messages do not include such data.
The following example removes pre-equalization exclusion for the specified OUI and interface. This results in the cable modem or OUI to return to normal pre-equalization functions. Ranging messages resume sending pre-equalization data.
Router(config)# no cable pre-equalization exclude { oui | modem } mac-addrRemoval of this feature can be verified with the following debug command:
•
For additional information about this or other commands, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
PXF ARP Filter
Cisco IOS Release 12.3(17a)BC introduces PXF ARP Filter feature. The ARP filter now has a PXF component that filters ARP packets for identified "ARP offenders", thereby decreasing ARP punt rate and RP CPU usage.
For additional information, refer to the following document on Cisco.com
•
PXF Divert Rate Limiting
Cisco IOS Release 12.3(17a)BC introduces PXF Divert Rate Limiting feature. Rate-limiting on the divert path causes packets that will cause congestion to toRP queues to be dropped, before any packets have been queued, so valid packets are unaffected.
For additional information, refer to the following document on Cisco.com
•
show cable modem Command Changes
Cisco IOS Release 12.3(17a)BC introduces changes for two versions of the show cable modem command.
•
The information displayed with this command is revised. The DOCSIS 2.0 column in the Quality of Service (QoS) Provision Mode field has been removed, as this field is not applicable to QoS provisioning in DOCSIS 2.0.
Command Output in Cisco IOS Release 12.3(17a)BC and Later Releases
Router# show cable modem mac summaryCable Modem Summary-------------------Mac Version QoS Provision ModeInterface Total DOC2.0 DOC1.1 DOC1.0 Reg/Online DOC1.1 DOC1.0Cable5/1/0/U0 10 0 2 8 10 0 10Command Output in Cisco IOS Release 12.3(13a)BC and Earlier Releases
Router# show cable modem mac summaryCable Modem Summary-------------------Mac Version QoS Provision ModeInterface Total DOC2.0 DOC1.1 DOC1.0 Reg/Online DOC2.0 DOC1.1 DOC1.0Cable8/0/0/U0 8 0 5 3 5 0 5 0•
The information displayed with this command is revised. The MicroReflec column (MicroReflections) has been removed, and the DOCSIS Prov (DOCSIS Provider) column has been added in its place. This new column contains DOCSIS version information.
Command Output in Cisco IOS Release 12.3(17a)BC and Later Releases
Router#show cable modem phyMAC Address I/F Sid USPwr USSNR Timing DSPwr DSSNR Mode DOCSIS(dBmV) (dB) Offset (dBmV) (dB) Prov0003.e350.9a3f C5/1/0/U0 1 0.00 30.23 2811 0.00 ----- tdma 1.00050.734e.c1a1 C5/1/0/U0 2 0.00 30.47 2811 0.00 ----- tdma 1.00007.0e01.1749 C5/1/0/U0 3 0.00 30.65 2808 0.00 ----- tdma 1.00007.0e00.90dd C5/1/0/U0 4 0.00 30.66 2806 0.00 ----- tdma 1.00003.e350.9ad3 C5/1/0/U0 5 0.00 30.47 2810 0.00 ----- tdma 1.00003.e38f.f4e5 C5/1/0/U0 6 0.00 30.36 2813 0.00 ----- tdma 1.00003.e350.9b97 C5/1/0/U0 7 0.00 30.44 2812 0.00 ----- tdma 1.00003.e350.9bed C5/1/0/U0 8 0.00 30.16 2814 0.00 ----- tdma 1.00003.e308.455d C5/1/0/U0 9 0.00 30.79 2811 0.00 ----- tdma 1.00003.6bd6.bfaf C5/1/0/U0 10 0.00 30.40 2813 0.00 ----- tdma 1.0Command Output in Cisco IOS Release 12.3(13a)BC and Earlier Releases
Router#show cable modem phyMAC Address I/F Sid USPwr USSNR Timing MicroReflec DSPwr DSSNR Mode(dBmV) (dB) Offset (dBc) (dBmV) (dB)0008.0e06.7b14 C8/0/0/U0 1 0.00 30.36 1938 0 0.00 ----- tdma0050.f112.5977 C8/0/0/U0 2 0.00 30.36 1695 0 0.00 ----- tdma0090.837b.b0b9 C8/0/0/U0 3 0.00 30.64 1187 0 0.00 ----- tdma0007.0e03.6e99 C8/0/0/U0 5 0.00 30.36 2747 0 0.00 ----- tdma0007.0e04.5091 C8/0/0/U0 6 0.00 30.94 2746 0 0.00 ----- tdma0006.5314.81d9 C8/0/0/U0 7 0.00 30.36 2745 0 0.00 ----- tdma0003.6b1b.ee63 C8/0/0/U0 8 0.00 31.26 2745 0 0.00 ----- tdma0030.eb15.84e7 C8/0/0/U0 12 0.00 30.36 1157 0 0.00 ----- tdmaFor additional information about this or other commands, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Secure Socket Layer Server for Usage-Based Billing
Cisco IOS Release 12.3(17a)BC introduces support for the Secure Socket Layer (SSL) Server, used with the Usage-Based Billing feature of the Cisco CMTS. Usage-Based Billing implements the DOCSIS Subscriber Account Management Interface Specification (SAMIS) format.
This new capability enables the configuration of the SSL server between the Cisco CMTS and a collection server. Configuration, certificate creation, and debug commands are added or enhanced to support the SSL Server and certificates with the Usage-Based Billing feature.
For additional information, refer to the following document on Cisco.com:
•
SSM Mapping
Cisco IOS Release 12.3(17a)BC introduces Source-Specific Multicast (SSM) Mapping support on the Cisco uBR10012 router.
When the SSM Mapping feature is configured, if a router receives an IGMP version 1 or version 2 membership report for a particular group G, the router translates this in one or more SSM (S, G) channel memberships, such as IGMPv3 (S, G) INCLUDE membership reports) for the well known sources associated with this group.
When the router receives an IGMP version 1 or version 2 membership report for group G, the router uses SSM mapping to determine one or more source IP addresses (Si) for group G. SSM mapping then translates the membership report as an IGMP version 3 report INCLUDE (G, [S1, G], [S2, G]...[Sn, G] and continues as if it had received an IGMP version 3 report. The router then sends out PIM joins toward (S1, G) to (Sn, G) and continues to be joined to these groups as long as it continues to receive the IGMP version 1 or version 2 membership reports and as long as the SSM mapping for the group remains the same.
When SSM Mapping feature is statically configured on the router, the source address or addresses (S) can be discovered either by a statically configured table on the router or by consulting a DNS. When the statically configured table is changed, or when the DNS mapping changes, the router will leave join to the current sources associated with the joined groups.
For additional information about this feature, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html
New Hardware Features in Cisco IOS Release 12.3(13a)BC6
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC6:
New Software Features in Cisco IOS Release 12.3(13a)BC6
There are no new software features supported in Cisco IOS Release 12.3(13a)BC6.
New Hardware Features in Cisco IOS Release 12.3(13a)BC5
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC5:
New Software Features in Cisco IOS Release 12.3(13a)BC5
There are no new software features supported in Cisco IOS Release 12.3(13a)BC5.
New Hardware Features in Cisco IOS Release 12.3(13a)BC4
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC4:
New Software Features in Cisco IOS Release 12.3(13a)BC4
There are no new software features supported in Cisco IOS Release 12.3(13a)BC4.
New Hardware Features in Cisco IOS Release 12.3(13a)BC3
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC3:
New Software Features in Cisco IOS Release 12.3(13a)BC3
There are no new software features supported in Cisco IOS Release 12.3(13a)BC3.
New Hardware Features in Cisco IOS Release 12.3(13a)BC2
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC2:
New Software Features in Cisco IOS Release 12.3(13a)BC2
There are no new software features supported in Cisco IOS Release 12.3(13a)BC2.
New Hardware Features in Cisco IOS Release 12.3(13a)BC1
There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC1.
New Software Features in Cisco IOS Release 12.3(13a)BC1
There are no new software features supported in Cisco IOS Release 12.3(13a)BC1.
New Hardware Features in Cisco IOS Release 12.3(13a)BC
The following hardware features are new in Cisco IOS Release 12.3(13a)BC:
•
•
•
•
Cisco Half-Height Gigabit Ethernet Line Card
Cisco IOS Release 12.3(13a)BC introduces support for the new Cisco Half-Height Gigabit Ethernet line card (HHGE) for the Cisco uBR10012 router. The HHGE line card is a half-height, single-port, full-bandwidth Gigabit Ethernet line card providing multiple GigE links to the IP backbone. The HHGE line card also supports DOCSIS wideband capability through the Cisco uBR10012 universal broadband router.
The HHGE line card supports IEEE 802.3z-compliant Ethernet interface that can run up to 1 Gbps in full duplex mode. The HHGE line card supports single Ethernet interfaces based on SFP GBIC technology, supporting 1000BASE-SX and 1000BASE-LX/LH physical interfaces with SFP modules. It provides full-duplex 1 Gbps data rate with the PRE-2 performance routing engine module.
The following SFPs are supported by this line card:
•
•
•
Link spans of up to 100 km are possible using premium single-mode fiber or dispersion-shifted single-mode fiber. The SFP provides an optical link budget of 23 dB—the precise link span length depends on multiple factors such as fiber quality, number of splices, and connectors.
Restrictions
The HHGE line card cannot be used in slot 1 (subslot 1 or 0), or slot 2 (subslot 1 or 0) in the Cisco uBR10012 universal broadband router.
Additional Information
For additional information about the Cisco Half-Height Gigabit Ethernet Line Card, refer to the following documents on Cisco.com:
•
•
•
•
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/guide/u10kspec.html
Processor/IO Memory for the PRE1 Route Processor Module
Cisco IOS Release 12.3(13a)BC introduces support for and availability of additional processor and input/output (I/O) memory for PRE1 route processor modules on the Cisco uBR10012 router.
Cisco uBR10-MC5X20S/U Broadband Processing Engine
Commencing with Cisco IOS Release 12.3(9a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:
•
•
Commencing with Cisco IOS Release 12.3(13a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these and additional features:
•
•
•
•
•
Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
The Cisco uBR10012 OC-48 DPT/POS interface module supports both PRE1 and PRE2 performance routing engine modules in the Cisco uBR10012 router chassis. The Cisco OC-48 DPT/POS interface module is a dual-mode module, providing interface support for Packet over SONET (POS) or Spatial Reuse Protocol (SRP).
For additional information about installing and configuring the Cisco uBR10012 OC-48 DPT/POS interface module, refer to these documents on Cisco.com:
•
•
Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 performance routing engine 2 (PRE2) route processing modules.
The Cisco uBR10012, which is qualified for PacketCable 1.0, Data over Cable Service Interface Specifications (DOCSIS) 1.1 and EuroDOCSIS 1.1, is built to meet the current and future needs of multiple system operators (MSOs). With full Layer 3 routing capabilities and industry-leading capacity and scalability, the Cisco uBR10012 delivers the highest level of performance for mass deployment of next-generation IP services.
The Cisco uBR10012 is designed to meet the services, performance, and reliability required for large-scale multiservice applications. The Cisco uBR10012 allows cable providers to deliver value-added IP services with consistent high performance. Based on Cisco IOS® Software—the standard in routing technology—the Cisco uBR10012 offers the most advanced networking and routing options available.
The Cisco uBR10012 features these components:
•
•
•
•
•
Benefits of the Cisco uBR10012 PRE2 include the following:
•
•
•
•
•
Table 4 provides additional details about the features and benefits of the Cisco uBR10012 PRE2.
Upgrading from Cisco uBR10012 PRE or PRE1 Modules to Cisco uBR10012 PRE2 Modules
For information about insertion, removal and upgrade of Field Replaceable Units such as the PRE2 modules, refer to the following document on Cisco.com:
•
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_quick_start09186a00802b5eaa.html
New Software Features for Cisco IOS Release 12.3(13a)BC
This section describes the following new software features and CLI command changes for Cisco IOS Release 12.3(13a)BC and the Cisco uBR10012 router:
•
•
•
•
•
•
•
•
•
•
•
•
–
–
•
•
•
•
•
•
•
•
•
Access Control List Support for COPS Intercept
Cisco IOS Release 12.3(13a)BC introduces enhanced support for Access Control Lists (ACLs) and associated commands for the Common Open Policy Service (COPS) feature.
To configure access control lists (ACLs) for inbound connections to all COPS listener applications on the Cisco CMTS, user the cops listeners access-list command in global configuration mode. To remove this setting from the Cisco CMTS, us the no form of this command.
cops listeners access-list {acl-num | acl-name}
no cops listeners access-list {acl-num | acl-name}
Syntax Description
Note
Additional Information
Refer also the Service Independent Intercept (SII) feature in this document. For additional information, refer to the following documents on Cisco.com:
•
•
•
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml
Admission Control for the Cisco CMTS
Cisco IOS Release 12.3(13a)BC introduces Admission Control for the Cisco Cable Modem Termination System (CMTS).
Admission Control for the Cisco Cable Modem Termination System (CMTS) is a multifaceted feature that implements a Quality of Service (QoS) policy on the CMTS Headend. Admission Control establishes efficient resource and bandwidth utilization in a way that was not possible in prior Cisco IOS releases.
Admission Control monitors multiple system-level resources on the Cisco CMTS, and performs automatic resource allocation on a service-request basis. Admission Control maintains optimal system-level operation by preventing resource consumption that would otherwise degrade the performance for the entire Cisco CMTS. Furthermore, Admission Control can allocate upstream or downstream bandwidth resources to specific DOCSIS traffic types, and maintain such prioritization amidst very dynamic traffic conditions.
Admission Control uses two event types for resource monitoring and management—cable modem registration and dynamic service (voice call) requests. When either of these two events occurs on the Cisco CMTS, Admission Control verifies that the associated resources conform to the configured limits prior to admitting and supporting the service call request.
Admission Control is not a mechanism to apply QOS to the traffic flows. Scheduling and queuing are some of the mechanisms used for implementing the QOS. The QOS is applied on a per-packet basis. Admission Control checks are performed before the flow is committed.
Admission Control in Cisco IOS Release 12.3(13)BC monitors the following resources on the Cisco CMTS.
•
•
•
Cisco IOS Release 12.3(13a)BC introduces new configuration, debug and show commands for Admission Control on the Cisco CMTS. For additional information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_adm.html
Advanced-mode DOCSIS Set-Top Gateway Issue 1.1
Cisco IOS Release 12.3(13a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.1 on the Cisco uBR10012 router. DSG 1.1 builds on and supports the enhancements of DOCSIS Set-Top Gateway Issue 1.0 in the prior Cisco IOS 12.3(9a)BC release.
A-DSG 1.1 introduces powerful support for DOCSIS 1.1 and DOCSIS 2.0, and the latest DOCSIS DSG specifications. The benefits provided by A-DSG include the following:
•
•
•
•
•
•
•
These powerful advantages maximize the performance and return of hybrid fiber-coaxial (HFC) plant investments.
Changes from Cisco DSG 1.0
DSG Issue 1.0 is oriented to the DOCSIS DSG-I01 specifications, while DSG Issue 1.1 is oriented towards DOCSIS DSG-I02 specifications, to include the new Advanced Mode DSG (A-DSG).
The following DSG 1.1 features are supported in 12.3(13a)BC while continuing support for Basic Mode DSG:
•
•
Unlike earlier issues of DSG, Advanced-mode DSG (A-DSG) uses a DOCSIS MAC Management Message called the Downstream Channel Descriptor (DCD) message, and this DCD message manages the DSG Tunnel traffic. The DCD message is sent once per second on each downstream and is used by the DSG Client to determine which tunnel and classifier to use.
The DCD has a DSG address table located in the DOCSIS MAC management message. The primary difference between DSG 1.0 (and earlier issues) and A-DSG 1.1 is that advanced mode uses DCD messages to manage the DSG tunnels.
The DCD message contains a group of DSG Rules and DSG Classifiers, including the following:
•
•
•
•
•
•
•
Prerequisites for DSG 1.1
•
•
•
–
Note
http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_end-of-life_notice0900aecd80183921.html
–
–
Restrictions and Caveats for DSG 1.1
Cisco DSG 1.1 has the following restrictions:
•
•
•
•
•
Additional Information about DSG 1.1
•
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00802065c8.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_white_paper09186a00801b3f0f.shtml
•
Advanced Spectrum Management Support on the Cisco uBR10012 CMTS
Cisco IOS release 12.3(13a)BC introduces Advanced Spectrum Management for the Cisco uBR10012 router, with the following enhancements:
•
Note
http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_end-of-life_notice0900aecd80183921.html
•
•
•
•
•
•
Commands for Enhanced Spectrum Management
A variety of commands for enhanced spectrum management now provide new options.
•
•
•
•
•
•
Note
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html
For additional information about spectrum management and advanced spectrum management on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html
•
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_spctrm_mgt.html
Backup Path Testing for the Cisco RF Switch
Cisco IOS Release 12.3(13a)BC introduces the show hccp channel switch Cisco IOS command, wherein the Cisco RF Switch communicates with each module in the chassis to provide information as programmed in the RF Switch module bitmap. Cisco IOS Release 12.3(13a)BC performs polling every 10 seconds in response to this command, and reports RF Switch information as stored in cache. In normal operation, the switch requires from two to five seconds for SNMP response.
If SNMP errors are detected in response to this command, the switch may require a significantly longer timeout period. Cisco IOS Release 12.3(13a)BC introduces a keyboard break sequence to disrupt this timeout in such circumstances.
To introduce a break for the show hccp channel switch command, use the Ctrl-Shift-6-x break sequence—hold Ctrl-Shift keys, then press 6 then x.
After the break sequence, use the show hccp g m channel command to examine each individual HCCP member of a group, as required.
For additional information about HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html#wp1043160
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines
Cisco IOS Release 12.3(13a)BC introduces support for the Cable Monitor feature for the Cisco MC5x20U-D broadband processing engine (BPE) and the Cisco MC28U cable interface line card. These field replaceable units (FRUs) apply to the Cisco uBR10012 router, and the latter to the Cisco uBR7246VXR router. This feature enables intercept and monitoring capabilities for DOCSIS-compliant frames.
Note
Note
The Cable Monitor and Intercept features for Cisco Cable Modem Termination System (CMTS) routers provide a software solution for monitoring and intercepting traffic coming from a cable network. This feature also gives service providers Lawful Intercept capabilities, such as those required by the Communications Assistance for Law Enforcement Act (CALEA).
The following example configures cable monitor for a specific interface and the associated MAC addresses:
Router(config)# interface Cable3/0Router(config-if)# cable monitor interface GigabitEthernet0/1mac-address 000e.5cc8.fa5fpacket-type data ethernetRouter(config-if)#mac-address 000e.5cac.59f8packet-type data ethernetTo display cable monitor configuration and status information, use the show interfaces command in Privileged EXEC mode:
Router# show interfaces cable 3/0 monitorUS/ Time Outbound Flow Flow Type Flow Packet MAC MAC EncapDS Stmp Interface Type Identifier Extn. Type Extn. Type Typeall no Gi0/1 mac-addr 000e.5cc8.fa5f yes data no - ethernetall no Gi0/1 mac-addr 000e.5cac.59f8 yes data no - ethernetTo display and monitor traffic statistics and counters over time, use the show cable modem counters and the show interfaces commands in Privileged EXEC mode, as illustrated:
Router# show interfaces cable 3/0 monitorUS/ Time Outbound Flow Flow Type Flow Packet MAC MAC EncapDS Stmp Interface Type Identifier Extn. Type Extn. Type Typeall no Gi0/1 mac-addr 000e.5cc8.fa5f yes data no - ethernetall no Gi0/1 mac-addr 000e.5cac.59f8 yes data no - ethernetRouter# show cable modem 000e.5cac.59f8 countersMAC Address US Packets US Bytes DS Packets DS Bytes000e.5cac.59f8 7537986 3828867645 7199188 3711248288Router# show interfaces GigabitEthernet 0/1GigabitEthernet0/1 is up, line protocol is upHardware is BCM1250 Internal MAC, address is 000e.d6bd.2001 (bia 000e.d6bd.2001)Description: ***Sonde_analyse_trafic***Internet address is 82.216.52.1/30MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full-duplex, 100Mb/s, media type is RJ45output flow-control is XON, input flow-control is XONARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:08, output 00:00:01, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/5/0 (size/max/drops/flushes); Total output drops:361Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec1094862 packets input, 70425672 bytes, 0 no bufferReceived 0 broadcasts, 5 runts, 0 giants, 0 throttles0 input errors, 10 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog, 37 multicast, 0 pause input0 input packets with dribble condition detected188665 packets output, 29355747 bytes, 0 underruns <<< 188665 packets0 output errors, 0 collisions, 6 interface resets0 babbles, 0 late collision, 0 deferred12 lost carrier, 0 no carrier, 0 pause output0 output buffer failures, 0 output buffers swapped outWhen cable monitor is active, counters for the above commands should increase over time. For additional information about cable monitoring on the Cisco CMTS, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
COPS TCP Support for the Cisco Cable Modem Termination System
Cisco IOS Release 12.3(13a)BC introduces optimized support for the Common Open Policy Service (COPS) feature for the Cisco uBR10012 router. This feature supports two new configuration commands for enabling and setting COPS processes. The COPS feature in Cisco 12.3(13a)BC enables the following COPS functions:
COPS DSCP Marking for the Cisco CMTS
This feature allows you to change the DSCP marking for COPS messages that are transmitted or received by the Cisco router. Differentiated Services Code Point (DSCP) values are used in Quality of Service (QoS) configurations on a Cisco router. DSCP summarizes the relationship between DSCP and IP precedence.
Cisco IOS Release 12.3(13a)BC supports this function with the cops ip dscp command in global configuration mode.
COPS TCP Window Size for the Cisco CMTS
This feature allows you to override the default TCP receive window size that is used by COPS processes. This setting can be used to prevent the COPS server from sending too much data at one time.
Cisco IOS Release 12.3(13a)BC supports this function with the cops tcp window-size command in global configuration mode.
Note
cops ip dscp
To specify the marking for COPS messages that are transmitted by the Cisco router, use the cops ip dscp command in global configuration mode. To remove this configuration, use the no form of this command.
cops ip dscp x
no cops ip dscp
Syntax Description
Defaults
•
•
Usage Guidelines
•
•
•
Examples
The following example illustrates the cops ip dscp command with supported command variations:
Router(config)# cops ip dscp ?<0-63> DSCP valueaf11 Use AF11 dscp (001010)af12 Use AF12 dscp (001100)af13 Use AF13 dscp (001110)af21 Use AF21 dscp (010010)af22 Use AF22 dscp (010100)af23 Use AF23 dscp (010110)af31 Use AF31 dscp (011010)af32 Use AF32 dscp (011100)af33 Use AF33 dscp (011110)af41 Use AF41 dscp (100010)af42 Use AF42 dscp (100100)af43 Use AF43 dscp (100110)cs1 Use CS1 dscp (001000) [precedence 1]cs2 Use CS2 dscp (010000) [precedence 2]cs3 Use CS3 dscp (011000) [precedence 3]cs4 Use CS4 dscp (100000) [precedence 4]cs5 Use CS5 dscp (101000) [precedence 5]cs6 Use CS6 dscp (110000) [precedence 6]cs7 Use CS7 dscp (111000) [precedence 7]default Use default dscp (000000)ef Use EF dscp (101110)Additional COPS Information
Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.
For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll
cops tcp window-size
To override the default TCP receive window size on the Cisco CMTS, use the cops tcp window-size command in global configuration mode. This setting allows you to prevent the COPS server from sending too much data at one time. To return the TCP window size to a default setting of 4K, use the no form of this command.
cops tcp window-size bytes
no cops tcp window-size
Syntax Description
Defaults
The default COPS TCP window size is 4000 bytes.
Usage Guidelines
This command does not affect existing connections to COPS servers. Once you issue this command, this function is supported only for new connections after that point in time.
Examples
The following example configures the TCP window size to be 64000 bytes.
Router(config)# cops tcp window-size 64000The following example illustrates online help for this command:
Router(config)# cops tcp window-size ?<516-65535> Size in bytesAdditional COPS Information
Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.
For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll
DHCP MAC Address Exclusion List for cable-source verify dhcp Command
Cisco IOS Release 12.3(13a)BC introduces the ability to exclude trusted MAC addresses from standard DHCP source verification checks, as supported in previous Cisco IOS releases for the Cisco CMTS. This feature enables packets from trusted MAC addresses to pass when otherwise packets would be rejected with standard DHCP source verification. This feature overrides the cable source-verify command on the Cisco CMTS for the specified MAC address, yet maintains overall support for standard and enabled DHCP source verification processes. This feature is supported on Performance Routing Engine 1 (PRE1) and PRE2 modules on the Cisco uBR10012 router chassis.
To enable packets from trusted source MAC addresses in DHCP, use the cable trust command in global configuration mode. To remove a trusted MAC address from the MAC exclusion list, use the no form of this command. Removing a MAC address from the exclusion list subjects all packets from that source to standard DHCP source verification.
cable trust mac-address
no cable trust mac-address
Syntax Description
mac-address
The MAC address of a trusted DHCP source, and from which packets will not be subject to standard DHCP source verification.
Usage Guidelines
This command and capability are only supported in circumstances in which the Cable Source Verify feature is first enabled on the Cisco CMTS.
When this feature is enabled in addition to cable source verify, a packet's source must belong to the MAC Exclude list on the Cisco CMTS. If the packet succeeds this exclusionary check, then the source IP address is verified against Address Resolution Protocol (ARP) tables as per normal and previously supported source verification checks. The service ID (SID) and the source IP address of the packet must match those in the ARP host database on the Cisco CMTS. If the packet check succeeds, the packet is allowed to pass. Rejected packets are discarded in either of these two checks.
Any trusted source MAC address in the optional exclusion list may be removed at any time. Removal of a MAC address returns previously trusted packets to non-trusted status, and subjects all packets to standard source verification checks on the Cisco CMTS.
For additional information about the enhanced Cable Source Verify DHCP feature, and general guidelines for its use, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/sourcver.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/cblsrcvy.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/tech/tk86/tk803/technologies_tech_note09186a00800a7828.shtml
DOCSIS 1.0 Concatenation Override
Cisco IOS release 12.3(13a)BC introduces support for the DOCSIS 1.0 concatenation override feature on the Cisco uBR10012 router. This feature provides the ability to disable concatenation on DOCSIS 1.0 cable modems, even in circumstances where concatenation is otherwise supported for the upstream channel.
DOCSIS 1.0 concatenation allows the cable modem to make a single-time slice request for multiple packets, and to send all packets in a single large burst on the upstream. Concatenation was introduced in the upstream receive driver in the previous Cisco IOS releases that supported DOCSIS 1.0 +. Per-SID counters were later added in Cisco IOS release 12.1(4)CX for debugging concatenation activity.
In some circumstances, overriding concatenation on DOCSIS 1.0 cable modems may be preferable, and Cisco IOS release 12.3(13a)BC supports either option.
Note
To enable DOCSIS 1.0 concatenation override with Cisco IOS release 12.3(13a)BC and later releases, use the new docsis10 keyword with the previously supported cable upstream n concatenation command in privileged EXEC mode:
cable upstream n concatenation docsis10
Syntax Description
n
Specifies the upstream port number. Valid values start with 0 for the first upstream port on the cable interface line card.
Examples
The following example illustrates DOCSIS 1.0 concatenation override on the Cisco uBR10012 router:
Router# no cable upstream 0 concatenation docsis10In this example, DOCSIS 1.0 cable modems are updated with REG-RSP so that they are not permitted to use concatenation.
For additional information about this command, refer to the Cisco IOS CMTS Cable Command Reference on Cisco.com:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
DOCSIS BPI+ Multiple Root Certificate Support
Cisco IOS Release 12.3(13a)BC introduces support for multiple DOCSIS root certificates with Baseline Privacy Interface Plus (BPI+) on the Cisco CMTS. This feature enables the Cisco CMTS to support either North American or European cable modems, with the following guidelines for implementation:
•
•
Dynamic SID/VRF Mapping Support
Cisco IOS release 12.3(13a)BC introduces support for dynamic service ID (SID) and VRF mapping on the Cisco CMTS, to support Voice over IP (VoIP) with MPLS. Formerly, the MPLS SID mapping feature only applied to provisioned service flows. This feature enables the mapping of all PacketCable DQoS service flows to one particular VRF.
For additional information, refer to the following:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/sfidmpls.html
Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems
Cisco IOS release 12.3(13a)BC introduces Enhanced Rate Bandwidth Allocation (ERBA) support for DOCSIS 1.0 cable modems and the Cisco uBR10012 router. ERBA allows DOCSIS1.0 modems to burst their temporary transmission rate up to the full line rate for short durations of time. This capability provides higher bandwidth for instantaneous bandwidth requests, such as those in Internet downloads, without having to make changes to existing service levels in the QoS Profile.
This feature enables MSOs to set the DOCSIS 1.0 cable modems burst transmissions, with mapping to overriding DOCSIS 1.1 QoS profile parameters on the Cisco CMTS. DOCSIS 1.0 cable modems require DOCSIS 1.0 parameters when registering to a matching QoS profile. This feature enables maximum downstream line rates, and the ERBA setting applies to all cable modems that register to the corresponding QoS profile.
Note
ERBA for DOCSIS 1.0 cable modems is supported with these new or enhanced commands or keywords in Cisco IOS release 12.3(13a)BC:
•
•
To define ERBA on the downstream for DOCSIS 1.0 cable modems, use the cable qos promax-ds-burst command in global configuration mode. To remove this ERBA setting from the QoS profile, use the no form of this command.
cable qos pro max-ds-burst burst-size
no cable qos pro max-ds-burst
Syntax Description
To display ERBA settings as applied to DOCSIS 1.0 cable modems and QoS profiles on the Cisco CMTS, use the show cable qos profile command in Privileged EXEC mode.
The following example of the cable qos profile command in global configuration mode illustrates changes to the cable qos profile command. Fields relating to the ERBA feature are shown in bold for illustration:
Router(config)# cable qos pro 10 ?grant-interval Grant intervalgrant-size Grant sizeguaranteed-upstream Guaranteed Upstreammax-burst Max Upstream Tx Burstmax-ds-burst Max Downstream Tx burst (cisco specific)max-downstream Max Downstreammax-upstream Max Upstreamname QoS Profile name string (cisco specific)priority Priorityprivacy Cable Baseline Privacy Enabletos-overwrite Overwrite TOS byte by setting mask bits to valueThe following example of the show cable qos profile command illustrates that the maximum downstream burst has been defined, and is a management-created QoS profile:
Router# show cable qos proID Prio Max Guarantee Max Max TOS TOS Create B IP prec.upstream upstream downstream tx mask value by priv ratebandwidth bandwidth bandwidth burst enab enab1 0 0 0 0 0 0xFF 0x0 cmts(r) no no2 0 64000 0 1000000 0 0xFF 0x0 cmts(r) no no3 7 31200 31200 0 0 0xFF 0x0 cmts yes no4 7 87200 87200 0 0 0xFF 0x0 cmts yes no6 1 90000 0 90000 1522 0xFF 0x0 mgmt yes no10 1 90000 0 90000 1522 0x1 0xA0 mgmt no no50 0 0 0 96000 0 0xFF 0x0 mgmt no no51 0 0 0 97000 0 0xFF 0x0 mgmt no noThe following example illustrates the maximum downstream burst size in sample QoS profile 10 with the show cable qos prof verbose command in privileged EXEC mode:
Router# show cable qos pro 10 verProfile Index 10NameUpstream Traffic Priority 1Upstream Maximum Rate (bps) 90000Upstream Guaranteed Rate (bps) 0Unsolicited Grant Size (bytes) 0Unsolicited Grant Interval (usecs) 0Upstream Maximum Transmit Burst (bytes) 1522Downstreamam Maximum Transmit Burst (bytes) 100000IP Type of Service Overwrite Mask 0x1IP Type of Service Overwrite Value 0xA0Downstream Maximum Rate (bps) 90000Created By mgmtBaseline Privacy Enabled noUsage Guidelines
If a cable modem registers with a QoS profile that matches one of the existing QoS profiles on the Cisco CMTS, then the maximum downstream burst size, as defined for that profile, is used instead of the default DOCSIS QoS profile of 1522.
For example, a DOCSIS 1.0 configuration that matches QoS profile 10 in the previous examples would be as follows:
03 (Net Access Control) = 104 (Class of Service Encodings Block)S01 (Class ID) = 1S02 (Maximum DS rate) = 90000S03 (Maximum US rate) = 90000S06 (US burst) = 1522S04 (US Channel Priority) = 1S07 (Privacy Enable) = 0The maximum downstream burst size (as well as the ToS overwrite values) are not explicitly defined in the QoS configuration file because they are not defined in DOCSIS. However, because all other parameters are a perfect match to profile 10 in this example, then any cable modem that registers with these QoS parameters has a maximum downstream burst of 100000 bytes applied to it.
For further illustration, consider a scenario in which packets are set in lengths of 1000 bytes at 100 packets per second (pps). Therefore, the total rate is a multiplied total of 1000, 100, and 8, or 800kbps.
To change these settings, two or more traffic profiles are defined, with differing downstream QoS settings as desired. Table 5 provides two examples of such QoS profiles for illustration:
In this scenario, both QoS profiles are identical except for the max-ds-burst size, which is set to 5000 in QoS profile 101 and 5000 in QoS profile 102.
Optimal Settings for ERBA
DOCSIS allows the setting different token bucket parameters for each service flow, including the token bucket burst size. When burst sizes are closer to 0, QoS is enforced in a stricter manner, allowing a more predictable sharing of network resources, and as a result easier network planning.
When burst sizes are larger, individual flows can transmit information faster (lower latency), although the latency variance can be larger as well.
For individual flows, a larger burst size is likely to be better. As long as the system is not congested, a large burst size reduces the chances of two flows transmitting at the same time, because each burst is likely to take less time to transmit. However, as channel bandwidth consumption increases, it is probably that large burst traffic would exceed the thresholds of buffer depths, and latency is longer than with well shaped traffic.
For additional information about the cable qos profile command and configuring QoS profiles, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
High Availability Features
Cisco IOS release 12.3(13a)BC introduces several High Availability features on the Cisco uBR10012 router:
•
•
•
•
Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events
Cisco IOS release 12.3(13a)BC introduces the Auto-Revert feature for the Cisco uBR10012 router, to further enhance HCCP N+1 Redundancy on the Cisco CMTS. With this feature, when a switchover event is performed in manual fashion, from the HCCP Protect line card, and the Protect line card has a hardware fault, HCCP automatically reverts back to the HCCP Working line card. This is a very helpful feature, in that periodic switchovers can be performed for regular maintenance or testing purposes, yet subscriber service is not interrupted should such switchovers reveal unexpected problems with HCCP Protect line cards.
For further information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Global N+1 Redundancy
Cisco IOS release 12.3(13a)BC introduces the Global N+1 Linecard Redundancy (or, HCCP Rapid Configuration) feature on the Cisco uBR10012 router to streamline the configuration of N+1 line card redundancy. The feature implements a simpler command-line interface (CLI) to establish the Working and Protect line card relationships, which no longer requires configuration of the legacy hccp interface configuration commands.
For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Shutdown and No Shutdown Enhancement for Cable Interfaces
Cisco IOS release 12.3(13a)BC introduces a new behavior with the [no] shutdown interface configuration command. In HCCP N+1 Redundancy schemes, an interface that is shut down with the shutdown command does not create an HCCP Switchover event for the associated Working or Protect interface. Instead, cable modems go offline and return online when the no shutdown command is issued.
For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
MIBs Enhancements
Subinterface support in ifTable Object
Cisco IOS Release 12.3(13a)BC introduces enhanced SNMP MIB support in which subinterface information is included in the ifTable for the associated device. This enhanced ifTable provides new subinterface information in addition to the main interface information previously supported in earlier Cisco IOS releases.
This subinterface MIB information is only supported in the ifTable if an IP address is assigned to the subinterface and the main interface under which it resides. This subinterface MIB information is not supported when the IP address of a main or subinterface is removed with the no interface command in interface configuration mode.
For additional information about the ifTable and SNMP MIBs for the Cisco CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
Multicast QoS Support on the Cisco uBR10012 CMTS
Cisco IOS Release 12.3(13a)BC introduces support for Multicast downstream QoS feature. This feature provides the ability to assign static mapping to a multicast group. The Multicast downstream QoS feature uses the existing infrastructure (DOCSIS 1.1 service flow) to assign a multicast service identifier (SID) to a multicast group used in the Baseline Privacy Interface (BPI) encryption feature.
When disabled, the Multicast downstream QoS feature does not impact any other features. The multicast packets to downstream cable interfaces are sent to the default service flow.
This feature is being implemented in response to CSCeg22989 which states, multicast traffic is not classified to any service flow, and therefore ends up queued on the default service flow. The default service flow has no specific QoS guarantees assigned to it. So once the interface approaches congestion level, multicast packets may be dropped.
Restrictions
•
•
•
•
•
New and Changed Commands
cable match address
Use the existing "cable match" command to assign QoS to a multicast group, with BPI either enabled or disabled.
Router# cable match address <number>|<name> [service-class <name> [bpi-enable]]Router# no cable match address [<number>|<name> [service-class <name> [bpi-enable]]]debug cable mcast-qos
Use this command to turn on CMTS Multicast Qos debugging.
Router# debug cable mcast-qosOnline Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router
Cisco IOS Release 12.3(13a)BC introduces support for Online Offline Diagnostics (OOD) in the field for the Cisco uBR1002 router, including support in a high availability environment with HCCP N+1 Redundancy. The Online Offline Diagnostics (OOD) feature introduces a Field Diagnostic tool that provides a method of testing and verifying line card hardware problems.
This feature is supported on the following field replaceable units (FRUs) of the Cisco uBR10012 router:
•
•
•
To view a list of hardware on the Cisco uBR10012 router that is supported by Field Diagnostics, refer to the following document:
•
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/troubleshooting/fdub10k.html
If you would like to perform a hardware diagnostic test on a line card in your Cisco uBR10000 series router, an OOD Field Diagnostic image can be downloaded free of charge from Cisco Systems and used to test whether the line card problems are indeed due to faulty hardware. The test results verify whether or not the hardware is faulty.
Optional Upstream Scheduler Modes
With this feature, the user is able to select either Unsolicited Grant Services (UGS) or Real Time Polling Service (rtPS) scheduling types, as well as packet-based or TDM-based scheduling. Low latency queueing (LLQ) emulates a packet-mode-like operation over the Time Division Multiplex (TDM) infrastructure of DOCSIS. As such, the feature provides the typical tradeoff between packets and TDM: with LLQ, the user has more flexibility in defining service parameters for UGS or rtPS, but with no guarantee (other than statistical distribution) regarding parameters such as delay and jitter.
Restrictions
•
•
•
New and Changed Commands
cable upstream n scheduling type
Use this new command to turn the various scheduling modes on or off, where n specifies the upstream port.
Router(config-if)# [no] cable upstream n scheduling type [ugs | rtps] mode [llq | docsis]For additional information about scheduler enhancements on the Cisco CMTS, refer to the following:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/cmtsfg.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
PacketCable Emergency 911 Cable Interface Line Card Prioritization
Cisco IOS Release 12.3(13a)BC introduces PacketCable Emergency 911 cable interface line cad prioritization on the Cisco CMTS. This feature enables cable interface line cards that are supporting an Emergency 911 call to be given automatic priority over cable interface line cards supporting non-emergency voice calls, even in the case of HCCP switchover events. In such cases, Protect HCCP line card interfaces automatically prioritize service to Emergency 911 voice calls, should Working HCCP cable interface line cards be disrupted. This feature is enabled by default in Cisco IOS release 12.3(13a)BC, and may not be disabled with manual configuration.
Note
During HCCP switchover events, cable modems recover in the following sequence in Cisco IOS release 12.3(13a)BC:
1.
2.
3.
4.
To view information about Emergency 911 voice events and cable interface line card prioritization on the Cisco CMTS, use the show hccp <int x> <int y> modem and show hccp event-history commands in privileged EXEC mode.
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml
PacketCable Emergency 911 Services Listing and History
Cisco IOS release 12.3(13a)BC introduces enhanced informational support for PacketCable Emergency 911 calls on the Cisco CMTS, to include the following information and related history:
•
•
•
•
This feature is enabled and supported with the following new Cisco IOS command-line interface (CLI) configuration and show commands:
•
•
•
•
•
To set the call window (in minutes) during which the Cisco CMTS maintains records of Emergency 911 calls, use the cable high-priority-call-window command in global configuration mode. To remove the call window configuration from the Cisco CMTS, use the no form of this command:
cable high-priority-call-window <minutes>
no cable high-priority-call-window
The following command example configures the call window on the Cisco uBR10012 router to be 1 minute in length:
Router(config)# cable high-priority-call-window 1To observe Emergency 911 calls made within the configured window, use the show cable calls command in privileged EXEC mode:
show cable calls
The following command example illustrates that one Emergency 911 call was made on the Cable8/1/1 interface on the Cisco uBR10012 router during the window set for high priority calls:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 1 1 0 0Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 1 1 0 0The following command example illustrates the change on the Cisco uBR10012 router when this Emergency 911 calls ends:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 0 0 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 0 0 1The following command example illustrates available information when making a voice call from the same MTA to another MTA on the same interface:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 2 1 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 2 1 1The following command example illustrates available information when a voice call from the same MTA to another MTA on the same interface ends:
Router# show cable callsInterface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMsCable5/0/0 0 0 0 0Cable5/0/1 0 0 0 0Cable5/1/0 0 0 0 0Cable5/1/1 0 0 0 0Cable5/1/2 0 0 0 0Cable5/1/3 0 0 0 0Cable5/1/4 0 0 0 0Cable6/0/0 0 0 0 0Cable6/0/1 0 0 0 0Cable7/0/0 0 0 0 0Cable7/0/1 0 0 0 0Cable8/1/0 0 0 0 0Cable8/1/1 0 0 0 1Cable8/1/2 0 0 0 0Cable8/1/3 0 0 0 0Cable8/1/4 0 0 0 0Total 0 0 0 1The following example illustrates the show cable modem calls command on the Cisco uBR10012 router over a period of time, with changing call status information:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:39The following example illustrates that call information disappears when a call ends:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)The following example illustrates a new Emergency 911 call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 HV 1:30The following example illustrates a the end of the Emergency 911 call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:3The following example illustrates a non-emergency voice call on the Cisco CMTS from the same MTA:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.ca36.f97d 10.10.155.25 C8/1/1/U0 5 V -0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 RV 0:30The following example illustrates a the end of the non-emergency voice call on the Cisco CMTS:
Router# show cable modem callsCable Modem Call Status Flags:H: Active high priority callsR: Recent high priority callsV: Active voice calls (including high priority)MAC Address IP Address I/F Prim CMCallStatus LatestHiPriCallSid (min:sec)0000.cab7.7b04 10.10.155.38 C8/1/1/U0 18 R 0:36For additional informationabout PacketCable Emergency 911 calls on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml
PacketCable Multimedia for the Cisco CMTS
Cisco IOS Release 12.3(13a)BC introduces support for PacketCable Multimedia (PCMM) on the Cisco uBR10012 universal broadband router, and fully supports the CableLabs PacketCable Multimedia Specification, PKT-SP-MM-I02-040930.
http://www.cablelabs.com/packetcable/specifications/multimedia.html
As described by CableLabs, some key features of the PCMM service delivery framework include the following:
•
•
•
More specifically, Cisco IOS Release 12.3(13a)BC expands or changes several PacketCable functions in earlier Cisco IOS releases, including the following:
•
–
–
–
–
–
–
–
–
–
–
•
•
–
PCMM differs in that each gate is now unidirectional, and is associated with only one service flow. As a result, the gate info element structure in PCMM differs significantly from that of PacketCable. PCMM only needs to maintain one set of service flow information, rather than maintaining both upstream and downstream information as does PacketCable.
–
–
–
–
•
For additional information about PacketCable and PacketCable Multimedia on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml
"PacketCable is a CableLabs®-led initiative that is aimed at developing interoperable interface specifications for delivering advanced, real-time multimedia services over two-way cable plant. Built on top of the industry's highly successful cable modem infrastructure, PacketCable networks use Internet protocol (IP) technology to enable a wide range of multimedia services, such as IP telephony, multimedia conferencing, interactive gaming, and general multimedia applications." (PacketCable.com)
CableLabs® describes key features of the PacketCable Multimedia IP service delivery framework as follows:
•
•
•
PacketCable™ is a registered trademark of CableLabs®. Additional information and specifications are available online at the following CableLabs websites:
•
http://www.cablelabs.com/packetcable/
•
http://www.cablelabs.com/packetcable/specifications/multimedia.html
Service Independent Intercept (SII) Support
Cisco CMTS supports the Communications Assistance for Law Enforcement Act (CALEA) for voice and data. Cisco IOS Release 12.3(13a)BC introduces support for Service Independent Intercept (SII) on the Cisco uBR10012 CMTS. Cisco SII provides a more robust level of the lawful intercept (LI) options offered in the Packet Intercept feature. Cisco SII is the next level of support for judicially authorized electronic intercept, to include dial access, mobile wireless, tunneled traffic, and Resilient Transport Protocol (RTP) for voice and data traffic on the Cisco CMTS. SII on the Cisco CMTS includes these functions:
•
•
•
Note
Note
Cisco IOS Release 12.3(13a)BC enables full Multiple Service Operator (MSO) compliance with SII and LI regulations. Service providers worldwide are legally required to allow government agencies to conduct surveillance on the service provider's traditional telephony equipment. The objective of the SII feature is to enable service providers with New World networks that legally allow government agencies to conduct electronic network surveillance.
Lawful Intercept (LI) describes the process and judicial authority by which law enforcement agencies conduct electronic surveillance of circuit and packet-mode communications. LI is authorized by judicial or administrative order and implemented for either voice or data traffic on the Cisco CMTS. Table 6 lists the differences between packet intercept and SII features as implemented on the Cisco uBR10012.
Additional Information
For additional information, refer to the following documents:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml
Transparent LAN Service and Layer 2 Virtual Private Networks
Cisco IOS Release 12.3(13a)BC introduces the following changes or requirements for the TLS feature with Layer 2 VPNs:
•
•
Refer to the following documents on Cisco.com for additional TLS information:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/tls-cmts.html
•
Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE
Cisco IOS Release 12.3(13a)BC introduces support for virtual interface bundling on the Cisco uBR10012 universal broadband router and the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE), and the Cisco uBR7246VXR router.
In prior Cisco IOS releases, cable interface bundling was limited to physical interfaces as master or slave interfaces, and show commands did not supply bundle information.
Virtual interface bundling removes the prior concepts of master and slave interfaces, and introduces these additional changes:
•
•
•
Virtual interface bundling prevents loss of connectivity on physical interfaces should there be a failure, problematic online insertion and removal (OIR) of one line card in the bundle, or erroneous removal of configuration on the master interface.
Virtual interface bundling supports and governs the following Layer 3 settings for the bundle member interfaces:
•
•
•
•
•
•
•
For additional configuration information, examples, and guidelines for virtual interface bundling, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html
•
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml
•
New Hardware Features in Cisco IOS Release 12.3(9a)BC9
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC9.
New Software Features in Cisco IOS Release 12.3(9a)BC9
There are no new software features supported in Cisco IOS Release 12.3(9a)BC9.
New Hardware Features in Cisco IOS Release 12.3(9a)BC8
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC8.
New Software Features in Cisco IOS Release 12.3(9a)BC8
There are no new software features supported in Cisco IOS Release 12.3(9a)BC8.
New Hardware Features in Cisco IOS Release 12.3(9a)BC7
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC7.
New Software Features in Cisco IOS Release 12.3(9a)BC7
There are no new software features supported in Cisco IOS Release 12.3(9a)BC7.
New Hardware Features in Cisco IOS Release 12.3(9a)BC6
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC6.
New Software Features in Cisco IOS Release 12.3(9a)BC6
There are no new software features supported in Cisco IOS Release 12.3(9a)BC6.
New Hardware Features in Cisco IOS Release 12.3(9a)BC5
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC5.
New Software Features in Cisco IOS Release 12.3(9a)BC5
There are no new software features supported in Cisco IOS Release 12.3(9a)BC5.
New Hardware Features in Cisco IOS Release 12.3(9a)BC4
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC4.
New Software Features in Cisco IOS Release 12.3(9a)BC4
There are no new software features supported in Cisco IOS Release 12.3(9a)BC4.
New Hardware Features in Cisco IOS Release 12.3(9a)BC3
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC3.
New Software Features in Cisco IOS Release 12.3(9a)BC3
There are no new software features supported in Cisco IOS Release 12.3(9a)BC3.
New Hardware Features in Cisco IOS Release 12.3(9a)BC2
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC2.
New Software Features in Cisco IOS Release 12.3(9a)BC2
There are no new software features supported in Cisco IOS Release 12.3(9a)BC2.
New Hardware Features in Cisco IOS Release 12.3(9a)BC1
There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC1.
New Software Features in Cisco IOS Release 12.3(9a)BC1
There are no new software features supported in Cisco IOS Release 12.3(9a)BC1.
New Hardware Features in Cisco IOS Release 12.3(9a)BC
The following hardware features are new in Cisco IOS Release 12.3(9a)BC:
Cisco uBR10-MC5X20S/U Broadband Processing Engine
Commencing with Cisco IOS Release 12.3(9a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:
•
•
Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
The Cisco uBR10012 OC-48 DPT/POS interface module supports both PRE1 and PRE2 performance routing engine modules in the Cisco uBR10012 router chassis. The Cisco OC-48 DPT/POS interface module is a dual-mode module, providing interface support for Packet over SONET (POS) or Spatial Reuse Protocol (SRP).
Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 OC-48 DPT/POS interface module with these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:
•
•
•
For additional information about installing and configuring the Cisco uBR10012 OC-48 DPT/POS interface module, refer to these documents on Cisco.com:
•
•
Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules
Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 performance routing engine 2 (PRE2) route processing modules.
The Cisco uBR10012, which is qualified for PacketCable 1.0, Data over Cable Service Interface Specifications (DOCSIS) 1.1 and EuroDOCSIS 1.1, is built to meet the current and future needs of multiple system operators (MSOs). With full Layer 3 routing capabilities and industry-leading capacity and scalability, the Cisco uBR10012 delivers the highest level of performance for mass deployment of next-generation IP services.
The Cisco uBR10012 is designed to meet the services, performance, and reliability required for large-scale multiservice applications. The Cisco uBR10012 allows cable providers to deliver value-added IP services with consistent high performance. Based on Cisco IOS® Software—the standard in routing technology—the Cisco uBR10012 offers the most advanced networking and routing options available.
The Cisco uBR10012 features these components:
•
•
•
•
•
Benefits of the Cisco uBR10012 PRE2 include the following:
•
•
•
•
•
Table 7 provides additional details about the features and benefits of the Cisco uBR10012 PRE2.
Upgrading from Cisco uBR10012 PRE or PRE1 Modules to Cisco uBR10012 PRE2 Modules
For information about insertion, removal and upgrade of Field Replaceable Units such as the PRE2 modules, refer to the following document on Cisco.com:
•
DOCSIS System Interoperability on the Cisco uBR10012 CMTS
This section describes the operation of primary interoperability features in the Cisco uBR10012 router. For additional DOCSIS information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
DOCSIS 1.0 Baseline Privacy
DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and cable modem. BPI ensures that a cable modem, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for services only it is authorized to access.
To enable BPI, choose software at both the CMTS and cable modem that support this mode of operation. Select a Cisco IOS image that supports BPI. BPI must be enabled using the DOCSIS configuration file.
The cable modem must also support BPI. Cable modems must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment.
Note
Cable Modem Interoperability
•
•
DOCSIS 1.0 and 1.0+ Extensions
Earlier releases of Cisco IOS software for the uBR10012 router provide support for the original DOCSIS 1.0 standard, featuring basic best-effort data traffic and Internet access over the coaxial cable network. The DOCSIS 1.0+ extensions provides Quality of Service (QoS) enhancements for real-time traffic, such as voice calls, in anticipation of full DOCSIS 1.1 support.
Note
DOCSIS 1.1 Extensions
The DOCSIS 1.1 specification provides the following functional enhancements over DOCSIS 1.0 coaxial cable networks:
•
–
–
–
–
–
•
–
–
–
–
–
•
•
•
•
•
DOCSIS 1.1 Quality of Service
The DOCSIS 1.1 QoS framework is based on the following objects:
•
•
•
•
In DOCSIS 1.1, the basic unit of QoS is the service flow, which is a unidirectional sequence of packets transported across the RF interface between the cable modem and CMTS. A service flow is characterized by a set of QoS parameters such as latency, jitter, and throughput assurances.
Every cable modem establishes a primary service flow in both the upstream and downstream directions. The primary flows maintain connectivity between the cable modem and CMTS at all times.
In addition, a DOCSIS 1.1 cable modem can establish multiple secondary service flows. The secondary service flows can either be permanently created (they persist until the cable modem is reset or powered off) or they can be created dynamically to meet the needs of the on demand traffic being transmitted.
Each service flow has a set of QoS attributes associated with it. These QoS attributes define a particular class of service and determine characteristics such as the maximum bandwidth for the service flow and the priority of its traffic. The class of service attributes can be inherited from a preconfigured CMTS local service class (class-based flows), or they can be individually specified at the time of the creation of the service flow.
Each service flow has multiple packet classifiers associated with it, which determine the type of application traffic allowed to be sent on that service flow. Each service flow can also have a Payload header suppression (PHS) rule associated with it to determine which portion of the packet header will be suppressed when packets are transmitted on the flow.
New Software Features for Cisco IOS Release 12.3(9a)BC
This section describes the following new software features and CLI command changes for Cisco IOS Release 12.3(9a)BC and the Cisco uBR10012 router:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cable ARP Filter Enhancement
The cable arp filter command, introduced with Cisco IOS Release 12.2(15)BC2b, enables service providers to filter ARP request and reply packets. This prevents a large volume of such packets from interfering with the other traffic on the cable network.
Cisco IOS Release 12.3(9a)BC introduces enhanced command option syntax for the cable arp filter command, where number and window-size values are optional for reply-accept and request-send settings.
To control the number of Address Resolution Protocol (ARP) packets that are allowable for each Service ID (SID) on a cable interface, use the cable arp command in cable interface configuration mode. To stop the filtering of ARP broadcasts for CMs, use the no form of this command.
cable arp filter {reply-accept number window-size | request-send number window-size}
no cable arp filter {reply-accept | request-send}
default cable arp filter {reply-accept | request-send}
Syntax Description
Cisco IOS Release 12.3(9a)BC also removes a prior caveat with HCCP Protect interfaces. Previously, in the event of a revert-back HCCP N+1 switchover, manual removal of cable arp filter reply and cable arp filter request configurations may have been required afterward on Protect interfaces.
For more information about ARP Filtering, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/cblarpfl.html
Cisco Broadband Troubleshooter 3.2
Cisco IOS Release 12.3(9a)BC introduces support for the Cisco Broadband Troubleshooter (CBT) Version 3.2 on the Cisco uBR10012 universal broadband router, with newly supported interoperability for the following additional software features:
•
•
Multiple Service Operators (MSO) provide a variety of services such as TV, video on demand, data, and voice telephony to subscribers. Network Administrators and radio frequency (RF) technicians need specialized tools to resolve RF problems in the MSO's cable plant. Cisco Broadband Troubleshooter 3.2 (CBT 3.2) is a simple, easy-to-use tool designed to accurately recognize and resolve such issues.
The user can select up to three different cable modems (CMs) under the same CMTS or three different upstreams under the same CMTS. In addition, CBT 3.2 introduces the ability to display upstreams and cable modems combined (mixed) on the same trace window for monitoring and for playback.
Note
For additional information about CBT 3.2, spectrum management and STM 1.1, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html
Cisco CMTS Static CPE Override
The cable submgmt static-cpe-override command enables Multiple Service Operators (MSOs) to override network DHCP settings on CPE devices when performing troubleshooting with a laptop computer and console connection to the Cisco universal broadband router.
For additional information about using the cable submgmt static-cpe-override command, refer to these documents on Cisco.com:
•
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/stat_cpe.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements
Cisco IOS Release 12.3(9a)BC introduces or enhances the following CLI commands for the Cisco uBR10012 router:
•
For additional information about these command changes, refer to these resources:
•
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
DOCSIS Set-Top Gateway Issue 1.0
Cisco IOS Release 12.3(9a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.0 on the Cisco uBR10012 universal broadband router. The DOCSIS Set-Top Gateway (DSG) feature allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing DOCSIS networks. This allows MSOs and other service providers to combine both DOCSIS and STB operations over one, open, vendor-independent network, without any change to the existing network or cable modems.
DSG is a CableLabs® specification that allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing Data-over-Cable Service Interface Specifications (DOCSIS) cable networks. DSG 1.0 allows cable Multi-System Operators (MSOs) and other service providers to combine both DOCSIS and STB operations over a single, open and vendor-independent network without requiring any changes to the existing DOCSIS network infrastructure.
At the time of this Cisco publication, the CableLabs® DOCSIS DSG specification is in the current status of "Issued" as characterized by stability, rigorous review in industry and cross-vendor interoperability.
For additional information about configuring and using DSG 1.0 on the Cisco uBR10012 router, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdsg12.html
Dynamic Shared Secret (DMIC) with OUI Exclusion
Cisco IOS Release 12.3(9a)BC introduces the option of excluding the Organizational Unique Identifiers (OUIs) from being subjected to the DMIC check. The new cable dynamic-secret exclude command allow specific cable modems to be excluded from the Dynamic Shared Secret feature on the following Cisco CMTS platforms:
•
•
The Dynamic Shared Secret feature automatically creates a unique DOCSIS shared secret on a per-modem basis, creating a one-time use DOCSIS configuration file that is valid only for the current session. This ensures that a DOCSIS configuration file that has been downloaded for one cable modem can never be used by any other modem, nor can the same modem reuse this configuration file at a later time.
This patent-pending feature is designed to guarantee that all registered modems are using only the quality of service (QoS) parameters that have been specified by the DOCSIS provisioning system for that particular modem at the time of its registration.
For additional command information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdmic.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
EtherChannel Support on the Cisco uBR10012 Universal Broadband Router
Cisco IOS Release 12.3(9a)BC introduces support for Gigabit EtherChannel (GEC) on the Cisco uBR10012 universal broadband router with the PRE2 performance routing engine modules. Cisco IOS Release 12.3(9) supports Gigabit Ethernet interfaces for IEEE 802.1Q inter-VLAN trunking with increased bandwidth on the Cisco uBR10012 router.
Note
Note
EtherChannel provides Gigabit Ethernet (GE) speeds by grouping multiple GE-speed ports into a logical port channel that supports speeds up to 8 Gbps. This provides fault-tolerant, high-speed links between switches, routers and servers.
Trunking is configured between the switch and the router to provide inter-VLAN communication over the network. Trunking carries traffic from several VLANs over a point-to-point link between the two network devices. In a campus network, trunking is configured over an EtherChannel link to carry the multiple VLAN information over a high-bandwidth channel.
For additional information about configuring EtherChannel on the Cisco uBR10012 router, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_ethr.html
MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC
Cisco IOS Release 12.3(9a)BC adds the following new MIB support for the Cisco uBR10012 router.
For additional information about MIBs for the Cisco CMTS, refer to the following resources on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
•
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en
CISCO-CABLE-METERING-MIB
The CISCO-CABLE-METERING-MIB contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, also known as Usage-Based Billing on the Cisco CMTS. This format is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.
The MODULE-IDENTITY for the CISCO-CABLE-METERING-MIB is ciscoCableMeteringMIB, and its top-level OID is 1.3.6.1.4.1.9.9.424 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableMeteringMIB).
Note
Additional Information
For additional SAMIS information, refer to the following resources:
•
•
CISCO-CABLE-QOS-MONITOR MIB
Cisco IOS Release 12.3(9a)BC introduces additional features for the CISCO-CABLE-QOS-MONITOR MIB, including the following:
•
•
•
•
Note
CISCO-CABLE-SPECTRUM-MIB
Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router, with these additional MIB object enhancements:
•
•
downstream,upstreamandMacas indices to replace the ccsFlapTable object.•
•
•
•
•
The following objects are also now deprecated:
•
•
•
•
•
The maximum number of entries in the flap-list was changed from a maximum of 8191 for the entire router, to the following:
•
•
Two objects are now used to track the flap list size:
•
•
Note
CISCO-ENHANCED-MEMPOOL-MIB
Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router. The CISCO-ENHANCED-MEMPOOL-MIB enables you to monitor CPU and memory utilization for "intelligent" line cards and broadband processing engines on the Cisco uBR10012 router. These include the Cisco MC16X and MC28X series line cards.
Note
CISCO-PROCESS-MIB
Cisco IOS Release 12.3(9) introduces support for the CISCO-PROCESS-MIB on the Cisco uBR10012 universal broadband router with PRE2 modules.The CISCO-PROCESS-MIB enables you to monitor CPU and memory utilization for RF cards, cable interface line cards and broadband processing engines on the Cisco uBR10012 router.
Note
DOCS-QOS-MIB
Cisco IOS Release 12.3(9) introduces additional MIB object enhancements for the DOCS-QOS-MIB on the Cisco uBR10012 universal broadband router:
•
•
Note
DSG-IF-MIB
The DSG-IF-MIB defines objects that are used to configure, control, and monitor the operation of the DOCSIS Set-top Gateway (DSG) 1.0 feature on Cisco uBR7200 series and Cisco uBR10012 routers.
Note
Note
NetFlow Accounting Versions 5 and 8 Support
Cisco IOS Release 12.3(9a)BC introduces support for NetFlow Accounting Versions 5 and 8 on the Cisco uBR10012 router.
Note
NetFlow enables you to collect traffic flow statistics on your routing devices. NetFlow provides network administrators with access to "call detail recording" information from their data networks. Exported NetFlow data can be used for a variety of purposes, including network management and planning, enterprise accounting and departmental chargebacks, ISP billing, data warehousing and data mining for marketing purposes.
NetFlow is based on identifying packet flows for ingress IP packets. It does not require any connection-setup protocol either between routers or to any other networking device or end station and does not require any change externally—either to the traffic or packets themselves or to any other networking device.
NetFlow is completely transparent to the existing network, including end stations and application software and network devices like LAN switches. Also, NetFlow is performed independently on each internetworking device, it need not be operational on each router in the network. Using NetFlow Data Export (NDE), you can export data to a remote workstation for data collection and further processing. Network planners can selectively invoke NDE on a router or on a per-subinterface basis to gain traffic performance, control, or accounting benefits in specific network locations.
NetFlow Version 5 Features and Format
NetFlow exports flow information in UDP datagrams in one of two formats. The version 1 format was the initially released version, and version 5 is a later enhancement to add Border Gateway Protocol (BGP) autonomous system (AS) information and flow sequence numbers.
In NetFlow Version 1 and Version 5 formats, the datagram consists of a header and one or more flow records. The first field of the header contain the version number of the export datagram. Typically, a receiving application that accepts either format allocates a buffer big enough for the biggest possible datagram from either format and uses the version from the header to determine how to interpret the datagram. The second field in the header is the number of records in the datagram and should be used to index through the records.
All fields in either version 1 or version 5 formats are in network byte order. Table 5 and Table 6 describe the data format for version 1, and Table 7 and Table 8 describe the data format for version 5.
We recommend that receiving applications check datagrams to ensure that the datagrams are from a valid NetFlow source. We recommend you first check the size of the datagram to make sure it is at least long enough to contain the version and count fields. Next we recommend you verify that the version is valid (1 or 5) and that the number of received bytes is enough for the header and count flow records (using the appropriate version).
Because NetFlow export uses UDP to send export datagrams, it is possible for datagrams to be lost. To determine whether or not flow export information is lost, the version 5 header format contains a flow sequence number. The sequence number is equal to the sequence number of the previous plus the number of flows in the previous datagram. After receiving a new datagram, the receiving application can subtract the expected sequence number from the sequence number in the header to get the number of missed flows.
Table 8 lists the byte definitions for NetFlow Version 5 header format.
Table 8 NetFlow Version 5 Header Format
0-3
version and count
NetFlow export format version number and number of flows exported in this packet (1-30).1
4-7
SysUptime
Current time in milliseconds since router booted
8-11
unix_secs
Current seconds since 0000 UTC 1970.
12-15
unix_nsecs
Residual nanoseconds since 0000 UTC 1970.
16-19
flow_sequence
Sequence counter of total flows seen.
20-23
reserved
Unused (zero) bytes.
1 NetFlow Version 5 export packets (set with ip flow-export command) allow the number of records stored in the datagram to be a variable between 1 and 30.
Table 9 lists the byte definitions for Version 5 flow record format.
NetFlow Version 8 Features and Format
NetFlow exports flow information in UDP datagrams in one of several formats. Version 8, a new data export version, has been added to support data exports from aggregation caches. Version 8 allows for export datagrams to contain a subset of the usual version 5 export data, which is valid for a particular aggregations scheme type.
Figure 1 illustrates the NetFlow Version 8 header format.
Figure 1 Version 8 Header Format
Table 10 lists definitions for terms used in the version 8 header.
Additional Information about NetFlow on the Cisco CMTS
For additional information about configuring NetFlow Accounting on Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/net_mgmt/netflow_collection_engine/5.0/user/guide/overview.html
•
•
•
•
http://www.cisco.com/en/US/products/ps6601/prod_white_papers_list.html
•
http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html
PacketCable 1.0 With CALEA
Cisco IOS Release 12.3(9a)BC introduces DOCSIS 1.1 support for PacketCable 1.0 with Communications Assistance for Law Enforcement Act (CALEA) on the Cisco uBR10012 universal broadband router with the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE).
PacketCable is a program initiative from Cablelabs and its associated vendors to establish a standard way of providing packet-based, real-time video and other multimedia traffic over hybrid fiber-coaxial (HFC) cable networks. The PacketCable specification is built upon the Data-over-Cable System Interface Specifications (DOCSIS) 1.1, but it extends the DOCSIS protocol with several other protocols for use over non-cable networks, such as the Internet and the public switched telephone network (PSTN).
This allows PacketCable to be an end-to-end solution for traffic that originates or terminates on a cable network, simplifying the task of providing multimedia services over an infrastructure composed of disparate networks and media types. It also provides an integrated approach to end-to-end call signaling, provisioning, quality of service (QoS), security, billing, and network management.
Cisco IOS Release 12.2(11)BC1 and later releases in the Cisco IOS 12.3 release train support the PacketCable 1.0 specifications and the CALEA intercept capabilities of the PacketCable 1.1 specifications.
For additional information about configuring PacketCable on the Cisco CMTS, refer to the following document on Cisco.com:
•
SFID Support for Multicast and Cable Interface Bundling
Cisco IOS Release 12.3(9a)BC removes the prior restriction in Caveat CSCea45592 that prevented the creation of DOCSIS 1.1 upstream packet classifiers and service flow IDs (SFIDs) when configuring multicast groups with bundled cable interfaces. Cable interface bundling now supports SFIDs on Multicast groups.
Note
Note
For additional configuration information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html
CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE
Cisco IOS Release 12.3(9a)BC introduces support for remote spectrum management for the Cisco uBR10012 router. Cisco uBR10012 spectrum management supports interoperability with these enhancements to the Cisco CMTS in Cisco IOS 12.3(9a)BC:
•
•
Additional supported spectrum management functions are available on the Cisco uBR10012 router. For a complete list, and the latest information about Spectrum Management on the Cisco uBR10012 router, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html
•
Subscriber Traffic Management (STM) Version 1.1
Cisco IOS Release 12.3(9a)BC introduces support for Subscriber Traffic Management (STM) through Version 1.1 on the Cisco uBR10012 universal broadband router. STM 1.1 supports DOCSIS 1.1-compliant cable modems.
The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM is a simple bandwidth management tool which works as a low CPU alternative to Network-Based Application Recognition (NBAR) and access control lists (ACLs), however, using STM does not mean that NBAR and ACLs have to be turned off; STM can be applied along with NBAR and ACLs. STM 1.1 also works in conjunction with the Cisco Broadband Troubleshooter 3.2 to support additional network management and troubleshooting functions in the Cisco CMTS.
STM 1.1 extends earlier STM functions to monitor a subscriber's traffic on DOCSIS 1.1 primary service flows and supports these additional features:
•
•
•
•
For additional information about STM 1.1 and Cisco CBT 3.2, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html
•
http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html
Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q
Cisco IOS 12.3(9a)BC introduces support for the Transparent LAN Service over Cable feature on the Cisco 10012 router. This feature enhances existing Wide Area Network (WAN) support to provide more flexible Managed Access for multiple Internet service provider (ISP) support over a hybrid fiber-coaxial (HFC) cable network.
This feature allows service providers to create a Layer 2 tunnel by mapping an upstream service identifier (SID) to an IEEE 802.1Q Virtual Local Area Network (VLAN).
For additional information about configuring TLS on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/tls-cmts.html
Note
Usage Based Billing (SAMIS)
Cisco IOS Release 12.3(9a)BC introduces the Usage-Based Billing feature on the Cisco uBR10012 router. This feature provides subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. SAMIS is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.
The CISCO-CABLE-METERING-MIB is also introduced with Cisco IOS Release 12.3(9a)BC in support of SAMIS.
For additional information about configuring and monitoring Usage-Based Billing (SAMIS) on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html
Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE
Virtual interfaces (VI) and frequency stacking (FS) are two features that allow user-configurable MAC domains and multiple frequencies on one physical connector.
•
Cisco IOS Release 12.3(9a)BC introduces Virtual Interface Support for HCCP N+1 Redundancy with the Cisco uBR10-MC5X20S/U BPE.
•
Cisco IOS Release 12.3(9a)BC introduces support for frequency stacking on the Cisco uBR10012 router.
For additional information about configuring virtual interfaces and frequency stacking, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml
•
Virtual Interface Support for HCCP N+1 Redundancy
Cisco IOS Release 12.3(9a)BC introduces support for HCCP N+1 Redundancy for virtual interfaces configured on the Cisco uBR10012 universal broadband router using the Cisco uBR10-MC5X20S/U BPE.
HCCP N+1 Redundancy is an important step toward high availability on CMTS and telecommunications networks that use broadband media. HCCP N+1 Redundancy can help limit Customer Premises Equipment (CPE) downtime by enabling robust automatic switchover and recovery in the event that there is a localized disruption in service.
Beginning with Cisco IOS Release 12.2(15)BC2a, HCCP N+1 Redundancy adds synchronization between HCCP Working interface configurations and those inherited upon switchover to HCCP Protect interfaces. This makes the configuration of both easier and switchover times faster.
For additional information about configuring virtual interfaces in HCCP N+1 redundancy on the Cisco CMTS, refer to the following document on Cisco.com:
•
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html
MIBs
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://tools.cisco.com/ITDIT/MIBS/servlet/index
If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:
http://tools.cisco.com/RPF/register/register.do
MIB Changes and Enhancements for Cisco IOS Release 12.3(21)BC:
The DOC-QOS-MIB enhancement in Cisco IOS Release 12.3(21)BC added new tables to support SNMP QoS MIB query time in a large scale system with much less CPU consumption. The overall performance is better in multiple SNMP query sessions on the six tables than a single session. However, this solution has the following restrictions:
•
•
•
Note
MIB Constraints and Notes
This MIB is supported only in Cisco IOS Release 12.2(4)BC1 through Release 12.2(11)BC3 to support DOCSIS 1.1 operations. The MIB is deprecated in later releases to conform with the DOCSIS 2.0 specifications.
.
Note
http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html
MIB Changes and Enhancements for Cisco IOS Release 12.3(17a)BC:
MIB enhancements in Cisco IOS Release 12.3(17a)BC provide enhanced management features that enable the Cisco uBR 7200 Series router and the Cisco uBR 10012 router to be managed through the Simple Network Management Protocol (SNMP). These enhanced management features allow you to:
•
•
•
•
•
For a complete list of changes to the Cisco CMTS Universal Broadband Router MIB Specifications Guide, go to the Revision History table:
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html
Important Notes
The following sections contain important notes about Cisco IOS Release 12.3(23)BC7 that apply to the Cisco uBR10012 universal broadband router universal broadband router.
How to Upgrade to Cisco IOS Release 12.3(21)BC
In circumstances in which non-volatile memory (NVRAM) becomes corrupted on the Cisco CMTS, configurations and feature behavior may become corrupted or lost, looping behavior in NVRAM may result, and additional measures to resolve corrupted NVRAM and lost configurations would be required.
This issue can be generated by upgrading to later Cisco IOS releases from prior Cisco IOS releases that do not contain resolution to a specific and known issue. This issue is not limited to Cisco IOS releases installed on the Cisco universal broadband routers.
Symptoms of Corrupted NVRAM
This issue is displayed with the following symptoms in the case of the Cisco CMTS:
•
–
This error message is displayed either when the router boots, or when you enter one of the following commands:
•
•
•
•
Conditions of Corrupted NVRAM
This symptom is observed under the following conditions:
•
–
–
–
–
When upgrading to Cisco IOS Release 12.3(21)BC, the following upgrade procedure prevents corruption to NVRAM, retains configurations made in earlier releases, and successfully installs Cisco IOS Release 12.3(21)BC images. This procedure is subject to the feature restrictions and prerequisites of Cisco IOS Release 12.3(21)BC, described in these release notes.
Prerequisites
Cisco strongly recommends that you back up your configuration files prior to performing this upgrade, or any upgrade.
SUMMARY STEPS
Perform these steps to upgrade to Cisco IOS 12.3(21)BC, after TFTP file transfer operations are complete.
1.
2.
3.
4.
5.
6.
DETAILED STEPS
New Command Information for Cisco IOS Release 12.3(21)BC
Cisco IOS Release 12.3(21)BC introduces support and modifications to the following commands for Cisco Cable Modem Termination System (CMTS) universal broadband routers.
Refer to the following sections for more information:
•
•
cable throttle-ranging
To enable faster cable modem registration times, use the cable throttle-ranging command in global configuration mode. To disable faster cable modem registration times, use the no form of this command.
cable throttle-ranging
no cable throttle-ranging
Syntax Description
This command has no arguments or keywords
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
The cable throttle-ranging command enables faster cable modem registration times on the CMTS.
Reload the Cisco CMTS with a Cisco IOS Release 12.3(21)BC image and configure the cable throttle-ranging command on the CMTS. Once the cable throttle-ranging has been configured, save the new configuration and reload the Cisco CMTS again. Faster cable modem registration times will now be enabled on the Cisco CMTS.
Note
Examples
The following example shows how to enable Fast CM registration feature on a Cisco CMTS:
Router# cable throttle-rangingRouter(config)#
Related Commands
There are no related commands for this command.
card
To preprovision a slot in the Cisco uBR10012 universal broadband router for a particular interface card, so that you can configure the interface without it being physically present in the slot, use the card command in global configuration mode. To remove the preprovisioning for a card, so that the physical slot reports being empty, use the no form of this command.
card {slot/subslot | slot/subslot/bay} card-type
no card {slot/subslot | slot/subslot/bay}
Syntax Description
slot/subslot
Identifies the chassis slot and subslot for the card. The following are the valid values:
•
•
slot/subslot/bay
Identifies the chassis slot and subslot for the Cisco Wideband SIP, and the bay number in the SIP where the Cisco Wideband SPA is located. The following are the valid values:
•
•
•
card-type
Specifies the type of card that should be used to preprovision the slot. See Table 12 for a list of the supported cards.
Note
Defaults
An empty card slot is not preprovisioned and cannot be configured or displayed.
Command Modes
Global configuration
Command History
Usage Guidelines
This command preprovisions a slot in the Cisco uBR10012 router to accept a particular line card, so that you can configure the interface without the card being physically present in the chassis. This command allows system administrators to plan for future configurations, without having to wait for the physical hardware to first arrive. When the line card does arrive, the installer can bring the card online by inserting the card into the chassis and connecting the necessary cables, without having to do any further configuration using the command-line interface.
The type of card must be appropriate for the slot being specified. Slots 1/1 and 2/1 are reserved for TCC+ utility cards. Slots 1/0 through 4/0 are reserved for network uplink line cards. Slot 5/0 through 8/1 are reserved for cable interface line cards. Slot 0/0 is reserved for the FastEthernet interface on the PRE1 module and cannot be specified in this command.
Table 12 lists the types of cards that are supported as card-types for the card command:
Tip
When a line card is inserted in the Cisco uBR10012 chassis, the router performs the following actions, depending on whether the card slot is preprovisioned for the card:
•
•
•
Tip
The no card version of the command removes the preprovisioning information from the given card slot. This also removes all configuration information for that card slot, as well as any information in the SNMP MIB database about the card and its card slot.
Examples
The following example shows a list of supported card types for Cisco IOS Release 12.2(8)BC1, and then shows that slot 8/0 is being preprovisioned for a Cisco uBR-LCP2-MC28C cable interface line card. The cable interface for slot 8/0 can then be configured.
Router# config tRouter(config)# card 5/0 ?1cable-mc16c create a uBR10000 line card with MC16C1cable-mc16e create a uBR10000 line card with MC16E1gigethernet-1 create a GE_1_PORT cardtype1oc12pos-1 create a OC12POS_1_PORT cardtype2cable-mc28bnc create a uBR10000 line card with MC28C, BNC connector2cable-mc28c create a uBR10000 line card with MC28C2oc12srp-sm-lr create a uBR10000 oc12 SRP card with SM LRRouter(config)# card 8/0 2cable-mc28cRouter(config)# int c8/0Router(config-if)#The following example shows the output from the show interface command for a preprovisioned cable interface. The second line of the output shows that the hardware is not present.
Router# show interface c8/0/0Cable8/0/0 is initializing, line protocol is downHardware is not presentHardware is UBR10000 CLC, address is 0001.6440.d160 (bia 0001.6440.d160)MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation MCNS, loopback not setARP type: ARPA, ARP Timeout 04:00:00Last input never, output never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outRouter#The following examples show the two steps required to preprovision the Wideband SIP and Wideband SPA.
The Wideband SIP is preprovisioned with the card command and 2jacket-1 as the card type. For example:
Router# configure terminalRouter(config)# card 1/0 2jacket-1Router(config)#The Wideband SPA is preprovisioned with the card command and 24rfchannel-spa-1 as the card type. For example:
Router# configure terminalRouter(config)# card 1/0/0 24rfchannel-spa-1Router(config)#The preceding card command creates 12 wideband channels on the Wideband SPA.
Related Commands
show interface cable
Displays the current configuration and status of a cable interface.
clear cable modem reset
To remove one or more CMs from the Station Maintenance List and reset them, use the clear cable modem reset command in privileged EXEC mode.
clear cable modem {mac-addr | ip-addr | [cable slot/port] {all | oui string | reject} } reset
clear cable modem {mac-addr | ip-addr | [cable slot/subslot/port] {all | oui string | reject | wideband registered-traditional-docsis} } reset
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command instructs the Cisco CMTS to stop sending DOCSIS station maintenance messages to one or more CMs, which effectively terminates the link to those CMs. A CM responds to this by resetting itself. Depending on when the CM received the last station maintenance message, it can take up to 30 seconds before the CM detects the missing station maintenance messages and resets itself.
In some circumstances, the customer premises equipment (CPE) devices behind a CM stops receiving traffic after the CM is reset. This is because the CMTS still has the CPE device listed in its address tables, but the CM does not after being reset, so the traffic passes through the CMTS but is dropped by the CM. To resolve this situation, the CPE device should simply send some type of traffic to the CM, such as a ping packet. (You can also resolve this situation by using the clear arp-cache command on the Cisco CMTS router to clear the router's address table, but this is not recommended, because it temporarily interrupts all traffic on the router.)
Note
Caution
Tip
Examples
The following example shows how to reset the CM at 172.23.45.67:
Router# clear cable modem 172.23.45.67 resetRouter#The following example shows how to reset all CMs that have a OUI that has been defined as having the vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco resetRouter#The following example shows how to reset all CMs that are currently in one of the reject states:
Router# clear cable modem reject resetRouter#The following example shows how to reset all wideband CMs that are registered as traditional DOCSIS modems.:
Router# clear cable modem wideband registered-traditional-docsis resetMAC Address IP Address I/F MAC Prim BG DSID MD-DS-SGState Sid ID0018.6852.825c 80.18.0.9 C5/0/0/U0 online 1 0 256 N/A0018.6852.8286 80.18.0.10 C5/0/0/U0 online 2 0 264 N/A0016.92fb.55be 80.18.0.7 C5/0/0/U0 online 3 0 288 N/A0016.92f0.9104 80.18.0.5 C5/0/0/U0 online 4 0 280 N/A0016.92fb.55c0 80.18.0.6 C5/0/0/U0 online 5 0 272 N/ARouter#
Related Commands
hw-module reload
To reload the software in and restart a Cisco 1-Gbps Wideband SPA, use the hw-module reload command in privileged EXEC mode.
hw-module bay slot/subslot/bay reload
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
12.3(21)BC
This command was introduced for the Cisco uBR10012 universal broadband router.
Usage Guidelines
The hw-module reload command reloads the software in and restarts a Cisco 1-Gbps Wideband SPA.
Examples
The following example shows reloads the Cisco Wideband SPA in slot 1, subslot 0, bay 1.
Router# hw-module bay 1/0/1 reloadRouter#Related Commands
hw-module shutdown
To shut down a particular Performance Routing Engine (PRE1) module, line card, Wideband SIP or Wideband SPA, use the hw-module shutdown command in global configuration mode. To activate a specific PRE1, line card, Wideband SIP or Wideband SPA, use the no form of this command.
hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/subslot |
bay slot/subslot/bay} shutdown [unpowered]no hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/subslot |
bay slot/subslot/bay} shutdownSyntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.2(4)XF
This command was introduced for the Cisco uBR10012 router.
12.3(21)BC
Support was added for the Cisco Wideband SIP and Cisco 1-Gbps Wideband SPA.
Usage Guidelines
The hw-module shutdown command shuts down a particular Performance Routing Engine (PRE1) module, line card, Wideband SIP or Wideband SPA. To activate a specific PRE1, line card, Wideband SIP, or Wideband SPA, use the no form of this command.
Caution
Examples
The following example shows the standby PRE1 module being shut down:
Router(config)# hw-module sec-cpu shutdownRouter(config)#The following example shows the active PRE1 module being shut down (which will trigger a switchover to the standby PRE1 module):
Router(config)# hw-module main-cpu shutdownRouter(config)#The following example shows the PRE1 module in PRE1 slot B being shut down:
Router(config)# hw-module pre B shutdownRouter(config)#
Note
The following example shows how to deactivate and verify deactivation for the Cisco Wideband SPA located in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the "admin down" in the Operational Status field.
Router# configure terminalRouter(config)# hw-module bay 1/0/0 shutdown unpowered%SPAWBCMTS-4-SFP_MISSING: Wideband-Cable 1/0/0, 1000BASE-SX SFP missing from port 0%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:1, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:2, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:3, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:4, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:5, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:6, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:7, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:8, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:9, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:10, changed state to down%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:11, changed state to down...Router# show hw-module bay 1/0/0 oirModule Model Operational Status-------------- ------------------ -------------------------bay 1/0/0 SPA-24XDS-SFP admin downThe following example shows how to activate and verify activation for the Cisco Wideband SPA located in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the "ok" in the Operational Status field.
Router# configure terminalRouter(config)# no hw-module bay 1/0/0 shutdown%SPAWBCMTS-4-SFP_OK: Wideband-Cable 1/0/0, 1000BASE-SX SFP inserted in port 0%SPAWBCMTS-4-SFP_LINK_OK: Wideband-Cable 1/0/0, port 0 link changed state to up%SNMP-5-LINK_UP: LinkUp:Interface Wideband-Cable1/0/0:0 changed state to up%LINK-3-UPDOWN: Interface Cable1/0/0:0, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:1, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:2, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:3, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:4, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:5, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:6, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:7, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:8, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:9, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:10, changed state to up%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:11, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Wideband-Cable1/0/0:0, changed state to up...Router# show hw-module bay 1/0/0 oirModule Model Operational Status-------------- ------------------ -------------------------bay 1/0/0 SPA-24XDS-SFP okRelated Commands
show cable modem summary
To display a summary of CMs on one or more cable interfaces, use the show cable modem command in privileged EXEC mode.
show cable modem summary [total]
show cable modem summary interface1 [interface2] total
show cable modem summary interface1 [interface2] upstream port1 port2 total
show cable modem cable slot/port [upstream port] summary
show cable modem cable slot/subslot/port [upstream port] summary
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays a summary of CMs for a single cable interface or upstream, or for a range of cable interfaces or upstreams. The following possible combinations are possible for this command:
•
•
•
•
•
Note
Examples
The following example shows typical output for the default form of the show cable modem summary command on a Cisco uBR7200 series router:
Router# show cable modem summaryInterface Total Active Registered DescriptionModems Modems ModemsCable3/0/U0 165 141 141 Line 32/1Cable3/0/U1 209 172 170 Line 32/2Cable3/0/U2 262 207 203 Line 32/3Cable3/0/U3 256 194 188 Line 32/4Cable5/0/U0 746 714 711 Line 41/1Cable6/0/U0 806 764 759 Line 42/2Router#
Note
The following example shows typical output for the show cable modem summary command with the total option on a Cisco uBR7200 series router:
Router# show cable modem summary totalInterface Total Active Registered DescriptionModems Modems ModemsCable5/0/U0 746 714 711 Node1Cable6/0/U1 806 764 759 Node3Total: 1552 1478 1470Router#The following example shows sample output for the show cable modem summary command with the total option for a Cisco uBR10012 router:
Router# show cable modem summary totalInterface Cable Modem DescriptionTotal Reg Unreg Offline Wideband initRC initD initIO initOC5/0/0/U0 84 84 0 0 84 0 0 0 0C5/0/0/U1 84 84 0 0 84 0 0 0 0C5/0/0/U2 83 83 0 0 83 0 0 0 0C5/0/0/U3 83 83 0 0 83 0 0 0 0<<output omitted>>Total: 8020 8020 0 0 8016 0 0 0 0Router#The following example shows sample output for the show cable modem summary total command for a range of interfaces on the Cisco uBR10012 router:
Router# show cable modem summary c5/1/1 c5/1/2 totalInterface Cable Modem DescriptionTotal Reg Unreg Offline Wideband initRC initD initIO initOC5/1/1/U0 84 84 0 0 84 0 0 0 0C5/1/1/U1 84 84 0 0 83 0 0 0 0C5/1/1/U2 83 83 0 0 83 0 0 0 0C5/1/1/U3 83 83 0 0 83 0 0 0 0C5/1/2/U0 84 84 0 0 84 0 0 0 0C5/1/2/U1 84 84 0 0 84 0 0 0 0C5/1/2/U2 83 83 0 0 83 0 0 0 0C5/1/2/U3 83 83 0 0 83 0 0 0 0Total: 668 668 0 0 667 0 0 0 0Router#The following example shows sample output for the show cable modem summary total command for a range of interfaces and upstreams on the Cisco uBR10012 router:
Router# show cable modem summary c5/1/1 c5/1/2 upstream 0 1 totalInterface Cable Modem DescriptionTotal Reg Unreg Offline Wideband initRC initD initIO initOC5/1/1/U0 84 84 0 0 84 0 0 0 0C5/1/1/U1 84 84 0 0 83 0 0 0 0C5/1/2/U0 84 84 0 0 84 0 0 0 0C5/1/2/U1 84 84 0 0 84 0 0 0 0Total: 336 336 0 0 335 0 0 0 0Router#
Note
Table 13 describes the fields shown in the show cable modem summary displays:
Note
Tip
Related Commands
show cable modem wideband
To display information for registered and unregistered wideband CMs, use the show cable modem wideband command in privileged EXEC mode.
show cable modem wideband [registered-traditional-docsis]
show cable modem [ip-address | mac-address | cable slot/subslot/port] wideband
Syntax Description
Command Modes
Privileged EXEC
Command History
12.3(21)BC
This command was introduced for the Cisco uBR10012 universal broadband router.
Usage Guidelines
This command displays information for a one or more wideband CMs. Optionally, the CMs for which to display information can be identified IP address, MAC address, or cable interface.
If a wideband-capable CM is not able to register as a wideband CM (for example, if no wideband channel is available), the CM attempts to register as a traditional DOCSIS modem. The registered-traditional-docsis keyword limits the set of wideband CMs for which to display information to wideband-capable CMs that are currently registered as DOCSIS 1.X or DOCSIS 2.0 modems.
Examples
The following example shows typical output for the default form of the show cable modem wideband command on a Cisco uBR10012 router:
Router# show cable modem widebandMAC Address IP Address I/F MAC Prim BG DSID MD-DS-SGState Sid ID0014.bfbe.3cc0 1.11.0.1 C5/0/1/U0 w-online(pt) 3 24 24 N/A0016.92f0.90d6 1.11.0.4 C5/0/1/U0 w-online(pt) 5 24 272 10014.bfbe.3cb8 1.11.0.2 C6/0/1/U0 w-online(pt) 3 36 36 N/A0016.92f0.90d8 1.11.0.3 C6/0/1/U0 w-online(pt) 5 36 274 1Router#Table 14 describes the fields that are shown in the show cable modem wideband display:
Table 15 shows the possible values for the MAC State field for a wideband CM modem that registers as a traditional DOCSIS modem:
Table 15 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1
init(r1)
The CM sent initial ranging.
init(r2)
The CM is ranging. The CMTS received initial ranging from the CM and has sent RF power, timing offset, and frequency adjustments to the CM.
init(rc)
Ranging has completed.
Note
init(d)
The DHCP request was received, as DHCPDISCOVER. This also indicates that the first IP broadcast packet has been received from the CM.
init(dr)
The DHCP request has been sent to the cable modem.
init(i)
The cable modem has received the DHCPOFFER reply (DHCPACK) from the DHCP server that has assigned an IP address to the modem, but the modem has not yet replied with a DHCPREQUEST message requesting that particular IP address, nor has it sent an IP packet with that IP address.
Note
init(io)
The Cisco CMTS has seen the DHCP offer as sent to the cable modem from the DHCP server that has assigned an IP address to the modem.
init(o)
The CM has begun to download the option file (DOCSIS configuration file) using the Trivial File Transfer Protocol (TFTP), as specified in the DHCP response. If the CM remains in this state, it indicates that the download has failed.
init(t)
Time-of-day (TOD) exchange has started.
resetting
The CM is being reset and will shortly restart the registration process.
cc(r1)
The CM had registered and was online, but has received a Downstream Channel Change (DCC) or Upstream Channel Change (UCC) request message from the CMTS. The CM has begun moving to the new channel, and the CMTS has received the CM's initial ranging on the new downstream or upstream channel. At the MAC layer, the CM is considered offline because it is not yet passing traffic on the new channel, but this state does not trigger the flap-list counters.
cc(r2)
This state should normally follow cc(r1) and indicates that the CM has finished its initial ranging on the new channel, and is currently performing continuous ranging on the new channel. At the MAC layer, the CM is considered offline because it is not yet passing traffic on the new channel, but this state does not trigger the flap-list counters.
offline
The CM is considered offline (disconnected or powered down).
online
The CM has registered and is enabled to pass data on the network.
online(d)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. The CM does not forward traffic to or from the CPE devices, but the CMTS can continue to communicate with the CM using DOCSIS messages and IP traffic (such as SNMP commands).
Note
online(pkd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and KEK is assigned.
Note
online(ptd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and TEK is assigned. BPI encryption is now being performed.
Note
online(pk)
The CM registered, BPI is enabled and KEK is assigned.
online(pt)
The CM registered, BPI is enabled and TEK is assigned. BPI encryption is now being performed.
Note
Note
expire(pk)
The CM registered, BPI is enabled, KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value.
expire(pkd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value.
Note
expire(pt)
The CM registered, BPI is enabled, TEK was assigned, but the current TEK expired before the CM could successfully renew a new KEK value.
expire(ptd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, TEK was assigned, but the current TEK expired before the CM could successfully renew a new KEK value.
Note
reject(m)
The CM attempted to register but registration was refused due to a bad Message Integrity Check (MIC) value. This also could indicate that the shared secret in the DOCSIS configuration file does not match the value configured on the CMTS with the cable shared-secret command.
In Cisco IOS Release 12.1(11b)EC1 and Cisco IOS Release 12.2(8)BC2 or later releases, this could also indicate that the cable tftp-enforce command has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before registering, but the CM did not do so.
reject(c)
The CM attempted to register, but registration was refused due to a a number of possible errors:
•
•
•
•
•
reject(pk)
KEK key assignment is rejected, BPI encryption has not been established.
reject(pkd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because KEK key assignment was rejected.
Note
reject(pt)
TEK key assignment is rejected, BPI encryption has not been established.
reject(ptd)
The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because TEK key assignment was rejected.
Note
reject(ts)
The CM attempted to register, but registration failed because the TFTP server timestamp in the CM registration request did not match the timestamp maintained by the CMTS. This might indicate that the CM attempted to register by replaying an old DOCSIS configuration file used during a prior registration attempt.
reject(ip)
The CM attempted to register, but registration failed because the IP address in the CM request did not match the IP address that the TFTP server recorded when it sent the DOCSIS configuration file to the CM. IP spoofing could be occurring.
reject(na)
The CM attempted to register, but registration failed because the CM did not send a Registration-Acknowledgement (REG-ACK) message in reply to the Registration-Response (REG-RSP) message sent by the CMTS. A Registration-NonAcknowledgement (REG-NACK) is assumed.
1 The CM MAC state field can also be retrieved using SNMP by getting the value of the cdxCmtsCmStatusValue object in the CISCO-DOCS-EXT-MIB.
Tip
Table 16 shows the possible values for the MAC state field for a wideband-capable CM that registers as a wideband modem:
Related Commands
show interface wideband-cable
To display the current configuration and status for a wideband channel, use the show interface wideband-cable command in privileged EXEC mode.
show interface wideband-cable slot/subslot/bay:wideband_channel [options]
Syntax Description
Note
Command Modes
Privileged EXEC
Command History
12.3(21)BC
This command was introduced on the uBR10012 universal broadband router.
Examples
The following is a sample output for the show interface wideband-cable command:Router# show interface wideband-cable 1/0/0:1Wideband-Cable1/0/0:1 is up, line protocol is upHardware is Wideband CMTS Cable interface, address is 0012.001a.8897 (bia 0012.001a.8897)MTU 1500 bytes, BW 74730 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation MCNS, loopback not setKeepalive set (10 sec)ARP type: ARPA, ARP Timeout 04:00:00Last input never, output 00:00:09, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort24224 packets output, 1222002 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outRouter#Table 17 describes the fields shown in the show interface wideband-cable display.
Tip
Related Commands
Restrictions for Cisco IOS Release 12.3(17a)BC
When upgrading the CiscouBR10012 Performance Routing Engine 1 (PRE1) modules to Cisco uBR10012 PRE2 modules, you must reconfigure the cable intercept feature when enabled on a slave interface. For additional information about the Cable Intercept feature, cable interface bundling, or virtual master interfaces in cable interface bundling, refer to the following documents on Cisco.com:
–
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html
–
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
–
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
New Command Information for Cisco IOS Release 12.3(13a)BC3
Cisco IOS Release 12.3(13a)BC3 introduces support for the debug cable classifier command, which displays debugging information supporting DOCSIS packet classifiers.
debug cable classifiers
To display debugging messages for DOCSIS packet classifiers, use the debug cable classifiers command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.
debug cable classifiers
no debug cable classifiers
Syntax Description
No additional keywords or syntax components are required.
Command Modes
Privileged EXEC mode
Defaults
DOCSIS packet classifier debugging is disabled by default.
Command History
12.3(13a)BC3
This command was introduced on the Cisco uBR10012 and Cisco uBR7246VXR universal broadband routers.
Usage Guidelines
The debug cable classifiers command provides detailed information about the allocation, removal, activation and deactivation of packet classifiers. Generally, classifiers are used to identify IP packets by source port, destination port, or type of service. Classifiers are associated with service flows. For example, packet classifiers are dynamically created in most Voice over IP (VoIP) deployments and this debug command can be used to troubleshoot issues related to these classifiers as VOIP calls are created and torn down.
Because this command can produce a large volume of debug information, use this command only when you have also enabled debugging for a particular MAC address, set of MAC addresses, or a MAC address mask, using the debug cable mac-address command.
For additional debug command information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Examples
The following example enables classifier debugging for a single MAC address:
Router# debug cable mac-address 000a.73fa.dbaaRouter# debug cable classifiersCMTS Packet Classifiers debugging is onThe following enables classifier debugging for all MAC addresses with Organizational Unique Identifier (OUI) OUI 0013.11:
Router# debug cable mac-addr 0013.1100.0000 ffff.ff00.0000Routerv# debug cable classifiersCMTS Packet Classifiers debugging is onThe following example illustrates sample output of the debug cable classifiers command for the given MAC addresses:
Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 1 adm 1 act 1Feb 7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 1 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 2 adm 2 act 2Feb 7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 2 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 3 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 1 dir 0 prov 3 adm 3 act 0Feb 7 18:43:50.181: CFR cmts_activate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 0 prov 3 adm 3 act 3Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 4 adm 0 act 0Feb 7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 1 dir 1 prov 4 adm 4 act 0Feb 7 18:43:50.181: CFR cmts_activate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 1 prov 4 adm 4 act 4Feb 7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 1 pri 0 ord 0 dir 0 st 2 phsi 0Feb 7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 2Feb 7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 0 dir 0 type 0 cfrid 0 pri 1 ord 0 dir 0 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 2 pri 0 ord 0 dir 1 st 2 phsi 0Feb 7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 0 dir 1 st 2Feb 7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 1 dir 1 st 1 phsi 0Feb 7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 0 dir 1 typRelated Commands
debug cable dynsrv
Displays information about DOCSIS 1.1 dynamic service flow messages.
debug cable qos
Activates quality-of-service (QoS) debugging.
New Command Information for Cisco IOS Release 12.3(13a)BC2
Cisco IOS Release 12.3(13a)BC2 introduces support for the cable service flow activity-timeout command, which enables the configuration of dynamic service flow timeout settings apart from a PacketCable environment.
cable service flow activity-timeout
To configure the activity timeout for dynamic cable service flows in DOCSIS 1.1 environments, where PacketCable is inactive, use the cable service flow activity-timeout command in global configuration mode. To remove the activity timer once configured, use the no form of this command.
cable service flow activity-timeout n
no cable service flow activity-timeout [<n>]
Syntax Description
n
The timeout length in seconds. Valid range is 0 - 65535 seconds. Setting this value to 0 configures the service flow to never timeout.
Defaults
The default timeout length for a DOCSIS 1.0+ cable service flow is 300 seconds (five minutes).
Command Modes
Global configuration
Command History
12.3(13a)BC
This command was introduced to support DOCSIS 1.1 service flow operation in non-Packet-Cable environments.
Usage Guidelines
Dynamic service flows in DOCSIS 1.0+ are created with a default activity timeout of 300 seconds. This enables the deletion of idle service flows after five minutes. This new command enables such functions within DOCSIS 1.1 environments with a wide range of timeout length options.
In DOCSIS 1.1, the default inactivity timeout is often set by the application that triggers the creation of dynamic service flows. PacketCable frequently performs this function when supported on the Cisco CMTS. However, this new command configures inactivity timeout where PacketCable is not active on the Cisco CMTS.
Note
Apart from PacketCable, this command enables the cable modem to control the setup of the dynamic service flows, and to remove inactive service flows. During the creation of service flows, all Upstream and Downstream flows in the request are checked to see if the configured activity timeout needs to be applied.
Examples
The following example in global configuration mode configures the cable modems connected to the Cisco CMTS to use activity timeout of zero, which means that related service flows do not timeout in a non-PacketCable environment:
Router(config)# cable service flow activity-timeout 0Related Commands
Restrictions for Cisco IOS Release 12.3(13a)BC
The following restrictions apply to Cisco IOS Release 12.3(13aq)BC:
•
•
–
–
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
–
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Restrictions for Cisco IOS Release 12.3(9a)BC
The following restrictions apply to Cisco IOS Release 12.3(9a)BC:
•
•
–
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
–
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
New and Changed Command Reference for Cisco IOS Release 12.3(9a)BC
Cisco IOS Release 12.3(9a)BC introduces or enhances the following Cisco IOS commands for the Cisco uBR10012 router:
cable logging layer2events
To save selected (low priority) DOCSIS events that are specified in CMTS MIB Registry to the cable logging buffer (instead of to the general logging buffer), use the cable logging layer2events command in global configuration mode. To disable the logging of DOCSIS events to the cable logging buffer, use the no form of this command.
cable logging layer2events
no cable logging layer2events
Syntax Description
This command has no additional arguments or keywords.
Defaults
DOCSIS events are saved to the general logging buffer on the Cisco CMTS by default.
Command Modes
Global configuration mode
Command History
12.3(9a)BC
This command was introduced on the Cisco uBR10012 and Cisco uBR7246VXR universal broadband routers.
Usage Guidelines
Use the show cable logging command to check whether the logging feature is enabled and the status of the logging buffer.
Examples
The following example shows how to clear the log buffer that contains a bad IP source address error messages:
Router# show cable logging summaryCable logging: BADIPSOURCE EnabledTotal buffer size (bytes): 1000000Used buffer size (bytes) : 36968Logged messages : 231Router# clear cable logging badipsourceRouter# show cable logging summaryCable logging: BADIPSOURCE EnabledTotal buffer size (bytes): 1000000Used buffer size (bytes) : 0Logged messages : 0Related Commands
For additional information about logging events on the Cisco CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
cable source-verify
To enable verification of IP addresses or service IDs (SIDs) for CMs and CPE devices on the upstream, use the cable source-verify command in global configuration, cable interface configuration or subinterface configuration modes. To disable verification, use the no form of this command.
Cable Interface and Subinterface Configuration Modes
cable source-verify [dhcp | leasetimer value | leasequery-filter upstream query-num interval]
no cable source-verify
Global Configuration Mode
cable source-verify leasequery-filter downstream query-num interval
no cable source-verify
Syntax Description
Defaults
Disabled. When the dhcp option is specified, the leasetimer option is set by default to 60 minutes.
Command Modes
Global configuration, Cable interface configuration or subinterface configuration
Note
Command History
For additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
cable submgmt default
To enable the Cisco CMTS Static CPE Override feature on the Cisco CMTS, use the cable submgmt default command in global configuration mode. This command enables field technicians to add a temporary CPE device behind the subscriber's cable modem. The temporary CPE device shares the same SID settings as the original CPE device, even though the temporary CPE device has a different MAC address. The original CPE device automatically changes from dhcp cpe to static cpe in the CMTS host routing tables, and the CPE device continues to receive service with the same SID. To disable Cisco CMTS Static CPE Override on the Cisco CMTS, use the no form of this command. This automatically updates the routing tables and enables the MAC address from the technician's laptop for a future field service connection at a different location.
cable submgmt default {active | filter-group {cm | cpe} | learnable | max-cpe}
no cable submgmt default
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Global configuration mode
Command History
12.3(9a)BC
This feature was introduced on Cisco uBR10012 and Cisco uBR7200 series universal broadband routers.
Usage Guidelines
Prior to using this command, the first (existing) DHCP CPE device maintains its DHCP dynamic MAC address behind the cable modem. The SID is assigned to this IP address.
However, by enabling Static CPE override, you gain the following states and options on two CPE devices behind the cable modem.
•
•
Note
Examples
The following example enables Cisco CMTS Static CPE Override in the field, enabling more or more additional CPE devices to be added behind a subscriber's cable modem:
Router(config)# cable submgmt default activeThe following example configures the Cisco CMTS to accept a temporary CPE device, which inherits and filters by the subscriber's default downstream cable modem group:
Router(config)# cable submgmt default filter-group cm downstreamThe following example configures the Cisco CMTS to accept a temporary CPE device, and to update the temporary CPE device with the current routing table from the Cisco CMTS:
Router(config)# cable submgmt default learnableThe following example configures the Cisco CMTS to accept a maximum of five temporary CPE devices behind a subscriber's cable modem:
Router(config)# cable submgmt default max-cpe 5Related Commands
show cable host
Displays the CPE devices (hosts) residing behind a specified cable modem (MAC address).
show cable tech-support
Cisco IOS Release 12.3(9a)BC introduces changes to the output of the show cable tech-support command. This change allows users with large numbers of online cable modems to collect the necessary information without consuming the console session for a long period of time.
To display general information about the router when reporting a problem, use the show cable tech-support command in privileged EXEC mode.
show cable tech-support [cable slot/port | cable slot/subslot/port]
Syntax Description
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Examples
The following example illustrates the cable modem and interface information for the Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed.
Router# show cable tech-support----------------------------------- Slot 8/1 ----------------------------------------------------- show cable modem Cable8/1/0 ------------------MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPIState Sid (dB) Offset CPE Enb------------------ show cable modem Cable8/1/0 connectivity ------------------Prim 1st time Times %online Online time Offline timeSid online Online min avg max min avg max------------------ show interface Cable8/1/0 sid ------------------Sid Prim MAC Address IP Address Type Age Admin Sched SfidState Type------------------ show interface Cable8/1/0 sid counter ------------------Sid Req-polls BW-reqs Grants Packets Frag Concatpktsissued received issued received complete received------------------ show interface Cable8/1/0 sid association ------------------Sid Prim Online IP Address MAC Address Interface VRF Name------------------ show interface Cable8/1/0 modem 0 ------------------SID Priv bits Type State IP address method MAC address------------------ show cable modem Cable8/1/1 ------------------MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPIState Sid (dB) Offset CPE Enb------------------ show cable modem Cable8/1/1 connectivity ------------------Prim 1st time Times %online Online time Offline timeSid online Online min avg max min avg max------------------ show interface Cable8/1/1 sid ------------------Sid Prim MAC Address IP Address Type Age Admin Sched SfidState Type------------------ show interface Cable8/1/1 sid counter ------------------Sid Req-polls BW-reqs Grants Packets Frag Concatpktsissued received issued received complete received------------------ show interface Cable8/1/1 sid association ------------------Sid Prim Online IP Address MAC Address Interface VRF Name------------------ show interface Cable8/1/1 modem 0 ------------------SID Priv bits Type State IP address method MAC addressFor additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
show controllers cable
Cisco IOS Release 12.3(9a)BC adds the tech-support keyword to the show controllers cable command. This change allows users with large numbers of online cable modems to collect the necessary line card information without consuming the console session for a long period of time.
Additional and related improvements are also available for the show tech-support command.
To display information about the interface controllers for a cable interface on the Cisco CMTS router, use the show controllers cable command in user EXEC or privileged EXEC mode.
show controllers cable {slot/port | slot/subslot/port} [downstream | upstream [port] | [mem-stat] [memory] [proc-cpu] [tech-support] ]
Syntax Description
slot/port
Identifies the cable interface and downstream port on the Cisco uBR7100 series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On the Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0 or 1, depending on the cable interface.
slot/subslot/port
Identifies the cable interface on the Cisco uBR10012 router. The following are the valid values:
•
•
•
downstream
(Optional) Displays downstream interface status.
upstream
(Optional) Displays upstream interface status.
port
(Optional) Specifies the desired upstream port. Valid values start with 0 for the first upstream port on the cable interface line card.
mem-stat
(Optional) Displays the output from the show memory statistics command to display a summary of memory statistics for a Broadband Processing Engine (BPE) cable interface line card.
memory
(Optional) Displays the output from the show memory command to display a summary of memory statistics, including the memory as it is allocated per process, for a Broadband Processing Engine (BPE) cable interface line card.
proc-cpu
(Optional) Displays the output from the show processes cpu command to display the processor status for a Broadband Processing Engine (BPE) cable interface line card.
tech-support
(Optional, privileged EXEC mode only) Displays the output from the show cable tech-support command for a Broadband Processing Engine (BPE) cable interface line card.
Command Modes
User EXEC, Privileged EXEC
Command History
Usage Guidelines
The mem-stat, memory, and proc-cpu keywords execute the related command on the processor that runs on added to obtain the relevant information from the onboard processor on Broadband Processing Engine (BPE) cable interface line cards, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U cards. This allows you to obtain information that is specific for that particular cable interface card, as opposed to having to run these commands on the entire router.
Note
Examples
The following is sample output for the downstream connection for cable interface 8/1/0 on a Cisco uBR10012 router:
Router# show controllers c8/1/0 downstreamCable8/1/0 Downstream is upFrequency not set, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 MspsFEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4Downstream channel ID: 0Dynamic Services Stats:DSA: 0 REQs 0 RSPs 0 ACKs0 Successful DSAs 0 DSA FailuresDSC: 0 REQs 0 RSPs 0 ACKs0 Successful DSCs 0 DSC FailuresDSD: 0 REQs 0 RSPs0 Successful DSDs 0 DSD FailuresDCC: 0 REQs 0 RSPs 0 ACKs0 Successful DCCs 0 DCC FailuresTable 18 describes the fields displayed by the show controllers cable downstream command.
Examples
The following example illustrates the information from the show controllers cable command for slot/subslot/port 8/1/0 on a Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed.
Router# show controllers c8/1/0Interface Cable8/1/0Hardware is MC28C(F-connector)BCM3210 revision=0x56B2idb 0x61329EB0 MAC regs 0x3E104000 PLX regs 0x3E000000rx ring entries 1024 tx ring entries 128 MAP tx ring entries 128Rx ring 0xC1AD080 shadow 0x613AAB38 head 0Tx ring 0xC1AF0C0 shadow 0x613ABBA8 head 34 tail 34 count 0MAP Tx ring 0xC1AF500 shadow 0x613AC018 head 52 tail 52 count 0Timestamp is from TCCplus cardthrottled 0 enabled 0 disabled 0Rx: spurious 0 framing_err 0 hcs_err 0 no_buffer 0 short_pkt 0no_enqueue 0 no_enp 0 miss_count 0 latency 0invalid_sid 0 invalid_mac 0 bad_ext_hdr_pdu 0 concat 0 bad-concat 0Tx: full 0 drop 0 stuck 0 latency 20MTx: full 0 drop 0 stuck 0 latency 10Slots 0 NoUWCollNoEngy 0 FECorHCS 1 HCS 1Req 3842362657 ReqColl 0 ReqNoise 0 ReqNoEnergy 3842362657ReqData 32 ReqDataColl 0 ReqDataNoise 0 ReqDataNoEnergy 32Rng 0 RngColl 0 RngNoise 0FECBlks 1 UnCorFECBlks 1 CorFECBlks 0MAP FIFO overflow 0, Rx FIFO overflow 0, No rx buf 0DS FIFO overflow 0, US FIFO overflow 0, US stuck 0Bandwidth Requests= 0x0--More--The following example illustrates memory statistics for the specified slot/subslot/port on the Cisco uBR10012 router:
Router# show controllers c8/1/0 mem-statHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 60F3FB40 185337024 8644376 176692648 176557288 176638828I/O C000000 67108864 6679384 60429480 60429480 60405696The following example illustrates upstream information for the specified slot/subslot/port on the Cisco uBR10012 router:
Router# show controllers c8/1/0 upstreamCable8/1/0 Upstream 0 is upFrequency 25.008 MHz, Channel Width 1.600 MHz, QPSK Symbol Rate 1.280 MspsSpectrum Group is overriddenSNR - Unknown - no modems online.Nominal Input Power Level 0 dBmV, Tx Timing Offset 0Ranging Backoff automatic (Start 0, End 3)Ranging Insertion Interval automatic (60 ms)Tx Backoff Start 3, Tx Backoff End 5Modulation Profile Group 1Concatenation is enabledFragmentation is enabledpart_id=0x3137, rev_id=0x03, rev2_id=0xFFnb_agc_thr=0x0000, nb_agc_nom=0x0000Range Load Reg Size=0x58Request Load Reg Size=0x0EMinislot Size in number of Timebase Ticks is = 4Minislot Size in Symbols = 32Bandwidth Requests = 0x0Piggyback Requests = 0x0Invalid BW Requests= 0x0Minislots Requested= 0x0Minislots Granted = 0x0Minislot Size in Bytes = 8Map Advance (Dynamic) : 2180 usecsUCD Count = 320676DES Ctrl Reg#0 = C000C043, Reg#1 = 0The following example illustrates CPU processes for the specified slot/subslot/port on the Cisco uBR10012 router:
Router# show controllers c8/1/0 proc-cpuCPU utilization for five seconds: 1%/1%; one minute: 1%; five minutes: 1%PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process1 4 1 4000 0.00% 0.00% 0.00% 0 Chunk Manager2 0 128036 0 0.00% 0.00% 0.00% 0 Load Meter3 248 395 627 0.00% 0.00% 0.00% 0 CR10K IPC MSG Pr4 428012 384113 1114 0.07% 0.07% 0.07% 0 CR10K NonBlk Xmt5 43392 65009 667 0.00% 0.00% 0.00% 0 Check heaps6 8 561 14 0.00% 0.00% 0.00% 0 Pool Manager7 0 1 0 0.00% 0.00% 0.00% 0 AAA_SERVER_DEADT8 0 2 0 0.00% 0.00% 0.00% 0 Timers9 0 2 0 0.00% 0.00% 0.00% 0 AAA high-capacit10 0 10680 0 0.00% 0.00% 0.00% 0 ARP Input11 0 1 0 0.00% 0.00% 0.00% 0 Entity MIB API12 0 2 0 0.00% 0.00% 0.00% 0 Serial BackgrounThe following example illustrates memory processor information for the specified slot/subslot/port on the Cisco uBR10012 router:
Router# show controllers c8/1/0 memoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 60F3FB40 185337024 8644376 176692648 176557288 176638828I/O C000000 67108864 6679384 60429480 60429480 60405696Processor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what60F3FB40 0000020004 00000000 60F4498C 001 -------- -------- 60113308 Managed Chunk Queue Elements60F4498C 0000001504 60F3FB40 60F44F94 001 -------- -------- 60126F88 List Elements60F44F94 0000005004 60F4498C 60F46348 001 -------- -------- 60126FCC List Headers60F46348 0000000048 60F44F94 60F463A0 001 -------- -------- 6055D4E4 *Init*60F463A0 0000000028 60F46348 60F463E4 001 -------- -------- 604C12B4 *Init*60F463E4 0000000048 60F463A0 60F4643C 001 -------- -------- 6055D4E4 *Init*60F4643C 0000000200 60F463E4 60F4652C 001 -------- -------- 6014BE28 *Init*60F4652C 0000004260 60F4643C 60F475F8 001 -------- -------- 60065A2C TTY data60F475F8 0000002004 60F4652C 60F47DF4 001 -------- -------- 60069164 TTY Input BufThe following example illustrates the first information for the tech-support option for the specified slot/subslot/port on the Cisco uBR10012 router:
Router# show controllers c8/1/0 tech-support------------------ show version ------------------Cisco Internetwork Operating System SoftwareIOS (tm) 7200 Software (UBR10KCLC-LC-M), Experimental Version 12.3(20040708:144155) [bguckel-geo_cable-l2 102]Copyright (c) 1986-2004 by cisco Systems, Inc.Compiled Mon 12-Jul-04 11:28 by bguckelImage text-base: 0x60008EB8, data-base: 0x60CB0000ROM: System Bootstrap, Version 12.2(20011031:221132) [maheshj-cr10k-rommon 15],DEVELOPMENT SOFTWAREBOOTLDR: 7200 Software (UBR10KCLC-LC-M), Experimental Version 12.2(20011107:233103) [janez-v122_2_xf_throttle.Nov5A 101]clc_8_1 uptime is 1 week, 9 hours, 54 minutesSystem returned to ROM by power-onSystem restarted at 08:59:44 UTC Wed Jul 21 2004Running default softwarecisco uBR10K CLC (NPE-CLC) processor (revision A) with 196608K/65536K bytes of memory.Processor board IDR7000 CPU at 262MHz, Implementation 39, Rev 2.1, 256KB L2 Cache6 slot midplane, Version 1.0For additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
show tech-support
Cisco IOS Release 12.3(9a)BC shortens the output of the show tech-support command on the Cisco uBR10012 and the Cisco uBR7246VXR routers. This change allows users with large numbers of online cable modems to collect information without consuming the console session for a long period of time.
To display general information about the Cisco CMTS router when reporting a problem to Cisco technical support, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password] [cef | ipc | ipmulticast | isis | mpls | ospf | rsvp]
Note
Note
Syntax Description
For additional information about this and other commands, refer to the following document on Cisco.com (updated through Cisco IOS Release 12.3(9a)BC):
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Caveats for Cisco IOS Release 12.3 BC
Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.
Cisco IOS Release 12.3 mainline is the parent release train for12.3(23)BC7. Unless otherwise noted, Cisco IOS Release 12.3(23)BC7 maintains support for the changes and caveat resolutions introduced in earlier releases of Cisco IOS Release 12.3 mainline.
Note
Open Caveats for Release 12.3(23)BC10
Table 19 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(23)BC10.
Resolved Caveats for Release 12.3(23)BC10
Table 20 lists only severity 1 and 2 caveats and select severity 3 resolved caveats for Cisco IOS Release 12.3(23)BC10.
Table 20 Resolved Caveats for Cisco IOS Release 12.3(23)BC10
CSCsz45567
A device running Cisco IOS Software, Cisco IOS XE Software, or Cisco IOS XR Software is vulnerable to a remote denial of service condition if it is configured for Multiprotocol Label Switching (MPLS) and has support for Label Distribution Protocol (LDP).
A crafted LDP UDP packet can cause an affected device running Cisco IOS Software or Cisco IOS XE Software to reload. On devices running affected versions of Cisco IOS XR Software, such packets can cause the device to restart the mpls_ldp process. A system is vulnerable if configured with either LDP or Tag Distribution Protocol (TDP).
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available.
This advisory is posted at:
http://www.cisco.com/warp/public/707/cisco-sa-20100324-ldp.shtml
CSCsz53710
Symptoms: Cannot ping or provision a Multimedia Terminal Adaptor (MTA) that has no IP connectivity.
Conditions: This issue occurs while upgrading to Cisco IOS Release 12.2(33)SCB2.
Workaround: Reset the MTA.
CSCsz75186
Cisco IOS Software is affected by a denial of service vulnerability that may allow a remote unauthenticated attacker to cause an affected device to reload or hang. The vulnerability may be triggered by a TCP segment containing crafted TCP options that is received during the TCP session establishment phase. In addition to specific, crafted TCP options, the device must have a special configuration to be affected by this vulnerability.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100324-tcp.shtml
CSCtc44253
Symptoms: The accumulated timing offset of a modem goes to a negative value. The following error message is displayed on the CMTS:
"%UBR10000-4-BADTXOFFSET: Bad timing offset -182443 detected for cable modem 000a.73cc.c7b7. "
Conditions: This issue occurs on the Cisco uBR10-MC5X20 line card.
Workaround: There is no workaround.
CSCte07585
Symptoms: The standby PRE crashes during the cable modem entry cleanup.
Conditions: This issue is seen on the Cisco uBR10012 (PRE 2) running the Cisco IOS Release 12.2(33)SCB4. This issue is seen when there are many cable modems and service flows on the network and there is congestion between the active and standby Router Processors, which could lead to the IPC packet drop.
Workaround: There is no workaround.
CSCte19290
Symptoms: PRE crashes after OIR or crash of the cable line card.
Conditions: This issue occurs when a bundle member cable line card is removed from the system before it is removed from the running configuration. This crashes the active PRE and the cable line card. This problem does not occur with every OIR, however, it occurs when there is a punted packet associated with the OIR/crashed interface.
Workaround: Remove the cable line card from the bundle configuration (running config) before OIR of the card.
CSCtf48376
Symptoms: A crash occurs on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB5 with PRE-4.
Conditions: This issue occurs when the show cable modem ip service flow verbose command is executed several times.
Workaround: Delete the fiber node configuration and reconfigure it.
CSCti25339
Symptoms: Cisco IOS device may experience a device reload.
Conditions: This issue occurs when the Cisco IOS device is configured for SNMP and receives certain SNMP packets from an authenticated user. Successful exploitation causes the affected device to reload. This vulnerability could be exploited repeatedly to cause an extended DoS condition.
Workaround: There is no workaround.
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 6.8/5.6:
CVE ID CVE-2010-3050 has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
CSCti81896
Symptoms: When the ingress cancellation feature is enabled, all modems on an upstream may momentarily go offline and then recover within minutes. This problem is not observed when the ingress cancellation feature is disabled.
Conditions: This issue occurs because the Rogue modems may transmit during ingress cancellation idle period. During this period, modems should not transmit. One or more modems consistently transmitting at this time period can create poor ingress cancellation performance for the burst receiver, and in the worst case situation, it can cause all modems to go offline momentarily until the upstream receiver re-adapts.
Workaround: Disable the ingress cancellation feature for that upstream, for which the rogue modems failures are encountered.
CSCtk09023
Symptoms: The service flow ID does not appear under scm service-flow main but appears under service-flow detail.
Conditions: This issue occurs with Cisco IOS Release 12.3(23)BCx, Cisco IOS Release 12.2(33)SCBx, Cisco IOS Release 12.2(33)SCCx and Cisco IOS Release 12.2(33)SCDx. The Cisco uBR10012 router may have service flow mismatch between the route processor and the cable line card when there is a high CPU usage by the line card or when there is a huge traffic load on the IPC bus due to mass cable modem registration events like an RF node failure. This affects both the upstream and downstream secondary service flows that are local or remote. When the downstream is remote, the CMTS reports 0 blaze index error for the affected downstream service flow.
For example,
scm 0011.e6fe.55ce service-flowSfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate ThroughputState Type26429 US act 5290 BE 1 1024000 10000000 0 6826441 US act 5296 NRTPS 4 64000 3044 32000 0 <-- Here26430 DS act N/A BE 1 6600000 12000000 0 026442 DS act N/A BE 4 64000 96000 32000 0UPSTREAM SERVICE FLOW DETAIL:SFID SID Requests Polls Grants Delayed Dropped PacketsGrants Grants26429 5290 86 0 86 0 0 3026439 5290 86 0 86 0 0 30 <-- HereWorkaround: There is no workaround.
CSCtl79450
Symptoms: High CPU usage during SNMP polling using OID docsQosMacToSrvFlowTable.
Conditions: This issue occurs during SNMP query on the docsQosMacToSrvFlowTable when the cable interfaces are located at the end of the list resulting in a search loop.
Workaround: Stop querying this table.
Open Caveats for Release 12.3(23)BC9
Table 21 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(23)BC9.
Resolved Caveats for Release 12.3(23)BC9
Table 22 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(33)BC9.