Cisco IOS CMTS Cable Software Configuration Guide, Release 12.2SC - DOCSIS 3.0 Downstream Bonding for Bronze Certification [Cisco uBR10000 Series Universal Broadband Routers]

Table Of Contents

DOCSIS 3.0 Downstream Bonding for Bronze Certification

Finding Feature Information

Contents

Prerequisites for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Restrictions for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Information About DOCSIS 3.0 Downstream Bonding for Bronze Certification

Receive Channel Profile

Receive Channel Configuration

RCC Template

Channel Assignment

Downstream Traffic Forwarding

How to Configure an RCC Encoding

Configuring an RCC Template

Prerequisites

Assigning an RCC Template to a Cable Interface

Configuring an RCC Encoding

Prerequisites

Verifying the RCC Configuration

How to Configure Attribute Masks

Prerequisites

Restrictions

Configuring Provisioned Attributes for a Cable Interface

Configuring Provisioned Attributes for a Modular Cable Interface

Configuring Provisioned Attributes for a Wideband Cable Interface

Verifying the Attribute-Based Service Flow Assignments

Receive Channel Profile Verbose Reporting

Enabling Verbose Reporting for Receive Channel Profiles

Configuration Example for an RCC

Additional References

Related Documents

Standards

MIBs

Technical Assistance

Command Reference

Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification

DOCSIS 3.0 Downstream Bonding for Bronze Certification

Revised: March 16, 2009

First Published: December 17, 2008

The DOCSIS 3.0 Downstream Bonding for Bronze Certification feature helps cable operators offer new, more bandwidth-intensive services by adding one or more additional downstream quadrature amplitude modulation (QAM) channels to the standard broadband DOCSIS system.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To see a list of the releases in which each feature is supported, see the "Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Contents

•Prerequisites for DOCSIS 3.0 Downstream Bonding for Bronze Certification

•Restrictions for DOCSIS 3.0 Downstream Bonding for Bronze Certification

•Information About DOCSIS 3.0 Downstream Bonding for Bronze Certification

•How to Configure an RCC Encoding

•How to Configure Attribute Masks

•Receive Channel Profile Verbose Reporting

•Configuration Example for an RCC

•Additional References

•Command Reference

•Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Prerequisites for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Table 1 shows the hardware compatibility prerequisites for the DOCSIS 3.0 Downstream Bonding for Bronze Certification feature.

Table 1 Cable Hardware Compatibility Matrix for Downstream Bonding

CMTS Platform

Processor Engine

Cable Interface Line Cards

Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.2(33)SCB

•PRE2

•PRE4

Cisco uBR10-MC5X20S/U/H

Restrictions for DOCSIS 3.0 Downstream Bonding for Bronze Certification

This feature has the following general restrictions:

•Although verbose receive channel profile (RCP) reporting can be enabled on a given cable interface, this does not eliminate the need to define a receive channel configuration (RCC) template in order to support a non-standard RCP ID.

•An RCC template configuration cannot be modified or removed if it is associated to any Media Access Control (MAC) domain. The operator must remove the association first in order to make modifications to an existing RCC template.

•The CMTS does not create a new RCP or modify an existing RCP based on the verbose RCP report from a cable modem (CM) at run time. The operator should explicitly add an RCC template and the RCP ID association per RCP requirements.

Information About DOCSIS 3.0 Downstream Bonding for Bronze Certification

The DOCSIS 3.0 Downstream Bonding for Bronze Certification feature enables high-speed broadband access (100 Mbps) and helps cable operators offer more bandwidth-intensive services by adding one or more additional downstream quadrature amplitude modulation channels to the standard broadband DOCSIS system. This new set of downstream channels is grouped into one larger channel, known as a bonded channel.

Channel bonding combines several radio frequency (RF) channels into one virtual channel. Data rates in this virtual channel range from hundreds of megabits to potentially gigabits per second creating more available bandwidth in the network.

