Table Of Contents
CM Steering on the Cisco CMTS Routers
Finding Feature Information
Contents
Prerequisites for CM Steering
Restrictions for CM Steering
Information About CM Steering
Channel Redirection
Channel Restriction
How to Configure CM Steering on Cisco CMTS Routers
Configuring a Channel Redirection
Restrictions
Verifying a Channel Redirection
Clearing a Channel Redirection
Configuring a Channel Restriction
Prerequisites
Restrictions
Verifying a Channel Restriction
Clearing Attribute Masks
Debugging Channel Redirection
Troubleshooting Tips
Configuration Examples for CM Steering
Configuring Channel Redirection: Example
Configuring Channel Restriction: Example
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for CM Steering
CM Steering on the Cisco CMTS Routers
Revised: November 16, 2009
First Published: December 18, 2008
The cable modem (CM) steering feature helps to redirect or steer CMs to multiple Cable Modem Termination Systems (CMTS) using downstream frequency overrides. A configurable string is used to bond the CM to the proper CMTS. Once the bonding is done, the CMTS can move the CM within itself for load balancing.
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 for CM Steering" 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 CM Steering
•
Restrictions for CM Steering
•
Information About CM Steering
•
How to Configure CM Steering on Cisco CMTS Routers
•
Configuration Examples for CM Steering
•
Additional References
•
Feature Information for CM Steering
Prerequisites for CM Steering
DOCSIS 3.0-defined Type-Length-Values (TLVs) are required to aid channel selection. All TLVs encoded as general extension information in CM configuration files are backward compatible with DOCSIS 1.1 and DOCSIS 2.0 CMs.
Table 1 shows the Cisco Cable Modem Termination System (CMTS) hardware compatibility prerequisites for this feature.
Table 1
CMTS Platform
|
Processor Engine
|
Cable Interface Cards
|
Cisco uBR10012 Universal Broadband Router
|
Cisco IOS Release 12.2(33)SCB and later
• PRE2
• PRE4
|
Cisco IOS Release 12.2(33)SCB and later
• Cisco uBR10-MC5X20S/U/H
• Cisco UBR-MC20X20V
|
Cisco uBR7200 Series Universal Broadband Routers
|
Cisco IOS Release 12.2(33)SCB and later
• Cisco uBR7246VXR Universal Broadband Router only
• NPE-G1
• NPE-G2
|
Cisco IOS Release 12.2(33)SCB and later
• Cisco uBR-MC28U/X
• Cisco uBR-MC16U/X
|
Cisco uBR7225VXR Universal Broadband Router
|
Cisco IOS Release 12.2(33)SCB and later
• NPE-G1
• NPE-G2
|
Cisco IOS Release 12.2(33)SCB and later
• Cisco uBR-E-28U
• Cisco uBR-E-16U
• Cisco uBR-MC28U/X
• Cisco uBR-MC16U/X
|
CM Steering Hardware Compatibility Matrix
Restrictions for CM Steering
The CM steering feature has the following general restrictions:
•
To restrict the CM on the exact downstream on the target CMTS, the redirection must be configured on the target CMTS.
•
You must manually execute the clear cable modem service-type command to clear the CM service type identifier stored at the CMTS during registration.
•
You must manually execute the clear cable modem attribute-masks command to clear the CM attribute masks stored at the CMTS during registration. These attribute masks are used to restrict usage of upstream channels during ranging time.
•
CM steering supports only upstream masks.
•
Channel steering does not take place when the CM fails in initial ranging.
•
The CM will take more time to come online when channel steering is deployed. The time taken is proportional to the number of modems, and the downstreams and upstreams that the CM can reach.
•
A modem cannot be load balanced to any upstream channel with attributes that conflict with attribute masks of the modem.
•
The keep alive detection feature may trigger an line card (LC) switchover. For more details on the Keep Alive feature, refer to the N+1 Redundancy for the Cisco Cable Modem Termination System chapter of the Cisco Cable Modem Termination System Feature Guide.
•
Each interface should have an active modem or use no keepalive on this interface.
Information About CM Steering
CM steering allows you to redirect or steer the CMs to one or more CMTS using downstream frequency overrides. Once a CM registers on a downstream on the proper CMTS, the CMTS can move the CM to any location for load balancing.
The DOCSIS 3.0-compliant Service Type Identifier used as the configurable string in the CM configuration file is backward-compatible with DOCSIS 1.1 and DOCSIS 2.0 CMs.
The CMTS can also impose restrictions on the number of channels a CM can use. DOCSIS 3.0 defines several TLVs to aid the channel selection.
The following TLVs are used in CM steering:
•
TLV 43.9 (Cable Modem Attribute Masks) limits the set of channels the CMTS can assign to the CM by allowing or forbidding certain binary attributes. The CM Attribute Masks have four sub-TLVs and CM steering makes use of two sub-TLVs, which are listed below:
–
TLV 43.9.3—Cable Modem Upstream Required Attribute Mask (C.1.1.18.1.8.3 of CM-SP-MULPIv3.0-I07-080215). It is a 32-bit mask representing the set of binary upstream channel attributes required for the CM.
–
TLV 43.9.4—Cable Modem Upstream Forbidden Attribute Mask (C.1.1.18.1.8.4 of CM-SP-MULPIv3.0-I07-080215). It is a 32-bit mask representing the set of binary upstream channel attributes forbidden for the CM.
•
TLV 43.11 is used for a redirection action based on the service type identifier field. The CM sends the TLV 43.11 in the REG-REQ MAC message. The DOCSIS 1.1 and DOCSIS 2.0 modems will also send this file ID when doing the registration.
•
TLV43.1, defined as Policy ID in DOCSIS 2.0 and DOCSIS 3.0, is parsed and stored in the CM during registration. Before moving the CM during load balancing (LB), the CMTS checks whether the CM has a preconfigured policy with the same Policy ID. If the policy does exist, the CMTS disables LB for this CM and moves to the next CM. If the policy does not exist on the CMTS, or the Policy ID is missing from the CM configuration file, LB prohibition is not performed.
The following TLVs are supported in CM Steering:
•
TLV 43.11 (Service type identifier) from section C.1.1.18.1.10 in CM-SP-MULPIv3.0-I07-080215.
•
CM attribute masks (TLV 43.9) from C.1.1.18.1.8.3 and C.1.1.18.1.8.4 of CM-SP-MULPIv3.0-I07-080215.
•
TLV portion (43.1, Policy ID) of REQ-REQ
CM steering contains three small featurettes: Channel Redirection, Channel Restriction, and Load Balancing. The Load Balancing feature is covered in the Configuring Load Balancing and Dynamic Channel Change (DCC) on the Cisco CMTS document.
Channel Redirection
The service type identifier-based channel redirection allows you to redirect or steer the CMs to one or more CMTS using downstream frequency overrides. A configurable string in the CM configuration file is used to bond the CM to the correct CMTS. A global CLI ties the string to the downstream frequency, which is configured on the CMTS.
Once a CM registers on a downstream of a CMTS, the CMTS can move the CM to any location within the CMTS for load balancing.
A DOCSIS 3.0-compliant TLV (TLV 43.11) service identifier is used as the configurable string in the CM configuration file. It is backward-compatible with DOCSIS 1.1 and DOCSIS 2.0 CMs. This TLV is used as the tag of the CM to decide whether to redirect or not. The method used to redirect is downstream frequency override in the ranging phase.
Channel Restriction
The CMTS can impose restrictions on the channels a CM uses based on the CMs configuration file or its capabilities. For example, Advanced Time Division Multiple Access (ATDMA) capable CMs should not use Time Division Multiple Access (TDMA) upstream channels.
DOCSIS 3.0 provides guidelines on how a CMTS can choose a pair of channels for a CM at both registration time and during autonomous load balancing. DOCSIS 3.0 defines several TLVs to aid channel selection, including the service type identifier, load balancing group ID, and CM attribute masks and service flow attribute masks.
Except for the service flow attribute masks, the TLVs are encoded as general extension information in the CM configuration file, which are backward compatible with DOCSIS 1.1 and DOCSIS 2.0 CMs.
Channel restriction looks only for upstream CM attribute masks, and is therefore compatible with DOCSIS 1.1, DOCSIS 2.0 and DOCSIS 3.0 CMs in non-Multiple Transmit Channel (MTC) mode.
Note
In Cisco IOS Release 12.2(33)SCC and later releases, it is recommended to assign a CM to different Restricted Load Balancing Groups (RLBGs) to restrict the usage of channels, instead of using attribute masks.
How to Configure CM Steering on Cisco CMTS Routers
This section describes the following required and optional procedures:
•
Configuring a Channel Redirection (required)
•
Verifying a Channel Redirection (optional)
•
Clearing a Channel Redirection (optional)
•
Configuring a Channel Restriction (required)
•
Verifying a Channel Restriction (optional)
Configuring a Channel Redirection
To configure a channel redirection that allows you to redirect or steer the CMs to one or more CMTS using the downstream frequency override in the ranging phase, use the cable service type ds-frequency command.
Restrictions
You can redirect CMs matching the service type identifier to a downstream frequency. However, one service type identifier cannot be redirected to multiple downstream frequencies.
During registration, the CM service type identifier is stored in the CMTS to redirect target downstream frequency during ranging time. If you want to clear the stored service type identifier, you must manually execute the clear cable modem service-type command.
To restrict the CM on the exact downstream on the target CMTS, the redirection must be configured on the target CMTS. If the CMs are redirected to the source CMTS, the dynamic load balance may not work properly and the CM may drop offline during load balancing. For the CMs to be redirected it must reach the target frequency.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cable service type [service-type-id] ds-frequency [frequency]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
cable service type [service-type-id]
ds-frequency [frequency]
Example:
Router(config)# cable service type commercial
ds-frequency 519000000
|
Redirects matching service types to downstream frequency.
service-type-id—Specifies the service type identifier to be redirected. Maximum length is 16.
frequency—Specifies the downstream frequency to which the CMs are redirected.
|
Verifying a Channel Redirection
To verify configuration of channel redirection, use the show cable modem verbose command as shown in the following example:
Router# show cable modem verbose
MAC Address : 0014.bfbe.81e3
Upstream Power : 0.00 dBmV (SNR = 36.12 dB)
Downstream Power : 0.00 dBmV (SNR = ----- dB)
Initial Timing Offset : 1874
Curr US Timing Adjust : 0
Prev US Timing Adjust : 0
Received Power : 0.00 dBmV
QoS Provisioned Mode : DOC1.1
Enable DOCSIS2.0 Mode : Y
Phy Operating Mode : tdma
Modem Status : {Modem=online(pt), Security=assign(tek)}
Capabilities : {Frag=Y, Concat=Y, PHS=Y}
Security Capabilities : {Priv=BPI+, EAE=N}
L2VPN Capabilities : {L2VPN=N, eSAFE=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}
Number of CPE IPs : 0(Max CPE IPs = 16)
Stn Mtn Failures : 0 aborts, 0 exhausted
Total US Flows : 1(1 active)
Total DS Flows : 1(1 active)
Total US Data : 1 packets, 401 bytes
Total US Throughput : 0 bits/sec, 0 packets/sec
Total DS Data : 0 packets, 0 bytes
Total DS Throughput : 0 bits/sec, 0 packets/sec
Required DS Attribute Mask : 0x0
Forbidden DS Attribute Mask : 0x0
Required US Attribute Mask : 0x0
Forbidden US Attribute Mask : 0x0
Service Type ID : commercial
Active Classifiers : 0 (Max = NO LIMIT)
DSA/DSX messages : permit all
Number of Multicast DSIDs Support : 15
FCType10 Forwarding Support : N
Total Time Online : 00:59
To view the modems having the service type identifier, use the show cable modem service-type-id command as shown in the following example:
Router# show cable modem service-type-id
MAC Address IP Address I/F MAC Prim Service-type-id P I
0018.6812.29ae 41.42.2.212 C6/1/4/U2 offline 3838 commercial N N
0018.6811.f9f8 41.42.0.140 C6/1/4/U2 offline 3225 commercial N N
0018.6811.fba6 41.42.5.169 C6/1/4/U2 offline 3439 commercial N N
0018.6812.225a 41.42.3.210 C6/1/4/U2 offline 3355 commercial N N
0018.6811.fa8c 41.42.1.133 C6/1/4/U2 offline 3091 commercial N N
0018.6812.37e8 41.42.0.136 C6/1/4/U2 offline 7439 commercial N N
0018.6811.fbca 41.42.2.255 C6/1/4/U2 offline 6263 commercial N N
0018.6811.fb44 41.42.2.17 C6/1/4/U2 offline 2996 commercial N N
0018.6812.2f20 41.42.0.100 C6/1/4/U2 offline 3544 commercial N N
Clearing a Channel Redirection
To clear the cable modem attributes, use the clear cable modem command as shown in the following examples:
Router# clear cable modem all
Router# clear cable modem oui string
Router# clear cable modem cable slot/subslot/port offline
To clear the cable modem service type identifiers, use the clear cable modem service-type command as shown in the following examples:
Router# clear cable modem all service-type-id
Router# clear cable modem oui string service-type-id
Router# clear cable modem slot/subslot/port offline service-type-id
Configuring a Channel Restriction
To impose restrictions on the channels a CM can use based on its configuration file or capabilities, use the cable upstream attribute-mask command.
Prerequisites
Advanced Time Division Multiple Access (ATDMA) capable cable modems should be restricted from using Time Division Multiple Access (TDMA) upstream channels.
Restrictions
•
The CM attribute masks (TLV 43.9) are a function of the CMTS support and are compatible only with legacy DOCSIS 1.1 and DOCSIS 2.0 CMs.
•
When the CMTS cannot find an appropriate US channel in the same legacy LB group, the CM steering checking is skipped and CMs come online. The US channel must meet the requirement of CM US attribute masks if a load balancing group (LBG) is not configured.
•
During registration, the CM attribute masks are stored at the CMTS. These are then used to restrict usage of upstream channels during ranging time. You must manually execute the clear cable modem attribute-masks command to clear the stored attribute masks.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface cable slot/subslot/port
4.
cable upstream [upstream-interface] attribute-mask [attribute-mask]
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode.
|
Step 3
|
interface cable slot/subslot/port
Example:
Router# configure terminal
|
Enables the cable interface.
|
Step 4
|
cable upstream upstream-interface
attribute-mask attribute-mask
Example:
Router(config-if)# cable upstream 0
attribute-mask ffff]
|
Configures the attribute mask on a particular upstream interface.
• upstream-interface—Specifies the upstream port.
• attribute-mask—Specifies the attribute mask bitmap in hexadecimal format. Example: 0-FFFFFFFF
Note From Cisco IOS Release 12.2(33)SCC, the bit 0 in attribute-mask is bypassed when CM steering checks it.
|
Verifying a Channel Restriction
To verify the service type identifier and CM attribute masks configured for a CM, use the show cable modem verbose command as shown in the following example:
Router# show cable modem 0019.474d.e291 verbose
MAC Address : 0019.474d.e291
Host Interface : C5/0/4/U0
Primary Downstream : Mo1/0/0:0 (RfId : 0)
Upstream Power : 0.00 dBmV (SNR = 36.12 dB)
Downstream Power : 0.00 dBmV (SNR = ----- dB)
Initial Timing Offset : 1573
Curr US Timing Adjust : 0
Prev US Timing Adjust : 0
Received Power : -0.50 dBmV
QoS Provisioned Mode : DOC1.1
Enable DOCSIS2.0 Mode : Y
Phy Operating Mode : tdma
Modem Status : {Modem=online, Security=disabled}
Capabilities : {Frag=Y, Concat=Y, PHS=Y}
Security Capabilities : {Priv=, EAE=N}
L2VPN Capabilities : {L2VPN=N, eSAFE=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}
Number of CPE IPs : 0(Max CPE IPs = 16)
Stn Mtn Failures : 0 aborts, 0 exhausted
Total US Flows : 1(1 active)
Total DS Flows : 1(1 active)
Total US Data : 7 packets, 619 bytes
Total US Throughput : 0 bits/sec, 0 packets/sec
Total DS Data : 2 packets, 148 bytes
Total DS Throughput : 4 bits/sec, 0 packets/sec
Required DS Attribute Mask : 0x0
Forbidden DS Attribute Mask : 0x0
Required US Attribute Mask : 0x1111
Forbidden US Attribute Mask : 0x0
Service Type ID : commercial
Active Classifiers : 0 (Max = NO LIMIT)
DSA/DSX messages : permit all
Number of Multicast DSIDs Support : 0
FCType10 Forwarding Support : N
Total Time Online : 00:19
Clearing Attribute Masks
If the CM fails to come online after configuring attribute masks in the CM configuration file, you can use the following procedure to verify the contents of the CM configuration file and clear its contents if the attribute masks are configured differently.
SUMMARY STEPS
1.
enable
2.
show cable modem verbose
3.
clear cable modem attribute-masks
4.
show running-config
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
show cable modem verbose
Example:
Router# cable modem verbose
|
Verifies whether the CM attribute masks have been configured in the CM configuration file.
Note If the CM configuration file shows any change, use the clear cable modem attribute-masks command.
|
Step 3
|
clear cable modem attribute-masks
Example:
Router# clear cable modem all attribute-masks
|
Clears the CM attribute masks stored in CMTS.
|
Step 4
|
show running-config
Example:
Router# show running-config
|
Displays the running configuration.
Use it to verify whether upstream masks of the CM are configured on the corresponding upstream channel.
|
Debugging Channel Redirection
Use the following steps to debug channel redirection:
SUMMARY STEPS
1.
enable
2.
show running config
3.
debug cable range
4.
debug cable registration
5.
debug cable mac-address [mac] verbose
6.
clear cable modem [mac] delete
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
enable
Example:
Router> enable
|
Enables privileged EXEC mode.
• Enter your password if prompted.
|
Step 2
|
show running config
Example:
Router# show running config
|
Displays the running configuration.
Note You can use this information to verify the CMTS configuration to make sure that the CMs can reach the configured downstream-frequency.
|
Step 3
|
debug cable range
Example:
Router# debug cable range
|
Displays ranging messages from CMs on the Hybrid Fiber-Coaxial (HFC) network.
|
Step 4
|
debug cable registration
Example:
Router# debug cable registration
|
Displays debug messages for the CM registration process.
|
Step 5
|
debug cable mac-address [mac] verbose
Example:
Router# debug cable mac-address 00E0.1E00.0000
ffff.ff00.0000 verbose
|
Displays debug information for a specific CM.
|
Step 6
|
clear cable modem [mac] delete
Example:
Router# clear cable modem 00E0.1E00.0000
ffff.ff00.0000 delete
|
Removes the specified modem from the CMTS.
Note This allows the CMTS to re-register the CM's page.
|
Troubleshooting Tips
This section provides tips and commands you can use to troubleshoot your CM Steering configuration.
•
Clearing Attribute Masks
•
Debugging Channel Redirection
•
Because empty rules are not allowed, if you remove the last rule of a policy, using no cable load-balance docsis-policy policy-id rule rule-id or no cable load-balance rule rule-id, the policy itself will be removed.
•
Use the show running | include docsis-policy command or the show running-config | include rule command to see the policy and rule configured in the system.
Configuration Examples for CM Steering
This section provides the following configuration examples:
•
Configuring Channel Redirection: Example
•
Configuring Channel Restriction: Example
Configuring Channel Redirection: Example
In the following example, CMs matching a particular service type identifier are redirected to a particular downstream frequency.
Router(config)# cable service type commercial ds-frequency 519000000
Configuring Channel Restriction: Example
The following example sets an upstream's attribute mask in hexadecimal format for channel restriction.
Router# configure terminal
Router(config)# interface Cable 5/0/4
Router(config-if)# cable upstream 0 attribute-mask ffff
To verify the channel restriction configuration, use the following command:
Router# show cable modem service-type-id
MAC Address IP Address I/F MAC Prim Service-type-id P I
0018.6812.29ae 41.42.2.212 C6/1/4/U2 offline 3838 commercial N N
0018.6811.f9f8 41.42.0.140 C6/1/4/U2 offline 3225 commercial N N
0018.6811.fba6 41.42.5.169 C6/1/4/U2 offline 3439 commercial N N
0018.6812.225a 41.42.3.210 C6/1/4/U2 offline 3355 commercial N N
0018.6811.fa8c 41.42.1.133 C6/1/4/U2 offline 3091 commercial N N
0018.6812.37e8 41.42.0.136 C6/1/4/U2 offline 7439 commercial N N
0018.6811.fbca 41.42.2.255 C6/1/4/U2 offline 6263 commercial N N
0018.6811.fb44 41.42.2.17 C6/1/4/U2 offline 2996 commercial N N
0018.6812.2f20 41.42.0.100 C6/1/4/U2 offline 3544 commercial N N
Additional References
The following sections provide references related to the CM Steering feature.
Related Documents
Standards
Standard
|
Title
|
CM-SP-MULPIv3.0-I07-080215
|
DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
|
CM-SP-MULPIv3.0-I08-080522
|
DOCSIS 3.0 MAC and Upper Layer Protocols Interface Specification
|
CM-SP-RFI2.0-I13-080215
|
DOCSIS 2.0 Radio Frequency Interface Specification
|
MIBs
MIB
|
MIBs Link
|
No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature.
|
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
RFCs
RFC
|
Title
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
|
|
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/support
|
Feature Information for CM Steering
Table 2 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 2 lists only the Cisco IOS software release that introduced support for a given feature in a given Cisco IOS software release. Unless noted otherwise, subsequent releases of that Cisco IOS software release also support that feature.
Table 2 Feature Information for CM Steering on the Cisco CMTS Routers
Feature Name
|
Releases
|
Feature Information
|
Channel Redirection
|
12.2(33)SCB
|
Channel redirection allows you to redirect or steer the CMs to one or more CMTS using downstream overrides.
The following sections provide information about this feature:
• Channel Redirection
• Configuring a Channel Redirection
• Verifying a Channel Redirection
The following commands were introduced or modified: cable service type, cable service type ds-frequency, clear cable modem attribute-masks, clear cable modem service-type, show cable modem service-type-id.
|
Channel Restriction
|
12.2(33)SCB
|
The CMTS can impose restrictions on the channels a CM can use based on the CM configuration file or its capabilities.
The following sections provide information about this feature:
• Channel Restriction
• Configuring a Channel Restriction
• Verifying a Channel Restriction
The following command is introduced: cable upstream attribute-mask.
|
Channel Restriction
|
12.2(33)SCB4
|
When the CMTS cannot find an appropriate US channel in the same legacy LB group, the CM steering checking is skipped and CMs come online.
The following sections provide information about this feature:
• Configuring a Channel Restriction
|
RLBG/GLBG Support and NB DBS Interact with DLB Support
|
12.2(33)SCC
|
The following sections have been updated with information about this feature:
• Channel Restriction
• Configuring a Channel Restriction
|
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.