-
Cisco uBR7200 Series Software Configuration Guide
-
Preface
-
Chapter 1: Overview of Cisco uBR7200 Series Software
-
Chapter 2: Configuring the Cable Modem Termination System for the First Time
-
Chapter 3: Configuring Cable Modem Interface Features
-
Chapter 4: Configuring DOCSIS Baseline Privacy Interface on the Cisco uBR7200 Series
-
Chapter 5: Managing Cable Modems on the Hybrid Fiber-Coaxial Network
-
Chapter 6: Configuring Basic Broadband Internet Access
-
Chapter 7: Overview of the Cisco Network Registrar for the Cisco uBR7200 Series
-
Chapter 8: Troubleshooting the System
-
Appendix A: Installing or Upgrading Cisco IOS Software
-
Appendix B: Resolving Common Image Installation Problems
-
Appendix C: Viewing Sample Configuration Files
-
Appendix D: Frequency Allocation Tables
-
Appendix E: Configuration Register Information for the Cisco uBR7200 Series Universal Broadband Routers
-
Table Of Contents
Overview of Cisco uBR7200 Series Software
Cisco IOS Releases and Images for the Cisco uBR7200 Series
Determining Your Cisco IOS Software Release
Upgrading to a New Software Release
12.3 BC Release Train Images and Requirements
12.2 BC Release Train Images and Requirements
12.2 CX Images and Requirements
12.1 EC Images and Requirements
Cisco uBR7200 Series Chassis Overview
Cisco uBR7200 Series Universal Broadband Routers
Cisco uBR7246 VXR Universal Broadband Router
Cisco uBR7246 Universal Broadband Router
Cisco uBR7223 Universal Broadband Router
Supported Hardware on the Cisco uBR7200 Series
Network Interface Port Adapters
Cisco uBR7200 Series Router Configuration Overview
Port Adapter and Line Card Slot and Logical Interface Numbering
Cable Interface Line Card Slots
Supported Software Features for the Cisco uBR7200 Series
Cisco uBR7200 Series Router Features and Cisco IOS Releases
Cisco uBR7200 Series Router Configuration Tools
Cable Interface Setup Facility
Cable Interface Extended Setup Facility
Internal Modem Configuration File Editor
Manual Configuration Mode for the Cisco uBR7200 Series CMTS
Virtual Interface Support and Frequency Stacking Support
Cisco IOS Command-Line Enhancements
Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements
Cisco Quality of Service Features
Cisco Network-Based Application Recognition (NBAR)
DHCP Servers and Feature Support
Configurable Leasequery Server
DHCP MAC Address Exclusion List for cable-source verify dhcp Command
DOCSIS 1.0 Baseline Privacy Interface Encryption and Encrypted Key Exchange
DOCSIS 1.0 Concatenation Override Featurette
DOCSIS Quality of Service Enhancements Prior to DOCSIS 1.1
DOCSIS Customer Premises Equipment Configurator
Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems
Unsolicited Grant Service (CBR-scheduling) on the Upstream
Baseline Privacy Interface Plus (BPI+)
Cable Modulation Profile Default Templates
DHCP Client ID/Remote ID Options
DHCP, Time of Day (ToD) and TFTP Servers
DOCSIS 1.1 Quality of Service Features
DOCSIS 1.1 Two-way Transmission (Cisco uBR7246VXR Router)
Downstream Rate Shaping with IP Type of Service Bits
Optional Upstream Scheduler Modes
Cisco DDC (Dual DOCSIS Channel)
DSX Messages and Synchronized PHS Information
Globally Configured HCCP 4+1 Redundancy on the Cisco uBR7246VXR Router
HCCP Support for the Cisco uBR-MC16S Cable Interface Line Card
High Availability Features in Cisco IOS Release 12.3(13a)BC
High Availability Support for Encrypted IP Multicast
IF Muting for HCCP N+1 Redundancy
Access Control List Support for COPS Intercept
COPS TCP Support for the Cisco Cable Modem Termination System
Service Independent Intercept (SII) Support on the Cisco uBR7200 Series
IP Broadcast and Multicast Features
Multicast QoS Support on the Cisco uBR7246VXR CMTS
Cable Interface Bundling and Cable Subinterfaces
Configurable Alternate Termination System Information Messages
IP Enhanced IGRP Route Authentication
IP Network Address Translation/Port Address Translation
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
Router-Port Group Management Protocol
Supported Protocols on the Cisco uBR7200 Series
Admission Control for the Cisco CMTS
cable map-advance Command Enhancements
Cisco IOS Internationalization
Downstream Load Balancing Distribution with Upstream Load Balancing
Dynamic Channel Change (DCC) for Loadbalancing
Load Balancing for the Cisco CMTS
Management Information Base (MIB) Changes and Enhancements
MAX-CPE Override for Cable Modems
Per-Modem Error Counter Enhancements
Pre-equalization Control for Cable Modems
Subscriber Traffic Management (STM) Version 1.1
DOCSIS Set-top Gateway (DSG) 1.0
Advanced-mode DOCSIS Set-Top Gateway Issue 1.1
Advanced-mode DOCSIS Set-Top Gateway Issue 1.2
IP Multicast Load Splitting across Equal-Cost Paths
IP Multicast over ATM Point-to-Multipoint Virtual Circuits
IP Multicast over Token Ring LANs
PacketCable and Voice Support Features
Automated Double Authentication
Cable Modem and Multicast Authentication Using RADIUS
Cable Source Verification (cable source-verify Command)
Cisco IOS Firewall Feature Set
Cisco IOS Firewall Feature Enhancements
Dynamic Shared Secret for DOCSIS
Dynamic Shared Secret (DMIC) with OUI Exclusion for DOCSIS
Named Method Lists for AAA Authorization & Accounting
Per-Modem Filters (Per-Modem and Per-Host Access Lists)
Redirect-Number Support for RADIUS and TACACS+ Servers
Secure Shell (SSH) Supported in "k1" Images for Cisco uBR7200
Vendor-Proprietary RADIUS Attributes
SNMP Features and Enhancements
LinkUp/Down Traps Support (RFC 2233)
SNMP Management Information Base (MIB) Enhancements
SNMP MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC
Spectrum Management and Advanced Spectrum Management Features
Cable Modulation Profile Default Templates
Guided and Scheduled Spectrum Management
Spectrum Management Enhancements in Cisco IOS Release 12.3(9a)BC
Testing, Troubleshooting and Diagnostic Features
Cable Downstream Frequency Override
Cisco Broadband Troubleshooter (CBT) 3.2
Cisco CMTS Static CPE Override
Virtual Interface Bundling on the Cisco uBR-MC28/U BPE
HSRP over ISL in Virtual LAN Configurations
VPN and Layer 2 Tunneling Features
Dynamic SID/VRF Mapping Support
IP Type-of-Service and Precedence for GRE Tunnels
Mapping Service Flows to MPLS-VPN
MPLS VPN Support for Subinterfaces and Cable Interface Bundles
Overlapping Subinterface IP Addresses
Transparent LAN Services (TLS) and L2 Tunneling ATM/SIDs
Transparent LAN Services (TLS) and L2 Virtual Private Networks
WAN Optimization and Services Features
Bandwidth Allocation Control Protocol (BACP)
Closed User Group Selection Facility Suppress Option
Enhanced Local Management Interface (ELMI)
Microsoft Point-to-Point Compression (MPPC)
National ISDN Switch Types for BRI and PRI
PPPoE Termination Support on Cable Interfaces
X.25 Switching Between PVCs and SVCs
DOCSIS and CMTS Interoperability
DOCSIS-Compliant Downstream Signals
DOCSIS-Compliant Upstream Signals
Overview of Cisco uBR7200 Series Software
The Cisco uBR7200 series uses Cisco IOS® software to offer enhanced stability, features, performance and investment protection. This chapter summarizes system and software features of the Cisco uBR7200 series Cable Modem Termination System (CMTS). This chapter contains the following sections:
"Cisco IOS Releases and Images for the Cisco uBR7200 Series," page 2
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.
Describes the Cisco uBR7200 series routers, and their supported hardware features and interoperability.
"Cisco uBR7200 Series Router Configuration Overview," page 15
Provides an overview of the hardware and interfaces that typically require configuration through Cisco IOS software.
"Supported Software Features for the Cisco uBR7200 Series," page 22
Describes the features and configuration utilities that are available on the Cisco uBR7200 series.
Provides an overview of DOCSIS NTSC and EuroDOCSIS cable plants, DOCSIS-compliant signals, and traffic engineering.
Cisco IOS Releases and Images for the Cisco uBR7200 Series
This section describes the supported releases, latest images, memory requirements, and major software features for the following Cisco IOS software:
•
Determining Your Cisco IOS Software Release
•
•
•
•
•
To configure the CMTS for the first time, refer to Chapter 2, "Configuring the Cable Modem Termination System for the First Time."
For additional release information, refer to the Cisco uBR7200 Series Software Release Notes on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/release/notes/12_3bc/123BCu72.html
Determining Your Cisco IOS Software Release
To determine the version of Cisco IOS software running on the Cisco uBR7200 series universal broadband router, log in to the router and enter the show version command in User or privileged EXEC mode.
Router> show versionCisco Internetwork Operating System SoftwareIOS (tm) Cisco IOS 12.2 BC Software (ubr7200-is-mz), Version Cisco IOS Release 12.2(4)BC1, RELEASE SOFTWARE
Note
Upgrading to a New Software Release
An upgrade is an order placed for a Cisco IOS feature set that contains more functionality than the feature set that you are replacing. An upgrade is not an "update." An update consists of installing a more recent version of the same feature set.
•
For general information about upgrading to a new software release, refer to the Cisco IOS Upgrade Ordering Instructions on Cisco.com. Also refer to Appendix A, "Installing or Upgrading Cisco IOS Software."
12.3 BC Release Train Images and Requirements
The Cisco 12.3 BC release train is the latest Cisco IOS release train to support the Cisco uBR7200 Series, and emphasizes additional features and performance specifically for the Cisco uBR7246VXR universal broadband router.
Table 1-2 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7200 series universal broadband routers for Cisco IOS Release 12.3(9a)BC. Cisco uBR7200 series routers are only available with a 48 MB or 128 MB of Flash disk memory on the I/O Controller cards. The UBR7200-NPE-G1 uses compact Flash disk only.
Note
The image subset legend for Table 1-2 is as follows:
•
•
•
•
•
Note
Note
12.2 BC Release Train Images and Requirements
Note
The 12.2 BC train is an interim release train that provides certified DOCSIS 1.1 two-way support on the Cisco uBR7246 VXR universal broadband router, along with support for selected new features. The latest release in this train, Cisco IOS Release 12.2(4)BC1, provides a migration path from the earlier Cisco IOS 12.2 XF releases, which included a subset of the features supported in these Cisco IOS release trains:
•
•
•
Table 1-2 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7200 series universal broadband routers for Cisco IOS Release 12.2(15)BC1 and 12.2(15)BC2a. Cisco uBR7200 series routers are available with 48 MB or 128 MB of Flash disk memory on the I/O Controller cards. The UBR7200-NPE-G1 uses compact Flash disk only.
Note
Note
Table 1-2 Memory Recommendations for the Cisco uBR7200 Series Routers, Cisco IOS Release 12.2(15)BC1 and 12.2(15)BC2a Feature Sets
Flash Memory
DRAM Memory
FromDOCSIS Two-Way
ubr7200-p-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
DOCSIS Two-Way IP Plus
ubr7200-is-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
DOCSIS Two-Way with BPI
ubr7200-k8p-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
DOCSIS Two-Way IP Plus
with BPIubr7200-ik8s-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
DOCSIS Two-Way 3DES
ubr7200-k9p-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
DOCSIS Two-Way 3DES IP Plus
ubr7200-ik9s-mz
16 MB Flash
32 MB Flash1
128 MB DRAM
RAM
Boot Image
UBR7200 Boot Image
ubr7200-kboot-mz
None
None
—
UBR7200 Boot Image
ubr7200-boot-mz
None
None
—
1 32 MB of Flash is required for Cisco IOS Release 12.2(15)BC2a and later releases in the Cisco IOS BC train.
The image subset legend for Table 1-2 is as follows:
•
•
•
•
•
Note
Note
12.2 CX Images and Requirements
The 12.2 CX releases are based on Cisco IOS Release 12.2(15)BC1, which is a child of Cisco IOS Release 12.2(15)T. The 12.2 BC train is an interim release train that provides DOCSIS 1.1 two-way support, along with fixes for software caveats and support for selected new features.
The latest image in the 12.2 CX release train, Cisco IOS Release 12.2(15)CX1, provides two different boot images for the Cisco uBR7200 series routers:
•
The "kboot" version of the boot image is a new version of the boot image software that can run only on the Cisco uBR7200-NPE-G1 processor and the UBR7200-I/O-2FE/E I/O controller, because it is too large to load on the other I/O controllers. This image contains support for almost all supported port adapters, allowing the Cisco uBR7246VXR router to boot over almost any type of WAN interface.
•
The "boot" version of the boot image is small enough to be loaded on I/O controllers with 4MB of Flash memory, but it supports only Ethernet, FastEthernet, Gigabit Ethernet, OC POS, and a limited number of ATM port adapters. If you are using a serial port adapter or most ATM port adapters, you will not be able to boot over the WAN interface.
This difference in boot images affects only the ability of the Cisco uBR7246VXR router to boot over the WAN interface. When the router has successfully loaded the Cisco IOS software, it has connectivity over all of the port adapters that this particular version of Cisco IOS software supports.
Table 1-3 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7200 series universal broadband routers for Cisco IOS Release 12.2(15)CX1. Cisco uBR7200 series routers are only available with a 48 MB or 128 MB of Flash disk memory on the I/O Controller cards. The UBR7200-NPE-G1 uses only compact Flash disk.
Flash disks, an alternative to linear Flash memory, are Flash memory-based devices that can be used as file storage media in the PCMCIA card slots of the I/O Controllers. Each I/O Controller has two PCMCIA slots and can be configured with up to 256 MB of Flash disk memory.
The image subset legend for Table 1-3 is as follows:
•
•
•
•
•
12.1 EC Images and Requirements
The 12.1 EC train is the Cisco cable-specific early deployment release train that introduces several new feature sets, support for the Cisco uBR-MC28C cable interface line card, and several new software features.
Table 4 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7200 series universal broadband routers for the latest Cisco IOS Release 12.1(20)EC1. Cisco uBR7200 series routers support a 16-MB or 20-MB Type II PCMCIA Flash memory card.
Table 4 Memory Recommendations for the Cisco uBR7200 Series Routers, Cisco Release 12.1(20)EC1 Feature Sets
Flash
Memory
DRAM
Memory
FromDOCSIS Two-Way
ubr7200-p-mz
16 MB Flash
128 MB DRAM
RAM
DOCSIS Two-Way IP Plus
ubr7200-is-mz
16 MB Flash
128 MB DRAM
RAM
DOCSIS Two-Way with BPI
ubr7200-k1p-mz
16 MB Flash
128 MB DRAM
RAM
DOCSIS Two-Way IP Plus
with BPIubr7200-ik1s-mz
16 MB Flash
128 MB DRAM
RAM
DOCSIS IP Plus Telco Return
ubr7200-ist-mz
16 MB Flash
128 MB DRAM
RAM
DOCSIS IP Plus Telco Return
with BPIubr7200-ik1st-mz
16 MB Flash
128 MB DRAM
RAM
UBR7200 Boot Image1
ubr7200-boot-mz
None
None
—
1 The 12.1 EC UBR7200 boot image is provided for the IUBR7200-I/O-2FE/E input/output controller, which must use the Cisco IOS 12.1(10)EC1 or later 12.1 EC release boot image. This image cannot be used on any other I/O controllers.
The image subset legend for Table 4 is as follows:
•
•
•
•
•
Note
Cisco uBR7200 Series Chassis Overview
The Cisco uBR7200 series universal broadband routers allow high-speed data services to be packaged similar to cable TV service or video fare. Cisco uBR7200 Series equipment supports data and digitized voice connectivity between Internet Protocol (IP) hosts and connected subscribers using a bidirectional cable TV and IP backbone.
Note
For international cable plants that use 8-MHz Phase Alternating Line (PAL) or Systeme Electronique Couleur Avec Memoire (SECAM) channel plans, Cisco uBR7200 Series equipment supports bidirectional transfer of traffic between the Cable Modem Termination System (CMTS) and EuroDOCSIS-based CMs or set top box (STB) units with integrated EuroDOCSIS modems.Cable companies and Internet service providers (ISPs) can allocate radio frequency (RF) channel capacity for Internet access, Virtual Private Network (VPN), or Voice over IP (VoIP) services using a hybrid fiber/coax (HFC) or all-coax cable plant. Cisco currently provides three router-based DOCSIS CMTS solutions that offer a wider feature set and better manageability than bridge-based systems.
•
•
•
Note
Cisco cable interface line cards serve as the RF cable TV interfaces, supporting downstream and upstream signal combining and splitting arrangements. The cards currently require external upconverters to connect to the cable system. Cisco port adapters connect to the IP backbone and external networks. Your cable plant, combined with your planned and installed subscriber base, service offering, and external network connections, determine the Cisco uBR7200 Series chassis, cable interface line cards, port adapters, and other components you use.
Data is modulated or demodulated using either of the following two methods:
•
NTSC uses a 6 MHz-wide modulated signal with an interlaced format of 25 frames per second and 525 lines per frame. NTSC is compatible with CCIR Standard M. PAL, used in West Germany, England, Holland, Australia, and several other countries.
Note
•
PAL uses a 625-line scan picture delivered at 25 frames per second where the color carrier phase definition changes in alternate scan lines. SECAM uses an 819 line scan picture that provides better resolution than PAL's 625-line and NTSC's 525-line.
The MC16E uses the EuroDOCSIS J.112 (Annex A) standard, CableLabs ECR RFI-R-98036, which is similar to the Digital Audio Video Council/Digital Video Broadcast (DAVIC/DVB) ITU J.83 Annex A physical layer. Cable companies can support data, voice, and video services with DOCSIS-based CMs or set top boxes (STBs) that contain integrated EuroDOCSIS modems.
Caution
Note
The DOCSIS Radio Frequency (RF) specification defines the RF communication paths between the CMTS and CMs (or CMs in STBs). The DOCSIS RF specification defines the physical, link, and network layer aspects of the communication interfaces. It includes specifications for power level, frequency, modulation, coding, multiplexing, and contention control. Cisco offers products that support all DOCSIS error correction encoding and modulation types and formats, and that support DOCSIS Annex B or EuroDOCSIS Annex A operations.
Cisco uBR7200 Series Universal Broadband Routers
The Cisco uBR7200 series universal broadband routers are based on the Data-over-Cable Service Interface Specification (DOCSIS) standards. Each is designed to be installed at a cable operator's headend facility or distribution hub and to function as the cable modem termination system (CMTS) for subscriber-end devices such as the Cisco uBR905 and Cisco uBR925 cable access routers, and other DOCSIS-compliant CMs and set-top boxes (STBs).
Cisco uBR7200 series universal broadband routers allow two-way transmission of digital data and Voice over IP (VoIP) traffic over a hybrid fiber-coaxial (HFC) network. For cable plants not fully upgraded to support two-way cable transmission, the routers support DOCSIS-compliant telco return, where the cable modem's return path to the CMTS uses a dial-up telephone line connection instead of an upstream channel over the coaxial cable. The telco-return delivery mechanism enables cable operators to accelerate deployment of high-speed data services before the cable systems are upgraded to two-way plants.
The Cisco uBR7200 series routers support IP routing with a wide variety of protocols and combinations of Ethernet, Fast Ethernet, Gigabit Ethernet, serial, High-Speed Serial Interface (HSSI), Packet over SONET (POS) OC-3 and OC-12c, and Asynchronous Transfer Mode (ATM) media.
Cisco uBR7246 VXR Universal Broadband Router
The Cisco uBR7246VXR offers an industry-proven CMTS and carrier-class router in a scalable platform with a high-performance network processing engine to support data, voice, and video services for medium to large network installations.
The Cisco uBR7246 VXR provides the following major hardware features:
•
•
•
•
•
•
Note
Cisco uBR7246 Universal Broadband Router
The Cisco uBR7246 offers an industry-proven CMTS and carrier-class router in a scalable platform to support data, voice, and video services for medium to large network installations. The Cisco uBR7246 provides the following major hardware features:
•
•
•
•
•
•
Cisco uBR7223 Universal Broadband Router
The Cisco uBR7223 is a cost-effective, scalable interface between subscriber CMs and the backbone data network, and is designed specifically for small to medium network installations.
The Cisco uBR7223 provides the following major hardware features:
•
•
•
•
•
•
Supported Hardware on the Cisco uBR7200 Series
Table 1-5 provides a quick overview of the major hardware features of the Cisco uBR7200 series routers.
Note
The UBR7200-NPE-G1 does not require that an I/O controller be installed. Refer to the Cisco uBR7200 Series Software Release Notes on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/release/notes/12_3bc/123BCu72.html
Network Processing Engines
The Cisco uBR7246 VXR supports the following Network Processing Engines (NPEs):
•
•
•
•
The Cisco uBR7223 and the Cisco uBR7246 support the following Network Processing Engines (NPE) :
•
•
•
Note
For more information, refer to the following resources on Cisco.com:
•
I/O Controllers
The Cisco uBR7200 series universal broadband routers support the following input/output (I/O) controllers:
•
–
–
–
–
•
–
–
–
–
–
•
–
–
–
Note
http://www.cisco.com/en/US/products/hw/cable/ps2217/prod_eol_notice09186a00800a470d.html
Note
Network Interface Port Adapters
The Cisco uBR7200 series routers support multiple port adaptors with Ethernet, Gigabit Ethernet and Serial versions. Enhancements and options are available in multiple Cisco IOS Software release trains. For the latest information about supported port adaptors, refer to Cisco uBR7200 Series Software Release Notes on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/release/notes/12_3bc/123BCu72.html
Note
Note
Cable Interface Line Cards
The Cisco uBR7200 series supports the following cable interface line cards, all of which provide connection to the hybrid fiber-coaxial (HFC) network.
Table 1-6 provides a quick overview of the cable interface line cards that are supported with Cisco uBR7200 series routers.
For the latest information about supported cable interface line cards, refer to Cisco uBR7200 Series Software Release Notes on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/release/notes/12_3bc/123BCu72.html
System Interoperability
This section describes guidelines about the interoperability of certain features in the Cisco uBR7200 series universal broadband routers. Additional DOCSIS interoperability is described in the "Supported Software Features for the Cisco uBR7200 Series" section.
Cable Modem Interoperability
The Cisco uBR7200 series interoperates with the following cable modems:
•
•
To support telco return, use a Cisco uBR7200 series software image that contains "t" in its file name. The telco-return cable modem must be DOCSIS-based or compliant and must be configured to support telco return.
Note
•
EuroDOCSIS operation support includes 8-MHz Phase Alternating Line (PAL) or Systeme Electronique Couleur Avec Memoire (SECAM) channel plans.
Clock Synchronization
The Cisco uBR7200 series support clock hardware and software to enable high-quality delivery of IP telephony services through synchronized data transmissions. To support the clock feature set, a Cisco uBR7246 VXR chassis must be used. The Cisco uBR7246 VXR must contain a clock card and an MC16S, MC16E, or MC28C cable interface line card. Only the MC16S, MC16E, and MC28C cable interface line cards support the external clock reference from the clock card to distribute that signal to CMs or STBs attached to the specific network segments. A chassis configured with an MC16S or MC16E cable interface line card must be running Cisco IOS Release 12.1(2)EC1 or higher. A chassis configured with an MC28C cable interface line card must be running Cisco IOS Release 12.1(3a)EC1 or higher.
Each cable modem must also support VoIP applications and the clock reference feature set to enable synchronized timing. The Cisco uBR924 cable access router, running Cisco IOS Release 12.0(7)T or later, supports the clock reference feature set automatically.
Cisco uBR7200 Series Router Configuration Overview
This section describes Cisco uBR7200 series router features that require software configuration, and summarizes these features of the Cisco uBR7200 series router:
•
•
•
Refer to the "Cisco uBR7200 Series Router Configuration Tools" section for additional configuration utilities.
Port Adapter and Line Card Slot and Logical Interface Numbering
For Cisco uBR7200 series components, the slot number is the chassis slot in which a port adapter or a cable interface card is installed. The logical interface number is the physical location of the interface port on a port adapter. Numbers on a Cisco uBR7200 series router begin with 0. Using a Cisco uBR7246 to illustrate, slot/port positioning is as follows:
•
•
•
To configure the system, define the Cisco uBR7200 series interfaces, using the interface type slot/port commands:
•
•
•
Configuring Cisco cable interface line cards is particularly important because these components serve as the cable TV RF interfaces. Configuration involves the following tasks for each interface:
•
Router (config-int)# cable downstream frequency down-freq-hz
Note
The digital carrier frequency is specified to be the center of a 6 or 8 MHz channel based on your channel plan. To illustrate for NTSC channel plans, EIA channel 95 spans 90.00 to 96.00 MHz. The center frequency is 93.000 MHz which is the digital carrier frequency that should be configured as the downstream frequency.
Tip
•
Router (config-int)# no shutdownThe particular downstream port LED should light.
•
Tip
The cable interface will not operate until you either set a fixed upstream frequency or create and configure a spectrum group. Enter the fixed center frequency for your upstream RF carrier in Hz and specify a port number from 0 to 5:
Router (config-int)# cable upstream port frequency up-freq-hz
Note
•
•
Router (config-int)# no cable upstream port shutdownThe specified upstream port LED lights.
Repeat the above for each upstream port to activate.
•
Router# show running-config•
Router# copy running start•
•
MAC-Layer Addressing
The Media Access Control (MAC)-layer or hardware address is a standardized data link layer address required for certain network interface types. These addresses are not used by other devices in the network; they are specific and unique to each port. The Cisco uBR7200 series uses a specific method to assign and control the MAC-layer addresses for port adapters.
All LAN interfaces (ports) require unique MAC-layer addresses, also known as hardware addresses. Typically, the MAC address of an interface is stored on a memory component that resides directly on the interface circuitry; however, the online insertion and removal (OIR) feature requires a different method. The OIR feature lets you remove a port adapter or cable interface card and replace it with another identically configured one. If the new port adapter or cable interface card matches the port adapter or cable interface card you removed, the system immediately brings it online.
To support OIR, an address allocator with a unique MAC address is stored in an EEPROM on the universal broadband router midplane. Each address is reserved for a specific port and slot in the router regardless of whether a port adapter or a cable interface card resides in that slot.
Note
Caution
The MAC addresses are assigned to the slots in sequence. The first addresses are assigned to port adapter slot 0 and slot 1, and the next addresses are assigned to port adapter slot 2 through cable interface card slot 6. This address scheme allows you to remove port adapters or cable interface cards and insert them into other universal broadband routers without causing the MAC addresses to move around the network or be assigned to multiple devices.
Storing the MAC addresses for every slot in one central location means the addresses stay with the memory device on which they are stored.
Cable Interface Line Cards
As of the date of this publication, the following Cisco cable interface cards can be installed in a Cisco uBR7200 series router:
•
–
–
Note
Because the FPGA version of the MC11 card supports only one upstream modulation and channel width, you cannot define an upstream modulation profile for the card. The default modulation profile 1 cannot be changed when using the FPGA version of the MC11 card.•
•
•
–
Note
–
•
The MC16S includes the ability to scan portions of the upstream spectrum for clean channels of varying widths. A daughtercard on the MC16S samples the 5-to-42 MHz upstream spectrum and initiates a frequency hop if an administrator-defined threshold value for offline CMs is met. The threshold value is contained in the router's configuration file. When the threshold value is reached, the spectrum management daughtercard takes a snapshot of the available upstream spectrum and passes this information to the Cisco IOS software where it is analyzed for indications of significant ingress or impulse noise. From this analysis, the Cisco IOS software draws informed conclusions on the cleanest portion(s) of the upstream frequency spectrum to switch to and initiates a frequency hop.
•
Note
The cable interface cards can be configured in a number of different upstream combinations based on the card used, your cable network, and the anticipated subscription and service levels. Table 1-7 shows the DOCSIS and EuroDOCSIS data rates.
Cable Interface Line Card Slots
To display information about a specific cable interface card slot's downstream channel, use the show interfaces cable command with the cable modem line card's slot number and downstream port number in the following format:
show interfaces cable slot/downstream-port [downstream]
Use the slot number and downstream port number to display information about a downstream interface. You can abbreviate the command to sh int c. The following example illustrates the display for downstream channel port 0 in cable interface slot 3 of a Cisco uBR7246:
Router# sh int c 3/0Cable3/0 is up, line protocol is upHardware is CMTS, address is 0009.0ed6.ee18 (bia 0009.0ed6.ee18Internet address is 1.1.1.1/24MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, rely 255/255, load 1/255Encapsulation MCNS, loopback not set, keepalive not setARP type: ARPA, ARP Timeout 04:00:00Last input 00:00:00, output 00:00:00, output hang neverLast clearing of "show interface" counters neverQueueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 41000 bits/sec, 45 packets/sec5 minute output rate 43000 bits/sec, 45 packets/sec1616534 packets input, 184284660 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort1616534 packets output, 184284660 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outTo display information about a specific cable interface card slot's upstream channel, use the show interfaces cable command with the cable modem card's slot number, downstream port number, and upstream port number in the format of show interfaces cable slot/downstream-port [upstream] upstream-port. Use the slot number, downstream port number, and upstream port number to display information about an upstream interface. You can abbreviate the command to sh int c.
The following example shows the display for upstream channel port 0 in cable interface slot 3 of a Cisco uBR7246 that is turned up:
Router# sh int c 3/0 0Cable6/0: Upstream 0 is upReceived 3699 broadcasts, 0 multicasts, 28586 unicasts0 discards, 0 errors, 0 unknown protocol21817 packets error-free, 2371 corrected, 8097 uncorrectable0 noise, 0 microreflectionsCBR_queue_depth: [not implemented], ABR_queue_depth: [not implemented],UBR[1]_queue_depth: 0, UBR[2]_queue_depth: 0,UBR[3]_queue_depth: 0, POLLS_queue_depth: [not implemented]ADMIN_queue_depth: [not implemented]Last Minislot Stamp (current_time_base):190026 FLAG:1Last Minislot Stamp (scheduler_time_base):200706 FLAG:1Interfaces and Physical Ports
Table 1-8 maps the cable interface card's interfaces and physical ports. The cards can be configured in a number of different upstream combinations.
Port Adapter Slots
You can display information on a specific port adapter or all port adapters in the Cisco uBR7200 series. To display information about all port adapter slots, use the show interfaces command. To display information about a specific port adapter slot, use the show interfaces command with the port adapter type and slot number in the format of show interfaces [type slot/port].
Tip
The follow example illustrates the show interfaces command with status information (including the physical port adapter number) for each port adapter and cable interface card in the Cisco uBR7246 router:
Router# sh intFastEthernet0/0 is administratively up, line protocol is upHardware is DEC21140, address is 0000.0000.0000 (bia 0000.0000.0000)Internet address is 1.1.1.3 MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 (display text omitted) Hssi1/0 is administratively down, line protocol is downHardware is MIF68840_MM, address is 0000.0000.0000 (bia 0000.0000.0000) Internet address is 1.1.1.0MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255(display text omitted)Ethernet2/0 is administratively up, line protocol is up Hardware is AmdP2, address is 0000.0000.0000 (bia 0000.0000.0000)Internet address is 1.1.1.7MTU 1500 bytes, BW 100000 Kbit, DLY 1000 usec, rely 255/255, load 1/255 (display text omitted)Cable3/0 is up, line protocol is upHardware is CMTS, address is 0009.0ed6.ee18 (bia 0009.0ed6.ee18)Internet address is 1.1.1.1/24MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, rely 255/255, load 1/255(display text omitted)You can also use arguments such as the interface type (Ethernet, Fast Ethernet, ATM, serial, HSSI, Packet-over-SONET, and so forth) and the port address (slot/port) to display information about a specific port adapter interface only. The following example shows such a display:
Router# sh int f1/0FastEthernet1/0 is up, line protocol is upHardware is AmdFE, address is 0030.7bfa.a81c (bia 0030.7bfa.a81c)Internet address is 111.0.1.18/30MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation ARPA, loopback not setKeepalive set (10 sec)Full-duplex, 100Mb/s, 100BaseTX/FXARP type:ARPA, ARP Timeout 04:00:00Last input 00:00:01, output 00:00:02, output hang neverLast clearing of "show interface" counters neverQueueing strategy:fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets put, 230925 bytesReceived 146107 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored0 watchdog0 input packets with dribble condition detected0 packets put, 284529 bytes, 0 underruns0 output errors, 0 collisions, 10 interface resets0 babbles, 0 late collision, 0 deferred0 lost carrier, 0 no carrier0 output buffer failures, 0 output buffers swapped outSupported Software Features for the Cisco uBR7200 Series
This section summarizes Cisco uBR7200 series router software features for all supported Cisco IOS Release trains, and directs you to additional configuration information for each feature.
Cisco uBR7200 Series Router Features and Cisco IOS Releases
Table 1-9 summarizes the software-related features and related Cisco IOS releases that support the Cisco uBR7200 series 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
Many additional features were introduced in release trains prior to those listed above, such as 12.0 T, 12.0 SC, 12.1 XF and other earlier releases that may no longer be supported on the Cisco uBR7200 Series. Refer to the release notes for your respective Cisco IOS release for additional feature support and image information.
Table 1-9 Cisco uBR7200 Series Routers Features by Cisco IOS Release
12.0 T, 12.0 XR, 12.0 SC, 12.1 EC, 12.1 CX, 12.2 BC and 12.3 BC releases
12.1 EC, 12.1 CX, 12.2 BC and 12.3 BC releases
12.1(3a)EC1 and all later Cisco IOS releases supporting the Cisco uBR7200 Series CMTS
12.1 EC, 12.2 BC, 12.3 BC
12.0 T, 12.0 XR, 12.0 SC, 12.1 EC, 12.1 CX, 12.2 BC and 12.3 BC releases
12.2(1)XF1 and later 12.2 XF, 12.2 BC and 12.3 BC releases
All Cisco IOS releases supporting the Cisco uBR7200 Series CMTS
12.3(9a)BC and later 12.3 BC releases
12.3(9a)BC and later 12.3 BC releases
12.1(12c)EC, 12.2(8)BC2 and later 12.1 EC, 12.2 BC and 12.3 BC releases
Multiple Cisco IOS software releases. Enhancements include:
•
Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements
12.3(9a) enhancements to or introductions of the following commands:
12.1(10)EC, 12.2 BC and later releases
11.3(11)NA, 12.0 T and later releases
12.3(17a)BC and later 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
See the "DOCSIS 1.1 Feature Support" section for additional DHCP features.
12.0(6)SC, 12.1 EC and later releases
DOCSIS 1.0 Baseline Privacy Interface Encryption and Encrypted Key Exchange
12.0 SC and later releases in multiple release trains
12.3(13a)BC and later 12.3 BC releases
12.0(16)SC3, 12.1 EC, 12.2 CX, 12.2 BC, and 12.3 BC
12.1 EC, 12.2 CX, 12.2 BC, and 12.3 BC
Several additional DOCSIS 1.0 QoS enhancements for the Cisco uBR7200 Series are described in release notes for earlier releases.
DOCSIS quality of service (QoS) enhancements added to Cisco IOS Release 12.1(1a)T1 and continue with later releases in multiple trains.
12.3(17a)BC2 and later 12.3 BC releases.
DOCSIS CPE Configurator V2.0.4 and V 3.2 supported in multiple Cisco IOS releases.
Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems
12.3(13a)BC and later 12.3 BC releases
12.1(1)T and later releases in multiple trains support DOCSIS 1.0+ on the Cisco uBR7200 Series.
12.2(4)BC1 and later 12.2 BC and 12.3 BC releases
12.2(4)BC1 and later 12.2 BC and 12.3 BC releases
12.1(3a)EC1 and later 12.1 EC releases
12.0(4)T, with additional enhancements and support in 12.0 (6) SC, 12.1(2) EC1, 12.1(3a)EC, 12.2(15)BC2 and later releases
12.0(16)SC3 and later releases in multiple release trains
Multiple releases in multiple release trains beginning with 12.0 early deployment releases
12.2 BC and 12.3 BC release trains, with additional DOCSIS 1.1 features supported in certain earlier Cisco IOS 12.1 EC and 12.0 SC release trains. Includes:
•
•
•
•
•
•
12.2 BC, 12.3 BC
12.0(4)T and later releases in multiple trains
12.0(6)SC, 12.1 EC and later releases supporting the Cisco uBR7200 series
12.2 BC and 12.3 BC release trains
12.2 BC and 12.3 BC release trains
11.3NA, 12.0(5)T and later releases in multiple release trains.
11.3(6) NA, with additional enhancements and support in 12.0(4)XI, 12.0(5)T1, 12.1(1)EC1, 12.2(4)BC1 and later releases.
12.3(13a)BC and later 12.3 BC releases
12.2(15)CX and continues with later 12.2 CX, 12.2 BC and 12.3 BC releases
12.3(9a)BC and later 12.3 BC releases
12.3(17a)BC and later 12.3 BC releases
HCCP Support for the Cisco uBR-MC16S Cable Interface Line Card
12.1(7)EC and later releases in multiple release trains
12.1(10)EC, with additional enhancements and support in 12.2(4)XF1, 12.2(4)BC1, 12.2(8)BC2, 12.2(11)BC1, 12.2(15)BC1, 12.2(15)BC2a and later releases in multiple trains
12.3(13a)BC and later 12.3 BC releases
12.1(3a)EC and later releases in multiple release trains
12.2(15)BC2a and later 12.2 BC and 12.3 BC releases
12.3(13a)BC and later 12.3 BC releases
12.3(17a)BC and later 12.3 BC releases
COPS TCP Support for the Cisco Cable Modem Termination System
12.3(13a)BC and later 12.3 BC releases
Service Independent Intercept (SII) Support on the Cisco uBR7200 Series
12.3(13a)BC and later 12.3 BC releases
12.3(13a)BC and later 12.3 BC releases
12.2(15)BC2b and later 12.2 BC and 12.3 BC releases
12.0 SC, 12.1 EC, 12.2 BC and later BC releases
Configurable Alternate Termination System Information Messages
12.1(2)EC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
12.0 XC and later releases in this and additional release trains
12.1 T and later releases in this and additional release trains
Multiple protocols are supported in all release trains that support the Cisco uBR7200 Series.
12.3(13a)BC and later 12.3 BC releases
Cable ARP and Proxy ARP (cable arp and cable proxy arp commands)
12.1T , 12.0(6)SC , 12.1(2) EC1, 12.2(8)BC1, and later releases in respective release trains
12.1 EC and later releases in multiple release trains
12.0(6)EC with additional enhancements and support in later releases in multiple release trains
12.0(5)T1, 12.0(6)SC, 12.1(2)EC, 12.2(4)BC1 and later releases in respective release trains
12.3(17a)BC and later 12.3 BC releases
Downstream Load Balancing Distribution with Upstream Load Balancing
12.3(17b)BC and later 12.3 BC releases
12.3(17a)BC and later 12.3 BC releases
12.1 EC and later releases in this and multiple release trains
12.2(15)BC1 and later releases in the 12.2 BC and 12.3 BC release trains
12.3(17a)BC and later 12.3 BC releases
12.1(2)EC1 and later releases or release trains
12.1(4)CX, 12.2(1)XF, and 12.2(4)BC1 and later releases in these release trains
12.3(17a)BC and later 12.3 BC releases
12.3(9a)BC and later 12.3 BC releases
12.3(9a)BC and later 12.3 BC releases
12.1 EC, 12.2 BC
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
12.1(3)T and later releases in multiple release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.3(13a)BC and later 12.3 BC releases
12.2(4)XF1 and later XF and BC releases
12.2(10)EC and later EC releases
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
11.3 XA with additional support and enhancements in later releases in additional release trains
12.0(1)T and later releases in this and additional release trains
12.1 XM and later releases in this and additional release trains
12.1 CX, 12.2(4)XF and later releases in this and additional release trains
12.2(15)BC1 and later releases in the 12.2 BC and 12.3 BC release trains
12.3(9a)BC and later 12.3 BC releases
12.2(4)BC1 and later releases in this and additional release trains
12.0 T, 12.0 CX, and later releases in these and additional release trains
12.0(5)T1, 12.0(6)SC, and later releases in these and additional release trains
12.0 T and later releases in this and additional release trains
12.0(4)XI with additional support and enhancements in later releases in additional release trains
12.0 XC and later releases in this and additional release trains
Secure Shell (SSH) Supported in "k1" Images for Cisco uBR7200
12.1(1)T, 12.2(2)XA, 12.2 CX and later releases in this and additional release trains
12.1 EC, 12.2 CX, 12.2(4)XF1 and later releases in these and additional release trains
11.3(11)NA, 12.0 T and later releases in these and additional release trains
12.1(3)T and later releases in this and additional release trains
12.1 EC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 T and later releases in this and additional release trains
12.1 EC and later releases in this and additional release trains
Multiple Cisco IOS releases and release trains
SNMP MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC
12.3(9a)BC and later 12.3 BC releases
12.1 CX, 12.1 EC and later releases in these and additional release trains
Spectrum Management and Advanced Spectrum Management Features
12.1 CX and later releases in this and additional release trains
12.1 EC and later releases in this and additional release trains
12.0(7)XR2, 12.2(2)XF1 and later releases in these and additional release trains
12.1(3)EC and later releases in this and additional release trains
Refer to the following features:
•
•
•
•
11.3 NA, with additional enhancements in 12.0(7)XR2, 12.0(13)SC, 12.1(4)EC, 12.2(4)BC1 and later releases in these release trains
Spectrum Management Enhancements in Cisco IOS Release 12.3(9a)BC
12.3(9a)BC and later 12.3 BC releases
11.3(9)NA and later releases in this and additional release trains
12.0 SC, 12.1 EC, 12.1T and 12.2BC release trains
11.3 NA, 12.0(4)XA, 12.0(7)XR, 12.1(2)EC, 12.1(5)EC, 12.1(7)CX, 12.2(4)BC1 and later releases in these and additional release trains
12.3(9a)BC and later 12.3 BC releases
12.3(9a)BC and later 12.3 BC releases
12.2(15)BC1 and later 12.2 BC and 12.3 BC releases
12.3(13a)BC and later 12.3 BC releases
NAT—Support for NetMeeting Directory (Internet Locator Service—ILS)
12.0 XC and later releases in this and additional release trains
12.3(17a)BC and later 12.3 BC releases
12.2(11)BC2 and later 12.2 BC and 12.3 BC releases
MPLS VPN Support for Subinterfaces and Cable Interface Bundles
12.1 CX, 12.1 EC and later releases in these and additional release trains
12.1(3)EC and later releases in this and additional release trains
12.3(9a)BC and later 12.3 BC releases
Transparent LAN Services (TLS) and L2 Virtual Private Networks
12.3(13a)BC and later 12.3 BC releases
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.1 T, 12.1 XM and later releases in these and additional release trains
11.3(11)T, 12.0 XC and later releases in these and additional release trains
12.2(4)BC1 and later 12.2 BC and 12.3 BC releases
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.3(13a)BC and later 12.3 BC releases
12.0 XC and later releases in this and additional release trains
12.0 XC and later releases in this and additional release trains
12.1(5)T and later releases in this and additional release trains
12.3(9a)BC and later 12.3 BC releases
12.0 XC and later releases in this and additional release trains
11.3(11)NA and later releases in additional release trains
11.3(11)NA and later releases in additional release trains
For feature comparisons between multiple releases, refer to the corresponding release notes, or to the Cisco IOS Feature Navigator on Cisco.com (registration required).
Cisco uBR7200 Series Router Configuration Tools
The Cisco uBR7200 series router provides you with the following configuration tools, allowing you flexibility in choosing your configuration method:
•
•
•
•
•
•
Autoinstall
The AutoInstall Using DHCP for LAN Interfaces feature replaces the use of the Bootstrap Protocol (BOOTP) with the use of the Dynamic Host Configuration Protocol (DHCP) for Cisco IOS AutoInstall over LAN interfaces. AutoInstall is a Cisco IOS software feature that provides for the configuration of a new routing device automatically when the device is initialized. DHCP (defined in RFC 2131) is based on the Bootstrap Protocol, which provides the framework for passing configuration information to hosts on a TCP/IP network. DHCP adds the capability of automatic allocation of reusable network addresses and additional configuration options.
In Cisco IOS Release 12.1(5)T, the IP address procurement phase of the AutoInstall process is now accomplished using DHCP for Ethernet, Token Ring, and FDDI interfaces. Before this release, IP addresses for LAN interfaces were obtained using BOOTP during the AutoInstall process. The AutoInstall Using DHCP for LAN Interfaces feature also allows the routing device to recognize IP address allocation messages coming from regular BOOTP servers, providing a seamless transition for those devices already using BOOTP servers for AutoInstall. Additionally, this feature allows for the uploading of configuration files using unicast Trivial File Transfer Protocol (TFTP).
Use the Autoinstall facility to configure the Cisco uBR7200 series router automatically after connection to your WAN. For further details, refer to these sections or documents:
•
•
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt_dhcpa.html
Cable Interface Setup Facility
Use the Setup facility prior to completing a WAN or LAN connection to your router. The Setup facility supports 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 uBR7200 Series Using the Setup Facility" section on page 2-17.
Cable Interface Extended Setup Facility
The Extended Setup facility enhances the Setup Facility by prompting you to configure each interface on the system as you progress through the CMTS configuration. The Configuration mode allows you to configure the Cisco uBR7200 series router manually if you prefer not to use Autoinstall or the Setup Facility. Refer to the "Configuring the Cable Interface with the Extended Setup Facility" section on page 2-25.
Cisco Network Registrar
The Cisco Network Registrar (CNR) is a configuration tool that automates dynamic IP address allocation to cable interfaces, PCs, and other devices on the broadband network. CNR 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.
Cisco provides the CNR with each Cisco uBR7200 series router. CNR dramatically improves the reliability of naming and addressing services for enterprise and service provider networks. CNR provides scalable Domain Name System (DNS) and Dynamic Host Configuration Protocol (DHCP) services and forms the basis of a DOCSIS cable modem provisioning system.
For additional information about configuring or using CNR, refer to the document titled Cisco Network Registrar for the Cisco uBR7200 Series Routers:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/feature/guide/6126inst.html
Interface Range Specification
The Interface Range Specification feature allows specification of a range of interfaces to which subsequent commands are applied and supports definition of macros that contain an interface range.
Implement the Interface Range Specification feature with the range keyword, which is used with the interface command. In the interface configuration mode with the range keyword, all entered commands are applied to all interfaces within the range until you exit interface configuration mode.
For additional command information, refer to the Interface Range Specification feature module on Cisco.com:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t4/feature/guide/range.html
Internal Modem Configuration File Editor
This feature adds support for internal DOCSIS cable modem configuration file storage and generation. The cable modem configuration file is generated and stored as part of the Cisco IOS configuration file. The DOCSIS configuration files are not stored in Flash memory but are automatically generated when requested for TFTP downloads to cable modems.
For the latest additional information about DOCSIS configuration files, refer to the document titled Internal DOCSIS Configurator File Generator for the Cisco Cable Modem Termination System on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufgCFile.html
Manual Configuration Mode for the Cisco uBR7200 Series CMTS
The Configuration mode allows you to configure the Cisco uBR7200 series router manually if you prefer not to use Autoinstall or the Setup Facility. Refer to the "Configuring the Cisco uBR7200 Series Manually Using Configuration Mode" section on page 2-27.
Virtual Interface Support and Frequency Stacking Support
Cisco IOS Release 12.3(9a)BC supports virtual interfaces and frequency stacking on the Cisco uBR7246VXR router. Virtual interfaces allows a DS interface to be configured with up to eight upstream channels. Frequency stacking allows two frequencies to be configured on one physical connector.
For additional information about frequency stacking and virtual interfaces on the Cisco uBR7246VXR router, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml
Bandwidth Management Features
This section describes the following bandwidth management feature available on the Cisco uBR7200 Series:
Load Balancing Support
Cisco IOS Release 12.3(9a)BC introduces support for Load Balancing on the Cisco uBR7246VXR router. The Load Balancing feature allows system operators to distribute cable modems across radio frequency (RF) downstreams and upstreams, to maximize bandwidth and usage of the cable plant.
The Load Balancing feature allows service providers to optimally use both downstream and upstream bandwidth, enabling the deployment of new, high-speed services such as voice and video services. This feature also can help reduce network congestion due to the uneven distribution of cable modems across the cable network and due to different usage patterns of individual customers.
By default, the Cisco CMTS platforms use a form of load balancing that attempts to equally distribute the cable modems to different upstreams when the cable modems register. You can refine this form of load balancing by imposing a limit on the number of cable modems that can register on any particular upstream, using the cable upstream admission-control command.
However, this default form of load balancing affects the cable modems only when they initially register with the Cisco CMTS. It does not dynamically rebalance the cable modems at later times, such as when they might change upstream channels in response to RF noise problems, or when bandwidth conditions change rapidly because of real-time traffic such as Voice over IP (VoIP) and video services. It also does not affect how the cable modems are distributed among downstream channels.
For additional information about configuring Load Balancing on the Cisco CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html
Cisco IOS Command-Line Enhancements
In addition to new or enhanced commands that tie to a specific feature, this section describes general enhancements to Cisco IOS Software commands that support the Cisco uBR7200 series.
•
•
In some cases, additional feature descriptions that relate to these commands are available elsewhere in this chapter.
exec prompt timestamp Command
Cisco IOS Release 12.1(12c)EC and 12.2(8)BC2 add a new command, exec prompt timestamp. This command adds load information and a timestamp to all show commands. This can be useful for troubleshooting and system analysis.
The exec prompt timestamp command has the following syntax in line configuration mode:
Router(config-line)# [no] exec prompt timestampThe command has the following syntax in User EXEC mode, so that users who do not know the enable password can also timestamp their show commands:
Router> terminal [no] exec prompt timestampThe following example illustrates how to enable and disable the timestamp for the console connection:
Router# config tRouter(config)# line console 0Router(config-line)# exec prompt timestampRouter(config-line)# no exec prompt timestampThe following example illustrates how to enable and disable the timestamp for the first five telnet connections:
Router(config)# line vty 0 4Router(config-line)# exec prompt timestampRouter(config-line)# no exec prompt timestampThe following example illustrates how to enable and disable the timestamp when logged into User EXEC mode:
Router> terminal exec prompt timestampRouter> terminal no exec prompt timestampparser cache Command
A new global configuration command, [no] parser cache, allows you to enable or disable the parser cache feature on the Cisco uBR7200 series.The parser cache feature is enabled by default on all platforms using Cisco IOS Release 12.1(5)T or later.
The parser cache feature optimizes the parsing (translation) of Cisco IOS software configuration command lines by remembering how to parse recently encountered command lines. This feature improves the scalability of the Cisco IOS software command-line interface (CLI) parser when processing large configuration files.
This improvement is especially useful for those cases in which thousands of virtual circuits must be configured for interfaces, or hundreds of access control lists (ACLs) are required. The parser chain cache can rapidly recognize and translate configuration lines that differ slightly from previously used configuration lines (for example, pvc 0/100, pvc 0/101, and so on).
Note
For additional information, refer to the Parser Cache feature module on Cisco.com:
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t5/feature/guide/dt5parse.html
show Command Enhancements
The Cisco uBR7200 series universal broadband routers contain the following additional or changed show commands.
show cable qos
The show cable qos command is changed to show cable qos profile n command, where the optional argument n can be used to display a specific profile.
Note
show int cx/y sid
The show int cx/y sid command displays more complete Service ID (SID) status information.
show cable modem
The show cable modem command displays a list of options for a single modem to be specified by entering either the cable modem's IP address or MAC address.
show cable modulation-profile
The show cable burst-profile command has been removed. Its functions have been incorporated into the show cable modulation-profile command, which includes an added option number that displays the modulation profile number.
show cable modem summary
Commencing with Cisco IOS Release 12.1(6) EC, the show cable modem summary command is enhanced with the following options to display per-card and per-port totals:
•
•
•
•
•
For additional command information, 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
Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements
Cisco IOS Release 12.3(9a)BC supports the following new or enhanced command-line interface:
For additional information about these command changes, refer to this document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
cable logging layer2events
To save DOCSIS events that are specified in Cable Device MIB to the cable logging buffer (instead of to the general logging buffer), use the cable logging layer2events command in global configuration mode. To disable the logging of DOCSIS events to the cable logging buffer, use the no form of this command.
cable logging layer2events
no cable logging layer2events
Syntax Description
This command has no additional arguments or keywords.
Defaults
DOCSIS events are saved to the general logging buffer on the Cisco CMTS by default.
Command Modes
Global configuration mode
Command History
12.3(9a)BC
This command was introduced on the Cisco uBR10012 and Cisco uBR7246VXR universal broadband routers.
Usage Guidelines
Use the show cable logging command to check whether the logging feature is enabled and the status of the logging buffer.
Examples
The following example shows how to clear the log buffer that contains a bad IP source address error messages:
Router# show cable logging summaryCable logging: BADIPSOURCE EnabledTotal buffer size (bytes): 1000000Used buffer size (bytes) : 36968Logged messages : 231Router# clear cable logging badipsourceRouter# show cable logging summaryCable logging: BADIPSOURCE EnabledTotal buffer size (bytes): 1000000Used buffer size (bytes) : 0Logged messages : 0Related Commands
For additional information about logging events on the Cisco CMTS, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
cable source-verify
To enable verification of IP addresses or service IDs (SIDs) for CMs and CPE devices on the upstream, use the cable source-verify command in global configuration, cable interface configuration or subinterface configuration modes. To disable verification, use the no form of this command.
Cable Interface and Subinterface Configuration Modes
cable source-verify [dhcp | leasetimer value | leasequery-filter upstream query-num interval]
no cable source-verify
Global Configuration Mode
cable source-verify leasequery-filter downstream query-num interval
no cable source-verify
Syntax Description
Defaults
Disabled. When the dhcp option is specified, the leasetimer option is set by default to 60 minutes.
Command Modes
Global configuration, Cable interface configuration or subinterface configuration
Note
Command History
For additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
cable submgmt default
To enable the Cisco CMTS Static CPE Override feature on the Cisco CMTS, use the cable submgmt default command in global configuration mode. This command enables field technicians to add a temporary CPE device behind the subscriber's cable modem. The temporary CPE device shares the same SID settings as the original CPE device, even though the temporary CPE device has a different MAC address. The original CPE device automatically changes from dhcp cpe to static cpe in the CMTS host routing tables, and the CPE device continues to receive service with the same SID. To disable Cisco CMTS Static CPE Override on the Cisco CMTS, use the no form of this command. This automatically updates the routing tables and enables the MAC address from the technician's laptop for a future field service connection at a different location.
cable submgmt default {active | filter-group {cm | cpe} | learnable | max-cpe}
no cable submgmt default
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Global configuration mode
Command History
12.3(9a)BC
This feature was introduced on Cisco uBR10012 and Cisco uBR7200 series universal broadband routers.
Usage Guidelines
Prior to using this command, the first (existing) DHCP CPE device maintains its DHCP dynamic MAC address behind the cable modem. The SID is assigned to this IP address.
However, by enabling Static CPE override, you gain the following states and options on two CPE devices behind the cable modem.
•
•
Note
Examples
The following example enables Cisco CMTS Static CPE Override in the field, enabling more or more additional CPE devices to be added behind a subscriber's cable modem:
Router(config)# cable submgmt default activeThe following example configures the Cisco CMTS to accept a temporary CPE device, which inherits and filters by the subscriber's default downstream cable modem group:
Router(config)# cable submgmt default filter-group cm downstreamThe following example configures the Cisco CMTS to accept a temporary CPE device, and to update the temporary CPE device with the current routing table from the Cisco CMTS:
Router(config)# cable submgmt default learnableThe following example configures the Cisco CMTS to accept a maximum of five temporary CPE devices behind a subscriber's cable modem:
Router(config)# cable submgmt default max-cpe 5Related Commands
show cable host
Displays the CPE devices (hosts) residing behind a specified cable modem (MAC address).
show cable tech-support
Cisco IOS Release 12.3(9a)BC introduces changes to the output of the show cable tech-support command. This change allows users with large numbers of online cable modems to collect the necessary information without consuming the console session for a long period of time.
To display general information about the router when reporting a problem, use the show cable tech-support command in privileged EXEC mode.
show cable tech-support
Syntax Description
This command has no additional arguments or keywords.
Defaults
This command has no default behavior or values.
Command Modes
Privileged EXEC
Command History
Examples
The following example illustrates the cable modem and interface information from a Cisco uBR7246VXR router on which Cisco IOS Release 12.3(9a)BC is installed.
Router# show cable tech-supportFor additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
show controllers cable
Cisco IOS Release 12.3(9a)BC removes the tech-support keyword from the show controllers cable command. This change allows users with large numbers of online cable modems to collect the necessary information without consuming the console session for a long period of time.
Additional and related improvements are also available for the show tech-support command.
To display information about the interface controllers for a cable interface on the Cisco CMTS router, use the show controllers cable command in user EXEC or privileged EXEC mode.
show controllers cable {slot/port | slot/subslot/port} [downstream | upstream [port] | [mem-stat] [memory] [proc-cpu]] [tech-support]
Syntax Description
Command Modes
User EXEC, Privileged EXEC
Command History
Usage Guidelines
The mem-stat, memory, and proc-cpu keywords execute the related command on the processor that runs on added to obtain the relevant information from the onboard processor on Broadband Processing Engine (BPE) cable interface line cards, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC5X20S/U cards. This allows you to obtain information that is specific for that particular cable interface card, as opposed to having to run these commands on the entire router.
Note
Examples
The following is sample output for the downstream connection for slot 3 on port 0 on Cisco CMTS router from the show controllers cable downstream command:
CMTS01# show controllers cable 3/0 downstreamCable 3/0 Downstream is upFrequency not set, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 MspsFEC ITU-T J.83 Annex A, R/S Interleave I=12, J=17Table 10 describes the fields displayed by the show controllers cable downstream command.
The following example illustrates the information from the show controllers cable command on a Cisco uBR7246VXR router on which Cisco IOS Release 12.3(9a)BC is installed.
Router# show controllers cable x/yFor additional information about this and other commands, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
show tech-support
Cisco IOS Release 12.3(9a)BC shortens the output of the show tech-support command on the Cisco uBR10012 and the Cisco uBR7246VXR routers. This change allows users with large numbers of online cable modems to collect information without consuming the console session for a long period of time.
To display general information about the Cisco CMTS router when reporting a problem to Cisco technical support, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password] [cef | ipc | ipmulticast | isis | mpls | ospf | rsvp]
Note
Note
Syntax Description
For additional information about this and other commands, refer to the following document on Cisco.com (updated through Cisco IOS Release 12.3(9a)BC):
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Cisco Quality of Service Features
Networks must provide secure, predictable, measurable, and sometimes guaranteed services. Achieving the required Quality of Service (QoS) by managing delay, delay variation (jitter), bandwidth, and packet loss parameters on a network becomes the secret to a successful end-to-end business solution. Cisco QoS is the set of techniques to manage network resources. The Cisco uBR7200 series CMTS offers the following Cisco QoS features, in addition to supporting additional DOCSIS QoS features.
•
For additional information, refer to the Cisco IOS Quality of Service Web page on Cisco.com:
Cisco Network-Based Application Recognition (NBAR)
Cisco IOS Release 12.1(10)EC added support for Cisco IOS Network-Based Application Recognition (NBAR). The NBAR feature is a new classification engine that can recognize a wide variety of network applications, including Web-based applications, client/server applications, and other difficult-to-classify protocols that dynamically assign TCP or UDP port numbers.
NBAR enhances existing methods of application-recognition by adding several new classification features:
•
•
•
•
NBAR can also classify static port protocols. Although access control lists (ACLs) can also be used for this purpose, NBAR is easier to configure and can provide other options and classification statistics that are not available when using ACLs.
After NBAR recognizes an application, the Cisco uBR7200 series router can invoke specific services appropriate for that application. These services can provide QoS features such as:
•
•
•
•
The Cisco IOS NBAR feature can also be used to detect and respond to denial-of-service and other types of network attacks. Cisco IOS NBAR uses a protocol description language module (PDLM) to define the rules by which the NBAR processes recognize an application. New PDLM definitions can usually be loaded without the need for a Cisco IOS software upgrade or a router reboot, allowing for a rapid response to discovered attacks.
Note
For information on configuring NBAR for Quality of Service (QoS) control, see the "Configuring Network-Based Application Recognition" chapter of theCisco IOS Release 12.2 Quality of Service Solutions Configuration Guide.
These documents are available on Cisco.com and the Customer Documentation CD-ROM.
Tip
RTP Header Compression
Real-Time Transport Protocol (RTP) is the Internet Standard (RFC 1889) protocol for the transport of real-time data. It is intended to provide end-to-end network transport functions for applications that support audio, video, or simulation data over multicast or unicast network services.
RTP provides support for real-time conferencing of groups of any size within the Internet. This support includes source identification and support for gateways such as audio and video bridges as well as multicast-to-unicast translators. RTP offers QoS feedback from receivers to the multicast group, and support for the synchronization of different media streams.
RTP includes a data portion and a header portion. The data portion of RTP is a thin protocol that provides support for the real-time properties of applications, such as continuous media, including timing reconstruction, loss detection, and content identification.
The header portion of RTP is considerably large. As shown in Figure 16, the minimal 12 bytes of the RTP header, combined with 20 bytes of IP header (IPH) and 8 bytes of UDP header, create a 40-byte IP/UDP/RTP header. For compressed-payload audio applications, the RTP packet typically has a 20-byte to 160-byte payload. Given the size of the IP/UDP/RTP header combinations, it is inefficient to send the IP/UDP/RTP header without compressing it.
To avoid the unnecessary consumption of available bandwidth, the RTP header compression feature—referred to as CRTP—is used on a link-by-link basis.
For configuration information and additional explanation, refer to the Link Efficiency Mechanisms" chapters of the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 on Cisco.com.
DHCP Servers and Feature Support
Cisco IOS software supports multiple DHCP features and server functions on the network for the Cisco uBR7200 series.
•
•
•
Configurable Leasequery Server
Previously, lease query requests could only be sent to the DHCP server. Beginning with Cisco IOS Release 12.3(17a)BC, an alternate server may be configured to receive the requests.
There are a few restrictions:
•
•
•
•
Regardless of which server is configured (DHCP or alternate), unknown IP addresses that are found in packets for customer premises equipment (CPE) devices that use the cable modems on the cable interface are verified. The DHCP server or configured alternate server returns a DHCP ACK message with the MAC address of the CPE device that has been assigned this IP address, if any.
To configure the Cisco CMTS router to send DHCP LEASEQUERY requests to an alternate server, use the cable source-verify dhcp server ipaddress and no cable arp commands. (To configure the DHCP server instead, use the cable source-verify dhcp and no cable arp commands.)
For additional information about this feature, refer to the following documents on Cisco.com:
•
URL: http://www.cisco.com/en/US/docs/cable/cmts/feature/cblsrcvy.html
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
For additional information about the enhanced Cable Source Verify DHCP feature, and general guidelines for its use, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/sourcver.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/cblsrcvy.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/tech/tk86/tk803/technologies_tech_note09186a00800a7828.shtml
DOCSIS 1.0 Feature Support
The Cisco uBR7200 series and associated Cisco IOS software support multiple DOCSIS 1.0 enhancements, extensions, and features.
•
•
•
•
•
•
DOCSIS 1.0 Baseline Privacy
DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and cable modem. BPI ensures that a cable modem, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for services only it is authorized to access.
To enable BPI, choose software at both the CMTS and cable modem that support the mode of operation. For the Cisco uBR7200 series software, choose an image with "k1" in its file name or BPI in the feature set description.
The cable modem must also support BPI. CMs must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment. BPI must be enabled using the DOCSIS configuration file.
Note
DOCSIS 1.0 Baseline Privacy Interface Encryption and Encrypted Key Exchange
The Cisco uBR7200 series supports full DOCSIS 1.0 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 cable modem 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 cable modem, uniquely identified by its MAC address, can obtain keying material for services only when it is authorized to access.
Note
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.
Baseline privacy extensions permit the encryption of data transferred between the cable modem and the Cisco uBR7200 series universal broadband router. The key management protocol defined by baseline privacy allows Cisco uBR7200 series universal broadband routers to provide two types of keys to cable modems. The Key Exchange Key (KEK) decrypts the Traffic Exchange Keys (TEK). The TEK is the key used to encrypt and decrypt data packets.
DOCSIS 1.0 Concatenation Override Featurette
Cisco IOS release 12.3(13a)BC introduces support for the DOCSIS 1.0 concatenation override feature on the Cisco uBR10012 router. This feature provides the ability to disable concatenation on DOCSIS 1.0 cable modems, even in circumstances where concatenation is otherwise supported for the upstream channel.
DOCSIS 1.0 concatenation allows the cable modem to make a single-time slice request for multiple packets, and to send all packets in a single large burst on the upstream. Concatenation was introduced in the upstream receive driver in the previous Cisco IOS releases that supported DOCSIS 1.0 +. Per-SID counters were later added in Cisco IOS release 12.1(4)CX for debugging concatenation activity.
In some circumstances, overriding concatenation on DOCSIS 1.0 cable modems may be preferable, and Cisco IOS release 12.3(13a)BC supports either option.
Note
To enable DOCSIS 1.0 concatenation override with Cisco IOS release 12.3(13a)BC and later releases, use the new docsis10 keyword with the previously supported cable upstream <n> concatenation command in privileged EXEC mode:
cable upstream <n> concatenation docsis10
Syntax Description
n
Specifies the upstream port number. Valid values start with 0 for the first upstream port on the cable interface line card.
Examples
The following example illustrates DOCSIS 1.0 concatenation override on the Cisco uBR7246VXR router:
Router# no cable upstream 0 concatenation docsis10In this example, DOCSIS 1.0 cable modems are updated with REG-RSP so that they are not permitted to use concatenation.
For additional information about this command, refer to the Cisco IOS CMTS Cable Command Reference Guide on Cisco.com:
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
DOCSIS 1.0 Extensions
The Cisco uBR7200 series supports the following DOCSIS 1.0 Quality of Service (QoS) extensions:
•
•
•
•
–
Note
DOCSIS 1.0 Quality of Service
The Cisco uBR7200 series universal broadband routers support quality of service (QoS) as defined by the DOCSIS 1.0 specification. Service class profiles can be configured through the command-line interface to support the QoS profile number, traffic priority, maximum upstream bandwidth, guaranteed upstream bandwidth, maximum downstream bandwidth, maximum transmit burst length, baseline privacy enable/disable, and type of service (ToS) overwrite byte.
QoS Profile Enforcement allows cable modem termination system (CMTS) operators to control the QoS to eliminate any interference from improper local-rate limiting implemented on the cable modem. The CMTS provisions a registering cable modem with a default DOCSIS 1.0 service class assigned by the operator, overriding any service class that previously existed on the modem. This service class has no upstream or downstream rate limits, so that the CMTS can do traffic shaping based on the QoS profile enforced by the operator.
The following commands are available on Cisco uBR7200 series universal broadband routers to update the QoS table:
•
•
•
DOCSIS Quality of Service Enhancements Prior to DOCSIS 1.1
A number of DOCSIS quality of service (QoS) enhancements were added to Cisco IOS Release 12.1(1a)T1 and continue with later releases; these features paralleled some of those that were expected in the DOCSIS 1.1 specification prior to finalization.
For supported DOCSIS 1.1 QoS features, refer to the "DOCSIS 1.1 Quality of Service Features" section.
Note
Concatenation Support Prior to DOCSIS 1.1
DOCSIS Concatenation combines multiple upstream packets into one packet to reduce packet overhead and overall latency, as well as increase transmission efficiency. Using concatenation, a DOCSIS cable modem needs to make only one bandwidth request for a concatenated packet, as opposed to making a different bandwidth request for each individual packet; this technique is especially effective for burst-intensive real-time traffic, such as voice calls.
Concatenation is enabled by default for current cable modem cards (see the "Cable Modem Cards" section), but can be disabled with the Cisco IOS command no cable upstream number concatenation interface. The show controller command displays whether concatenation is enabled on an interface.
Note
Embedded Client Signaling (dynamic SIDs)
Supports the dynamic creation, configuration, and deletion of Service Identifiers (SIDs) to accommodate different classes of service. This allows cable modems to request high-priority or high-bandwidth data streams as needed, such as when a VoIP call is made.
Note
IP Precedence-Based Rate Limiting
In addition to the currently supported traffic shaping techniques, Cisco IOS Release 12.1(1a)T1 supports a new configuration field that associates a maximum bandwidth (in kbps) with a particular setting of the IP type of service (ToS) bits. This can be used to ensure that certain traffic, such as data, does not exceed a preset rate limit and thereby interfere with higher-priority real-time traffic, such as VoIP calls.
Support for Unsolicited Grants
New fields in the DOCSIS configuration file can be used so that when a cable modem requests a voice or fax SID, the MAC scheduler on the Cisco uBR7200 series router schedules fixed periodic slots on the upstream for that traffic flow. The cable modem does not have to contend for these slots, and because the Cisco uBR7200 series router controls the timing of the slots, it has a very precise control over potential delay and jitter. This provides a Constant Bit Rate (CBR) traffic flow for real-time traffic such as voice and fax calls.
In addition, the Cisco uBR7200 series router can create QoS profiles for G.711 fax traffic and G.729 voice traffic. These profiles can be customized with the scheduling parameters required for the G.711 and G.729 CODECs being used at the subscriber's site.
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.
DOCSIS Customer Premises Equipment Configurator
DOCSIS CPE Configurator V2.0.4
The DOCSIS specification requires that a DOCSIS-compliant modem download a DOCSIS configuration file during its power-on or reset sequence. This file must be in the format described in the DOCSIS Radio Frequency Specification (SP-RFI-IOS-991105).
The DOCSIS Customer Premises Equipment (CPE) Configurator V2.0.4 provides you with a Web-based graphical user interface (GUI) that allows you to collect information needed to generate and download configuration files for DOCSIS or EuroDOCSIS CMs and STBs.
There are two versions of the Cisco DOCSIS CPE Configurator V2.0.4:
•
•
http://www.cisco.com/pcgi-bin/tablebuild.pl/cpe-conf.
Refer to the following document for additional information about CPE Configurator V2.0.4:
•
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_q_and_a_item09186a00800a4ae5.shtml
DOCSIS CPE Configurator V3.2
Cisco has developed the DOCSIS CPE Configurator tool Version 3.2 that allows to configure DOCSIS 1.1 specific features like upstream and downstream service flows, upstream and downstream Packet Classification, and Payload Header Suppression.
If you are a registered user and are logged in to Cisco.com, you can download the stand-alone DOCSIS CPE Configurator tool Version 3.2 at this online location:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cpe-conf.
Refer to the following document for additional information about the DOCSIS CPE Configurator V3.2, which is available to registered, logged in users only.
•
http://www.cisco.com/en/US/customer/tech/tk86/tk168/technologies_tech_note09186a0080094d00.shtml
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 uBR7200 series router. ERBA allows DOCSIS1.0 modems to burst their temporary transmission rate up to the full line rate for short durations of time. This capability provides higher bandwidth for instantaneous bandwidth requests, such as those in Internet downloads, without having to make changes to existing service levels in the QoS Profile.
This feature enables MSOs to set the DOCSIS 1.0 cable modems burst transmissions, with mapping to overriding DOCSIS 1.1 QoS profile parameters on the Cisco CMTS. DOCSIS 1.0 cable modems require DOCSIS 1.0 parameters when registering to a matching QoS profile. This feature enables maximum downstream line rates, and the ERBA setting applies to all cable modems that register to the corresponding QoS profile.
Note
ERBA for DOCSIS 1.0 cable modems is supported with these new or enhanced commands or keywords in Cisco IOS release 12.3(13a)BC:
•
•
To define ERBA on the downstream for DOCSIS 1.0 cable modems, use the cable qos promax-ds-burst command in global configuration mode. To remove this ERBA setting from the QoS profile, use the no form of this command.
cable qos pro max-ds-burst burst-size
no cable qos pro max-ds-burst
Syntax Description
To display ERBA settings as applied to DOCSIS 1.0 cable modems and QoS profiles on the Cisco CMTS, use the show cable qos profile command in Privileged EXEC mode.
The following example of the cable qos profile command in global configuration mode illustrates changes to the cable qos profile command. Fields relating to the ERBA feature are shown in bold for illustration:
Router(config)# cable qos pro 10 ?grant-interval Grant intervalgrant-size Grant sizeguaranteed-upstream Guaranteed Upstreammax-burst Max Upstream Tx Burstmax-ds-burst Max Downstream Tx burst (cisco specific)max-downstream Max Downstreammax-upstream Max Upstreamname QoS Profile name string (cisco specific)priority Priorityprivacy Cable Baseline Privacy Enabletos-overwrite Overwrite TOS byte by setting mask bits to valueThe following example of the show cable qos profile command illustrates that the maximum downstream burst has been defined, and is a management-created QoS profile:
Router# show cable qos proID Prio Max Guarantee Max Max TOS TOS Create B IP prec.upstream upstream downstream tx mask value by priv ratebandwidth bandwidth bandwidth burst enab enab1 0 0 0 0 0 0xFF 0x0 cmts(r) no no2 0 64000 0 1000000 0 0xFF 0x0 cmts(r) no no3 7 31200 31200 0 0 0xFF 0x0 cmts yes no4 7 87200 87200 0 0 0xFF 0x0 cmts yes no6 1 90000 0 90000 1522 0xFF 0x0 mgmt yes no10 1 90000 0 90000 1522 0x1 0xA0 mgmt no no50 0 0 0 96000 0 0xFF 0x0 mgmt no no51 0 0 0 97000 0 0xFF 0x0 mgmt no noThe following example illustrates the maximum downstream burst size in sample QoS profile 10 with the show cable qos prof verbose command in privileged EXEC mode:
Router# show cable qos pro 10 verProfile Index 10NameUpstream Traffic Priority 1Upstream Maximum Rate (bps) 90000Upstream Guaranteed Rate (bps) 0Unsolicited Grant Size (bytes) 0Unsolicited Grant Interval (usecs) 0Upstream Maximum Transmit Burst (bytes) 1522Downstreamam Maximum Transmit Burst (bytes) 100000IP Type of Service Overwrite Mask 0x1IP Type of Service Overwrite Value 0xA0Downstream Maximum Rate (bps) 90000Created By mgmtBaseline Privacy Enabled noUsage Guidelines
If a cable modem registers with a QoS profile that matches one of the existing QoS profiles on the Cisco CMTS, then the maximum downstream burst size, as defined for that profile, is used instead of the default DOCSIS QoS profile of 1522.
For example, a DOCSIS 1.0 configuration that matches QoS profile 10 in the previous examples would be as follows:
03 (Net Access Control) = 104 (Class of Service Encodings Block)S01 (Class ID) = 1S02 (Maximum DS rate) = 90000S03 (Maximum US rate) = 90000S06 (US burst) = 1522S04 (US Channel Priority) = 1S07 (Privacy Enable) = 0The maximum downstream burst size (as well as the ToS overwrite values) are not explicitly defined in the QoS configuration file because they are not defined in DOCSIS. However, because all other parameters are a perfect match to profile 10 in this example, then any cable modem that registers with these QoS parameters has a maximum downstream burst of 100000 bytes applied to it.
For further illustration, consider a scenario in which packets are set in lengths of 1000 bytes at 100 packets per second (pps). Therefore, the total rate is a multiplied total of 1000, 100, and 8, or 800kbps.
To change these settings, two or more traffic profiles are defined, with differing downstream QoS settings as desired. Table 11 provides two examples of such QoS profiles for illustration:
In this scenario, both QoS profiles are identical except for the max-ds-burst size, which is set to 5000 in QoS profile 101 and 5000 in QoS profile 102.
Optimal Settings for 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:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
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. The main enhancements provide basic Voice-over IP (VoIP) service over the DOCSIS link, support for dynamic creation and teardown of flows during voice calls, support for one new unsolicited grant service (UGS) slot scheduling mechanism for voice slots, and per IP-precedence rate shaping on the downstream. In particular, the Cisco DOCSIS 1.0+ extensions include the DOCSIS 1.1 features described in this section:
•
•
•
Refer to the following online document for additional information about DOCSIS 1.0+ support on the Cisco uBR7200 Series:
•
http://www.cisco.com/en/US/tech/tk86/tk168/technologies_q_and_a_item09186a0080094eb2.shtml
Concatenation for DOCSIS 1.0+
Concatenation allows a cable modem to send several packets in one large burst, instead of having to make a separate grant request for each.
Caution
Dynamic MAC messages
The Dynamic Service Addition (DSA) and Dynamic Service Deletion (DSD) 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.
Multiple SIDs per Cable Modem
This feature creates separate service flows for voice and data traffic. This allows the CMTS and cable modem to give higher priority for voice traffic, preventing the data traffic from affecting the quality of the voice calls.
Separate Downstream Rates
This feature provides an ability to provide separate downstream rates for any given cable modem, 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.
Unsolicited Grant Service (CBR-scheduling) on the Upstream
This feature helps provide a higher-quality channel for upstream VoIP packets from an Integrated Telephony Cable Modem (ITCM) such as the Cisco uBR924 cable access router.
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.
This section describes the major enhancements supported on the Cisco uBR7200 series:
•
•
•
•
•
•
•
•
•
Baseline Privacy Interface Plus (BPI+)
Baseline Privacy Interface Plus (BPI+) is available and supported on the Cisco uBR7200 series with Cisco IOS Release 12.2(4)BC1 and subsequent BC1 releases.
DOCSIS 1.1 enhances these security features with Baseline Privacy Interface Plus (BPI+), which includes the following enhancements:
•
•
•
•
•
Additional feature information and configuration guidelines are provided in Configuring DOCSIS Baseline Privacy Interface on the Cisco uBR7200 Series, available on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/ubr7200/configuration/guide/u72_bpi.html
Burst Profile Configuration
For each modulation/burst profile configuration, Cisco uBR7200 series universal broadband routers support burst profile number, burst profile interval usage code, burst type, preamble length and unique word length, differential encoding enable/disable, forward error correction (FEC) correctable bytes value, FEC code word length, scrambler seed value, maximum burst size, guard time size, last code word shortened/lengthened, and scrambler enable/disable.
Note
Cable Modulation Profile Default Templates
Commencing with Release 12.1(3a)EC1 and later releases, the cable modulation-profile global configuration command has been enhanced with three new options that enable you to quickly create basic modulation profiles using the default values for each burst type.
To define the modulation profile, use the cable modulation-profile command in global configuration mode. Use the no form of this command to remove the entire modulation profile or to reset a particular burst to its default values.
cable modulation-profile profile {mix | qam-16 | qpsk}
no cable modulation-profile profile {mix | qam-16 | qpsk}
Syntax Description
The syntax for the new options is as follows:
DHCP Cable Modem Host ID
This feature—also known as Cable Modem and Host Subnet Addressing—allows the Cisco uBR7200 series universal broadband router to set the GIADDR field of DHCPDISCOVER and DHCPREQUEST packets with a Relay IP address to help automate the provisioning of cable modems on systems that use multiple IP subnets.
To modify the GIADDR field of DHCPDISCOVER and DHCPREQUEST packets with a Relay IP address before they are forwarded to the DHCP server, use the cable dhcp-giaddr command in cable interface or subinterface configuration mode. To set the GIADDR field to its default, use the no form of this command.
cable dhcp-giaddr [policy | primary]
no cable dhcp-giaddr
Syntax Description
For additional command information, refer to the Cisco IOS CMTS Cable Command Reference Guide on Cisco.com.
DHCP Client ID/Remote ID Options
This feature—also known as the Customer Premises Equipment (CPE) Limitation—allows Cisco uBR7200 series universal broadband routers to report and limit the number of CPEs that can use the cable modem to access the cable network.
Note
DHCP, Time of Day (ToD) and TFTP Servers
The Cisco uBR7200 series routers support onboard Dynamic Host Configuration Protocol (DHCP) servers, Time of Day (ToD) and TFTP servers. This allows the Cisco uBR7200 series routers to provide cable modems with IP address information, to supply an RFC 868-compliant time-of-day timestamp, and to download a DOCSIS configuration file, without requiring separate and external servers.
A DOCSIS-compliant cable modem requires access to three types of servers in order to successfully come online:
•
•
•
The Dynamic Host Configuration Protocol (DHCP) is a network management features that simplifies CMTS provisioning. DHCP provides configuration parameters to Internet hosts. DHCP consists of two components:
•
•
DHCP is built on a client/server model, where designated DHCP server hosts allocate network addresses and deliver configuration parameters to dynamically configured hosts. DHCP supports three mechanisms for IP address allocation:
•
•
•
The Cisco IOS DHCP server feature is a full DHCP server implementation that assigns and manages IP addresses from specified address pools within the router to DHCP clients. If the Cisco IOS DHCP server cannot satisfy a DHCP request from its own database, it can forward the request to one or more secondary DHCP servers defined by the network administrator.
You can configure a DHCP server in the following ways:
•
•
DOCSIS 1.1 Quality of Service Features
DOCSIS 1.1 modifies the DOCSIS 1.0 specification to provide better performance, in particular for real-time traffic such as voice calls. The DOCSIS 1.1 specification provides several functional enhancements over DOCSIS 1.0 coaxial cable networks.
DOCSIS 1.1 features are supported in the Cisco IOS 12.2 BC release train, with additional DOCSIS 1.1 features being supported in certain earlier Cisco IOS 12.1 EC and 12.0 SC release trains.
Concatenation for DOCSIS 1.1
Concatenation allows a cable modem to send multiple MAC frames in the same time slot, as opposed to making an individual grant request for each frame. This avoids wasting upstream bandwidth when sending a number of very small packets, such as TCP acknowledgement packets.
You can turn concatenation on or off. For information about configuring concatenation, refer to Configuring Concatenation on the Cisco uBR7200 Series Cable Router on Cisco.com.
DOCSIS 1.0 and 1.0+ Cable Modem Support
DOCSIS 1.1 cable modems can coexist with DOCSIS 1.0 and 1.0+ cable modems in the same network—the Cisco uBR7200 series provides the levels of service that are appropriate for each cable modem.
DOCSIS 1.1 Service Flow Model
DOCSIS 1.1 offers enhanced Quality of Service (QoS) features that give priority for real-time traffic such as voice and video:
•
•
•
•
•
Downstream QoS Handling Supported
Downstream QoS handling is compliant with Multimedia Cable Network System (MCNS) requirements. For additional downstream QoS feature configuration, refer to the DOCSIS 1.1 for the Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
Dynamic MAC Messages
Dynamic Service MAC messages allow dynamic signaling of QoS between the cable modem and the CMTS. These messages are DOCSIS link layer equivalents of the higher layer messages that create, tear down, and modify a service flow. These messages are collectively known as DSX messages.
The DSX state machine module on the CMTS manages the several concurrent dynamic service transactions between cable modems and the CMTS. It include state machine support for all three DOCSIS1.1 DSX MAC messages:
•
•
•
For additional information, refer to the DOCSIS 1.1 for the Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
Dynamic Map-Advance
A CMTS administrator can enhance the upstream throughput from a cable modem connected to the Cisco Cisco uBR7200 series CMTS. The system employs a new algorithm that automatically tunes the lookahead time in MAPs, based on several input parameters for the corresponding upstream channel. The use of dynamic and optimal lookahead time in MAPs significantly improves the per-modem upstream throughput.
For configuration information, refer to "Configuring the Dynamic Map Advance Algorithm" section on page 5-7.
Dynamic SID Support
For additional feature information, refer to the document titled Cisco uBR7200 - QoS/MAC Enhancements for Voice and Fax Calls: DOCSIS 1.0+ on Cisco.com.
Fragmentation (Layer 2)
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.
Multiple SID Support
This feature consists of changes made to various show commands to expand service identifier (SID) information.
•
•
For additional information, refer to Multiple Service ID Support for the Cisco uBR7200 Series Cable Router on Cisco.com:
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t5/feature/guide/multisid.html
Payload Header Suppression (PHS)
Payload Header Suppression (PHS) conserves link-layer bandwidth by suppressing unnecessary packet headers on both upstream and downstream traffic flows.
To configure PHS, refer to the "Configuring Payload Header Suppression and Restoration" section on page 3-33. For additional information about configuring these and other DOCSIS features, refer to the DOCSIS 1.1 for the Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
QoS Configuration
QoS configuration information is now included in the Cable Modem Database Manager, which is described further in the document titled DOCSIS 1.1 for the Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
QoS Profile Enforcement
This feature allows CMTS operators to override the provisioned service class of a cable modem at the time of registration with a CMTS local-static quality of service (QoS) profile. CMTS operators can control the QoS from the CMTS and eliminate any interference from improper local-rate limiting implemented on the cable modem. The CMTS provisions a registering cable modem with a default Data-over-Cable Service Interface Specifications (DOCSIS) 1.0 service class that is assigned by the operator. This service class has no upstream or downstream rate limits.
When the modem 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.
For configuration information, refer to the document titled QoS Profile Enforcement for the Cisco uBR7200 Series Router on Cisco.com:
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t4/feature/guide/qospr124.html
Time-of-Day Server
The Time-of-Day (ToD) server enables the Cisco Cable Modem Termination System (CMTS) to provide a ToD server to the CMs and other customer premises equipment (CPE) devices connected to its cable interfaces. The cable modem uses the ToD server to get the current date and time to accurately time-stamp its Simple Network Management Protocol (SNMP) messages and error log entries.
The Data-over-Cable System Interface Specifications (DOCSIS) 1.0 and 1.1 specifications require that a DOCSIS cable modem or other CPE device must specify the following time-related fields in the Dynamic Host Configuration Protocol (DHCP) request it sends during its initial power-on provisioning:
•
•
•
For configuration information, refer to the chapter titled Time of Day Server" in the Cisco Cable Modem Termination System Feature Guide on Cisco.com.
Trivial File Transfer Protocol Server
A DOCSIS-compliant cable modem requires access to three types of servers in order to successfully come online:
•
•
•
Type/Length/Value 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.
To display the Type/Length/Value (TLV) encodings parsed by the DOCSIS 1.1 TLV parser/encoder, use the debug cable tlvs command in privileged EXEC mode. The no form of this command disables debugging output.
debug cable tlvs
no debug cable tlvs
Refer to the following documents on Cisco.com for additional information about the TLV parser/encoder:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/DOCSIS11.html
•
http://www.cisco.com/warp/public/109/cable_faq_docsis11.shtml
UpstreamAddress 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 cable modem. Cable modem 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 uBR7200 series CMTS reports this. Using customer databases, administrators can cross-reference the spoofing cable modem and PC to prevent further usage.
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 5, "Managing Cable Modems on the Hybrid Fiber-Coaxial Network".
Upstream QoS Improvements
Supported QoS models for the upstream are:
•
•
•
•
For detailed information about QoS, refer to the DOCSIS 1.1 for the Cisco uBR7200 Series Universal Broadband Routers feature module on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/cmtsfg.html
Upstream QoS Models Supported
Supported QoS models for the upstream are as follows:
•
•
•
•
•
•
DOCSIS 1.1 Two-way Transmission (Cisco uBR7246VXR Router)
The Cisco uBR7200 series routers allow DOCSIS 1.1 two-way transmission of digital data and Voice over IP (VoIP) traffic over a hybrid fiber-coaxial (HFC) network. The Cisco uBR7200 series support IP routing with a wide variety of protocols and combinations of Ethernet, Fast Ethernet, Gigabit Ethernet, serial, High-Speed Serial Interface (HSSI), Packet over SONET (POS) OC-3 and OC-12c, and Asynchronous Transfer Mode (ATM) media.
Downstream Channel ID
This feature allows all cable modems in an HFC network to identify themselves via unique downstream channel IDs instead of their downstream frequencies.
To configure the downstream channel ID, use the cable downstream channel-id configuration command. Use the no form of this command to set the downstream channel ID to its default value.
cable downstream channel-id id
no cable downstream channel-id
Syntax DescriptionSyntax Description
For additional information, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t4/feature/guide/downchan.html
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Downstream Frequency Override
Downstream frequency override allows the CMTS administrator to change the downstream frequency assigned to a cable modem, overriding the frequency set in the cable modem DOCSIS configuration file.
To enable cable downstream frequency override, use the cable downstream override command in cable interface configuration mode. To disable the override feature, use the no form of this command.
cable downstream override
no cable downstream override
For additional command information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html
Downstream Packet Classifier
This feature helps to map packets into DOCSIS service flows. The Cisco CMTS supports downstream IP packet classifiers.
Downstream Packet Scheduler
This module controls all output packet queuing service on the downstream link of each cable interface.
Downstream Rate Shaping with IP Type of Service Bits
Cisco uBR7200 series routers support downstream data rate shaping on a per-modem basis. The Type of Service (ToS) bits in the IP packet header can be set to specify that packet's class of service, allowing packets for certain traffic flows (such as VoIP) to be given precedence over packets for other flows (such as data).
Downstream rate shaping with ToS bits allows you to configure multiple data rates for a given modem. Also, by specifying a maximum data rate for a particular ToS, you can override the common maximum downstream data rate. Packets that contain ToS bytes that have not been configured for downstream data rates continue to use the common data rate limits.
Prior releases set the ToS bits to zero; however, with the advent of virtual private network (VPN) and QoS applications, it is desirable to copy the ToS bits when the router encapsulates the packets using generic routing encapsulation (GRE). Thus, intermediate routers between tunnel endpoints can also take advantage of QoS features such as weighted fair queuing (WFQ) and weighted random early detection (WRED).
For additional information, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/ios/12_0t/12_0t5/feature/guide/tosbit.html
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 trade-off 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
•
•
•
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 documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_schd.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
DOCSIS 2.0 Feature Support
This section describes DOCSIS 2.0 enhancements supported on the Cisco uBR7200 series:
DOCSIS 2.0 A-TDMA Support
Support for DOCSIS 2.0 A-TDMA on the Cisco uBR7200 series commences with Cisco IOS Release 12.2(15)CX and continues with later releases in the 12.2 CX, 12.2 BC and 12.3 BC release trains.
The Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cards improve the maximum upstream bandwidth on existing DOCSIS 1.0 and DOCSIS 1.1 cable networks by providing a number of advanced PHY capabilities that have been specified by the new DOCSIS 2.0 specifications.
The DOCSIS 2.0 A-TDMA Support feature incorporates the following advantages and improvements of DOCSIS 2.0 networks:
•
•
–
–
–
Note
•
•
•
•
•
For additional information on DOCSIS 2.0 A-TDMA Support on the Cisco uBR-MC16U/X card, refer to the section, "DOCSIS 2.0 A-TDMA Support" in Configuring the Cisco uBR-MC16U/MC16X Cable Interface Line Card on Cisco.com:
For additional information on DOCSIS 2.0 A-TDMA Support on the Cisco uBR-MC28U/X card, refer to the section, "DOCSIS 2.0 A-TDMA Support" in Configuring the Cisco uBR-MC28U/MC28X Cable Interface Line Card on Cisco.com:
High Availability Features
Several powerful High Availability features are supported on the Cisco uBR7200 series:
•
•
•
•
•
•
•
Cisco DDC (Dual DOCSIS Channel)
The Cisco Dual DOCSIS Channel (DDC) feature provides redundancy to cable voice and data customers by using two or three CMTSs with connected RF upstreams and downstreams. Redundancy is provided by controlling each CMTS on which the cable modems register, and by allowing movement of the cable modems between the Cisco CMTS systems.
Cisco DDC provides redundancy during planned downtime, especially during software upgrades, with minimal configuration or control external to the Cisco CMTS.
For information about configuring, maintaining and troubleshooting DDC on the Cisco uBR7246VXR router, refer to the section "Configuring Dual DOCSIS Channel on the Cisco uBR7246VXR Universal Broadband Router" in the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/docs_DDC.html
DRP Server Agent
The Director Response Protocol (DRP) is a simple User Datagram Protocol (UDP)-based application developed by Cisco Systems. It enables Cisco's DistributedDirector product to query routers (DRP Server Agents) in the field for Border Gateway Protocol (BGP) and Interior Gateway Protocol (IGP) routing table metrics between distributed servers and clients. DistributedDirector, a separate standalone product, uses DRP to transparently redirect end-user service requests to the topologically closest responsive server. DRP enables DistributedDirector to provide dynamic, scalable, and "network intelligent" Internet traffic load distribution between multiple geographically dispersed servers.
DRP Server Agents are border routers (or peers to border routers) that support the geographically distributed servers for which DistributedDirector service distribution is desired. Note that, because DistributedDirector makes decisions based on BGP and IGP information, all DRP Server Agents must have access to full BGP and IGP routing tables. For configuration information, refer to the section titled "Configuring a DRP Server Agent" in the Cisco IOS IP Configuration Guide, Release 12.2.
DSX Messages and Synchronized PHS Information
Cisco IOS Release 12.3(17a)BC introduces support for PHS rules in a High Availability environment. In this release, and later releases, PHS rules synchronize and are supported during a switchover event of these types:
•
•
For additional information about these enhancements, and related High Availability features, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
•
http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html
Globally Configured HCCP 4+1 Redundancy on the Cisco uBR7246VXR Router
Cisco IOS Release 12.3(17a)BC introduces support for HCCP 4+1 Redundancy on the Cisco uBR7246VXR router. Global configuration makes this High Availability feature quick to implement in the HCCP redundancy scheme.
In this High Availability configuration, four Working router chassis are supported with one Protect router chassis. These five routers are further cabled and configured with two Cisco RF Switches in the same rack using the Cisco Hot Standby Connection to Connection (HCCP) protocol.
HCCP 4+1 Redundancy is a global configuration for all the Cisco uBR7246VXR routers in the scheme. HCCP 4+1 Redundancy supports the Cisco uBR-MC28U broadband processing engine (BPE), configured in inter-chassis protection, where the Working and Protect cable interface line cards or BPEs are operating in different router chassis. A switchover event applies to an entire cable interface line card.
Note
For additional information about HCCP 4+1 Redundancy, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
HCCP Support for the Cisco uBR-MC16S Cable Interface Line Card
Cisco IOS Release 12.1(7)EC adds support for the Cisco uBR-MC16S cable interface line card when used in an HCCP 1+1 redundant configuration. Previously, the Cisco uBR-MC16S card could be used in a redundant configuration only by first disabling its intelligent spectrum management features.
In Cisco IOS Release 12.1(7)EC and later releases, the Cisco uBR-MC16S card can be used as the protect cable interface or working cable interface, with either another Cisco uBR-MC16S card or a Cisco uBR-MC16C card. Table 9 shows how a switchover in each of these configurations affects the intelligent spectrum management features of the Cisco uBR-MC16S card.
For additional information, refer to Advanced Spectrum Management Features for the Cisco uBR-MC16S Spectrum Management Card on Cisco.com.
Note
HCCP N+1 Redundancy
HCCP N+1 Redundancy is made possible with the addition of the Cisco RF Switch to your cable headend network. Together with the Cisco uBR10012 and/or the Cisco uBR7246VXR routers, the Cisco RF Switch provides a fully redundant system that enables cable operators to achieve PacketCable system availability, minimize service disruptions, and simplify operations.
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 system failure.
Beginning with Cisco IOS Release 12.2(15)BC2, 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 configuration information about HCCP N+1 Redundancy, refer to HCCP N+1 Redundancy for the Cisco Cable Modem Termination System on Cisco.com:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
High Availability Features in Cisco IOS Release 12.3(13a)BC
Cisco IOS Release 12.3(13a)BC removes support for HCCP N+1 Redundancy on the Cisco uBR7200 series routers. Associated configuration, show, and debug commands are not supported in this release.
Note
HCCP N+1 Redundancy for the Cisco CMTS is described for earlier releases in this and additional documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
High Availability Support for Encrypted IP Multicast
Cisco IOS Release 12.3(17a)BC introduces support for IP Multicast streams during switchover events in a High Availability environment. This feature is supported for Route Processor Redundancy Plus (RPR+), N+1 Redundancy, and encrypted BPI+ streams.
For additional information about IP Multicast and High Availability, refer to these documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/ubrmibv5.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdmic.html
•
http://www.cisco.com/en/US/tech/tk828/technologies_case_study0900aecd802e2ce2.shtml
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html
Hot-Standby 1+1 Redundancy
The Hot-Standby 1+1 Redundancy feature offers the ability to provide high system availability when configuring a Cisco uBR7200 series universal broadband router to wait in hot-standby mode to protect another Cisco uBR7200 series router in case of system failure.
The 1+1 redundancy feature is essential in a residential Voice over IP (VoIP) cable network, since it provides a three- to five-second automatic system recovery time, thus helping to eliminate "call drops" in the VoIP cable network. System failure in a non-redundancy (unprotected) deployment results in loss of all voice calls in progress as well as all voice calls in "setup" phase, because the CMTS requires human intervention to reconfigure and bring the CMTS back online.
Configuration for 1+1 redundancy takes place at the cable interface line card interface level. That is, rather than assigning an entire Cisco uBR7200 series router to support another Cisco uBR7200 series router, individual interfaces on one Cisco uBR7200 series router are configured to protect individual interfaces installed in a different Cisco uBR7200 series router.
Note
You can configure the system to switch over automatically when the interface state of a cable interface line card interface moves from "up" to "down." Alternatively, you can manually force a switch over.
Note
For more information on the 1+1 redundancy feature, including information on configuration tasks and command reference, refer to the document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/HCCPfeat.html
IF Muting for HCCP N+1 Redundancy
Beginning with Cisco IOS Release 12.2(15)BC2a, Cisco supports IF Muting with both SNMP and non-SNMP-capable upconverters in HCCP N+1 Redundancy. IF Muting offers the following benefits:
•
•
•
For additional information about IF Muting and configuring HCCP N+1 Redundancy, refer to the following document on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html#wp1049303
Intercept Features
The Cisco uBR7200 Series supports several intercept features through multiple Cisco IOS release trains:
•
•
•
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
Additional Information
Refer also the Service Independent Intercept (SII) feature in this document. For additional information, refer to the following documents on Cisco.com:
•
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
Cable Monitor Enhancements
Cisco IOS Release 12.3(17a)BC introduces the following enhancements to the cable monitor feature:
•
•
For additional information about this enhancements to the cable monitor feature, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
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 uBR7200 series routers. This feature supports two new configuration commands for enabling and setting COPS processes. The COPS feature in Cisco 12.3(13a)BC enables the following COPS functions:
COPS DSCP Marking for the Cisco CMTS
This feature allows you to change the DSCP marking for COPS messages that are transmitted or received by the Cisco router. Differentiated Services Code Point (DSCP) values are used in Quality of Service (QoS) configurations on a Cisco router. DSCP summarizes the relationship between DSCP and IP precedence.
Cisco IOS Release 12.3(13a)BC supports this function with the cops ip dscp command in global configuration mode.
COPS TCP Window Size for the Cisco CMTS
This feature allows you to override the default TCP receive window size that is used by COPS processes. This setting can be used to prevent the COPS server from sending too much data at one time.
Cisco IOS Release 12.3(13a)BC supports this function with the cops tcp window-size command in global configuration mode.
Note
cops ip dscp
To specify the marking for COPS messages that are transmitted by the Cisco router, use the cops ip dscp command in global configuration mode. To remove this configuration, use the no form of this command.
cops ip dscp x
no cops ip dscp
Syntax Description
Defaults
•
•
Usage Guidelines
•
•
•
Examples
The following example illustrates the cops ip dscp command with supported command variations:
Router(config)# cops ip dscp ?<0-63> DSCP valueaf11 Use AF11 dscp (001010)af12 Use AF12 dscp (001100)af13 Use AF13 dscp (001110)af21 Use AF21 dscp (010010)af22 Use AF22 dscp (010100)af23 Use AF23 dscp (010110)af31 Use AF31 dscp (011010)af32 Use AF32 dscp (011100)af33 Use AF33 dscp (011110)af41 Use AF41 dscp (100010)af42 Use AF42 dscp (100100)af43 Use AF43 dscp (100110)cs1 Use CS1 dscp (001000) [precedence 1]cs2 Use CS2 dscp (010000) [precedence 2]cs3 Use CS3 dscp (011000) [precedence 3]cs4 Use CS4 dscp (100000) [precedence 4]cs5 Use CS5 dscp (101000) [precedence 5]cs6 Use CS6 dscp (110000) [precedence 6]cs7 Use CS7 dscp (111000) [precedence 7]default Use default dscp (000000)ef Use EF dscp (101110)Additional COPS Information
Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.
For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
•
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t1/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
Defaults
The default COPS TCP window size is 4000 bytes.
Usage Guidelines
This command does not affect existing connections to COPS servers. Once you issue this command, this function is supported only for new connections after that point in time.
Examples
The following example configures the TCP window size to be 64000 bytes.
Router(config)# cops tcp window-size 64000The following example illustrates online help for this command:
Router(config)# cops tcp window-size ?<516-65535> Size in bytesAdditional COPS Information
Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.
For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
•
http://www.cisco.com/en/US/docs/ios/12_1t/12_1t1/feature/guide/CopsRSVP.html
Service Independent Intercept (SII) Support on the Cisco uBR7200 Series
The 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 uBR7200 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 in Cisco IOS release 12.3(13a)BC includes these functions:
•
•
•
Note
Cisco IOS Release 12.3(13a)BC enables full Multiple Service Operator (MSO) compliance with SII and LI regulations. Service providers worldwide are legally required to allow government agencies to conduct surveillance on the service provider's traditional telephony equipment. The objective of the SII feature is to enable service providers with New World networks that legally allow government agencies to conduct electronic network surveillance.
Lawful Intercept (LI) describes the process and judicial authority by which law enforcement agencies conduct electronic surveillance of circuit and packet-mode communications. LI is authorized by judicial or administrative order and implemented for either voice or data traffic on the Cisco CMTS. Table 13 lists the differences between packet intercept and SII features
Additional Information
For additional information, refer to the following documents:
•
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html
•
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html
•
IP Broadcast and Multicast Features
The Cisco uBR7200 Series supports the following IP broadcast and Multicast feature:
•
Multicast QoS Support on the Cisco uBR7246VXR CMTS
Cisco IOS Release 12.3(13a)BC introduces support for Multicast downstream QoS feature. This feature t provides the ability to assign static mapping to a multicast group. The Multicast downstream QoS feature uses the existing infrastructure (DOCSIS 1.1 service flow) to assign a multicast service identifier (SID) to a multicast group used in the Baseline Privacy Interface (BPI) encryption feature.
When disabled, the Multicast downstream QoS feature does not impact any other features. The multicast packets to downstream cable interfaces are sent to the default service flow.
This feature is being implemented in response to CSCeg22989 which states, multicast traffic is not classified to any service flow, and therefore ends up queued on the default service flow. The default service flow has no specific QoS guarantees assigned to it. So once the interface approaches congestion level, multicast packets may be dropped.
Restrictions
•
•
•
•
•
New and Changed Commands
cable match address
Use the existing "cable match" command to assign QoS to a multicast group, with BPI either enabled or disabled.
router# cable match address <number>|<name> [service-class <name> [bpi-enable]]router# no cable match address [<number>|<name> [service-class <name> [bpi-enable]]]debug cable mcast-qos
Use this command to turn on CMTS Multicast Qos debugging.
router# debug cable mcast-qosIP Routing Features
The Cisco uBR7200 series router offers you several features to assist with IP routing configuration and performance.
•
•
•
•
•
•
•
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
