-
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 Commands: snmp through w
snmp-server enable traps cable
snmp-server enable traps docsis-cm
snmp-server enable traps docsis-cmts
snmp-server enable traps docsis-resil
snmp-server host traps docsis-resil
test cable dcc (Supporting Dynamic Channel Change)
test packetcable gc client-accept
test packetcable gc gate-alloc
test packetcable gc gate-delete
test packetcable gc gate-set multimedia
Cable Commands: snmp through w
Revised: May 27, 2013, OL-15510-16
New Commands
Modified Commands
snmp manager
To create a DOCSIS configuration file that specifies the IP address for the Simple Network Management Protocol (SNMP) manager, use the snmp manager command in cable config-file configuration mode. To disable this function, use the no form of this command.
snmp manager ip-address
no snmp manager
Syntax Description
Defaults
No SNMP manager is defined.
Command Modes
Cable config-file configuration (config-file)
Command History
12.1(2)EC1
This command was introduced.
12.2(4)BC1
Support was added to the Release 12.2 BC train.
Usage Guidelines
For SNMP commands that affect the operation of the CMTS, see the Cisco IOS Configuration Fundamentals Command Reference Guide.
Examples
The following example shows how to specify the IP address of the SNMP manager in a DOCSIS configuration file:
router(config)# cable config-file snmp.cmrouter(config-file)# snmp manager 10.10.1.1router(config-file)# exitrouter(config)#Related Commands
snmp-server enable traps cable
To enable the sending of Simple Network Management Protocol (SNMP) traps for cable related events, use the snmp-server enable traps cable command in global configuration mode. To disable the sending of traps, use the no form of this command.
Cisco uBR10012 Universal Broadband Router
snmp-server enable traps cable [admission_control] [cm-chover] [cm-onoff] [cm-remote-query] [dmic-lock] [enfrule-violation] [hccp-failover] [hopping] [metering] [rfswitch-polling] [sfp-link]
no snmp-server enable traps cable [admission_control] [cm-chover] [cm-onoff] [cm-remote-query] [dmic-lock] [enfrule-violation] [hccp-failover] [hopping] [metering] [rfswitch-polling] [sfp-link]
Cisco uBR7225VXR and Cisco uBR7246VXR Universal Broadband Routers
snmp-server enable traps cable [admission_control] [cm-chover] [cm-onoff] [cm-remote-query] [dmic-lock] [enfrule-violation] [hccp-failover] [hopping] [metering]
no snmp-server enable traps cable [admission_control] [cm-chover] [cm-onoff] [cm-remote-query] [dmic-lock] [enfrule-violation] [hccp-failover] [hopping] [metering]
Syntax Description
Command Default
No SNMP traps for cable-related events are enabled. You can specify one type of trap or any combination of traps. When the snmp-server enable traps cable command is given without any options, all cable-related traps are enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
For other SNMP commands that affect the operation of the CMTS, see the Cisco CMTS Universal Broadband Router Series MIB Specifications Guide.
Examples
The following example shows how to enable all traps for cable-related events except HCCP switchover on the CMTS:
Router# configure terminalRouter(config)# snmp-server enable traps cable cm-chover cm-onoff cm-remote-query hoppingRouter(config)#The following example shows how to enable traps for any HCCP switchovers that occur on the CMTS:
Router# configure terminalRouter(config)# snmp-server enable traps cable hccp-failoverRouter(config)#The following example shows how to enable traps for when a user violates the maximum bandwidth for the quality of service (QoS) profile specified by their enforce-rule.
Router# configure terminalRouter(config)# snmp-server enable traps cable enforce-ruleRouter(config)#The following example shows how to enable traps for to see the SFP port link status on the Cisco uBR10012 router
Router# configure terminalRouter(config)# snmp-server enable traps cable sfp-linkRouter(config)#Related Commands
snmp-server enable traps docsis-cm
To enable one or more Simple Network Management Protocol (SNMP) traps for DOCSIS 1.1 events, use the snmp-server enable traps docsis-cm command in global configuration mode. To disable the SNMP traps, use the no form of this command.
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
snmp-server enable traps docsis-cm [bpi | bpkm | dccack | dccreq | dccrsp | dhcp | dsack | dsreq | dsrsp | dynsa | swupcvc | swupfail | swupinit | swupsucc | tlv]
no snmp-server enable traps docsis-cm [bpi | bpkm | dccack | dccreq | dccrsp | dhcp | dsack | dsreq | dsrsp | dynsa | swupcvc | swupfail | swupinit | swupsucc | tlv]
Syntax Description
Defaults
No traps are enabled. If no options are specified, all DOCSIS-related traps are enabled.
Command Modes
Global configuration
Command History
12.2(15)CZ
This command was introduced on the Cisco uBR905 and Cisco uBR925 cable access routers, and the Cisco CVA122 Cable Voice Adapter.
Usage Guidelines
This command enables the sending of SNMP traps when DOCSIS-related events occur. Multiple traps can be enabled at the same time.
Note
The traps are described in the DOCS-CABLE-DEVICE-TRAP-MIB MIB, which is an extension of the CABLE DEVICE MIB that is defined in RFC 2669.
Examples
The following example shows the BPI+ and secure software download traps being enabled:
Router# config terminalRouter(config)# snmp-server enable traps docsis-cm bpi bpkm swupcvc swupfail swupinit swupsuccRouter(config)#Related Commands
show snmp
Checks the status of SNMP communications.
snmp-server manager
Starts the SNMP manager process.
snmp-server enable traps docsis-cmts
To enable the sending of Simple Network Management Protocol (SNMP) traps for DOCSIS-related events, use the snmp-server enable traps docsis-cmts command in global configuration mode. To disable the sending of traps, use the no form of this command.
snmp-server enable traps docsis-cmts [docsis-events]
no snmp-server enable traps docsis-cmts [docsis-events]
Syntax Description
Defaults
No SNMP traps for DOCSIS-related events are enabled. When the snmp-server enable traps docsis-cmts command is given without any options, all DOCSIS-related traps are enabled.
Command Modes
Global configuration (config)
Command History
12.1(7)CX1, 12.2(4)BC1
This command, along with the DOCS-CABLE-DEVICE-TRAP-MIB MIB, was introduced.
Usage Guidelines
This command enables traps that are defined in the DOCS-CABLE-DEVICE-TRAP-MIB MIB.
For other SNMP commands that affect the operation of the CMTS, see the Cisco IOS Configuration Fundamentals Command Reference Guide.
Examples
The following example shows how to enable traps for the failure of DOCSIS registration-related events on the CMTS:
router(config)# snmp-server enable traps docsis-cmts reqack reqreq regrsprouter(config)#Related Commands
snmp-server enable traps docsis-resil
To enable Simple Network Management Protocol (SNMP) traps for Wideband Resiliency specific events on the Cisco CMTS, use the snmp-server enable traps docsis-resil command in global configuration mode. To disable SNMP traps, use the no form of this command.
snmp-server enable traps docsis-resil [resil-events]
no snmp-server enable traps docsis-resil [resil-events]
Syntax Description
Defaults
No SNMP traps for wideband resiliency specific events are enabled. When the snmp-server enable traps docsis-resil command is given without any options, all wideband resiliency specific traps are enabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command enables traps that are defined in the CISCO-DOCS-EXT-MIB.my MIB.
For other SNMP commands that affect the operation of the Cisco CMTS, see the Cisco IOS Configuration Fundamentals Command Reference Guide.
Examples
The following example shows how to enable traps when the RF channel logical status changes to DOWN on the Cisco CMTS:
router(config)# snmp-server enable traps docsis-resil rf-downrouter(config)#Associated FeaturesThe snmp-server enable traps docsis-resil command is associated with the Wideband Modem Resiliency feature.
Related Commands
snmp-server host traps docsis-resil
To enable Wideband Resiliency trap notifications to a specific Simple Network Management Protocol (SNMP) host on the Cisco CMTS, use the snmp-server host traps docsis-resil command in global configuration mode. To disable Wideband Resiliency trap notifications to a specific SNMP host, use the no form of this command.
snmp-server host ipaddr traps string docsis-resil
no snmp-server host ipaddr traps string
Syntax Description
ipaddr
IPv4 or IPv6 address of the SNMP notification host.
string
SNMPv1 community string, SNMPv2c community string, or SNMPv3 username.
Command Default
Wideband Resiliency trap notifications are not sent to an SNMP host.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use this command to start or stop sending Wideband Resiliency traps to a specific SNMP host.
Examples
The following example shows how to enable Wideband Resiliency trap notifications to an SNMP host:
Router# configure terminalRouter(config)# snmp-server host 172.17.2.0 traps snmphost01 docsis-resilAssociated FeaturesThe snmp-server host traps docsis-resil command is associated with the Wideband Modem Resiliency feature.
Related Commands
switchover pxf restart
To configure the maximum number of PXF crashes that are allowed within a specified time period, use the switchover pxf restart command in redundancy configuration (main-cpu) mode. To reset the router to its default values, use the no form of this command.
switchover pxf restart number-of-crashes time-period
no switchover pxf restart
Syntax Description
Defaults
2 PXF crashes within 5 hours are allowed (switchover pxf restart 2 5)
Command Modes
Redundancy configuration, main-cpu mode (config-r-mc)
Command History
Usage Guidelines
The PXF processors that are onboard the PRE1 module automatically restart themselves if a crash occurs. Occasional crashes could be expected, but repeated crashes could indicate a hardware problem.
The switchover pxf restart command specifies the maximum number of times that a PXF processor can crash during a specified time period before the router switches over to the redundant PRE1 module. If the PXF processors crash this number of times, the router assumes a hardware problem and initiates a switchover to the redundant PRE1 module.
Note
C10KEVENTMGR-3-PXF_FAIL_SWITCHOVER: Multiple PXF failures, switchover to redundant PRE initiated.
Examples
The following example shows how to configure the router so that if five PXF crashes occur within a one-hour period, the router should initiate a switchover to the redundant PRE1 module.
Router# config tRouter(config)# redundancyRouter(config-r)# main-cpuRouter(config-r-mc)# switchover pxf restart 5 1Router(config-r-mc)# exitRouter(config-f)# exitRouter(config)#Related Commands
switchover timeout
To configure the switchover timeout period of the PRE1 module, use the switchover timeout command in redundancy configuration (main-cpu) mode. To reset the timeout period to its default value, use the no form of this command.
switchover timeout timeout-period
no switchover timeout
Syntax Description
timeout-period
Specifies the timeout, in milliseconds. The valid range is 0 to 25000 milliseconds (25 seconds), where 0 specifies no timeout period.
Defaults
The default is 0.
Command Modes
Redundancy configuration, main-cpu mode
Command History
Usage Guidelines
The switchover timeout command specifies how long the standby PRE module should wait when it does not detect a heartbeat from the active PRE module before initiating a switchover and assuming responsibility as the active PRE module. If set to 0, the standby PRE module initiates a switchover immediately when the active PRE module misses a scheduled heartbeat.
Examples
The following example shows how to set the timeout period to 60 milliseconds:
Router# config tRouter(config)# redundancyRouter(config-r)# main-cpuRouter(config-r-mc)# switchover timeout 60Router(config-r-mc)# exitRouter(config-f)# exitRouter(config)#Related Commands
tag
To add a tag to a restricted load balancing group (RLBG), use the tag command in the config-lb-group configuration mode. To remove the tag, use the no form of this command.
tag tag-name
no tag tag-name
Syntax Description
Command Default
No default behavior or values.
Command Modes
DOCSIS load balancing group mode (config-lb-group)
Command History
Usage Guidelines
You can use the tag command to add a tag to a RLBG, only if the tag is already created using the cable tag command for the DOCSIS load balancing group on the CMTS.
Examples
The following example shows how to add a tag to a RLBG using the tag command.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# cable load-balance docsis-group 1Router(config-lb-group)# restrictedRouter(config-lb-group)# tag CSCORouter(config-lb-group)#Related Commands
test cable dcc (Supporting Dynamic Channel Change)
To move a specified cable modem or a group of cable modems to another channel, or to test Dynamic Channel Change (DCC) for load balancing on the Cisco CMTS, use the following command in privileged EXEC mode.
test cable dcc {source-interface [cable slot/subslot/cable-interface-index | integrated-cable slot/subslot/cable-interface-index | modular-cable slot/subslot/cable-interface-index] | sid | ip-addr | mac-addr | frequency frequency}
{destination-interface [cable slot/subslot/cable-interface-index | integrated-cable slot/subslot/cable-interface-index | modular-cable slot/subslot/cable-interface-index] upstream-port}
{init-tech | force | tlv}Syntax Description
Command Default
Test functions are disabled by default.
Command Modes
Privileged EXEC (#)
Command History
Examples
The following examples illustrate DCC verification, using the test cable dcc command.
The following example shows how to move a target cable modem, specified by MAC address, IP address, or the primary SID value on the source interface to a target downstream with the specified frequency using DCC intialization technique 0:
Router# test cable dcc [<mac-addr>|<ip-addr>|<cable-if-src><sid>] frequency <freq-value>Frequency-value: <55000000-858000000> New Downstream Frequency in HZ.The following example shows how to move a target cable modem, specified by MAC address, IP address, or the primary SID value on the source interface to a upstream channel on a target downstream with the DCC-REQ TLV given in the specified HEX data.
Router# test cable dcc [<mac-addr>|<ip-addr>|<cable-if-src><sid>] TLV <Hex-data>The following example shows how to move all cable modems on a source interface to a target downstream with the specified frequency using DCC intialization technique 0.
Router# test cable dcc <cable-if-src> frequency <frequency-value>Frequency-value: <55000000-858000000> New Downstream Frequency in HZ.The following example shows how to force a cable modem to move to a modular-cable interface 7/0/0:2 with init-tech set to 0:
Router# test cable dcc 0023.4ed0.db25 modular-Cable 7/0/0:0 0 0 forceRouter# show cable modem 0023.4ed0.db25Load for five secs: 1%/0%; one minute: 1%; five minutes: 1%Time source is hardware calendar, *10:00:48.167 SGT Wed Nov 16 2011DMAC Address IP Address I/F MAC Prim RxPwr Timing Num IState Sid (dBmv) Offset CPE P0023.4ed0.db25 30.11.2.118 C7/0/0/U0 offline 19 0.50 1862 0 NUsage Guidelines
This command is subject to the restrictions and prerequisites described in Load Balancing, Dynamic Channel Change, and Dynamic Bonding Change on the Cisco CMTS Routers.
The Cisco CMTS does not support the force option for test cable dcc tlv command where tlv is a HEXDATA node.
Related Commands
test cable voice
To manually set voice tag of a cable modem, use the test cable voice command in privileged EXEC mode.
test cable voice {mac-addr | ip-addr}
Syntax Description
Command Default
No voice tags are enabled
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The test cable voice command is intended for use by Cisco Systems technical support personnel.
Examples
The following example shows how to enable the voice tag of a cable modem:
Router# test cable voice 209.165.200.225Related Commands
show cable modem voice
Displays the detected voice-enabled modems.
clear cable modem voice
Clears the voice tag that is set for a cable modem.
test packetcable gate create
To create a test PacketCable or PCMM gate, use the test packetcable gate create command in privileged EXEC mode. The number of requested gates is created with the subscriber address, which must be specified. The gates created with this command are used by other test commands, such as gate-info or gate-delete, to test functionality.
test packetcable gate create subscriber addr [dqos | multimedia] [ # of gates ]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS.
Related Commands
test packetcable gc client-accept
To send a client-accept request to a Packetcable or PCMM Call Management Server (CMS), and to initiate a session with that server, use the test packetcable gc client-accept command in Privileged EXEC mode.
test packetcable gc client-accept
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS. The CMS-to-client session that starts as a result of using this command can be viewed with multiple show, debug and test commands.
Examples
The following example illustrates a test client-accept request:
Router# test packetcable gc client-acceptRelated Commands
test packetcable gc gate-alloc
To send a gate allocation message to the Packetcable DQoS processor, use the test packetcable gc gate-alloc command in privileged EXEC mode. This test message generates from the gate controller that is specified by the GC address value. The gate is allocated for the subscriber address specified in the command.
test packetcable gc gate-alloc gc-addr subscriber-addr
Syntax Description
gc-addr
IP address for the gate controller to test.
subscriber-addr
IP address for the subscriber to test.
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS.
Related Commands
test packetcable gc gate-delete
To send a gate-delete request to either the Packetcable Multimedia or PC DQoS message processor, use the test packetcable gc gate-delete command in privileged EXEC mode. The request includes the subscriber ID and gate ID specified in the command. The message is sent to either the DQoS or PCMM processor depending on the type of server that was used when the GC address was added.
test packetcable gc gate-delete gc-addr subscriber-id gate-id
Syntax Description
gc addr
IP address of the gate controller.
subscriber-id
The subscriber identifier to be inserted into the gate-set message.
gate-id
Gate identifier for the gate that generates the test message.
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS.
Related Commands
test packetcable gc gate-info
To send a gate information request to the Packetcable Multimedia message processor, as if originating from the gate controller address specified, use the test packetcable gc gate-info command in privileged EXEC mode. The gate ID must be specified when using this command.
test packetcable gc gate-info gc-addr gate-id
Syntax Description
gc addr
IP address of the gate controller.
gate-id
Gate identifier for the gate that generates the test message.
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS.
Related Commands
test packetcable gc gate-set multimedia
To send a test gate-set request to the Packetcable Multimedia message processor, as if it comes from the gate controller, use the test packetcable gc gate-set multimedia command in privileged EXEC mode.
The gate ID, subscriber ID, gate state and traffic profile information are included in the test gate-set message. Other traffic profile information, like traffic profile details, display static values by default.
test packetcable gc gate-set gc-addr multimedia subscriber-id state gate-id traffic-type service-class-name
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was introduced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PCMM on the Cisco CMTS.
Related Commands
test packetcable gc initiate
To add a test Call Management Server (CMS) for either PacketCable (DQoS) or PCMM, use the test packetcable gc initiate command in privileged EXEC mode.
test packetcable gc initiate [dqos | multimedia] GC-IP
Syntax Description
dqos
(Optional) Specifies a PacketCable Dynamic Quality of Service (DQoS) CMS.
multimedia
(Optional) Specifies a PCMM CMS.
GC-IP
IP address of the gate controller.
Command Modes
Privileged EXEC (#)
Command History
12.3(13a)BC
This command was enhanced to support PCMM on the Cisco uBR10012 router and the Cisco uBR7246VXR router.
Usage Guidelines
This command is supported for PC or PCMM on the Cisco CMTS. The type of CMS added determines the type of gate that is created. This gate type is used in all future PacketCable test commands that use the gate controller address specified.
Related Commands
threshold
To specify the load limit beyond which load balancing occurs, use the threshold command in the config-lb-group configuration mode. To remove the specified load limit, use the no form of this command.
threshold {load {minimum 1-100 | 1-100} | pcmm 1-100 | stability 0-100 | ugs 1-100}
no threshold {load {minimum | 1-100} | pcmm 1-100 | stability 0-100 | ugs 1-100}
Syntax Description
Command Default
No default behavior or values.
Command Modes
DOCSIS load balancing group mode (config-lb-group)
Command History
Examples
The following example shows how to configure the threshold of the DOCSIS LBG using the threshold command.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# cable load-balance docsis-group 1Router(config-lb-group)# threshold load minimum 10Router(config-lb-group)#Related Commands
timestamp
To create a DOCSIS configuration file that enables timestamp generation, use the timestamp command in cable config-file configuration mode. To disable this function, use the no form of this command.
timestamp
no timestamp
Syntax Description
This command has no arguments or keywords.
Command Default
No default behaviors or values
Command Modes
Cable config-file configuration (config-file)
Command History
12.1(2)EC1
This command was introduced.
12.2(4)BC1
Support was added to the Release 12.2 BC train.
Usage Guidelines
The DOCSIS specification supports the optional time-stamping of DOCSIS configuration files by adding a field to the file that shows the time that the file was sent to the CM. This prevents someone from trying to subvert DOCSIS security by replaying a valid DOCSIS configuration file to another CM. The timestamp is expressed as the number of seconds since midnight on January 1, 1900.
Examples
The following example shows how to enable timestamp generation for the DOCSIS configuration file.
router(config)# cable config-file upgrade.cmrouter(config-file)# timestamprouter(config-file)# exitrouter(config)#Related Commands
tlv
To configure a TLV type tag matching rule, use the tlv command in CMTS-tag configuration mode.
tlv type value
Syntax Description
Command Default
None
Command Modes
CMTS tag configuration mode (config-cmts-tag).
Command History
Examples
The following example shows how to configure the tlv command:
Router# enableRouter(config)# cable tag 1Router(config-cmts-tag)# tlv mrcs 3Related Commands
tos
To configure the Type of Service (ToS) byte in the header of Layer 2 tunneled packets, use the tos command in DEPI tunnel configuration mode. To disable a configured ToS value, use the no form of this command.
tos value
no tos value
Syntax Description
value
Value of the ToS byte for IP packets in a Layer 2 Tunnel Protocol version 3 (L2TPv3) data session. The valid values range from 0 to 255. The default value is 0.
Command Default
None
Command Modes
DEPI tunnel configuration
Command History
Usage Guidelines
The tos command allows you to manually configure the value of the ToS byte used in the headers of Layer 2 tunneled packets.
Examples
The following example shows how to assign a ToS value of 100:
Router# configure terminalRouter(config)# depi-tunnel rf6Router(config-depi-tunnel)# tos 100Related Commands
depi-tunnel
Specifies the name of the depi-tunnel and enters the DEPI tunnel configuration mode.
tos (multicast qos)
To set type of service (ToS) low byte, high byte, and mask values within a multicast QoS group, use the tos command in multicast QoS configuration mode. To disable the type of service, use the no form of this command.
tos low-byte high-byte mask
no tos low-byte high-byte mask
Syntax Description
Command Default
ToS parameters are not defined for a specific multicast QoS group.
Command Modes
Multicast QoS configuration (config-mqos)
Command History
Usage Guidelines
The three precedence bits in the ToS byte in the IP header specifies a class of service assignment for each packet. Those packets with the precedence bit set in the ToS field are given higher priority.
Examples
The following example defines the low and high ToS rates and the mask value using the tos command:
Router(config)# cable multicast qos group 20 priority 55 globalRouter(config-mqos)# tos 1 6 15Related Commands
upgrade fpga auto-upgrade
To perform a firmware Field-Programmable Gate Array (FPGA) automatic upgrade on the PRE4 module on the Cisco uBR10012 router, use the upgrade fpga auto-upgrade command in privileged EXEC mode.
upgrade fpga auto-upgrade {debug-off | debug-on | disable | enable | show}
Syntax Description
Command Default
FPGA auto upgrade is enabled by default.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The FPGA auto upgrade feature enables automatic upgrade of the FPGA image on the PRE4 module on the Cisco uBR10012 router. To disable auto upgrade of the FPGA, use the upgrade fpga auto-upgrade disable command.
Examples
The following example shows how to activate the FPGA debugging on the Cisco uBR10012 router:
Router# upgrade fpga auto-upgrade debug-onRouter#The following example shows how to disable automatic upgrade of the FPGA firmware on the Cisco uBR10012 router:
Router# upgrade fpga auto-upgrade disableThe following example shows how to display the FPGA version, which is the FPGA in the flash on the PRE4 module:
Router# upgrade fpga auto-upgrade showAlternative IOFPGA Running, version - 0x05111800Default IOFPGA version - 0x00000000Alternative IOFPGA version - 0x00000000Bundle IOFPGA version - 0x0A0A0D01IOFPGA auto-upgrade enabled - NoIOFPGA auto-upgrade debug - NoIOFPGA auto-upgrade test mode - (Default IOFPGA:flash image verify error)Table 254 describes the significant fields shown in the display.
Associated FeaturesThe upgrade fpga auto-upgrade command is used to automatically upgrade of the FPGA on the PRE4 module on the Cisco uBR10012 router.
•
Related Commands
upgrade fpga file
Upgrades the FPGA on the PRE4 module on the Cisco uBR10012 router.
upgrade fpga file
To upgrade the Field-Programmable Gate Array (FPGA) image on the Performance Routing Engine 4 (PRE4) module on the Cisco uBR10012 router, use the upgrade fpga file command in privileged EXEC mode.
upgrade fpga {alt | def} file {url}{version}
Syntax Description
alt
Specifies the alternative IOFPGA version.
def
Specifies the default IOFPGA version.
url
URL of the IOFPGA file.
version
Version of the IOFPGA file.
Command Default
FPGA is disabled by default.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SCB
This command was introduced.
12.2(33)SCG
This command is modified. The argument version is added to the command.
Usage Guidelines
Use this command to upgrade the FPGA image on the PRE4 module on the Cisco uBR10012 router.
Note
If you are using a PRE4 VE board and running Cisco IOS Release 12.2(33)SCG, use the upgrade fpga {alt | def} file {url} command to upgrade the PRE4 module.
Examples
The following example shows how to upgrade the FPGA on the Cisco uBR10012 router:
Router# upgrade fpga alt file disk0:pre4_iofpga.bin 0x0A0A0D01Associated FeaturesThe upgrade fpga file command is used to manually upgrade the FPGA on the PRE4 module on the Cisco uBR10012 router. For more information, see
•
Related Commands
upgrade fpga auto-upgrade
Performs automatic upgrade of the IOFPGA on the PRE4 module on the Cisco uBR10012 router.
upstream
To add upstream channels to an upstream bonding group, use the upstream command in upstream bonding configuration submode. To disable this configuration, use the no form of this command.
upstream number
no upstream number
Syntax Description
Command Default
None
Command Modes
Upstream bonding configuration submode (config-upstream-bonding)
Command History
Usage Guidelines
DOCSIS 3.0-certified cable modems can support only four upstream channels on an upstream bonding group. These cable modems cannot accept additional upstream channels that you have added to an upstream bonding group.
Examples
The following example shows how to add upstream channels to an upstream bonding group on a cable interface line card on a Cisco uBR10012 router:
Router# configure terminalRouter(config)# interface cable7/1/0Router(config-if)# cable upstream bonding-group 20Router(config-upstream-bonding)# upstream 0Router(config-upstream-bonding)# upstream 1Router(config-upstream-bonding)# upstream 2Router(config-upstream-bonding)# upstream 3Related Commands
cable upstream bonding-group
Creates an upstream bonding group on a cable interface.
cable fiber-node
Creates a fiber node and enters cable fiber-node configuration mode.
upstream (config-lb-group)
To set upstream channels in a DOCSIS load balancing group, use the upstream command in the config-lb-group configuration mode. To disable the upstream channel configuration, use the no form of this command.
Cisco uBR10012 Router
upstream cable slot/subslot/port upstream-list
no upstream cable slot/subslot/port upstream-list
Cisco uBR7225VXR and Cisco uBR7246VXR Routers
upstream cable slot/port upstream-list
no upstream cable slot/port upstream-list
Syntax Description
Command Default
None
Command Modes
DOCSIS load balancing group mode (config-lb-group)
Command History
Examples
The following example shows how to set upstream channels in a DOCSIS LBG using the upstream command.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# cable load-balance docsis-group 1Router(config-lb-group)# upstream cable 1/0/1 2Router(config-lb-group)#Related Commands
upstream cable connector
To configure an upstream cable connector for a fiber node, use the upstream cable connector command in cable fiber node configuration mode. To disable the configuration, use the no form of this command.
Cisco uBR10012 Router
upstream cable slot/subslot connector port-number
no upstream cable slot/subslot connector port-number
Cisco uBR7225VXR and Cisco uBR7246VXR Routers
upstream cable slot connector port-number
no upstream cable slot connector port-number
Syntax Description
Command Default
None
Command Modes
Cable fiber node configuration (config-fiber-node)
Command History
12.2(33)SCC
This command was introduced in Cisco IOS Release 12.2(33)SCC.
12.2(33)SCD
Added support for Cisco uBR7246VXR and Cisco uBR7225VXR routers.
Examples
The following example shows how to configure an upstream cable connector for a fiber node on a Cisco uBR10012 router:
Router# configure terminalRouter(config)# cable fiber-node 2Router(config-fiber-node)# upstream cable 5/0 connector 2Related Commands
upstream freq-range
To configure the Cisco CMTS router for the range of frequencies that are acceptable on upstreams, use the upstream freq-range command in global configuration mode. To restore the default value of North American ranges, use the no form of this command.
upstream freq-range [european | japanese | north american]
no upstream freq-range
Syntax Description
Defaults
North American (DOCSIS, 5 MHz to 42 MHz)
Command Modes
Global configuration
Command History
12.2(15)BC2
This command was introduced for the Cisco uBR7246VXR and Cisco uBR10012 universal broadband routers.
Usage Guidelines
In Cisco IOS Release 12.2(15)BC2 and later, the Cisco CMTS router supports three different modes of operation, depending on the cable interface line cards being used. The range of frequencies that are allowed in each mode are as follows:
•
•
•
To configure the router so that it supports the proper range of upstream frequencies, use the upstream freq-range command. After you have configured the router with the upstream freq-range command, the cable upstream frequency command then accepts only frequencies that are in the configured range.
Note
The allowable range for the upstream channel frequency depends on the cable interface line card and Cisco IOS software release being used. See Table 2-12 on page 2-367 for the currently supported values.
Examples
The following example shows how to configure the Cisco CMTS router to support the EuroDOCSIS upstream frequency range of 5 MHz to 65 MHz:
Router# configure terminalRouter(config)# upstream freq-range europeanRouter(config)#The following example shows how to configure the Cisco CMTS router to support the expanded Japanese upstream frequency range of 5 MHz to 55 MHz:
Router# configure terminalRouter(config)# upstream freq-range japaneseRouter(config)#The following example shows how to configure the Cisco CMTS router for its default configuration (DOCSIS upstream frequency range of 5 MHz to 42 MHz):
Router# configure terminalRouter(config)# upstream freq-range north americanRouter(config)#The following example shows all of the commands that are needed to configure the cable interface and upstream on a Cisco uBR-MC28U/X cable interface line card to support a frequency in the EuroDOCSIS upstream frequency range of 5 MHz to 65 MHz:
Router# configure terminalRouter(config)# upstream freq-range europeanRouter(config)# interface 3/0Router(config-if)# cable downstream annex aRouter(config-if)# cable upstream 0 frequency 62500000Router(config-if)#Related Commands
voice-port
To enter voice-port configuration mode, use the voice-port command in global configuration mode.
Cisco uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
voice-port number
Syntax Description:
number
Identifies the voice port. Valid entries are 0 (which corresponds to the RJ-11 connector labeled V1) and 1 (which corresponds to the RJ-11 connector labeled V2).
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the voice-port global configuration command to enter voice-port configuration mode. Use the exit command to exit the voice-port configuration mode and return to the global configuration mode. See the Cisco IOS Multiservice Applications Command Reference, available on Cisco.com and the Documentation CD-ROM for a list of subcommands that are supported by the voice-port command.
Examples
The following example shows how to enter the voice-port configuration mode for port 0, the first voice port (labeled "V1+V2") on the router.
Router# configure terminalRouter(config)# voice-port 0Router(config-voice-port)#Related Commands
dial-peer voice
Enters dial-peer configuration mode, defines the type of dial peer, and defines the tag number associated with a dial peer.
vrf (multicast qos)
To specify the name for a virtual routing and forwarding (VRF) instance, use the vrf command in multicast QoS configuration mode. To disable the VRF instance, use the no form of this command.
vrf name
no vrf name
Syntax Description
name
Specifies the routing and forwarding instance that is populated with multicast Virtual Private Network (MVPN) routes.
Command Default
A VRF name is not defined for the multicast QoS group.
Command Modes
Multicast QoS configuration (config-mqos)
Command History
Usage Guidelines
If a multicast QoS (MQoS) group is not defined for the named VRF instance, you will see an error message. You must either define a specific MQoS group for each VRF instance, or define a default MQoS that can be assigned in those situations where no matching MQoS group is found.
Examples
The following example identifies a multicast QoS group VRF name using the vrf command:
Router(config)# cable multicast qos group 20 priority 55 globalRouter(config-mqos)# vrf name1Related Commands
weekend duration
To configure different subscriber monitoring options over weekends on a Cisco CMTS router, use the weekend duration command in enforce-rule configuration mode. To remove the weekend monitoring configuration and to return to the same monitoring conditions for all days of the week, use the no weekend form of this command.
weekend duration minutes avg-rate rate sample-interval interval [penalty duration] {downstream | upstream} [enforce]
no weekend duration minutes avg-rate rate sample-interval interval [penalty duration] {downstream | upstream} [enforce]
no weekend
Syntax Description
Command Default
Weekend monitoring is disabled.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
12.3(23)BC2
This command was introduced.
12.2(33)SCD2
The penalty keyword option was added.
Usage Guidelines
Note
The weekend duration command works similarly to the duration command for subscriber traffic monitoring. Use the weekend duration command when you want to configure different monitoring parameters for subscribers on weekends.
This command can only be used when you have already configured the duration or peak-time1 commands as weekday monitoring conditions for an enforce-rule.
If you still want to monitor traffic over the weekend, but want to return to the same monitoring conditions for every day of the week, use the no weekend command. This command removes the weekend monitoring conditions, but still performs monitoring over the weekends according to the other monitoring options that you have configured in the enforce-rule.
If you want to disable monitoring entirely over the weekend, use the weekend off command.
The penalty duration, which is configured using the weekend duration command, is unique to weekends, and takes precedence over the global penalty duration configured using the penalty-period command.
Examples
The following example specifies automatic monitoring of upstream traffic over the weekend if a subscriber is identified as violating their QoS profile. The monitoring will take place every 10 minutes and last for 5 minutes, with traffic sampled at an average rate of 2 kb/s:
Router(enforce-rule)# weekend duration 5 avg-rate 2 sample-interval 10 penalty 11 upstream enforceRelated Commands
weekend off
To disable peak and offpeak monitoring on weekends on a Cisco CMTS router, use the weekend off command in enforce-rule configuration mode. To re-enable the configuration for weekend monitoring, use the no form of this command.
weekend off
no weekend off
Syntax Description
This command has no arguments or keywords.
Command Default
Weekend monitoring is enabled once you configure the weekend duration or weekend peak-time1 commands.
Command Modes
Enforce-rule configuration (enforce-rule)
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
Use the weekend off command to disable previously configured weekend monitoring and stop the CMTS router from monitoring cable modems (CMs) with that enforce-rule over the weekend. This command allows you to retain or modify your weekend monitoring configuration without enabling it for actual monitoring use on the CMTS router.
To perform weekend monitoring according to the same parameters used for weekday monitoring, use the no weekend command.
Examples
The following example shows how to disable weekend monitoring when weekend peak-time monitoring has previously been configured on a Cisco CMTS router:
Router(config)# cable qos enforce-rule testRouter(enforce-rule)# weekend peak-time1 8 duration 60 avg-rate 100 peak-time2 20 duration 60 avg-rate 10000 duration 90 avg-rate 20000 sample-interval 20 downstream enforceRouter(enforce-rule)# weekend offRelated Commands
weekend peak-time1
To configure peak and offpeak subscriber monitoring over weekends on a Cisco CMTS router, use the weekend peak-time1 command in enforce-rule configuration mode. To remove the peak and offpeak weekend monitoring configuration, use the no form of this command.
weekend peak-time1{hour| hour:minutes} duration minutes avg-rate rate [peak-time2 {hour| hour:minutes} duration minutes avg-rate rate] [duration offpeak-minutes avg-rate offpeak-rate] sample-interval minutes [penalty minutes] {downstream | upstream}[enforce]
no weekend peak-time1 {hour| hour:minutes}duration minutes avg-rate rate [peak-time2 {hour| hour:minutes} duration minutes avg-rate rate][duration offpeak-minutes avg-rate offpeak-rate] sample-interval minutes [penalty minutes] {downstream | upstream}[enforce]
Syntax Description
Command Default
Weekend monitoring is disabled. The only default value for the weekend peak-time1 command is the 15-minute sample interval.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
Note
The weekend peak-time1 command is similar to the peak-time1 command for subscriber traffic monitoring. Use the weekend peak-time1 command when you want to configure different peak and offpeak monitoring parameters for subscribers on weekends.
This command can only be used when you have already configured the duration or peak-time1 commands as weekday monitoring conditions for an enforce-rule.
The penalty duration, which is configured using the weekend peak-time1 command, is unique to weekends, and takes precedence over the global penalty duration configured using the penalty-period command.
Examples
The following example shows configuration of two peak monitoring windows on the weekend, with the first monitoring period beginning at 8:00 A.M. for one hour and the second monitoring period beginning at 8:00 P.M. for one hour, and monitoring at all other times of the weekend for 1-1/2 hours (90 minutes) for downstream traffic. The unique penalty period for both weekend peaktime1 and peaktime2 is configured as 60 minutes:
Router(enforce-rule)# weekend peak-time1 8 duration 60 avg-rate 10000 peak-time2 20 duration 60 avg-rate 100 duration 90 avg-rate 20000 sample-interval 20 penalty 60 downstream enforceRelated Commands
