DOCSIS 3.0 Downstream Bonding for Bronze Certification

First Published: December 17, 2008

Last Updated: November 29, 2010

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 find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http:/​/​tools.cisco.com/​ITDIT/​CFN/​. An account on http:/​/​www.cisco.com/​ is not required.

Contents

Prerequisites for DOCSIS 3.0 Downstream Bonding for Bronze Certification

The table below shows the hardware compatibility prerequisites for the DOCSIS 3.0 Downstream Bonding for the Bronze Certification feature.


Note
The hardware components introduced in a given Cisco IOS Release will be supported in all subsequent releases unless otherwise specified.
Table 1 Cable Hardware Compatibility Matrix for Downstream Bonding

CMTS Platform

Processor Engine

Cable Interface Cards

Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.2(33)SCA and later releases

  • PRE2

Cisco IOS Release 12.2(33)SCB and later releases

  • PRE4

Cisco IOS Release 12.2(33)SCH and later releases

  • PRE5

Cisco IOS Release 12.2(33)SCB and later releases

  • Cisco uBR10-MC5X20U/H

Cisco IOS Release 12.2(33)SCC and later releases

  • Cisco UBR-MC20X20V

Cisco IOS Release 12.2(33)SCE and later releases

  • Cisco uBR-MC3GX60V 1

Cisco uBR7246VXR Universal Broadband Router

Cisco IOS Release 12.2(33)SCA and later releases

  • NPE-G1
  • NPE-G2

Cisco IOS Release 12.2(33)SCA and later releases

  • Cisco uBR-MC28U/X

Cisco IOS Release 12.2(33)SCD and later releases

  • Cisco uBR-MC88V 2

Cisco uBR7225VXR Universal Broadband Router

Cisco IOS Release 12.2(33)SCA and later releases

  • NPE-G1

Cisco IOS Release 12.2(33)SCB and later releases

  • NPE-G2

Cisco IOS Release 12.2(33)SCA and later releases

  • Cisco uBR-E-28U
  • Cisco uBR-E-16U
  • Cisco uBR-MC28U/X

Cisco IOS Release 12.2(33)SCD and later releases

  • Cisco uBR-MC88V
1 Cisco uBR3GX60V cable interface line card is not compatible with PRE2. You must use PRE4 with the Cisco uBR3GX60V cable interface line card.
2 Cisco uBR-MC88V cable interface line card is not compatible with NPE-G1. You must use NPE-G2 with the Cisco uBR-MC88V cable interface line card.

Restrictions for DOCSIS 3.0 Downstream Bonding for Bronze Certification

  • 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 to support a non-standard RCP ID.
  • An RCC template configuration cannot be modified or removed if it is associated to any MAC domain. The operator must remove the association first 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 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 enables high-speed broadband access and helps cable operators offer more bandwidth-intensive services by adding one or more additional downstream quadrature amplitude modulation (QAM) 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 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

An RCP is an encoding that represents the receive channels and receive modules of a cable modem. A cable modem 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 cable modem 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 cable modem’s downstream physical layer in terms of receive channels (RCs) and receive modules (RMs). The CMTS initially configures the cable modem’s receive channels and receive modules with an RCC encoding in the registration response.

Beginning Cisco IOS Release 12.2(33)SCB, this feature supports any arbitrary RCP ID configuration and receive channel configuration on a Cisco uBR10012 universal broadband router and Cisco IOS Release 12.2(33)SCD provides this support on the Cisco uBR7225VXR and Cisco uBR7246VXR routers.

RCC Template

You can configure one or more 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 only to the cable interface (MAC domain).

Channel Assignment

The CMTS assigns a receive channel configuration encoding to a DOCSIS 3.0-certified cable modem operating in a Multiple Receive Channel (MRC) mode during cable modem 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 cable modem 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.

RCC encodings may be derived from RCC templates or from a wideband-cable interface configuration.


Note
The cable modem can support up to 8 physical downstream channels. If you do not have 8 channel bonding group configured, the modem can lock a downstream primary channel and then decide to either use the bonding group that primary is part of or use the other 4-channel bonding group, which makes it appear as 5 downstream channels.

In the following example you can see the CMTS or cable modem add the 5th downstream channel when you use two wideband interfaces with 4 DS channels. 

Downstream Channel DCID RF Channel : 40 1/2/0:16
Downstream Channel DCID RF Channel : 28 1/2/0:4
Downstream Channel DCID RF Channel : 29 1/2/0:5
Downstream Channel DCID RF Channel : 30 1/2/0:6
Downstream Channel DCID RF Channel : 31 1/2/0:7