Receive Channel Profile

A receive channel profile (RCP) is an encoding that represents the receive channels and receive modules of a cable modem (CM). A CM communicates to the CMTS one or more RCP encodings within its registration request using either verbose description, which contains complete subtype encoding defined in DOCSIS 3.0, or simple description, which only contains RCP identifiers. The CM reporting method is controlled by the CMTS using a MAC Domain Descriptor (MDD).

Receive Channel Configuration

A cable modem reports its ability to receive multiple channels with one or more RCP encodings in a REG-REQ or REG-REQ-MP message. Each receive channel profile describes a logical representation of the CM's downstream physical layer in terms of receive channels (RCs) and receive modules (RMs). The CMTS initially configures the CM's receive channels and receive modules with a receive channel configuration (RCC) encoding in the registration response.

Cisco IOS Release 12.2(33)SCB supports any arbitrary RCP ID configuration and receive channel configuration.

RCC Template

You can configure one or more receive channel configuration (RCC) templates for an RCP. An RCC template configures the physical layer components described by an RCP, including receive modules and receive channels to specific downstream frequencies. The template also specifies the interconnections among receive modules, or between a receive module and a receive channel. An RCC template can be associated to a wideband or cable interface.

Channel Assignment

The CMTS assigns a receive channel configuration encoding to a DOCSIS 3.0-certified CM operating in a Multiple Receive Channel (MRC) mode during CM registration. Prior to Cisco IOS Release 12.2(33)SCB, the channel assignment was based on a random selection from eligible bonding groups.

With the implementation of this feature, the DOCSIS 3.0-certified CM reports its receiving capabilities and characteristics using the receive channel profile Type-Length-Value (TLV) list in the registration request message. Based on this report, the CMTS assigns an RCC encoding that is compatible with the reported RCP. Cable modems operating in an MRC mode are assigned an RCC encoding that is derived from an RCC template, which is associated with an RCP. An RCC encoding can also be derived from a wideband interface configuration if an RCC template is not configured and associated to the Media Access Control (MAC) domain of a particular CM.

Downstream Traffic Forwarding

DOCSIS 3.0 introduces the concept of assigning service flows of CMs, which are operating in an MRC mode, to downstream (DS) channels or bonding groups. Forwarding interfaces assigned to service flows (SFs) can be either DS channel interfaces (cable or modular cable interfaces) or bonding groups (wideband interfaces). These forwarding interfaces will override the default CMTS assignment of a service flow to a wideband interface.

Note Valid interfaces that are available for SF assignment must be a subset of the CM's assigned RCC encoding.

How to Configure an RCC Encoding

The following tasks describe how to configure a receive channel configuration encoding for a receive channel profile:

•Configuring an RCC Template

•Assigning an RCC Template to a Cable Interface

•Configuring an RCC Encoding

•Verifying the RCC Configuration

Configuring an RCC Template

You must configure an RCC template with a unique RCP ID for a particular CMTS. A valid RCC template consists of a configured RCP ID, receive modules (RMs), and receive channels (RCs).

Prerequisites

In order to configure an RCC template, the verbose encoding of the corresponding RCP ID must be available.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable rcc-template index

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
cable rcc-template index
Example:

Router(config)# cable rcc-template 1
Defines an RCC template.

•index—Specifies an RCC template ID in the range 1 to 255.
Assigning an RCC Template to a Cable Interface

After defining an RCC template, you must assign the template to a cable interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable slot/subslot/port

4. cable rcc-template index

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface cable slot/subslot/port
Example:

Router(config)# interface cable7/0/0
Specifies the cable interface line card, where:

•slot—Specifies the chassis slot number of the cable interface line card.

•subslot—(Cisco uBR10012 only) Specifies the secondary slot number of the cable interface line card. Valid subslots are 0 or 1.

•port—Specifies the downstream port number.
Step 4
cable rcc-template index
Example:

