-
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
ip dhcp relay information option
ipdr session (global configuration)
packetcable authorize vanilla-docsis-mta
packetcable gate send-subscriberID
Cable Commands: i through p
Revised: March 30, 2009, OL-15510-09
New Commands
Modified Commands
interface cable
To configure a cable interface, use the interface cable command in global configuration mode. To disable this configuration, use the no form of this command.
interface cable slot/subslot/port
no interface cable slot/subslot/port
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to configure a cable interface in slot 8, subslot 0, and port 0 on a Cisco uBR10012 router:
Router# configure terminalRouter(config)# interface cable 8/0/0Related Commands
interface modular-cable
Specifies a modular cable interface.
interface wideband-cable
Specifies a wideband cable interface.
interface cable-modem
To enter interface configuration mode for the cable interface on a router, use the interface cable-modem command in global configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
interface cable-modem number
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
When this command is entered, the router switches from global configuration mode to interface configuration mode.
Examples
The following example shows how to enter interface configuration mode for the router's cable interface and then to enter the available interface configuration commands:
Router(config)# interface cable-modem 0Router(config-if)# cable-modem ?compliant Enter compliant modes for interfacedownstream Downstream channel characteristicsfast-search Enable/disable the DS fast searchupstream upstream channel characteristicsvoip Options for Voice over IP traffic over the cable interfaceRouter(config-if)#Related Commands
interface gigabitethernet
The interface gigabitethernet command is now documented as the gigabitethernet keyword of the interface command. For more information, see the interface command.
interface modular-cable
To configure a modular cable interface, use the interface modular-cable command in global configuration mode. To disable this configuration, use the no form of this command.
Cisco IOS Releases 2.3(21)BC, 12.3(23)BC, and 12.2(33)SCA
interface modular-cable slot/subslot/bay:nb-channel-number
no interface modular-cable slot/subslot/bay:nb-channel-number
Cisco IOS Release 12.2(33)SCB
interface modular-cable slot/bay/port:nb-channel-number
no interface modular-cable slot/bay/port:nb-channel-number
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to configure a modular cable interface in slot 1, bay 0, and port 0 on a Cisco uBR10012 router:
Router# configure terminalRouter(config)# interface modular-cable 1/0/0:0Related Commands
interface port-channel
To create an EtherChannel interface on the Cisco Cable Modem Termination System (CMTS), use the interface port-channel command in global configuration mode. To remove this EtherChannel port from the Cisco CMTS, use the no form of this command.
interface port-channel n
no interface port-channel n
Syntax Description
number
Identifying port channel number for this interface (EtherChannel port). The range is 1 to 64.
Command Default
By default, EtherChannel groups and ports are not defined, and they are disabled (off mode) configured.
Command Modes
Global configuration
Command History
12.2(11)BC3
This command was introduced on the Cisco uBR7246VXR router.
12.2(9a)BC
This command was introduced on the Cisco uBR10012 router.
Usage Guidelines
The first EtherChannel interface configured becomes the bundle master for all EtherChannel interfaces in the group. That is, the MAC address of the first EtherChannel interface is the MAC address for all EtherChannel interfaces in the group. If the first EtherChannel interface is later removed, the second EtherChannel interface to be configured becomes the bundled master by default.
Repeat this configuration on every EtherChannel port to be bundled into a FastEtherChannel (FEC) or GigabitEtherChannel (GEC) group. This configuration must be present on all EtherChannel interfaces before the EtherChannel group can be configured.
For additional information about using the EtherChannel feature on the Cisco CMTS, refer to the following document on Cisco.com:
•
EtherChannel for the Cisco CMTS
Examples
The following example configures the port to have an EtherChannel port number of 1 within its EtherChannel group. The EtherChannel group is defined with the channel-group command.
Router(config-if)# interface port-channel 1Related Commands
interface usb
To enter the interface configuration mode for the Universal Serial Bus (USB) interface, use the interface usb command in global configuration mode.
Cisco uBR925 cable access router, Cisco CVA122 Cable Voice Adapter
interface usb number
Syntax Description
Command Default
Disabled
Command Modes
Global configuration
Command History
12.1(5) XU1
This command was introduced for the Cisco CVA122 Cable Voice Adapter.
12.2(2)XA
Support was added for the Cisco uBR925 cable access router.
Usage Guidelines
When this command is entered, the router switches from global configuration mode to interface configuration mode for the USB interface.
Examples
The following example shows how to enter interface configuration mode for the USB interface and then to display the available commands:
Router(config)# interface usb 0
Router(config-if)#?
Interface configuration commands:
access-expression Build a bridge boolean access expression
arp Set arp type (arpa, probe, snap) or timeout
bandwidth Set bandwidth informational parameter
bridge-group Transparent bridging interface parameters
carrier-delay Specify delay for interface transitions
cdp CDP interface subcommands
crypto Encryption/Decryption commands
custom-queue-list Assign a custom queue list to an interface
default Set a command to its defaults
delay Specify interface throughput delay
description Interface specific description
exit Exit from interface configuration mode
fair-queue Enable Fair Queuing on an Interface
h323-gateway Configure H323 Gateway
help Description of the interactive help system
hold-queue Set hold queue depth
ip Interface Internet Protocol config commands
keepalive Enable keepalive
load-interval Specify interval for load calculation for an
interface
logging Configure logging for interface
mac-address Manually set interface MAC address
max-reserved-bandwidth Maximum Reservable Bandwidth on an Interface
mtu Set the interface Maximum Transmission Unit (MTU)
no Negate a command or set its defaults
ntp Configure NTP
priority-group Assign a priority group to an interface
random-detect Enable Weighted Random Early Detection (WRED) on an
Interface
service-policy Configure QoS Service Policy
shutdown Shutdown the selected interface
snmp Modify SNMP interface parameters
standby Interface HSRP configuration commands
timeout Define timeout values for this interface
traffic-shape Enable Traffic Shaping on an Interface or
Sub-Interface
transmit-interface Assign a transmit interface to a receive-only
interface
tx-ring-limit Configure PA level transmit ring limit
Router(config-if)#Related Commands
show controllers usb
Displays the high-level controller information for the USB interface.
show interfaces usb
Displays configuration information about the USB interface.
interface wideband-cable
To configure a wideband cable interface, use the interface wideband-cable command in global configuration mode. To disable this configuration, use the no form of this command.
Cisco IOS Releases 12.3(21)BC, 12.3(23)BC, and 12.2(33)SCA
interface wideband-cable slot/subslot/bay:wideband-channel
no interface wideband-cable slot/subslot/bay:wideband-channel
Cisco IOS Release 12.2(33)SCB
interface wideband-cable slot/bay/port:wideband-channel
no interface wideband-cable slot/bay/port:wideband-channel
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Examples
The following example shows how to configure a wideband cable interface in slot 1, bay 0, and port 0 on a Cisco uBR10012 router:
Router# configure terminalRouter(config)# interface wideband-cable 1/0/0:0Related Commands
ip-address (controller)
To set the IP address of the Wideband SPA FPGA, use the ip-address (controller) command in controller configuration mode. To remove the IP address of the Wideband SPA FPGA, use the no form of this command.
ip-address ip-address
no ip-address ip-address
Syntax Description
Command Default
No IP address is set for the Wideband SPA FPGA.
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
Use this command to set the IP address for the Wideband SPA FPGA. This address is used as the source IP address for packets that the Wideband SPA transmits to the EQAM device.
Examples
The following example shows how to set the IP address of the Wideband SPA FPGA. The SPA is located in slot 1, subslot 0, bay 0.
Router(config)# controller modular-cable 1/0/0Router(config-controller)# ip-address 192.168.200.6Related Commands
ip accounting mac-address
To enable IP accounting on a LAN interface based on the source and destination Media Access Control (MAC) address, use the ip accounting mac-address command in interface configuration mode. To disable IP accounting based on the source and destination MAC address, use the no form of this command.
ip accounting mac-address {input | output}
no ip accounting mac-address {input | output}
Syntax Description
input
Performs accounting based on the source MAC address on received packets.
output
Performs accounting based on the destination MAC address on transmitted packets.
Defaults
Disabled
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This feature is supported on Ethernet, Fast Ethernet, and FDDI interfaces.
To display the MAC accounting information, use the show interface mac EXEC command.
MAC address accounting provides accounting information for IP traffic based on the source and destination MAC address on LAN interfaces. This calculates the total packet and byte counts for a LAN interface that receives or sends IP packets to or from a unique MAC address. It also records a timestamp for the last packet received or sent. With MAC address accounting, you can determine how much traffic is being sent to and/or received from various peers at NAPS/peering points.
Examples
The following example enables IP accounting based on the source and destination MAC address for received and transmitted packets:
interface ethernet 4/0/0ip accounting mac-address inputip accounting mac-address outputCisco uBR10012 Universal Broadband Router
The following example enables IP accounting based on the source MAC address for received packets on a Gigabit Ethernet interface:
Router#configure terminalRouter(config)#interface GigabitEthernet3/0/0Router(config-if)#ip accounting mac-address inputRelated Commands
show interface mac
Displays MAC accounting information for interfaces configured for MAC accounting.
ip address docsis
To specify that the cable access router should use the DHCP protocol, as required by the DOCSIS specification, to assign an IP address for its cable interface, use the ip address docsis command in cable interface configuration mode. To disable the use of DHCP, use the no form of this command.
Cisco uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
ip address docsis
no ip address docsis
Syntax Description
There are no key words or arguments for this command.
Command Default
The cable access router uses the DHCP protocol, as required by the DOCSIS specification, to assign an IP address to its cable interface during system power-on.
Command Modes
Interface configuration (cable interface only)
Command History
Usage Guidelines
The ip address docsis command configures the cable access router so that it obtains its IP address from a DHCP server at system power-on, which is a requirement for DOCSIS operation. This is the default mode of operation. If the configuration for the cable interface does not include any form of ip address command, the cable access router defaults to configuring the cable interface with the ip address docsis command.
Configuring the cable interface with any other form of the ip address command or with the no ip address docsis command prevents the cable access router from operating in DOCSIS networks. This mode of operation should be used only in lab or test networks.
Note
Examples
The following example shows how to configure the cable access router so that it obtains the IP address for its cable interface from a DHCP server:
Router(config)# interface cable-modem 0Router(config-if)# ip address docsisRouter(config-if)# exitRouter(config)#Related Commands
ip dhcp ping packet 0
To instruct the DHCP server to assign an IP address from its pool without first sending an ICMP ping to test whether a client is already currently using that IP address, use the ip dhcp ping packet 0 command in global configuration mode. Use the no form of this command to remove this configuration.
ip dhcp ping packet 0
no ip dhcp ping packet 0
Syntax Description
This command has no additional keywords or arguments.
Command Default
By default, the DHCP server pings a pool address twice before assigning a particular address to a requesting client. If the ping is unanswered, the DHCP server assumes that the address is not in use and assigns the address to the requesting client.
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.
For additional information about DHCP configuration on the Cisco CMTS, refer to the following documents on Cisco.com:
•
•
Examples
The following example of the show version command illustrates configuration of this feature on the Cisco CMTS:
version 12.1no service pad! provides nice timestamps on all log messagesservice timestamps debug datetime msec localtimeservice timestamps log uptime! turn service password-encryption on to encrypt passwordsno service password-encryption! provides additional space for longer configuration fileservice compress-config! supports a large number of modems / hosts attaching quicklyservice udp-small-servers max-servers no-limit!hostname Router!boot system disk0:!no cable qos permission createno cable qos permission updatecable qos permission modems! permits cable modems to obtain Time of Day (TOD) from uBR7100cable time-server!! High performance DOCSIS config file, additional options may be added! 10 Mbit/sec download, 128 Kbit/sec upload speed, 10 Kbit/sec guaranteed upstream! NOTE: cable upstream 0 admission-control 150 will prevent modems from! connecting after 150% of guaranteed-bandwidth has been allocated to! registered modems. This can be used for peek load balancing.! max-burst 1600 prevents a modem with concatenation turned on from consuming! too much wire time, and interfering with VoIP traffic.! cpe max 8 limits the modem to 8 hosts connected before the CMTS refuses! additional host MAC addresses.! Timestamp option makes the config file only valid for a short period of time.!cable config-file platinum.cmservice-class 1 max-upstream 128service-class 1 guaranteed-upstream 10service-class 1 max-downstream 10000service-class 1 max-burst 1600cpe max 8timestamp!! Medium performance DOCSIS config file, additional options may be added! 5 Mbit/sec download, 128 Kbit/sec upload speed!cable config-file gold.cmservice-class 1 max-upstream 64service-class 1 max-downstream 5000service-class 1 max-burst 1600cpe max 3timestamp!! Low performance DOCSIS config file, additional options may be added! 1 Mbit/sec download, 64 Kbit/sec upload speed!cable config-file silver.cmservice-class 1 max-upstream 64service-class 1 max-downstream 1000service-class 1 max-burst 1600cpe max 1timestamp!! No Access DOCSIS config file, used to correctly shut down an unused cable modem! 1 kbit/sec download, 1 Kbit/sec upload speed, with USB/ethernet port shut down.!cable config-file disable.cmaccess-deniedservice-class 1 max-upstream 1service-class 1 max-downstream 1service-class 1 max-burst 1600cpe max 1timestamp!ip subnet-zero! Turn on cef switching / routing, anything but process switching (no ip route-cache)ip cefip cef accounting per-prefix! Disables the finger serverno ip finger! Prevents CMTS from looking up domain names / attempting to connect to! machines when mistyping commandsno ip domain-lookup! Prevents issuance of IP address that is already in use.ip dhcp ping packets 0Related Commands
ip dhcp pool
To create a DHCP address pool and enter DHCP pool configuration file mode, use the ip dhcp pool command in global configuration mode. To remove a configured DHCP pool, use the no form of this command.
Syntax Description
Command Default
DHCP pool names 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.
For additional information about DHCP configuration on the Cisco CMTS, refer to the following documents on Cisco.com:
•
•
Examples
The following example configures a DHCP pool with the name indicated, and enables additional configuration in the DHCP pool configuration mode:
Router# configure terminal
Router(config)# ip dhcp pool local
Router(dhcp-config)#
The following examples illustrate additional configurations that are typical for a DHCP pool configured when starting with the ip dhcp pool command, or with additional DHCP configuration commands.
ip dhcp pool cm-platinumnetwork 10.128.4.0 255.255.255.0bootfile platinum.cmnext-server 10.128.4.1default-router 10.128.4.1option 2 hex ffff.8f80option 4 ip 10.1.4.1option 7 ip 10.1.4.1lease 7 0 10!ip dhcp pool cm-goldnetwork 10.129.4.0 255.255.255.0bootfile gold.cmnext-server 10.129.4.1default-router 10.129.4.1option 2 hex ffff.8f80option 4 ip 10.1.4.1option 7 ip 10.1.4.1lease 7 0 10!ip dhcp pool cm-silvernetwork 10.130.4.0 255.255.255.0bootfile silver.cmnext-server 10.130.4.1default-router 10.130.4.1option 2 hex ffff.8f80option 4 ip 10.1.4.1option 7 ip 10.1.4.1lease 7 0 10!ip dhcp pool DisabledModem(0010.aaaa.0001)host 10.128.1.9 255.255.255.0client-identifier 0100.10aa.aa00.01bootfile disable.cm!ip dhcp pool DisabledModem(0020.bbbb.0002)host 10.128.1.10 255.255.255.0client-identifier 0100.20bb.bb00.02bootfile disable.cm!ip dhcp pool DisabledModem(1010.9581.7f66)host 10.128.1.11 255.255.255.0client-identifier 0100.1095.817f.66bootfile disable.cm!ip dhcp pool hostsnetwork 10.254.1.0 255.255.255.0default-router 10.254.1.1dns-server 10.254.1.1 10.128.1.1domain-name ExamplesDomainName.comlease 7 0 10!Related Commands
ip dhcp relay information option
To configure the Cisco CMTS so that it inserts the MAC address of a CM into the DHCP packet received from a CM or host before it forwards the packet to a DHCP server, use the ip dhcp relay information option in global configuration mode. To disable the MAC address insertion, use the no form of this command.
ip dhcp relay information option
no ip dhcp relay information option
Syntax Description
This command has no keywords or arguments.
Command Default
no ip dhcp relay info option
Command Modes
Global configuration
Command History
Usage Guidelines
This functionality enables a DHCP server to identify the user (CM) sending the request. When this option is enabled, the CMTS inserts the DHCP relay agent information option (also called option 82), which contains the CM or host MAC address, in forwarded BOOTREQUEST messages.
Examples
The following example shows how to enable the insertion of DHCP relay agent information into DHCP packets:
Router# configure terminalRouter(config)# ip dhcp relay information optionRelated Commands
ip dhcp smart-relay
To monitor client retransmissions when address pool depletion occurs, use the ip dhcp smart-relay in global configuration mode. To disable this function, use the no form of this command.
ip dhcp smart-relay
no ip dhcp smart-relay
Syntax Description
This command has no arguments or keywords.
Command Default
This command is disabled by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
When relay detects excessive retransmissions, it changes the GIADDR, which in turn causes the server to index a different address pool.
Examples
The following example shows how to enable the insertion of DHCP smart relay agent information into DHCP packets:
configure terminalip dhcp smart-relayThe following example shows how to disable the DHCP smart-relay feature, which would be done when the DHCP clients send multiple DHCP request messages at the same time:
no ip dhcp smart-relayRelated Commands
ip http cable-monitor
To enable the cable access router's onboard Cable Monitor web server, use the ip http cable-monitor command in global configuration mode. To disable the Cable Monitor and turn off all access to the onboard Cisco web server, use the no form of this command.
Cisco uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
ip http cable-monitor {basic | advance} [url-ip-address url-mask]
no ip http cable-monitor
Syntax Description
Command Default
For url-ip-address, 192.168.100.1
For url-mask, 255.255.255.0
Command Modes
Global configuration
Command History
Usage Guidelines
This command enables the Cable Monitor, an onboard web server that displays current status, troubleshooting, and performance information. The Cable Monitor can be accessed in two ways:
•
•
Enabling the Cable Monitor also enables the Cisco web server that is onboard the cable access router, which is the equivalent to entering the ip http server command. However, when the Cable Monitor is enabled, all other access, including CLI access, to the onboard web server is automatically disabled.
Note
Disabling the Cable Monitor using the no ip http cable-monitor command also automatically disables the Cisco web server, which is the equivalent of giving the no ip http server command. When disabling the Cable Monitor, the console might display warning messages similar to the following:
% monitor-209.165.202.131 is not in the database.% monitor-192.168.100.1 is not in the database.% Range [209.165.202.131, 209.165.202.131] is not in the database.% Range [192.168.100.1, 192.168.100.1] is not in the database.These messages can be ignored because they are simply confirming that the IP addresses used for the Cable Monitor are no longer being used for that purpose.
The URL-IP-address and URL-mask arguments also specify that the class C private network 192.168.100.0 is the default address pool for the temporary DHCP server that activates when the cable interface goes down.
Note
Examples
The following example shows how to enable the Cable Monitor for advanced mode, in which all status and diagnostic pages are displayed:
Router(config)# ip http cable-monitor advanceRouter(config)#The following example shows how to disable both the Cable Monitor and the Cisco web server, preventing all web server access to the Cisco uBR924 cable access router:
Router(config)# no ip http cable-monitorRouter(config)#Related Commands
Note
ip http ezvpn
To enable the Cisco Easy VPN Remote web server interface, use the ip http ezvpn command in global configuration mode. To disable the Cisco Easy VPN Remote web interface, use the no form of this command.
Cisco uBR905 and BR925 cable access routers
ip http ezvpn
no ip http ezvpn
Syntax Description
This command has no keywords or arguments.
Command Default
The Cisco Easy VPN Remote web interface is disabled by default.
Command Modes
Global configuration
Command History
12.2(8)YJ, 12.2(15)T
This command was introduced for the Cisco uBR905 and Cisco uBR925 cable access routers.
Usage Guidelines
This command enables the Cisco Easy VPN Remote web server, an onboard web server that allows users to connect an IPSec Easy VPN tunnel and to provide the required authentication information. This allows the user to perform these functions without having to use the Cisco command-line interface.
Before using this command, you must first enable the Cisco web server that is onboard the cable access router by entering the ip http server command. Then use the ip http ezvpn command to enable the Cisco Easy VPN Remote web server. You can then access the web server by entering the IP address for the router's Ethernet interface in your web browser.
Note
Examples
The following example shows how to enable the Cisco Easy VPN Remote web server interface:
Router# configure terminalRouter(config)# ip http serverRouter(config)# ip http ezvpnRouter(config)# exitRouter# copy running-config startup-configRelated Commands
ip-address (controller)
To set the IP address of the Wideband SPA FPGA, use the ip-address (controller) command in controller configuration mode. To remove the IP address of the Wideband SPA FPGA, use the no form of this command.
ip-address ip-address
no ip-address ip-address
Syntax Description
Command Default
No IP address is set for the Wideband SPA FPGA.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
Use this command to set the IP address for the Wideband SPA FPGA. This address is used as the source IP address for packets that the Wideband SPA transmits to the EQAM device.
Examples
The following example shows how to set the IP address of the Wideband SPA FPGA. The SPA is located in slot 1, subslot 0, bay 0.
Router(config)# controller modular-cable 1/0/0Router(config-controller)# ip-address 192.168.200.6Related Commands
ipdr associate
To associate the Collector with a session, use the ipdr associate command in global configuration mode. To remove the association, use the no form of this command.
ipdr associate session_id collector_name priority
no ipdr associate session_id collector_name
Syntax Description
Command Default
An association with the session will not be created.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command allows the user to associate the Collector with a session. Once the Collector is configured, the Exporter sends data to the Collector. IPDR supports redundant collector and consistent streaming continues when a collector is down or not functioning.
The no form of the command will only remove the association for the stopped session.
Note
Examples
The following example configures a Collector.
Router# configure terminalRouter(config)#ipdr associate 1 federal 1Related Commands
ipdr collector
To configure the Internet Protocol Detail Record (IPDR) Collector details, use the ipdr collector command in global configuration mode. To remove the Collector, use the no form of this command.
ipdr collector collector_name ip_addr [port]
no ipdr collector collector_name
Syntax Description
Command Default
A Collector will not be configured.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command allows the user to configure an IPDR Collector and authenticate the IPDR protocol. Once the Collector is configured, the Exporter sends data to the Collector. User must provide the collector name and the IP address. Port number is used when an exporter creates an active connection.
The no form of the command will remove a specific IPDR Collector. If the collector is associated with an active session, you should stop the session before using the no command.
Examples
The following example configures a Collector.
Router# configure terminalRouter(config)#ipdr collector federal 192.0.2.0Related Commands
ipdr exporter start
To enable the CMTS application, to start the Internet Protocol Detail Record (IPDR) Exporter process to connect the exporter and the collector, use the ipdr exporter start command in global configuration mode. To terminate the connection between the exporter and collector, use the no form of this command.
ipdr exporter start
no ipdr exporter start
Syntax Description
This command has no arguments or keywords.
Command Default
By default, the IPDR exporter process will not be started.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command allows the user to explicitly start the IPDR Exporter and connect to the collector. As a default behavior, the command will initiate all the sessions configured in the Exporter to a "Start" state.
The no form of the command will stop the IPDR Exporter process. The command will also clear the connection with the collector while retaining other configurations.
Examples
The following example starts the IPDR Exporter process on the CMTS.
Router# configure terminalRouter(config)#ipdr exporter startRelated Commands
ipdr session
To start or stop a specific session, use the ipdr session command in the privileged EXEC mode.
ipdr session session_id {start | stop}
Syntax Description
session_id
The unique IPDR session ID.
start
The keyword to start the session.
stop
The keyword to stop the session.
Command Default
No sessions are started.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to start or stop a specific session. This command can be executed only when the IPDR exporter is started.
Note
Examples
The following example enables the user to start a session.
Router# configure terminalRouter(config)#ipdr session 1 startRelated Commands
ipdr session (global configuration)
To enable the CMTS application to add a session to the Internet Protocol Detail Record (IPDR) exporter, use the ipdr session command in global configuration mode. To remove the session, use the no form of this command.
ipdr session session_id session_name session_descr
no ipdr session session_id
Syntax Description
session_id
The unique IPDR session ID.
session_name
The session name. The name should not contain extra spaces.
session_descr
The description of the session.
Command Default
No sessions are added to the IPDR exporter. It depends on the status of the IPDR exporter. After configuring one session;if the status of exporter is started, then the session is started automatically.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command allows the user to add a session to the IPDR exporter. User should provide session ID, session name and session description for every session.
The no form of the command will remove a specific session. Once a session is removed, the template and other information associated with the session is also lost.
Note
Examples
The following example adds a session to the Exporter.
Router# configure terminalRouter(config)#ipdr session 1 test no_descrRelated Commands
ipdr template
To add an Internet Protocol Detail Record (IPDR) template to the IPDR Session, use the ipdr template command in global configuration mode. To remove the template, use the no form of this command.
ipdr template session_id template_name
no ipdr template session_id template_name
Syntax Description
Command Default
Template is not added to the session.
Command Modes
Global configuration mode
Command History
Usage Guidelines
This command allows the user to add an IPDR template to the desired session (based on session ID.)
The no form of the command will remove a specific template from the session.
Note
Examples
The following example adds a template to the session.
Router# configure terminalRouter(config)#ipdr template 1 SAMISRelated Commands
issu linecard abortversion
To abort or roll back the current image version on a single line card or multiple line cards to the previous version, use the issu linecard abortversion command in the privileged EXEC mode.
Note
issu linecard abortversion all | lc_slot[/subslot] [forced]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to roll back to prior image on working or primary line card on a single or multiple line cards to the previous versions.
Note
The following example aborts the specific redundant line card's image version.
Router# configure terminalRouter(config)#issu linecard abortversionRelated Commands
issu linecard acceptversion
To accept the new image version on the working line card, use the issu linecard acceptversion command in the privileged EXEC mode.
issu linecard acceptversion lc_slot[/subslot]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to accept the new image version on the working line card. The command also indicates the completion of changing the image version for the specific line card and allows the ISSU of the next line card in the queue.
Examples
The following example indicates a command accepting the image version on the slot 7 of the line card.
Router# configure terminalRouter(config)#issu linecard acceptversion 7/0Related Commands
issu linecard changeversion
To start the upgrade or downgrade activity of the image version for a single working line card or multiple working line cards, use the issu linecard changeversion command in the privileged EXEC mode.
issu linecard changeversion {all | stop | slot_1[/subslot_1] ... [slot_n[/subslot_n]]} [forced]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to start the upgrade or downgrade activity of the image version for a single line card or multiple line cards. Here the line cards are of the primary or working type only.
Using the all option, you can change the image version of all the redundant line cards instead of specifying explicity each of the line card.
Using the stop option, you can abort or stop the version change process for a line card.
Examples
The following example displays the command and uses the all option.
Router# configure terminalRouter(config)#issu linecard changeversion allThe following example displays the command and uses the slot value of 6.
Router# configure terminalRouter(config)#issu linecard changeversion 6/0Related Commands
issu linecard loadversion
To load a specific image version on the primary line card, use the issu linecard loadversion command in the privileged EXEC mode.
issu linecard loadversion slot[/subslot]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to load a specific image version on the working line card.
Examples
The following example shows the command that loads the image version on a line card with the slot number 7.
Router# configure terminalRouter(config)#issu linecard loadversion 7/0Related Commands
issu linecard prepareversion
To determine if the image version on the line card has to be upgraded or downgraded to the route processor's image version, use the issu linecard prepareversion command in the privileged EXEC mode.
issu linecard prepareversion lc_slot[/subslot] [forced]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to check if the image version on the line card has to be upgraded or downgraded to the route processor's image version.
This command also checks if the line card has a valid redundancy configuration. If the line card does not have a valid configuration, then the user has to reload the line card using the issu linecard reloadversion command.
Examples
The following example shows the command executed for a line card with a slot value of 7.
Router# configure terminalRouter(config)#issu linecard prepareversion 7/0Related Commands
issu linecard reloadversion
To reload the new loaded image on a working or a primary line card, use the issu linecard reloadversion command in the privileged EXEC mode.
issu linecard reloadversion {original | target} all | slot_1[/subslot_1] ... [slot_n[/subslot_n]]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to reload the new loaded image on a working or a primary line card.
This command can be used for the following line card conditions.
•
•
Examples
The following example shows the command executed with the original keyword.
Router# configure terminalRouter(config)#issu linecard reloadversion original 8/0The following example shows the command executed with the target keyword.
Router# configure terminalRouter(config)#issu linecard reloadversion target 8/0Related Commands
issu linecard runversion
To run the new loaded image on a working or a primary line card, use the issu linecard runversion command in the privileged EXEC mode.
issu linecard runversion lc_slot[/subslot] [forced]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Privileged EXEC mode
Command History
Usage Guidelines
This command allows the user to run the new loaded image on a working or a primary line card.
Examples
The following example displays the command executed to run the loaded image in the line card slot 7.
Router# configure terminalRouter(config)#issu linecard runversion 7/0Related Commands
mac-address
To modify the default MAC address of an interface to some user-defined address, use the mac-address command in interface configuration mode. To return to the default MAC address on the interface, use the no form of this command.
mac-address ieee-address
no mac-address ieee-address
Syntax Description
Defaults
The interface uses a default MAC address that is derived from the base address stored in the electrically erasable programmable read-only memory (EEPROM).
Command Modes
Interface configuration
Usage Guidelines
Be sure that no other interface on the network is using the MAC address that you assign.
There is a known defect in earlier forms of this command when the Texas Instruments Token Ring MAC firmware is used. This implementation is used by Proteon, Apollo, and IBM RTs. A host using a MAC address whose first two bytes are zeros (such as a Cisco router) will not properly communicate with hosts using that form of this command of TI firmware.
There are two solutions. The first involves installing a static Routing Information Field (RIF) entry for every faulty node with which the router communicates. If there are many such nodes on the ring, this may not be practical. The second solution involves setting the MAC address of the Cisco Token Ring to a value that works around the problem.
This command forces the use of a different MAC address on the specified interface, thereby avoiding the Texas Instrument MAC firmware problem. It is up to the network administrator to ensure that no other host on the network is using that MAC address.
Examples
The following example sets the MAC layer address, where xx.xxxx is an appropriate second half of the MAC address to use:
interface tokenring 0mac-address 5000.5axx.xxxxThe following example changes the default MAC address on the interface to 1111.2222.3333:
Router# configure terminal
Router(config)# interface fastethernet 2/1/1
Router(config-if)# mac-address 1111.2222.3333
Related Commands
show interfaces fastethernet
Displays information about the Fast Ethernet interfaces.
show interfaces gigabitethernet
Displays information about the Gigabit Ethernet interfaces.
main-cpu
To enter main-CPU redundancy configuration mode, so that you can configure the synchronization of the active and standby Performance Routing Engine (PRE1) modules, use the main-cpu command in redundancy configuration mode.
main-cpu
Syntax Description
This command has no keywords or arguments.
Defaults
No default behavior or values
Command Modes
Redundancy configuration (config-r)
Command History
Usage Guidelines
When you enter main-CPU redundancy configuration mode, the prompt changes to the following:
Router(config-r-mc)#After you enter main-CPU redundancy configuration mode, you can use the auto-sync command to specify which files are synchronized between the active and standby PRE1 modules. In Cisco IOS Release 12.2(11)BC3 and later releases, you can also use the switchover timeout command to specify the amount of time that the standby PRE1 module should wait when it first detects that the active PRE1 module is not active and when it initiates a switchover and becomes the active PRE1 module.
To leave main-CPU redundancy configuration mode and to return to redundancy configuration mode, use the exit command.
Examples
The following example shows how to enter main-CPU redundancy mode and the commands that are available there:
Router# config tRouter(config)# redundancyRouter(config-r)# main-cpuRouter(config-r-mc)# ?Main Cpu redundancy configuration commands:auto-sync Sync elementsexit Exit from main-cpu configuration modeno Negate a command or set its defaultsswitchover Configuration of switchoverRouter(config-r-mc)#Related Commands
maintenance-mode
To configure the PRE1 modules on the router for maintenance mode, use the maintenance-mode command in redundancy configuration mode. To return to normal operations, use the no form of this command.
maintenance-mode
no maintenance-mode
Syntax Description
This command has no keywords or arguments.
Command Default
Normal operations (no maintenance-mode)
Command Modes
Redundancy configuration
Command History
Usage Guidelines
When the Cisco uBR10012 router is configured with redundant PRE1 modules, the active PRE1 module automatically synchronizes the configuration, network state information, and other information with the standby PRE1 module, so that if a switchover occurs, the standby module can restore normal operations quickly. You can use the maintenance-mode command to disable this automatic synchronization of the PRE1 modules, and to disable the reporting of any faults on the standby module to the active module.
Note
Examples
The following example shows how to disable the automatic PRE1 module synchronization on the Cisco uBR10012 router and enter maintenance mode:
Router# config tRouter(config)# redundancyRouter(config-r)# maintenance-modeRouter(config-r)# exitRouter(config)#The following example shows how to leave maintenance mode and return to normal operations, which includes the automatic synchronization of the PRE1 modules:
Router# config tRouter(config)# redundancyRouter(config-r)# no maintenance-modeRouter(config-r)# exitRouter(config)#Related Commands
auto-sync
Configures which files are synchronized between the active and standby PRE1 modules.
redundancy
Enters redundancy configuration mode.
match rule
To configure the match rule, rule priority and related action in the selected cable multicast authorization profile, use the match rule command in interface configuration mode. To disable a cable multicast authorization profile match, use the no form of this command.
match rule [ipv4 | ipv6] [source-prefix] [group-prefix] priority [priority-value] [permit | deny]
no match rule [ipv4/ipv6] [source-prefix] [group-prefix] priority [priority-value] [permit/deny]
Syntax Description
Command Default
Cable multicast authorization is disabled.
Command Modes
Interface configuration—cable interface only (config-mauth)
Command History
Usage Guidelines
This command specifies the cable multicast authorization profile match to be used.
Examples
The following example shows how to use the selected multicast authorization profile match:
Router(config-mauth)# match rule rule1Related Commands
member subslot
To configure the redundancy role of a line card, use the member subslot command in line card redundancy group mode.
member subslot slot/subslot {primary | secondary}
no member subslot slot/subslot {primary | secondary}
uBR10012 Router and uBR7200 Series Universal Broadband Routers
member subslot slot/subslot {protect | working | revertive | reverttime value}
no member subslot slot/subslot {protect | working | revertive | reverttime value}
Syntax Description
Command Default
None
Command Modes
Line card redundancy group
Command History
Usage Guidelines
The primary line card must be the first line card configured and must occupy subslot 1. The secondary line card must be the second line card configured and must occupy subslot 0. Only one primary line card and one secondary line card can be configured.
Examples
The following creates line card group number 1 for one-to-one line card redundancy. It also specifies the line card in subslot 1 as the primary (active) line card, and the line card in subslot 0 as the secondary (standby) line card:
Router# configure terminalRouter(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 2/1 primaryRouter(config-red-lc)# member subslot 2/0 secondaryRelated Commands
microcode (uBR10012)
To reload the microcode software images on a Parallel eXpress Forwarding (PXF) processor or on all line cards that support downloadable microcode, use the microcode command in global configuration mode.
microcode {pxf filename | reload}
Syntax Description
Command Default
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
By default, the Cisco uBR10012 router automatically loads all required microcode on to the PXF processors and other line cards when it loads the Cisco IOS software image. Also, the PRE1 module automatically reloads the microcode on a card when certain faults occur, allowing the card to recover from the fault.
You can reload the microcode on the PRE1 module or on all line cards that support downloadable microcode by using the microcode command. Typically, this is not needed and should be done only upon the advice of Cisco TAC or field service engineers.
Tip
Examples
The following example shows how to reload the microcode on all PRE processors and line cards that support downloadable microcode:
Router# configure terminalRouter(config)# microcode reloadReload microcode? [confirm] yes00:49:41: Downloading Microcode: file=system:pxf/ubr10k-ucode.1.2.3,version=1.1.0, description=Release Software created Wed 17-Jul-02 16:58<<list of interfaces going down or coming up>>00:49:42: !!pxf clients started, forwarding code operational!!Router(config)#The following example shows how to reload the microcode on the PXF processors on the PRE1 module, using a specific image that is stored in the Flash memory:
Router# configure terminalRouter(config)# microcode pxf flash:pxf/ubr10k-ucode.122.1.2.3Reload microcode? [confirm] yes1d04h: Downloading Microcode: file=flash:pxf/ubr10k-ucode.122.1.2.3, version=122.1.2.3, description=Release Software created Thu 17-Oct-02 11:33<<list of interfaces going down or coming up>>1d04h: !!pxf clients started, forwarding code operational!!Router(config)#Related Commands
microcode reload (uBR10012)
To reload the microcode software images on one or all line cards that support downloadable microcode, use the microcode reload command in privileged EXEC mode.
microcode reload {all | pxf [device:[filename]]}
Syntax Description
Command Default
For microcode reload pxf, defaults to loading the microcode image that was originally loaded when the Cisco IOS software image was loaded.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
By default, the Cisco uBR10012 router automatically loads all required microcode on to the PXF processors and other line cards when it loads the Cisco IOS software image. Also, the PRE1 module automatically reloads the microcode on a card when certain faults occur, allowing the card to recover from the fault.
You can reload the microcode on the PRE1 module or on all line cards that support downloadable microcode by using the microcode reload command. Typically, this is not needed and should be done only upon the advice of Cisco TAC or field service engineers.
Tip
Examples
The following example shows how to reload the microcode on all PRE processors and line cards that support downloadable microcode:
Router# microcode reload allReload microcode? [confirm] yes00:49:41: Downloading Microcode: file=system:pxf/ubr10k-1-ucode.122.1.0, version=122.1.0, description=Release Software created Wed 17-Jul-02 16:58<<list of interfaces going down or coming up>>00:49:42: !!pxf clients started, forwarding code operational!!Router#The following example shows a typical list of devices that you can use when loading microcode for the PXF processors. This list might vary, depending on whether a standby PRE1 module is installed and depending on the version of Cisco IOS software being used.
Router# microcode reload pxf ?bootflash: location of microcodedisk0: location of microcodedisk1: location of microcodeflash: location of microcodeftp: location of microcodenull: location of microcodenvram: location of microcodercp: location of microcodescp: location of microcodesec-bootflash: location of microcodesec-disk0: location of microcodesec-disk1: location of microcodesec-nvram: location of microcodesec-slot0: location of microcodesec-slot1: location of microcodeslot0: location of microcodeslot1: location of microcodesystem: location of microcodetftp: location of microcode<cr>Router#The following example shows how to reload the microcode on the PXF processors on the PRE1 module, using a specific image that is stored in the Flash memory:
Router# microcode reload pxf flash:pxf/ubr10k-1-ucode.122.1.0.4Reload microcode? [confirm] yes3d00h: Downloading Microcode: file=flash:pxf/ubr10k-1-ucode.122.1.0.4, version=122.1.0.4, description=Release Software created Thu 27-Jun-02 16:05<<list of interfaces going down or coming up>>3d00h: !!pxf clients started, forwarding code operational!!Router#Related Commands
mode (redundancy)
To configure the redundancy mode of operation, use the mode command in redundancy configuration mode.
Cisco 7304 Router
mode {rpr | rpr-plus | sso}
Cisco 7500 Series Routers
mode {hsa | rpr | rpr-plus | sso}
Cisco 10000 Series Routers
mode {rpr-plus | sso}
Cisco 12000 Series Routers
mode {rpr | rpr-plus | sso}
Cisco uBR10012 Universal Broadband Router
mode {rpr-plus | sso}
Syntax Description
Command Default
The default mode for the Cisco 7500 series routers is HSA.
The default mode for the Cisco 7304 router and Cisco 10000 series routers is SSO.
The default mode for the Cisco 12000 series routers is RPR.
The default mode for the Cisco uBR10012 universal broadband router is SSO.Command Modes
Redundancy configuration (config-red)
Command History
Usage Guidelines
The mode selected by the mode command in redundancy configuration mode must be fully supported by the image that has been set into both the active and standby Route Processors (RPs). A high availability image must be installed into the RPs before RPR can be configured. Use the hw-module slot image command to specify a high availability image to run on the standby RP.
For Cisco IOS Release 12.2(33)SCA on the Cisco 10000 series routers and the Cisco uBR10012 universal broadband router, the use of SSO redundancy mode is recommended because RPR+ redundancy mode is being removed. If you enable RPR+ redundancy mode, you may see the following message:
********************************************************** Warning, The redundancy mode RPR+ is being deprecated ** and will be removed in future releases. Please change ** mode to SSO: ** redundancy ** mode sso *********************************************************Examples
The following example configures RPR+ redundancy mode on a Cisco 12000 series or Cisco 1000 series router:
Router# mode rpr-plusThe following example sets the mode to HSA on a Cisco 7500 series router:
Router# mode hsaRelated Commands
modular-host subslot
To specify the modular-host line card that will be used for DOCSIS 3.0 downstream or downstream channel bonding operations, use the modular-host subslot command in controller configuration mode. To remove the modular-host line card used for DOCSIS 3.0 downstream or downstream channel bonding operations, use the no form of this command.
modular-host subslot slot/subslot
no modular-host subslot slot/subslot
Syntax Description
Command Default
No modular-host line card is configured for DOCSIS 3.0 downstream or downstream channel bonding operations.
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
This command specifies the modular-host line card for DOCSIS 3.0 downstream or downstream channel bonding operations. This applies to the cable interface line card (for example, the Cisco uBR10-MC5X20S-D line card) that is used for these operations. The Wideband SPA itself does not support DOCSIS 3.0 downstream channel bonding operations.
Examples
The following example shows how to configure the modular-host line card for DOCSIS 3.0 downstream channel bonding operations for the Wideband SPA located in slot/subslot/bay 1/0/0:
Router(config)# controller modular-cable 1/0/0Router(config-controller)# modular-host subslot 7/0Related Commands
monitoring-basics
To specify the type of monitoring for subscriber traffic management on a Cisco CMTS router, use the monitoring-basics command in enforce-rule configuration mode. To disable the selected monitoring, use the no form of this command.
monitoring-basics {legacy | peak-offpeak} {docsis10 | docsis11}
no monitoring-basics {legacy | peak-offpeak} {docsis10 | docsis11}
Syntax Description
Command Default
The default for this command is legacy and docsis10.
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
Legacy monitoring (using the legacy keyword) occurs 24 hours a day, with no distinction between peak and offpeak hours. The available monitoring duration is between 10 minutes and 31 days.
Use the peak-offpeak keyword to set up monitoring duration and threshold for first peak, second peak, and offpeak monitoring. Each one can be different. After setting up first peak and second peak durations, the remaining hours are treated as offpeak. Monitoring happens during offpeak hours if the offpeak duration and threshold are defined. Monitoring duration is between 60 minutes and 23 hours.
Examples
The following example shows configuration of peak-offpeak monitoring for DOCSIS 1.1 cable modems:
Router(enforce-rule)# monitoring-basics peak-offpeak docsis11Related Commands
monitoring-duration
Note
To specify the time period and sample rate to be used for monitoring subscribers, use the monitoring-duration command in enforce-rule configuration mode. To reset an enforce-rule to its default values, use the no form of this command.
monitoring-duration minutes [sample-rate minutes]
no monitoring-duration
Syntax Description
Defaults
The monitoring-duration value defaults to 360 minutes (6 hours), and the sample-rate value defaults to 15 minutes.
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
The sample-rate minutes must be less than or equal to the monitoring-duration minutes period.
When you enable an enforce-rule, the Cisco CMTS router periodically checks the bandwidth being used by subscribers, to determine whether any subscribers are consuming more bandwidth than that specified by their registered QoS profile. The Cisco CMTS router keeps track of the subscribers using a sliding window that begins at each sample-rate interval and continues for the monitoring-duration period.
For example, with the default sample-rate interval of 15 minutes and the default monitoring-duration window of 360 minutes, the Cisco CMTS router samples the bandwidth usage every 15 minutes and determines the total bytes transmitted at the end of each 360-minute period. Each sample-rate interval begins a new sliding window period for which the Cisco CMTS router keeps track of the total bytes transmitted.
Note
When you change the configuration of a currently active enforce-rule, that rule begins using the new configuration immediately to manage the cable modems tracked by this enforce-rule.
For more information about the Subscriber Traffic Management feature and to see an illustration of a sample monitoring window, refer to the Subscriber Traffic Management for the Cisco CMTS Routers feature document on Cisco.com.
Examples
The following example shows an enforce-rule being configured for a monitoring-duration period that is 20 minutes in length, with a sampling rate of every 10 minutes:
Router# configure terminalRouter(config)# cable qos enforce-rule residentialRouter(enforce-rule)# monitoring-duration 20 sample-interval 10The following example shows the error message that is displayed when the sample-rate interval is configured to be greater than the monitoring-duration period. In this situation, the command is ignored and the parameters remain unchanged.
Router# configure terminalRouter(config)# cable qos enforce-rule residentialRouter(enforce-rule)# monitoring-duration 20 sample-interval 30Monitoring duration cannot be less than the Sampling interval -- so the valueswould remain unchangedRelated Commands
mtu
To adjust the maximum packet size or maximum transmission unit (MTU) size, use the mtu command in interface configuration mode or connect configuration submode. To restore the MTU value to its original default value, use the no form of this command.
mtu bytes
no mtu
Syntax Description
Defaults
Table 23 lists default MTU values according to media type.
Table 23 Default Media MTU Values
Ethernet
1500
Serial
1500
Token Ring
4464
ATM
4470
FDDI
4470
HSSI (HSA)
4470
Command Modes
Interface configuration (config-if)
Connect configuration submode (for Frame Relay Layer 2 interworking)Command History
Usage Guidelines
Each interface has a default maximum packet size or MTU size. This number generally defaults to the largest size possible for that interface type. On serial interfaces, the MTU size varies but cannot be set to a value less than 64 bytes.
Changing the MTU Size
Changing the MTU size is not supported on a loopback interface.
Changing an MTU size on a Cisco 7500 series router results in the recarving of buffers and resetting of all interfaces. The following message is displayed:
%RSP-3-Restart:cbus complex.You can configure native Gigabit Ethernet ports on the Cisco 7200 series router to a maximum MTU size of 9216 bytes. The MTU values range from 1500 to 9216 bytes.
Protocol-Specific Versions of the mtu Command
Changing the MTU value with the mtu interface configuration command can affect values for the protocol-specific versions of the command (the ip mtu command, for example). If the value specified with the ip mtu interface configuration command is the same as the value specified with the mtu interface configuration command, and you change the value for the mtu interface configuration command, the ip mtu value automatically matches the new mtu interface configuration command value. However, changing the values for the ip mtu configuration commands has no effect on the value for the mtu interface configuration command.
ATM and LANE Interfaces
ATM interfaces are not bound by what is configured on the major interface. By default, the MTU on a subinterface is equal to the default MTU (4490); if a client is configured, the default is 1500. The MTU can be changed on subinterfaces, but it may result in recarving of buffers to accommodate the new maximum MTU on the interface.
Cisco 7600 Valid MTU Values
On the Cisco 7600 platform, valid values are from 64 to 9216 for SVI ports; from 1500 to 9170 for the GE-WAN+ ports; and from 1500 to 9216 for all other ports.
If you enable the jumbo frames, the default is 64 for the SVI ports and 9216 for all the other ports. The jumbo frames are disabled by default.
Cisco uBR10012 Universal Broadband Router
When configuring the interface MTU size on a Gigabit Ethernet SPA on a Cisco uBR10012 router, consider the following guidelines:
•
–
–
–
•
•
Note
Examples
The following example specifies an MTU of 1000 bytes:
Router(config)# interface serial 1Router(config-if)# mtu 1000Cisco uBR10012 Universal Broadband Router
The following example shows how to specify an MTU size on a Gigabit Ethernet SPA on the Cisco uBR10012 router:
Router# configure terminalRouter(config)#interface GigabitEthernet3/0/0Router(config-if)#mtu 1800Related Commands
encapsulation smds
Enables SMDS service on the desired interface.
ip mtu
Sets the MTU size of IP packets sent on an interface.
negotiation
, use the negotiation command in interface configuration mode. To disable automatic negotiation, use the no negotiation auto command.
negotiation {forced | auto}
no negotiation auto
Syntax Description
Defaults
auto
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
The negotiation command is applicable to the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E and interfaces on the 2-port 10/100/1000 Gigabit Ethernet SPA that are using fiber media. The negotiation auto command is used instead of the duplex and speed commands (which are used on Ethernet and Fast Ethernet interfaces, and interfaces on the 2-port 10/100/1000 Gigabit Ethernet SPA that are using RJ-45 media) to automatically configure the duplex and speed settings of the interfaces.
The negotiation forced command is used to configure the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E to be 1000/full-duplex only and to disable flow control. The negotiation forced command is not supported by the 2-port 10/100/1000 Gigabit Ethernet SPA.
The Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E and the interfaces on the 2-port 10/100/1000 Gigabit Ethernet SPA that are using fiber media are restricted to 1000 Mbps/full duplex only. Autonegotiation advertises and negotiates only to these values.
Cisco uBR10012 Universal Broadband Router
Autonegotiation is enabled by default and can be disabled on the 5-Port Gigabit Ethernet SPA. During autonegotiation, advertisement for flow control, speed, and duplex occurs. If autonegotiation is disabled on one end of a link, it must be disabled on the other end of the link. If one end of a link has autonegotiation disabled while the other end of the link does not, the link does not come up properly on both ends. Flow control is always negotiated when autonegotiation is enabled.
Note
Examples
The following example enables the second interface (port 1) on a 2-port 10/100/1000 Gigabit Ethernet SPA for autonegotiation, where the SPA is installed in the bottom subslot (1) of the MSC, and the MSC is installed in slot 2 of the Cisco 7304 router:
Router(config)# interface gigabitethernet 2/1/1Router(config-if)# media-type gbicRouter(config-if)# negotiation autoThe following example disables the second interface (port 1) on a 2-port 10/100/1000 Gigabit Ethernet SPA for autonegotiation, where the SPA is installed in the bottom subslot (1) of the MSC, and the MSC is installed in slot 2 of the Cisco 7304 router:
Router(config)# interface gigabitethernet 2/1/1Router(config-if)# no negotiation autoRelated Commands
show interfaces gigabitethernet
Displays information about the Gigabit Ethernet interfaces.
network
To configure the DHCP address pool with the specified network-number and subnet mask, which are the DHCP yiaddr field and Subnet Mask (DHCP option 1) field, use the network command in global configuration mode. To remove this configuration, use the no form of this command.
network network-number [mask]
no network network-number [mask]
Syntax Description
network-number
The DHCP yiaddr field.
mask
Subnet Mask (DHCP option 1). If you do not specify the mask value, it is supported to 255.255.255.255.
Command Default
DHCP settings are not configured by default.
Command Modes
DHCP configuration
Command History
Release 12.2(4)BC1
Supoported on the Cisco uBR7100 series, Cisco uBR7200 series, and Cisco uBR10012 routers.
Usage Guidelines
This command requires that you first use the dhcp ip dhcp pool name command in global configuration mode to enter DHCP configuration mode.
Note
For additional information about DHCP support on the Cisco CMTS, refer to the following document on Cisco.com:
•
Examples
The following example illustrates use of the network command with the ip dhcp pool name command.
Router# configure terminal
Router(config)# ip dhcp pool name platinum
Router(dhcp-config)# network 10.10.10.0 255.255.0.0
Router(dhcp-config)#
Related Commands
nls
To enable Network Layer signaliing (NLS) functionality, use the nls command in global configuration mode. To disable NLS functionality, use the no form of this command.
nls [authentication]
no nls [authentication]
Syntax Description
Command Default
Disabled.
Command Modes
Global configuaration
Command History
Usage Guidelines
It is recommended that NLS message authentication is enabled all the time.
Examples
The following example shows nls enabled on a router:
router (config)# nlsRelated Commands
cpd
Enables the CPD feature.
nls ag-id auth-key
Configures an Authorization Group Identifier (AG ID) for CMTS.
nls resp-timeout
Configures NLS response timeout.
nls ag-id auth-key
To configure an Authorization Group Identifier (AG ID) for CMTS, use the nls ag-id auth-key command in global configuration mode. To disable the AG ID, use the no form of this command.
nls ag-id auth-key
no nls ag-id auth-key
Syntax Description
ag-id number
Authorization Group Identifier. The valid range is 1-4294967294.
auth-key char
Authentication key provisioned on CMTS. The valid range is 20-64.
Command Default
Disabled
Command Modes
Global configuaration
Command History
Examples
The following example shows configuring the AG ID:
Router(config) # nls ag-id 345 auth-key 54Related Commands
cpd
Enables CPD.
nls
Enables Network Layer signaliing (NLS) functionality.
nls resp-timeout
Configures NLS response timeout.
nls resp-timeout
To configure the NLS response timeout, use the nls resp-timeout command in global configuration mode. To disable CPD, use the no form of this command.
nls resp-timeout timeout number
no nls resp-timeout timeout number
Syntax Description
timeout number
Controls the time CTMS will wait before getting a response for an NLS information request. The valid range is 1-60 seconds. Upon a response timeout, the CPD message is dropped.
Command Default
The default timeout is 1 second.
Command Modes
Global configuration
Command History
Examples
The following example shows configuring the NLS response timeout:
Router(config)#nls rssp-timeout 35Related Commands
cpd
Enables CPD.
nls
Enables Network Layer signalling (NLS) functionality.
nls ag-id auth-key
Configures an Authorization Group Identifier (AG ID) for CMTS.
peak-time1
To specify peak and offpeak monitoring times on a Cisco CMTS router, use the peak-time1 command in enforce-rule configuration mode. To disable configuration of peak monitoring times, use the no form of this command.
peak-time1 hour duration minutes avg-rate rate [peak-time2 hour duration minutes avg-rate rate] [duration offpeak-minutes avg-rate offpeak-rate] sample-interval minutes {downstream | upstream}[enforce]
no peak-time1 hour duration minutes avg-rate rate [peak-time2 hour duration minutes avg-rate rate] [duration offpeak-minutes avg-rate offpeak-rate] sample-interval minutes {downstream | upstream}[enforce]
Syntax Description
Command Default
Peak and offpeak monitoring is disabled. The only default value for the peak-time1 command is the 15-minute sample interval.
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
You can use the peak-time1 command to monitor two peak monitoring periods, using the initial peak-time1 command and its options followed by the peak-time2 keyword and corresponding options. The remaining hours are considered "offpeak" and can be monitored by configuring the optional duration keyword and corresponding options.
When you use the show running-configuration command to display the configuration, the keyword options for the peak-time1 command are truncated. In the following example, "d" represents duration (a single peak and offpeak duration are configured), "avg" represents avg-rate, "sa" represents sample-interval, "do" represents downstream, and "enf" represents enforce:
Router# show running-configuration...peak-time1 1 d 60 avg 2 d 60 avg 40 sa 10 do enfExamples
The following example shows an enforce-rule that defines two peak monitoring times for upstream traffic:
Router(enforce-rule)# peak-time1 10 duration 120 avg-rate 10 peak-time2 23 duration 60 avg-rate 10 sample-interval 10 upstream enforceRelated Commands
penalty-period
To specify the time period that an enforced quality of service (QoS) profile should be in force for subscribers that violate their registered QoS profile, use the penalty-period command in enforce-rule configuration mode. To reset an enforce-rule to its default penalty period, use the no form of this command.
penalty-period minutes [time-of-day hour]
no penalty-periodminutes [time-of-day hour]
Syntax Description
Command Default
The default time period is 10080 minutes (7 days).
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
When a subscriber overconsumes the maximum bandwidth that is specified in the enforce-rule, the Cisco CMTS router can automatically switch the subscriber to an enforced QoS profile for the penalty period specified with the penalty-period command. When the penalty period expires, the Cisco CMTS router restores the subscriber to their registered QoS profile.
The penalty period continues across reboots of the cable modem, so a user cannot avoid the enforced QoS profile by trying to reset their modem and reregister on the cable network. This allows service providers to set an appropriate penalty for those users that consistently exceed the maximum bandwidth they have been allocated.
Note
When you change the configuration of a currently active enforce-rule, that rule begins using the new configuration immediately to manage the cable modems tracked by this enforce-rule.
Note
Examples
The following example shows an enforce-rule named "test" configured with a penalty period of 1440 minutes (1 day):
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# penalty-period 1440The following example shows an enforce-rule named "test" configured with a penalty period of 1440 minutes (1 day), but allowing removal of any CMs in penalty at 11:00 P.M.:
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# penalty-period 1440 time-of-day 23Related Commands
option
To create a DOCSIS configuration file that specifies vendor-specific information fields, or other options that are not available through the other cable config-file commands, use the option command in cable config-file configuration mode. To remove the entry for this option, use the no form of this command.
option n [instance inst-num] {ascii string | hex hexstring | ip ip-address}
no option n
Syntax Description
n
Specifies the configuration file option code. Valid range is 5 to 254.
Note
instance inst-num
(Optional) Specifies the instance of this option, so that you can give the same option multiple times. Valid range is 0 to 255.
ascii string
Specifies that the data is a network verification tool (NVT) ASCII string. If the string contains white space, you must surround it with quotation marks.
hex hexstring
Specifies the data as a raw hexadecimal string. Each byte in the hexadecimal string is two hexadecimal digits—each byte can be separated by a period, colon, or white space. A maximum of 254 bytes can be specified.
Note
ip ip-address
Specifies an IP address.
Command Default
No default behaviors or values
Command Modes
Cable config-file configuration
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 provides for a great many options and parameters in the DOCSIS configuration files. In particular, it allows unspecified vendor-specific options that can vary from vendor to vendor and from model to model. To create a DOCSIS configuration file that references these options, use the option command.
The option command allows you to specify configuration file parameters that are not defined by the other cable config-file options. These options are defined in the DOCSIS Radio Frequency (RF) Interface Specification. However, certain options are not allowed because they are either reserved for DOCSIS use or because they are specified using other cable config-file commands.
Table 0-24 lists the options that cannot be specified by the cable config-file option command. Where applicable, the table shows the cable config-file command you can use to specify that option.
Note
Using Option 43 (Vendor-Specific Information Fields)
The most common use of the cable config-file option command is to specify vendor-specific information field values, which vendors use to implement features that are unique to their products. In this case, the value for n must be 43.When you use the vendor-specific option (option 43), you must specify the data using the hex option.
The hexadecimal data must be presented in the DOCSIS Type/Length/Value (TLV) format, where the first byte specifies the suboption type, the second byte specifies the length of the data, and the remaining bytes specify the data itself. The exact meaning of the suboption type and data values is defined by each vendor.
For example, Cisco CMs support a vendor-specific suboption (128) that instructs the CM to download and execute a Cisco IOS configuration file. The data for this suboption is the fully qualified path name of the Cisco IOS configuration file on the TFTP server. Other vendors, however, could define vendor-specific suboption 128 to have a totally different function.
To ensure that a vendor-specific option is executed only by equipment that supports that option, the vendor ID must always be the first part of the data in an option 43 command. The suboption number for the vendor ID function is 08, and the data is the three byte Organization Unique Identifier (OUI) for that vendor, as issued by the Institute of Electrical and Electronics Engineers (IEEE).
The vendor could have defined a global OUI for all of their equipment, or they could have requested a separate OUI ID for different products or family of products. For example, the global OUI for Cisco equipment is 00 00 0C.
Note
Example of Constructing an Option 43 Command
For example, to create a vendor-specific option that downloads a Cisco IOS configuration file, you would create a hexadecimal data string that first contains suboption 8, to specify the vendor ID in TLV format. You would then add the hexadecimal string that contains suboption 128, to specify the filename for the configuration file to be downloaded, in TLV format.
The TLV for the Cisco vendor ID would be 08:03:00:00:0C, where 08 is the suboption type, 03 is the length, and 00:00:0C is the Cisco OUI vendor ID. If the Cisco IOS filename is ios.cfg, the second TLV would be 80:07:69:6F:73:2E:63:66:67, where 80 is the suboption type (128 decimal), 07 is the length of the data, and the data is the filename expressed in hexadecimal ASCII values.
The complete hex data string would be 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67. The complete command would be option 43 hex 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67.
Note
Caution
The following example shows how to specify a static downstream frequency for a Cisco uBR905, Cisco uBR924, Cisco uBR925, or Cisco CVA, using the option 43 command to specify Cisco vendor-specific option 1.
router(config)# cable config-file statfreq.cmrouter(config-file)# option 43 hex 08:03:00:00:0C:01:04:05:7F:9F:90router(config-file)# exitrouter(config)#The hexadecimal data shown in this command consists of the two TLVs shown in Table 0-25:
Note
The following example shows how to configure a Cisco uBR924, Cisco uBR925, or Cisco CVA122 so that it downloads a Cisco IOS configuration file named ios.cfg and configures the router for two voice ports. Three vendor-specific options are included: suboption 8, which specifies the vendor ID, suboption 128, which specifies the configuration file name, and suboption 10, which specifies the number of active voice ports.
router(config)# cable config-file iosfile.cmrouter(config-file)# option 43 hex 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67:0A:01:02router(config-file)# exitrouter(config)#The hexadecimal data shown in this command consists of the three TLVs shown in Table 0-26:
Cisco CMs also support giving a limited number of Cisco IOS configuration mode commands in the DOCSIS configuration file, using vendor-specific suboption 131. The following example shows how to use the option 43 command to specify that the Cisco CM should execute the ip http cable-monitor advance command to enable its onboard Cable Monitor web server.
router(config-file)# option 43 hex 08:03:00:00:0C:83:1D:69:70:20:68:74:74:70:20:63:61:62: 6C:65:2D:6D:6F:6E:69:74:6F:72:20:61:64:76:61:6E:63:65router(config-file)#Table 0-27 lists the two TLVs shown in this example:
The following example shows the instance keyword being used to give multiple option 43 commands. This example uses the same commands shown in the previous three examples.
router(config-file)# option 43 instance 1 hex 08:03:00:00:0C:01:04:05:7F:9F:90router(config-file)# option 43 instance 2 hex 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67: 0A:01:02router(config-file)# option 43 instance 3 hex 08:03:00:00:0C:83:1D:69:70:20:68:74:74:70:20:63:61:62:6C:65:2D:6D:6F:6E:69:74:6F:72:20:61: 64:76:61:6E:63:65router(config-file)#The following example shows an attempt to specify two options that cannot be specified through the DOCSIS configuration file. Option 12 is reserved for the DOCSIS registration process, and Option 9 must be specified using the download command.
router(config-file)# option 12 ip 10.11.12.13%Option 12 must not be specified manuallyrouter(config-file)# option 9 ascii newsoftware.file%Option 9 must be specified directly (not as raw option)router(config-file)#Related Commands
packetcable
To enable PacketCable operations on the Cisco CMTS, use the packetcable command in global configuration mode. To disable PacketCable operations, use the no form of this command.
packetcable
no packetcable
Syntax Description
This command has no keywords or arguments.
Command Default
PacketCable operation is disabled.
Command Modes
Global Configuration
Command History
Usage Guidelines
This command enables PacketCable operations on all cable interfaces and takes effect immediately. If you do not need to change any parameters from their default values, this is the only command needed to enable PacketCable operations.
In Cisco IOS Release 12.2(11)BC1 and later releases, this command also automatically creates a random Element ID for the CMTS that is in the range of 0 and 99,999. To ensure that this Element ID is unique across the entire PacketCable domain, you should use the packetcable element-id command.
Note
Channel Width Limitations
The 200,000 Hz channel width cannot be used on upstreams that support PacketCable voice calls, or on any upstreams that use Unsolicited Grant Service (UGS) or UGS with Activity Detection (UGS-AD) service flows. Using this small a channel width with voice and other UGS/UGS-AD service flows results in calls being rejected because of "DSA MULTIPLE ERRORS".
Examples
The following example shows PacketCable operation being enabled:
Router# configure terminalRouter(config)# packetcableRouter(config)#The following example shows PacketCable operation being disabled (default):
Router# configure terminalRouter(config)# no packetcableRouter(config)#Related Commands
packetcable authorize vanilla-docsis-mta
To allow Unsolicited Grant Service (UGS) service flows without a proper PacketCable gate ID when PacketCable operations are enabled on the Cisco CMTS, use the packetcable authorize vanilla-docsis-mta command in global configuration mode. To prevent CMs from requesting non-PacketCable UGS service flows when PacketCable operations are enabled, use the no form of this command.
packetcable authorize vanilla-docsis-mta
no packetcable authorize vanilla-docsis-mta
Syntax Description
This command has no keywords or arguments.
Command Default
Non-PacketCable UGS service flows are not allowed when PacketCable operations are enabled.
Command Modes
Global Configuration
Command History
12.2(11)BC2
This command was introduced for the Cisco uBR7200 series universal broadband router.
12.2(15)BC1
Support was added for the Cisco uBR10012 router.
Usage Guidelines
By default, when PacketCable operations are enabled (using the packetcable ccommand), CMs must follow the PacketCable protocol when requesting UGS service flows. This prevents DOCSIS CMs that do not support PacketCable operations from using DOCSIS-style UGS service flows.
If you have a mixed network that contains both PacketCable and non-PacketCable DOCSIS CMs, you can allow DOCSIS CMs to request UGS service flows by using the packetcable authorize vanilla-docsis-mta command. If, however, your CMTS is providing PacketCable services, use the no packetcable authorize vanilla-docsis-mta command to disable DOCSIS-style service flows. This is the default configuration when PacketCable operations are enabled, and it requires that CMs must provide a validly authorized gate ID before being granted a UGS service flow.
Examples
The following example shows PacketCable operation being enabled, while still allowing DOCSIS-style UGS service flows:
Router# configure terminalRouter(config)# packetcableRouter(config)# packetcable authorize vanilla-docsis-mtaRouter(config)#The show packetcable global command has also been enhanced to display whether non-PacketCable DOCSIS-style UGS service flows are allowed:
Router# show packetcable globalPacket Cable Global configuration:Enabled : YesElement ID: 12456Max Gates : 1048576Allow non-PacketCable UGSDefault Timer value -T0 : 30000 msecT1 : 300000 msecT2 : 2000 msecT5 : 500 msecRouter#Related Commands
packetcable element-id
To configure the PacketCable Event Message Element ID on the Cisco CMTS, use the packetcable element-id command in global configuration mode. To reset the counter to its default value, use the no form of this command.
packetcable element-id n
no packetcable element-id
Syntax Description
n
PacketCable Event Message Element ID for the Cisco CMTS. The valid range is 0 through 99999, with a default that is a random number in that range.
Command Default
A random value between 0 and 99,999.
Command Modes
Global Configuration
Command History
12.2(11)BC1
This command was introduced for the Cisco uBR7200 series universal broadband router.
12.2(15)BC1
Support was added for the Cisco uBR10012 router.
Usage Guidelines
The PacketCable Event Message specification (PKT-SP-EM-I03-011221) requires that each trusted PacketCable network element that generates an Event Message MUST identify itself with a static Element ID that is unique across an entire PacketCable domain. This command allows you to configure the CMTS with an Element ID that is unique for your particular network. If you do not manually configure this parameter with the packetcable element-id command, it defaults to a random value between 0 and 99,999 when PacketCable operations is enabled.
The CMTS includes the Element ID in its Event Messages, along with its timezone information. You can display the current value using the show packetcable global command.
Examples
The following example shows the Event Message Element ID for this particular CMTS being set to 12456:
Router# configure terminalRouter(config)# packetcable element-id 12456Pktcbl: Configured element ID 12456Router(config)#Related Commands
packetcable gate maxcount
To change the maximum number of PacketCable gate IDs in the gate database on the Cisco CMTS, use the packetcable gate maxcount command in global configuration mode. To reset the counter to its default value, use the no form of this command.
packetcable gate maxcount n
no packetcable gate maxcount
Syntax Description
Defaults
2097152 gate IDs
Command Modes
Global Configuration
Command History
Usage Guidelines
This command configures the number of gate IDs that the Cisco CMTS can store in its gate database. Because each PacketCable gate ID typically refers to both an upstream gate and a downstream gate, multiple this number by 2 to get the maximum number of gates that can be created on the CMTS.
Note
Examples
The following example shows the maximum number of gate IDs being set to 524288, which is sufficient for two cable interface line cards:
Router# configure terminalRouter(config)# packetcable gate maxcount 524288Router(config)#Related Commands
packetcable gate send-subscriberID
To include subscriber identification in GATE-OPEN and GATE-CLOSE gate control messages, use the packetcable gate send-subscriberID command in global configuration mode. To remove subscriber identification information from the gate control messages, use the no form of this command.
packetcable gate send-subscriberID
no packetcable gate send-subscriberID
Syntax Description
This command has no arguments or keywords.
Command Default
No subscriber identification information is provided in the GATE-OPEN and GATE-CLOSE gate control messages.
Command Modes
Global configuration (config)
Command History
12.3(23)BC1
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.
Examples
The following example enables gate control subscriber identification information using the packetcable gate send-subscriberID command:
Router(config)# packetcable gate send-subscriberIDRelated Commands
packetcable timer
To change the value of the different PacketCable Dynamic Quality of Service (DQoS) timers, use the packetcable timer command in global configuration mode. To reset a timer to its default value, use the no form of this command.
packetcable timer {T0 timer-value | T1 timer-value}
no packetcable timer {T0 | T1}
Syntax Description
Command Types
T0 has a default value of 30000 milliseconds (30 seconds).
T1 has a default value of 200000 milliseconds (200 seconds).
Command Modes
Global Configuration
Command History
Usage Guidelines
This command sets the following timers, which are defined in the PacketCable™ Dynamic Quality-of-Service Specification (PKT-SP-DQOS-I03-020116):
•
•
Note
Examples
The following example shows the T0 timer being set to 20 seconds (20,000 milliseconds):
Router# configure terminalRouter(config)# packetcable timer T0 20000Router(config)#Related Commands
penalty-period
To specify the time period that an enforced quality of service (QoS) profile should be in force for subscribers that violate their registered QoS profile, use the penalty-period command in enforce-rule configuration mode. To reset an enforce-rule to its default penalty period, use the no form of this command.
penalty-period minutes [time-of-day hour]
no penalty-periodminutes [time-of-day hour]
Syntax Description
Command Default
The default time period is 10080 minutes (7 days).
Command Modes
Enforce-rule configuration (enforce-rule)
Command History
Usage Guidelines
When a subscriber overconsumes the maximum bandwidth that is specified in the enforce-rule, the Cisco CMTS router can automatically switch the subscriber to an enforced QoS profile for the penalty period specified with the penalty-period command. When the penalty period expires, the Cisco CMTS router restores the subscriber to their registered QoS profile.
The penalty period continues across reboots of the cable modem, so a user cannot avoid the enforced QoS profile by trying to reset their modem and reregister on the cable network. This allows service providers to set an appropriate penalty for those users that consistently exceed the maximum bandwidth they have been allocated.
Note
When you change the configuration of a currently active enforce-rule, that rule begins using the new configuration immediately to manage the cable modems tracked by this enforce-rule.
Note
Examples
The following example shows an enforce-rule named "test" configured with a penalty period of 1440 minutes (1 day):
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# penalty-period 1440The following example shows an enforce-rule named "test" configured with a penalty period of 1440 minutes (1 day), but allowing removal of any CMs in penalty at 11:00 P.M.:
Router# configure terminalRouter(config)# cable qos enforce-rule testRouter(enforce-rule)# penalty-period 1440 time-of-day 23Related Commands
ping docsis
To determine whether a specific cable modem (CM) is reachable from the CMTS at the DOCSIS MAC layer, use the ping docsis command in privileged EXEC mode.
ping docsis {mac-addr | ip-addr | name fqdn} [count] [verbose]
Syntax Description
Defaults
If no count is specified, five DOCSIS ping packets are sent.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The DOCSIS ping is a unique Cisco patented technology that allows a cable operator to quickly diagnose the health of a channel between the CMTS router and any particular DOCSIS cable CPE device. The DOCSIS ping is similar in concept to the IP ping but uses the lower MAC layer instead of the datalink or transport layers. Using the MAC layer has two major advantages:
•
•
In addition to providing connectivity information, the ping docsis command provides a real-time view and plot of requested power adjustments, frequency, timing offset adjustments, and a measure of optimal headend reception power.
If a CM responds to the ping docsis command, but does not respond to an IP ping, the problem could be one of the following:
•
•
•
•
Note
Note
Table 28 explains the different characters that can appear in the output for the ping docsis command:
Note
Examples
The following example shows a default ping docsis command that sends five packets to the CM with the MAC address of 00d0.ba77.7595, with a response being received for each:
Router# ping docsis 00d0.ba77.7595Queueing 5 MAC-layer station maintenance intervals, timeout is 25 msec:!!!!!Success rate is 100 percent (5/5)Router#The following example shows the verbose output for the same command:
Router# ping docsis 00d0.ba77.7595 verboseQueueing 5 MAC-layer station maintenance intervals, timeout is 25 msec:Reply from 00d0.ba77.7595: 2 ms, tadj=-1, padj=0.50, fadj=0Reply from 00d0.ba77.7595: 2 ms, tadj=-1, padj=0.50, fadj=0Reply from 00d0.ba77.7595: 2 ms, tadj=-1, padj=0.50, fadj=0Reply from 00d0.ba77.7595: 98 ms, tadj=-1, padj=0.25, fadj=0Reply from 00d0.ba77.7595: 2 ms, tadj=-1, padj=0.25, fadj=0Success rate is 100 percent (5/5)Router#The following example shows that the CM at 192.168.100.10 is connected to the network and is operational, but that one ping packet was lost and that several power adjustments were made during the ping process:
router# ping docsis 192.168.100.10Queueing 100 MAC-layer station maintenance intervals, timeout is 25 msec:!!!!!a!!!!!!!a!a!!!!!!!!!!!!!!!!!!!!!aa!!!!!!!!!!a!!!a!a!!!aa!!!!!!.!!a!!!a!a!a!!!!!!!!aa!!!!!!!aa!aSuccess rate is 99 percent (99/100)A CM that displays output such as that above (a higher percentage of successful pings but with a number of power-adjustment readings) is most likely experiencing a problem that is not bad enough to force the modem offline but that should be addressed.
If this problem is consistent for just a small number of CMs on an upstream receiver (such as a fiber node within a combining group), then the problem is likely related to in-home wiring at those modem locations. It could also be due to a cable TV network element that is on the same HFC segment.
If the problem occurs for all CMs on a single fiber node, then changing the upstream frequency or reducing the number of homes passed per combining group might improve conditions. If this does not help the situation, the problem could be due to a faulty cable drop, dirty optical connector on the node, or other physical plant problem.
The ping docsis command cannot be used with a CM that has not yet registered with the CMTS. The following example shows the responses for a CM that has not yet registered with the CMTS.
router# ping docsis 192.168.100.111Cable modem with IP address 192.168.100.111 not registered.Please try using MAC address instead.router# ping docsis 0123.4567.89abCable modem with MAC address 0123.4567.89ab not registered.router#Related Commands
plim qos input map
To configure a priority queue on Gigabit Ethernet SPAs, use the plim qos input map command in interface or subinterface configuration mode. To remove a priority queue, use the no form of this command.
plim qos input map {cos {enable | cos-value queue low-latency} | ip {dscp-based | dscp dscp-value queue low-latency} | ip {precedence-based | precedence precedence-value queue low-latency} | ipv6 tc
