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)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)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: March 30, 2009, OL-6760-45
CDC Date: January 12, 2009The 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)BC7, 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(23)BC7, 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)BC7 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(23)BC7.
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.
Table 3 Cisco uBR10012 Universal Broadband Router Supported Hardware
Cable Interface Line Cards
Up to eight of the following broadband processing engines and cable interface line cards can be housed in a chassis in any combination:
•
•
•
Note
http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_eol_notice0900aecd80183921.html
Note
Cisco Half-Height Gigabit Ethernet Line Card
The Gigabit Ethernet (GigE) line card is a half-height, single-port, full-bandwidth Gigabit Ethernet line card providing multiple GigE links to the IP backbone. The Cisco half-height GigE line card also supports DOCSIS wideband capability through the Cisco uBR10000 universal broadband router.
Network Uplink Line Cards
Up to four line cards with any combination of the following WAN choices:
•
•
•
•
•
Timing, Communication and Control Plus (TCC+) Card
The TCC+ card can connect to an external reference Stratum 3 clock source that is traceable to a Stratum 1 source. Two such sources can be connected for redundancy.
The TCC+ card also monitors the cable line cards and power supply use, as well as control the LCD display screen on the chassis. Two cards can be installed for redundancy.
Performance Routing Engine 2 (PRE2)
The new Cisco uBR10012 Series PRE2 effectively doubles the bandwidth available to each slot on the router as supported by cable interface line cards or Cisco Broadband Processing Engines.
The PRE2 module introduces support for full-duplex Gigabit Ethernet ports, and increases the supported connections to 1.6 Gbps in full duplex (each direction per half-slot). Full-slot modules can now have up to 3.2 Gbps to and from the PRE2 module. This is twice the connection rate of the Cisco uBR10012 PRE1 route processor module.
Performance Routing Engine (PRE or PRE1)
One PRE or PRE1 module performs layer 2 and layer 3 packet processing, as well as routing and system management functions. Two PRE or PRE1 modules can be installed for redundancy.
Note
Note
AC-Input Power Entry Module (PEM)
The Cisco uBR10012 router ships with two AC power entry modules (AC PEMs) that provide a redundant power supply to the system. One AC PEM can provide sufficient power for a fully configured chassis, so that if one AC PEM fails, the other automatically begins providing power for the entire router, without impacting system operations.
The AC PEMs use standard 200-240 VAC (50/60 Hz) input power obtained through power receptacles on the front panel of each PEM. The two AC PEMs convert the AC power to provide filtered, redundant, and load shared DC power to the Cisco uBR10012 chassis.
Caution
DC-input Power Entry Module (PEM)
The Cisco uBR10012 router may ship with two DC PEMs to provide power to the chassis. The use of two PEMs provide power balancing and redundancy, as well as the ability to hot-swap a single power supply when needed.
Caution
Fan Assembly Module
The fan assembly module contains four fans that are capable of cooling the chassis even with the failure of a single fan. The fan assembly is dual-speed, providing additional cooling when the chassis temperature exceeds the nominal operating range.
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.cablemodem.com/specifications/gateway.html
•
http://www.packetcable.com/specifications/
•
–
http://www.packetcable.com/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:
•
For Cisco IOS Upgrade Ordering Instructions, refer to the document at the following location:
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://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
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:
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(23)BC7:
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)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_19_show_m_to_show_z.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_t.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 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, linking the port with a fiber-optic network. 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 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.
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
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/products/hw/cable/ps2217/products_feature_guide_book09186a008019b6bd.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/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:
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
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a0080459fc8.html
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:
•
http://www.cisco.com/en/US/products/hw/cable/ps2929/prod_release_note09186a00807d75e8.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2929/prod_configuration_guide09186a00807d75b2.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2929/prod_command_reference09186a00807d75cf.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:
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801ef1d7.html
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/ps2217/products_feature_guide_book09186a008019b6bd.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/products/hw/cable/ps2217/products_feature_guide09186a00801b17f2html
•
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™:
•
http://www.cablelabs.com/specifications/archives/CM-SP-DSG-I05-050812-Superseded.pdf
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/products/hw/cable/ps2217/products_feature_guides_list.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:
•
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:
•
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:
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801ef1d7.html
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/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/products/hw/cable/ps2217/products_feature_guide09186a00801b17f2.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801b17f2.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:
•
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/products/hw/cable/ps2217/products_feature_guide09186a00801b17cc.html
•
http://www.cisco.com/en/US/tech/tk828/technologies_case_study0900aecd802e2ce2.shtml
•
•
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/univercd/cc/td/doc/product/cable/cmtsmib/index.htm
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
•
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
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801eefa9.html
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
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801eefa9.html
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:
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801ef1d7.html
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/products/hw/cable/ps2209/tsd_products_support_series_home.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/tsd_products_support_series_home.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/tsd_products_support_series_home.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:
•
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/products/hw/cable/ps2209/prod_eol_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_guides_list.html
•
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
•
http://www.cablemodem.com/downloads/specs/CM-SP-DSG-I03-041124.pdf
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/products/hw/cable/ps2209/prod_eol_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.htmlFor 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/products/sw/iosswrel/ps5013/products_feature_guide09186a00801999b2.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/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/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:
•
•
•
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:
•
•
•
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/products/sw/iosswrel/ps1830/products_feature_guide09186a0080087b55.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a008021b8fb.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/products/hw/cable/ps2217/products_feature_guide_book09186a008019b6bd.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:
•
•
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:
•
•
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:
•
•
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:
•
•
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:
•
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/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/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.packetcable.com/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/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.packetcable.com/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/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/products/hw/cable/ps2217/products_feature_guide09186a0080159396.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:
•
•
•
•
Guest