Router(config-if)# cable rcc-template 1
Assigns the RCC template to the specified cable interface.

•index—Specifies the template you want to assign to the cable interface. The valid range is 1 to 255.
Configuring an RCC Encoding

You can configure an RCC encoding after defining an RCC template. The CMTS derives an RCC or RCCs from the RCC template for each MAC Domain Downstream Service Group (MD-DS-SG). Each RCC encoding contains all operational DS channels with their channel parameters, including the frequency match RC attribute specified in the RCC template. An RCC template specifies the intended receive channel assignment in the available DS spectrum.

The following information is required for RCC configuration:

•The RCC templates associated to the MAC domain

•DS channel physical parameters including frequency and connected-receive-module index

•Modular cable interface operational state (primary indicator)

•DS channel membership to the MD-DS-SG

•CM membership to the MD-DS-SG

Note If an RCC template is removed from a MAC domain through configuration, the CMTS removes all of the RCC encodings derived from the RCC template, and all CMs assigned to the RCC encodings are marked offline.

Prerequisites

At least one receive channel (RC) must be configured as a primary RC.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable rcc-template index

4. rcp-id rcp-id

5. receive-module index first-channel-center-frequency Hz [connected-receive-module index]

6. receive-channel index center-frequency Hz connected-receive-module index [primary]

DETAILED STEPS
Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
cable rcc-template index
Example:

Router(config)# cable rcc-template 1
Defines the RCC template.

•index—Specifies an RCC template ID in the range 1 to 255.
Step 4

rcp-id rcp-id
Example:

Router(config-rcc-template)# rcp-id 00 10 00 00 03

•rcp-id—Specifies an RCP ID for the RCC template. The valid range is 00 00 00 00 00 to FF FF FF FF. By default the RCP ID is set to 00 00 00 00 00.

Step 5

receive-module index first-channel-center-frequency Hz [connected-receive-module index]
Example:

Router(config-rcc-template)# receive-module 1 first-channel-center-frequency 555000000 connected-receive-module 1

Specifies a receive module configuration for the selected RCP.

•index—Specifies the index value for the receive module. The valid range is 1 to 10.

•first-channel-center-frequency—Specifies the center frequency of the first channel of the receive module channel block. The first channel center frequency assignment defines a frequency within the minimum and maximum range of center frequencies configured for the RM.

•Hz—Specifies the center frequency value in Hz. The valid range is 55000000 to 858000000.

•connected-receive-module—(Optional) Specifies a nested receive module in the RCC template. Generally, only one receive module is configured for an RCC template.

•index—(Optional) Specifies the index value for the connected receive module. The valid range is 1 to 10.

Step 6

receive-channel index center-frequency Hz connected-receive-module index [primary]
Example:

Router(config-rcc-template)# receive-channel 1 center-frequency 555000000 connected-receive-module 1 primary

Specifies a receive channel configuration for the selected RCP.

•index—Specifies the index value for the receive channel. The valid range is 1 to 10.

•center-frequency—Specifies the center frequency for the receive channel.

•Hz—Specifies the center frequency value in Hz. The valid range is 55000000-858000000.

•connected-receive-module—Specifies a nested receive module in the RCC template. Generally, only one receive module is configured for an RCC template.

•index—Specifies the index value for the connected receive module. The valid range is 1 to 10.

•Primary—(Optional) Indicates that it is a CM primary channel and an RCC can be derived from this channel.
Verifying the RCC Configuration

To verify the runtime RCCs on a cable interface, use the show cable mac-domain rcc command as shown in the following example:
Router# show cable mac-domain c8/0/0 rcc
RCC-ID   RCP                 RCs MD-DS-SG CMs   WB/RCC-TMPL
1        00 00 00 00 00      2   0        0     WB (101)
2        00 10 00 00 03      3   2        0     RCC-TMPL (1)
Table 2 shows descriptions for the fields displayed by this command.