Downstream Traffic Forwarding

DOCSIS 3.0 introduces the concept of assigning downstream service flows of cable modems, 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, integrated cable interfaces or modular cable interfaces) or downstream 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 cable modem’s assigned RCC encoding.

Service Flow Priority in Downstream Extended Header

The purpose of the feature is to be able to reflect the traffic priority of downstream packets into the DOCSIS extended header. The priority is derived from the service flow that the packet is mapped to. Priority refers to the service flow priority specified in the CM configuration file, or the Cisco CMTS service class configuration.

The service flow priority can be set using cable modem configuration file, or dynamic configuration.

By default, this feature is disabled on Cisco cBR-8 router, user can use cable service flow priority command to enable this feature.

How to Configure 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, RMs, and RCs.

Before You Begin

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

     Command or ActionPurpose
    Step 1enable


    Example: 
    Router> enable
     

    Enables privileged EXEC mode.

    • Enter your password if prompted.
     
    Step 2configure terminal


    Example: 
    Router# configure terminal
     

    Enters global configuration mode.

     
    Step 3cable 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.

     

    Configuring 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
    • DS channel primary capable indicator
    • DS channel membership to the MD-DS-SG
    • Cable modem 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 cable modems assigned to the RCC encodings are marked offline.

    Before You Begin

    At least one RC must be configured as a primary RC.

       Command or ActionPurpose
      Step 1enable


      Example: 
      Router> enable
       

      Enables privileged EXEC mode.

      • Enter your password if prompted.
       
      Step 2configure terminal


      Example: 
      Router# configure terminal
       

      Enters global configuration mode.

       
      Step 3cable 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 4rcp-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 5receive-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 from 55000000 to 1050000000.
      • 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 from 1 to 10.
       
      Step 6receive-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 from 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 from 55000000 to 1050000000.
      • 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 from 1 to 10.
      • Primary—(Optional) Indicates that it is a primary channel and an RCC can be derived from this channel. At least one receive-channel must be configured as primary.
       
      What to Do Next

      After defining an RCC template, you must assign the template to a cable interface. See Assigning an RCC Template to a Cable Interface.

      Assigning an RCC Template to a Cable Interface

      This section describes how to assign an RCC template to a cable interface.

         Command or ActionPurpose
        Step 1enable


        Example: 
        Router> enable
         

        Enables privileged EXEC mode.

        • Enter your password if prompted.
         
        Step 2configure terminal


        Example: 
        Router# configure terminal
         

        Enters global configuration mode.

         
        Step 3interface cable {slot/port | slot/subslot/port}

        Example: 
        Router(config)# interface cable7/0/0
         

        Specifies the cable interface line card on a Cisco CMTS router:

        • slot—Chassis slot number of the cable interface line card.

          Cisco uBR7246VXR router: The valid range is from 3 to 6.

          Cisco uBR7225VXR router: The valid range is from 1 to 2.

          Cisco uBR10012 router: The valid range is from 5 to 8.

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

        • port—Downstream port number.

          Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid port value is 0 or 1.

          Cisco uBR10012 router: The valid range is from 0 to 4 (depending on the cable interface).

         
        Step 4cable 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 from 1 to 255.
         

        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:

        Cisco uBR10012 Router

        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)

        Cisco uBR7200 Series Routers

        Router# show cable mac-domain cable 5/0 rcc
RCC-ID   RCP                 RCs MD-DS-SG CMs   WB/RCC-TMPL
1        00 00 00 00 00      3   0        3     WB (25)

        The table below 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 cable modems 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.

        Verifying the MD-DS-SG Configuration

        To verify the MD-DS-SG on a cable interface, use the show cable mac-domain downstream-service-group command as shown in the following example: 

        Router# show cable mac-domain cable 5/0 downstream-service-group
