-
Cisco IOS CMTS Cable Command Reference
-
Cisco IOS CMTS Cable Command Reference Title
-
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
-
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 through show cable t
-
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
-
Table Of Contents
redundancy force-failover main-cpu
rf-channel cable downstream channel-id
rf-channel ip-address mac-address udp-port
service divert-rate-limit ip trusted-site
service divert-rate-limit non-ip
service divert-rate-limit trusted-site
service udp-small-servers max-servers no-limit
Cable Commands: q through sg
Revised: March 30, 2009, OL-15510-09
New Commands
Modified Commands
Removed Commands
qos-profile enforced
To specify a quality-of-service (QoS) profile that should be enforced when users violate their registered QoS profiles, use the qos-profile enforced command in enforce-rule configuration mode. To delete the enforced QoS profile from the enforce-rule, use the no form of this command.
qos-profile enforced profile-id [no-persistence]
no qos-profile enforced profile-id [no-persistence]
Syntax Description
Command Default
The value of profile-id defaults to 0, and enforced QoS profiles are persistent across cable modem reboots.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
Both the originally provisioned QoS profile and the enforced QoS profile must be created on the Cisco CMTS router. The profile-id does not support QoS profiles that are created by the cable modem.
An enforce-rule can specify an enforced QoS profile, which is automatically applied to subscribers who transmit more traffic than allowed by their registered QoS profile. The enforced QoS profile remains in effect during the penalty time period (see the penalty-period command). At the end of the penalty period, the subscriber returns to the registered QoS profile.
If a cable modem reboots while it is in its penalty time period, it continues using the enforced QoS profile, unless the service provider has manually changed the cable modem's registered QoS profile using the cable modem qos profile command.
When you change the enforced QoS profile for a currently active enforce-rule, any cable modems using this rule that are currently in the penalty period continue using the previously configured enforced QoS profile. Any cable modems that enter the penalty period after this configuration change, however, use the new enforced QoS profile.
An enforced QoS profile must already have been created on the Cisco CMTS router before you can assign it to an enforce-rule. If the rule does not exist, the system displays an error message.
When the no-persistence option is specified, the enforced QoS profile is still automatically applied to subscribers who violate their bandwidth requirements. However, when the cable modem reboots, the Cisco CMTS router 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 using the Subscriber Traffic Management feature to identify potential problem applications and users. When repeat offenders are identified, they can then be assigned enforce-rules that do not use the no-persistence option, so that they remain in the penalty period even if they reboot their cable modems.
Note
The system automatically applies the enforced QoS profile to violators only if the enforce keyword has been used with the activate-rule-at-byte-count command.
Examples
The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule:
Router# configure terminalRouter(config)# cable qos enforce-rule residentialRouter(enforce-rule)# qos-profile enforced 12The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule, but with the no-persistence option specified, so that the enforced QoS profile does not remain in force if the cable modem reboots:
Router# configure terminalRouter(config)# cable qos enforce-rule residentialRouter(enforce-rule)# qos-profile enforced 12 no-persistenceThe following example shows the error message that is displayed when the specified QoS profile does not exist on the CMTS:
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# qos-profile enforced 98The qos profile 98 doesn't exist or it's a cm created QoS profileRelated Commands
qos-profile registered
To specify the registered quality of service (QoS) profile that should be used for this enforce-rule, use the qos-profile registered command in enforce-rule configuration mode. To remove the registered QoS profile from the enforce-rule, use the no form of this command.
qos-profile registered profile-id
no qos-profile registered profile-id
Syntax Description
Command Default
The default profile ID is 0.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
You must specify a registered QoS profile for each enforce-rule. The Cisco CMTS router then uses the registered profile ID to match subscribers' service flows to the proper enforce-rules.
When you change the registered QoS profile for an active rule, the cable modems that had been using the previous registered QoS profile are no longer managed by the Subscriber Traffic Management feature. Instead, the rule begins managing those cable modems that use the new registered QoS profile.
Note
Examples
The following example shows profile 50 being assigned as the registered QoS profile to an enforce-rule:
Router# configure terminalRouter(config)# cable qos enforce-rule enforce-ruleRouter(enforce-rule)# qos-profile registered 50The following example shows the error message that is displayed when the specified QoS profile does not exist on the CMTS:
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# qos-profile registered 99The qos profile 99 doesn't exist or it's a cm created QoS profileRelated Commands
rcp-id
To assign a receive channel profile (RCP) ID to a receive channel configuration (RCC) template, use the rcp-id command in RCC template configuration mode. To remove the RCP ID, use the no form of this command.
rcp-id rcp-id
no rcp-id rcp-id
Syntax Description
rcp-id
Specifies an RCP ID for the RCC template. The valid range is from 00 00 00 00 00 to FF FF FF FF FF.
Command Default
By default the RCP ID is set to 00 00 00 00 00. However, you must change the default value to a non-zero RCP ID.
Command Modes
RCC template configuration (config-rcc-template)
Command History
Usage Guidelines
A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive channel (RC) entry.
First, you define an RCC template for an RCP, and then assign the template to a cable interface to generate RCCs based on the actual DS channel configuration.
Examples
The following example shows how to assign an RCP ID to an RCC template:
Router# configure terminalRouter(config)# cable rcc-template 1Router(config-rcc-template)# rcp-id 00 10 00 00 03Related Commands
receive-channel
To associate a receive channel to a receive module (RC), use the receive-channel command in RCC template configuration mode. To restore the default value, use the no form of this command.
receive-channel index center-frequency Hz connected-receive-module index [primary]
no receive-channel index center-frequency Hz connected-receive-module index
Syntax Description
Command Default
.No default behavior or values.
Command Modes
RCC template configuration (config-rcc-template)
Command History
Usage Guidelines
A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive channel (RC) entry. First, you define an RCC template for an RCP, and then assign the template to a cable interface to generate RCCs based on the actual DS channel configuration.
An RCC template configures the physical layer components described by an RCP, including receive modules and receive channels to specific downstream frequencies, and specifies the interconnections among receive modules or between receive modules and receive channels.
A receive module can include multiple receive channels. So we need to specify which receive channel belongs to which receive module.
Examples
The following example shows how to associate a receive channel to a receive module:
Router# configure terminalRouter(config)# cable rcc-template 1Router(config-rcc-template)# rcp-id 00 10 00 00 03Router(config-rcc-template)# receive-module 1 first-channel-center-frequency 555000000Router(config-rcc-template)# receive-channel 1 center-frequency 555000000 connected-receive-module 1 primaryRouter(config-rcc-template)# receive-channel 2 center-frequency 561000000 connected-receive-module 1Related Commands
receive-module
To associate a receive module (RC) to a Receive Channel Configuration (RCC) template, use the receive-module command in RCC template configuration mode. To restore the default value, use the no form of this command.
receive-module index first-channel-center-frequency Hz [connected-receive-module index]
no receive-module index first-channel-center-frequency Hz [connected-receive-module index]
Syntax Description
Command Default
.No default behavior or values.
Command Modes
RCC template configuration (config-rcc-template)
Command History
Usage Guidelines
A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive channel (RC) entry. First, you define an RCC template for an RCP, and then assign the template to a cable interface to generate RCCs based on the actual DS channel configuration.
An RCC template configures the physical layer components described by an RCP, including receive modules and receive channels to specific downstream frequencies, and specifies the interconnections among receive modules or between receive modules and receive channels.
A receive module can include multiple receive channels. So we need to specify which receive channel belongs to which receive module.
Examples
The following example shows how to associate a receive module to an RCC template:
Router# configure terminalRouter(config)# cable rcc-template 1Router(config-rcc-template)# rcp-id 00 10 00 00 03Router(config-rcc-template)# receive-module 1 first-channel-center-frequency 555000000Router(config-rcc-template)# receive-channel 1 center-frequency 555000000 connected-receive-module 1 primaryRouter(config-rcc-template)# receive-channel 2 center-frequency 561000000 connected-receive-module 1Related Commands
redundancy
To enter redundancy configuration mode, use the redundancy command in global configuration mode.
redundancy
Syntax Description
This command has no arguments or keywords.
Command Default
No default behaviors or values.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the redundancy command to enter redundancy configuration mode, where you can define aspects of redundancy such as shelf redundancy for the Cisco AS5800 universal access server.
Cisco 10000 Series Router
Before configuring line card redundancy, install the Y-cables. Before deconfiguring redundancy, remove the Y-cables.
The following restrictions apply to line card redundancy on the Cisco 10000 series router:
•
•
•
Cisco 7600 Series Router
From redundancy configuration mode, you can enter the main CPU submode to manually synchronize the configurations that are used by the two supervisor engines.
From the main CPU submode, you can use the auto-sync command to use all of the redundancy commands that are applicable to the main CPU.
To select the type of redundancy mode, use the mode command.
Nonstop forwarding (NSF) with stateful switchover (SSO) redundancy mode supports IPv4. NSF with SSO redundancy mode does not support IPv6, INternetwork Packet Exchange (IPX), and Multiprotocol Label Switching (MPLS).
Cisco uBR10012 Universal Broadband Router
After you enter redundancy configuration mode, you can use the main-cpu command to enter main-CPU redundancy configuration mode, which allows you to specify which files are synchronized between the active and standby Performance Routing Engine (PRE) modules.
Examples
The following example enables redundancy mode:
Router(config)# redundancyRouter(config-red)#The following example assigns the configured router shelf to the redundancy pair designated as 25. This command must be issued on both router shelves in the redundant router-shelf pair:
Router(config)# redundancyRouter(config-red)# failover group-number 25Cisco 10000 Series Router
The following example configures two 4-port channelized T3 half eight line cards that are installed in line card slot 2 for one-to-one redundancy:
Router(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 2/1 primaryRouter(config-red-lc)# member subslot 2/0 secondaryCisco 7600 Series Router
The following example shows how to enter the main CPU submode:
Router (config)# redundancyRouter (config-r)# main-cpuRouter (config-r-mc)#Cisco uBR10012 Universal Broadband Router
The following example shows how to enter redundancy configuration mode and the commands that are available in that mode on the Cisco uBR10012 router:
Router# config tRouter(config)# redundancyRouter(config-r)# ?Redundancy configuration commands:associate Associate redundant slotsexit Exit from redundancy configuration modemain-cpu Enter main-cpu modeno Negate a command or set its defaultsRelated Commands
redundancy force-failover main-cpu
To force a switchover, so that the standby Performance Routing Engine (PRE1) module becomes the active PRE1 module, use the redundancy force-failover main-cpu command in privileged EXEC mode.
redundancy force-failover main-cpu
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The redundancy force-failover main-cpu command initiates a manual switchover, so that the standby PRE1 module becomes the active PRE1 module and assumes full responsibilities for router operations. This command requires that both PRE1 modules are running a Cisco IOS software image that supports the Route Processor Redundancy (RPR) feature.
Note
A manual switchover is typically done for one of the following reasons:
•
•
•
A switchover can also be manually initiated by removing the active PRE1 module from the chassis, but using the redundancy force-failover main-cpu command provides a more graceful switchover, without generating hardware alarms.
Tip
Tip
Examples
The following example shows a switchover being manually initiated:
Router# redundancy force-failover main-cpuProceed with switchover to standby PRE? [confirm] y
Note
The following example shows a switchover being attempted but failing because the standby PRE1 module is either not ready, not available, or not installed:
Router# redundancy force-failover main-cpuProceed with switchover to standby PRE? [confirm]Standby PRE not ready, switchover aborted.Router#
Note
Unable to communicate with standby PRE, switchover aborted.Related Commands
redundancy force-switchover
To force the standby Route Processor (RP) to assume the role of the active RP, use the redundancy force-switchover command in privileged EXEC mode.
redundancy force-switchover [main-cpu]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the redundancy force-switchover command to switch control of a router from the active RP to the standby RP. Both the active and standby RPs must have a high availability Cisco IOS image installed and must be configured for Route Processor Redundancy (RPR) mode before the redundancy force-switchover command can be used. Before the system switches over, it verifies that the standby RP is ready to take over.
When you use the redundancy force-switchover command and the current running configuration is different from the startup configuration, the system prompts you to save the running configuration before the switchover is performed.
Note
On Cisco 7600 series routers, the redundancy force-switchover command conducts a manual switchover to the redundant supervisor engine. The redundant supervisor engine becomes the new active supervisor engine running the new Cisco IOS image. The modules are reset and the module software is downloaded from the new active supervisor engine.
The active and redundant supervisor engines do not reset on a Route Processor Redundancy Plus (RPR+) switchover. The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine.
Beginning with Cisco IOS Release 12.2(33)SCA, you can force a Performance Routing Engine (PRE) switchover using the redundancy force-switchover main-cpu command from either the primary or standby PRE. If you force a switchover from the active PRE, both PREs synchronize and the active PRE reloads normally. When you force a switchover from the standby PRE, a crash dump of the active PRE occurs for troubleshooting purposes. Forcing a switchover from the standby PRE should only be done if you cannot access the active PRE.
Examples
The following example shows a switchover from the active RP to the standby RP on a Cisco 7513 router with RPR configured:
Router# configure terminalRouter(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# hw-module slot 6 image slot0:rsp-pv-mzRouter(config)# slave auto-sync configRouter(config)# redundancyRouter(config-r)# mode rprRouter(config-r)# endRouter# copy running-config startup-configRouter# redundancy force-switchoverThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is different from the startup configuration:
Router# redundancy force-switchoverSystem configuration has been modified. Save? [yes/no]:yBuilding configuration.........[OK]Proceed with switchover to standby NSE? [confirm]y00:07:35:%SYS-5-SWITCHOVER:Switchover requestedThe following example shows how to perform a manual switchover from the active to the standby RP when the running configuration is the same as the startup configuration:
Router# redundancy force-switchoverProceed with switchover to standby NSE? [confirm]00:07:35:%SYS-5-SWITCHOVER:Switchover requestedRelated Commands
redundancy reload
To reset the standby PRE module or to reset both the active and standby PRE modules, use the redundancy reload command in privileged EXEC mode.
redundancy reload {peer | shelf}
Syntax Description
Defaults
No default behavior or values
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The redundancy reload peer command reloads the Cisco IOS software on the standby PRE1 module, which does not have an impact on router operations, assuming a switchover is not required while the standby module is resetting. The redundancy reload shelf command reloads the Cisco IOS software on both the active and standby PRE1 modules, which will interrupt services on the router until all PRE1 modules and line cards initialize and come back online.
Examples
The following example shows a switchover being manually initiated, overriding any checks that might prevent or delay the switchover:
Router# redundancy reload peerReload peer? [confirm] yPreparing to reload peer
Note
The following example shows the system's response when a standby PRE1 module is not installed in the router:
Router# redundancy reload peerSystem is running in SIMPLEX mode, reload anyway? [confirm] nPeer reload not performed.The following example shows how to reload both PRE1 modules:
Router# redundancy reload shelfReload the entire shelf [confirm] yPreparing to reload entire shelf
Note
Related Commands
redundancy switch-activity
To force a switchover to the standby PRE module, use the redundancy switch-activity command in privileged EXEC mode.
redundancy switch-activity [force]
Note
Syntax Description
force
(Optional) Forces a switchover immediately, overriding any checks in the code or configuration that might prevent or delay a switchover.
Command Default
No default behavior or values
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The redundancy switch-activity command is similar to the redundancy force-failover main-cpu command, except that it includes an option to force the switchover, overriding any configuration checks or other checks in the software that could prevent the switchover. In all cases, this command verifies that the standby PRE module is available and capable of performing the switchover before it transfers control to that PRE module. This command also synchronizes the current running-config and client data before initiating the switchover.
Examples
The following example shows a switchover being manually initiated, overriding any checks that might prevent or delay the switchover:
Router# redundancy switch-activity forceProceed with switchover to standby PRE? [confirm] y
Note
Related Commands
registered qos-profile
Note
To specify the registered quality of service (QoS) profile that should be used for this enforce-rule, use the registered qos-profile command in enforce-rule configuration mode. To remove the registered QoS profile from the enforce-rule, use the no form of this command.
registered qos-profile profile-id
no registered qos-profile profile-id
Syntax Description
Command Default
The default profile ID is 0.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
12.2(15)BC1
This command was introduced.
12.3(9a)BC
This command was replaced by the qos-profile registered command.
Usage Guidelines
You must specify a registered QoS profile for each enforce-rule. The Cisco CMTS router then uses the registered profile ID to match subscribers' service flows to the proper enforce-rules.
When you change the registered QoS profile for an active rule, the cable modems that had been using the previous registered QoS profile are no longer managed by the Subscriber Traffic Management feature. Instead, the rule begins managing those cable modems that use the new registered QoS profile.
Note
Examples
The following example shows profile 50 being assigned as the registered QoS profile to an enforce-rule:
Router# configure terminalRouter(config)# cable qos enforce-rule enforce-ruleRouter(enforce-rule)# registered qos-profile 50The following example shows the error message that is displayed when the specified QoS profile does not exist on the CMTS:
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# registered qos-profile 99The qos profile 99 doesn't exist or it's a cm created QoS profileRelated Commands
revertive
To enable the revert operation on a protect card, use the revertive command in line card redundancy group mode.
revertive time
no revertive time
Syntax Description
Command Default
None
Command Modes
Line card redundancy group (config-red-lc)
Command History
Examples
The following example shows how to specify the revert operation time for a protect card on a uBR10012 router:
Router# configure terminalRouter(config)# redundancyRouter(config-red)# linecard-group 1 cableRouter(config-red-lc)# revertive 30Related Commands
linecard-group
Creates a line card group for one-to-one line card redundancy.
redundancy
Enters redundancy mode.
member subslot
Enables the redundancy role of a line card.
rf-channel cable downstream channel-id
To assign a downstream channel ID to an RF channel, use the rf-channel cable downstream channel-id command in controller configuration mode. To remove a downstream channel ID for an RF channel, use the no form of this command.
rf-channel rf-port cable downstream channel-id channel-id
no rf-channel rf-port cable downstream channel-id channel-id
Syntax Description
Command Default
If the rf-channel cable downstream channel-id command is not issued, Cisco IOS software assigns a unique downstream channel ID to the RF channel.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
For the wideband channel to work correctly, each RF channel on the fiber node that the wideband channel uses must have a unique downstream channel ID. By default, Cisco IOS software assigns a unique downstream channel ID to the RF channel. Use the rf-channel cable downstream channel-id command to change the default channel ID.
The downstream channel ID that is assigned to the RF channel must be unique on the fiber node.
•
•
You can check downstream channel IDs that are being used by examining the CMTS router configuration file.
Refer to cable downstream channel-id id command for the updated downstream channel ID scheme table.
Note
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels depending on how the SPA is configured with the annex modulation command.
•
•
Note
Examples
The following example shows how to assign a downstream channel ID of 123 to RF channel 3 on the Wideband SPA located in slot/subslot/bay 1/0/1.
Router# configure terminalRouter(config)# controller modular-cable 1/0/1Router(config-controller)# rf-channel 3 cable downstream channel-id 123Related Commands
rf-channel description
To configure the description of an RF channel on a Wideband SPA, use the rf-channel description command in controller configuration mode. To remove an RF channel configuration, use the no form of this command.
rf-channel rf-port description description
no rf-channel rf-port description description
Syntax Description
Command Default
No default RF channel configuration values are set for the description.
Command Modes
Controller configuration (config-controller)
Command History
12.3(21)BC
This command was introduced for the Cisco uBR10012 router.
12.2(33)SCA
This command was integrated into Cisco IOS Release 12.2(33)SCA.
Usage Guidelines
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels depending on how the SPA is configured with the annex modulation command. For annex A and 256 QAM, each Wideband SPA supports up to 18 RF channels at full rate and up to 24 RF channels at less than full rate. For all other cases, the SPA supports 24 RF channels.
Note
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel using the rf-channel frequency command. The annex modulation command is obsolete.Examples
The following example shows how to configure the description of the RF channel characteristics for RF port 0:
Router# configure terminalRouter(config)# controller modular-cable 1/0/0Router(config-controller)# rf-channel 0 description Primary downstream channelRelated Commands
rf-channel frequency
To configure the frequency of an RF channel on a Wideband SPA, use the rf-channel frequency command in controller configuration mode. To remove the frequency of an RF channel configuration, use the no form of this command.
Cisco IOS Releases 12.3(21)BC and 12.2(33)SCA
rf-channel rf-port frequency freq
no rf-channel rf-port frequency
Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB
rf-channel rf-port frequency freq [annex {A | B} modulation {64 | 256}
[interleave-depth {8 | 12 | 16 | 32 | 64 | 128}]]no rf-channel rf-port frequency
Syntax Description
Command Default
No default RF channel configuration values are set for frequency, annex, and modulation. The default value for interleave-depth is 32.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
Cisco IOS Release 12.3(21)BC and Cisco IOS Release 12.2(33)SCA
This command configures the frequency for an RF channel on a Wideband SPA.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels depending on how the SPA is configured with the annex modulation command. For annex A and 256 QAM, each Wideband SPA supports up to 18 RF channels. For all other cases, the SPA supports up to 24 RF channels.
Note
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel using the rf-channel frequency command. The annex modulation command is obsolete.Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB
This command configures the frequency for an RF channel on a Wideband SPA. The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels. For annex A and 256 QAM, each Wideband SPA supports up to 18 RF channels at full rate. For all other cases, the SPA supports up to 24 RF channels.
For each RF channel, use the rf-channel frequency command in controller configuration mode to configure RF-channel characteristics. For Cisco IOS Release 12.3(21)BC, for each RF channel (rf-port), the frequency option must be configured with the rf-channel frequency command.
Uniqueness of frequency is required for all cable downstream channels on all cable interfaces and all Wideband SPAs on the CMTS.
Note
Examples
The following example shows how to configure RF channel frequency for RF port 0:
Router# configure terminalRouter(config)# controller modular-cable 1/0/0Router(config-controller)# rf-channel 0 frequency 699000000 annex A modulation 256 interleave-depth 64Related Commands
rf-channel ip-address mac-address udp-port
To configure the IP address, MAC address, UDP port and DEPI remote ID of an RF channel on a Wideband SPA, use the rf-channel ip-address mac-address udp-port command in controller configuration mode. To remove the IP address, MAC address, UDP port and DEPI remote ID configuration of an RF channel, use the no form of this command.
Cisco IOS Releases 12.3(21)BC and 12.2(33)SCA
rf-channel rf-port ip-address ip-address mac-address mac-address udp-port portnum
no rf-channel rf-port ip-address ip-address mac-address mac-address udp-port portnum
Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB
rf-channel rf-port ip-address ip-address mac-address mac-address {udp-port portnum | depi-remote-id session-id}
no rf-channel rf-port ip-address ip-address mac-address mac-address {udp-port portnum | depi-remote-id session-id}
Syntax Description
Command Default
No default RF channel configuration values are set.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
For each RF channel, use the rf-channel ip-address mac-address udp-port command in controller configuration mode to configure RF-channel characteristics.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels depending on how the SPA is configured with the annex modulation command. For annex A and 256 QAM, each Wideband SPA supports up to18 RF channels. For all other cases, the SPA supports up to 24 RF channels.
Note
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel using the rf-channel frequency command. The annex modulation command is obsolete.For each RF channel (rf-port), the following items must be configured with rf-channel ip-address mac-address udp-port command:
Cisco IOS Release 12.3(21)BC and Cisco IOS Release 12.2(33)SCA
•
•
•
•
Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB
•
•
•
•
The value used for mac-address in the mac-address argument is as follows:
•
•
The UDP port number set for the RF channel allows mapping an input UDP session to a specific QAM output port. Wideband traffic from different Wideband SPAs cannot be mixed on the same QAM output ports.
Note
Examples
The following example shows how to configure the RF channel IP address, MAC address UDP port and DEPI remote ID characteristics for RF port 0:
Router# configure terminalRouter(config)# controller modular-cable 1/0/0Router(config-controller)# rf-channel 0 ip-address 192.168.200.30 mac-address0011-920e-a9ff udp-port 49152Related Commands
rf-channel network-delay
To configure the network delay for an RF channel on a Wideband SPA, use the rf-channel network delay command in controller configuration mode. To remove the network delay configuration for an RF channel, use the no form of this command.
rf-channel rf-port network-delay delay
no rf-channel rf-port network-delay delay
Syntax Description
Command Default
No default RF channel network delay configuration values are set.
Command Modes
Controller configuration (config-controller)
Command History
12.3(23)BC
This command was introduced for the Cisco uBR10012 router.
12.2(33)SCB
This command was integrated into Cisco IOS Release 12.2(33)SCB.
Usage Guidelines
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF channels depending on how the SPA is configured with the annex modulation command. For annex A and 256 QAM, each Wideband SPA supports up to18 RF channels. For all other cases, the SPA supports up to 24 RF channels.
Note
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel using the rf-channel frequency command. The annex modulation command is obsolete.Examples
The following example shows how to configure the RF channel network delay characteristics for RF port 0:
Router# configure terminalRouter(config)# controller modular-cable 1/0/0Router(config-controller)# rf-channel 0 network-delay 1000Related Commands
secondary aux
To enable the auxiliary port on the standby PRE1 module, use the secondary aux command in redundancy configuration (main-cpu) mode. To disable the auxiliary port, use the no form of this command.
secondary aux
no secondary aux
Syntax Description
This command has no keywords or arguments.
Command Default
The auxiliary port on the standby PRE1 module is disabled.
Command Modes
Redundancy configuration, main-cpu mode
Command History
Examples
The following example shows how to enable the auxiliary port on the standby PRE1 module.
Router# config tRouter(config)# redundancyRouter(config-r)# main-cpuRouter(config-r-mc)# secondary auxRouter(config-r-mc)# exitRouter(config-f)# exitRouter(config)#Related Commands
service-class (enforce-rule)
To identify a particular service class for cable modem monitoring in an enforce-rule, use the service-class (enforce-rule) command in enforce-rule configuration mode. To remove the service class from the enforce-rule, use the no form of this command.
service-class {enforced | registered} name
no service-class {enforced | registered} name
Syntax Description
enforced
Specifies an enforced service class.
registered
Specifies enforcing of QoS profiles for the registered service class.
name
Specifies the name of the service class.
Command Default
No default behavior or values
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
12.3(9a)BC
This command was introduced.
12.2(33)SCA
This command was integrated into Cisco IOS Release 12.2(33)SCA. Support for the Cisco uBR7225VXR router was added.
Usage Guidelines
The service-class (enforce-rule) command allows operators to identify the name of the initial registered service class for a CM in an enforce-rule, and also the name of a new service class to be enforced if the CM violates its registered service parameters.
Examples
The following example shows specification of the enforced service class called "test" in an enforce-rule:
Router(enforce-rule)# service-class enforced test
Related Commands
service divert-rate-limit
Note
To configure PXF Divert-Rate-Limit, use the service divert-rate-limit command in interface configuration mode. To reset this feature to the default parameters, use the no form of this command.
service divert-rate-limit divert-code rate [limit limit]
no service divert-rate-limit divert-code
Syntax Description
Defaults
Divert-Rate-Limit contains the following default behavior and values:
•
•
•
Command Modes
Interface configuration—cable interface only (config-if)
Command History
Usage Guidelines
The service divert-rate-limit command is used to configure the PXF Divert-Rate-Limit for fwd-glean and rpf-glean packets in order to identify packet streams that will cause congestion of the FP-to-RP interface.
Examples
The following example shows how to configure rate-limiting for fib-rp-glean, with a rate of 10 packets-per-second and a limit of 20 packets:
Router(config-if)# service divert-rate-limit fib-rp-glean 10 limit 20The following example shows how to return rate-limiting for fib-rp-glean to the default values:
Router(config-if)# no service divert-rate-limit fib-rp-gleanPass and fail counters are kept for fwd-glean, rpf-glean, and cable-ARP packets. To show the statistics for the pass and fail counter, use the show pxf cpu statistics drl command:
Router(config-if)# show pxf cpu statistics drlDivert-Rate-Limit statisticscode total diverted droppedfib_rpf_glean 500 59 441fib_rp_glean 500 54 446arp_filter 0 0 0
Note
Packets dropped by Divert-Rate-Limit and the ARP Filter will be recorded in the regular PXF drop statistics:
Router(config-if)# show pxf cpu statistics drop c5/0/0FP drop statistics for Cable5/0/0packets bytesvcci undefined 0 0vcci C...divert_rate_limit 441 28224arp_filter_reply 0 0arp_filter_request 0 0Related Commands
show cable arp-filter
Displays the total number of Address Resolution Protocol (ARP) offenders.
service divert-rate-limit ip
To set DRL rate and limit for WAN-side IP packet streams, use the service divert-rate-limit ip command in global configuration mode. To reset the rate and limit to the default values for all IP divert-codes, use the no form of this command. Using no service divert-rate-limit ip divert-code will reset rate and limit to the default values for the specified divert code.
service divert-rate-limit ip divert-code rate rate limit limit
no service divert-rate-limit ip
Syntax Description
Command Default
For WAN-side IP packet streams, the default rate is 4000 packets per second and default limit is 4000 packets. These defaults apply to each uniquely identified IP packet stream.
Command Modes
Global configuration (config)
Command History
12.2(33)SCB
This command was introduced.
The service divert-rate-limit ip fib-rp-glean command is the WAN-side replacement for the service divert-rate limit fib-rp-glean command.
Usage Guidelines
You can configure a rate and limit for a particular IP divert-code for WAN-side IP packets. However, each IP packet-stream is uniquely identified (using a hash of the VRF, the IP source address, and the divert-code), and then packets in that stream are sent through a rate-limiter with the configured rate and limit.
Examples
The following example shows how to set the rate and limit for the specified divert code:
Router(config)# service divert-rate-limit ip fib-rp-glean rate 1 limit 4Related Commands
service divert-rate-limit ip trusted-site
To add entries to the trusted site list, use the service divert-rate-limit ip trusted-site command in the global configuration mode. To remove all entries from the trusted site list, use the no form of this command.
service divert-rate-limit ip trusted-site ip-address mask ip-address tos tos-value mask tos-mask vrf vrf-name
no service divert-rate-limit ip trusted-site ip-address mask ip-address tos tos-value mask tos-mask vrf vrf-name
Syntax Description
Command Default
No default behavior or values.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The service divert-rate-limit ip trusted-site command is used to configure trusted site list that contains a source IP address and mask, IP ToS value and mask, and a VRF. If no IP address is specified, the entire trusted site list is cleared. The trusted site list contains a source IP address and mask, IP ToS value and mask, and a VRF. The trusted site list applies only to WAN-IP IPv4 packets. There is a limitation of four trusted sites.
Examples
The following example shows how to configure trusted site list:
Router(config)# service divert-rate-limit trusted-site 64.12.13.0 255.255.0.255tos 0xD0 mask 0xF3 vrf name1Related Commands
service divert-rate-limit non-ip
This command sets and limit default values for the specified divert code.
service divert-rate-limit non-ip
To set DRL for WAN-side non-IP packet streams, use the service divert-rate-limit non-ip command in global configuration mode. To reset the rate and limit to the default values for all non-IP divert-codes, use the no form of this command. Using no service divert-rate-limit non-ip divert-code will reset rate and limit to the default values for the specified divert-code.
service divert-rate-limit non-ip divert-code rate rate limit limit
no service divert-rate-limit non-ip
Syntax Description
Command Default
For WAN-side non-IP packets, the default rate is 2000 packets per second and default limit is 2000 packets.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
You can configure a rate and limit for a particular non-IP divert-code, and all packets arriving with that divert-code are sent through a single rate-limiter with the configured rate and limit. but the explanation is fairly straightforward: there is a single rate-limiter for each non-IP divert-code. No attempt is made to uniquely identify the source of the attacking packet stream.
Examples
The following example shows how to set and limit default values for the specified divert code:
Router(config)# service divert-rate-limit non-ip fib-rpf-glean rate 5 limit 25Related Commands
service divert-rate-limit ip
This command configures DRL rate and limit for WAN-side IP packet streams.
service divert-rate-limit trusted-site
To add entries to the trusted site list, use the service divert-rate-limit trusted-site command in the global configuration mode. To remove all entries from the trusted site list, use the no form of this command.
service divert-rate-limit trusted-site ip-address mask-ip-address tos tos-value mask tos-mask [global | vrf vrf-name]
no service divert-rate-limit trusted-site
Syntax Description
Command Default
No default behavior or values.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
The service divert-rate-limit ip trusted-site command is used to configure trusted site list that contains a source IP address and mask, IP ToS value and mask, and a VRF. The trusted site list contains a source IP address and mask, IP ToS value and mask, and a VRF. The trusted site list applies only to WAN-IP IPv4 packets. There is a limitation of four trusted sites.
To remove specified entry from the trusted site list, use no service divert-rate-limit trusted-site ip-address mask ip-address tos tos-value mask tos-mask [global | vrf vrf-name]. If no IP address is specified, the entire trusted site list is cleared.
Examples
The following example shows how to configure trusted site list:
Router(config)# service divert-rate-limit trusted-site 64.12.13.0 255.255.0.255tos 0xD0 mask 0xF3 vrf name1Related Commands
service divert-rate-limit non-ip
This command sets and limit default values for the specified divert code.
service udp-small-servers max-servers no-limit
To enable use of minor servers that use the UDP protocol (such as ToD, echo, chargen, and discard), use the service udp-small-servers max-servers no-limit command in global configuration mode. To remove this configuration, use the no form of this command.
service udp-small-servers max-servers no-limit
no service udp-small-servers max-servers no-limit
Command Default
DHCP or ToD servers are not configured by default.
Command Modes
Global configuration
Command History
Usage Guidelines
Disabling the ping option can speed up address assignment when a large number of modems are trying to connect at the same time. However, disabling the ping option can also result in duplicate IP addresses being assigned if users assign unauthorized static IP addresses to their CPE devices.
Examples
The following example illustrates configuration of this command:
Router# configure terminal
Router(config)# service udp-small-servers max-servers no-limit
Router(config)#
The following example shows a typical ToD server configuration:
service udp-small-servers max-servers no-limitcable time-serverThese are the only commands required to enable the ToD server.
Usage Guidelines
The max-servers no-limit option allows a large number of cable modems to obtain the ToD server at one time, in the event that a cable or power failure forces many cable modems offline. When the problem has been resolved, the cable modems can quickly reconnect.
Note
For additional information about DHCP configuration on the Cisco CMTS, refer to the following documents on Cisco.com:
•
•
Related Commands
service-class
To create a DOCSIS configuration file that specifies the quality-of-service (QoS) service-class options for the CM configuration file, use the service-class command in cable config-file configuration mode. To disable the specification, use the no form of this command.
service-class class {guaranteed-upstream us-bandwidth max-burst burst-size max-downstream max-dsbandwidth max-upstream max-usbandwidth priority priority-num privacy}
no service-class
Syntax Description
Command Default
Service-class is not set by default. A CM cannot register on a Cisco CMTS unless at least one parameter in a service class is specified.
Command Modes
Cable config-file (config-file)
Command History
Usage Guidelines
Default values can be used only if service-class class is specified. A single configuration file should not contain multiple service-class ID numbers. Thus, all parameters should be set using a single service-class ID. However, different configuration files can reuse the same service-class ID.
Note
Examples
The following example shows how to specify the service-class command for a DOCSIS configuration file:
router(config)# cable config-file upgrade.cmrouter(config-file)# service-class 1 priority 0router(config-file)# service-class 1 max-upstream 3247router(config-file)# service-class 1 max-downstream 10000router(config-file)# service-class 1 max-burst 1600router(config-file)# service-class 1 privacyrouter(config-file)# privacyrouter(config-file)# exitRelated Commands
session-range
To identify the multicast QoS group session range, use the session-range command in multicast QoS configuration mode. To disable the QoS group session range, use the no form of this command.
session-range ip-address ip-mask
no session-range ip-address ip-mask
Syntax Description
ip-address
Specifies the IP address of the multicast QoS group.
ip-mask
Specifies the IP mask of the multicast QoS group.
Command Default
A session range IP address and IP mask are not defined for a specific multicast QoS group.
Command Modes
Multicast QoS configuration (config-mqos)
Command History
Usage Guidelines
Use the session-range command to configure the session range to specify the number of multicast sessions to be admitted on a particular service flow. CMTS does not admit new sessions (no forwarding) if the current number of sessions has reached the defined limit, and waits until a session ends to free up a slot for new sessions. You can configure multiple session ranges.
Examples
The following example defines a session range IP address and IP mask using the session-range command:
Router(config)# cable multicast qos group 20 priority 55 globalRouter(config-mqos)# session-range 224.10.10.01 255.255.255.254Related Commands
set clock
To set the system clock on the Cisco CMTS, use the set clock command in global configuration mode.
set clock time-date
Syntax Description
Command Default
Time-of-Day, DHCP, and TFTP server configuration not defined on the Cisco CMTS by default.
Command Modes
Global configuration
Command History
Usage Guidelines
To supply an accurate clock, the system clock on the Cisco CMTS should be configured for the correct time, either by using the set clock command or by configuring the Cisco CMTS to act as a Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) client.
For proper operation of the DOCSIS network, especially a DOCSIS 1.1 network using BPI+ encryption and authentication, the system clock on the Cisco CMTS must be set accurately. You can achieve this by manually using the set clock command, or by configuring the CMTS to use either the Network Time Protocol (NTP) or the Simple Network Time Protocol (SNTP).
For additional information about the set clock command, refer to the following documents on Cisco.com:
•
•
Related Commands
