-
Cisco IOS CMTS Cable Command Reference
-
Introduction
-
Cable Commands: a through cable-modem
-
Cable Commands: cable a through cable c
-
Cable Commands: cable d
-
Cable Commands: cable e through cable i
-
Cable Commands: cable l
-
Cable Commands: cable m to n
-
Cable Commands: cable p through cable r
-
Cable Commands: cable s
-
Cable Commands: cable t
-
Cable Commands: cable u through cable w
-
Cable Commands: ca through cr
-
Cable Commands: d through h
-
Cable Commands: i through p
-
Cable Commands: q through sg
-
Cable Commands: show a through show cable l
-
Cable Commands: show cable m to show cable u
-
Cable Commands: show ch through show cr
-
Cable Commands: show d through show i
-
Cable Commands: show m through show z
-
Cable Commands: snmp through w
-
Appendix A: Cable Debug Commands
-
Appendix B: Cisco CMTS Router ROM Monitor Commands
-
Feedback
Table Of Contents
cable metering data-per-session
cable metering source-interface
cable modem service-class-name
cable modulation-profile global-scheme
cable multicast auth enable default-action
cable multicast auth profile-name
cable multicast group-encryption
cable multicast group-qos default
Cable Commands: cable m to n
Revised: 8 August, 2013, OL-15510-16
New Commands
Modified Commands
cable map-advance
To configure the dynamic map advance algorithm, use the cable map-advance command in cable interface configuration mode. Use the no form of this command to disable this function.
cable map-advance [dynamic [safety] | static] [max-delay]
no cable map-advance
Syntax Description
Defaults
Dynamic map advance with a safety factor of 1000 microseconds and a max-delay of 1800 microseconds
Command Modes
Interface configuration (cable interface only)
Command History
Usage Guidelines
The max-delay option, which was introduced in Cisco IOS Release 12.1(10)EC, specifies the maximum possible round-trip delay between the cable plant and furthest CM in the cable network. A CM will not be allowed to exceed the maximum timing offset given by the max-delay value (in static mode) or given by the combination of the max-delay and safety values (in dynamic mode). If a CM reports a timing offset beyond the maximum value, the CMTS will reset its offset to the maximum value and put an exclamation point (!) next to its offset value in the show cable modem display.
In dynamic MAP operation, Cisco IOS 12.1(10)EC also implements a regular polling of the furthest CM, to determine if that CM is now offline. If the furthest CM has gone offline, the CMTS scans the currently online CMs to determine which CM is now the furthest offline and updates the dynamic MAP advance algorithm with the new value.
Examples
The following example shows how to configure the dynamic map advance to 1500 microseconds:
router(config-if)# cable map-advance dynamic 1500Related Commands
cable match address
To specify that IP multicast streams be encrypted, use the cable match address command in cable interface configuration mode. To specify that multicast streams should not be encrypted, use the no form of this command.
cable match address access-list
no cable match address
Syntax Description
Command Default
No default behavior or values
Command Modes
Interface configuration—cable interface only (config-if)
Command History
Usage Guidelines
The cable match address command binds an access-list to a cable interface, allowing multicast encryption to be performed on traffic through that interface. To configure the access list, use the ip access-list command.
Note
This command is not available for cable subinterfaces.
For additional information on configuring for multicast operations, see the chapters on IP Multicast in the Release 12.2 Cisco IOS IP Configuration Guide and in Volume 3 of the Cisco IOS IP Command Reference.
Note
Examples
The following example shows how to specify that the multicast stream defined by the access list named reno be encrypted on cable interface 3/0:
Router(config)# interface c3/0Router(config-if)# cable match address renoThe following example shows how to specify that the multicast stream defined by the access list number 102 be encrypted:
Router(config)# interface c3/0Router(config-if)# cable match address 102Related Commands
cable max-hosts
To specify the maximum number of hosts that can be attached to a subscriber's CM, use the cable max-hosts command in cable interface configuration mode. Use the no form of this command to reset the allowable number of hosts attached to a CM to the default value of 0 hosts.
cable max-hosts n
no cable max-hosts
Syntax Description
n
Specify the maximum number of hosts that can be attached to a CM on this interface. Valid range is from 0 to 255 hosts. Default value is 0.
Command Default
0
Command Modes
Interface configuration (cable interface only)
Command History
12.0(4)XI
This command was introduced.
12.0(6)SC, 12.1(2)EC1
Support was added on the Cisco IOS 12.0 SC and 12.1 EC release trains.
Usage Guidelines
The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
•
•
•
The more specific commands override the settings of the less specific commands. For example, if you use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note
Tip
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.Examples
The following example shows how to set the maximum hosts for CMs on this particular cable interface to 15:
Router(config)# interface c6/0Router(config-if)# cable max-hosts 15Related Commands
cable metering data-per-session
To view the number of cable metering data flows per session for a cable modem termination system, use the cable metering data-per-session command in the global configuration mode. To disable this feature, use the no form of this command.
cable metering data-per-session data-per-session timer timer value
no cable metering data-per-session data-per-session timer timer value
Syntax Description
Command Default
The cable metering data flow values will not be visible.
Command Modes
Global configuration mode
Command History
12.2(33)SCB1
This command was introduced.
12.3(23)BC7
This command was integrated into Cisco IOS Release 12.3(23)BC7.
Usage Guidelines
The cable metering data-per-session command allows users to view the number of cable metering data flows per session. The command limits or throttles the data collection between the cable line card and the route processor.
Examples
The following example displays the number of cable metering data flows per session:
Router#configure terminalRouter(config)#cable metering data-per-session 8 timer 100Router#show run | inc meteringcable metering destination 2.7.36.88 6789 0 15 non-securecable metering data-per-session 8 timer 100Related Commands
cable metering destination
To enable usage-based billing and to stream the billing records to an external collection server, use the cable metering destination command in global configuration mode. To disable usage-based billing, use the no form of this command.
cable metering destination ip-address port [ip-address2 port2] retries minutes {non-secure | secure} [cpe-list-suppress] [flow-aggregate] [full-records]
no cable metering
Syntax Description
Command Default
Usage-based billing is disabled, by default. When enabled, CPE IP addresses (a maximum of five per cable modem) are included in the billing records by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The cable metering destination command enables usage-based filling and configures it for streaming mode, where the Cisco CMTS creates the billing records and regularly sends them to an external server for use by the billing application.
The Cisco CMTS attempts to establish a connection with the first (primary) external server, and if this fails, the CMTS sends an SNMP trap about the failure. The Cisco CMTS retries the connection for the number of times specified in the cable metering destination command, and if all of those attempts fail, the Cisco CMTS switches to the secondary external server, if configured. The Cisco CMTS repeats this sequence at every interval, and always tries to connect to the primary server first before attempting to use the secondary server.
Note
If the CMTS cannot transmit the billing record to the external server, and if metering traps have been enabled using the snmp-server enable traps cable metering command, the CMTS sends an SNMP trap to the SNMP manager describing the reason for the failure. Typically, the reason is either that a timeout occurred with the external server, or that the billing record no longer exists on the local filesystem. An SNMP trap is sent for each connection failure.
To disable usage-based billing, use the no cable metering command. This immediately stops the collection of billing information, except when the billing records are currently being streamed to the external server. If a billing operation is in progress when you give the no cable metering command, the system displays the message "CMTS Metering in progress. Ignoring current config." Wait until the billing operation is finished and then reenter the no cable metering command.
Note
Examples
The following example shows how to enable usage-based billing for streaming mode, with the CMTS transmitting the billing records every 60 minutes to the server at the IP address of 10.10.10.37 and TCP port of 5215, using a secure socket layer (SSL) TCP connection. A secondary external service is also defined. The CMTS will retry the connection three times before giving up and switching to the secondary server, as well as sending an SNMPv3 trap to notify the SNMP management system of the failure:
U7246VXR# configure terminalU7246VXR(config)# cable metering destination 10.10.10.37 5215 10.10.10.41 5215 3 60 secureU7246VXR(config)#The following example shows how to enable usage-based billing for streaming mode, with the CMTS transmitting the billing records every 30 minutes to the server at the IP address of 10.10.10.37 and TCP port of 8181, using an unencrypted TCP connection. No secondary server is defined. The CMTS will retry the connection only once before giving up and sending an SNMPv3 trap to notify the SNMP management system of the failure:
Router# configure terminalRouter(config)# cable metering destination 10.10.10.37 8181 1 30 non-secureRouter(config)#The following example shows how to enable usage-based billing, using the same configuration as above, except that the billing records do not include the IP addresses for the CPE devices:
Router# configure terminalRouter(config)# cable metering destination 10.10.10.37 8181 1 30 non-secure cpe-list-suppressRouter(config)#The following example shows how to enable usage-based billing, using an unencrypted TCP connection, including the IP addresses for the CPE devices, and enabling the full-records option:
Router# configure terminalRouter(config)# cable metering destination 10.10.10.37 11 1 222 non-secure full-records cpe-list-suppressRouter#Related Commands
cable metering filesystem
To enable usage-based billing and to write the records to a file on a local file system, use the cable metering filesystem command in global configuration mode. To disable usage-based billing, use the no form of this command.
cable metering filesystem filesystem [cpe-list-suppress] [flow-aggregate] [full-records]
no cable metering
Syntax Description
Command Default
Usage-based billing is disabled, by default. When usage-based billing is enabled, CPE IP addresses (a maximum of five) are included in the billing records by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The cable metering filesystem command enables usage-based filling and configures it for file mode, where the CMTS writes the billing records to the local file system. The system writes the billing record to the filesystem specified by this command, using a file name that consists of the router's hostname followed by a timestamp for when the file was created.
When the CMTS writes a billing record, it can also optionally send an SNMPv3 trap to notify the billing application that a billing record is available for pickup. The billing application can then log into the Cisco CMTS and use the File Transfer Protocol (FTP) or Secure Copy (SCP) to pick up the file.
Note
If the CMTS cannot write the billing record to the local filesystem, and if metering traps have been enabled using the snmp-server enable traps cable metering command, the CMTS sends an SNMP trap to the SNMP manager describing the reason for the failure. Typically, the reason is either that the disk is full or that an disk error occurred (such as no PCMCIA card in the slot).
To disable usage-based billing, use the no cable metering command. This immediately stops the collection of billing information, except when the billing records are currently being written to the local file system. If a billing operation is in progress when you give the no cable metering command, the system displays the message "CMTS Metering in progress. Ignoring current config." Wait until the billing operation is finished and then reenter the no cable metering command.
Examples
The following example shows how to enable usage-based billing, writing the records to a file on the disk0: device.
U7246VXR# configure terminalU7246VXR(config)# cable metering filesystem disk0:U7246VXR(config)#
Note
Router(config)# cable metering filesystem nvram:
The following example shows how to enable usage-based billing, writing the records to files on the disk2 device on an NPE-G1 processor:
Router# configure terminalRouter(config)# cable metering filesystem disk2:Router(config)#The following example shows how to enable usage-based billing, writing the records to files in Flash Memory. The IP addresses for the CPE devices are not included in the billing records.
Router# configure terminalRouter(config)# cable metering filesystem flash: cpe-list-suppressRouter(config)#The following example shows how to enable usage-based billing, writing the records to files in Flash Memory, and enabling the full-records option:
Router# configure terminalRouter(config)# cable metering filesystem disk2:xyz full-recordsRouter#Related Commands
cable metering ipdr
To configure the Subscriber Account Management Interface Specification (SAMIS) and to enable usage-based billing on DOCSIS 2.0 cable modems, use the cable metering ipdr command in global configuration mode. To disable usage-based billing, use the no form of this command.
cable metering ipdr interval session session-id [flow-aggregate] [full-records]
no cable metering
Syntax Description
Command Default
Usage-based billing is disabled, by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The cable metering ipdr command configures how SAMIS data is exported. This command is used for DOCSIS 2.0 SAMIS schema.
When flow-aggregate is enabled, the service flows are combined into one record per cable modem:
•
•
Examples
The following example shows how to enable usage-based billing for IPDR, with the billing record interval set to every 60 minutes with full-records and flow-aggregate options enabled:
Router# configure terminalRouter(config)# cable metering ipdr 60 session 111 full-records flow-aggregateRouter(config)#Related Commands
cable metering ipdr-d3
To configure the Subscriber Account Management Interface Specification (SAMIS) and to enable usage-based billing on DOCSIS 3.0 cable modems, use the cable metering ipdr-d3 command in global configuration mode. To disable usage-based billing, use the no form of this command.
cable metering ipdr-d3 session session-id type type [flow-aggregate] [full-records]
no cable metering
Syntax Description
Command Default
Usage-based billing is disabled, by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The cable metering ipdr-d3 command configures how the SAMIS data is exported. This command is used for DOCSIS 3.0 SAMIS schema (including type 1 and type 2).
When flow-aggregate is enabled, the service flows are combined into one record per cable modem:
•
•
Examples
The following example shows how to enable usage-based billing for IPDR DOCSIS 3.0, with full-records and flow-aggregate options enabled:
Router# configure terminalRouter(config)# cable metering ipdr-d3 session 111 type 2 full-records flow-aggregateRouter(config)#Related Commands
cable metering source-interface
To enables specification of the source-interface for the billing packets, use the cable metering source-interface command in privileged EXEC mode. To turn off the specified source-interface, use the no form of this command.
cable metering source-interface interface
no cable metering source-interface interface
Syntax Description
Defaults
Usage billing is disabled. When enabled, CPE IP addresses (a maximum of five per cable modem) are included in the billing records by default.
Command Modes
Global configuration
Command History
Usage Guidelines
The cable metering source-interface command enables the user to specify the source-interface of the usage based billing packets. All billing packets are usually automatically assigned a source-interface, but users using the cable metering source-interface command can set the source-interface to be the ip address of the loopback interface.
If the user does not specify the source-interface configuration, SAMIS will pick the highest IP address of the loopback interface as the source interface. If the loopback interface is not there, then SAMIS will select the highest IP of the physical interface for source interface.
Refer the DDTS for more info CSCek39658.
Note
Note
If the cable metering source-interface command is used when the Cable ARP Filtering feature is operating in the File Mode, the CMTS IP address in the billing packets will be changed to the ip address of the source-interface as specified through cable metering source-interface command or through setting the ccmtrCollectionSrcIfIndex object. The mac address in the billing packets' header will also be changed to the mac address of the source-interface.
If the cable metering source-interface command is used when the Cable ARP Filtering feature is operating in the Streaming Mode, the CMTS IP address in the billing packets, as well as the source IP address of the billing packets, will be changed to the ip address of the source-interface as specified through cable metering source-interface command or through setting the ccmtrCollectionSrcIfIndex object. The mac address in the billing packets' header will also be changed to the mac address of the source-interface.
When defining the source-interface, the following possible error checks can be performed to determine if the source-interface that the user has defined is a valid source-interface for metering:
1.
2.
Note
Examples
The following is an example where the source-interface specified was a loopback interface and it had a mac-address of 000C31F6F400 and an ip address of 1.100.100.100.
Router# configure terminalRouter(config)# cable metering source-interface loopback 1.100.100.100<?xmlversion="1.0"encoding="UTF8"?><IPDRDocxmlns="http://www.ipdr.org/namespaces/ipdr" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="DOCSIS-3.5-A.0.xsd" docId="C7B1B20E-0000-0000-0000-000C31F6F400" creationTime="2006-03-02T18:03:58Z" IPDRRecorderInfo="VXR3" version="3.5-A.0"><IPDR xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-02T18:03:58Z</IPDRcreationTime><CMTShostn ame>VXR3</CMTShostname><CMTSipAddress>1.100.100.100</CMTSipAddress><CMTSsysUpTime>185867 </CMTSsysUpTime><CMTScatvIfName>Cable4/0</CMTScatvIfName><CMTScatvIfIndex>16</CMTScatvIfIn dex><CMTSupIfName>Ca4/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownI fName>Ca4/0-downstream</CMTSdownIfName><CMmacAddress>00-07-0E-07-0B-0D</CMmacAddress><CMip Address>11.11.0.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><servic eIdentifier>0</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>1< /serviceDirection><serviceOctetsPassed>6225</serviceOctetsPassed><servicePktsPassed>21</se rvicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>1</serviceS laDelayPkts><serviceTimeCreated>0</serviceTimeCreated><serviceTimeActive>0</serviceTimeAct ive></IPDR><IPDR xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-02T18:03:58Z</IPDRcreationTime><CMTShostn ame>VXR3</CMTShostname><CMTSipAddress>1.100.100.100</CMTSipAddress><CMTSsysUpTime>185867 </CMTSsysUpTime><CMTScatvIfName>Cable4/0</CMTScatvIfName><CMTScatvIfIndex>16</CMTScatvIfIn dex><CMTSupIfName>Ca4/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownI fName>Ca4/0-downstream</CMTSdownIfName><CMmacAddress>00-07-0E-07-0B-0D</CMmacAddress><CMip Address>11.11.0.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><servic eIdentifier>0</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>2< /serviceDirection><serviceOctetsPassed>12300</serviceOctetsPassed><servicePktsPassed>29</s ervicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>13</servic eSlaDelayPkts><serviceTimeCreated>0</serviceTimeCreated><serviceTimeActive>0</serviceTimeA ctive></IPDR><IPDRDoc.End count="2" endTime="2006-03-02T18:03:59Z"/></IPDRDoc>Router(config)#The following is an example where the source-interface specified was a loopback interface and it had a mac-address of 00027D67DC0 and an ip address of 2.90.100.100.
Router# configure terminalRouter(config)# cable metering source-interface loopback 2.90.100.10Accept 2.90.100.100:42380<?xmlversion="1.0"encoding="UTF8"?><IPDRDocxmlns="http://www.ipdr.org/namespaces/ipdr" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="DOCSIS-3.5-A.0.xsd" docId="C7B701D1-0000-0000-0000-00027D67DC00" creationTime="2006-03-06T18:45:37Z" IPDRRecorderInfo="ubr7246-R7427" version="3.5-A.0"><IPDR xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-06T18:45:37Z</IPDRcreationTime><CMTShostn ame>ubr7246-R7427</CMTShostname><CMTSipAddress>2.90.100.100</CMTSipAddress><CMTSsysUpTime> 372172 </CMTSsysUpTime><CMTScatvIfName>Cable3/0</CMTScatvIfName><CMTScatvIfIndex>5</CMTScatvIfInd ex><CMTSupIfName>Ca3/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownIf Name>Ca3/0-downstream</CMTSdownIfName><CMmacAddress>00-50-04-F9-EF-88</CMmacAddress><CMipA ddress>11.40.1.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><service Identifier>3</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>2</ serviceDirection><serviceOctetsPassed>228392</serviceOctetsPassed><servicePktsPassed>2216< /servicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>0</servi ceSlaDelayPkts><serviceTimeCreated>6500</serviceTimeCreated><serviceTimeActive>3648</servi ceTimeActive></IPDR><IPDR xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-06T18:45:37Z</IPDRcreationTime><CMTShostn ame>ubr7246-R7427</CMTShostname><CMTSipAddress>2.90.100.100</CMTSipAddress><CMTSsysUpTime> 372172 </CMTSsysUpTime><CMTScatvIfName>Cable3/0</CMTScatvIfName><CMTScatvIfIndex>5</CMTScatvIfInd ex><CMTSupIfName>Ca3/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownIf Name>Ca3/0-downstream</CMTSdownIfName><CMmacAddress>00-50-04-F9-EF-88</CMmacAddress><CMipA ddress>11.40.1.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><service Identifier>4</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>1</ serviceDirection><serviceOctetsPassed>200134</serviceOctetsPassed><servicePktsPassed>2197< /servicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>0</servi ceSlaDelayPkts><serviceTimeCreated>6500</serviceTimeCreated><serviceTimeActive>3648</servi ceTimeActive></IPDR><IPDRDoc.End count="2" endTime="2006-03-06T18:45:37Z"/></IPDRDoc>Closing socket 2.90.100.100:42380Router(config)#Related Commands
cable modem access-group
To configure the access-group for a CM, use the cable modem access-group command in privileged EXEC mode. To disable the specification, use the no access-group form of this command.
cable modem {mac-addr | ip-addr} access-group [access-list | access-name]
cable modem {mac-addr | ip-addr} no access-group
Note
Syntax Description
Command Default
No default behaviors or values
Command Modes
Privileged EXEC
Command History
Examples
The following example shows the cable modem access-group command assigning access-list 1 to the CM with the MAC address of abcd.ef01.2345:
Router# cable modem abcd.ef01.2345 access-group 1Router#Related Commands
cable modem change-frequency
To override the frequency used by a CM, use the cable modem change-frequency command in privileged EXEC mode.
cable modem {mac-addr | ip-addr} change-frequency {ds-frequency-hz [us-channel-id] | us-channel-id}
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command allows the CMTS administrator to change the downstream frequency for a CM, overriding the DOCSIS configuration file setting. This command is not applicable on Cisco IOS Release 12.1(3a)EC.
Examples
The following example shows how to change the downstream frequency of the CM having IP address 172.172.172.12 to 570 MHz:
Router# cable modem 172.172.172.12 change-freq 57000000Router#Related Commands
cable modem max-cpe
To specify a maximum number of permitted hosts per modem (overriding the max-cpe value in the CM configuration file), use the cable modem max-cpe command in global configuration mode.
cable modem max-cpe [n | unlimited]
Syntax Description
n
Specifies the configuration file value. Valid range is 1 to 255.
unlimited
Specifies the maximum CPE value to be unlimited.
Command Default
The max-cpe value provided in the configuration file will be used by the CMTS to limit the number of hosts connected to a single CM (no cable modem max-cpe).
Command Modes
Global configuration
Command History
Examples
The following example shows how to override the max-cpe setting in a CM configuration file:
Router(config)# cable modem max-cpe unlimitedUsage Guidelines
The CMTS enables up to n number of hosts for a modem.When set to unlimited, or n is greater than the max-cpe value in the configuration file of a CM, the max-cpe value in the configuration file of the CM is used.
Note
Note
Caution
The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
•
•
•
The more specific commands override the settings of the less specific commands. For example, if you use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note
Tip
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.
Note
Related Commands
cable modem v6-max-cpe-prefix
To specify the maximum number of IPv6 addresses per modem, use the cable modem v6-max-cpe-prefix command in global configuration mode. To set the default value of the command, use the no form of this command.
cable modem v6-max-cpe-prefix [n]
no cable modem v6-max-cpe-prefix [n]
Syntax Description
n
Specifies the maximum number of IPv6 addresses per modem. The range is from 0 to 1023. The default is 16.
Command Default
The default number of IPv6 addresses per modem is 16.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Note
Examples
The following example shows how to specify the maximum number of the IPv6 addresses per modem:
Router> enableRouter# configure terminalRouter(config)# cable modem v6-max-cpe-prefix 10Router(config)# cable submgmt default activeRouter(config)# exitRelated Commands
show cable modem
Displays information for the registered and unregistered cable modems.
cable modem max-hosts
To specify the maximum number of customer premises equipment (CPE) devices (hosts) that can be supported by a specific CM, use the cable modem max-hosts command in privileged EXEC mode.
cable modem {mac-addr | ip-addr} max-hosts {n | default}
Syntax Description
Command Default
0
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
•
•
•
The more specific commands override the settings of the less specific commands. For example, if you use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note
Tip
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.Examples
The following example shows sets the CM with the IP address of 172.172.172.12 to a maximum of 40 attached CPE devices:
Router# cable modem 172.172.172.12 max-hosts 40Related Commands
cable modem qos profile
To force a DOCSIS 1.0 CM to use a specific quality-of-service (QoS) profile, use the cable modem qos profile command in global configuration mode.
cable modem {mac-addr | ip-addr} qos profile qos-profile-index [no-persistence]
Syntax Description
Command Default
No default behaviors or values
Command Modes
Global configuration
Command History
Usage Guidelines
On a Cisco CMTS running DOCSIS 1.0 software, the cable modem qos profile command forces a CM to use a specific QoS profile.
On a Cisco CMTS running DOCSIS 1.1 software, the cable modem qos profile command temporarily forces a DOCSIS 1.0 or DOCSIS 1.0+ CM to use a specific QoS profile, without forcing the CM to first go off-line and re-register. For DOCSIS 1.0+ CMs, this command affects only the primary SID on the CM.
Note
This command does not affect DOCSIS 1.1 CMs, which support dynamic service change messages that allow the QoS profile to be changed dynamically.
Note
When the no-persistence option is specified, the QoS profile is not applied when a cable modem reboots. Instead, the Cisco CMTS allows the cable modem to use the QoS profile that is specified in its DOCSIS configuration file.
The no-persistence option can be used when initially when identifying potential problem applications and users. When repeat offenders are identified, the service provider can remove the no-persistence option, so that these users continue to use the specified QoS profile even if they reboot their cable modems.
Examples
The following example shows how to specify a QoS profile index to a CM:
Router# cable modem qos profile 255Router#Related Commands
cable modem remote-query
To enable and configure the remote query feature to gather cable modem performance statistics on the Cisco CMTS router, use the cable modem remote-query command in global configuration mode. To disable the gathering of cable modem statistics, use the no form of this command.
cable modem remote-query [polling-interval community-string] [src-ip ip-address]
no cable modem remote-query [src-ip ip-address]
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Usage Guidelines
To use the remote query feature, you must configure the cable modem and Cisco CMTS as follows:
•
•
•
Note
The polling-interval time period determines only how long the Cisco CMTS router waits after completing one polling cycle before beginning a new polling cycle. It does not indicate how long the router spends in each polling cycle, which depends on the number of cable modems being polled. To calculate the approximate time for a polling cycle, assume 4 to 5 CMs per second (100 to 200 milliseconds per CM). Also take into account the possibility that one or more cable modems might not respond, with an approximate timeout period of 90 seconds.
You must specify matching community strings for the cable modem, the snmp-server community community-string command, and the cable modem remote-query command.
You can reissue the cable modem remote-query command to change the polling interval at any time, and the change becomes effective immediately. However, to change the SNMP community string, you must first disable remote polling with the no snmp manager and no cable modem remote-query commands. Then reconfigure the new community string with the snmp-server community community-string, snmp-server manager, and cable modem remote-query commands.
You must configure the remote query feature before configuring the scr-ip option.
Tip
Resetting the Community String for Cable Modem Remote Query
In Cisco IOS Release 12.3BC and later releases, if you wish to reconfigure the SNMP community string for the cable modem remote query feature, perform these brief steps.
1.
2.
3.
4.
Examples
The following example illustrates how to set the polling interval to 5 seconds and the SNMP community string to private:
Router# configure terminalRouter(config)# cable modem remote-query 5 privateRouter(config)# snmp-server community privateRouter(config)# snmp-server managerThe following example demonstrates how to change the remote query configuration, by first deleting the existing configuration and then giving the new configuration:
Router# configure terminalRouter(config)# no cable modem remote-queryRouter(config)# no snmp-server managerRouter(config)# cable modem remote-query 10 publicRouter(config)# snmp-server community publicRouter(config)# snmp-server managerRelated Commands
cable modem service-class-name
To change a QoS service class for a particular cable modem (CM), use the cable modem service-class-name command in privileged EXEC mode.
cable modem {ip-address | mac-address} service-class-name name
Syntax Description
Command Default
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
12.3(23)BC2
This command was introduced.
12.2(33)SCB
This command was integrated into Cisco IOS Release 12.2(33)SCB. Support for the Cisco uBR7225VXR router was added.
Usage Guidelines
This command has the following restrictions:
•
•
•
•
Examples
The following example changes the QoS parameter set for the CM with MAC address aaaa.bbbb.cccc to the service class named "test":
Router# cable modem aaaa.bbbb.cccc service-class-name testRelated Commands
cable multicast ses-cache
To enable multicast replication session on the forwarding interface, use the cable multicast ses-cache command in global configuration and interface configuration mode. To disable, use the no cable multicast ses-cache command.
cable multicast ses-cache value
no cable multicast ses-cache value
Syntax Description
value
Sets the value for the multicast replication session cache. The valid range is from 0 to 500. The default value is 0.
Command Default
This command is disabled by default.
Command Modes
Global configuration (config)
Interface configuration (config-if)
Command History
Usage Guidelines
Multicast replication session cache feature helps reducing CPU utilization by reusing multicast replication sessions stored in the cache. The sessions are cached and reused later when a new IGMP join request is received.
Note
The multicast replication session cache can be configured at a global level for all the interfaces on the Cisco uBR10012 router or at an interface level for a forwarding interface. The session cache value configured at the interface shall override the global configuration.
The cable multicast ses-cache command is supported on the integrated-cable, modular-cable, and wideband-cable interfaces.
Note
•
Associated FeaturesThe cable multicast ses-cache command is used with the multicast replication session cache feature:
•
Examples
The following example sets the multicast replication session cache to 100 at the global level on the Cisco uBR10012 router:
Router# configure terminalRouter(config)# cable multicast ses-cache 100Router(config)# exitThe following example sets the multicast replication session cache on the integrated interface to 10:Router# configure terminalRouter(config)# interface Integrated-Cable 8/1/0:0Router(config-if)# cable multicast ses-cache 10Related Commands
cable modem vendor
To associate the name of a vendor with its Organizational Unique Identifier (OUI), use the cable modem vendor command in global configuration mode. To remove the association of the vendor name with its OUI, use the no form of this command.
cable modem vendor OUI [vendor-name]
no cable modem vendor OUI [vendor-name]
Syntax Description
Command Default
A default database contains approximately 300 OUIs associated with approximately 60 vendor names.
Command Modes
Global configuration
Command History
Usage Guidelines
The cable modem vendor command allows you to associate an arbitrary string with an OUI to identify the vendor of the associated CM. The vendor name is then displayed as part of the show cable modem vendor command.
The show cable modem vendor command uses a default database of approximately 300 OUIs. If the OUI and vendor are not in that database, the show cable modem vendor command displays the OUI as the vendor name, but you can use the cable modem vendor command to associate a vendor name with the new OUI.
If you specify an OUI with the cable modem vendor command that already exists in the OUI database, the previous value is overwritten with the new value. You can use the default prefix to restore the original value for an OUI in the default database.
You can also use the no cable modem vendor command to remove the association between an OUI and a vendor name. The show cable modem vendor command then displays only the OUI as the vendor name.
Tip
Examples
The following shows several examples of the cable modem vendor command using Cisco OUIs:
Router(config)# cable modem vendor 00:01:42 CiscoRouter(config)# cable modem vendor 00:01:43 CiscoRouter(config)# cable modem vendor 00:01:63 CiscoRouter(config)# cable modem vendor 00:01:64 CiscoRouter(config)# cable modem vendor 00:0A:41 CiscoRouter(config)# cable modem vendor 00:0A:42 CiscoRouter(config)#The following shows an example of the default cable modem vendor command being used to restore the original association between Cisco and its company OUI of 00:00:0C. Any previous user-defined vendor name is deleted from the OUI database.
Router(config)# default cable modem vendor 00000CThe following shows an example of the no cable modem vendor command being used to remove the association between Cisco and an OUI of 00:0A:42. If any CMs exist with that OUI, the show cable modem vendor command will display the OUI ("00:0A:42") as the vendor name.
Router(config)# no cable modem vendor 00:0A:42Router(config)#Related Commands
show cable modem vendor
Displays the vendor name or Organizational Unique Identifier (OUI) for the CMs on each cable interface.
cable modulation-profile
To define a modulation profile for use on the router, use the cable modulation-profile command in global configuration mode. To remove the entire modulation profile or to reset a default profile to its default values, use the no form of this command.
DOCSIS 1.0 and 1.1 Mixed Mode:
cable modulation-profile profile {mix | qam-16 | qpsk | robust-mix}
no cable modulation-profile profile {iuc | mix | qam-16 | qpsk | robust-mix}
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len
DOCSIS 1.x/2.0 Mixed Mode:
cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-mid | robust-mix-qam}
no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-mid | robust-mix-qam}
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len
DOCSIS 2.0 A-TDMA Mode:
cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-8 | qam-16 | qam-32 | qam-64 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}
no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-8 | qam-16 | qam-32 | qam-64 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len
Cisco IOS Release 12.2(33)SCC and Later
DOCSIS 2.0 A-TDMA Mode and DOCSIS 2.0 S-CDMA Mode:
cable modulation-profile profile {mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}
no cable modulation-profile profile {iuc | mix-high | mix-low | mix-mid | mix-qam | qam-16 | qpsk | robust-mix-high | robust-mix-low | robust-mix-mid}
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff pre-len last-cw uw-len
Syntax Description
profile
Specifies the modulation profile number. The valid values for the profile number depend on the cable interface being used and the upstream's mode of operation.
See Table 10 for a list of valid ranges based on cable interface and modulation type.
In Cisco IOS Release 12.2(15)CX and later releases, you can create a maximum of 10 profiles for each mode of operation, for a total of 30 profiles. In earlier software releases, you can create a maximum of 8 profiles only for DOCSIS 1.0 and DOCSIS 1.1 mode.
mix
(DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM mix modulation profile where short and long grant bursts are sent using 16-QAM, while request, initial ranging, and station maintenance bursts are sent using QPSK). The burst parameters are set to their default values for each burst type.
mix-high
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default QPSK/64-QAM modulation profile.
mix-low
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default QPSK/16-QAM modulation profile.
mix-mid
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/32-QAM modulation profile.
mix-qam
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default 16-QAM/64-QAM modulation profile.
qam-8
(DOCSIS 2.0 A-TDMA mode only) Creates a default 8-QAM modulation profile.
This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.
qam-16
Creates a default 16-QAM modulation profile.
qam-32
(DOCSIS 2.0 A-TDMA mode only) Creates a default 32-QAM modulation profile.
This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.
qam-64
(DOCSIS 2.0 A-TDMA mode only) Creates a default 64-QAM modulation profile.
This modulation profile is available in hidden and internal mode only from Cisco IOS Release 12.2(33)SCC onwards.
qpsk
Creates a default QPSK modulation profile.
robust-mix
(DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM modulation profile with a longer preamble that is more robust and more able to deal with noise on the upstream better than the mix profile.
robust-mix-high
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/64-QAM mixed modulation profile with a longer preamble that is more robust and more able to deal with noise on the upstream better than the mix-high profile.
robust-mix-low
(DOCSIS 2.0 A-TDMA mode only) Creates a default QPSK/16-QAM modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-low profile.
robust-mix-mid
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a default QPSK/32-QAM modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-mid profile.
robust-mix-qam
(DOCSIS 1.x/2.0 mixed mode only) Creates a default 16-QAM/64-QAM mixed modulation profile with a longer preamble that is more robust and better able to deal with noise on the upstream than the mix-qam profile.
iuc
Interval usage code. Valid entries depend on the mode of operation:
•
•
•
The reqdata burst type is included as a placeholder for scripts that might reference it, but the DOCSIS MAC scheduler on the Cisco CMTS does not use this type of burst.
When you are using the initial and station bursts for DOCSIS 2.0 A-TDMA mode, qam-8, qam-32, and qam-64 modulation profiles are available in hidden mode only.
preamble
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the preamble format. Valid values are qpsk0 and qpsk1.
rs-interleave-depth
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the RS interleave depth. The valid range is from 0 to 114.
rs-interleave-block
(DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and a-short options) Specifies the RS interleave block size. The valid range is from 18 to 2048.
fec-tbytes
The number of bytes that can be corrected per FEC code word. For DOCSIS 1.0 and DOCSIS 1.1 mode, valid values are from 0 to 10 (decimal), where 0 means no FEC. For DOCSIS 2.0 A-TDMA mode, the valid values are from 0 to 16 (decimal), where 0 means no FEC.
fec-len
FEC code-word length. Valid values are from 16 to 253.
burst-len
Maximum burst length in minislots. Valid values are from 0 to 255, where 0 means no limit.
guard-t
Guard time in symbols. The time between successive bursts, with a range from 22 to 255. (In Cisco IOS Release 12.2(15)BC2 and earlier releases, the minimum guard time was 0 symbols, but we do not recommend using a guard time smaller than 22 symbols.)
mod
Modulation. Valid entries are 16qam and qpsk for DOCSIS 1.0 and DOCSIS 1.1 upstreams. Valid entries are 8qam, 16qam, 32qam, 64qam, and qpsk for DOCSIS 2.0 upstreams.
The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and internal modes only from Cisco IOS Release 12.2(33)SCC onwards.
scrambler
Enable or disable scrambler. Valid entries are scrambler and no-scrambler.
seed
(Required if scrambler option used) Scrambler seed in hexadecimal format. Valid values are from 0x0 to 0x7FFF.
diff
Enable or disable differential encoding. Valid entries are diff and no-diff.
In DOCSIS 2.0 mode, differential encoding cannot be enabled for the 8-QAM, 32-QAM, and 64-QAM modulations.
The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and internal modes only from Cisco IOS Release 12.2(33)SCC onwards.
pre-len
Preamble length in bits. Valid values are from 2 to 256.
last-cw
Handling of FEC for last code word. Valid entries are fixed for fixed code-word length and shortened for shortened last code word.
uw-len
Upstream unique word length. Enter uw8 for 8-bit unique code words or uw16 for 16-bit unique code words.
Command Default
Modulation profile 1 is defined as a qpsk Time Division Multiple Access (TDMA) profile.
In Cisco IOS Release 12.2(15)CX, Release 12.2(15)BC2 and later releases, additional modulation profiles are defined as the default mixed TDMA/A-TDMA profile and the default Advanced TDMA (A-TDMA) profile. See Table 10 for a list of valid ranges based on cable interface and modulation type.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
A modulation profile is a collection of at least six burst profiles that are sent out in an upstream channel descriptor (UCD) message to configure a modem's transmit parameters.
You can use the no cable modulation-profile command to remove all modulation profiles except the default modulation profiles (1, 21, 41, 101, 121, 201, 221, 241, and 321, depending on the cable interface line cards being used). In the case of the default modulation profiles, the no cable modulation-profile command resets the default profile to its default values.
We recommend that you use the predefined profiles instead of manually specifying the individual bursts for a modulation profile. The predefined profiles are optimized for the default of 32 symbols per minislot for each particular modulation scheme. The robust predefined profiles use a longer preamble for better handling of noise on the upstream, but at the cost of consuming more PHY layer bandwidth than the other non-robust profiles.
If you want to manually specify the individual bursts, enter a line with all parameters for each upstream burst type. Then repeat this command for each burst type, which also must be fully specified. A profile with incomplete or missing bursts can cause unreliable operation or loss of modem connectivity.
Caution
Note
From Cisco IOS Release 12.2(33)SCC onwards, the qam-8, qam-32, and qam-64 modulation profiles are available in hidden and internal modes only. When you are using the initial and station bursts for DOCSIS 2.0 A-TDMA mode, qam-8, qam-32, and qam-64 modulation profiles are available in hidden mode only. However, these modulation profiles are available for a-long, a-short, a-ugs, long, request, reqdata, and short.
Modulation Profile Ranges
The valid range for modulation profiles depends on the cable interface being used and the type of modulation profile being created. Table 10 lists the valid ranges according to cable interface and modulation type.
Table 10 Allowable Ranges for Modulation Profiles
Cisco uBR7100 series
1 to 101 , default=1
N/A
N/A
N/A
Cisco uBR-MC16C
1 to 10, default=1
N/A
N/A
N/A
Cisco uBR-MC16S
1 to 10, default=1
N/A
N/A
N/A
Cisco uBR-MC28C
1 to 10, default=1
N/A
N/A
N/A
Cisco uBR-MC5X20S, Cisco uBR-MC5X20U, Cisco uBR-MC5X20H
21 to 30, default=21
121 to 130, default=121
221 to 230, default=221
321 to 330 (default is 321)
Cisco uBR-MC16U/X, Cisco uBR-MC28U/X
41 to 50, default=41
141 to 150, default=141
241 to 250, default=241
N/A
1 Only 8 modulation profiles are supported in Cisco IOS software releases before 12.2(15)BC1, so in these releases the valid range is from 1 to 8.
DOCSIS 1.0 and DOCSIS 1.1 Support
For DOCSIS 1.0 and 1.1 cable modems, the following burst types are required: request, request data, initial maintenance, station maintenance, short grant, and long grant. You must issue the cable modulation-profile command six times for each individual burst type to correctly create a new modulation profile.
The three default profiles can be used to quickly create modulation profiles, without having to specify the parameters for each individual burst: mix, qpsk, and qam-16. The burst parameters for the request, initial, station maintenance, short, and long bursts are set to their default values for each burst type. (The reqdata burst type is not created when using the default modulation profiles because it is not used by the MAC scheduler.)
The default profiles allow basic profiles to be implemented for initial network connectivity. As the characteristics of a cable plant become better known, the profiles can then be adjusted accordingly.
Note
Caution
Errors or incompatible configurations in the burst profiles cause cable modems to drop connectivity, to drop short or long data packets, or to fail to connect to the network. It is possible to build a burst profile set for which no implementation of a DOCSIS receiver is capable of receiving the modem's transmission.
Data rates of 160 Ksymbol/sec and 2560 Ksymbol/sec are highly sensitive to unique word length, preamble length, and FEC sizing. Incorrect choices for these values can cause poor, or no, connectivity at these symbol rates.
DOCSIS 2.0 Support
Cisco IOS Release 12.2(11)CY, 12.2(15)BC1, 12.3BC, 12.2(33)SCA, 12.2(33)SCC, and later releases support 10 modulation profiles for each of the three DOCSIS modes (DOCSIS 1.X, DOCSIS 2.0, and mixed mode), for a total maximum of 30 modulation profiles. In addition, the router also creates several default modulation profiles (1, 21, 41, 101, 121, 141, 201, 221, 241, and 321, depending on the cable interface line cards that are installed).
Examples
The following example shows how to create a mixed modulation profile, using 16-QAM for the short and long grant bursts and QPSK for the request, initial ranging, and station maintenance bursts. The burst parameters are set to their default values for each burst type.
Router(config)# cable modulation-profile 8 mixRouter(config)# exitRouter# show cable modulation-profile 8Mod IUC Type Preamb Diff FEC FEC Scrambl Max Guard Last Scrambl Preamblength enco T CW seed B time CW offsetBYTES size size size short8 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 08 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 08 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 08 short qam 144 no 0x6 0x4B 0x152 6 8 yes yes 08 long qam 160 no 0x8 0xDC 0x152 0 8 yes yes 0Router#
Note
The following example shows how to define the burst parameters for profile 2 with the following parameters: 0 fec-tbytes, 16 kbytes fec-len, a burst-len of 1, a guard time of 8, a mod value of qpsk, scrambler enabled with a seed value of 152, differential encoding disabled, a preamble length of 64 bits, a fixed code-word length, and 8-bit unique words for upstream unique word length.
Router(config)# cable modulation-profile 2 request 0 16 1 8 qpsk scrambler 152 no-diff 64 fixed uw8Router(config)# cable modulation-profile 2 reqdata 0 16 1 8 qpsk scrambler 152 no-diff 64 fixed uw8Router(config)# cable modulation-profile 2 initial 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16Router(config)# cable modulation-profile 2 station 5 34 0 48 qpsk scrambler 152 no-diff 128 fixed uw16Router(config)# cable modulation-profile 2 short 6 75 6 8 16qam scrambler 152 no-diff 144 fixed uw8Router(config)# cable modulation-profile 2 long 8 220 0 8 16qam scrambler 152 no-diff 160 fixed uw8
Note
The following example shows an example of a DOCSIS 1.X/DOCSIS 2.0 mixed modulation profile:
Router# configure terminalRouter(config)# cable modulation-profile 142 request 0 16 0 8 qpsk scrambler 152 no-diff 64 fixed uw8Router(config)# cable modulation-profile 142 initial 5 34 0 48 qpsk scrambler 152 no-diff 32 fixed uw16Router(config)# cable modulation-profile 142 station 5 34 0 48 qpsk scrambler 152 no-diff 32 fixed uw16Router(config)# cable modulation-profile 142 short 5 75 6 8 qpsk scrambler 152 no-diff 72 shortened uw8Router(config)# cable modulation-profile 142 long 8 220 0 8 qpsk scrambler 152 no-diff 80 shortened uw8Router(config)# cable modulation-profile 142 a-short qpsk0 0 18 5 99 10 8 64qam scrambler 152 no-diff 128 shortened uw8Router(config)# cable modulation-profile 142 a-long qpsk0 0 18 15 200 0 8 64qam scrambler 152 no-diff 128 shortened uw8Router(config)#The following example shows an example of a DOCSIS 2.0 A-TDMA modulation profile:
Router# configure terminalRouter(config)# cable modulation-profile 242 request qpsk0 0 0 0 16 0 8 qpsk scrambler 152 no-diff 64 fixed uw8Router(config)# cable modulation-profile 242 initial qpsk0 0 0 5 34 0 48 qpsk scrambler 152 no-diff 32 fixed uw16Router(config)# cable modulation-profile 242 station qpsk0 0 0 5 34 0 48 qpsk scrambler 152 no-diff 32 fixed uw16Router(config)# cable modulation-profile 242 short qpsk0 0 0 5 75 6 8 qpsk scrambler 152 no-diff 72 shortened uw8Router(config)# cable modulation-profile 242 long qpsk0 0 0 8 220 0 8 qpsk scrambler 152 no-diff 80 shortened uw8Router(config)# cable modulation-profile 242 a-short qpsk0 0 18 5 99 10 8 64qam scrambler 152 no-diff 128 shortened uw8Router(config)# cable modulation-profile 242 a-long qpsk0 0 18 15 200 0 8 64qam scrambler 152 no-diff 128 shortened uw8Router(config)#The following example shows an example of a DOCSIS 2.0 S-CDMA modulation profile:
Router# configure terminalRouter(config)# cable modulation-profile 324 request 0 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 spreader 12 12 no-tcmRouter(config)# cable modulation-profile 324 initial 0 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 off-spreader 12 12 no-tcmRouter(config)# cable modulation-profile 324 station 0 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 off-spreader 12 12 no-tcmRouter(config)# cable modulation-profile 324 a-short 0 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 off-spreader 12 12 no-tcmRouter(config)# cable modulation-profile 324 a-long 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 off-spreader 12 12 no-tcmRouter(config)# cable modulation-profile 324 a-ugs 16 10 16qam scrambler 152 no-diff 64 fixed qpsk0 off-spreader 12 12 no-tcmRouter(config)#See the show cable modulation-profile command for a description of the output display fields.
Related Commands
cable upstream modulation-profile
Assigns a modulation profile to an interface.
show cable modulation-profile
Displays a modulation profile group's information.
cable modulation-profile global-scheme
To define a global modulation profile for use on the router, use the cable modulation-profile global-scheme command in global configuration mode. To remove the newly created modulation profile or to reset to the legacy profile mode, use the no form of this command.
cable modulation-profile global-scheme profile
no cable modulation-profile global-scheme
Syntax Description
Command Default
The global modulation profile scheme is disabled by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Using the global modulation profile scheme, you can assign any number between 1 to 400 to any modulation profiles. It eliminates the number space restriction and increases the number of modulation profiles that can be created per DOCSIS mode. The global modulation profile mode allows you to create and configure DOCSIS 3.0 channel type 4SR (scdma-d3). When an upstream DOCSIS mode is changed to scdma-d3 , it is initially assigned to the system created default modulation profile as shown in Table 11.
Note
All the existing and previously defined modulation profiles are converted to the new format. However, all the newly created modulation profiles, which are outside of the legacy number space range, are lost when you revert to the legacy modulation profile.
Note
Modulation Profile Ranges
The valid range for modulation profiles depends on the cable interface being used and the type of modulation profile being created.
Table 11 lists the valid ranges according to cable interface and modulation type:
Table 11 Allowable Ranges for Modulation Profiles
Cisco UBR-MC20X20V
321 to 330 (default is 321)
1 to 400 (default is 381)
Examples
The following example shows how to create a global modulation profile scheme:
Router(config)# cable modulation-profile global-schemeRelated Commands
cable upstream modulation-profile
Assigns a modulation profile to an interface.
show cable modulation-profile
Displays modulation profile information of a group.
cable monitor
To enable the forwarding of selected packets on the cable interface to an external LAN analyzer, use the cable monitor command in cable interface configuration mode. To disable this function, use the no form of this command.
cable monitor [incoming | outbound] [timestamp]
interface interface {slot/{subslot | bay}/port} [access-list {name | number}] | [mac-address address] | [sid sid-number] | [upstream number]
[packet-type {data docsis | data ethernet | mac [type type] }]cable monitor outbound downstream {modular-cable | Integrated-cable | wideband-cable} slot/(subslot | bay}/controller:channel
no cable monitor
Syntax Description
Command Default
Both upstream (incoming) and downstream (outbound) traffic is forwarded.
Command Modes
Interface configuration—cable interface only (config-if)
Command History
Usage Guidelines
The cable monitor command allows an external LAN packet analyzer to monitor inbound and outbound data packets for specific types of traffic between the Cisco CMTS and the CMs on a cable interface. This feature enables the CMTS administrator to analyze traffic problems with customer data exchanges.
The interface used for forwarding packets can be used only for the external LAN analyzer; and cannot be used for other purposes. For complete information on configuring and using this feature, see the
Cable Monitor for the Cisco CMTS chapter in the Cisco CMTS Feature Guide or the Cisco IOS CMTS Cable Software Configuration Guide, available on Cisco.com.
Note
–
–
–
Tip
Associated FeaturesThe cable monitor command is used to configure the following features:
•
Examples
The following example shows how to configure the Cisco CMTS so that it monitors incoming MAC-layer packets for the CM with the MAC address of 0123.4567.89ab and forwards copies of the packets to the LAN analyzer on the Ethernet interface in slot 1, port 2:
Router(config-if)# cable monitor incoming interface e1/2 mac-address 0123.4567.89ab packet-type macThe following example shows how to configure a Cisco CMTS running DOCSIS 1.1 software so that it monitors incoming MAC-layer packets of type DSA for the CM identified by SID 173 and forwards copies of the packets to the LAN analyzer on the Ethernet interface in slot 1, port 2:
Router(config-if)# cable monitor incoming interface e1/2 sid 173 packet-type mac type dsaThe following example shows how to configure a mac domain to monitor all packets on a modular primary downstream and forward copies of the packets to a Gigabit Ethernet interface:
Router# configure terminalRouter(config)# interface cable 5/0/0Router(config-if)# cable monitor outbound downstream Modular-Cable 5/1/0:21Router(config-if)# cable monitor outbound interface GigabitEthernet3/0/0Router(config-if)# exitThe following example shows how to configure a mac domain to monitor all packets on a particular downstream bonding group and forward copies of the packets to a Gigabit Ethernet interface:
Router# configure terminalRouter(config)# interface cable 5/0/0Router(config-if)# cable monitor outbound downstream Wideband-Cable 5/1/2:30Router(config-if)# cable monitor outbound interface GigabitEthernet3/0/0Router(config-if)# exitThe following example shows how to configure a mac domain to monitor all packets on a particular bonding group destined to a specific modem and forward copies of the packets to a Gigabit Ethernet interface:
Router# configure terminalRouter(config)# interface cable 5/0/0Router(config-if)# cable monitor outbound downstream Wideband-Cable 5/1/2:30Router(config-if)# cable monitor outbound interface GigabitEthernet3/0/0 mac-address 0123.4567.89abRouter(config-if)# exitRelated Commands
cable mrc-mode
To enable Multiple Receive Channel (MRC) mode for a Media Access Control (MAC) interface during or after the cable modem (CM) registration, use the cable mrc-mode command in cable interface configuration mode. To disable this configuration, use the no form of this command.
cable mrc-mode
no cable mrc-mode
Syntax Description
This command has no arguments or keywords.
Command Default
The MRC mode is enabled by default on a downstream bonding capable cable interface line card.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
When you enable or disable the MRC mode, cable modems switch the operation to or from the MRC mode only after the reinitialization of cable modems. You cannot enable the MRC mode on a non-upstream bonding capable cable interface line card.
Examples
The following example shows how to enable the MRC mode for a MAC interface:
Router# configure terminalRouter(config)# interface cable 7/1/0Router(config-if)# cable mrc-modeRelated Commands
cable mtc-mode
Enables or disables the Multiple Transmit Channel mode (MTC) for a MAC interface.
cable mtc-mode
To enable Multiple Transmit Channel (MTC) mode for a Media Access Control (MAC) interface during or after the cable modem (CM) registration, use the cable mtc-mode command in cable interface configuration mode. To disable this configuration, use the no form of this command.
cable mtc-mode [required-attribute]
no cable mtc-mode [required-attribute]
Syntax Description
Command Default
The MTC mode is enabled by default with the required attribute. With this default configuration, the Cisco CMTS router enables the MTC mode on a per-CM basis by looking at the configuration file of each cable modem.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
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:
•
•
Note
You cannot enable the MTC mode on a non-upstream bonding capable cable interface line card.
Examples
The following example shows how to enable the MTC mode for all cable modems in a MAC domain:
Router# configure terminalRouter(config)# interface cable 7/1/0Router(config-if)# cable mtc-modeRelated Commands
cable mrc-mode
Enables the Multiple Receive Channel mode (MRC) for a MAC interface.
cable multicast auth enable default-action
To enable cable multicast authorization profile and set the maximum sessions limit, use the cable multicast auth enable default-action command in global configuration mode. To disable a cable multicast authorization profile, use the no form of this command.
cable multicast auth enable default-action {permit | deny} max-sessions [limit]
no cable multicast auth enable
Syntax Description
permit
Specifies packets to forward.
deny
Specifies packets to reject.
limit
Specifies the maximum number of dynamic multicast sessions allowed per CM.
No default value.
Max value allowed is 65535.
Command Default
Cable multicast authorization is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command is used to enable cable multicast authorization profile feature and defines the default value. However, it does not define the actual authorization files.
Examples
The following example shows how to enable the default multicast authorization profile:
Router(config)# cable multicast auth enable default-action deny max-sessions 10Related Commands
cable multicast auth profile-name
To define a cable multicast authorization profile, and to set it as the default profile, use the cable multicast auth profile-name command in global configuration mode. To disable a cable multicast authorization profile, use the no form of this command.
cable multicast auth profile-name name [default]
no cable multicast auth profile-name name [default]
Syntax Description
name
Specifies the name of the authorization profile to be used.
default
(Optional) Specifies that the profile name should be treated as the default profile.
Command Default
Cable multicast authorization is disabled.
Command Modes
Global configuration (config)
Command History
12.2(33)SCB
This command was introduced.
12.2(33)SCC
The optional default keyword was added.
Usage Guidelines
This command defines a cable multicast authorization profile, and optionally sets it as the default profile. If the default keyword is not used while modifying the profile, the profile is automatically converted to a non-default profile. Similarly, if the default keyword is added while modifying a profile, the profile is treated as a default profile.
Examples
The following example shows how to use the selected multicast authorization profile:
Router(config)# cable multicast auth profile-name GOLD defaultRelated Commands
cable multicast group-encryption
To configure a group encryption profile for a multicast group, use the cable multicast group-encryption command in global configuration mode. To disable a group encryption profile, use the no form of this command.
cable multicast group-encryption number algorithm 56bit-des
no cable multicast group-encryption number algorithm 56bit-des
Syntax Description
number
Specifies the number of a specific cable multicast QoS group encryption profile. The valid range is 1-255.
algorithm 56bit-des
Specifies that the data encryption standard (DES) is 56 bits.
Command Default
Cable multicast group encryption is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
To apply encryption rules to a cable multicast QoS group, you must first enable and identify an encryption group.
Examples
The following example enables encryption, identifies encryption group 12, and applies the encryption rule to QoS group 2:
Router(config)# cable multicast group-encryption 12 algorithm 56bit-desRouter(config)# cable multicast qos group 2 priority 7 globalRouter(config-mqos)# group-encryption 12Related Commands
cable multicast group-qos
To configure a QoS profile for a QoS group, use the cable multicast group-qos command in global configuration mode. To disable a QoS profile, use the no form of this command.
cable multicast group-qos number scn service-class-name control {single | aggregate
[limit max-sessions]}no cable multicast group-qos number scn service-class-name control {single | aggregate
[limit max-sessions]}Syntax Description
Command Default
The QoS profile for a QoS group is not enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If a QoS profile number is not specified, a default QoS profile is applied. The default group QoS configuration creates a default multicast service flow for each cable interface that is used when a multicast session does not match any classifiers of a GC on the interface.
Examples
The following example configures QoS profile 5 with a service name of name1 and a control of single to indicate that a separate service flow is created for each session. QoS profile 5 is then assigned to QoS group 2.
Router(config)# cable multicast group-qos 5 scn name1 control singleRouter(config)# cable multicast qos group 2 priority 7 globalRouter(config-mqos)# cable multicast group-qos 5Related Commands
cable multicast group-qos default
To configure the service class name of the default multicast quality of service (MQoS) for the QoS profile, use the cable multicast group-qos default command in global configuration mode. To disable the service class name of the default MQoS for the QoS profile, use the no form of this command.
cable multicast group-qos default scn service-class-name aggregate
no cable multicast group-qos default scn service-class-name aggregate
Syntax Description
scn service-class-name
Specifies a service class name for the QoS profile.
aggregate
Specifies that service flows are grouped for sessions in the same MQoS group.
Command Default
The default MQoS profile is not configured.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
If you configure the service class name with the DOCSIS Setup Gateway (DSG) tunnel when no default MQoS exists, the configuration is rejected and you are prompted to configure the default MQoS.
The CMTS selects the primary downstream channel to forward the multicast traffic when the default MQoS is configured and there is no matching MQoS group configuration. Otherwise, the wideband interface is used to forward the multicast traffic.
Note
Examples
The following example configures the default MQoS profile with the service class name name1.
Router(config)# cable multicast group-qos default scn name1 aggregateRelated Commands
cable multicast mdf-disable
To disable Multicast DSID-based Forwarding (MDF) capability of all cable modems associated with a Cisco CMTS router, use the cable multicast mdf-disable command in global configuration mode. To enable MDF on the cable modem, use the no form of this command.
cable multicast mdf-disable [wb-incapable-cm | dsg]
no cable multicast mdf-disable [wb-incapable-cm | dsg]
Syntax Description
Command Default
By default, MDF is not always enabled on the cable modem because it is dependent on the cable modem hardware.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
In Cisco IOS Release 12.2(33)SCE4, the wb-incapable-cm keyword was added to the cable multicast mdf-disable command to disable MDF on all DOCSIS 2.0 hybrid cable modems, including DOCSIS 2.0 DSG embedded cable modems. In Cisco IOS Release 12.2(33)SCF2, the wb-incapable-cm keyword was changed to include only non-DSG DOCSIS 2.0 hybrid cable modems.
After disabling MDF capability, you must run clear cable modem reset command to bring all DSG embedded cable modems online.
Examples
The following example shows how to disable MDF capability on all cable modems:
Router# configure terminalRouter(config)# cable multicast mdf-disableThe following example shows how to disable MDF capability of all non-DSG DOCSIS 2.0 hybrid cable modems:
Router# configure terminalRouter(config)# cable multicast mdf-disable wb-incapable-cmThe following example shows how to disable MDF capability of all DSG embedded cable modems:
Router# configure terminalRouter(config)# cable multicast mdf-disable dsgAssociated FeaturesThe cable multicast mdf-disable command is associated with the following feature:
•
Related Commands
ip multicast-routing
Enables multicast routing globally or on a particular virtual routing and forwarding (VRF) interface.
cable multicast qos group
To specify and configure a cable multicast QoS group and enter multicast QoS configuration mode, use the cable multicast qos group command in global configuration mode. To disable a cable multicast QoS group, use the no form of this command.
cable multicast qos group id priority value [global]
no cable multicast qos group id priority value [global]
Syntax Description
Command Default
A cable multicast QoS group is not identified.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
You must configure a group QoS profile (cable multicast group-qos) and a group encryption profile (cable multicast group-encryption) before you configure a cable multicast QoS group.
Examples
The following example specifies multicast QoS group 2 with a priority of 6 and global application. Application ID, group encryption, group QoS, session range, ToS, and VRF options are configured for QoS group 2.
Router(config)# cable multicast qos group 2 priority 6 globalRouter(config-mqos)# application-id 44Router(config-mqos)# group-encryption 4Router(config-mqos)# group-qos 3Router(config-mqos)# session-range 224.10.10.01 255.255.255.254Router(config-mqos)# tos 1 6 15Router(config-mqos)# vrf name1Related Commands
cable multicast source
To configure a multicast session range for a PacketCable Multimedia (PCMM) multicast group on a Cisco CMTS router, use the cable multicast source command in global configuration mode. To disable this configuration, use the no form of this command.
cable multicast source pcmm
no cable multicast source pcmm
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to configure a multicast session range for a PCMM multicast group on a Cisco CMTS router:
Router# configure terminalRouter(config)# cable multicast source pcmmRouter(config-msrc)# session-range 229.0.0.0 255.0.0.0Related Commands
show packetcable gate multimedia
Displays information about the total number of PCMM multicast gates.
cable nd
To enable the IPv6 Neighbor Discovery (ND) Gleaning feature on the Cisco CMTS router, use the cable nd command in bundle interface configuration mode. To disable IPv6 ND gleaning, use the no form of this command.
cable nd
no cable nd
Syntax Description
This command has no arguments or keywords.
Command Default
The IPv6 ND Gleaning feature is enabled by default.
Command Modes
Bundle interface configuration (config-if)
Command History
Usage Guidelines
The cable nd command adds a CPE (host behind a cable modem) to the Cisco CMTS subscriber database. This command does not impact the IPv6 ND protocol operation on the Cisco CMTS router.
The cable ipv6 source-verify and cable nd commands are not compatible with each other in Cisco IOS Release 12.2(33)SCE and later. You must disable IPv6 ND gleaning using the no form of the cable nd command before configuring IPv6 source verification using the DHCPv6 Leasequery feature.
Examples
The following example shows how to configure IPv6 ND gleaning on the Cisco CMTS router:
Router# configure terminalRouter(config)# interface bundle 1Router(config-if)# cable ndAssociated FeaturesThe cable nd command is associated with the IPv6 ND Gleaning feature.
Related Commands
cable ipv6 source-verify
Enables source verification of IPv6 packets on the Cisco CMTS router.
