Cisco uBR10012 Universal Broadband Router Software Configuration Guide
Chapter 1: Overview of Cisco uBR10012 Universal Broadband Router Software
Downloads: This chapterpdf (PDF - 1.38MB) The complete bookPDF (PDF - 6.42MB) | Feedback

Overview of Cisco uBR10012 Universal Broadband Router Software

Table Of Contents

Overview of Cisco uBR10012 Universal Broadband Router Software

Cisco IOS Releases and Images for the Cisco uBR10012 Router

Operational Overview

Cisco IOS Software Location

Determining Your Cisco IOS Software Release

Upgrading to a New Software Release

12.3 BC Release Train and Images

12.2 BC Release Train and Images

12.2 CY Release Train and Images

Cisco uBR10012 Universal Broadband Router Chassis Overview

Cisco uBR10012 Router Slot Numbering

Hardware Supported on the Cisco uBR10012 Router

Supported Software Features for the Cisco uBR10012 Router

Cisco uBR10012 Router Features and Cisco IOS Releases

Cisco uBR10012 Router Configuration Tools

AutoInstall

Cable Interface Setup Facility

Configuration Mode (Command Line Interface Configuration)

Cisco Network Registrar

Extended Setup Facility

Cisco IOS Release 12.3 BC Command-line Enhancements

Cisco IOS Release 12.3(13a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

DHCP Servers and Feature Support

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

Integrated DHCP Server

DOCSIS 1.0 Feature Support

DOCSIS 1.0 Baseline Privacy Interface

DOCSIS 1.0 Concatenation Override

DOCSIS 1.0 Configuration File Settings

DOCSIS 1.0 Constant Bit Rate Extension

DOCSIS 1.0 MAC Driver

DOCSIS 1.0 Quality of Service Support

DOCSIS 1.0 Payload Header Suppression

DOCSIS 1.0 per SID Bandwidth Request and Grant Counters

DOCSIS 1.0 ToS Overwrite

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

DOCSIS 1.0+ Feature Support

DOCSIS 1.1 Feature Support

DOCSIS 1.1 Baseline Privacy Interface Plus Features

DOCSIS BPI+ Multiple Root Certificate Support

DOCSIS 1.1 CM Compatibility

DOCSIS 1.1 CM Database Manager

DOCSIS 1.1 Concatenation Support

DOCSIS 1.1 Customer Premises Equipment Configurator

DOCSIS 1.1 Downstream Packet Classifier

DOCSIS 1.1 Downstream Packet Scheduler

DOCSIS 1.1 Dynamic MAC Messages

DOCSIS 1.1 Enhanced Registration

DOCSIS 1.1 Fragmentation and Reassembly

DOCSIS 1.1 Layer 2 Fragmentation

DOCSIS 1.1 MAC Scheduler

DOCSIS 1.1 Payload Header Suppression and Restoration

DOCSIS 1.1 Quality of Service Support

DOCSIS 1.1 Rate Limiting and Traffic Shaping

DOCSIS 1.1 Service Flow Manager

DOCSIS 1.1 Service Template and Class Manager

DOCSIS 1.1 Software Infrastructure

DOCSIS 1.1 Subscriber Management

DOCSIS 1.1 Time Slot Scheduling

DOCSIS 1.1 TLV Parser and Encoder

DOCSIS 1.1 Token-Bucket Rate Shaping

DOCSIS 1.1 Two-Way Interoperability

Optional Upstream Scheduler Modes

High Availability Features

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Backup Path Testing for the Cisco RF Switch

DSX Messages and Synchronized PHS Information

Factory-Configured HCCP N+1 Redundancy

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

HCCP N+1 Redundancy Supporting DOCSIS 1.1 for the Cisco CMTS

HCCP Timing and Error Enhancements in HCCP Redundancy Show Commands

High Availability Support for Encrypted IP Multicast

Shutdown and No Shutdown Enhancement for Cable Interfaces

Intercept Features

Access Control List Support for COPS Intercept

Basic Wiretap Support

Cable Monitor Enhancements

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

cable monitor Command

COPS TCP Support for the Cisco Cable Modem Termination System

Packet Intercept

PXF ARP Filter

PXF Divert Rate Limiting

Service Independent Intercept (SII) Support

IP Broadcast and Multicast Features

IP Broadcast Echo

IP Multicast Echo

Multicast QoS Support on the Cisco uBR10012 CMTS

SSM Mapping

IP Routing Features

Cable ARP Filter Enhancement

Configurable Registration Timeout

Host-to-Host Communication (Proxy Address Resolution Protocol)

Integrated Time-of-Day Server

PBR support for the Cisco uBR10012

Supported Protocols

Management Features

Admission Control for the Cisco CMTS

Broadband Internet Access

Cable Interface Bundling

CNEM Compliance

Customer Premises Equipment Limitation and Override

DOCSIS 2.0 SAMIS ECR Data Set

DOCSIS Set-Top Gateway Issue 1.0

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Advanced-mode DOCSIS Set-Top Gateway Issue 1.2

Downstream Channel ID Configuration

Downstream Frequency Override

Downstream Load Balancing Distribution with Upstream Load Balancing

Dynamic Channel Change (DCC) for Loadbalancing

Dynamic Modulation Profiles

Dynamic Upstream Modulation

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

Management Information Base (MIB) Changes and Enhancements

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

Pre-equalization Control for Cable Modems

Route Processor Redundancy Support

Secure Socket Layer Server for Usage-Based Billing

SFID Support for Multicast and Cable Interface Bundling

Simple Network Management Protocol Cable Modem Remote Query

Simple Network Management Protocol v3

Spectrum Management

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Static CPE Override (cable submgmt default Command)

Statistical Counters

Subscriber Traffic Management (STM) Version 1.1

Usage Based Billing (SAMIS)

PacketCable and Voice Support Features

PacketCable 1.0 With CALEA

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

Packetcable Multimedia for the Cisco CMTS

Security Features

Address Verification

CM Transmission Burst Size

Dynamic or Mobile Host Support

Dynamic Shared Secret (DMIC) with OUI Exclusion

Testing, Troubleshooting and Diagnostic Features

Cisco Broadband Troubleshooter 3.2

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Dynamic Ranging

Flap List Support

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Virtual Interfaces

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

VLAN Features

VPN and Layer 2 Tunneling Features

Dynamic SID/VRF Mapping Support

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

IPv6 over L2VPN

MPLS-VPN Network Support

NetFlow Accounting Versions 5 and 8 Support

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Transparent LAN Service and Layer 2 Virtual Private Networks


Overview of Cisco uBR10012 Universal Broadband Router Software


This chapter describes the Cisco uBR10012 Universal Broadband Router Cable Modem Termination System (CMTS), supported service offerings, software, and related hardware features. This chapter contains the following sections:

Section
Purpose

Cisco IOS Releases and Images for the Cisco uBR10012 Router

Describes the supported Cisco IOS release trains, associated features, and latest Cisco IOS images for each recently supported train.

One early step in CMTS feature configuration is to verify your Cisco IOS release train, the associated image and feature set. This section guides you in determining such information.

Cisco uBR10012 Universal Broadband Router Chassis Overview

Describes the Cisco uBR10012 router, and supported hardware features and interoperability.

Supported Software Features for the Cisco uBR10012 Router

Describes the features and configuration utilities that are available on the Cisco uBR10012 router.


The remaining chapters in this guide provide basic software configuration and troubleshooting procedures.

Cisco IOS Releases and Images for the Cisco uBR10012 Router

The Cisco uBR10012 router supports the following Cisco IOS methods and release trains:

Operational Overview

Cisco IOS Software Location

Determining Your Cisco IOS Software Release

Upgrading to a New Software Release

12.3 BC Release Train and Images

12.2 BC Release Train and Images

12.2 CY Release Train and Images

Operational Overview

The Cisco uBR10012 router runs the IOS image that is located on the Type II Personal Computer Memory Card International Association (PCMCIA) Flash memory disks. These disks are located in the two PCMCIA slots in the primary Performance Routing Engine 1 (PRE1). A PCMCIA disk in either slot can store a Cisco IOS image or configuration file.

In addition to the Flash memory disks, each PRE1 module contains onboard Flash memory that is used to store a boot loader. The loader executes following a system reset to reload and execute the Cisco IOS software on the Flash memory disks.

The PRE1 module also stores the system configuration in the onboard Flash memory. The configuration information read from the Flash memory is buffered in operational memory following initialization, and is written to the Flash memory device when you save the configuration.

Each line card also contains onboard Flash memory that is used to store a boot loader, similar in function to that used on the PRE1 module. However, the line card loader executes following a system reset, line card reset, or line card insertion to reload and execute any code that must run on the line card for it to operate properly. Software images may also be stored on an external TFTP server. If the Cisco uBR10012 router is so configured, it then downloads the proper image from the TFTP server and executes it.

Cisco IOS Software Location

Cisco IOS software is stored on the PRE1 module, which includes two PCMCIA slots that are accessible from the front panel. Either slot can store an IOS image or configuration file.

The Flash memory on the PRE1 module is used to store a simple ROM monitor or boot loader. The loader executes following a system reset, line card reset, or line card insertion.

Line card images may also be stored in PRE1 module Flash memory or on an external TFTP server.

The PRE1 module stores the system configuration in a 512 KB NVRAM device. Configuration information read from NVRAM is buffered in RAM following initialization and is written to the device when you save the configuration.

Determining Your Cisco IOS Software Release

To determine the version of Cisco IOS software running on the Cisco uBR10012 router, log in to the router and enter the show version command in privileged EXEC mode. For example:

Router> show version
Cisco Internetwork Operating System Software 
IOS (tm) 12.2 XF Software (ubr10k-k8p6-mz), Version 12.2 XF, RELEASE SOFTWARE
 
   

Upgrading to a New Software Release

An upgrade is an order placed for a Cisco IOS® feature set that contains more functionality than the one that you are replacing. And upgrade is not an update. An update consists of installing a more recent version of the SAME feature set. Exception— If a feature set has been made obsolete, the next, closest feature set, on a more recent release, will be considered an update.

For general information about upgrading to a new software release, refer to the Cisco IOS Upgrade Ordering Instructions on Cisco.com.

12.3 BC Release Train and Images

The 12.3 Release Train is the first Cisco IOS Release to support the Performance Routing Engine 2 (PRE2) modules on the Cisco uBR10012 universal broadband router. This release adds a substantial number of additional features while continuing to support earlier supported features from the 12.2 Release Train. These features are introduced in the "Supported Software Features for the Cisco uBR10012 Router" section, with additional links for configuration documentation.

Table 1-1 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.3(9a)BC.

Table 1-1 Memory Recommendations for the Cisco uBR10012 Routers, Cisco IOS Release 12.3(9a)BC Feature Sets 

Feature Set
Cisco uBR10012 Route Processor
Software Image
Recommended
Flash Memory
Recommended
DRAM Memory 1
Runs
From

DOCSIS BPI IP Plus

PRE1

ubr10k-k8p6-mz

48MB

512 MB

RAM

PRE2

ubr10k2-k8p6-mz

48MB

1.0 GB

RAM

DOCSIS Base 3 DES

PRE1

ubr10k-k9p6-mz

48MB

512 MB

RAM

PRE2

ubr10k2-k9p6-mz

48MB

1.0 GB

RAM

1 DRAM memory is not configurable on the Cisco uBR10012 router.


12.2 BC Release Train and Images

The 12.2 BC train is an interim release train that provides DOCSIS 1.1 two-way support, along with support for selected new features.

Cisco IOS Release 12.2(4)BC1b, provides a migration path from the earlier 12.2 XF releases. Cisco IOS Release 12.2(4)BC1b supports the Cisco uBR10012 universal broadband router, which provides a high-capacity, high-throughput cable modem termination system (CMTS), optimized for aggregating traffic at the edge of the cable network. Designed for cable operators and service providers, the platform connects residential subscribers via cable modems, digital set-top boxes, or IP telephony cable modems for high-speed data, broadband entertainment, and IP telephony solutions.


Note Cisco IOS Release 12.2(4)BC1b does not include support for telco-return images.


Table 1-2 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.2(4)BC1b. Cisco uBR10012 universal broadband routers are available with a 48-MB or 120-MB Type II PCMCIA Flash memory card.

Table 1-2 Memory Recommendations for the Cisco uBR10012 Routers,
Cisco Release 12.2 BC Feature Sets

Feature Set
Software Image
Recommended Flash Memory
Recommended DRAM Memory
Runs From

DOCSIS BPI IP Plus

ubr10k-k8p6-mz1

40 MB Flash

128 MB DRAM

RAM

1 The Cisco IOS 12.2(11)BC3 image cannot be loaded from a 128 MB Flask Disk. This image is not available in the Cisco IOS 12.2(11)BC2a rebuild release.



Note In Cisco IOS Release 12.2(11)BC3 only, the ubr10k-k8p6-mz software image could not be loaded from a 128 MB Flash Disk card. See caveat CSCea65301 in Bug Toolkit for more information. This caveat was fixed, and this limitation removed, in Cisco ISO 12.2(11)BC3a and later Release 12.2 BC releases.


12.2 CY Release Train and Images

The Cisco IOS 12.2 CY release train is based on Cisco IOS Release 12.2(11)BC1b, which in turn is based on Cisco IOS Release 12.2(11)T. The Cisco IOS Release 12.2(11)BC1b train is an interim release train that provides DOCSIS 1.1 two-way support, along with support for selected new features. Cisco IOS Release 12.2(11)BC1b provides a migration path from the earlier 12.2 XF releases.

The Cisco IOS 12.2 CY release train provides the following additional software features:

PBR support for Cisco uBR10012

VLAN support for Cisco uBR10012


Note Cisco IOS Release 12.2(11)CY does not include support for telco-return images.


Table 1-2 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.2(11)CY. Cisco uBR10012 universal broadband routers are available with a 48-MB or 120-MB Type II PCMCIA Flash memory card.

Table 1-3 Memory Recommendations for the Cisco uBR10012 Routers,
Cisco Release 12.2 CY Feature Sets

Feature Set
Software Image
Recommended Flash Memory
Recommended DRAM Memory
Runs From

DOCSIS IP Plus

ubr10k-p6-mz

40 MB Flash

128 MB DRAM

RAM

DOCSIS BPI IP Plus

ubr10k-k8p6-mz

40 MB Flash

128 MB DRAM

RAM


Cisco uBR10012 Universal Broadband Router Chassis Overview

The Cisco uBR10012 router provides a cost-effective, scalable, and industry-proven CMTS, optimized for aggregating traffic at the edge of the cable network. It has eight broadband aggregation slots and four WAN backhaul slots. The broadband slots can support Cisco uBR7200 series broadband cards through an adapter card (line card processor).

Designed for cable operators and service providers, the Cisco uBR10012 router CMTS platform connects residential subscribers via CMs, digital set-top boxes, or IP telephony CMs for high-speed data, broadband entertainment, and IP telephony solutions.


Note This guide focuses on Cisco uBR10012 router software and related hardware. For detailed descriptions of the Cisco uBR10012 router chassis and components, refer to these resources:


Cisco uBR10012 Universal Broadband Router Hardware Installation Guide

Cisco uBR10012 Field Replaceable Units (FRUs) web page on Cisco.com

The Cisco uBR10012 router chassis is designed for front and rear access. The front of the chassis provides access to these components, shown in Figure 1-1:

Two Performance Routing Engine 1 (PRE1) or PRE2 processor modules

LCD Display

Two DC Power Entry Modules (DC PEMs)

Fan Assembly Module

The rear of the chassis provides access to these components, shown in Figure 1-2:

Eight Cable Interface Line Cards (single-slot)

Four High-Speed, High-Performance Network Uplink Interface Line Cards

Two Timing, Communication, and Control Plus (TCC+) Cards

The Cisco uBR10012 router uses redundant PEMs using -48-60 VDC input power. An optional AC-input power shelf can be used to provide the DC-output power for the Cisco uBR10012 router.

Cisco uBR10012 Router Slot Numbering

The Cisco uBR10012 router contains 16 card slots total for the following cards:

Front Access (refer to Figure 1-1):

One or two PRE1 or PRE2 modules (two modules for redundant configuration)

Rear Access (refer to Figure 1-2):

Eight cable interface line cards

Four network uplink line cards (either OC-12 POS or GigE)

One or two TCC+ cards (two TCC+ cards for redundant configuration)—each TCC+ card also provides a connector for an external clock reference source, with a second connector for a backup clock source

Figure 1-1 shows the slot numbering for the front view components of a fully loaded Cisco uBR10012 router with the corresponding slot numbering (without bezel).

Figure 1-1 Cisco uBR10012 Router Slot Numbering—Front View (without bezel)


Tip The Fast Ethernet interface on the backup PRE module is not used unless the primary PRE module fails and the backup PRE module is activated. When the backup PRE module becomes the active PRE module, its FastEthernet interface automatically becomes the active FastEthernet interface at slot 0/0.


Figure 1-2 shows the rear view components of a fully loaded Cisco uBR10012 router with the corresponding slot numbering.

Figure 1-2 Cisco uBR10012 Router Slot Numbering—Rear View

Hardware Supported on the Cisco uBR10012 Router

Cisco IOS Release 12.3(9a)BC supports the following hardware on the Cisco uBR10012 router. This and earlier descriptions of supported hardware are available in the release notes for your respective Cisco IOS release.

Table 1-4 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:

Cisco uBR10-MC5X20S/U broadband processing engines

Cisco uBR10-LCP2-MC16C/MC16E/MC16S cable interface line cards

Cisco uBR10-LCP2-MC28C cable interface line cards

Note The Cisco uBR7200 Series MC28U BPE does not support the Cisco uBR10012 router, though the Cisco MC28U BPE physically fits into the Cisco uBR10012 router chassis.

Network Uplink Line Cards

Up to four line cards with any combination of the following WAN choices:

Cisco uBR10-SRP-OC12SML DPT WAN Line Card for the Cisco uBR10012 Router

Cisco uBR10012 OC-48 DPT/POS interface module

Cisco uBR10-1GE Gigabit Ethernet (GigE) uplink line card

Cisco uBR10-1OC12/P-SMI OC-12 POS uplink line card

Cisco uBR10-SRP-OC12SML Dynamic Packet Transport (DPT) WAN card

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 (PRE1 or PRE2)

One PRE1 or PRE2 module performs layer 2 and layer 3 packet processing, as well as routing and system management functions. Two PRE modules can be installed for redundancy.

Note The PRE1 module is functionally identical to the PRE module except that it adds support for the Error Checking and Correction (ECC) feature, which can automatically correct single-bit memory errors.

Note The Cisco uBR10012 PRE1 module supports an Ethernet port to a LAN for a 10BASE-T or 100BASE-T connection for network management. The PRE1 module supports connections of 800 Mbps in full duplex (each direction) per half-slot.

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 The Cisco uBR10012 router does not support mixing AC and DC PEMs. Both PEMs must be either AC PEMs or DC PEMs.

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 The Cisco uBR10012 router does not support mixing AC and DC PEMs. Both PEMs must be either AC PEMs or DC PEMs.

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.


Supported Software Features for the Cisco uBR10012 Router

This section summarizes Cisco uBR10012 router software features for all supported Cisco IOS Release trains, and directs you to additional configuration information for each feature.

Cisco uBR10012 Router Features and Cisco IOS Releases

Table 1-5 summarizes the software-related features and related Cisco IOS releases that support the Cisco uBR10012 router. Cisco IOS features indicate the first release in which the feature was introduced. Unless otherwise noted, feature support continues in later releases of the same or related Cisco IOS release train.

Table 1-5 Cisco uBR10012 Router Features by Cisco IOS Release 

Feature
Supporting Cisco IOS Releases

AutoInstall

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Cable Interface Setup Facility

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Cisco Network Registrar

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Configuration Mode (Command Line Interface Configuration)

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Extended Setup Facility

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

12.3(9a)BC and later 12.3 BC releases

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

Cisco IOS Release 12.3(13a)BC and later 12.3 BC releases.

Integrated DHCP Server

Multiple Cisco IOS releases and trains.

DOCSIS 1.0 Baseline Privacy Interface

DOCSIS 1.0 BPI encryption and authentication supported in Cisco IOS 12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 Concatenation Override

12.3(13a)BC and later 12.3 BC releases

DOCSIS 1.0 Configuration File Settings

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 Constant Bit Rate Extension

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 MAC Driver

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 Quality of Service Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 Payload Header Suppression

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 per SID Bandwidth Request and Grant Counters

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.0 ToS Overwrite

12.3(17a)BC2 and later 12.3 BC releases.

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

12.3(13a)BC and later 12.3 BC releases

DOCSIS 1.1 CM Compatibility

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Baseline Privacy Interface Plus Features

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS BPI+ Multiple Root Certificate Support

12.3(13a)BC and later 12.3 BC releases

DOCSIS 1.1 CM Compatibility

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 CM Database Manager

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Concatenation Support

See also DOCSIS 1.0 Concatenation Override

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Customer Premises Equipment Configurator

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Downstream Packet Classifier

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Downstream Packet Scheduler

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Dynamic MAC Messages

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Enhanced Registration

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Fragmentation and Reassembly

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Layer 2 Fragmentation

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 MAC Scheduler

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Payload Header Suppression and Restoration

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Quality of Service Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Rate Limiting and Traffic Shaping

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Service Flow Manager

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Service Template and Class Manager

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Software Infrastructure

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Subscriber Management

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Time Slot Scheduling

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 TLV Parser and Encoder

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Token-Bucket Rate Shaping

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 1.1 Two-Way Interoperability

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Optional Upstream Scheduler Modes

12.3(13a)BC and later 12.3 BC releases

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

12.3(13a)BC and later 12.3 BC releases

Backup Path Testing for the Cisco RF Switch

12.3(13a)BC and later 12.3 BC releases

DSX Messages and Synchronized PHS Information

12.3(17a)BC and later 12.3 BC releases

Factory-Configured HCCP N+1 Redundancy

12.3(13a)BC and later 12.3 BC releases

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

12.3(17a)BC and later 12.3 BC releases

HCCP N+1 Redundancy Supporting DOCSIS 1.1 for the Cisco CMTS

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

HCCP Timing and Error Enhancements in HCCP Redundancy Show Commands

12.3(13a)BC and later 12.3 BC releases

High Availability Support for Encrypted IP Multicast

12.3(17a)BC and later 12.3 BC releases

Shutdown and No Shutdown Enhancement for Cable Interfaces

12.3(13a)BC and later 12.3 BC releases

Access Control List Support for COPS Intercept

12.3(13a)BC and later 12.3 BC releases

Basic Wiretap Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Cable Monitor Enhancements

12.3(17a)BC and later 12.3 BC releases

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

12.3(13a)BC and later 12.3 BC releases

cable monitor Command

12.2(4)XF and later 12.2 XF, 12.2 BC and 12.3 BC releases

COPS TCP Support for the Cisco Cable Modem Termination System

12.3(13a)BC and later 12.3 BC releases

Packet Intercept

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

PXF ARP Filter

12.3(17a)BC and later 12.3 BC releases

PXF Divert Rate Limiting

12.3(17a)BC and later 12.3 BC releases

Service Independent Intercept (SII) Support

12.3(13a)BC and later 12.3 BC releases

IP Broadcast Echo

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

IP Multicast Echo

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Multicast QoS Support on the Cisco uBR10012 CMTS

12.3(13a)BC and later 12.3 BC releases

SSM Mapping

12.3(17a)BC and later 12.3 BC releases

Cable ARP Filter Enhancement

12.3(9a)BC and later 12.3BC releases

Configurable Registration Timeout

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

12.3(13a)BC and later 12.3 BC releases

Host-to-Host Communication (Proxy Address Resolution Protocol)

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Integrated DHCP Server

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Integrated Time-of-Day Server

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

PBR support for the Cisco uBR10012

12.2(11) CY and later CY releases

Supported Protocols

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Admission Control for the Cisco CMTS

12.3(13a)BC and later 12.3 BC releases

Broadband Internet Access

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Cable Interface Bundling

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

CNEM Compliance

12.3(17a)BC and later 12.3 BC releases

Customer Premises Equipment Limitation and Override

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

DOCSIS 2.0 SAMIS ECR Data Set

12.3(17a)BC and later 12.3 BC releases

DOCSIS Set-Top Gateway Issue 1.0

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Advanced-mode DOCSIS Set-Top Gateway Issue 1.2

12.3(9a)BC and later 12.3 BC releases

12.3(13a)BC and later 12.3 BC releases

12.3(17a)BC2 and later 12.3 BC releases

Downstream Channel ID Configuration

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Downstream Frequency Override

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Downstream Load Balancing Distribution with Upstream Load Balancing

12.3(17b)BC and later 12.3 BC releases

Dynamic Channel Change (DCC) for Loadbalancing

12.3(17a)BC and later 12.3 BC releases

Dynamic Modulation Profiles

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Dynamic Upstream Modulation

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

12.3(9a)BC and later 12.3 BC releases

Management Information Base (MIB) Changes and Enhancements

12.3(17a)BC and later 12.3 BC releases

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

12.3(9a)BC and later 12.3 BC releases

Pre-equalization Control for Cable Modems

12.3(17a)BC and later 12.3 BC releases

Route Processor Redundancy Support

12.2(4)XF 12.2 XF , 12.2 BC and 12.3 BC releases

Secure Socket Layer Server for Usage-Based Billing

12.3(17a)BC and later 12.3 BC releases

SFID Support for Multicast and Cable Interface Bundling

12.3(9a)BC and later 12.3 BC releases

Simple Network Management Protocol Cable Modem Remote Query

12.2(4)BC1b and later 12.2 BC and 12.3 BC releases

Simple Network Management Protocol v3

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Spectrum Management

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

12.3(13a)BC and later 12.3 BC releases

Static CPE Override (cable submgmt default Command)

12.3(9a)BC and later 12.3 BC releases

Statistical Counters

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Subscriber Traffic Management (STM) Version 1.1

12.3(9a)BC and later 12.3 BC releases

Usage Based Billing (SAMIS)

12.3(9a)BC and later 12.3 BC releases

PacketCable 1.0 With CALEA

12.3(9a)BC and later 12.3 BC releases

PacketCable Emergency 911 Cable Interface Line Card Prioritization

12.3(13a)BC and later 12.3 BC releases

PacketCable Emergency 911 Services Listing and History

12.3(13a)BC and later 12.3 BC releases

Packetcable Multimedia for the Cisco CMTS

12.3(13a)BC and later 12.3 BC releases

Address Verification

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

CM Transmission Burst Size

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Dynamic or Mobile Host Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Dynamic Shared Secret (DMIC) with OUI Exclusion

12.3(9a)BC and later 12.3 BC releases

Cisco Broadband Troubleshooter 3.2

12.3(9a)BC and later 12.3 BC releases

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

12.3(9a)BC and later 12.3 BC releases

Dynamic Ranging

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Flap List Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

12.3(13a)BC and later 12.3 BC releases

Virtual Interfaces

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

12.3(9a)BC and later 12.3 BC releases

Virtual Interface Support for HCCP N+1 Redundancy

12.3(9a)BC and later 12.3 BC releases

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

12.3(13a)BC and later 12.3 BC releases

VLAN Features

12.2(11)CY and later 12.2 CY releases

Dynamic SID/VRF Mapping Support

12.3(13a)BC and later 12.3 BC releases

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

12.3(17a)BC and later 12.3 BC releases

IPv6 over L2VPN

12.3(17a)BC and later 12.3 BC releases

MPLS-VPN Network Support

12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases

NetFlow Accounting Versions 5 and 8 Support

12.3(9a)BC and later 12.3 BC releases

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

12.3(9a)BC and later 12.3 BC releases

Transparent LAN Service and Layer 2 Virtual Private Networks

12.3(13a)BC and later 12.3 BC releases


Cisco uBR10012 Router Configuration Tools

The Cisco uBR10012 Universal Broadband Router provides you with the following configuration tools, allowing you flexibility in choosing your configuration method:

AutoInstall

Cable Interface Setup Facility

Cisco Network Registrar

Configuration Mode (Command Line Interface Configuration)

Extended Setup Facility

AutoInstall

The AutoInstall process configures the Cisco uBR10012 router automatically after connection to your WAN. For additional information, refer to the "Configuring the Cisco uBR10012 Router Using AutoInstall" section.

Cable Interface Setup Facility

The Cisco uBR10012 router Setup facility (also called the System Configuration dialog) is a useful and efficient tool for configuring your CMTS. The Setup facility supports the a number of functions so that cable interfaces and cable interface line cards are fully operational (after initial setup). Refer to the "Configuring the Cisco uBR10012 Router Using the Setup Facility" section.

Configuration Mode (Command Line Interface Configuration)

The Configuration mode allows you to configure the Cisco uBR10012 router manually if you prefer not to use Autoinstall or the Cable Interface Setup facility. For additional information, refer to the "Configuring the Cisco uBR10012 Router Manually Using Configuration Mode" section.

Cisco Network Registrar

Cisco provides the Cisco Network Registrar with each Cisco uBR10012 router. Cisco Network Registrar dramatically improves the reliability of naming and addressing services for enterprise and service provider networks. Cisco Network Registrar provides scalable Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) services and forms the basis of a DOCSIS CM provisioning system.