Cable    MD-DS-SG              RF
IF       Id        Resource    Chan     Primary Chan
C5/0     1         5/0         00-03    0

        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, modular, integrated or wideband interface are called provisioned attribute masks.

        The two types of attributes are as follows:

        • Specification-defined attributes—Contain default values based on the characteristics of the channel or bonding group.
        • Operator-defined attributes—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 cable modem 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 cable modem-initiated dynamic service request, the cable modem 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 cable modem configuration file.

        The table below 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, integrated cable, wideband cable, and modular cable interfaces.

        Prerequisites

        • To assign an interface to a wideband cable modem’s service flow, the interface must be a subset of the cable modem’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.
        • To assign a service flow to an integrated cable (IC) channel, the corresponding integrated cable interface must be configured and operational.

        Restrictions

        • The dynamic bonding group is not supported.
        • The service flow from a narrowband cable modem is always assigned to the primary interface of the cable modem. No attribute checking is performed in this case.

        This section describes the following:

        Configuring Provisioned Attributes for a Cable Interface

        The default provisioned attribute is zero for a cable interface.


        Note
        Provisioning the cable downstream attribute-mask command is not supported on the Cisco uBR7225VXR and Cisco uBR7246VXR routers.
           Command or ActionPurpose
          Step 1enable


          Example: 
          Router> enable
           

          Enables privileged EXEC mode.

          • Enter your password if prompted.
           
          Step 2configure terminal


          Example: 
          Router# configure terminal
           

          Enters global configuration mode.

           
          Step 3interface cable slot/subslot/port

          Example: 
          Router(config)# interface cable 7/0/0
           

          Specifies the cable interface line card on a Cisco CMTS router:

          • slot—Chassis slot number of the cable interface line card.

            Cisco uBR10012 router: The valid range is from 5 to 8.

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

          • port—Downstream port number.

            Cisco uBR10012 router: The valid range is from 0 to 4 (depending on the cable interface).

           
          Step 4cable 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

          This section describes how to configure the provisioned attributes for a modular cable interface on the Cisco uBR10012 universal broadband router. The default provisioned attribute is zero for a modular cable interface.

             Command or ActionPurpose
            Step 1enable


            Example: 
            Router> enable
             

            Enables privileged EXEC mode.

            • Enter your password if prompted.
             
            Step 2configure terminal


            Example: 
            Router# configure terminal
             

            Enters global configuration mode.

             
            Step 3interface 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 4cable attribute-mask mask


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

            Specifies the mask for the modular-cable interface.

             

            Configuring Provisioned Attributes for an Integrated Cable Interface

            The default provisioned attribute is zero for an integrated cable interface.

               Command or ActionPurpose
              Step 1enable


              Example: 
              Router> enable
               

              Enables privileged EXEC mode.

              • Enter your password if prompted.
               
              Step 2configure terminal


              Example: 
              Router# configure terminal
               

              Enters global configuration mode.

               
              Step 3 interface integrated-cable {slot/port | slot/subslot/port}:rf-channel


              Example: 
              Router(config)# interface integrated-cable 1/0/0:0
               

              Specifies the cable interface line card on a Cisco CMTS router:

              • slot—Chassis slot number of the cable interface line card.

                Cisco uBR7246VXR router: The valid range is from 3 to 6.

                Cisco uBR7225VXR router: The valid range is from 1 to 2.

                Cisco uBR10012 router: The valid range is from 5 to 8.

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

              • port—Downstream port number.

                Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid port value is 0 or 1.

                Cisco uBR10012 router: The valid range is from 0 to 4 (depending on the cable interface).

              • rf-channel—RF channel number with a range of 0 to 3.

               
              Step 4cable attribute-mask mask


              Example: 
              Router(config-if)# cable 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.

                 Command or ActionPurpose
                Step 1enable


                Example: 
                Router> enable
                 

                Enables privileged EXEC mode.

                • Enter your password if prompted.
                 
                Step 2configure terminal


                Example: 
                Router# configure terminal
                 

                Enters global configuration mode.

                 
                Step 3interface wideband-cable {slot/port | slot/subslot/port}:wideband-channel


                Example: 
                Router(config)# interface wideband-cable 1/0/1:4
                 

                Specifies the wideband cable interface and enters interface configuration mode:

                 
                Step 4cable 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 or show interface wideband-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  DS-ForwIf/
                            Prov Adm   Act              State Time    US-BG/CH
17    4     001c.ea37.9aac  3    3     3     P     US   act   13h21m  CH 3 
18    N/A   001c.ea37.9aac  4    4     4     P     DS   act   13h21m  Wi3/0:0 
21    6     001c.ea37.9b5a  3    3     3     P     US   act   13h21m  CH 4 
22    N/A   001c.ea37.9b5a  4    4     4     P     DS   act   13h21m  Wi3/0:0 
23    7     0016.925e.654c  3    3     3     P     US   act   13h21m  CH 3 
24    N/A   0016.925e.654c  4    4     4     P     DS   act   13h21m  In3/0:0 

