Downloads |
Table Of Contents
Prerequisites for Upstream Channel Bonding
Restrictions for Upstream Channel Bonding
Information About Upstream Channel Bonding
Multiple Transmit Channel Mode
Dynamic Range Window and Transmit Power Levels for Upstream Channel Bonding
Fiber Node Configuration for Upstream Channel Bonding
New TLVs for Upstream Channel Bonding
Upstream Weighted Fair Queuing
Class-Based Weighted Fair Queuing
Activity-Based Weighted Fair Queuing
Custom Weight for Service Flow Priorities
Upstream Scheduler and Service Flows
Cisco uBR10-MC5X20H Line Card Rate Limiting
How to Configure Upstream Channel Bonding
Enabling MTC Mode on a Cisco CMTS Router
Default MTC Mode Configuration on a Cisco CMTS Router
Adding Upstream Channels to a Bonding Group
Adding Upstream Channel Ports to a Fiber Node
Configuring the Class-Based Weighted Fair Queuing
Configuring the Activity-Based Weighted Fair Queuing
Configuring Custom Weights for Service Flow Priorities
Configuring the Service ID Cluster
Configuring the Channel Timeout for a Cable Modem
Configuring Cable Upstream Resiliency
Configuring Rate Limiting on the Cisco uBR10-MC5X20H Line Card
Enabling Upstream Related Events for CM Status Reports
Modifying the Bonding Group Attributes
Modifying the Ranging Poll Interval on Upstream Channels
Configuring the Reduced Channel Set Assignment
Configuring DOCSIS Extended Transmit Power Feature
Configuration Example for Upstream Channel Bonding
Enabling MTC Mode for a Single CM Using the CM Configuration File: Example
Verifying the Upstream Channel Bonding Configuration
Verifying Weighted Fair Queuing for Upstream Service Flows
Verifying Rate Limiting for Upstream Bonded Service Flows
Verifying Extended Power Transmission
Feature Information for Upstream Channel Bonding
Upstream Channel Bonding
First Published: November 16, 2009Last Updated: Jan 30, 2012The Upstream Channel Bonding (USCB) feature helps cable operators offer higher upstream (US) bandwidth per cable modem (CM) user by combining multiple radio frequency (RF) channels to form a larger bonding group at the MAC layer.
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 Upstream Channel Bonding" 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 Upstream Channel Bonding
•
•
•
•
•
•
Prerequisites for Upstream Channel Bonding
•
•
•
Table 1 shows the hardware compatibility prerequisites for the Upstream Channel Bonding feature.
Table 1 Cable Hardware Compatibility Matrix for Upstream Channel Bonding
Cisco uBR10012 router
Cisco IOS Release 12.2(33)SCC and later releases
•
•
Cisco IOS Release 12.2(33)SCC and later releases
•
•
Cisco IOS Release 12.2(33)SCE and later releases
•
Cisco uBR7246VXR router
Cisco IOS Release 12.2(33)SCD and later releases
•
Cisco IOS Release 12.2(33)SCD and later releases
•
Cisco uBR7225VXR router
Cisco IOS Release 12.2(33)SCD and later releases
•
Cisco IOS Release 12.2(33)SCD and later releases
•
1 Cisco uBR-MC3GX60V cable interface line card is compatible only with PRE4.
Restrictions for Upstream Channel Bonding
The following are the general restrictions for the Upstream Channel Bonding feature:
•
•
•
Cisco CMTS allows oversubscription of the available bandwidth for individual upstream channels. However, oversubscription of bandwidth is not supported for USCB groups.
An individual upstream may get oversubscribed due to static CIR service flows created for voice traffic. This may cause the DOCSIS 3.0 CMs with USCB to come online on single channel US bonding group (also known as default bonding group).
This problem is mainly encountered in the voice deployments using static service flows. It is, therefore, recommended to choose from the following voice deployments such that the CIR is allocated (or released) when a voice call is attempted (or dropped):
1.
2.
3.
These deployments avoid the individual upstream oversubscription and CMs come online on expected bonding groups.
Information About Upstream Channel Bonding
DOCSIS 3.0-based upstream channel bonding is a method for increasing upstream bandwidth up to a maximum of 120 Mbps raw throughput per CM user in a cable communications system that includes a Cisco CMTS router and multiple CMs. The upstream channel bonding method enables a CM to transmit data to a Cisco CMTS router on multiple upstream channels simultaneously.
Channel bonding is a method by which smaller bandwidth upstream channels are bonded together to create a larger upstream bonding group in the MAC domain. A MAC domain is a logical subcomponent of a Cisco CMTS router and is responsible for implementing all DOCSIS functions on a set of downstream and upstream channels.
The Upstream Channel Bonding feature supports upstream traffic in Multiple Transmit Channel (MTC) mode for data and video services as these services require more bandwidth than voice-based services. Voice-based services either use the traditional single upstream channel or a single upstream channel bonding group configuration. Any traffic contract that exceeds 30 Mbps requires upstream channel bonding as the physical capacity of a single RF channel in DOCSIS cannot exceed 30 Mbps.
The Upstream Channel Bonding feature is supported on the Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCC and later. Upstream data from the subscriber comes through the upstream ports (US0-US19) that are automatically configured on the cable interface line card. The cable interface line card processes the data and sends it across the backplane to the WAN card and out to the Internet.
Table 2 lists the downstream and upstream frequencies supported on the various cable interface line cards.
Table 2 Downstream and Upstream Frequencies
Cisco uBR10-MC5X20H
55-858 MHz
The upstream frequency range changes according the region and Annex A or Annex B configuration.
•
•
•
Cisco uBR10-MC20X20V
55-999 MHz
Cisco uBR-MC88V
69-999 MHz
Cisco uBR-MC3GX60V
55-999 MHz1
The upstream frequency range for the Cisco uBR-MC3GX60V line card is from 5 to 85 MHz irrespective of the region and Annexure configuration.
1 This frequency range is subjected to the frequency restriction of the attached EQAM device.
Multiple Transmit Channel Mode
Multiple Transmit Channel mode is a CM capability that enables CMs to send upstream traffic on multiple upstream channels. You can enable the MTC mode on a cable interface line card in two ways:
•
•
Multiple Receive Channel Mode
MRC mode is a CM capability that enables CMs to receive downstream traffic on multiple downstream channels. The MRC mode is enabled by default on an upstream bonding capable cable interface line card. You can enable or disable the MRC mode in the MAC domain during or after the CM registration using the cable mrc-mode command.
Dynamic Range Window and Transmit Power Levels for Upstream Channel Bonding
The dynamic range window functionality is based on the CableLabs DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification and DOCSIS 3.0 Specification. This requires a DOCSIS 3.0 CM to have upstream transmit channel power level within a 12 dB range for all channels in its transmit channel set (TCS).
DOCSIS 1.x or 2.0 CMs operating with a single upstream channel, in non-MTC mode, have a higher maximum transmit power level than DOCSIS 3.0 CMs operating in the MTC mode with two or more upstream channels. That is, the maximum transmit power level per channel is reduced in the MTC mode.
When the upstream attenuation exceeds the maximum transmit power level, a DOCSIS 3.0 CM attempting to register in the MTC mode may fail to come online, or register in partial mode. The CM fails to register when the transmit power level of all upstream channels in its TCS exceeds the maximum transmit power level. If the CM has some upstream channels that are within the maximum transmit power level, the CM may come online in partial mode. However, the upstream channels that exceed the maximum transmit power level are marked as down and cannot be used for upstream traffic.
To verify the transmit power levels on a CM, use the show cable modem command with the verbose keyword. This command displays the following transmit power values for each assigned upstream channel:
•
•
•
To support upstream channel bonding, the minimum transmit power must be less than or equal to the reported transmit power, and the reported transmit power must be less than or equal to the peak transmit power. The peak transmit power and minimum transmit power levels are derived from the CM TCS assignment and each individual upstream channel configuration.
If the minimum transmit power is higher than the reported transmit power, or the reported transmit power is higher than the peak transmit power, the CM may not come online or may register in partial mode.
You can troubleshoot this transmit power problem in the following two ways:
•
•
Extended Transmit Power
During the early deployment of DOCSIS 3.0 CMs, additional power is required from the CMs in order to compensate for the attenuation in the upstream path. CMs should transmit at extended power level than that defined in DOCSIS. This scenario is generally observed when USCB is enabled at the Cisco CMTS and the DOCSIS 3.0 CMs are operating in MTC mode.
Additional upstream power provides the operator with a power margin that helps overcome the upstream signal loss, reduces the cable plant operational cost, and enables rapid deployment of DOCSIS 3.0 CMs.
The Cisco CMTS supports the following features with which the CMs can transmit data at an extended power:
•
•
Cisco Extended Transmit Power Feature
The Cisco Extended Transmit Power feature, introduced in Cisco IOS Release 12.2(33)SCE3, supports DOCSIS 3.0 CMs operating in MTC mode to transmit at a higher power level than the power level specified in the DOCSIS 3.0 Specification. This feature is supported only with Cisco DPC3000 CMs.
The Cisco Extended Transmit Power feature enables cable operators to have better control on the cable modems that register in 4-channel or 2-channel MTC mode or in non-MTC mode to transmit at a higher power level than the DOCSIS-defined maximum power level. The cable operator can configure extended transmit power using the cable tx-power-headroom command in global configuration mode.
DOCSIS Extended Transmit Power Feature
The DOCSIS Extended Transmit Power feature, introduced in Cisco IOS Release 12.2(33)SCF2, supports extended upstream transmit power capability as defined in the DOCSIS3.0 Specification. This feature allows the CMs to transmit at a high extended power level to counter the attenuation in the US channel.
Table 3 lists the new TLVs supported by the DOCSIS Extended Transmit Power feature.
The Cisco CMTS sends TLV16 to inform the CM if the DOCSIS Extended Transmit Power feature is enabled. The CM in turn, sends TLV5.40 to the Cisco CMTS to communicate its extended power capability. After the negotiations are complete, the CM can transmit at an extended power.
DOCSIS Extended Transmit Power feature is enabled by default. Use the cable upstream ext-power command to enable or disable this feature. For more information on how to enable or disable DOCSIS Extended Power feature, see "Configuring DOCSIS Extended Transmit Power Feature" section.
Note
Reduced Transmit Channel Set
The Reduced Transmit Channel Set feature, introduced in Cisco IOS Release 12.2(33)SCE3, enables the Cisco CMTS router to reduce upstream channel set assignment based on the total power budget of the CM. For example, a reduction from four to two upstream channels gains 3 dB headroom. Further reduction from two channels to a single channel gains another 3 dB headroom, and the CM starts operating in non-MTC mode.
In order to take advantage of the reduced upstream channel set, the corresponding static bonding groups must be configured. For example, a MAC domain is configured with a bonding group having four channels. A CM with the reduced channel set of two is unable to match to the 4-channel bonding group, and can only be matched to a bonding group with two channels or less.
The Reduced Transmit Channel Set feature is helpful when a DOCSIS 3.0 CM is required to increase its total transmit power by 3 dB. For example, a DOCSIS 1.0 or 2.0 CM supports a maximum transmit power of 58 dBmV for Quadrature Phase Shift Keying (QPSK) modulation, while a DOCSIS 3.0 CM supports a maximum transmit power of 61 dBmV. In this case, the DOCSIS 3.0 CM operating in 4-channel MTC mode has a reduction in the maximum transmit power per upstream channel. This feature enables the Cisco CMTS router to support reduced input power level by 6 dB to prevent upstream path attenuation.
T4 Multiplier
T4 multiplier is the T4 timeout multiplier value for CMs that are in the MTC mode. The default value is derived from the number of channels in the modem transmit channel set. You can change the default T4 multiplier value using the cable upstream ranging-poll command in cable interface configuration mode. For example, DOCSIS 2.0 defines T4 timeout for the modem at 30 seconds. If the T4 multiplier value is equal to one, the CM will T4 time out in every 30 seconds. If you change the T4 multiplier to four, then the new T4 timeout value will be 120 seconds (4 x 30 = 120).
In the MTC mode, you can increase the T4 timeout value in order to reduce the router overhead associated with processing of ranging request (RNG-REQ) slots and ranging response messages. If an RNG-RSP message does not contain a T4 timeout multiplier value, then the CM uses the default T4 timeout value.
Fiber Node Configuration for Upstream Channel Bonding
The fiber node configuration on a Cisco CMTS router is used to define MAC domain downstream service groups (MD-DS-SGs) and MAC domain upstream service groups (MD-US-SGs) as defined in DOCSIS 3.0. Only the DOCSIS 3.0 certified modems use this information.
In hybrid fiber coaxial (HFC) networks, all CMs connected to the same coaxial segment of a fiber node reach the same set of downstream and upstream channels on one or more Cisco CMTS routers located at the headend.
A CM is physically connected to only one fiber node. The fiber node must include at least one primary-capable channel for the CM connected to the fiber node to be operational. The fiber node can include one or more primary-capable channels either from the cable interface line card, or from the primary-capable Shared Port Adaptor (SPA) downstream channels, or both.
Note
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_tech_note09186a00807f32fd.shtml
New TLVs for Upstream Channel Bonding
Table 4 lists the new CableLabs defined type, length, values (TLVs) for the Upstream Channel Bonding feature.
Table 4 New TLVs for Upstream Channel Bonding
CM vendor ID
43.8
3
Per vendor definition
Cable modem attribute mask
43.9
n
Cable modem attribute mask subtype encodings
A Cisco CMTS can have multiple upstream channel bonding groups (USBG) configured. Each of these bonding groups can include upstream channels with different upstream frequencies. Some bonding groups can include channels with frequencies within the extended frequency range (see Table 2). An HFC network consists of several types of CMs, each supporting standard or extended upstream frequencies.
When you register a CM, the Cisco CMTS does not assign bonding groups based on the upstream frequency range supported by that CM. The assignment of the bonding groups is done to balance the CM count on each of the bonding groups. This may lead to assignment of a bonding group, in the extended frequency range, to a CM that lacks the extended frequency support. As a result, the CM will not be able to register. This scenario is generally observed in the Cisco uBR-MC3GX60V line card deployment (containing a mix of CMs), which supports frequency as high as 85MHz (see Table 2).
If the Cisco CMTS assigns a USBG with a channel within the extended frequency range to a CM limited to the standard frequency range, that CM may not be able to register on that upstream bonding group. Use the TLV 43.9.3 (CM US Required Attribute Mask) or TLV 43.9.4 (CM US Forbidden Attribute Mask) as a workaround. These TLVs enable the Cisco CMTS to assign CM to a USBG, which is in the upstream frequency range supported by that CM.
The default attributes (in hexadecimal) on a CM Attribute Mask (TLV 43.9) are "80 00 00 00", which means by default the mask is all zeroes with the bonding bit enabled. The first four bytes are pre-defined while the last four bytes are user defined. In order to enable CMTS to assign bonding groups based on the frequency range supported by CMs, complete these steps:
1.
2.
Apply the mask you have configured above, to the CMs that support standard or extended frequency ranges. However, the ONLY CMs that need to employ the attribute mask are the ones with the standard frequency range, since they will not be able to register with the USBG configured with extended upstream frequency range. No attribute mask on the extended frequency supporting CMs means that these modems will be assigned any USBG.
The Cisco CMTS uses this mask, received in the CM configuration file during registration, to decide which USBG should be assigned to the CM.
Upstream Weighted Fair Queuing
The upstream weighted fair queuing (WFQ) is a quality of service (QoS) feature that enables the Cisco CMTS router to allocate optimum bandwidth to upstream service flows based on the WFQ parameter configurations. To enable upstream WFQ, you must configure either the class-based or activity-based WFQ on a cable interface.
The following WFQ parameter configurations are supported in Cisco IOS Release 12.2(33)SCD2 and later:
•
•
•
Class-Based Weighted Fair Queuing
In the class-based weighted fair queuing configuration, allocation of available bandwidth is dependent on the service flows that are active in a service class. A service class is a group of queuing attributes configured on the Cisco CMTS router. The class must have at least one active service flow. The class receives its portion of the available bandwidth based on the weight of the class. By default, each class (0 to 7) has a weight of "class + 1." For example, the class 0 has a weight of 1, and class 1 has a weight of 2.
Activity-Based Weighted Fair Queuing
In the activity-based weighted fair queuing configuration, allocation of available bandwidth is based on the service class and the total number of service flows that are active in a map for the service class. A service class with higher number of service flows receives the larger percentage of bandwidth.
Custom Weight for Service Flow Priorities
The weighted fair queuing functionality helps the Cisco CMTS router share the available bandwidth based on the weight of the service flow priorities specified for outstanding requests from an upstream service flow. Priority refers to the service flow priority specified in the CM configuration file, or the Cisco CMTS service class configuration. By default, the weight of a priority is equal to "priority+1." For example, priority 0 has a weight of 1, and priority 1 has a weight of 2. A higher priority provides more weight to the outstanding request. The custom weight can be specified for a total of eight priorities (0 to 7) in a service class.
The priority parameter refers to the priority of traffic in a service flow ranging from 0 (the lowest) to 7 (the highest). In the upstream traffic, all of the pending high priority service flows are scheduled for transmission before low priority service flows. You can configure the weight for priorities based on how much weight is appropriate per priority.
Table 5 lists the default weight for each service flow priority.
Table 5 Default Weight of Service Flow Priorities
0
1
1
2
2
3
3
4
4
5
5
6
6
7
7
8
Upstream Scheduler and Service Flows
A DOCSIS-qualified Cisco CMTS router can provide varied upstream scheduling modes for different packet streams or applications using upstream service flows. A service flow represents either an upstream or a downstream flow of data. A unique service flow ID (SFID) identifies each service flow. Each service flow can have its own quality of service (QoS) parameters, such as maximum throughput, minimum guaranteed throughput, and priority. In the case of upstream service flows, you can also specify a scheduling mode.
Scheduling is a process that enables the Cisco CMTS router to receive bandwidth requests and grant timeslots to CMs for the upstream traffic. The Cisco CMTS router periodically creates a grant map for each enabled upstream channel. The map grants individual timeslots to enable CMs to place packets on the upstream channels.
DOCSIS 3.0 describes a method by which a CM creates an upstream service flow. The following scheduling types enable the Cisco CMTS router to allocate bandwidth for upstream service flows:
•
•
The unsolicited grant service is primarily used for voice. In the case of UGS, the CM does not have to explicitly request grants from the Cisco CMTS router whereas in the solicited grant service the CM has to explicitly request grants from the Cisco CMTS router. The solicited grant service is primarily used for best effort (BE) services.
Unlike DOCSIS 2.0, DOCSIS 3.0 allows multiple outstanding requests per service flow. For more information about the upstream scheduler, see the Upstream Scheduler Mode for the Cisco CMTS Routers feature guide at the following URL:
Cisco uBR10-MC5X20H Line Card Rate Limiting
The rate limiting functionality enables you control the aggregated rate and CPU consumption of upstream traffic for DOCSIS 3.0 bonded service flows on the Cisco uBR10-MC5X20H line card. In Cisco IOS Release 12.2(33)SCC, this functionality is supported only on the Cisco uBR10-MC5X20H line card. The rate limiting functionality is configured by default on the Cisco uBR10-MC5X20H line card. However, the default configuration can be modified using the cable upstream rate-limit-ccf command.
The rate limiting functionality uses the following two rate limiting methods:
•
•
SID Tracking
The service ID (SID) tracking functionality enables you to track events related to upstream bandwidth requests and processing of grants. The SID tracker module can track events for a maximum of two service flows per MAC domain. The SID tracker module tracks up to 40,000 events per service flow on a cable interface line card.
You can enable SID tracking for the following types of events:
•
•
•
•
•
You can enable SID tracking using the track keyword along with the debug cable interface sid command. To verify SID tracking, use the show interface cable upstream debug command in privileged EXEC mode.
Service ID Clusters
A Cisco CMTS router can assign one or more service ID clusters to the upstream bonded service flows (upstream service flows assigned to an upstream bonding group) at the time of service flow creation. A SID cluster contains one SID per upstream in a bonding group. A CM uses one of the SIDs defined in the SID cluster for the upstream interface when the CM sends a bandwidth request. The CM chooses a SID or a SID cluster based on the SID cluster switching criteria.
For example, assume that a CM has ranged on upstream channels from 1 to 4. The Cisco CMTS router creates a bonded service flow and assigns a single SID cluster to each upstream channel. That is SID1 for UP1, SID2 for UP2, SID3 for UP3, and SID4 for UP4. Now, the CM can send a bandwidth request using any of the four upstream channels. That is, the CM can request bandwidth on any of the upstream interfaces in the SID cluster using the SID defined for the particular upstream. The Cisco CMTS router grants bandwidth to the CM using any combination of upstream channels.
How to Configure Upstream Channel Bonding
Note
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_tech_note09186a00807f32fd.shtm
The following tasks describe how to configure Upstream Channel Bonding on the Cisco uBR10012 router:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Enabling MTC Mode on a Cisco CMTS Router
To enable the MTC mode on a Cisco CMTS router:
•
Default MTC Mode Configuration on a Cisco CMTS Router
By default, the MTC mode required attribute is configured on a cable interface line card. With this default configuration, the Cisco CMTS router enables the MTC mode on a per CM basis depending on the configuration file of each CM. When the CM configuration file has the bonded-bit (bit-0) enabled in TLV 43.9.3 (cable modem upstream required attribute mask), the Cisco CMTS router enables the CM to come online in the MTC mode. If the CM configuration file does not have the bonded-bit on, the CM comes online in non-MTC mode.
For more information on how to add the required attribute in the CM configuration file, see "Enabling MTC Mode for a Single CM Using the CM Configuration File: Example" section.
Enable MTC Mode for All CMs
To enable MTC mode for all CMs in a MAC domain, use the cable mtc-mode command in cable interface configuration mode.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Creating a Bonding Group
An upstream bonding group is created by combining multiple upstream channels together on a cable interface line card.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Adding Upstream Channels to a Bonding Group
After creating an upstream bonding group, you must add upstream channels to the bonding group.
Restrictions
DOCSIS 3.0-certified CMs support only four upstream channels on an upstream bonding group. These CMs do not accept additional upstream channels that are added to a bonding group.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Adding Upstream Channel Ports to a Fiber Node
You must add upstream channel ports to a fiber node in order to complete the basic upstream channel bonding configuration on a cable interface line card. The fiber node must contain all upstream and downstream channels reached by the CMs.
Restrictions
•
•
Note
http://www.cisco.com/en/US/tech/tk86/tk804/technologies_tech_note09186a00807f32fd.shtml
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the Class-Based Weighted Fair Queuing
In the case of a class-based configuration, allocation of available bandwidth is dependent on the service flows that are active in a service class.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the Activity-Based Weighted Fair Queuing
In the activity-based configuration, allocation of available bandwidth is based on the service class and the total number of service flows that are active in a map for the service class.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Custom Weights for Service Flow Priorities
The WFQ functionality helps the Cisco CMTS router share the available bandwidth based on the weight of the service flow priorities specified for outstanding requests from an upstream service flow.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the Service ID Cluster
This section explains how to configure and assign a SID cluster to an upstream bonded service flow.
Note
If the cable sid-cluster-group command is not used, the router accepts the default SID cluster configuration. By default, only one SID cluster is configured. Similarly, if the cable sid-cluster-switching command is not used, the router accepts the default SID cluster switchover criterion. That is only one request can be made using the SID cluster.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring the Channel Timeout for a Cable Modem
The channel timeout configuration allows you to specify the maximum time that a CM can spend performing initial ranging on the upstream channels described in the Registration Response (REG-RSP) and REG-RSP-MP messages. The default channel timeout value (60 seconds) is automatically configured.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Cable Upstream Resiliency
The cable upstream resiliency module ensures that a CM remains operational if one or more non-primary upstream service flows of the CM enter temporary or persistent error states. This module enables a Cisco CMTS router to handle various events and maintain the transmit channel set of each CM.
In the event of the primary upstream service flow failure, the upstream resiliency module forces the CM to go offline.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Rate Limiting on the Cisco uBR10-MC5X20H Line Card
The rate limiting functionality is configured by default on the Cisco uBR10-MC5X20H line card. However, the default configuration can be modified using the cable upstream rate-limit-ccf command.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Enabling Upstream Related Events for CM Status Reports
You can enable upstream related CM status events only on a cable interface line card. You can enable the following upstream related CM status events per interface using the cable cm-status enable command:
•
•
•
For details on how to enable upstream and downstream related CM status events, see the Wideband Modem Resiliency feature guide at the following URL:
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/ubr_wm_resiliency.html
Modifying the Bonding Group Attributes
Bonding group attributes are automatically configured for each upstream bonding group. You can modify them using the attributes command in upstream bonding configuration mode.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Modifying the Ranging Poll Interval on Upstream Channels
You can change the default ranging poll interval (20 seconds) on upstream channels using the cable upstream ranging-poll command in cable interface configuration mode. You can also specify the T4 timeout multiplier value using this command.
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring the Reduced Channel Set Assignment
You need to configure the transmit power offset budget to enable the Cisco CMTS router to reduce upstream channel set assignment based on the total power budget of the CM.
Note
Prerequisites
•
•
Restrictions
•
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring DOCSIS Extended Transmit Power Feature
The DOCSIS Extended Transmit Power feature is enabled by default on the Cisco CMTS. However, the default configuration can be modified using the cable upstream ext-power command.
SUMMARY STEPS
1.
2.
3.
4.
5.
DETAILED STEPS
Troubleshooting Tips
The following debug commands help you troubleshoot an improper upstream channel bonding configuration and its related features:
•
•
•
•
Configuration Example for Upstream Channel Bonding
The following example shows how to configure the basic upstream channel bonding on the Cisco uBR-MC3GX60V line card interface 8/1/14 on the Cisco uBR10012 router:
interface Cable 8/1/14downstream Modular-Cable 8/1/0 rf-channel 0downstream Modular-Cable 8/1/1 rf-channel 8downstream Modular-Cable 8/1/2 rf-channel 16cable mtc-modeno cable packet-cachecable bundle 1cable upstream max-ports 4cable upstream bonding-group 81upstream 0upstream 1upstream 2upstream 3attributes A0000000cable upstream 0 connector 0cable upstream 0 frequency 15000000cable upstream 0 channel-width 1600000 1600000cable upstream 0 docsis-mode tdmacable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21cable upstream 0 attribute-mask 20000000no cable upstream 0 shutdowncable upstream 1 connector 0cable upstream 1 frequency 25000000cable upstream 1 channel-width 1600000 1600000cable upstream 1 docsis-mode tdmacable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21cable upstream 1 attribute-mask 20000000no cable upstream 1 shutdowncable upstream 2 connector 0cable upstream 2 frequency 30000000cable upstream 2 channel-width 1600000 1600000cable upstream 2 docsis-mode tdmacable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21cable upstream 2 attribute-mask 20000000no cable upstream 2 shutdowncable upstream 3 connector 0cable upstream 3 frequency 35000000cable upstream 3 channel-width 1600000 1600000cable upstream 3 docsis-mode tdmacable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21cable upstream 3 attribute-mask 20000000no cable upstream 3 shutdownendcable fiber-node 1downstream Modular-Cable 8/1/0 rf-channel 0-7upstream Cable 8/1 connector 0!cable fiber-node 13downstream Modular-Cable 8/1/1 rf-channel 8-15upstream Cable 8/1 connector 0!cable fiber-node 23downstream Modular-Cable 8/1/2 rf-channel 16-23upstream Cable 8/1 connector 0
Note
Note
Enabling MTC Mode for a Single CM Using the CM Configuration File: Example
The following example shows how to enable the MTC required attribute using the CM configuration file:
03 (Net Access Control) = 1Unknown Type 005 = 01 01 0118 (Maximum Number of CPE) = 424 (Upstream Service Flow Encodings)S01 (Service Flow Reference) = 1S06 (QoS Parameter Set Type) = 7S10 (Min Reserved Traffic Rate)= 50000025 (Downstream Service Flow Encodings)S01 (Service Flow Reference) = 2S06 (QoS Parameter Set Type) = 7S10 (Min Reserved Traffic Rate) = 100000029 (Privacy Enable) = 043 (Vendor Specific Options)S08 (Vendor ID) = ff ff ffS009 (Unknown sub-type) = 03 04 80 00 00 00Verifying the Upstream Channel Bonding Configuration
Use the following show commands to verify the upstream channel bonding configuration:
•
•
•
•
•
To verify the runtime statistics of the upstream service group on a cable interface line card, use the show cable mac-domain upstream-service-group command as shown in the following example:
Router# show cable mac-domain cable 8/1/14 upstream-service-groupCable MD 8/1/14US-SG-ID : 1 US-Chan : U0,1,2,3Primary-DS: 8/1/0:0 US-SG-ID: 1MDD US-List : U0,1,2,3MDD Ambiguity : U0,1,2,3Primary-DS: 8/1/1:8 US-SG-ID: 1MDD US-List : U0,1,2,3MDD Ambiguity : U0,1,2,3Primary-DS: 8/1/2:16 US-SG-ID: 1MDD US-List : U0,1,2,3MDD Ambiguity : U0,1,2,3To verify the configuration of a fiber node, use the show cable fiber-node command as shown in the following example:
Router# show cable fiber-nodeFiber-Node 1Channels : downstream Modular-Cable 8/1/0: 0-7Channel IDs : 169, 170, 171, 172, 173, 174, 175, 176upstream Cable 8/1: 0FN Config Status: Configured (status flags = 0x01)MDD Status: Valid---------------------------------------------------------------Fiber-Node 2Channels : downstream Modular-Cable 1/1/0: 0-1Channel IDs : 193, 194upstream Cable 5/0: 0FN Config Status: Configured (status flags = 0x01)MDD Status: Valid---------------------------------------------------------------Fiber-Node 13Channels : downstream Modular-Cable 8/1/1: 8-15Channel IDs : 177, 178, 179, 180, 181, 182, 183, 184upstream Cable 8/1: 0FN Config Status: Configured (status flags = 0x01)MDD Status: Valid---------------------------------------------------------------Fiber-Node 23Channels : downstream Modular-Cable 8/1/2: 16-23Channel IDs : 185, 186, 187, 188, 189, 190, 191, 192upstream Cable 8/1: 0FN Config Status: Configured (status flags = 0x01)MDD Status: ValidTo verify the bonding groups configured on a cable interface line card, use the show interface cable upstream command as shown in the following example:
Router# show interface cable 8/1/14 upstream bonding-groupCable8/1/14: Upstream Bonding Group 8112 packets input, 4614 octets inputSegments: 12 valid, 0 discarded, 0 lostReserved Bandwidth Max : 0 bits/secReserved Bandwidth : 0 bits/secAvailable Bandwidth : 10240000 bits/secTotal Service Flows On This Bonding Group: 1Cable8/1/14: Upstream Bonding Group 655360 packets input, 0 octets inputSegments: 0 valid, 0 discarded, 0 lostReserved Bandwidth Max : 0 bits/secReserved Bandwidth : 0 bits/secAvailable Bandwidth : 2560000 bits/secTotal Service Flows On This Bonding Group: 0Cable8/1/14: Upstream Bonding Group 655370 packets input, 0 octets inputSegments: 0 valid, 0 discarded, 0 lostReserved Bandwidth Max : 0 bits/secReserved Bandwidth : 0 bits/secAvailable Bandwidth : 2560000 bits/secTotal Service Flows On This Bonding Group: 0Cable8/1/14: Upstream Bonding Group 655380 packets input, 0 octets inputSegments: 0 valid, 0 discarded, 0 lostReserved Bandwidth Max : 0 bits/secReserved Bandwidth : 0 bits/secAvailable Bandwidth : 2560000 bits/secTotal Service Flows On This Bonding Group: 0Cable8/1/14: Upstream Bonding Group 655390 packets input, 0 octets inputSegments: 0 valid, 0 discarded, 0 lostReserved Bandwidth Max : 0 bits/secReserved Bandwidth : 0 bits/secAvailable Bandwidth : 2560000 bits/secTotal Service Flows On This Bonding Group: 0To verify upstream bonding information on a cable interface line card, use the show interface cable service-flow command as shown in the following example:
Router# show interface cable 8/1/14 service-flow 19 verboseSfid : 19Mac Address : 001e.6bfb.3332Type : PrimaryDirection : UpstreamCurrent State : ActiveCurrent QoS Indexes [Prov, Adm, Act] : [4, 4, 4]Active Time : 1h25mRequired Attributes : 0x00000000Forbidden Attributes : 0x00000000Aggregate Attributes : 0x00000000Sid : 6Traffic Priority : 0Maximum Sustained rate : 50000000 bits/secMaximum Burst : 3044 bytesMinimum Reserved Rate : 0 bits/secMinimum Packet Size : 0 bytesAdmitted QoS Timeout : 200 secondsActive QoS Timeout : 0 secondsPackets : 0Bytes : 0Rate Limit Delayed Grants : 0Rate Limit Dropped Grants : 0Current Throughput : 0 bits/sec, 0 packets/secApplication Priority : 0US Bonded : YESUpstream Bonding Group : UBG-65535Transmit Channel Set : 0xFSid Cluster : SC-0, Sid [ 6 6 6 6 ]Sid Cluster : SC-1, Sid [ 9 9 9 9 ]Segments Valid : 0Segments Discarded : 0Segments Lost : 0SID Cluster Switching InformationTotal Bytes Requested : 0Total Time : 20Outstanding Bytes : 25600Max Requests : 8Classifiers: NONETo verify the transmit power levels on a CM, use the show cable modem command as shown in the following example:
Router# show cable modem 0014.f831.d596 verboseMAC Address : 001e.6bfa.f02eIP Address : 30.10.0.6IPv6 Address : ---Dual IP : NPrim Sid : 5Host Interface : C5/1/0/UBMD-DS-SG / MD-US-SG : 1 / 1MD-CM-SG : 0xF0101Primary Wideband Channel ID : 48Primary Downstream : Mo3/0/0:0 (RfId : 120)Wideband Capable : YRCP Index : 3RCP ID : 00 10 00 00 04Multi-Transmit Channel Mode : YUpstream Channel : US1 US2 US3 US4Ranging Status : sta sta sta staUpstream Power (dBmV) : 0.00 0.00 0.00 0.00Upstream SNR (dB) : 36.12 36.12 36.12 33.1Received Power (dBmV) : 0.00 1.00 0.00 -0.75Reported Transmit Power (dBmV) : 45.00 45.00 45.00 54.75Peak Transmit Power (dBmV) : 51.00 51.00 56.00 56.00Minimum Transmit Power (dBmV) : 24.00 24.00 21.00 18.00Timing Offset (97.6 ns): 2312 2281 2282 2282Initial Timing Offset : 2314 2058 2058 2058Rng Timing Adj Moving Avg(0.381 ns): 7 4 0 -94Rng Timing Adj Lt Moving Avg : 63 30 11 -144Rng Timing Adj Minimum : -512 -256 -256 -512Rng Timing Adj Maximum : 256 57088 57344 57344Pre-EQ Good : 0 0 0 0Pre-EQ Scaled : 0 0 0 0Pre-EQ Impulse : 0 0 0 0Pre-EQ Direct Loads : 0 0 0 0Good Codewords rx : 5012 4996 4992 4990Corrected Codewords rx : 0 0 0 0Uncorrectable Codewords rx : 0 0 0 0Phy Operating Mode : atdma* atdma* tdma* tdma*sysDescr :Downstream Power : 0.00 dBmV (SNR = ----- dB)MAC Version : DOC3.0QoS Provisioned Mode : DOC1.1Enable DOCSIS2.0 Mode : YModem Status : {Modem= w-online, Security=disabled}Capabilities : {Frag=N, Concat=N, PHS=Y}Security Capabilities : {Priv=, EAE=Y, Key_len=}L2VPN Capabilities : {L2VPN=N, eSAFE=N}Sid/Said Limit : {Max US Sids=8, Max DS Saids=24}Optional Filtering Support : {802.1P=N, 802.1Q=N, DUT=N}Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24}Number of CPE IPs : 0(Max CPE IPs = 16)CFG Max-CPE : 4Flaps : 0()Errors : 0 CRCs, 0 HCSesStn Mtn Failures : 0 aborts, 0 exhaustedTotal US Flows : 2(2 active)Total DS Flows : 1(1 active)Total US Data : 6 packets, 1557 bytesTotal US Throughput : 0 bits/sec, 0 packets/secTotal DS Data : 0 packets, 0 bytesTotal DS Throughput : 0 bits/sec, 0 packets/secLB group ID assigned (index) : N/A (N/A)LB group ID in config file (index) : N/A (N/A)LB policy ID : 0LB policy ID in config file : 0LB priority : 0Tag :Required DS Attribute Mask : 0x0Forbidden DS Attribute Mask : 0x0Required US Attribute Mask : 0x0Forbidden US Attribute Mask : 0x0Service Type ID :Service Type ID in config file :Active Classifiers : 0 (Max = NO LIMIT)CM Upstream Filter Group : 0CM Downstream Filter Group : 0CPE Upstream Filter Group : 0CPE Downstream Filter Group : 0DSA/DSX messages : permit allVoice Enabled : NODS Change Times : 0Boolean Services : 2Number of Multicast DSIDs Support : 24MDF Capability Mode : 2IGMP/MLD Version : IGMPv3FCType10 Forwarding Support : YFeatures Bitmask : 0x0Total Time Online : 1d16hCM Initialization Reason : NO_PRIM_SF_USCHANCFG Max IPv6 CPE Prefix : 16 (-1 used)Verifying Weighted Fair Queuing for Upstream Service Flows
To verify WFQ parameters configured for upstream service flows on a cable interface line card, use the show interface cable mac-scheduler command as shown in the following example:
Router# show interface cable 5/0/2 mac-scheduler 0DOCSIS 1.1 MAC scheduler for Cable5/0/2/U0: rate 10240000wfq:Class, weights: 1 2 3 4 5 6 7 8Queue[Rng Polls] 0/128, 0 drops, flows 0 max 0Queue[CIR Grants] 0/256, 0 drops, flows 0 max 0Queue[BE(7) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(6) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(5) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(4) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(3) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(2) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(1) Grants] 0/32, 0 drops, flows 0 max 0Queue[BE(0) Grants] 0/32, 0 drops, flows 0 max 0Queue[LLQ Grants] 0/64, 0 drops, flows 0 max 0BG pending grant list entries: 0BG delay list entries: 0Req Slots 265389868, Req/Data Slots 4Init Mtn Slots 3798558, Stn Mtn Slots 0Short Grant Slots 0, Long Grant Slots 0Adv Phy Short Grant Slots 0, Adv Phy Long Grant Slots 0Adv Phy UGS Grant Slots 0Awacs Slots 0Fragmentation count 0Fragmentation test disabledAvg upstream channel utilization : 0%Avg percent contention slots : 97%Avg percent initial ranging slots : 3%Avg percent minislots lost on late MAPs : 0%Sched Table Rsv-state: Grants 0, Reqpolls 0Sched Table Adm-State: Grants 0, Reqpolls 0, Util 0%UGS : 0 SIDs, Reservation-level in bps 0UGS-AD : 0 SIDs, Reservation-level in bps 0RTPS : 0 SIDs, Reservation-level in bps 0NRTPS : 0 SIDs, Reservation-level in bps 0BE : 0 SIDs, Reservation-level in bps 0MAP TSS: lch_state 11, init_retries 0late_initial_maps 0, late_ucd_maps 0mac-phy tss errors 0r4k ticks in 1ms 800000Total scheduling events 0No search was needed 0Previous entry free 0Next entry free 0Could not schedule 0Recovery failed 0Curr time 251 entry 251Verifying Rate Limiting for Upstream Bonded Service Flows
To verify the rate limiting criteria configured on the Cisco uBR10-MC5X20H line card for upstream bonded service flows, use the show cable rate-limit-ccf command as shown in the following example:
Router# show cable rate-limit-ccfrate_limiting config: aggr_throughput: 215000000 aggr_burst: 240000cpu_threshold: 50 cpu_burst: 105X20H rate limit: cpu-throttle 0 ccf-bw-drop 0 others 05X20H rate limit ccf info count: 0
Note
Verifying Extended Power Transmission
To verify that a CM is transmitting at a higher power level, use the show cable modem command as shown in the following example:
Router# show cable modem 0022.2d56.d42d verbose...Multi-Transmit Channel Mode : YUpstream Channel : US1 US2 US3 US4Ranging Status : sta sta sta staUpstream SNR (dB) : 36.12 36.12 36.12 36.12Received Power (dBmV) : 1.00 !2.00 !2.00 !2.50Reported Transmit Power (dBmV): 54.00 54.00 54.00 54.00Peak Transmit Power (dBmV) : 51.00 51.00 51.00 51.00Minimum Transmit Power (dBmV): 21.00 21.00 21.00 21.00Timing Offset 97.6 ns) : 2311 2311 2310 2311!Compare the Reported Transmit Power and Peak Transmit Power values to verify that the cable modem is transmitting at a higher power level..To list all the CMs that are transmitting at higher power level, use the show cable modem extended-power command as shown in the following example:
Router# show cable modem extended-powerMAC Address IP Address I/F MAC Prim Report ECNState Sid Power001e.6bfb.3382 5.50.0.3 C7/0/0/UB w-online 3 57.00 Y0022.cea5.0214 5.50.1.102 C7/0/0/UB w-online 5 54.00 Y001e.6bfb.1378 5.50.6.83 C7/0/0/UB w-online 6 54.00 YAdditional References
The following sections provide references related to the Upstream Channel Bonding feature.
Related Documents
Commands on the Cisco CMTS routers
Cisco IOS CMTS Cable Command Reference
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.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
Cisco uBR10-MC5X20S/U/H Cable Interface Line Card
Cisco uBR10-MC5X20S/U/H Cable Interface Line Card Hardware Installation Guide
Dynamic Bandwidth Sharing
Cisco IOS CMTS Cable Software Configuration Guide, Release 12.2SC
Upstream Scheduler Mode
Cisco IOS CMTS Cable Software Configuration Guide, Release 12.2SC
Standards
MIBs
RFCs
No new or modified RFCs are supported, and support for existing RFCs has not been modified.
—
Technical Assistance
Feature Information for Upstream Channel Bonding
Table 6 lists the release history for this feature.
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
Table 6 Feature Information for Upstream Channel Bonding
Upstream Channel Bonding
12.2(33)SCC
The Upstream Channel Bonding feature helps cable operators offer higher upstream bandwidth per CM user by combining multiple physical RF channels to form a larger bonding group at the MAC layer.
The following sections provide information about this feature:
•
•
•
The following commands were introduced or modified:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Cisco uBR10-MC5X20H Line Card Specific Rate Limiting
12.2(33)SCC
The following commands were introduced:
•
•
SID Tracking
12.2(33)SCC
The following commands were introduced or modified:
•
•
Upstream Channel Bonding
12.2(33)SCD
Added support for Cisco uBR7246VXR and Cisco uBR7225VXR routers.
Upstream Weighted Fair Queuing
12.2(33)SCD2
Added support for class-based and activity-based weighted fair queuing configuration for upstream service flows.
The following commands were introduced or modified:
•
•
Upstream Channel Bonding
12.2(33)SCE
The following commands were modified to support the Cisco uBR-MC3GX60V cable interface line card:
•
•
•
Extended Transmit Power and Reduced Transmit Channel Set
12.2(33)SCE3
The Extended Transmit Power feature enables cable operators to have better control on the CMs that register in 4-channel or 2-channel MTC mode or in non-MTC mode to transmit at a higher power level than the DOCSIS-defined maximum power level.
The following commands were introduced or modified:
•
•
DOCSIS Extended Transmit Power
12.2(33)SCF2
This feature introduces the extended transmit power capability on the Cisco CMTS as per the DOCSIS specification. The DOCSIS 3.0 CMs can now transmit at a higher power level to overcome the signal loss because of the attenuation in the US path.
The following commands were introduced or modified:
•
•
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
©2009-2012 Cisco Systems, Inc. All rights reserved.