Table 2 show cable mac-domain rcc Field Descriptions

Field

Description

RCC-ID

RCC index per MAC domain.

RCP

The receive channel profile associated with the RCC object.

RCs

Total number of DS channels.

MD-DS-SG

Indicates the MAC domain DS service group for which the RCC is configured.

CM

Total number of CMs associated with the RCC object.

WB/RCC-TMPL

Indicates the wideband interface or the RCC template.

Note A zero (0) value in the RCP or MD-DS-SG field indicates that the RCC encoding is configured directly through a wideband interface configuration and not through any RCC templates.

How to Configure Attribute Masks

DOCSIS 3.0 introduces the concept of assigning service flows to channels or bonding groups based on binary attributes. The attribute masks configured on a cable interface, or a modular or wideband interface are called provisioned attribute masks.

Following are the two types of attributes:

•Specification-defined attributes—They have default values based on the characteristics of the channel or bonding group.

•Operator-defined attributes—They default to zero.

The operator can configure a provisioned attribute mask for each channel and provisioned bonding group to assign values to the operator-defined binary attributes. The operator can also assign new values to override the default values of the specification-defined attributes.

The operator can configure a required attribute mask and a forbidden attribute mask for a service flow in the CM configuration file. These required and forbidden attribute masks are optionally provided on the DOCSIS 3.0 service flows and are matched with the provisioned attribute masks of the interfaces.

Each service flow is optionally configured with the following TLV parameters:

•Service flow required attribute mask—To configure this, assign a service flow to a channel that has a 1-bit in all positions of its provisioned attribute mask corresponding to the 1-bit in the service flow required attribute mask.

•Service flow forbidden attribute mask—To configure this, assign a service flow to a channel that has a 0-bit in all positions of its provisioned attribute mask corresponding to the 1-bit in the service flow forbidden attribute mask.

Additionally, in a CM-initiated dynamic service request, the CM can include a required attribute mask and a forbidden attribute mask for a service flow. The CMTS assigns service flows to channels or bonding groups so that all required attributes are present and no forbidden attributes are present in the CM configuration file.

Table 3 lists the supported binary attributes for channels and bonding groups.

Table 3 Binary Attributes

Bit Position

Definition

Bit 0

Bonded—This bit is zero for all individual channel interfaces and one for all bonding groups.

Bit 1

Low latency—This bit is set when the interface can provide relatively low latency service. This bit is set to zero for all channels, and left up to the operator to define.

Bit 2

High availability—This bit is set to zero for all channels, and left up to the operator to define.

Bit 3:15

Reserved—Set to zero.

Bit 16:31

Operator defined—Set to zero by default.

You can configure provisioned attribute masks for cable, wideband cable, and modular cable interfaces.

Prerequisites

•To assign an interface to a wideband CM's service flow, the interface must be a subset of the CM's RCC.

•To assign a service flow to a modular shared port adapter (SPA) channel, the corresponding modular cable interface must be configured and operational.

Restrictions

•The dynamic bonding group is not supported.

•The service flow from a narrowband CM is always assigned to the primary interface of the CM. No attribute checking is performed in this case.

Configuring Provisioned Attributes for a Cable Interface

The default provisioned attribute is zero for a cable interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable slot/subslot/port

4. cable downstream attribute-mask mask

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface cable slot/subslot/port
Example:

Router(config)# interface cable 7/0/0
Specifies the cable interface line card and enters interface configuration mode.

•slot—Specifies the chassis slot number of the cable interface line card.

•subslot—(Cisco uBR10012 only) Specifies the secondary slot number of the cable interface line card. Valid subslots are 0 or 1.

•port—Specifies the downstream port number.
Step 4

cable downstream attribute-mask mask
Example:

Router(config-if)# cable downstream attribute-mask 800000ff

Specifies the mask for the interface.
Configuring Provisioned Attributes for a Modular Cable Interface

