Table Of Contents
DOCSIS 3.0 Downstream Bonding for Bronze Certification
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
Assigning an RCC Template to a Cable Interface
Verifying the RCC Configuration
How to Configure Attribute Masks
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
Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification
DOCSIS 3.0 Downstream Bonding for Bronze Certification
Revised: March 16, 2009First Published: December 17, 2008The 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
•
•
•
•
•
•
•
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.
Restrictions for DOCSIS 3.0 Downstream Bonding for Bronze Certification
This feature has the following general restrictions:
•
•
•
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
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
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.
2.
3.
DETAILED STEPS
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.
2.
3.
4.
DETAILED STEPS
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:
•
•
•
•
•
Note
Prerequisites
At least one receive channel (RC) must be configured as a primary RC.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
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 rccRCC-ID RCP RCs MD-DS-SG CMs WB/RCC-TMPL1 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.
Note
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:
•
•
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:
•
•
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.
You can configure provisioned attribute masks for cable, wideband cable, and modular cable interfaces.
Prerequisites
•
•
Restrictions
•
•
Configuring Provisioned Attributes for a Cable Interface
The default provisioned attribute is zero for a cable interface.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Configuring Provisioned Attributes for a Modular Cable Interface
The default provisioned attribute is zero for a modular cable interface.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
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.
2.
3.
4.
DETAILED STEPS
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-flowSfid Sid Mac Address QoS Param Index Type Dir Curr Active BG / DSProv Adm Act State Time12 N/A 0014.0496.3f9e 4 4 4 prim DS act 3h17m DS 111 5 0014.0496.3f9e 3 3 3 prim US act 3h17m14 N/A 0014.0496.3f76 4 4 4 prim DS act 3h17m BG 10213 6 0014.0496.3f76 3 3 3 prim US act 3h17m16 N/A 0007.0e07.24af 4 4 4 prim DS act 3h17m DS 115 7 0007.0e07.24af 3 3 3 prim US act 3h17m18 N/A 0007.0e06.e1b5 4 4 4 prim DS act 3h17m DS 317 8 0007.0e06.e1b5 3 3 3 prim US act 3h17mTable 4 shows descriptions for the fields displayed by this command.
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.
2.
3.
4.
DETAILED STEPS
Configuration Example for an RCC
The following example shows how to define and configure an RCC template on a cable interface:
Router#configure terminalRouter(config)#cable rcc-template 1Router(config-rcc-template)#rcp-id 00 10 00 00 03Router(config-rcc-template)#receive-module 1 first-channel-center-frequency 555000000Router(config-rcc-template)#receive-channel 1 center-frequency 555000000 connected-receive-module 1 primaryRouter(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
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
MIBs
Technical Assistance
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.
•
•
•
•
•
•
•
•
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 Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification
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:
•
•
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.
Guest