Router# show interface wideband-cable 5/1:0 service-flow
Sfid  Sid   Mac Address     QoS Param Index Type  Dir Curr   Active  DS-ForwIf/
                            Prov  Adm  Act            State  Time    US-BG/CH
3     8193  ffff.ffff.ffff   3     3    3   S(s)  DS  act    2h06m   Wi5/1:0

                The table below 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 cable modems 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 cable modem.

                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 cable modem and CMTS).

                Dir

                Indicates if this service flow is DS or 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.

                DS-ForwIf/US-BG/CH

                BG/DS

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

                How to Enable Service Flow Priority in Downstream Extender Header

                The following tasks describe how to enable service flow priority in downstream extender header:

                Enabling Service Flow Priority in Downstream Extender Header

                This section describes how to enable service flow priority in downstream extender header on the Cisco cBR-8 routers:

                   Command or ActionPurpose
                  Step 1enable


                  Example: 
                  Router> enable
                   

                  Enables privileged EXEC mode.

                  • Enter your password if prompted.
                   
                  Step 2configure terminal


                  Example: 
                  Router# configure terminal
                   

                  Enters global configuration mode.

                   
                  Step 3cable service flow priority


                  Example: 
                  Router(config)# cable service flow priority
                   

                  Enables the service flow priority in downstream extender header.

                   

                  Verifying the Enablement of the Service Flow Priority in Downstream Extended Header

                  To verify the enablement of the service flow priority in downstream extended header, use the show running-config | in service flow or show cable modem [ip-address | mac-address] verbose command as shown in the following example: 

                  Router# show running-config | in service flow
cable service flow priority

Router# show cable modem 100.1.2.110 verbose