The default provisioned attribute is zero for a modular cable interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface modular-cable slot/bay/port:nb-channel-number

4. cable downstream attribute-mask mask

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface modular-cable slot/bay/port:nb-channel-number
Example:

Router(config)# interface modular-cable 1/0/1:5
Specifies the modular cable interface and enters interface configuration mode.

•slot—The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3 can be used for SIPs.

•bay—The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and 1 (lower bay).

•port—Specifies the interface number on the SPA.

•nb-channel-number—Specifies the narrowband channel number.
Step 4

cable downstream attribute-mask mask
Example:

Router(config-if)# cable downstream attribute-mask 800000ff

Specifies the mask for the interface.
Configuring Provisioned Attributes for a Wideband Cable Interface

The default provisioned attribute is 0x80000000 for a wideband cable interface, and the zero bit is automatically added to the wideband cable interface whenever an attribute is configured for that interface.

SUMMARY STEPS

1. enable

2. configure terminal

3. interface wideband-cable slot/bay/port:wideband-channel

4. cable downstream attribute-mask mask

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface wideband-cable
slot/bay/port:wideband-channel
Example:

Router(config)# interface wideband-cable 1/0/1:4
Specifies the wideband cable interface and enters interface configuration mode.

•slot—The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3 can be used for SIPs.

•bay—The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and 1 (lower bay).

•port—Specifies the interface number on the SPA.

•wideband-channel—Specifies the wideband channel number. The valid range is 0 to 11.
Step 4

cable downstream attribute-mask mask
Example:

Router(config-if)# cable downstream attribute-mask 800000ff

Specifies the mask for the interface.
Verifying the Attribute-Based Service Flow Assignments

To verify the attribute-based assignment of service flows on a cable interface, use the show interface cable service-flow command as shown in the following example:
Router# show interface cable 3/0 service-flow 
Sfid  Sid   Mac Address     QoS Param Index Type  Dir  Curr  Active  BG / DS
                            Prov  Adm  Act             State Time
12    N/A   0014.0496.3f9e   4     4    4   prim  DS   act   3h17m   DS 1
11    5     0014.0496.3f9e   3     3    3   prim  US   act   3h17m   
14    N/A   0014.0496.3f76   4     4    4   prim  DS   act   3h17m   BG 102
13    6     0014.0496.3f76   3     3    3   prim  US   act   3h17m   
16    N/A   0007.0e07.24af   4     4    4   prim  DS   act   3h17m   DS 1
15    7     0007.0e07.24af   3     3    3   prim  US   act   3h17m   
18    N/A   0007.0e06.e1b5   4     4    4   prim  DS   act   3h17m   DS 3
17    8     0007.0e06.e1b5   3     3    3   prim  US   act   3h17m   
Table 4 shows descriptions for the fields displayed by this command.

Table 4 show interface cable service-flow Field Descriptions

Field

Description

Sfid

Identifies the service flow identification number.

Note Primary service flow IDs are displayed even for offline CMs because they are needed for modem re-registration.

Sid

Identifies the service identification number (upstream service flows only).

Mac Address

Identifies the MAC address for the CM.

QoS Parameter Index Prov

Identifies the QoS parameter index for the provisioned state of this flow.

QoS Parameter Index Adm

Identifies the QoS parameter index for the Admitted state of this flow.

QoS Parameter Index Act

Identifies the QoS parameter index for the Active state of this flow.

Type

Indicates if the service flow is the primary flow or a secondary service flow. Secondary service flows are identified by an "S" (created statically at the time of registration, using the DOCSIS configuration file) or "D" (created dynamically by the exchange of dynamic service messages between the CM and CMTS).

Dir

Indicates if this service flow is downstream (DS) or upstream (US).

Curr State

Indicates the current run-time state of the service flow.

Active Time

Indicates the length of time this service flow has been active.

BG/DS