Cisco Network Registrar is a configuration tool that automates dynamic IP address allocation to cable interfaces, PCs, and other devices on the broadband network. Cisco Network Registrar allows you to track serial numbers and MAC addresses for each cable interface on your network, and reduces customer service involvement when tracking subscriber CPE equipment.

For additional information about configuring or using Cisco Network Registrar, refer to the latest Cisco Network Registrar documentation at the Cisco Web site (http://www.cisco.com). One such document is Installing the Cisco Network Registrar for the Cisco uBR7200 series routers, and the Cisco Subscriber Registration Center Device Provisioning Registrar 2.0, both located on Cisco.com.

Extended Setup Facility

The Cable Interface Setup facility (described previously in this section) creates an initial CMTS configuration. The Extended Setup facility prompts you to configure each interface on the system as you progress through the CMTS configuration. For additional information, refer to the "Configuring the Cable Interface with the Extended Setup Facility" section.

Cisco IOS Release 12.3 BC Command-line Enhancements

This section describes general Cisco IOS commands introduced or enhanced in Cisco IOS Release 12.3(9a)BC and later releases in the 12.3 BC release train. Also refer to additional feature descriptions for new or enhanced commands that support specific new features.

Cisco IOS Release 12.3(13a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS Release 12.3(13a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS release 12.3(13a)BC introduces several new or enhanced commands. For this release, these feature-specific commands or enhancements are described with the features they support. Refer to additional feature descriptions in this document for additional information.

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS Release 12.3(9a)BC introduces or enhances the following CLI commands for the Cisco uBR10012 router:

cable arp filter (See Cable ARP Filter Enhancement)

cable logging layer2events

cable source-verify

show cable tech-support

show controllers cable

show tech-support

For additional information about these command changes, refer to these resources:

Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

DHCP Servers and Feature Support

Cisco IOS software supports multiple DHCP features and server functions on the network for the Cisco uBR10012 router:

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

Integrated DHCP Server

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.


Note When the cable source-verify dhcp feature is enabled, and a statically-defined IP address has been added to the CMTS for a CM using the cable trust command to override the cable source-verify dhcp checks for this device, packets from this CM will continue to be dropped until an entry for this CM is added to the ARP database of the CMTS. To achieve this, disable the cable source-verify dhcp feature, ping the CMTS from the CM to add an entry to the ARP database, and re-enable the cable source-verify dhcp feature.


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:

IP Address Verification for the Cisco uBR7200 Series Cable Router

http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/sourcver.html

Filtering Cable DHCP Lease Queries

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblsrcvy.html

Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

CABLE SECURITY, Cable Source-Verify and IP Address Security, White Paper

http://www.cisco.com/en/US/tech/tk86/tk803/technologies_tech_note09186a00800a7828.shtml

Integrated DHCP Server

This network management feature simplifies provisioning, offering an integrated Dynamic Host Configuration Protocol server. For information about configuring DHCP, ToD, or TFTP services, refer to the chapter titled "Configuring DHCP, ToD, and TFTP Services" in the Cisco Cable Modem Termination System Feature Guide on Cisco.com.

DOCSIS 1.0 Feature Support

The Cisco uBR10012 router and associated Cisco IOS software support multiple DOCSIS 1.0 enhancements, extensions, and features.

DOCSIS 1.0 Baseline Privacy Interface

DOCSIS 1.0 Concatenation Override

DOCSIS 1.0 Configuration File Settings

DOCSIS 1.0 Constant Bit Rate Extension

DOCSIS 1.0 MAC Driver

DOCSIS 1.0 Quality of Service Support

DOCSIS 1.0 Payload Header Suppression

DOCSIS 1.0 per SID Bandwidth Request and Grant Counters

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

For additional information about configuring DOCSIS QoS and other DOCSIS features, refer to the DOCSIS 1.1 Feature Module for the Cisco uBR7200 Routers on Cisco.com, and to other documents cited for DOCSIS 1.0 features below.


Caution All DOCSIS 1.0 extensions are activated only when a CM or equivalent device that supports these extensions solicits services using dynamic MAC messages. If the CMs in your network are all DOCSIS 1.0-based, they receive regular DOCSIS 1.0 treatment from the CMTS.

DOCSIS 1.0 Baseline Privacy Interface

The Cisco uBR10012 router supports full DOCSIS 1.0 Baseline Privacy Interface (BPI) specifications. The BPI for DOCSIS 1.0 protects user data privacy across the shared-medium cable network and prevents unauthorized access to DOCSIS-based data transport services across the cable network. BPI encrypts traffic across the RF interface between the CM and CMTS, and includes authentication, authorization, and accounting (AAA) features.

The level of data privacy is roughly equivalent to that provided by dedicated line network access services such as analog modems or digital subscriber lines (DSL). BPI provides basic protection of service, ensuring that a CM, uniquely identified by its MAC address, can obtain keying material for services only when it is authorized to access them.


Note Encryption and decryption are subject to export licensing controls.


BPI supports access control lists (ACLs), tunnels, filtering, protection against spoofing, and commands to configure source IP filtering on RF subnets to prevent subscribers from using source IP addresses that are not valid.


Note To conform with a recent change in the DOCSIS 1.0 Baseline Privacy Interface (BPI) Specification, Cisco IOS Release 12.2(8)BC1 and later releases require that the Baseline Privacy Configuration Settings Option (Type 17) must be included in the DOCSIS configuration file for all DOCSIS 1.0 cable modems attempting to register for BPI encryption. If the type 17 option is not included, an "Unauthorized SAID" warning will appear in the CMTS console, and the cable modem will not be allowed to come online.

Previous Cisco IOS releases allowed DOCSIS 1.0 cable modems to register for BPI encryption and to come online, even if the DOCSIS configuration file did not include the type 17 option. The change to the DOCSIS BPI specification, however, made the type 17 option mandatory for BPI operation.

For more information about this requirement, see the TAC technical note on Cisco.com at http://www.cisco.com/warp/public/109/bpi_changes_23895.html.


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 Even when DOCSIS 1.0 concatenation is disabled with this feature, concatenation remains enabled for cable modems that are compliant with DOCSIS 1.1 or DOCSIS 2.0.


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 docsis10
 
   

In 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 Guide on Cisco.com:

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

DOCSIS 1.0 Configuration File Settings

Refer to these sections for additional information about DOCSIS configuration files:

"DOCSIS 1.0 Constant Bit Rate Extension" section

"DOCSIS 1.0 Traffic Shaping and Rate Limiting Features" section

"DOCSIS 1.1 Subscriber Management" section

For additional information about configuring DOCSIS QoS and other DOCSIS features, refer to the DOCSIS 1.1 Feature Module for the Cisco uBR7200 Routers on Cisco.com and to other documents cited below.

DOCSIS 1.0 Constant Bit Rate Extension

This DOCSIS 1.0 extension enables better processing of higher-priority traffic; fields in the DOCSIS configuration file can be used so that when a CM requests a voice SID, the MAC scheduler on the Cisco uBR10012 router schedules fixed periodic slots on the upstream for that traffic flow. The CM does not have to contend for these slots and, because the Cisco uBR10012 router controls the timing of slots, it has precise control over potential delay and jitter.

DOCSIS 1.0 MAC Driver

This DOCSIS 1.0 driver supports CableLabs specifications for the MAC sublayer and associated interfaces. Refer to the "DOCSIS 1.0 MAC Enhancements to Improve Upstream per CM Data Throughput" section.

DOCSIS 1.0 Quality of Service Support

Cisco uBR10012 router software offers DOCSIS 1.0 Quality of Service (QoS) support. This allows you to define service levels in order to map data packets efficiently into traffic classes. These traffic classes determine how network resources are allocated and controlled. QoS can be delivered through a combined use of IP precedence ToS bits and QoS capabilities of IP and ATM core networks.

Cisco uBR10012 router software supports varying QoS definitions for differentiated services:

Guaranteed-rate service queue to store bandwidth requests from CMs subscribing to a class with minimum upstream rate on the upstream channel.

Best-effort service queue to store bandwidth requests from CMs subscribing to a class with no minimum upstream rate on the upstream channel.

Service priority of 7 to 0; a higher value indicates better service.

Maximum allowed upstream rate in bps.

Maximum upstream channel burst in minislots.

Minimum reserved upstream rate in bps.

Maximum allowed downstream rate in bps.

Additional information about the capabilities and configuration of DOCSIS QoS are described the following documents:

DOCSIS 1.1 Feature Module for the Cisco uBR7200 Routers

Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2

Cisco IOS Quality of Service Solutions Command Reference, Release 12.2

DOCSIS 1.0 MAC Enhancements to Improve Upstream per CM Data Throughput

DOCSIS 1.0 supports tiered best-effort and CIR-type service. The Cisco uBR10012 router and CMTS now support a mechanism to dynamically initiate and terminate MAC-level scheduling for high-priority traffic, and to specify exactly what QoS parameters to use.

In DOCSIS 1.0, the CM explicitly requests upstream bandwidth—either in contention or piggyback to grant minislots—for every single packet it wants to send upstream. This limits the maximum upstream data throughput that a CM can receive due to the inherent "request to grant" round-trip latency each packet incurs on the cable system. To support this per-cable-modem upstream throughput increase, the Cisco uBR10012 router software is enhanced. The CMTS can now receive a concatenated burst of multiple MAC frames from the same CM.


Note Both the CMTS and CM must support this capability.


DOCSIS 1.0 Downstream Rate Shaping with Type of Service (ToS)

This feature supports buffering downstream grants to rate-exceeding cable interfaces, without incurring TCP-related timeouts and retransmits. This feature uses the three precedence bits in the ToS field in the IP header to specify class of service assignment for each packet.

Those packets with the IP precedence bit set in the IP packet are given higher priority. This allows the CMTS administrator to calculate the data rate for a given flow, in addition to the data rate configured on a per CM basis.

IP Precedence-Based Downstream Rate Limits

DOCSIS 1.0 provides QoS, based on the SID. Each QoS profile carries a parameter maximum downstream rate, which is used to provide peak rate limiting and traffic shaping on the downstream. When higher-priority and traffic data are combined for a particular CM, rate-exceeded data packets might shut down or delay higher-priority packets, thereby degrading quality. IP precedence bits can be used as a basic differentiator to provide independent rate limits for different traffic streams.

DOCSIS 1.0 Downstream Signal Test Commands

The cable downstream if-output command provides several test capabilities and is enhanced with the following options to generate test signals on the downstream interface.

cable downstream if-output prbs—Shuts down the downstream interface and outputs a Pseudo-Random Bit Stream (PRBS) test signal.

cable downstream if-output continuous wave—Shuts down the downstream interface and outputs an unmodulated carrier signal.


Note The previous cable downstream if-output command has not changed and continues to output a standard modulated signal. The no cable downstream if-output command has not changed and stops all signal output and shuts down the interface.


For additional command information, refer to the Cisco Broadband Cable Command Reference Guide.

DOCSIS 1.0 Modem Power Enhancement Adjustments for Low SNR Failures

This feature allows Cisco uBR10012 router to adjust better when a CM seems to bounce—the CM requires frequent power adjustments in opposite directions. When this occurs, instead of making large power adjustments for each correction, the administrator can configure the Cisco uBR10012 router to calculate the average value of the power corrections before making power adjustments:

cable upstream power-adjust threshold—This command now accepts a range of 0 to 10 dB (the previous range was 0 to 2 dB).

cable upstream power-adjust noise % of power adjustment—This command sets the threshold value (in percent) for a particular upstream, switching between regular power adjustments and the noise power-adjustment method.

The noise power-adjustment method uses an averaging algorithm before sending any correction. For additional command information, refer to the Cisco Broadband Cable Command Reference Guide.

DOCSIS 1.0 Multi SID Support

This feature allows the Cisco uBR10012 router to support the definition of multiple SIDs on the upstream. This includes multiple service classes per cable interface, enabling administrators to delegate higher priority as required.

Higher-priority traffic can be designated on a higher QoS committed information rate (CIR) secondary SID, while data traffic can be forwarded on a best-effort basis on a primary SID.

Secondary SIDs can be defined to provide higher QoS CIR-type classes for higher-priority traffic. These classes have a nonzero minimum reserved rate (CIR-type service). These SIDs, therefore, receive preferential treatment at the CMTS for grants over any tiered best-effort type data SID for that upstream.


Note Best-effort service involves requests with no minimum upstream rate on the channel. The CMTS treats the primary and secondary SIDs independently for issuing grants. Each SID of a CM has an independent state machine. Channel access for each SID is independent of the other SID.


Cable-modem-initiated dynamic MAC messages—Dynamic Service Addition (DSA) and Dynamic Service Deletion (DSD). These messages allow dynamic SIDs to be created and deleted at run time.

Unsolicited grant service (CBR-scheduling) on the upstream helps provide a higher-quality channel for upstream packets from the Cisco uBR924 cable access router, for example.


Caution Reliable operation with higher-priority traffic requires multiple SIDs—at least two per cable interface to separate highest-priority traffic from data traffic. In DOCSIS 1.0, SIDs are set up statically. When supporting extensions to DOCSIS 1.0 or DOCSIS 1.1, SIDs can be set up either statically or dynamically. Both the CMTS and CM must support the feature set.

DOCSIS 1.0 QoS Profile Enforcement

QoS profile enforcement allows you to override the provisioned service class of a cable interface at the time of registration with a CMTS-defined QoS profile. When this feature is enabled, the CMTS provisions each registering CM with a default DOCSIS 1.0 service class, which the CMTS administrator configures.

The administrator-defined service class is enforced on CMs attempting to register with the CMTS. The service class has no upstream or downstream rate limits.

When the CM sends data upstream, it makes bandwidth requests without throttling or dropping packets because of its own rate-policing algorithm. The CMTS does traffic shaping based on the QoS profile enforced by the operator.


Note By default, the system does not enforce a specific QoS profile on the cable interface. The QoS profile assigned to the cable interface depends on the class of service parameters provisioned in the cable interface DOCSIS configuration file.


DOCSIS 1.0 RFC 2233 Support (RF Interface MIB)

The Cisco uBR10012 router supports DOCSIS OSSI Required Objects in RFC 2233.

DOCSIS 1.0 Service Class Profiles

The Cisco uBR10012 router allows you to create multiple service class profiles with the following characteristics:

A specific QoS profile number

Traffic priority (7, 6, 5, 4, 3, 2, 1, 0), with 7 being the highest

Maximum and guaranteed upstream rate in bps

Maximum upstream channel burst in minislot

Minimum upstream rate in bps

Maximum downstream rate in bps

Maximum transmit burst length

ToS overwrite byte

Using these service class profiles, you can define a guaranteed-rate service queue to store bandwidth requests from CMs subscribing to a class with minimum upstream rate on the upstream channel, and a best-effort service queue for CMs subscribing to a class with no minimum upstream rate on the upstream channel.

The Cisco uBR10012 router also supports multiple service classes per CM and dynamic service identifiers. This allows the Cisco uBR10012 router to dynamically allocate and delete service flows.

The CMTS also supports QoS profile enforcement to override interference from cable modems that might be improperly rate limited. The CMTS system administrator can assign a default DOCSIS 1.0 service class that overrides a pre-existing service class on the modem. The CMTS can do traffic shaping based on the QoS profile the administrator enforces.

DOCSIS 1.0 Traffic Shaping and Rate Limiting Features

Traffic shaping reduces the chance that information is retransmitted to hosts on the HFC network and, therefore, conserves bandwidth. Without traffic shaping, the Cisco IOS Release 12.2XF software drops bandwidth requests from CMs found to be exceeding their configured peak upstream transmission rate. Dropping bandwidth requests (and eventually upstream packets) from rate-exceeding cable interface causes TCP-related timeouts, which cause the host sending the information to retransmit its information.

The Cisco IOS Release 12.2XF supports the following traffic shaping features:

Downstream rate limiting—Allows downstream grants to rate-exceeding CMs to be buffered without incurring TCP-related timeouts and retransmits. Downstream rate shaping enables you to partition downstream traffic for a CM into multiple classes of service and multiple data rates by using the three precedence bits in the ToS byte in the IP header to specify a class of service assignment for each packet. Those packets with the precedence bit set in the ToS field are given higher priority.

Using the ToS byte, you can calculate the data rate for a specified flow, in addition to the data rate configured on a per-CM basis. By specifying a maximum data rate for a particular ToS, you can override the common maximum downstream data rate.


Note Packets that contain ToS bytes that have not been configured for downstream data rates continue to use the common data rate limits.


Upstream rate limiting—Allows upstream bandwidth requests from rate-exceeding CMs to be buffered without incurring TCP-related timeouts and retransmits. This enables the CMTS to enforce the peak upstream rate for each CM without degrading overall TCP performance for the subscriber CPEs. Upstream grant shaping is per cable interface (SID).

Token-bucket policing with shaping is the per-upstream default rate-limiting setting at the CMTS. Shaping can be enabled or disabled for the token-bucket algorithm.

Upstream traffic shaping delays the scheduling of an upstream packet, which causes the packet to be buffered on the cable CPE device instead of being dropped. This allows the TCP/IP stack to pace the application traffic appropriately and approach throughput commensurate with the subscriber's defined QoS levels.

DOCSIS 1.0 Payload Header Suppression

Payload Header Suppression (PHS) conserves link-layer bandwidth by suppressing unnecessary packet headers on both upstream and downstream traffic flows. For configuration information, refer to the "Configuring Payload Header Suppression and Restoration" section.

DOCSIS 1.0 per SID Bandwidth Request and Grant Counters

This feature promotes better control of higher-priority traffic, permitting per-SID bandwidth requests and grants. Profiles can be customized for scheduling parameters required at subscriber sites for the service offering.

The show interface cx/y/z sid counter command also supports a verbose option that displays:

Number of bandwidth requests successfully received by the Cisco uBR10012 router from the specified SID on the specified cable interface

Number of grants issued by the Cisco uBR10012 router to the specified SID

DOCSIS 1.0 ToS Overwrite

Cisco IOS release 12.3(17a)BC2 introduces support for the DOCSIS 1.0 Type of Service (ToS) Overwrite feature. 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.

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 QoS definitions must previously exist on the Cisco CMTS headend to support this feature.


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:

cable qos pro max-ds-burst burst-size

show cable qos profile n [verbose]

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

burst-size

The QoS profile's downstream burst size in bytes.


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 interval
  grant-size           Grant size
  guaranteed-upstream  Guaranteed Upstream
  max-burst            Max Upstream Tx Burst
  max-ds-burst        Max Downstream Tx burst (cisco specific) 
  max-downstream       Max Downstream
  max-upstream         Max Upstream
  name                 QoS Profile name string (cisco specific) 
  priority             Priority
  privacy              Cable Baseline Privacy Enable
tos-overwrite        Overwrite TOS byte by setting mask bits to value 
 
   

The 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 pro
ID  Prio Max       Guarantee Max        Max   TOS  TOS   Create  B     IP prec.
         upstream  upstream  downstream tx    mask value by      priv  rate
         bandwidth bandwidth bandwidth  burst                    enab  enab
1   0    0         0         0          0     0xFF 0x0   cmts(r) no    no
2   0    64000     0         1000000    0     0xFF 0x0   cmts(r) no    no
3   7    31200     31200     0          0     0xFF 0x0   cmts    yes   no
4   7    87200     87200     0          0     0xFF 0x0   cmts    yes   no
6   1    90000     0         90000      1522  0xFF 0x0   mgmt    yes   no
10  1    90000     0         90000      1522  0x1  0xA0  mgmt    no    no
50  0    0         0         96000      0     0xFF 0x0   mgmt    no    no
51  0    0         0         97000      0     0xFF 0x0   mgmt    no    no
  

The 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 ver
Profile Index                           10
Name
Upstream Traffic Priority               1
Upstream Maximum Rate (bps)             90000
Upstream Guaranteed Rate (bps)          0
Unsolicited Grant Size (bytes)          0
Unsolicited Grant Interval (usecs)      0
Upstream Maximum Transmit Burst (bytes) 1522
Downstreamam Maximum Transmit Burst (bytes) 100000
IP Type of Service Overwrite Mask       0x1
IP Type of Service Overwrite Value      0xA0
Downstream Maximum Rate (bps)           90000
Created By                              mgmt
Baseline Privacy Enabled                no

Usage 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)         = 1
 
   
04 (Class of Service Encodings Block)
   S01 (Class ID)               = 1
   S02 (Maximum DS rate)        = 90000
   S03 (Maximum US rate)        = 90000
   S06 (US burst)               = 1522
   S04 (US Channel Priority)    = 1
   S07 (Privacy Enable)         = 0
 
   

The 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 1-6 provides two examples of such QoS profiles for illustration:

Table 1-6 Sample QoS Profiles with Differing ERBA (Maximum Downstream) Settings

QoS Profile Setting
QoS Profile 101
QoS Profile 102

Maximum Downstream Transmit Burst (bytes)

max-burst 4000

max-burst 4000

Maximum Downstream Burst (bps)

max-ds-burst 20000

max-ds-burst 5000

Maximum Downstream Bandwidth

max-downstream 100

max-downstream 100


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 DOCSIS 1.0 Downstream Powerburst

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:

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Configuring DOCSIS 1.1 on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

DOCSIS 1.0+ Feature Support

In response to the limitations of DOCSIS 1.0 in handling real-time traffic, such as voice calls, Cisco created the DOCSIS 1.0+ extensions to provide the more important QoS enhancements that were expected in DOCSIS 1.1. In particular, the DOCSIS 1.0+ enhancements provide basic Voice-over IP (VoIP) service over the DOCSIS link.

Cisco DOCSIS 1.0+ extensions include the following DOCSIS 1.1 features:

Multiple SIDs per CM, creating separate service flows for voice and data traffic. This allows the CMTS and CM to give higher priority for voice traffic, preventing the data traffic from affecting the quality of the voice calls.

CM-initiated dynamic MAC messages—Dynamic Service Addition (DSA) and Dynamic Service Deletion (DSD). These messages allow dynamic SIDs to be created and deleted on demand so that the bandwidth required for a voice call can be allocated at the time a call is placed and then freed up for other uses when the call is over.

Unsolicited grant service (CBR-scheduling) on the upstream—This helps provide a higher-quality channel for upstream VoIP packets from an Integrated Telephony CM (ITCM) such as the Cisco uBR924 cable access router.

Ability to provide separate downstream rates for any given CM, based on the IP-precedence value in the packet—This helps separate voice signaling and data traffic that goes to the same ITCM to address rate shaping purposes.

Concatenation allows a CM to send several packets in one large burst, instead of having to make a separate grant request for each.


Caution All DOCSIS 1.0 extensions are available only when using a CM (such as the Cisco uBR924 cable access router) and CMTS (such as the Cisco uBR10012 router) that support these extensions. The CM activates the use of the extensions by sending a dynamic MAC message. DOCSIS 1.0 CMs continue to receive DOCSIS 1.0 treatment from the CMTS.

DOCSIS 1.1 Feature Support

DOCSIS 1.1 is the first major revision of the initial DOCSIS 1.0 standard for cable networks. Although the initial standard provided quality data traffic over the coaxial cable network, the demands of real-time traffic such as voice and video required many changes to the DOCSIS specification.


Note At the time of publication, the DOCSIS 1.1 specification is still being finalized. This document describes the DOCSIS 1.1 specification SP-RFIv1.1-IO3-991105. See the CableLabs Web site (http://www.cablelabs.com) for the current status on DOCSIS 1.1.


This section describes the major enhancements supported on the Cisco uBR10012 router:

DOCSIS 1.1 Baseline Privacy Interface Plus Features

DOCSIS BPI+ Multiple Root Certificate Support

DOCSIS 1.1 CM Compatibility

DOCSIS 1.1 CM Database Manager

DOCSIS 1.1 Concatenation Support

See also DOCSIS 1.0 Concatenation Override

DOCSIS 1.1 Customer Premises Equipment Configurator

DOCSIS 1.1 Downstream Packet Classifier

DOCSIS 1.1 Downstream Packet Scheduler

DOCSIS 1.1 Dynamic MAC Messages

DOCSIS 1.1 Enhanced Registration

DOCSIS 1.1 Fragmentation and Reassembly

DOCSIS 1.1 Layer 2 Fragmentation

DOCSIS 1.1 MAC Scheduler

DOCSIS 1.1 Payload Header Suppression and Restoration

DOCSIS 1.1 Quality of Service Support

DOCSIS 1.1 Rate Limiting and Traffic Shaping

DOCSIS 1.1 Service Flow Manager

DOCSIS 1.1 Service Template and Class Manager

DOCSIS 1.1 Software Infrastructure

DOCSIS 1.1 Subscriber Management

DOCSIS 1.1 Time Slot Scheduling

DOCSIS 1.1 TLV Parser and Encoder

DOCSIS 1.1 Token-Bucket Rate Shaping

DOCSIS 1.1 Two-Way Interoperability

Optional Upstream Scheduler Modes

DOCSIS 1.1 Baseline Privacy Interface Plus Features

DOCSIS 1.1 enhances the DOCSIS 1.0 BPI security features with BPI+, which includes the following features:

1024-bit public key with Pkcs#1 Version 2.0 encryption

Commands to configure source IP filtering on RF subnets to prevent subscribers from using source IP addresses that are not valid

Digital certificates that provide secure user identification and authentication

Filtering

IP security access control list (ACL) support

Key encryption that uses 168-bit Triple DES (3DES) encryption that is suitable for the most sensitive applications

Multicast support

Protection against spoofing

Secure software download allows a service provider to upgrade a CM's software remotely, without the threat of interception, interference, or alteration

Tunnels


Note BPI+ is described in the Baseline Privacy Interface Plus Specification (BPI+_I06-001215), available in PDF format from CableLabs (http://www.cablemodem.com).


Additional Information

For additional information about the differences in DOCSIS specifications, refer to DOCSIS 1.1 for Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com.

40-bit and 56-bit Baseline Privacy Data Encryption Standard (DES)

The Cisco uBR10012 router supports 40-bit and 56-bit encryption and decryption. When encryption and decryption is enabled, 56-bit is the default. If necessary, administrators can force the Cisco uBR10012 router to generate a 40-bit DES key, where the DES key that is generated and returned masks the first 16 bits of the 56-bit key to zero in software.


Note BPI+ encryption and authentication must be supported and enabled by both the CM and CMTS. In addition, the CM must contain a digital certificate that conforms to the DOCSIS 1.1 and BPI+ specifications.


Access Lists (Per-Modem and Per-Host)

Per-modem and per-host access lists allow the Cisco uBR10012 router to filter incoming packets from individual hosts or cable interfaces based on the source MAC or IP address. This allows access lists to be specified on a per-interface or a per-address basis.

You can preconfigure the filters by using the CLI, following standard Cisco IOS access list and access group configuration procedures. You can assign these filters to a user or modem by using the CLI or SNMP. The feature also supports traps to inform the CMTS about the online or offline status of modems.

Access Lists on the Cisco uBR10012 Router

The Parallel eXpress Forwarding (PXF) processors on the Cisco uBR10012 router provide the increased performance of Turbo Access Control Lists (Turbo ACL) by default by automatically compiling all access lists when access lists are configured.

You do not need to use the access-list compiled command to enable the Turbo ACL feature. To display access lists, use the show access-lists command without specifying the compiled option.

For complete information about access lists, see the "Traffic Filtering and Firewall" volume in the Cisco IOS Release 12.1 Security Configuration Guide at the following URL:

http://www.cisco.com/en/US/docs/ios/12_1/security/configuration/guide/scdacls.html

Authentication

DOCSIS 1.1 offers advanced authentication and security through X.509 digital certificates and Triple Data Encryption Standard (3DES) key encryption.

Cisco IOS Firewall

The Cisco uBR10012 router support Network Address Translation (NAT) and firewall functionality. Additional NAT documentation is available online at http://www.Cisco.com.

CM and Host Subnet Addressing

This feature enables the Cisco uBR10012 router to manipulate the GIADDR field of DHCPDISCOVER and DHCPREQUEST packets with a Relay IP address before they are forwarded to the DHCP server. By modifying the GIADDR field based on whether the source is a CM or a host, the Cisco uBR10012 router provides hints to the DHCP server as to where—on which IP subnet—the server should allocate addresses to the requesting client.

Upstream Address Verification

This feature prevents the spoofing of IP addresses. Using the CLI, administrators can determine the IP and MAC address of a given cable interface, and the SID number that shows the IP and MAC addresses of all devices learned in the cable interface's MAC table.

The CMTS verifies the source IP address against the MAC address for the CM. CM and PC IP addresses are verified to ensure that SID and MAC addresses are consistent. A PC behind a cable interface is assigned an IP address from the DHCP server. If a user on a second PC or cable interface statically assigns the same IP address to a PC, the Cisco uBR10012 router reports this. Using customer databases, administrators can cross-reference the spoofing CM and PC to prevent further usage.


Note The cable source-verify [dhcp] command (for cable interfaces) specifies that DHCP lease query requests are sent to verify any unknown source IP address found in upstream data packets. Upstream Address Verification requires a DHCP server that supports the new LEASEQUERY message type. Cisco Network Registrar supports the LEASEQUERY message type in Cisco IOS Release 3.01(T) and later releases.


For configuration information, refer to Chapter 4 "Managing Cable Modems on the Hybrid Fiber-Coaxial Network".

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:

In circumstances in which it is necessary to change from North American root certificates to European root certificates, or vice versa, it is necessary to over write the existing root certificate on the Cisco CMTS, and to reload the Cisco CMTS with the reload or restart command.

The Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE) supports both North American and European root certificates at the same time, and simultaneous root certificate support is a requirement in this case.

DOCSIS 1.1 CM Compatibility

DOCSIS 1.1 CMs can coexist with DOCSIS 1.0 and 1.0+ CMs in the same network—the Cisco uBR10012 router provides the levels of service that are appropriate for each CM. For additional configuration information, refer to Chapter 3 "Configuring Cable Interface Features for the Cisco uBR10012 Router."

DOCSIS 1.1 CM Database Manager

The CM Database Manager is a new software module that manages CM information on the CMTS. This module can be queried to obtain different types of information on a single CM (or a group of CMs). Using the show cable modem command, information maintained on a per-CM basis includes DOCSIS MAC capabilities, counters, errors, QoS configuration, MAC state, connectivity statistics, and so forth.

Command
Purpose

show cable modem [ip-address | interface | mac-address] [options]

Displays information for the registered and unregistered CMs.


Syntax Description

ip-address

Identifies the IP address of a specific modem to be displayed.

interface

Displays all CMs on a specific CMTS cable interface.

mac-address

Identifies the MAC address of a specific CM to be displayed.


Several additional command options are available. Refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

Examples

Router# show cable modem
MAC Address    IP Address      I/F       MAC         Prim RxPwr Timing Num  BPI
                                         State       Sid  (db)  Offset CPEs Enbld
0050.04f9.edf6 10.44.51.49     C7/1/0/U0 online      1   -0.50  3757   0    no
0050.04f9.efa0 10.44.51.48     C7/1/0/U0 online      2   -0.50  3757   0    no
0030.d002.41f5 10.44.51.147    C7/1/0/U0 online      3   -0.25  3829   0    no
0030.d002.4177 10.44.51.106    C7/1/0/U0 online      4   -0.50  3798   0    no
0030.d002.3f03 10.44.51.145    C7/1/0/U0 online      5   0.25   3827   0    no
0050.04f9.ee24 10.44.51.45     C7/1/0/U0 online      6   -1.00  3757   0    no
0030.d002.3efd 10.44.51.143    C7/1/0/U0 online      7   -0.25  3827   0    no
0030.d002.41f7 10.44.51.140    C7/1/0/U0 online      8   0.00   3814   0    no
0050.04f9.eb82 10.44.51.53     C7/1/0/U0 online      9   -0.50  3756   0    no
0050.f112.3327 10.44.51.154    C7/1/0/U0 online      10  0.25   3792   0    no
0030.d002.3f8f 10.44.51.141    C7/1/0/U0 online      11  0.00   3806   0    no
0001.64f9.1fb9 10.44.51.55     C7/1/0/U0 online      12  0.00   4483   0    no
0030.d002.417b 10.44.51.146    C7/1/0/U0 online      13  0.50   3812   0    no
0090.9600.6f7d 10.44.51.73     C7/1/0/U0 online      14  0.00   4071   0    no
0010.9501.ccbb 10.44.51.123    C7/1/0/U0 online      15  0.25   3691   0    no
 
   

DOCSIS 1.1 Concatenation Support

Concatenation allows the CM to make a single time slice request for multiple packets and send all packets in a single large burst on the upstream. This is in contrast to making an individual grant request for each frame. Concatenation was introduced in the upstream receive driver in the DOCSIS1.0+ releases. Per-SID counters have now been added in Cisco IOS Release 12.2XF for debugging concatenation activity.

Also see the "DOCSIS 1.0 Concatenation Override" section.

The combination of multiple upstream packets into one packet reduces packet overhead and overall latency, and increases transmission efficiency. Using concatenation, a CM needs to make only one bandwidth request for a concatenated packet, as opposed to making a different bandwidth request for each packet. This technique is particularly effective for real-time traffic.


Tip Concatenation is supported only with CMs that support DOCSIS concatenation as part of DOCSIS 1.0 extensions. The results of the show controller command indicate whether concatenation is enabled on an interface.

Concatenation is enabled by default for current cable interface line cards, but can be disabled with the Cisco IOS no cable upstream number concatenation interface command. A CM is considered noncompliant when it concatenates after the Cisco IOS no cable upstream number concatenation interface command is issued.


Commands

Router# show interface cable x/y sid [n] counters [verbose] 
Router# show controller cable x/y 
Router(config-if)# [no] cable upstream n concatenation 
Router# debug cable errors 
 
   

For additional configuration information, refer to the DOCSIS 1.1 for Cisco uBR7200 Series Universal Broadband Routers on Cisco.com.

DOCSIS 1.1 Customer Premises Equipment Configurator

Cisco offers an HTML-based DOCSIS 1.1 CPE Configurator tool—described and accessed from http://www.cisco.com/en/US/products/index.html. The tool is designed to collect information needed to generate a DOCSIS 1.1 CM configuration file. The generated file is in binary format consistent with the DOCSIS RF Specification (SP-RFI-105-991105) at http://www.cablelabs.com/cablemodem/specifications/.

DOCSIS 1.1 Downstream Packet Classifier

Packet classifiers help to map packets into DOCSIS service flows. The CMTS supports downstream IP packet classifiers.

Commands

Router# show interface cable x/y classifier
Router# show interface cable x/y service-flow [n] classifiers
Router# debug cable qos
 
   

For additional command information, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

DOCSIS 1.1 Downstream Packet Scheduler

The Downstream Packet Scheduler is a new module that controls all output packet queueing service on the downstream link of each cable interface.

Commands

Router# debug cable qos
Router# show interface cable x/y downstream
 
   

For additional command information, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

DOCSIS 1.1 Dynamic MAC Messages

DSX MAC messages allow dynamic signaling of QoS between the CM and the CMTS. These messages are DOCSIS link layer equivalents of higher-layer create, modify, and teardown messages. The DSX state machine module on the CMTS manages the several concurrent dynamic service transactions between CMs and the CMTS. It include state machine support for all 3 DOCSIS1.1 dynamic MAC messages (DSX messages):

Dynamic Service Add (DSA): This message is used to create a new service flow.

Dynamic Service Change (DSC): This message is used to change the attributes of an existing service flow.

Dynamic Service Deletion (DSD): This message is used to delete an existing service flow.

Commands

Router# debug cable dynsrv
Router# debug cable tlvs
 
   

For additional command information, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.


Note In Cisco IOS Release 12.1(4)CX, only cable-modem-initiated DSX messages are supported. CMTS-initiated DSX messages are not supported.


DOCSIS 1.1 Enhanced Registration

The registration module has been enhanced to support multiple registration styles (DOCSIS1.0/DOCSIS1.0+/DOCSIS1.1) in seamless fashion. Besides using services of the new Tag-Length-Value parser and encoder, this module also supports the conditional registration-acknowledgment MAC message state machine.

Commands

Router# debug cable registration
Router# debug cable tlvs
 
   

For additional command information, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

DOCSIS 1.1 Fragmentation and Reassembly

The MAC scheduler fragments data slots to fill the gaps in-between Unsolicited Grant Service (UGS) slots. Fragmentation reduces the jitter experienced by voice packets when large data packets are transmitted on the shared upstream channel and preempt the UGS slots used for voice. Fragmentation splits the large data packets so that they fit into the smaller timeslots available around the UGS slots. The grant fragmentation gets triggered in the MAC scheduler, and fragment reassembly happens in the upstream receive driver.


Note DOCSIS fragmentation should not be confused with the fragmentation of IP packets, which is done to fit the packets on network segments with smaller maximum transmission unit (MTU) size. DOCSIS fragmentation is Layer 2 fragmentation that is primarily concerned with efficiently transmitting lower-priority packets without interfering with high-priority real-time traffic, such as voice calls. IP fragmentation is done at Layer 3 and is primarily intended to accommodate routers that use different maximum packet sizes.


Commands

Router# show interface cable x/y sid [n] counters [verbose] 
Router(config-if)# [no] cable upstream n fragmentation
Router# debug cable errors	
 
   

DOCSIS 1.1 Layer 2 Fragmentation

Layer 2 fragmentation on the upstream prevents large data packets from affecting real-time traffic, such as voice and video. Large data packets are fragmented and then transmitted in the time slots that are available between the time slots used for the real-time traffic.

DOCSIS 1.1 MAC Scheduler

The MAC scheduler controls all time-slot assignment on the shared upstream channel. This block has been redesigned to support several new scheduling disciplines of DOCSIS1.1. Important enhancements include:

Support for grant fragmentation.

Support for multiple unsolicited grants per service ID (SID).

Support for Unsolicited Grant Service with Activity Detection (UGS-AD) and Real-Time Polling Service (RTPS) slot scheduling mechanisms besides Unsolicited Grant Service (UGS), best effort (BE), and Committed Information Rate (CIR) service of DOCSIS1.0+.

Enhanced per SID minimum or maximum rate shaping.

All old Cisco features, such as dynamic contention control are supported in the new design.

MAC Scheduler Commands

Router# show interface cable x/y mac-scheduler n 
Router(config-if)# [no] cable upstream n fragmentation 
Router(config-if)# [no] cable upstream n unfrag-slot-jitter 
Router# cable service flow inactivity-threshold n 
Router# debug cable mac-scheduler 
 
   

DOCSIS 1.1 Payload Header Suppression and Restoration

The Payload Header Suppression (PHS) feature is used to suppress repetitive or redundant portions in packet headers before transmission on the DOCSIS link. This is a new feature in the DOCSIS1.1 MAC driver. The upstream receive driver is now capable of restoring headers suppressed by CMs, and the downstream driver is capable of suppressing specific fields in packet headers before forwarding frames to the CM.

Commands

Router# show interface cable x/0 service-flow [sfid] phs 
Router# debug cable error 
Router# debug cable phs 
 
   

For additional command information, refer to the Cisco Broadband Cable Command Reference Guide on Cisco.com.

DOCSIS 1.1 Quality of Service Support

Enhanced quality of service (QoS) gives priority for real-time traffic such as voice and video.

The DOCSIS 1.0 QoS model (a service ID (SID) associated with a QoS profile) has been replaced with a service flow model that allows greater flexibility in assigning QoS parameters to different types of traffic and in responding to changing bandwidth conditions.

DOCSIS 1.1 offers support for multiple service flows per CM, which allows a single CM to support a combination of data, voice, and video traffic.

DOCSIS 1.1 offers greater granularity in QoS per CM in either direction, using unidirectional service flows.

Dynamic MAC messages create, modify, and delete traffic service flows to support on-demand traffic requests

Supported QoS models for the upstream are:

Best-effort—Data traffic sent on a non-guaranteed best-effort basis

Committed Information Rate (CIR)—Guaranteed minimum bandwidth for data traffic

Unsolicited Grants (UGS)—Constant bit rate (CBR) traffic, such as voice, that is characterized by fixed size packets at fixed intervals

Real-Time Polling (RTPS)—Real-time service flows, such as video, that produce unicast, variable-size packets at fixed intervals

Unsolicited Grants with Activity Detection (USG-AD)—Combination of UGS and RTPS, to accommodate real-time traffic that might have periods of inactivity (such as voice using silence suppression). The service flow uses UGS fixed grants while active, but switches to RTPS polling during periods of inactivity, to avoid wasting unused bandwidth.

The DOCSIS 1.1 QoS framework is based on the following objects:

Service class—A collection of settings maintained by the CMTS that provide a specific QoS service tier to a CM that has been assigned a service flow within a particular service class.

Service flow—A unidirectional sequence of packets receiving a service class on the DOCSIS link.

Packet classifier—A set of packet header fields used to classify packets onto a service flow to which the classifier belongs.

PHS rule—A set of packet header fields that are suppressed by the sending entity before transmitting on the link and that are restored by receiving entity after receiving a header-suppressed frame transmission. Payload Header Suppression increases the bandwidth efficiency by removing repeated packet headers before transmission.

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 CM and CMTS. A service flow is characterized by a set of QoS parameters such as latency, jitter, and throughput assurances.

Every CM establishes a primary service flow in both the upstream and downstream directions. The primary flows maintain connectivity between the CM and CMTS at all times.

In addition, a DOCSIS 1.1 CM can establish multiple secondary service flows. The secondary service flows either can be created permanently (they persist until the CM is reset or powered off) or 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.

Figure 1-3 illustrates the mapping of packet classifiers.


Note By default, the system does not enforce any specific QoS profile on the CM. The QoS profile assigned to the CM depends on the class of service parameters provisioned in the CM's DOCSIS configuration file.


Figure 1-3 Classification Within the MAC Layer

DOCSIS 1.1 Type of Service Overwrite

This feature allows you to overwrite the ToS byte in the IP datagrams received on the upstream before forwarding them downstream.

DOCSIS 1.1 Rate Limiting and Traffic Shaping

Cisco IOS Release 12.2XF software supports rate limiting per DOCSIS-1.0-99, which limits the data rate to and from a CM; the MAC scheduler supports traffic-shaping capabilities for downstream and upstream traffic.

Rate limiting ensures that no single CM consumes all of the channel bandwidth and allows a CMTS administrator to configure different maximum data rates for different subscribers. Subscribers requiring higher peak rates and willing to pay for this can be configured with higher peak rate limits in their CM DOCSIS configuration file over regular subscribers who pay less and get lower rate limits.

Each time a packet belonging to a flow is transmitted on an output channel, the token-bucket policer function checks the rate limit status of the flow, passing the following parameters:

Token-bucket peak rate in bits/msec.

Token-bucket depth (maximum transmit burst) in bits.

Length of current packet to be sent in bits.

Pointer to the flow's token bucket.

Pointer to the flow's token bucket last update time stamp.

Variable to return the msec buffering delay in case the packet needs to be shaped.

Maximum buffering delay that the subsequent traffic shaper can handle in msecs.

Every flow has its own shaping buffer where rate-exceeded packets are typically held back in first-in, first-out (FIFO) order for later transmission.

When rate-limiting CMs are implemented on the network, the Cisco IOS Release 12.2XF software typically drops packets to enforce the rate limit. Dropping packets from the requesting CM causes the host sending the information to retransmit its information. Retransmitted information wastes bandwidth on the network. If both hosts sending and requesting information are on the cable plant, the upstream bandwidth is wasted as well.

The traffic shaping feature delays the scheduling of the upstream packet, which in turn causes the packet to be buffered on the cable CPE device, instead of being dropped. This allows the user TCP/IP stack to pace the application traffic appropriately and approach throughput commensurate with the subscriber's defined QoS levels.

The Cisco uBR10012 router supports the following traffic shaping feature:

Downstream rate shaping to include ToS—Allows traffic shaping from the CMTS on a DOCSIS downstream channel. The feature allows administrators to configure the ToS byte to calculate the data rate for a specified flow. You can override the common maximum downstream data rate.

For additional information about downstream rate limiting (shaping), refer to the "Setting Downstream Rate Limiting and Traffic Shaping" section.


Tip Packets that contain ToS bytes that have not been configured for downstream data rates continue to use the common data rate limits.


Upstream rate shaping—Allows upstream rate shaping from the CMTS on a DOCSIS upstream channel. Upstream grant shaping is per CM (SID). The grant shaping feature is a configurable option for the current upstream token-bucket rate-limiting algorithm.

For configuration information, refer to the "Setting Upstream Rate Limiting and Traffic Shaping" section.


Tip Token-bucket policing with shaping is the new per-upstream default rate limiting setting at the CMTS. Shaping can be enabled or disabled for the token-bucket algorithm.


Restricted QoS class assignment—Allows a CMTS administrator to override the class of service provisioned for a CM. When this feature is enabled, the user-defined QoS profile is enforced on the CM attempting to register with the CMTS, regardless of the provisioned class of service.

For additional information about configuring DOCSIS QoS and other DOCSIS features, refer to the DOCSIS 1.1 Feature Module for the Cisco uBR7200 Routers, or to other documents cited below for DOCSIS features.


Tip This feature is added to address instances where a cable operator implemented rate limiting incorrectly. The feature allows an administrator to override the statically provisioned QoS parameters of the CM and force the CM to use a specific QoS profile defined at the CMTS.


DOCSIS 1.1 Service Flow Manager

The Service Flow Manager is a new module that manages different activities related to service flows on a cable interface. Typical events include the creation of new DOCSIS service flows, modification of the attributes of existing service flows, and the deletion of service flows.

Commands

Router# show interface cable x/y service-flow 
Router# debug cab qos
 
   

DOCSIS 1.1 Service Template and Class Manager

The Service Template and Class Manager is a software module that controls the creation, updating, and cleanup of various QoS service templates and user-defined service classes on the CMTS.

Commands

Router# show cable service-class 
Router(config)# cable service class n
Router# debug cable qos
 
   

DOCSIS 1.1 Software Infrastructure

Supports CableLabs specifications for high-speed Data-over-Cable systems involving the following categories:

RF interfaces between the Cisco uBR10012 router and the cable network—Downstream and upstream traffic.

Data interfaces for cable interfaces and CPE devices, as well as the CMTS network-side interface between the Cisco uBR10012 router and the data network.

Operations support interfaces—Network element management layer interfaces between the network elements and the operations support systems.

Secure software download allows a service provider to remotely upgrade a CM's software, without risk of interception or alteration.

DOCSIS 1.1 Subscriber Management

CMs are assigned to operate on specific cable channels to balance activity across several channels. Each Cisco uBR10012 router cable interface card serves a specific downstream channel and upstream segment. Part of network planning is to define the channels to use.

In typical cable networks, administrators limit the configuration responsibilities of field service technicians, and the amount of information collected on subscriber CPE devices. Field service technicians are sent to subscriber homes or businesses to install the CM or STB and ensure that all computing devices are DHCP-enabled.

The CMTS administrator defines and pushes DHCP and DOCSIS configuration files to appropriate servers so that each CM or CM in an STB on the network, when initialized, can transmit a DHCP request, receive its IP address, obtain its TFTP and ToD server addresses, and download its DOCSIS configuration file (and updated software image, if needed).

For additional information, refer to the Cisco Cable Modem Termination System Feature Guide on Cisco.com.

Connecting DOCSIS 1.0-Based CMs

DOCSIS 1.0-based CMs cannot connect to the broadband network until the following processes occur:

The CM initializes and ranges through available frequencies until it finds the first frequency that it can use to communicate to the CMTS—known as scanning for a downstream channel.

The CM obtains upstream parameters and performs ranging.

The CM goes through the DHCP server process and establishes IP connectivity, ToD, and security (optional). At this point, the CM cannot determine if it is communicating on the correct channel.

The CM receives a DOCSIS configuration file from the TFTP server. One of the parameters in the DOCSIS configuration file tells the CM which channel it can use.

The CM registers with the CMTS.

If the network supports DOCSIS BPI or other secure data sets, encryption/decryption processes are initialized.

The CM is ready for normal operations. Once initialized and operational, CMs send requests to initiate data transmission to the CMTS.

The CMTS system administrator or customer service representative ensures that appropriate databases are updated to activate and support the new subscriber account in the provisioning, billing, or network management systems in use for the network. Each CM or STB serial number and MAC address is typically stored in the billing and administrative system.

Initial and station maintenance management messages are sent to maintain communications between CMs and the CMTS. The following example displays CM reinitialization:

6d17h:580447.276 CMAC_LOG_DRIVER_INIT_IDB_RESET              0x080A2400
6d17h:580447.280 CMAC_LOG_LINK_DOWN                          
6d17h:580447.282 CMAC_LOG_RESET_FROM_DRIVER                  
6d17h:580447.284 CMAC_LOG_STATE_CHANGE
wait_for_link_up_state
6d17h:580447.286 CMAC_LOG_LINK_UP                            
6d17h:580447.290 CMAC_LOG_STATE_CHANGE
ds_channel_scanning_state
6d17h:580447.416 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
81/453000000/855000000/6000000
6d17h:580447.420 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
82/93000000/105000000/6000000
6d17h:580447.424 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
83/111025000/117025000/6000000
6d17h:580447.428 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
84/231012500/327012500/6000000
6d17h:580447.432 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
85/333025000/333025000/6000000
6d17h:580447.436 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
86/339012500/399012500/6000000
6d17h:580447.440 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
87/405000000/447000000/6000000
6d17h:580447.444 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
88/123012500/129012500/6000000
6d17h:580447.448 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
89/135012500/135012500/6000000
6d17h:580447.450 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
90/141000000/171000000/6000000
6d17h:580447.454 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
91/219000000/225000000/6000000
6d17h:580447.458 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
92/177000000/213000000/6000000
6d17h:580447.462 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
93/55752700/67753300/6000300
6d17h:580447.466 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
94/79753900/85754200/6000300
6d17h:580447.470 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
95/175758700/211760500/6000300
6d17h:580447.474 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
96/121756000/169758400/6000300
6d17h:580447.478 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
97/217760800/397769800/6000300
6d17h:580447.482 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
98/73753600/115755700/6000300
6d17h:580447.486 CMAC_LOG_WILL_SEARCH_DS_FREQUENCY_BAND
99/403770100/997799800/6000300
6d17h:580447.490 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY     501000000
6d17h:580447.492 CMAC_LOG_WILL_SEARCH_SAVED_DS_FREQUENCY     555000000
6d17h:%LINEPROTO-5-UPDOWN:Line protocol on Interface cable-modem0,
changed state to down
6d17h:580448.496 CMAC_LOG_UCD_MSG_RCVD                       1
6d17h:580448.500 CMAC_LOG_UCD_MSG_RCVD                       2
6d17h:580448.502 CMAC_LOG_UCD_MSG_RCVD                       3
6d17h:580448.504 CMAC_LOG_UCD_MSG_RCVD                       4
6d17h:580449.812 CMAC_LOG_DS_64QAM_LOCK_ACQUIRED             555000000
6d17h:580449.814 CMAC_LOG_DS_CHANNEL_SCAN_COMPLETED          
6d17h:580449.816 CMAC_LOG_STATE_CHANGE
wait_ucd_state
6d17h:580450.510 CMAC_LOG_UCD_MSG_RCVD                       1
6d17h:580450.512 CMAC_LOG_UCD_MSG_RCVD                       2
6d17h:580450.514 CMAC_LOG_UCD_MSG_RCVD                       3
6d17h:580450.518 CMAC_LOG_UCD_MSG_RCVD                       4
6d17h:580452.524 CMAC_LOG_UCD_MSG_RCVD                       1
6d17h:580452.528 CMAC_LOG_ALL_UCDS_FOUND                     
6d17h:580452.530 CMAC_LOG_STATE_CHANGE
wait_map_state
6d17h:580452.534 CMAC_LOG_UCD_NEW_US_FREQUENCY               19984000
6d17h:580452.536 CMAC_LOG_SLOT_SIZE_CHANGED                  8
6d17h:580452.616 CMAC_LOG_FOUND_US_CHANNEL                   4
6d17h:580452.618 CMAC_LOG_UCD_MSG_RCVD                       2
6d17h:580452.620 CMAC_LOG_UCD_MSG_RCVD                       3
6d17h:580452.624 CMAC_LOG_UCD_MSG_RCVD                       4
6d17h:580452.630 CMAC_LOG_MAP_MSG_RCVD                       
6d17h:580452.632 CMAC_LOG_INITIAL_RANGING_MINISLOTS          40
6d17h:580452.634 CMAC_LOG_STATE_CHANGE
ranging_1_state
6d17h:580452.636 CMAC_LOG_RANGING_OFFSET_SET_TO              9610
6d17h:580452.640 CMAC_LOG_POWER_LEVEL_IS                     28.0  dBmV
(commanded)
6d17h:580452.642 CMAC_LOG_STARTING_RANGING                   
6d17h:580452.644 CMAC_LOG_RANGING_BACKOFF_SET                0
6d17h:580452.648 CMAC_LOG_RNG_REQ_QUEUED                     0
6d17h:580452.690 CMAC_LOG_RNG_REQ_TRANSMITTED                
6d17h:580452.694 CMAC_LOG_RNG_RSP_MSG_RCVD                   
6d17h:580452.698 CMAC_LOG_RNG_RSP_SID_ASSIGNED               6
6d17h:580452.700 CMAC_LOG_ADJUST_RANGING_OFFSET              2291
6d17h:580452.702 CMAC_LOG_RANGING_OFFSET_SET_TO              11901
6d17h:580452.704 CMAC_LOG_ADJUST_TX_POWER                    9
6d17h:580452.706 CMAC_LOG_POWER_LEVEL_IS                     30.0  dBmV
(commanded)
6d17h:580452.710 CMAC_LOG_STATE_CHANGE
ranging_2_state
6d17h:580452.714 CMAC_LOG_RNG_REQ_QUEUED                     6
6d17h:580453.600 CMAC_LOG_RNG_REQ_TRANSMITTED                
6d17h:580453.604 CMAC_LOG_RNG_RSP_MSG_RCVD                   
6d17h:580453.606 CMAC_LOG_RANGING_SUCCESS                    
6d17h:580453.608 CMAC_LOG_STATE_CHANGE                       dhcp_state
6d17h:580453.742 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS           5.108.1.3
6d17h:580453.744 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS           128.1.1.2
6d17h:580453.746 CMAC_LOG_DHCP_TOD_SERVER_ADDRESS            128.1.1.2
6d17h:580453.750 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS           
6d17h:580453.752 CMAC_LOG_DHCP_TZ_OFFSET                     28800
6d17h:580453.754 CMAC_LOG_DHCP_CONFIG_FILE_NAME              gold.cm
6d17h:580453.756 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR  
6d17h:580453.760 CMAC_LOG_DHCP_COMPLETE                      
6d17h:580453.884 CMAC_LOG_STATE_CHANGE
establish_tod_state
6d17h:580453.890 CMAC_LOG_TOD_REQUEST_SENT                   
6d17h:580453.904 CMAC_LOG_TOD_REPLY_RECEIVED                 3165851032
6d17h:580453.910 CMAC_LOG_TOD_COMPLETE                       
6d17h:580453.912 CMAC_LOG_STATE_CHANGE
security_association_state
6d17h:580453.916 CMAC_LOG_SECURITY_BYPASSED                  
6d17h:580453.918 CMAC_LOG_STATE_CHANGE
configuration_file_state
6d17h:580453.920 CMAC_LOG_LOADING_CONFIG_FILE                gold.cm
6d17h:%LINEPROTO-5-UPDOWN:Line protocol on Interface cable-modem0,
changed state to up
6d17h:580454.950 CMAC_LOG_CONFIG_FILE_PROCESS_COMPLETE       
6d17h:580454.952 CMAC_LOG_STATE_CHANGE
registration_state
6d17h:580454.956 CMAC_LOG_REG_REQ_MSG_QUEUED                 
6d17h:580454.960 CMAC_LOG_REG_REQ_TRANSMITTED                
6d17h:580454.964 CMAC_LOG_REG_RSP_MSG_RCVD                   
6d17h:580454.966 CMAC_LOG_COS_ASSIGNED_SID                   1/6
6d17h:580454.970 CMAC_LOG_RNG_REQ_QUEUED                     6
6d17h:580454.976 CMAC_LOG_REGISTRATION_OK                    
6d17h:580454.978 CMAC_LOG_STATE_CHANGE
establish_privacy_state
6d17h:580454.980 CMAC_LOG_PRIVACY_NOT_CONFIGURED
6d17h:580454.982 CMAC_LOG_STATE_CHANGE
maintenance_state
 
   

DOCSIS 1.1 Time Slot Scheduling

Enhanced time-slot scheduling mechanisms to support guaranteed delay- or jitter-sensitive traffic on the shared multiple access upstream link. For additional information, refer to the document titled
TCC+ Card for the Cisco uBR10000 Series Router on Cisco.com and the Documentation CD-ROM.

DOCSIS 1.1 TLV Parser and Encoder

The Type-Length-Value (TLV) parser and encoder is a new module that handles parsing and encoding TLVs on the CMTS. All old DOCSIS1.0/1.0+ TLVs are supported. In addition, many new TLVs have been added in DOCSIS1.1, such as service flow encodings, classifier encodings, and support for PHS rules. The new TLV parser features are used by different MAC message modules.

Commands

Router# debug cable tlvs 
 
   

DOCSIS 1.1 Token-Bucket Rate Shaping

Each time a packet belonging to a flow is transmitted on an output channel, the token-bucket policing function checks the rate limit status of the flow, passing information about a number of parameters. For configuration information, refer to one of these two sections:

"Setting Downstream Rate Limiting and Traffic Shaping" section

"Setting Upstream Rate Limiting and Traffic Shaping" section

DOCSIS 1.1 Two-Way Interoperability

The Cisco uBR10012 router offers interoperability with DOCSIS-based two-way CMs, Cisco cable access routers such as the Cisco uBR924 or Cisco uBR904, or Cisco uBR910 series cable data service units (DSUs). For additional information, refer to Chapter 1 "Configuring Basic Broadband Internet Access."

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

To ensure proper operation, Call Admission Control (CAC) must be enabled. When the Low Latency Queueing (LLQ) option is enabled, it is possible for the upstream path to be filled with so many calls that it becomes unusable, making voice quality unacceptable. CAC must be used to limit the number of calls to ensure acceptable voice quality, as well as to ensure traffic other than voice traffic.

Even if CAC is not enabled, the default (DOCSIS) scheduling mode blocks traffic after a certain number of calls.

Unsolicited Grant Services with Activity Detection (UGS-AD) and Non Real Time Polling Service (nrtPS) are not supported.

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:

Cisco CMTS Feature Guide — Configuring Upstream Scheduler Modes on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_schd.html

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

High Availability Features

Several powerful High Availability features are supported on the Cisco uBR10012 router:

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Backup Path Testing for the Cisco RF Switch

DSX Messages and Synchronized PHS Information

Factory-Configured HCCP N+1 Redundancy

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

HCCP N+1 Redundancy Supporting DOCSIS 1.1 for the Cisco CMTS

HCCP Timing and Error Enhancements in HCCP Redundancy Show Commands

High Availability Support for Encrypted IP Multicast

Shutdown and No Shutdown Enhancement for Cable Interfaces

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:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.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:

"N+1 Redundancy on the Cisco CMTS" chapter in the Cisco Cable Modem Termination System Feature Guide:

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.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:

Route Processor Redundancy Plus (RPR+), with Active and Standby Performance Routing Engines (PREs)

HCCP N+1 Redundancy, with Working and Protect cable interface line cards

For additional information about these enhancements, and related High Availability features, refer to the following documents on Cisco.com:

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Route Processor Redundancy Plus for the Cisco uBR10012 Router

http://www.cisco.com/en/US/docs/cable/cmts/feature/u10krprp.html

Factory-Configured HCCP N+1 Redundancy

Cisco IOS release 12.3(13a)BC introduces factory-configured HCCP configurations at the command-line interface (CLI) that allow plug-and-play operation of the Cisco RF switch in 7+1 HCCP Redundancy configuration. This Cisco IOS release supports additional HCCP commands in global configuration mode that automatically generate bitmaps and interface configuration for HCCP 7+1 line-card level redundancy.

For users in which maximum power is required, Cisco IOS Release 12.3(13a)BC continues to support configurations supported in prior Cisco IOS Releases, making it possible to use the legacy HCCP configuration for both 7+1 and 4+1 HCCP Redundancy in interface level implementation.

For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

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:

7+1 Redundancy, supporting the Cisco uBR10012 router with two Cisco RF Switches

In this configuration, seven Working cable interface line cards are supported by one Protect cable interface l ine 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.

4+1 Redundancy, supporting the Cisco uBR10012 router with one Cisco RF Switch

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 N+1 Redundancy requires that all BPEs in the Cisco uBR10012 router be the same. Only the Cisco uBR-MC5X20U/D BPE is supported.



Note Cisco IOS Release 12.3(17a)BC introduces simplified global configuration commands, supporting 4+1 or 7+1 Redundancy on the Cisco uBR10012 router. However, earlier configuration commands are not supported when Global-level N+1 Redundancy is configured on the Cisco uBR10012 router.


For additional information about HCCP 4+1 Redundancy, refer to the following document on Cisco.com:

N+1 Redundancy for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

HCCP N+1 Redundancy Supporting DOCSIS 1.1 for the Cisco CMTS

The N+1 Redundancy for the Cisco CMTS feature extends the existing HCCP 1+1 cable interface redundancy feature, where one cable interface is designated the working interface, and a second cable interface is the protect interface. The protect interface comes online only when the working interface fails.

The N+1 Redundancy feature allows a single cable interface to act as the protect interface for up to 7 cable interfaces in the Cisco uBR10012 router, thereby significantly reducing the cost of providing redundant operation. The cable interface connections are made through the Cisco uBR-RFSW RF Switch.


Note For complete information about the N+1 Redundancy feature, see the "N+1 Redundancy for the Cisco CMTS" chapter in the Cisco Cable Modem Termination System Feature Guide on Cisco.com.


HCCP Timing and Error Enhancements in HCCP Redundancy Show Commands

Cisco IOS release 12.3(13a)BC introduces enhanced information in show commands that support HCCP N+1 Redundancy on the Cisco CMTS. These commands allow you to check for synchronization history and errors between the HCCP Working and HCCP Protect cable interface line cards.

Cisco IOS Release 12.3(13a)BC introduces such enhancements to the following show commands:

show hccp error

show hccp group

For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

High Availability Support for Encrypted IP Multicast

Cisco IOS Release 12.3(17a)BC introduces support for IP Multicast streams during switchover events in a High Availability environment. This feature is supported for Route Processor Redundancy Plus (RPR+), N+1 Redundancy, and encrypted BPI+ streams.

For additional information about IP Multicast and High Availability, refer to these documents on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Dynamic Shared Secret for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdmic.html

IP Multicast in Cable Networks, White Paper

http://www.cisco.com/en/US/technologies/tk648/tk828/technologies_case_study0900aecd802e2ce2.html

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Route Processor Redundancy Plus for the Cisco uBR10012 Router

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html

Shutdown and No Shutdown Enhancement for Cable Interfaces

Cisco IOS release 12.3(13a)BC introduces a new behavior with the [no] shutdown interface configuration command. In HCCP N+1 Redundancy schemes, an interface that is shut down with the shutdown command does not create an HCCP Switchover event for the associated Working or Protect interface. Instead, cable modems go offline and return online when the no shutdown command is issued.

For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Intercept Features

The Cisco uBR10012 router supports several intercept features through multiple Cisco IOS release trains:

Access Control List Support for COPS Intercept

Basic Wiretap Support

Cable Monitor Enhancements

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

cable monitor Command

COPS TCP Support for the Cisco Cable Modem Termination System

Packet Intercept

PXF ARP Filter

PXF Divert Rate Limiting

Service Independent Intercept (SII) Support

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

acl-num

Alphanumeric identifier of up to 30 characters, beginning with a letter that identifies the ACL to apply to the current interface.

acl-name

Numeric identifier that identifies the access list to apply to the current interface. For standard access lists, the valid range is 1 to 99; for extended access lists, the valid range is 100 to 199.


Additional Information

Refer also the Service Independent Interceopt (SII) feature in this document. For additional information, refer to the following documents on Cisco.com:

Configuring COPS for RSVP, Cisco IOS Versions 12.2 and 12.3

http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfcops_ps1835_TSD_Products_Configuration_Guide_Chapter.html

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_white_paper09186a0080179138.shtml

Basic Wiretap Support

This operations feature provides a mechanism that enables capture of user-to-user traffic. The wiretap facility is based on the MAC address of the RF CPE device, so the wiretap facility can be used for either data or digitized higher-priority connections. The feature is controlled by the new interface command, cable intercept, which requires a MAC address, an IP address, and a Universal Data Protocol (UDP) port number as its parameters:

cable intercept [mac-address] ip-address udp-port

When activated, the Cisco uBR10012 router examines each packet for the desired MAC address. When a matching MAC address is found (for either the origination or destination endpoint), a copy of the packet is encapsulated into a UDP packet, which is then sent to the specified server at the given IP address and port.

For additional command information, refer to the Cisco CMTS IOS Cable Command Reference Guide on Cisco.com.

Cable Monitor Enhancements

Cisco IOS Release 12.3(17a)BC introduces the following enhancements to the cable monitor feature:

Access Control Lists are now supported on the Cisco uBR-MC5X20U/D and Cisco uBR-MC28U cable interface line cards

Unconditional downstream sniffing now enables downstream packets to be monitored, either for MAC or data packets. This enhancement supports both DOCSIS and Ethernet packet encapsulation.

For additional information about this enhancements to the cable monitor feature, refer to the following documents on Cisco.com:

Cable Monitor and Intercept Features on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.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 The cable monitor feature does not support access lists for intelligent cable interface line cards such as the Cisco MC28U or Cisco MC16U in the Cisco uBR7246VXR router, or any intelligent cable interface line card in the Cisco uBR10012 router.


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/0
Router(config-if)# cable monitor interface GigabitEthernet0/1
mac-address 000e.5cc8.fa5f
packet-type data ethernet
Router(config-if)# 
mac-address 000e.5cac.59f8
packet-type data ethernet
 
   

To display cable monitor configuration and status information, use the show interfaces command in Privileged EXEC mode:

Router# show interfaces cable 3/0 monitor
US/ Time Outbound  Flow     Flow Type      Flow  Packet MAC   MAC	Encap
DS  Stmp Interface Type     Identifier     Extn. Type   Extn. Type	Type
all  no    Gi0/1   mac-addr 000e.5cc8.fa5f yes   data   no     -	ethernet
all  no    Gi0/1   mac-addr 000e.5cac.59f8 yes   data   no     -	ethernet
 
   

To 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 monitor
US/ Time Outbound  Flow     Flow Type      Flow  Packet MAC   MAC	Encap
DS  Stmp Interface Type     Identifier     Extn. Type   Extn. Type	Type
all  no    Gi0/1   mac-addr 000e.5cc8.fa5f yes   data   no     -	ethernet
all  no    Gi0/1   mac-addr 000e.5cac.59f8 yes   data   no     -	ethernet
 
   
Router# show cable modem 000e.5cac.59f8  counters
MAC Address    US Packets   US Bytes   DS Packets   DS Bytes
000e.5cac.59f8 7537986      3828867645 7199188      3711248288
 
   
Router# show interfaces GigabitEthernet 0/1
GigabitEthernet0/1 is up, line protocol is up 
  Hardware is BCM1250 Internal MAC, address is 000e.d6bd.2001 (bia 000e.d6bd.2001)
  Description: ***Sonde_analyse_trafic***
  Internet address is 82.216.52.1/30
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is RJ45
  output flow-control is XON, input flow-control is XON
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:08, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/5/0 (size/max/drops/flushes); Total output drops:361
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     1094862 packets input, 70425672 bytes, 0 no buffer
     Received 0 broadcasts, 5 runts, 0 giants, 0 throttles
     0 input errors, 10 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 37 multicast, 0 pause input
     0 input packets with dribble condition detected
     188665 packets output, 29355747 bytes, 0 underruns       <<< 188665 packets
     0 output errors, 0 collisions, 6 interface resets
     0 babbles, 0 late collision, 0 deferred
     12 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out
 
   

When 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:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

cable monitor Command

Cisco IOS Release 12.2(4)XF supports the cable monitor command, which allows an external LAN packet analyzer or other server to monitor inbound and outbound data packets for specific types of traffic sent between the Cisco CMTS and the CMs on a cable interface. This feature enables the CMTS administrator to analyze traffic problems with customer data exchanges. For complete information on configuring and using this feature, see the "Cable Monitor for the Cisco CMTS" chapter in the Cisco Cable Modem Termination System Feature Guide on Cisco.com and the Documentation CD-ROM.

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 These two commands affect all TCP connections with all COPS servers.


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

x

This value specifies the markings with which COPS messages are transmitted. The following values are supported:

0-63—DSCP value ranging from 0-63.

af11—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)


Defaults

For messages transmitted by the Cisco router, the default DSCP value is 0.

For incoming connections to the Cisco router, by default, the COPS engine takes the DSCP value used by the COPS server that initiates the TCP connection.

Usage Guidelines

The cops ip dscp command allows the Cisco router to re-mark the COPS packets for either incoming or outbound connections.

This command affects all TCP connections with all COPS servers.

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 illustrates the cops ip dscp command with supported command variations:

Router(config)# cops ip dscp ?
 <0-63>   DSCP value 
 af11     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:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Configuring COPS for RSVP

http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfcops_ps1835_TSD_Products_Configuration_Guide_Chapter.html

COPS for RSVP

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t2/feature/guide/CopsRSVP.html

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

bytes

This is the TCP window size setting in bytes. This value can range from 516 to 65535 bytes.


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 64000 

The following example illustrates online help for this command:

Router(config)# cops tcp window-size ? 
 <516-65535>  Size in bytes 
 
   

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:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Configuring COPS for RSVP

http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfcops_ps1835_TSD_Products_Configuration_Guide_Chapter.html

COPS for RSVP

http://www.cisco.com/en/US/docs/ios/12_1t/12_1t2/feature/guide/CopsRSVP.html

Packet Intercept

This feature allows you to intercept cable network activities according to the interface MAC address.

To allow the CMTS to forward all traffic to and from a particular CM to a data collector located at particular User Datagram Protocol (UDP) port, use the cable intercept command in cable interface configuration mode. To deactivate this function, use the no form of this command.

cable intercept mac-address ip-address udp-port

no cable intercept mac-address

Syntax Description

mac-address

Specifies the MAC address.

ip-address

Specifies the IP address for the destination data collector.

udp-port

Specifies the destination UDP port number for the intercept stream at the data collector. Valid range is 0 to 65535.


For additional command information, refer to the Cisco CMTS IOS Cable Command Reference Guide on Cisco.com.

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

Cable ARP Filtering

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblarpfl.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

Cable ARP Filtering

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblarpfl.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:

Packet intercept on specified or unspecified interfaces or ports

Packet intercept on virtual interface bundles

Corresponding SNMP MIB enhancements for each of these functions, as intercept requests are initiated by a mediation device (MD) using SNMPv3


Note For restrictions on this platform, see "Overview of CISCO-TAP-MIB" in Cable Monitor and Intercept Features for the Cisco CMTS. See Additional Information.



Note No new CLI commands are provided for this feature in Cisco IOS Release 12.3(13a)BC.


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 1-7 lists the differences between packet intercept and SII features as implemented on the Cisco uBR10012.

Table 1-7 Differences Between Packet Intercept and SII Features on the Cisco uBR10012

Feature
Packet Intercept
Service Independent Intercept

Interface Type

Cable

Cable

IP Masks

255.255.255.255 or 0.0.0.0

255.255.255.255 or 0.0.0.0

L4 Ports

Any single port or 0-65535

Any single port or 0-65535

Protocol

UDP

Any

TOS/DSCP

Not supported

Supported


Additional Information

For additional information, refer to the following documents:

Configuring COPS for RSVP, Cisco IOS Versions 12.2 and 12.3

http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfcops_ps1835_TSD_Products_Configuration_Guide_Chapter.html

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_white_paper09186a0080179138.shtml

IP Broadcast and Multicast Features

The Cisco uBR10012 router supports the following IP broadcast and Multicast features:

IP Broadcast Echo

IP Multicast Echo

Multicast QoS Support on the Cisco uBR10012 CMTS

SSM Mapping

IP Broadcast Echo

You can activate upstream IP broadcast echo so that the Cisco uBR10012 router can echo broadcast packets. For configuration information, refer to the "Setting Optional Broadcast and Cable IP Multicast Echo" section.

IP Multicast Echo

With this feature, you can send a copy of each multicast packet (received from a cable line card) to the downstream ports associated with the MAC domain of the receiving US port. This feature allows for all CMs within a MAC domain to receive multicast packets sent by a CM in the same MAC domain. For additional information, refer to the "Setting Optional Broadcast and Cable IP Multicast Echo" section.

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

The multicast definitions are per-bundle, not per interface. This means that all downstreams in a bundle share the same multicast to QoS association. The downstreams will create their own service flows according to the same QoS parameters.

Multicast to QoS definitions can not be assigned per sub-interface

Multicast SIDs are not deleted when a group becomes idle (no response to IGMP reports).

The QoS assignments for a multicast group can not be changed dynamically. If the user wishes to change them then a new "cable match" command must be configured.

Multicast QoS is not supported on Multicast Echo on Cisco uBR10012 router.

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-qos
 
   

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:

Source Specific Multicast (SSM) Mapping

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html

IP Routing Features

The Cisco uBR10012 router offers you several features to assist with IP routing configuration and performance.

Cable ARP Filter Enhancement

Configurable Registration Timeout

Host-to-Host Communication (Proxy Address Resolution Protocol)

Integrated Time-of-Day Server

PBR support for the Cisco uBR10012

Supported Protocols

For additional information about IP routing, refer to these and other documents on Cisco.com:

IP Routing Protocols section in the Cisco IOS IP Configuration Guide, Release 12.2

IP Routed Protocols

Top Issues: IP Routing Protocols web page by Cisco's Technical Assistance Center (TAC)

Cable ARP Filter Enhancement

The cable arp filter command, introduced with Cisco IOS Release 12.2(15)BC2b, enables service providers to filter ARP request and reply packets. This prevents a large volume of such packets from interfering with the other traffic on the cable network.

Cisco IOS Release 12.3(9a)BC introduces enhanced command option syntax for the cable arp filter command, where number and window-size values are optional for reply-accept and request-send settings.

To control the number of Address Resolution Protocol (ARP) packets that are allowable for each Service ID (SID) on a cable interface, use the cable arp command in cable interface configuration mode. To stop the filtering of ARP broadcasts for CMs, use the no form of this command.

cable arp filter {reply-accept number window-size | request-send number window-size}

no cable arp filter {reply-accept | request-send}

default cable arp filter {reply-accept | request-send}

Syntax Description

reply-accept number window-size

Configures the cable interface to accept only the specified number of ARP reply packets every window-size seconds for each active Service ID (SID) on that interface. The cable interface drops ARP reply packets for a SID that would exceed this number.

number = (Optional) Number of ARP reply packets that is allowed for each SID within the window time period. The allowable range is 0 to 20 packets, with a default of 4 packets. If number is 0, the cable interface drops all ARP reply packets. If not specified, this value uses default.

window-size = (Optional) Size of the window time period, in seconds, in which to monitor ARP replies. The valid range is 1 to 5 seconds, with a default of 2 seconds.

request-send number window-size

Configures the cable interface to send only the specified number of ARP request packets every window-size seconds for each active SID on that interface. The cable interface drops ARP requests for a SID that would exceed this number.

number = (Optional) Number of ARP request packets that is allowed for each SID within the window time period. The allowable range is 0 to 20 packets, with a default of 4 packets. If number is 0, the cable interface does not send any ARP request packets.

window-size = (Optional) Size of the window time period, in seconds, in which to monitor ARP requests. The valid range is 1 to 5 seconds, with a default of 2 seconds.


Cisco IOS Release 12.3(9a)BC also removes a prior caveat with HCCP Protect interfaces. Previously, in the event of a revert-back HCCP N+1 switchover, manual removal of cable arp filter reply and cable arp filter request configurations may have been required afterward on Protect interfaces.

For more information about ARP Filtering, refer to the following document on Cisco.com:

Cable ARP Filtering

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblarpfl.html

Configurable Registration Timeout

The registration timeout value (the T9 timer) is configurable. This configurable timer parameter describes the elapsed time from a CM's successful completion of Ranging State 2 to its initial registration request message. During this time, the CM establishes IP connectivity, Time of Day, and security (optional), and transfers operational parameters from the Trivial File Transfer Protocol (TFTP) server.

This capability allows you to change the CM registration value (the T9 timer). Use the registration-timeout command to set or reset the T9 timer.

Command
Description

registration-timeout minutes

Sets the T9 timer to the new value (from 2 to 60 minutes).

no cable registration-timeout

Resets the T9 timer to its default of 3 minutes.


Host-to-Host Communication (Proxy Address Resolution Protocol)

Proxy Address Resolution Protocol (ARP) allows the Cisco uBR10012 router to issue ARP requests on behalf of CMs on the same cable network subnet. Proxy ARP can help machines on a subnet reach remote subnets without configuring routing or a default gateway.

The Cisco router's interface should be configured to accept and respond to proxy ARP.

The workstation must be configured to view the entire network as a single network. This is typically done by configuring the workstation with a smaller subnet mask than the network really uses.

The router replies to the proxy ARP request with its MAC address. Therefore, the workstation sends all traffic for this destination address to the router, and the router forwards it according to the routing table.

Hosts have no idea of the physical details of their network and assume it to be a flat network in which they can reach any destination simply by sending an ARP request. But using ARP for everything has disadvantages, some of which are listed below:

This method increases the amount of ARP traffic on your segment.

Hosts need larger ARP tables to handle IP-to-MAC address mappings.

Security may be undermined. A machine can claim to be another in order to intercept packets, an act called "spoofing."

ARP does not work for networks that do not use ARP for address resolution.

ARP does not generalize to all network topologies (for example, more than one router connecting two physical networks).

For configuration information, refer to "Activating Cable Proxy ARP Requests" section.

Integrated Time-of-Day Server

This operational feature allows theCisco uBR10012 router to respond to time-of-day (ToD) (RFC 868) queries from cable interfaces during the registration process. For information about configuring DHCP, ToD, or TFTP services, refer to the chapter titled "Configuring DHCP, ToD, and TFTP Services" in the Cisco Cable Modem Termination System Feature Guide on Cisco.com.

PBR support for the Cisco uBR10012

Policy-Based Routing (PBR) provides a tool for expressing and implementing the forwarding or routing of data packets, on the basis of the policies that are defined by network administrators. PBR allows policy override on routing protocol decisions by selectively applying policies based on access list and/or packet size.

Network administrators can also use PBR to selectively change the IP ToS, IP precedence, and IP QoS Group fields for matching incoming packets on an interface.

The Cisco uBR10012 universal broadband router supports a maximum of 255 PBR policies and 32 route maps within each policy. The following subset of policy-based routing commands is supported in Cisco IOS release 12.2(11)CY:

ip policy route-map map-tag

route-map map-tag [permit | deny] [sequence-number]

match ip address {ACL-number | ACL-name} [ACL-number | ACL-name ...]

match length min max

set [default] interface type number [type number ...]

set ip [default] next-hop ip-address [ip-address ...]

set ip precedence value

set ip qos-group value

set ip tos value

show route-map [map-tag]

For more information on PBR, refer to the "Configuring Policy-Based Routing" chapter in the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at the following URL:

http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfpbr_ps1835_TSD_Products_Configuration_Guide_Chapter.html

Supported Protocols

The Cisco uBR10012 router supports multiple protocols of multiple classes, including but not limited to, the following:

Address Resolution Protocol (ARP)

Cisco Discovery Protocol (CDP)

Domain Name System (DNS)

Internet Protocol (IP) v4/v5

Simple Network Management Protocol (SNMP) v2 and SNMPv3 Integrated Dynamic Host Configuration Protocol (DHCP) server

Trivial File Transfer Protocol (TFTP) client

User Datagram Protocol (UDP)


Note Be aware that when configuring a routing protocol, the Cisco IOS software must reset the interfaces to enable the change. This normally does not significantly affect operations on the interface, except that when this is done on a cable interface, it causes all cable modems on that particular downstream to reinitialize, potentially interfering with data transmission on that downstream. Therefore, you should use routing global configuration commands, such as router rip, on a cable interface only when a minimum of subscribers would be affected.


For additional information about configuring IP routing protocols, refer to the "IP Routing Protocols" chapter in the Cisco IOS IP Configuration Guide, Release 12.2 on Cisco.com.

Management Features

The Cisco uBR10012 router provides you with the following features that make CMTS headend configuration, management, and DOCSIS support more powerful and efficient:

Admission Control for the Cisco CMTS

Broadband Internet Access

Cable Interface Bundling

CNEM Compliance

Customer Premises Equipment Limitation and Override

DOCSIS 2.0 SAMIS ECR Data Set

DOCSIS Set-Top Gateway Issue 1.0

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Downstream Channel ID Configuration

Downstream Frequency Override

Dynamic Channel Change (DCC) for Loadbalancing

Dynamic Modulation Profiles

Dynamic Upstream Modulation

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

Management Information Base (MIB) Changes and Enhancements

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

Pre-equalization Control for Cable Modems

Route Processor Redundancy Support

Secure Socket Layer Server for Usage-Based Billing

SFID Support for Multicast and Cable Interface Bundling

Simple Network Management Protocol Cable Modem Remote Query

Simple Network Management Protocol v3

Spectrum Management

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Static CPE Override (cable submgmt default Command)

Statistical Counters

Subscriber Traffic Management (STM) Version 1.1

Usage Based Billing (SAMIS)

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.

CPU utilization—Admission Control monitors CPU utilization on the Cisco CMTS, and preserves QoS for existing service flows when new traffic would otherwise compromise CPU resources on the Cisco CMTS.

Memory resource utilization (I/O, Processor, and combined total)—Admission Control monitors one or both memory resources and their consumption, and preserves QoS in the same way as CPU utilization.

Bandwidth utilization for upstream and downstream—Admission Control monitors upstream and downstream bandwidth utilization, and associated service classes, whether for data or dynamic service traffic.

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:

Admission Control for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_adm.html

Broadband Internet Access

The Cisco uBR10012 router provides subscribers with broadband Internet access that processes IF/RF signals, TV signals, and analog and digital data signals. For configuration information, refer to Chapter 1 "Configuring Basic Broadband Internet Access."

Cable Interface Bundling

Cable interface bundling provides for IP address conservation with routing capabilities over a two-way cable plant. If you have limited IP address space, interface bundling conserves your IP address resources.

Interface bundling supports sharing one IP subnet across multiple cable interfaces grouped into a cable interface bundle with support for bundle masters. This feature can be used with Multiprotocol Label Switching (MPLS) configurations. For configuration information, refer to the cable bundle command in the Cisco CMTS IOS Cable Command Reference Guide 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:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/12_2sc/reference/guide/ubrmibv5.html

Customer Premises Equipment Limitation and Override

Using the cpe max command, the Cisco uBR10012 router can report and limit the number of CPEs per CM using the CLI or SNMP. This feature is separate from the ability of a CM to support multiple CPE devices.

Command
Description

cpe max cpe-num

Specifies the maximum number of customer premises equipment (CPE) devices that can use the CM to connect to the cable network.

no cpe max

Removes the CPE specification.


Syntax Description

cpe-num

Specifies the number of CPEs. Valid range is 1 to 254.


For additional command information, refer to the Cisco CMTS IOS Cable Command Reference Guide and to the Cable Modem Termination System Feature Guide, both 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:

Usage-Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html

DOCSIS Set-Top Gateway Issue 1.0

Cisco IOS Release 12.3(9a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.0 on the Cisco uBR10012 universal broadband router. The DOCSIS Set-Top Gateway (DSG) feature allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing DOCSIS networks. This allows MSOs and other service providers to combine both DOCSIS and STB operations over one, open, vendor-independent network, without any change to the existing network or cable modems.

DSG is a CableLabs® specification that allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing Data-over-Cable Service Interface Specifications (DOCSIS) cable networks. DSG 1.0 allows cable Multi-System Operators (MSOs) and other service providers to combine both DOCSIS and STB operations over a single, open and vendor-independent network without requiring any changes to the existing DOCSIS network infrastructure.

At the time of this Cisco publication, the CableLabs® DOCSIS DSG specification is in the current status of "Issued" as characterized by stability, rigorous review in industry and cross-vendor interoperability.

For additional information about configuring and using DSG 1.0 on the Cisco uBR10012 router, refer to the following document on Cisco.com:

DOCSIS Set-Top Gateway for the Cisco CMTS

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guides_list.html

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Cisco IOS Release 12.3(13a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.1 on the Cisco uBR10012 router. DSG 1.1 builds on and supports the enhancements of DOCSIS Set-Top Gateway Issue 1.0 in the prior Cisco IOS 12.3(9a)BC release.

A-DSG 1.1 introduces powerful support for DOCSIS 1.1 and DOCSIS 2.0, and the latest DOCSIS DSG specifications. The benefits provided by A-DSG include the following:

Retains the essential nature of out of band (OOB) messaging, but moves it to a modern technology base.

Replaces single-vendor, low-density, special-purpose equipment on the network, with significantly increased subscriber bandwidth and traffic.

Consolidates cable modem and STB data traffic on a shared DOCSIS channel.

Increases high-speed data (HSD) services to cable TV subscribers over the DOCSIS 1.1 infrastructure,

Extends support for DOCSIS 1.1 digital video broadcast traffic.

Enables shared or dedicated support for either HSD or video traffic.

Supports one- or two-way operations, and advanced, two-way interactive applications such as streaming video, Web browsing, e-mail, real-time chat applications, and targeted advertising services.

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:

DSG 1.1 enables the learning of dynamic tunnel definitions. DSG 1.0 only had static tunnel definitions (programmed into the set-top box).

DSG 1.1 features new Cisco IOS command-line interface (CLI) configuration and show commands for A-DSG configuration and network information.

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:

DSG rules and rule priority

DSG classifiers

DSG channel list type/length value (TLV)

DSG client identifier (whether broadcast, CA System, application, or MAC-level)

DSG timer list

DSG upstream channel ID (UCID) list

Vendor-specific information field

Prerequisites for DSG 1.1

Cisco IOS release 12.3(13a)BC or a later 12.3 BC release are required.

Cisco DSG 1.1 is supported on the Cisco uBR10012 router with PRE1 or PRE2 performance routing engine modules.

Cisco DSG 1.1 is supported on the Cisco uBR10012 router with the following cable interface line cards and broadband processing engines (BPEs):

Cisco uBR10-LCP2-MC16C/MC16E/MC16S Cable Interface Line Card

Cisco uBR10-LCP2-MC28C Cable Interface Line Card

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Restrictions and Caveats for DSG 1.1

Cisco DSG 1.1 has the following restrictions:

Cisco DSG 1.1 does not support Service Flow Quality of Service (QoS), which is available at Layer 3.

Cisco DSG 1.1 does not support tunnel security, but strictly access control lists (ACLs).

Cisco DSG 1.1 does not support subinterfaces.

Cisco DSG 1.1 does not support HCCP N+1 interoperability.

Cisco DSG 1.1 does not support SNMP MIBS for A-DSG.

Additional Information about DSG 1.1

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubradsg.html

DOCSIS Set-Top Gateway (DSG) for the Cisco CMTS

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guides_list.html

Cisco DOCSIS Set-top Gateway White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_white_paper09186a00801b3f0f.shtml

CableLabs DOCSIS Set-top Gateway (DSG) Interface Specification SP-DSG-I03-041124

http://www.cablelabs.com/specifications/archives/CM-SP-DSG-I03-041124.pdf

Advanced-mode DOCSIS Set-Top Gateway Issue 1.2

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™:

DOCSIS Set-top Gateway (DSG) Interface Specification, CM-SP-DSG-I09-050812

http://www.cablelabs.com/specifications/archives/CM-SP-RFI2.0-I09-050812.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 DSG 1.2 information, refer to the following documents on Cisco.com:

Advanced-mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdsg12.html

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Downstream Channel ID Configuration

This operational feature allows all cable interfaces on the HFC network to identify themselves using unique downstream channel IDs, instead of their downstream frequencies. CMs communicate their downstream ID when making a connection, not their downstream frequency. System administrators can enter a configurable downstream channel ID to a value other than the default. Thus, each downstream channel ID can be unique on a cable network. For configuration information, refer to "Assigning the Downstream Channel ID" section.

Downstream Frequency Override

The Cisco uBR10012 router is able to change the downstream frequency for any or all CMs, overriding the DOCSIS configuration file settings. For DOCSIS QoS configuration information, refer to the feature module titled DOCSIS 1.1 for Cisco uBR7200 Series Universal Broadband Routers on Cisco.com.

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:

Load Balancing and Dynamic Channel Change on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Dynamic Channel Change (DCC) for Loadbalancing

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.

Load Balancing techniques allow for moving cable modems with DCC by using configurable initialization techniques.

DCC allows line card channel changes across separate downstream channels in the same cable interface line card, with the DCC initialization techniques ranging from 0 to 4.

DCC transfers cable modem state information from the originating downstream channel to the target downstream channel, and maintains synchronization of the cable modem information between the cable interface line card and the Network Processing Engine (NPE) or Route Processor (RP).

When the target channel is in ATDMA mode, only DOCSIS 2.0-capable modems can be successfully load balanced. (Only DOCSIS 2.0-capable modems can operate on an ATDMA-only upstream channel.) Cisco recommends identical channel configurations in a load balancing group.

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

cable load-balance group group-num dcc-init-technique <0-4>

cable load-balance group group-num policy { pcmm | ugs }

cable load-balance group group-num threshold {load | pcmm | stability | ugs} <1-100>

cable load-balance group group-num threshold load <1-100> {minimum}

cable load-balance group group-num threshold load <1-100> {enforce}

Testing Command

test cable dcc mac-addr {slot/port | slot/subslot/port} target-us-channel-id ranging-technique

For configuration, command reference, testing, and examples for DCC on the Cisco CMTS, refer to the following documents on Cisco.com:

Load Balancing and Dynamic Channel Change (DCC) on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html

Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Dynamic Modulation Profiles

For each modulation profile configuration, the Cisco uBR10012 router supports the following:

Burst profile interval usage code

Burst profile number

Burst type

Differential encoding enable and disable

FEC correctable bytes value

Forward error correction (FEC) code word length

Guard time size

Last code word shortened or lengthened

Maximum burst size (see also

Preamble length and unique word length

Scrambler enable and disable

Scrambler seed value

For additional information about configuring dynamic upstream modulation and modulation profiles, refer to the chapter titled Spectrum Management for the Cable Modem Termination System in the Cisco Cable Modem Termination System Feature Guide.

Dynamic Upstream Modulation

This spectrum management feature provides improved performance using proactive spectrum management functions. This feature monitors the signal-to-noise ratio (SNR) and forward error correction (FEC) counters in the active return path of each upstream port. It tracks whether the upstream channel signal quality can support the modulation scheme configured, and adjusts to the most robust modulation scheme when necessary.

For additional information about configuring dynamic upstream modulation and modulation profiles, refer to the chapter titled Spectrum Management for the Cable Modem Termination System in the Cisco Cable Modem Termination System Feature Guide.

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.3(9a)BC introduces support for Gigabit EtherChannel (GEC) on the Cisco uBR10012 universal broadband router with the PRE2 performance routing engine modules. Cisco IOS Release 12.3(9) supports Gigabit Ethernet interfaces for IEEE 802.1Q inter-VLAN trunking with increased bandwidth on the Cisco uBR10012 router.


Note FastEtherChannel (FEC) interfaces and ATM trunking are not supported on the Cisco uBR10012 router.


EtherChannel provides Gigabit Ethernet (GE) speeds by grouping multiple GE-speed ports into a logical port channel that supports speeds up to 8 Gbps. This provides fault-tolerant, high-speed links between switches, routers and servers.

Trunking is configured between the switch and the router to provide inter-VLAN communication over the network. Trunking carries traffic from several VLANs over a point-to-point link between the two network devices. In a campus network, trunking is configured over an EtherChannel link to carry the multiple VLAN information over a high-bandwidth channel.

For additional information about configuring EtherChannel on the Cisco uBR10012 router, refer to the following document on Cisco.com:

EtherChannel for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_ethr.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:

Use SNMP set and get requests to access information in Cisco CMTS universal broadband routers.

Reduce the amount of time and system resources required to perform functions like inventory management.

A standards-based technology (SNMP) for monitoring faults and performance on the router.

Support for SNMP versions (SNMPv1, SNMPv2c, and SNMPv3).

Notification of faults, alarms, and conditions that can affect services.

For additional information, refer to the following document on Cisco.com:

To access the Cisco CMTS Universal Broadband Router MIB Specifications Guide, go to:

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

Cisco IOS Release 12.3(9a)BC adds the following new MIB support for the Cisco uBR10012 router.

CISCO-CABLE-METERING-MIB

CISCO-CABLE-QOS-MONITOR MIB

CISCO-CABLE-SPECTRUM-MIB

CISCO-ENHANCED-MEMPOOL-MIB

CISCO-PROCESS-MIBDOCS-QOS-MIB

DSG-IF-MIB

For additional information about MIBs for the Cisco CMTS, refer to the following resources on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

SNMP Object Navigator

http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en

CISCO-CABLE-METERING-MIB

The CISCO-CABLE-METERING-MIB contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, also known as Usage-Based Billing on the Cisco CMTS. This format is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.

The MODULE-IDENTITY for the CISCO-CABLE-METERING-MIB is ciscoCableMeteringMIB, and its top-level OID is 1.3.6.1.4.1.9.9.424 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableMeteringMIB).


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


Additional Information

For additional SAMIS information, refer to the following resource:

Usage Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html

CISCO-CABLE-QOS-MONITOR MIB

Cisco IOS Release 12.3(9a)BC introduces additional features for the CISCO-CABLE-QOS-MONITOR MIB, including the following:

Clarified the descriptions of a number of objects.

Added a number of objects in the ccqmCmtsEnforceRuleTable to support DOCSIS 1.1 and DOCSIS 2.0 cable modems and to support peak and off-peak monitoring.

Added the ccqmCmtsIfBwUtilTable to provide thresholds for downstream/upstream bandwidth utilization.

Deprecated and removed ccqmCmtsEnfRuleByteCount.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-CABLE-SPECTRUM-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router, with these additional MIB object enhancements:

ccsFlapListMaxSize and ccsFlapListCurrentSize SNMP objects provide additional description for cable flap lists.

Added the ccsCmFlapTable to replace the ccsFlapTable. The new object uses downstream, upstream and Mac as indices to replace the ccsFlapTable object.

The enhanced ccsSNRRequestTable object provides a table of SNR requests with modified description.

Added the ccsUpSpecMgmtUpperBoundFreq object to assist with spectrum management on the Cisco CMTS.

Added the ccsCompliance5 object.

Added ccsCmFlapResetNow to reset the flap list for a particular cable modem.

Updated the descriptions for ccsFlapListMaxSize, ccsFlapListCurrentSize, and ccsSNRRequestTable.

The following objects are also now deprecated:

ccsFlapPowerAdjustThreshold

ccsFlapMissThreshold

ccsFlapResetAll

ccsFlapClearAll

ccsFlapLastClearTime

The maximum number of entries in the flap-list was changed from a maximum of 8191 for the entire router, to the following:

8191 entries for each Broadband Processing Engine (BPE) cable interface, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U.

8191 maximum flap-list entries for all non-BPE cable interfaces, such as the Cisco uBR-MC16C, Cisco uBR-MC16S, and Cisco uBR-MC28C.

Two objects are now used to track the flap list size:

ccsFlapListMaxSize—Reflects the flap list size, as configured by the cable flap-list size command.

ccsFlapListCurrentSize—Reflects the current size of the flap list for each MAC domain (downstream).


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-ENHANCED-MEMPOOL-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router. The CISCO-ENHANCED-MEMPOOL-MIB enables you to monitor CPU and memory utilization for "intelligent" line cards and broadband processing engines on the Cisco uBR10012 router. These include the Cisco MC16X and MC28X series line cards.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-PROCESS-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-PROCESS-MIB on the Cisco uBR10012 universal broadband router with PRE2 modules.The CISCO-PROCESS-MIB enables you to monitor CPU and memory utilization for RF cards, cable interface line cards and broadband processing engines on the Cisco uBR10012 router.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


DOCS-QOS-MIB

Cisco IOS Release 12.3(9) introduces additional MIB object enhancements for the DOCS-QOS-MIB on the Cisco uBR10012 universal broadband router:

Updated with the DOCSIS operations support system interface (OSSI) v2.0-N-04.0139-2.

The default values of docsQosPktClassIpSourceMask and docsQosPktClassIpDestMask objects are set to 0xFFFFFFFF.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


DSG-IF-MIB

The DSG-IF-MIB defines objects that are used to configure, control, and monitor the operation of the DOCSIS Set-top Gateway (DSG) 1.0 feature on Cisco uBR7200 series and Cisco uBR10012 routers.


Note The MODULE-IDENTITY for the DSG-IF-MIB is dsgIfMib, and its top-level OID is 1.3.6.1.4.1.9.9.999 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.dsgIfMib). Because this is an experimental MIB, its top-level OID is expected to change when the DSG specifications are finalized.



Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


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:

For pre-equalization to be supported on a per-modem basis, the cable modem must send verification of pre-equalization after it registers with the Cisco CMTS.

The option of excluding the OUI is a global configuration. For the cable modem on which OUI is excluded, the excluded OUI is disabled for all interfaces. This method uses a list of OUI values, recording which modems are sent and not sent pre-equalization.

cable 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

oui

Organizational Unique identifier for the interface specified. Using this keyword excludes the specified OUI during cable modem registration for the associated interface.

modem

Cable Modem identifier for the cable modem specified. Using this keyword excludes the cable modem.

mac-addr

Identifier for the OUI or cable modem to be excluded.


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

Release
Modification

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-addr
 
   
 
   

The 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-addr
 
   

The 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 t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# cable pre-equalization exclude oui 00.09.04
Router(config)# end
Router# show run
Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04
Router#
 
   

On the line card console for the same Cisco uBR10012 router, verify the configuration with the following command:

clc_7_1# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04
clc_7_1#
 
   

The 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.

npeg1-test# conf t
Enter configuration commands, one per line. End with CNTL/Z.
npeg1-test(config)# cable pre-equalization exclude oui 00.09.24
npeg1-test(config)# end
npeg1-test#show ru
02:58:10: %SYS-5-CONFIG_I: Configured from console by consolen
npeg1-test# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24
npeg1-test#
 
   

On the line card console for the same Cisco uBR7246VXR router, verify the configuration with the following command:

clc_4_0# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24
clc_4_0#
 
   

After 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:

debug cable range

debug cable interface cx/x/x mac-addr

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-addr
 
   

Removal of this feature can be verified with the following debug command:

debug cable interface cx/x/x mac-ad—Verifies the ranging message for all non-excl modems include pre-eq data, and for the excluded modems ranging messages do not include pre-eq data.

 
   

For additional information about this or other commands, refer to the following documents on Cisco.com:

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

Route Processor Redundancy Support

Cisco IOS Release 12.2(4)XF introduces support for Route Processor Redundancy (RPR) on the Cisco uBR10012 universal broadband router. The RPR feature enables the Cisco uBR10012 to use two PRE1 or PRE2 modules in a redundant configuration, so that if the primary PRE module fails or becomes inactive, the system automatically performs a failover, where the secondary PRE1 module takes over and assumes full responsibility for systems operations.

The RPR feature does not require a full reboot of the system to perform a failover. When the system is originally initialized, the secondary PRE1 or PRE2 module performs an abbreviated initialization routine—the module performs all self-checks and loads the Cisco IOS software, but instead of performing normal systems operations it begins monitoring the primary PRE module. If the secondary PRE1or PRE2 module detects a failure in the primary module, it can quickly assume the primary responsibility for systems operations.

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:

Usage-Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html

SFID Support for Multicast and Cable Interface Bundling

Cisco IOS Release 12.3(9a)BC removes the prior restriction in Caveat CSCea45592 that prevented the creation of DOCSIS 1.1 upstream packet classifiers and service flow IDs (SFIDs) when configuring multicast groups with bundled cable interfaces. Cable interface bundling now supports SFIDs on Multicast groups.


Note SFIDs map individual CPE devices to separate MPLS-Virtual Private Network (VPN) interfaces.



Note Cisco IOS Release with the Cisco uBR10012 router does not support overlapping IP addresses with MPLS-VPN.


For additional configuration information, refer to the following document on Cisco.com:

Cable Interface Bundling for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

Simple Network Management Protocol Cable Modem Remote Query

The cable modem remote-query command was introduced for the Cisco uBR10012 router in the Cisco IOS Release 12.2(4)BC1b, and allows customers to query the cable modem performance statistics directly from the cable modem termination system (CMTS).

Users can poll the cable modems periodically using Simple Network Management Protocol (SNMP) and cache the information such as:

IP address

MAC address

S/N ratio

Upstream Transmit Power on the CMTS

This information helps the operators to know at a glance the state of a single modem and to have an overall status of the plant. For configuration information, refer to the Configuring cable modem remote-query Command at http://www.cisco.com/en/US/tech/tk86/tk804/technologies_configuration_example09186a0080171c8e.shtml

Simple Network Management Protocol v3

SNMP version 3 offers enhanced security features and increases interoperability and ease of network management. The implementation set of MIBs allows the SNMP manager to gather data such as system card descriptions, serial numbers, hardware and software revision levels, and slot location. For additional information, refer to the "Configuring Global Parameters" section, and to the "MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC" section.

Service Class Setting Using SNMP

The Cisco uBR10012 router supports objects related to class of service. This aids in network management.

Spectrum Management

Spectrum management is a software and hardware feature provided in the CMTS so that the CMTS may sense both downstream and upstream plant impairments, report them to a management entity, and automatically mitigate them where possible. Spectrum management provides many capabilities that are described further in the Cisco Cable Modem Termination System Feature Guide.

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:

Supports additional software functionality for the Cisco uBR10-LCP2-MC16C/E/S cable interface line card and the Cisco MC5x20S/U broadband processing engine.

Supports spectrum analyzer functionality.

Supports proactive channel management and hopping decisions, so as to avoid the negative impact of ingress noise, and to maintain uninterrupted subscriber service.

Offers flexible configuration choices, allowing MSOs to determine the priority of the actions to be taken when ingress noise on the upstream channel exceeds the allowable thresholds. The configurable actions are frequency hopping, switching the modulation profile, and reducing the channel width.

Performs Cisco Network Registrar (CNR) calculations using DSP algorithms in real-time on a per-interface and a per-modem basis.

Intelligently determines when to modify the frequency, channel width, or modulation profile, based on CNR calculations in the active channel, the number of missed station maintenance polls, and the number of correctable or non-correctable Forward Error Correction (FEC) errors. Previously, channel hopping occurred when the number of missed station maintenance polls exceeded a user-defined threshold or the SNR reported by the Broadcom chip exceeded the DOCSIS thresholds.

Enhances the Dynamic Upstream Modulation feature for the Cisco uBR-MC16S line card. This feature supports dynamic modulation using two upstream profiles. The primary profile (typically using 16-QAM or a mixed modulation profile) remains in effect at low noise conditions, but if upstream conditions worsen, the cable modems switch to the secondary profile (typically using QPSK modulation) to avoid going offline. When the noise conditions improve, the modems are moved back to the primary profile.

Commands for Enhanced Spectrum Management

A variety of commands for enhanced spectrum management now provide new options.

cable upstream n threshold cnr-profile1 threshold1-in-dB cnr-profile2 threshold2-in-dB corr-fec fec-corrected uncorr-fec fec-uncorrected

cable upstream n upstream threshold snr-profiles threshold1-in-dB threshold2-in-dB

cable upstream n threshold corr-fec corrfec-threshold

cable upstream n threshold uncorr-fec uncorrfec-threshold

show cable hop n upstream history

show cable hop n upstream threshold


Note For additional information and examples, see "Configuring Proactive Channel Management" and "Verifying the Spectrum Management Configuration" in Spectrum Management for the Cisco CMTS, at the following URL

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html


For additional information about spectrum management and advanced spectrum management on the Cisco CMTS, refer to the following documents on Cisco.com:

Spectrum Management and Advanced Spectrum Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html

Advanced Spectrum Management Feature for the Cisco uBR-MC16S Cable Interface Line Card

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubrmc16s/feature/guide/mc16sii.html

Static CPE Override (cable submgmt default Command)

The cable submgmt static-cpe-override command enables Multiple Service Operators (MSOs) to override network DHCP settings on CPE devices when performing troubleshooting with a laptop computer and console connection to the Cisco universal broadband router.

For additional information about using the cable submgmt static-cpe-override command, refer to these documents on Cisco.com:

Cisco CMTS Static CPE Override

http://www.cisco.com/en/US/docs/cable/cmts/feature/stat_cpe.html

Cisco CMTS IOS Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Statistical Counters

The show controller cx/y upstream command has been enhanced to display additional statistical counters in the output.

Command
Description

show controller cx/0 upstream number

Provides statistical counters in the enhanced output that include:

Average percentage of upstream utilization in minislots

Average percentage of contention slots

Average percentage of initial ranging slots

Average percentage of minislots that were due because the MAP scheduler was not able to request them in time


For additional command information, refer to the Cisco IOS Interface Command Reference Guide, Release 12.2 on Cisco.com.

Subscriber Traffic Management (STM) Version 1.1

Cisco IOS Release 12.3(9a)BC introduces support for Subscriber Traffic Management (STM) through Version 1.1 on the Cisco uBR10012 universal broadband router. STM 1.1 supports DOCSIS 1.1-compliant cable modems.

The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM 1.1 works with Network-Based Application Recognition (NBAR) and Access control lists (ACLs) to ensure full network performance to other network subscribers that abide by their service agreements. STM 1.1 also works in conjunction with the Cisco Broadband Troubleshooter 3.2 to support additional network management and troubleshooting functions in the Cisco CMTS.

STM 1.1 extends earlier STM functions to monitor a subscriber's traffic on DOCSIS 1.1 primary service flows and supports these additional features:

Cisco Broadband Troubleshooter (CBT) 3.2 supports STM 1.1.

DOCSIS 1.0-compliant and DOCSIS 1.1-compliant cable modem are supported.

Monitoring and application of traffic management policies are applied on a service-flow basis.

Monitoring window duration increased from seven to 30 days.

For additional information about STM 1.1 and Cisco CBT 3.2, refer to the following document on Cisco.com:

Subscriber Traffic Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps819/prod_release_notes_list.html

Usage Based Billing (SAMIS)

Cisco IOS Release 12.3(9a)BC introduces the Usage-Based Billing feature on the Cisco uBR10012 router, supporting DOCSIS 1.0- and DOCSIS 1.1-compliant cable modems. This feature provides subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. SAMIS is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.

The CISCO-CABLE-METERING-MIB is also introduced with Cisco IOS Release 12.3(9a)BC in support of SAMIS.

For additional information about configuring and monitoring Usage-Based Billing (SAMIS) on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:

Usage Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html

PacketCable and Voice Support Features

The Cisco uBR10012 router supports the following PacketCable and PacketCable MultiMedia features:

PacketCable 1.0 With CALEA

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

Packetcable Multimedia for the Cisco CMTS

PacketCable 1.0 With CALEA

Cisco IOS Release 12.3(9a)BC introduces DOCSIS 1.1 support for PacketCable 1.0 with Communications Assistance for Law Enforcement Act (CALEA) on the Cisco uBR10012 universal broadband router with the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE).

PacketCable is a program initiative from Cablelabs and its associated vendors to establish a standard way of providing packet-based, real-time video and other multimedia traffic over hybrid fiber-coaxial (HFC) cable networks. The PacketCable specification is built upon the Data-over-Cable System Interface Specifications (DOCSIS) 1.1, but it extends the DOCSIS protocol with several other protocols for use over non-cable networks, such as the Internet and the public switched telephone network (PSTN).

This allows PacketCable to be an end-to-end solution for traffic that originates or terminates on a cable network, simplifying the task of providing multimedia services over an infrastructure composed of disparate networks and media types. It also provides an integrated approach to end-to-end call signaling, provisioning, quality of service (QoS), security, billing, and network management.

Cisco IOS Release 12.2(11)BC1 and later releases in the Cisco IOS 12.3 release train support the PacketCable 1.0 specifications and the CALEA intercept capabilities of the PacketCable 1.1 specifications.

For additional information about configuring PacketCable on the Cisco CMTS, refer to the following document on Cisco.com:

Configuring PacketCable on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/pcktcbl.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 Emergency 911 cable interface line card prioritization applies only to PacketCable voice calls.


During HCCP switchover events, cable modems recover in the following sequence in Cisco IOS release 12.3(13a)BC:

1. Cable modems supporting Emergency 911 voice traffic

2. Cable modems supporting non-emergency voice traffic

3. Cable modems that are nearing a T4 timeout event, in which service would be disrupted

4. Remaining cable modems

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.

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_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:

active Emergency 911 calls

recent Emergency 911 calls

regular voice calls

voice calls made after recent Emergency 911 calls

This feature is enabled and supported with the following new Cisco IOS command-line interface (CLI) configuration and show commands:

cable high-priority-call-window <minutes>

show cable calls [ interface cx/y | slot z ]

show cable calls [interface | slot] for the Cisco uBR 7200 Series

show cable calls [interface | slot/subslot] for the Cisco uBR10012 router

show cable modem [ip_addr | mac_addr | interface] calls

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 1
 
   

To 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 calls
 
   
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  1                 1               0                 0              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0              
 
   
Total       1                 1               0                 0              
 
   

The following command example illustrates the change on the Cisco uBR10012 router when this Emergency 911 calls ends:

Router# show cable calls
 
   
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 0               0                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0              
 
   
Total       0                 0               0                 1              
 
   

The 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 calls
 
   
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 2               1                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0              
 
   
Total       0                 2               1                 1              
 
   

The 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 calls
 
   
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 0               0                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0              
 
   
Total       0                 0               0                 1              
 
   

The 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# scm call
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:39
Router# scm call
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
 
   

The above example illustrates that call information disappears when a call ends. The following example illustrates a new Emergency 911 call on the Cisco CMTS:

Router# show cable modem calls
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    HV                  1:30
 
   
The following example illustrates a the end of the Emergency 911 call on the Cisco CMTS:
 
   
Router# show cable modem calls
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:3 
 
   

The following example illustrates a non-emergency voice call on the Cisco CMTS from the same MTA:

Router# show cable modem calls
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (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:30
 
   
The following example illustrates a the end of the non-emergency voice call on the Cisco CMTS:
Router# show cable modem calls
 
   
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
 
   
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:36
 
   

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_white_paper09186a0080179138.shtml

Packetcable Multimedia for the Cisco CMTS

Cisco IOS Release 12.3(13a)BC introduces support for PacketCable Multimedia (PCMM) on the Cisco uBR10012 universal broadband router, and fully supports the CableLabs PacketCable Multimedia Specification, PKT-SP-MM-I02-040930.

http://www.cablelabs.com/packetcable/specifications/multimedia.html

As described by CableLabs, some key features of the PCMM service delivery framework include the following:

Simple, powerful access to DOCSIS 1.1 QoS mechanisms supporting both time and volume-based network resource authorizations

Abstract, event-based network resource auditing and management mechanisms

A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces

More specifically, Cisco IOS Release 12.3(13a)BC expands or changes several PacketCable functions in earlier Cisco IOS releases, including the following:

Additional COPS Decision Messages—PCMM supports additional COPS decision messages, such as the following. The new objects for messages, such as Gate-Set, Gate-Set-Ack and Gate-Info, include different traffic profile definitions, different gate object formats, with additional objects for gate state reporting and flow utilization.

Gate-Set

Gate-Set-Ack

Gate-Set-Err

Gate-Info

Gate-Info-Ack

Gate-Info-Err

Gate-Delete

Gate-Delete-Ack

Gate-Delete-Err

State-Report

Different COPS client and UDP port for COPS sessions—PCMM uses a different COPS client type than does basic PacketCable, and PCMM uses a different UDP port for its COPS sessions. This can help to distinguish between PacketCable and PCMM COPS sessions on the Cisco CMTS.

MultiMedia State Machine—PCMM supports a different MultiMedia state machine than does PacketCable. The following are machine state changes introduced in PCMM with Cisco IOS Release 12.3(13a)BC:

PCMM gates are all unidirectional. In PacketCable, each gate is associated with both an upstream and downstream service flow. Although unidirectional flows are allowed, a bidirectional phone connection only has one gate.

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.

DOCSIS DSX service flow information is now maintained on the Cisco CMTS. With PacketCable, gates are authorized, reserved, or committed first on the Cisco CMTS with a specific gate ID, and then the Cisco CMTS initiates a DSX exchange using the reserved or committed gate ID in the message. With PacketCable, the cable modem must issue the DSX message and create the service flows. However, with PCMM, when a gate is reserved or committed, the DSX message is generated and sent immediately by the Cisco CMTS. Therefore, the Policy Server sends all of the service flow information necessary to setup the service flow to the Cisco CMTS instead of the cable modem. This causes a major change in the state machine that controls the gate allocation procedures.

New timer definitions and event actions are supported on PCMM. New timer definitions and timer event actions are supported for proper behavior of the net state machine. Some of the timers used with PacketCable have been eliminated, while the events associated with other times have changed for PCMM.

New state transitions that did not exist in PacketCable 1.x have been added to PCMM. Specifically, a gate can now be transitioned back from Committed to Authorized or Reserved state.

Cable interface line cards and broadband processing engines perform distributed DOCSIS functions. The Cisco MC28U cable interface line card on the Cisco uBR7200 series routers, and all the line cards on the Cisco uBR10012 router, are considered distributed, because the DOCSIS functionality is performed by the line card processor. The GCP signaling for PCMM and the gate state machine will executed on the NPE or RP processor. Because of the split in this functionality, IPC signaling resides between the gate state machine and the DOCSIS layer processing.

Event management—Event management messages have been modified to include information on the modified traffic profiles, and to match changes in the PCMM state machine. In addition, objects have been added to help support Gate usage and Gate commit time objects, used for usage limit based and time based gates.

For additional information about PacketCable and PacketCable Multimedia on the Cisco CMTS, refer to the following documents on Cisco.com:

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/netsol/ns341/ns121/ns342/ns343/networking_solutions_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:

Simple, powerful access to DOCSIS® 1.1 QoS mechanisms supporting both time and volume-basednetwork resource authorizations

Abstract, event-based network resource auditing and management mechanisms

A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces

PacketCable™ is a registered trademark of CableLabs®. Additional information and specifications are available online at the following CableLabs websites:

PacketCable website

http://www.cablelabs.com/packetcable/

PacketCable Multimedia specifications

http://www.cablelabs.com/packetcable/specifications/multimedia.html

Security Features

The Cisco uBR10012 router supports multiple security features:

Address Verification

CM Transmission Burst Size

Dynamic or Mobile Host Support

Dynamic Shared Secret (DMIC) with OUI Exclusion


Note Refer also to security features described in the "DOCSIS 1.1 Feature Support" section.


Address Verification

The Cisco uBR10012 router supports verification of cable interface and PC addresses to ensure that the cable interface service ID (SID) and MAC addresses are consistent. This security feature helps ensure that IP addresses are not spoofed. A PC behind a cable interface is assigned an IP address from the DHCP server. If a user on a second PC or cable interface statically assigns the same IP address to a PC, the Cisco uBR10012 router finds this case to help block the spoofing user. Using the command-line interface (CLI), administrators can determine the IP and MAC address of a given cable interface, and the SID number that shows the IP and MAC addresses of all devices learned in the cable interface MAC table. Using the service provider customer databases, administrators can cross-reference the spoofing cable interface and PC and prevent usage.

Refer to Chapter 4 "Managing Cable Modems on the Hybrid Fiber-Coaxial Network" to configure address verification.

CM Transmission Burst Size

The Cisco uBR10012 router allows CMs to register with a maximum transmission burst size up to 2000 bytes. This applies to DOCSIS 1.0 and 1.1 CMs that are configured with concatenation and no IP fragmentation.

For additional information about configuring dynamic upstream modulation and modulation profiles, refer to one or more of these documents on Cisco.com:

Cisco Cable Modem Termination System Feature Guide

Cisco uBR7200 Series Dynamic Upstream Modulation at http://www.cisco.com/en/US/docs/cable/cmts/feature/spec_mgt.html

Dynamic or Mobile Host Support

The cable source-verify command allows the CMTS administrator to bring up a PC behind one CM, then move it to another CM. This adds information for the hosts involved in host tables. To prevent security breaches, this feature supports pinging the host using the old SID to verify that it has indeed been moved. The security applies to upstream and downstream configuration.

Command
Description

cable source-verify dhcp

Configures the DHCP server to verify addresses.



Note The no cable arp command should be configured in the CMTS to prevent it from sending ARP requests.


The no cable arp command prevents the CMTS from sending an arp downstream to CPE hosts or to devices behind CMs requesting an IP/MAC address association. If the CMTS already knows the association, or is able to learn it in some other manner, IP packets are forwarded. Otherwise, if the destination is unknown, the packets are dropped.

Devices on a CM network may share a large subnet, but cannot communicate with each other without first going through the CMTS. The no cable proxy arp command prevents the CMTS from replying to arp requests for hosts on the same subnet, and thus prevents peer to peer communication between subscribers behind CMs.

For additional command information, refer to the Cisco CMTS IOS Cable Command Reference Guide on Cisco.com.

Dynamic Shared Secret (DMIC) with OUI Exclusion

Cisco IOS Release 12.3(9a)BC introduces the option of excluding the Organizational Unique Identifiers (OUIs) from being subjected to the DMIC check. The new cable dynamic-secret exclude command allow specific cable modems to be excluded from the Dynamic Shared Secret feature on the following Cisco CMTS platforms:

Cisco uBR7246VXR universal broadband router

Cisco uBR10012 universal broadband router

The Dynamic Shared Secret feature automatically creates a unique DOCSIS shared secret on a per-modem basis, creating a one-time use DOCSIS configuration file that is valid only for the current session. This ensures that a DOCSIS configuration file that has been downloaded for one cable modem can never be used by any other modem, nor can the same modem reuse this configuration file at a later time.

This patent-pending feature is designed to guarantee that all registered modems are using only the quality of service (QoS) parameters that have been specified by the DOCSIS provisioning system for that particular modem at the time of its registration.

For additional command information, refer to the following document on Cisco.com:

Configuring a Dynamic Shared Secret for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdmic.html

Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Testing, Troubleshooting and Diagnostic Features

The Cisco uBR10012 router supports several troubleshooting and diagnostic features:

Cisco Broadband Troubleshooter 3.2

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Dynamic Ranging

Flap List Support

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Cisco Broadband Troubleshooter 3.2

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco Broadband Troubleshooter (CBT) Version 3.2 on the Cisco uBR10012 universal broadband router, with newly supported interoperability for the following additional software features:

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Subscriber Traffic Management (STM) Version 1.1

Multiple Service Operators (MSO) provide a variety of services such as TV, video on demand, data, and voice telephony to subscribers. Network Administrators and radio frequency (RF) technicians need specialized tools to resolve RF problems in the MSO's cable plant. Cisco Broadband Troubleshooter 3.2 (CBT 3.2) is a simple, easy-to-use tool designed to accurately recognize and resolve such issues.

The user can select up to three different cable modems (CMs) under the same CMTS or three different upstreams under the same CMTS. In addition, CBT 3.2 introduces the ability to display upstreams and cable modems combined (mixed) on the same trace window for monitoring and for playback.


Note CBT 3.2 resolves the former CBT 3.1 caveat CSCee03388. With CBT 3.1, trace windows did not support the mixing of upstreams or cable modems.


For additional information about CBT 3.2, spectrum management and STM 1.1, refer to the following documents on Cisco.com:

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps819/prod_release_notes_list.html

Spectrum Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html

Subscriber Traffic Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Cisco IOS Release 12.3(9a)BC introduces support for remote spectrum management for the Cisco uBR10012 router. Cisco uBR10012 spectrum management supports interoperability with these enhancements to the Cisco CMTS in Cisco IOS 12.3(9a)BC:

Cisco Broadband Troubleshooter 3.2, supporting the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE)

Subscriber Traffic Management (STM) Version 1.1

Additional supported spectrum management functions are available on the Cisco uBR10012 router. For a complete list, and the latest information about Spectrum Management on the Cisco uBR10012 router, refer to the following document on Cisco.com:

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps819/prod_release_notes_list.html

Dynamic Ranging

Dynamic ranging is the Cisco patent-pending troubleshooting feature that supports quick restoration of service following a catastrophic plant failure. With dynamic ranging, hundreds of cable interfaces can come back online quickly, because the time that cable interfaces spend deferring contention-ranging slots is minimized. This reduces cable interface reinitialization time.

This results from use of Cisco uBR10012 router algorithms that vary the number of contention bandwidth-request minislots and request slots. Software converts unallocated minislots in the current MAC allocation and management messages—known as MAPs—into request minislots as needed. At low upstream loads, most of the MAPs of that upstream have no grants to serve, and the scheduler converts all unallocated (ungranted) minislots into request minislots. This helps ensure a low access delay for CMs at low loads due to the abundance of request opportunities. At high upstream loads, the scheduler has data grants to be served before allocating the next request region, and automatically reduces the number of request minislots.

The initial ranging slots—also called initial maintenance slots—are each about 2 msecs wide. These slots are used by CMs joining the cable network, and thus, are subject to ranging collisions. CMs use these slots for initial connectivity with the CMTS only. After the initial ranging message from the CM is received successfully, the CM no longer uses such contention-ranging slots for subsequent operations.

The CMTS periodically polls CMs with unicast station maintenance slots. Any action that involves a simultaneous bringing up of many CMs on an upstream channel—service restoration after a catastrophic power failure, online insertion and removal (OIR) for CMTS cable interface line cards, or fiber node servicing—gives rise to an impulse-ranging contention state on each of the affected upstream channels. Rebooted CMs on the upstream attempt to send initial ranging MAC messages using broadcast initial ranging slots at roughly the same time. Without theCisco uBR10012 router algorithms enabled, CMs can repeatedly collide and back off a random number of initial ranging slots independently before trying again.

With Cisco uBR10012 router algorithms enabled, the CMTS can detect such high-contention scenarios, and can increase the frequency of initial ranging slots to assist in quick resolution of ranging contention. After the high collision state is over—few persistent ranging collisions occur on the upstream—the CMTS detects this condition and switches back to the steady state mode. In the steady state mode, the frequency of initial ranging slots is a function of the upstream channel utilization. If extra upstream bandwidth is available, the CMTS allocates more initial upstream ranging slots. As soon as the MAC scheduler needs the upstream bandwidth for data grants, the MAC scheduler reduces the frequency of initial ranging slots.

For additional information about dynamic ranging on multiple components, refer to the Cisco Web site at http://www.cisco.com.

Flap List Support

The cable flap list troubleshooting feature tracks "flapping" CMs—CMs that have intermittent connectivity problems. Such connectivity problems might originate in the upstream or downstream portion of the cable plant, or originate in the CM itself. For additional information, refer to flap list information contained in the Cisco Cable Modem Termination System Feature Guide.

Online 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:

Cisco uBR10012 PRE1 and PRE2 Performance Routing Engine (PRE1 and PRE2) modules

Cisco uBR10K-MC520S/U broadband processing engine (BPE)

Cisco uBR10012 OC-48 DPT/POS WAN interface module

To view a list of hardware on the Cisco uBR10012 router that is supported by Field Diagnostics, refer to the following document:

Online Offline Diagnostics—User's Guide for Cisco uBR10012 Router Field Diagnostics

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.

Virtual Interfaces

The Cisco uBR10012 router supports the following virtual interface features, primarily in the Cisco IOS 12.3 BC release train:

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual interfaces (VI) and frequency stacking (FS) are two features that allow user-configurable MAC domains and multiple frequencies on one physical connector.

Virtual interfaces allow up to eight upstreams (USs) per downstream (DS). A virtual interface links an upstream (US) port to a physical connector.

Cisco IOS Release 12.3(9a)BC introduces Virtual Interface Support for HCCP N+1 Redundancy with the Cisco uBR10-MC5X20S/U BPE.

Frequency stacking allows two frequencies to be configured on one physical connector.

Cisco IOS Release 12.3(9a)BC introduces support for frequency stacking on the Cisco uBR10012 router.

The Cisco uBR10-MC5X20S/UBPE can be configured (initially) to match the DS and US configuration of an existing line card, and then the cable operator can modify the configurations according to their needs. This supports different DS-to-US port ratios as such combination ratios evolve (1x6 » 1x4 » 1x1). For example, the line card can be used in 1x1 configuration for a business customer and in 1x7 configuration for residential customers.

For additional information about configuring virtual interfaces and frequency stacking, refer to the following document on Cisco.com:

Virtual Interfaces and Frequency Stacking Configuration on MC5x20S and MC28U Linecards

http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml

Configuring Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/interfaces_modules/cable/broadband_processing_engines/ubr10_mc5x20s_u_h/feature/guide/mc5x2vif.html

Virtual Interface Support for HCCP N+1 Redundancy

Cisco IOS Release 12.3(9a)BC introduces support for HCCP N+1 Redundancy for virtual interfaces configured on the Cisco uBR10012 universal broadband router using the Cisco uBR10-MC5X20S/U BPE.

HCCP N+1 Redundancy is an important step toward high availability on CMTS and telecommunications networks that use broadband media. HCCP N+1 Redundancy can help limit Customer Premises Equipment (CPE) downtime by enabling robust automatic switchover and recovery in the event that there is a localized disruption in service.

Beginning with Cisco IOS Release 12.2(15)BC2a, HCCP N+1 Redundancy adds synchronization between HCCP Working interface configurations and those inherited upon switchover to HCCP Protect interfaces. This makes the configuration of both easier and switchover times faster.

For additional information about configuring virtual interfaces in HCCP N+1 redundancy on the Cisco CMTS, refer to the following document on Cisco.com:

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide_chapter09186a008015096c.html

Configuring Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/interfaces_modules/cable/broadband_processing_engines/ubr10_mc5x20s_u_h/feature/guide/mc5x2vif.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 uses bundle interface and bundle members instead of master and slave interfaces.

The virtual bundle interface is virtually defined, as with IP loopback addresses, for example.

Virtual interface bundling supports bundle information in multiple show ip interface commands.

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:

IP address

IP helper-address

source-verify and lease-timer functions

cable dhcp-giaddr (The giaddr field is set to the IP address of the DHCP client.)

Protocol Independent Multicast (PIM)

Access control lists (ACLs)

Sub-interfaces

For additional configuration information, examples, and guidelines for virtual interface bundling, refer to the following documents on Cisco.com:

Cable Interface Bundling and Virtual Interface Bundling for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

Virtual Interfaces and Frequency Stacking Configuration on MC5x20S and MC28U Line Cards

http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml

Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/interfaces_modules/cable/broadband_processing_engines/ubr10_mc5x20s_u_h/feature/guide/mc5x2vif.html

VLAN Features

Cisco IOS IEEE 802.1Q provides support for IEEE 802.1Q encapsulation for Virtual LANs (VLANs). VLANs can be implemented with Cisco IOS platforms in environments where the IEEE 802.1Q encapsulation standard is required. With the introduction of the Cisco IOS IEEE 802.1Q Support feature, Cisco IOS supported 802.1Q VLAN encapsulation, in addition to the currently supported ISL and IEEE 802.10 SDE encapsulations.

Release 12.2(11)CY adds 802.1Q VLAN support for the Cisco uBR10012 universal broadband router. Service providers can use 802.1Q VLANs on Gigabit Ethernet interfaces to provide isolation between different content providers' traffic. 802.1Q VLANs may be mapped to MPLS VPN, maintaining traffic separation across an MPLS infrastructure.

Refer to the Cisco IOS IEEE 802.1Q Support Guide for command reference information at the following URL:

http://www.cisco.com/en/US/docs/ios/12_0t/12_0t1/feature/guide/8021Q.html

VPN and Layer 2 Tunneling Features

The Cisco uBR10012 router supports multiple features and functions for virtual private networks (VPNs), to include the following:

Dynamic SID/VRF Mapping Support

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

IPv6 over L2VPN

MPLS-VPN Network Support

NetFlow Accounting Versions 5 and 8 Support

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Transparent LAN Service and Layer 2 Virtual Private Networks

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 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:

Mapping Service Flows to MPLS VPN on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/sfidmpls.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.

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 autoconfiguration. 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:

IPv6 Documentation: overview, technology, design and configuration information

http://www.cisco.com/en/US/tech/tk872/tsd_technology_support_protocol_home.html

MPLS-VPN Network Support

Using Multiprotocol Label Switching Virtual Private Network technology (MPLS VPN), service providers can create scalable and efficient private networks using a shared hybrid fiber-coaxial (HFC) network and Internet protocol (IP) infrastructure. For overview and configuration information, refer to the "Multiprotocol Label Switching" section in the Cisco IOS Switching Services Configuration Guide, Release 12.2 on Cisco.com.

NetFlow Accounting Versions 5 and 8 Support

Cisco IOS Release 12.3(9a)BC introduces support for NetFlow Accounting Versions 5 and 8 on the Cisco uBR10012 router.


Note The Cisco uBR10012 router requires the PRE2 performance routing engine module to support Netflow in Cisco IOS Release 12.3(9a)BC, and later releases in the 12.3 BC train. Also note that performance with packets-per-second (PPS) is reduced by 50% when Netflow is enabled, as two passes per packet are required.


NetFlow enables you to collect traffic flow statistics on your routing devices. NetFlow provides network administrators with access to "call detail recording" information from their data networks. Exported NetFlow data can be used for a variety of purposes, including network management and planning, enterprise accounting and departmental chargebacks, ISP billing, data warehousing and data mining for marketing purposes.

NetFlow is based on identifying packet flows for ingress IP packets. It does not require any connection-setup protocol either between routers or to any other networking device or end station and does not require any change externally—either to the traffic or packets themselves or to any other networking device.

NetFlow is completely transparent to the existing network, including end stations and application software and network devices like LAN switches. Also, NetFlow is performed independently on each internetworking device, it need not be operational on each router in the network. Using NetFlow Data Export (NDE), you can export data to a remote workstation for data collection and further processing. Network planners can selectively invoke NDE on a router or on a per-subinterface basis to gain traffic performance, control, or accounting benefits in specific network locations.

NetFlow Version 5 Features and Format

NetFlow exports flow information in UDP datagrams in one of two formats. The version 1 format was the initially released version, and version 5 is a later enhancement to add Border Gateway Protocol (BGP) autonomous system (AS) information and flow sequence numbers.

In Netflow Version 1 and Version 5 formats, the datagram consists of a header and one or more flow records. The first field of the header contain the version number of the export datagram. Typically, a receiving application that accepts either format allocates a buffer big enough for the biggest possible datagram from either format and uses the version from the header to determine how to interpret the datagram. The second field in the header is the number of records in the datagram and should be used to index through the records.

All fields in either version 1 or version 5 formats are in network byte order. Table 5 and Table 6 describe the data format for version 1, and Table 7 and Table 8 describe the data format for version 5.

We recommend that receiving applications check datagrams to ensure that the datagrams are from a valid NetFlow source. We recommend you first check the size of the datagram to make sure it is at least long enough to contain the version and count fields. Next we recommend you verify that the version is valid (1 or 5) and that the number of received bytes is enough for the header and count flow records (using the appropriate version).

Because NetFlow export uses UDP to send export datagrams, it is possible for datagrams to be lost. To determine whether or not flow export information is lost, the version 5 header format contains a flow sequence number. The sequence number is equal to the sequence number of the previous plus the number of flows in the previous datagram. After receiving a new datagram, the receiving application can subtract the expected sequence number from the sequence number in the header to get the number of missed flows.

Table 1-8 lists the byte definitions for Netflow Version 5 header format.

Table 1-8 Netflow Version 5 Header Format

Bytes
Content
Description

0-3

version and count

Netflow export format version number and number of flows exported in this packet (1-30).1

4-7

SysUptime

Current time in milliseconds since router booted

8-11

unix_secs

Current seconds since 0000 UTC 1970.

12-15

unix_nsecs

Residual nanoseconds since 0000 UTC 1970.

16-19

flow_sequence

Sequence counter of total flows seen.

20-23

reserved

Unused (zero) bytes.

1 Netflow Version 5 export packets (set with ip flow-export command) allow the number of records stored in the datagram to be a variable between 1 and 30.


Table 1-9 lists the byte definitions for Version 5 flow record format.

Table 1-9 Netflow Version 5 Flow Record Format

Bytes
Content
Description

0-3

srcaddr

Source IP address.

4-7

dstaddr

Destination IP address.

8-11

nexthop

Next hop router's IP address.

12-15

input and output

Input and output interface's SNMP index.

16-19

dPkts

Packets in the flow.

20-23

dOctets

Total number of Layer 3 bytes in the flow's packets.

24-27

First

SysUptime at start of flow.

28-31

Last

SysUptime at the time the last packet of flow was received.

32-35

srcport and dstport

TCP/UDP source and destination port number or equivalent.

36-39

pad1, tcp_flags, prot, and tos

Unused (zero) byte, Cumulative OR of TCP flags, IP protocol (for example, 6=TCP, 17=UDP), and IP type-of-service.

40-43

src_as and dst_as

AS of the source and destination, either origin or peer.

44-47

src_mask, dst_mask, and pad2

Source and destination address prefix mask bits, pad 2 is unused (zero) bytes.


Netflow Version 8 Features and Format

NetFlow exports flow information in UDP datagrams in one of several formats. Version 8, a new data export version, has been added to support data exports from aggregation caches. Version 8 allows for export datagrams to contain a subset of the usual version 5 export data, which is valid for a particular aggregations scheme type.

Figure 1-4 illustrates the Netflow Version 8 header format.

Figure 1-4 Version 8 Header Format

Table 3 lists definitions for terms used in the version 8 header.

Table 1-10 Terms and Definitions for Version 8 Headers

Term
Definition

Version

The flow export format version number. In this case, the number is "8".

Count

The number of export records in the datagram.

System Uptime

The number of milliseconds since the router was last booted.

UNIX Seconds

The number of seconds since 0000 Universal Time Code (UTC) 1970.

UNIX Nanoseconds

The number of residual nanoseconds since 0000UTC 1970.

Sequence Number

Sequence counter of total flows sent for this export stream.

Engine Type

The type of switching engine. RP=0 and LC=1.

Engine ID

The slot number of the NetFlow switching engine.

Aggregation

The type of aggregation scheme being used.

Aggregation Version

The aggregation subformat version number. The current value is "2".


Additional Information about Netflow on the Cisco CMTS

For additional information about configuring Netflow Accounting on Cisco CMTS, refer to the following documents on Cisco.com:

Cisco IOS NetFlow documentation home page

http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html

Cisco IOS NetFlow White Papers

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/prod_white_paper0900aecd80406232.html

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Cisco IOS 12.3(9a)BC introduces support for the Transparent LAN Service over Cable feature on the Cisco 10012 router. This feature enhances existing Wide Area Network (WAN) support to provide more flexible Managed Access for multiple Internet service provider (ISP) support over a hybrid fiber-coaxial (HFC) cable network.

This feature allows service providers to create a Layer 2 tunnel by mapping an upstream service identifier (SID) to an IEEE 802.1Q Virtual Local Area Network (VLAN).

For additional information about configuring TLS on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:

Transparent LAN Service over Cable

http://www.cisco.com/en/US/docs/cable/cmts/feature/tls-cmts.html

Cisco TLS for the Cisco uBR10012 router requires the PRE2 performance routing engine module with Cisco IOS Release 12.3(9a)BC or a later release in the Cisco IOS 12.3BC train.

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:

When the TLS feature is used with Layer 2 VPNs, the participating cable modems must have the Baseline Privacy Interface security feature (BPI) enabled. Otherwise, the Cisco CMTS drops such Layer 2 traffic in the upstream or downstream.

Information about Customer Premises Equipment (CPE) does not display in the output of the show cable modem command.

Refer to the following document on Cisco.com for additional TLS information:

TLS Over Cable - TAC Document #60027

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_configuration_example09186a008029160d.shtml