MAC Address                        : 0025.2e2d.74f8
IP Address                         : 100.1.2.110
IPv6 Address                       : 2001:420:3800:909:7964:98F3:7760:ED2
Dual IP                            : Y
Prim Sid                           : 1
Host Interface                     : C3/0/0/U0
MD-DS-SG / MD-US-SG                : N/A / N/A
MD-CM-SG                           : 0x900000
Primary Downstream                 : In3/0/0:32 (RfId : 12320, SC-QAM)
Wideband Capable                   : Y
DS Tuner Capability                : 8
RCP Index                          : 6
RCP ID                             : 00 00 00 00 00
Downstream Channel DCID RF Channel : 191   3/0/0:32 (SC-QAM)
UDC Enabled                        : N
US Frequency Range Capability      : Standard (5-42 MHz)
Extended Upstream Transmit Power   : 0dB
Multi-Transmit Channel Mode        : N
Upstream Channel                   : US0
Ranging Status                     : sta
Upstream SNR (dB)                  : 39.8
Upstream Data SNR (dB)             : 36.12
Received Power (dBmV)              : -1.00
Timing Offset             (97.6 ns): 1799
Initial Timing Offset              : 1799
Rng Timing Adj Moving Avg(0.381 ns): 0
Rng Timing Adj Lt Moving Avg       : 0
Rng Timing Adj Minimum             : 0
Rng Timing Adj Maximum             : 0
Pre-EQ Good                        : 0
Pre-EQ Scaled                      : 0
Pre-EQ Impulse                     : 0
Pre-EQ Direct Loads                : 0
Good Codewords rx                  : 8468
Corrected Codewords rx             : 0
Uncorrectable Codewords rx         : 0
Phy Operating Mode                 : atdma
sysDescr                           :
Downstream Power                   : 0.00 dBmV (SNR = ----- dB)
MAC Version                        : DOC3.0
QoS Provisioned Mode               : DOC1.1
Enable DOCSIS2.0 Mode              : Y
Service Flow Priority              : N
Modem Status                       : {Modem= online, Security=disabled}
Capabilities                       : {Frag=Y, Concat=Y, PHS=Y}
Security Capabilities              : {Priv=, EAE=N, Key_len=}
L2VPN Capabilities                 : {L2VPN=N, eSAFE=N}
L2VPN type                         : {CLI=N, DOCSIS=N}
Sid/Said Limit                     : {Max US Sids=16, Max DS Saids=15}
Optional Filtering Support         : {802.1P=N, 802.1Q=N, DUT=N}
Transmit Equalizer Support         : {Taps/Symbol= 1, Num of Taps= 24}
CM Capability Reject              : {15,22,23,24,25,26,27,28,29,35,36,38}
Flaps                              : 3(Oct 8  16:22:23)
Errors                             : 0 CRCs, 0 HCSes
Stn Mtn Failures                   : 0 aborts, 2 exhausted
Total US Flows                     : 1(1 active)
Total DS Flows                     : 1(1 active)
Total US Data                      : 294 packets, 25903 bytes
Total US Throughput                : 143 bits/sec, 0 packets/sec
Total DS Data                      : 91 packets, 10374 bytes
Total DS Throughput                : 0 bits/sec, 0 packets/sec
LB group ID assigned               : 1
LB group ID in config file         : N/A
LB policy ID                       : 0
LB policy ID in config file        : 0
LB priority                        : 0
Tag                                : d30
Required DS Attribute Mask         : 0x0
Forbidden DS Attribute Mask        : 0x0
Required US Attribute Mask         : 0x0
Forbidden US Attribute Mask        : 0x0
Service Type ID                    :
Service Type ID in config file     :
Active Classifiers                 : 0 (Max = NO LIMIT)
CM Upstream Filter Group           : 0
CM Downstream Filter Group         : 0
CPE Upstream Filter Group          : 0
CPE Downstream Filter Group        : 0
DSA/DSX messages                   : permit all
Voice Enabled                      : NO
DS Change Times                    : 0
Boolean Services                   : 0
CM Energy Management Capable       : N
CM Enable Energy Management        : N
CM Enter Energy Management         : NO
Battery Mode                       : N
Battery Mode Status                :
Number of Multicast DSIDs Support  : 16
MDF Capability Mode                : 2
IGMP/MLD Version                   : MLDv2
FCType10 Forwarding Support        : Y
Features Bitmask                   : 0x0
Total Time Online                  : 6h00m   (6h00m    since last counter reset)
CM Initialization Reason           : POWER_ON

                  Enabling Verbose Reporting for Receive Channel Profiles

                  A receive channel profile is an encoding that represents the receive channels and receive modules of a cable modem. A cable modem 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.

                     Command or ActionPurpose
                    Step 1enable


                    Example: 
                    Router> enable
                     

                    Enables privileged EXEC mode.

                    • Enter your password if prompted.
                     
                    Step 2configure terminal


                    Example: 
                    Router# configure terminal
                     

                    Enters global configuration mode.

                     
                    Step 3interface cable {slot/port | slot/subslot/port}

                    Example: 
                    Router(config)# interface cable7/0/0
                     

                    Specifies the cable interface line card on a Cisco CMTS router:

                    • slot—Chassis slot number of the cable interface line card.

                      Cisco uBR7246VXR router: The valid range is from 3 to 6.

                      Cisco uBR7225VXR router: The valid range is from 1 to 2.

                      Cisco uBR10012 router: The valid range is from 5 to 8.

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

                    • port—Downstream port number.

                      Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid port value is 0 or 1.

                      Cisco uBR10012 router: The valid range is from 0 to 4 (depending on the cable interface).

                     
                    Step 4cable rcp-control verbose


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

                    Enables RCP reporting with verbose description.

                     

                    Configuration Example for an RCC Template

                    The following sample shows an RCC template configuration: 

                    ...
!
cable rcc-template 1
  rcp-id 00 10 00 00 03
  receive-module 1 first-center-frequency 555000000 connected-receive-module 1
  receive-channel 1 center-frequency 555000000 connected-receive-module 1 primary
  receive-channel 2 center-frequency 561000000 connected-receive-module 1
  receive-channel 3 center-frequency 567000000 connected-receive-module 1 
!
...
!
interface Cable5/1
 downstream Integrated-Cable 5/1 rf-channel 0 upstream 0-3
 cable rcc-template 1
 cable rcp-control verbose
...

                    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 and RFCs

                    Standard

                    Title

                    CM-SP-MULPIv3.0-I08-080522

                    MAC and Upper Layer Protocols Interface Specifications

                    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

                    Feature Information for DOCSIS 3.0 Downstream Bonding for Bronze Certification

                    Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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

                    The table below lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train 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:

                    The following commands were introduced or modified in this release:

                    • 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

                    DOCSIS 3.0 Downstream Bonding for Bronze Certification

                    12.2(33)SCD

                    In Cisco IOS Release 12.2(33)SCD, this feature was introduced on the Cisco uBR7225VXR and Cisco uBR7246VXR routers.

                    The following commands were introduced or modified:

                    • interface cable
                    • show cable mac-domain rcc
                    • show cable mac-domain downstream-service-group