Indicates the bonding group ID or the downstream RFID of the forwarding interface assigned to the downstream service flow.

Receive Channel Profile Verbose Reporting

A receive channel profile is an encoding that represents the receive channels and receive modules of a CM. A CM communicates to the CMTS one or more RCP encodings within its registration request using either verbose description, which contains complete subtype encodings defined in DOCSIS 3.0, or simple description, which only contains RCP identifiers.

Enabling Verbose Reporting for Receive Channel Profiles

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable slot/subslot/port

4. cable rcp-control verbose

DETAILED STEPS
Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.
Step 3
interface cable slot/subslot/port
Example:

Router(config)# interface cable7/0/0
Specifies the cable interface line card and enters interface configuration mode.

•slot—Specifies the chassis slot number of the cable interface line card.

•subslot—(Cisco uBR10012 only) Specifies the secondary slot number of the cable interface line card. Valid subslots are 0 or 1.

•port—Specifies the downstream port number
Step 4

cable rcp-control verbose
Example:

Router(config-if)# cable rcp-control verbose

Enables RCP reporting with verbose description.
Configuration Example for an RCC

The following example shows how to define and configure an RCC template on a cable interface:
Router#configure terminal
Router(config)#cable rcc-template 1
Router(config-rcc-template)#rcp-id 00 10 00 00 03
Router(config-rcc-template)#receive-module 1 first-channel-center-frequency 555000000
Router(config-rcc-template)#receive-channel 1 center-frequency 555000000 
connected-receive-module 1 primary
Router(config-rcc-template)#receive-channel 2 center-frequency 561000000 connected-receive-module 1

Additional References

The following sections provide references related to the DOCSIS 3.0 Downstream Bonding for Bronze Certification feature.

Related Documents

Related Topic

Document Title

Commands on the Cisco CMTS (universal broadband routers)

Cisco IOS CMTS Cable Command Reference

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

Cisco DOCSIS 3.0 Downstream Solution

Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide

http://www.cisco.com/en/US/docs/cable/cmts/wideband/solution/guide/release_2.0/ds_solu.html

DOCSIS 3.0 Downstream Channel Bonding

Cisco Cable Wideband Solution Design and Implementation Guide

http://www.cisco.com/en/US/docs/cable/cmts/wideband/solution/guide/release_1.0/wb_solu.html

Standards

Standard

Title

CM-SP-MULPIv3.0-I08-080522

MAC and Upper Layer Protocols Interface Specifications

MIBs

MIB

MIBs Link

No new or modified MIBs are supported, and support for existing MIBs has not been modified.

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://www.cisco.com/go/mibs

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Command Reference

The following commands are introduced or modified in the feature or features documented in this module. For information about these commands, see the Cisco IOS CMTS Cable Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html. For information about all Cisco IOS commands, use the Command Lookup Tool at http://tools.cisco.com/Support/CLILookup or the Cisco IOS Master Command List, All Releases, at http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html.

•cable rcc-template

•cable rcp-control verbose

•rcp-id

•receive-module

•receive-channel

•show cable mac-domain rcc

•show interface cable service-flow

•show cable modem

Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Table 5 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.

Note Table 5 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release. Unless noted otherwise, subsequent releases of that Cisco IOS software release also support that feature.

Table 5 Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification

Feature Name

Releases

Feature Information

DOCSIS 3.0 Downstream Bonding for Bronze Certification

12.2(33)SCB

This feature was introduced to meet the Bronze requirements for the DOCSIS 3.0 downstream bonding. It also includes receive channel configuration for receive channel profiles.

In Cisco IOS Release 12.2(33)SCB, this feature was introduced on the Cisco uBR10012 router.

The following sections provide information about this feature:

•How to Configure an RCC Encoding

•How to Configure Attribute Masks

•Receive Channel Profile Verbose Reporting

CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2008 Cisco Systems, Inc. All rights reserved.