Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Reference
OL-15510-12
May 2010
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase,
Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip
Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work,
Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and
Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the
IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY,
PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are
registered trademarks of Cisco and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (1002R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Audience CBL-2
access-denied CBL-20
application-id CBL-27
auto-sync CBL-31
card CBL-657
channel-group CBL-664
cpd CBL-743
depi-class CBL-762
depi-tunnel CBL-764
dest-ip CBL-766
docsis-policy CBL-783
docsis-version CBL-784
download CBL-785
downstream CBL-787
dtmf-relay CBL-796
duration CBL-799
flowcontrol CBL-812
hold-queue CBL-851
init-tech-list CBL-865
init-tech-ovr CBL-866
interval CBL-880
mac-address CBL-922
main-cpu CBL-924
maintenance-mode CBL-926
method CBL-932
monitoring-basics CBL-943
monitoring-duration CBL-945
mtu CBL-947
name CBL-950
negotiation CBL-951
network CBL-953
nls CBL-954
oui CBL-957
output-rate CBL-958
override CBL-959
option CBL-960
packetcable CBL-965
peak-time1 CBL-974
penalty-period CBL-977
policy CBL-989
profile-description CBL-992
privacy CBL-994
rcp-id CBL-1004
receive-channel CBL-1005
receive-module CBL-1007
redundancy CBL-1009
revertive CBL-1024
service-class CBL-1061
service-type-id CBL-1063
session-range CBL-1065
CBL-1786
tag CBL-1946
threshold CBL-1957
timestamp CBL-1958
tos CBL-1960
upstream CBL-1965
voice-port CBL-1972
vrf (multicast qos) CBL-1973
CBL-1979
alias CBL-2208
boot CBL-2210
break CBL-2214
confreg CBL-2216
cont CBL-2219
context CBL-2221
cpu_card_type CBL-2223
dev CBL-2224
dir CBL-2226
dis CBL-2227
frame CBL-2229
help CBL-2231
history CBL-2233
meminfo CBL-2235
repeat CBL-2236
reset CBL-2238
set CBL-2240
show_spd CBL-2242
stack CBL-2245
sync CBL-2247
sysreset CBL-2249
unalias CBL-2251
unset CBL-2253
This introduction explains the objectives, intended audience, and organization of the Cisco IOS CMTS
Cable Command Reference. It provides the following sections:
• Document Objectives, page 1
• Audience, page 2
• Document Organization, page 2
• New and Modified Commands by Release, page 2
• Related Documents, page 17
• Obtaining Documentation and Submitting a Service Request, page 18
Document Objectives
Note Some of these products have reached End of Sale (EOS) or End of Life (EOL). For more information,
refer to the Video, Cable, and Content Delivery End-of-Sale and End-of-Life Products site at:
http://www.cisco.com/en/US/products/hw/video/prod_category_end_of_life.html
This guide describes the commands necessary to configure, maintain, and troubleshoot the following
cable platforms:
• Cisco Cable Modem Termination Systems (CMTS)
– Cisco uBR7100 series universal broadband routers, which include the Cisco uBR7111, the
Cisco uBR7114, the Cisco uBR7111E, and the Cisco uBR7114E routers.
– Cisco uBR7200 series universal broadband routers, which include the Cisco uBR7246, the
Cisco uBR7246 VXR, and the Cisco uBR7225VXR routers.
– Cisco uBR10012 universal broadband router.
• Cisco Cable Modems (CMs) and other Cable CPE Devices
– Cisco uBR904, Cisco uBR905, Cisco uBR924, and Cisco uBR925 cable access routers.
– Cisco CVA122 and Cisco CVA122E cable voice adapters.
Note This guide documents only the cable specific commands. For information about all Cisco IOS
commands, use the Command Lookup Tool or the Cisco IOS Master Command List, All Releases.
Audience
This book is intended for system administrators and support engineers who configure and maintain the
cable CMTS and CM devices.
Document Organization
This book is organized alphabetically. The first page of each chapter provides a command summary of
all commands included in that chapter, as well as identification of any new, modified, obsolete, or
replaced commands.
Debug commands and ROM monitor commands are included in separate appendixes at the end of the
book.
Note Command changes in Cisco IOS Release 12.3(23)BC, 12.3(23)BC1, and 12.3(23)BC2 do not apply to
Cisco IOS Release 12.2(33)SCA.
Note Command changes in Cisco IOS Release 12.3(23)BC5 do not apply to Cisco IOS Release 12.2(33)SCA.
Note Command changes in Cisco IOS Release 12.3(23)BC2 do not apply to Cisco IOS Release 12.2(33)SCA.
Note Command changes in Cisco IOS Release 12.3(23)BC1 do not apply to Cisco IOS Release 12.2(33)SCA.
Note Command changes in Cisco IOS Release 12.3(23)BC do not apply to Cisco IOS Release 12.2(33)SCA.
• receive-module
• service divert-rate-limit ip
• service divert-rate-limit ip trusted-site
• service divert-rate-limit non-ip
• service divert-rate-limit trusted-site
• show cable flap-list wb-rf
• show cable mac-domain rcc
• show cable modem auth-profile
• show cable modem service-type-id
• show cable modem summary wb-rf
• show cable modem wideband rcs-status
• show cable multicast authorization
• show cable multicast db
• show cable multicast dsid
• show cable multicast qos
• show cable rf-status
• show cable rsvp flow-db
• show interface rf-status
• show ipdr collector
• show ipdr exporter
• show ipdr session
• show ipdr session (collector)
• show ipdr session template
• show pxf cable multicast
• show pxf cpu drl-trusted-sites
• rf-channel network-delay
• show cable admission-control
• show cable flap-list
• show cable hop
• show cable load-balance
• show cable modem
• show cable modem cnr
• show cable modem flap
• show cable modem phy
• show cable modem qos
• show cable multicast dsid
• show cable service-class
• show controllers cable
• show controllers cable
• show controllers modular-cable
• show hccp
• show interface cable mac-scheduler
• show interface cable service-flow
• show interface cable upstream
• rf-channel rf-power
• show cable mac-domain cgd-associations
• show cable mac-domain downstream-service-group
• show cable mac-domain rcc
• show cable modem
• show cable multicast dsid
• show controller integrated-cable
• show interface cable privacy
• show interface cable service-flow
• show interface rf-status
• show interface wideband-cable
• upstream cable connector
Obsolete Commands
The following commands have been removed from certain Cisco IOS software releases:
Replaced Commands
The following commands have been replaced by new commands beginning in the following Cisco IOS
software releases:
Related Documents
This section lists the documents that provide more detailed hardware and software information about the
Cisco CMTS routers and Cisco Cable CPE devices documented in this guide. These documents are
available on Cisco.com and the customer documentation CD-ROM.
Note These products have reached End of Sale (EOS) or End of Life (EOL). For more information, refer to
the Video, Cable, and Content Delivery End-of-Sale and End-of-Life Products site at:
http://www.cisco.com/en/US/products/hw/video/prod_category_end_of_life.html
For detailed information about the Cisco cable CPE devices, see the following documents:
• Cisco uBR904 Installation and Configuration Guide
• Cisco uBR905/uBR925 Software Configuration Guide
• Cisco uBR905 Hardware Installation Guide
• Cisco uBR924 Software Configuration Guide
• Cisco uBR924 Hardware Installation Guide
• Cisco uBR925Hardware Installation Guide
• Cisco CVA122/CVA122E Features Guide
• Cisco CVA122/CVA122E Hardware Installation Guide
New Commands
Obsolete Commands
Replaced Commands
access-denied
To create a DOCSIS configuration file that disables network access to the customer premise equipment
(CPE) devices that are attached to the cable modem (CM) on a Cisco CMTS router, use the
access-denied command in cable config-file configuration mode. To enable access, use the no form of
this command.
access-denied
no access-denied
Usage Guidelines This command sets the Network Access Control object in the DOCSIS configuration file. If the object
is set to 1 (set by the default of no access-denied), the CPE devices behind the CM allow access to the
network. If the object is set to 0 (by configuration of the access-denied command) to disable network
access for the CPE devices, the CM does not forward traffic from its attached CPE devices.
For normal operation, the CM must be set to allow access (the default). However, to deny service for
reasons such as nonpayment or unauthorized use of services, the access-denied command can be used.
Examples The following example shows how to disable network access for the CPE devices that are connected to
the CM:
cable config-file disable.cm
access-denied
Command Description
frequency Specifies the downstream frequency.
option Specifies vendor-specific information fields in a DOCSIS configuration file.
privacy Specifies privacy options for baseline privacy images.
service-class Specifies service class definitions for the configuration file.
snmp manager Specifies Simple Network Management Protocol (SNMP) options.
timestamp Enables time-stamp generation.
activate-rule at-byte-count
Note Effective with Cisco IOS Release 12.3(9a)BC, the activate-rule at-byte-count command is not
available in Cisco IOS software.
To specify the number of bytes that a subscriber can transmit during the monitoring period on a Cisco
CMTS router, use the activate-rule at-byte-count command in enforce-rule configuration mode. To
reset the rule to its default values, use the no form of this command.
Syntax Description kbytes Maximum number of kilobytes that the subscriber can transmit in the
specified direction during the monitoring period. The valid range is 1
to 4294967, with a default of 0 (no limit).
Note To reset the kilobyte count to 0, use the no form of this
command.
downstream Specifies that the kilobyte count applies to traffic in the downstream di-
rection.
upstream Specifies that the kilobyte count applies to traffic in the upstream di-
rection. The default value is upstream.
enforce (Optional) Specifies that the enforce-rule QoS profile should be
applied automatically if a user violates the registered QoS profile.
Note You must have previously configured a registered QoS profile,
using the qos-profile registered command, before being able
to use the enforce keyword.
Command Default The kbytes value defaults to 0 (no limit), upstream direction, and enforce-rule QoS profiles are not
automatically applied (no activate-rule at-byte-count enforce).
Usage Guidelines The activate-rule at-byte-count command specifies the maximum number of bytes that a subscriber can
transmit during the monitor window period (see the monitoring-duration command). If a subscriber
transmits traffic beyond this maximum value, the CMTS router considers the subscriber to be
overconsuming.
If the optional enforce keyword has been specified for an enforce-rule, the CMTS router automatically
switches overconsuming subscribers to the enforced QoS profile (see the qos-profile enforced
command). The enforced QoS profile remains in force during the penalty time period (see the
qos-profile registered command).
An enforce-rule can be created for only one direction, either upstream or downstream. To activate
subscriber traffic management for both the upstream and downstream directions, create two different
enforce-rules, with one rule’s activate-rule-at-byte-count command specifying the downstream
direction and the other rule specifying the upstream direction.
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 the enforce-rule.
Note You can create an enforce-rule that is a duplicate of an existing enforce-rule, but the duplicate rule is not
activated and applied to service flows until at least one of its parameters is changed so that it has a unique
configuration.
Examples The following example shows a typical activate-rule-at-byte-count command for the downstream
direction:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# activate-rule at-byte-count 20 downstream
The following example shows a typical activate-rule-at-byte-count command for the upstream
direction. The enforce option is also added so that the enforce-rule QoS profile is automatically applied
to users who exceed their registered profile:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# activate-rule at-byte-count 5 upstream enforce
The following example shows the same command being given for a second enforce-rule. The system
rejects the command because it is a duplicate of an existing rule, using the same QoS profile and
direction. You must change at least one of the rule parameters to make it unique before it is mapped and
applied to service flows.
Router# configure terminal
Router(config)# cable qos enforce-rule test2
Router(enforce-rule)# activate-rule at-byte-count 5 upstream enforce
Enforce-rule test2 won't be mapped to service flows as it is duplicate of test1 with same
registered qos-profile 5 and same direction
Command Description
penalty-period Specifies the time period that an enforced QoS profile should be in
effect for subscribers that violate their registered QoS profiles.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate
their registered QoS profiles.
qos-profile registered Specifies the registered QoS profile that should be used for this
enforce-rule.
show cable qos enforce-rule Displays the QoS enforce-rules that are currently defined.
show cable subscriber-usage Displays subscribers who are violating their registered QoS profiles.
annex modulation
Note Effective with Cisco IOS Release 12.3(23)BC, the annex modulation command is obsolete and annex
and modulation are included as keyword options in the rf-channel frequency command.
To set the annex (MPEG framing format) and modulation for the Wideband SPA, use the
annex modulation command in controller configuration mode. To set the annex to B and the modulation
to 64 QAM, use the no form of this command.
Usage Guidelines Use this command to set the following on a Wideband SPA:
• Annex (MPEG framing format)
• Modulation
Examples The following example shows how to set the MPEG framing format and modulation for the Wideband
SPA located at slot 1, subslot 0, bay 0:
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# annex B modulation 64qam
application-id
To specify an application type to allow admission control to be applied to a group configuration, use the
application-id command in multicast QoS configuration mode. To disable admission control, use the no
form of this command.
application-id number
no application-id number
Syntax Description number Specifies the application identification number of the multicast QoS group.
The valid range is 1–65535.
Usage Guidelines In order to enable intelligent multicast admission control, you must enable and configure an application
type using the application-id command.
Examples The following example identifies a multicast QoS group application ID using the applicaton-id
command:
Router(config)# cable multicast qos group 20 priority 55 global
Router(config-mqos)# application-id 44
associate slot
To logically associate slots for automatic protection switching (APS) processor redundancy, use the
associate slot command in redundancy configuration mode. To disable slot associations, use the no form
of this command.
Single Router APS—Cisco 10000 Series Routers and Cisco uBR10012 Universal Broadband Router
Release Modification
12.0(26)S This command was integrated into Cisco IOS Release 12.0(26)S, and support
was added for the CHOC12, CHSTM1, OC32POS, and OC12POS line cards for
the Cisco 10000 series router.
12.2(4)XF1 This command was introduced for the Cisco uBR10012 router.
12.2(13)BC1 Support was added for the Cisco OC-48 DPT/POS adapter card on the Cisco
uBR10012 router.
12.2(31)SB This command was integrated into Cisco IOS Release 12.2(31)SB.
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA. Support
for the Cisco uBR7225VXR router was added.
Note You cannot use the associate command with any of the Performance Routing Engine (PRE) modules or
TCC+ cards, because these cards are automatically configured for redundant operation when two cards
are installed in the chassis.
auto-sync
To enable automatic synchronization of the configuration files in NVRAM, use the auto-sync command
in main-cpu redundancy configuration mode. To disable automatic synchronization, use the no form of
this command.
Defaults For the Performance Routing Engines (PREs) on the Cisco uBR10012 universal broadband router, the
system defaults to synchronizing all system files on the (auto-sync standard).
For the Supervisor Engines on the Cisco 7600 series routers, the system defaults to synchronizing the
running configuration. (running-config).
The following example shows how to configure the system to synchronize all system files except for the
startup configuration file. This typically is done when the two PRE1 (or PRE2) modules are running
different software images.
router(config)# redundancy
router(config-r)# main-cpu
router(config-r-mc)# no auto-sync startup-config
router(config-r-mc)# auto-sync config-register
router(config-r-mc)# auto-sync bootvar
router(config-r-mc)# exit
router(config-r)# exit
Related
Commands Command Description
redundancy Enters redundancy configuration mode.
main-cpu Enters main CPU redundancy configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines It is normally not necessary to enter this command in data-over-cable bridging applications because
DOCSIS-compliant bridging is enabled by default. However, to configure the router for full transparent
bridging or for routing mode, use the no form of the command and then configure the router as desired
using the appropriate CLI commands.
Examples The following example shows how to disable DOCSIS-compliant bridging on the cable interface:
Router# configure terminal
Router(config)# interface cable-modem 0
Router(config-if)# no cable-modem compliant bridge
Router(config-if)#
cable-modem dhcp-proxy
To specify that a Dynamic Host Configuration Protocol (DHCP) server should provide an IP address for
the router’s Ethernet interface, for the loopback interface, or for the router’s Network Address
Translation (NAT) address pool, use the cable-modem dhcp-proxy command in cable interface
configuration mode. To disable this feature so that you can then manually assign an IP address to the
Ethernet interface or NAT address pool, use the no form of this command.
Cisco uBR905, Cisco uBR924, Cisco uBR925 Cable Access Routers, and Cisco CVA122 Cable Voice Adapter
Note This command is available only when the router is configured for routing mode and cannot be used when
the router is configured for DOCSIS-compliant bridging.
Syntax Description interface ethernet number Identifies the Ethernet interface to be assigned the static IP address from
the DHCP server (always 0).
interface loopback number Identifies the loopback interface to be assigned the static IP address from
the DHCP server (always 0).
nat pool-name Specifies the name of the NAT pool to be created using the IP address and
subnet mask supplied by the DHCP server. (This option is equivalent to
giving the ip nat pool pool-name start-ip end-ip netmask subnet
command, using the IP address and subnet mask supplied by the DHCP
server.)
Note When replying to the proxy request for the Ethernet interface, the DHCP server should assign an IP
address that is on the same network as the customer premises equipment (CPE) devices that are attached
to the router’s Ethernet interface.
Tip If you have configured a Cisco CM for routing mode and are also using the cable-modem dhcp-proxy
nat command on the CM, you must configure the corresponding cable interface on the Cisco CMTS with
the cable dhcp-giaddr policy command.
The reason is that the default router configuration is for DOCSIS-compliant bridging, which includes
two bridge-group 59 commands for each interface. To use the cable-modem dhcp-proxy command,
you must put the router into routing mode, which means removing the bridge-group commands with the
equivalent no bridge-group commands.
However, because no bridge-group is the default for these CLI commands, they are not saved in the
running configuration. So when you save the Cisco IOS configuration file and copy it to other routers,
the router is only partially configured for routing mode and continually resets its interfaces.
In addition, whenever you use the cable-modem dhcp-proxy command to create a NAT pool, the router
automatically adds the appropriate ip nat pool commands to the configuration when it receives the actual
IP addresses from the DHCP server. The IP addresses specified in this command are particular to each
user and should not be copied to other routers.
To avoid this problem, use the following procedure to create a Cisco IOS configuration file that uses the
cable-modem dhcp-proxy command to create a NAT address pool for NAT/PAT address translation:
For example, the following are the relevant lines in a typical DHCP proxy NAT configuration for a cable
access router:
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
load-interval 30
!
interface cable-modem0
ip nat outside
load-interval 30
no cable-modem compliant bridge
cable-modem dhcp-proxy nat nat-pool
!
ip nat pool nat-pool 10.15.0.10 10.15.0.10 netmask 255.255.0.0
When you copy this configuration file to the TFTP server, modify this portion of the configuration file
to add the no bridge-group commands under each interface and to remove the ip nat pool command:
interface Ethernet0
ip address 192.168.1.1 255.255.255.0
ip nat inside
load-interval 30
no bridge-group 59
no bridge-group 59 spanning-disabled
!
interface cable-modem0
ip nat outside
load-interval 30
no cable-modem compliant bridge
Examples The following example shows how to configure the router so that it makes a proxy DHCP request to
obtain an IP address for its Ethernet interface:
Router(config)# interface c0
Router(config-if)# cable-modem dhcp-proxy interface ethernet 0
The following example creates a NAT address pool with the IP address assigned by the DHCP server;
this IP address must be in the network attached to the Ethernet address (which in this case is
192.168.100.0).
Router(config)# ip nat inside source list 1 pool net-208 overload
Router(config)# interface cable0
Router(config-if)# ip nat outside
Router(config-if)# no cable compliant bridge
Router(config-if)# cable-modem dhcp-proxy nat net-208
Router(config-if)# exit
Router(config)# interface ethernet0
Router(config-if)# ip address 192.168.100.94 255.255.255.0
Router(config-if)# ip nat inside
Router(config-if)# exit
Router(config)# access-list 1 permit 192.168.100.0 0.0.0.255
Router(config)#
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for
exclusive use by the DOCSIS provisioning process.
Syntax Description ds-frequency Downstream channel frequency in Hz, which can be from 91,000,000 to
860,000,000.
us-power Upstream power level in decibels per millivolt (dBmV), which can be from 8 to
61.
Usage Guidelines This command is auto-generated by the operation of the cable MAC layer process. The DOCSIS RFI
specification requires that CMs remember the downstream frequency and upstream power of the last
successfully ranged session. These arguments are called up as the first downstream frequency and
upstream power to use the next time the CM is booted. This operation dramatically speeds up the channel
search.
Use the no cable-modem downstream saved channel ds-frequency us-power command to remove the
saved frequency and power setting from the running configuration, which will be saved at the next
initialization cycle.
To comply with DOCSIS requirements, Cisco IOS Release 12.1(2)T removed this command from the
CLI for all platforms and reserved it for exclusive use by the DOCSIS provisioning process. This
command exists in earlier Cisco IOS versions, but Cisco recommends that this command NOT be used
by end users of Cisco cable CPE devices.
Examples The following example shows how to remove the downstream frequency of 91,000,000 Hz and the
upstream power level of 33 dBmV from the running configuration of a cable-modem interface:
Router(config)# interface cable-modem 0
Router(config-if)# no cable-modem downstream saved channel 91000000 33
Router(config-if)#
cable-modem fast-search
To enable a faster downstream search algorithm on the cable interface, use the cable-modem fast-search
command in cable interface configuration mode. To disable the downstream fast-search feature, use the
no form of this command.
cable-modem fast-search
no cable-modem fast-search
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for
exclusive use by the DOCSIS provisioning process.
Usage Guidelines This feature speeds up the frequency search performed by the cable access router. Normally it takes the
cable access router about 30 to 50 seconds to sample 30 to 50 frequencies. The cable-modem
fast-search command can reduce this search time. However, there might be some cases where this
fast-search algorithm might not perform as well as the default algorithm. Trial and error is the only way
to discover how well this feature works for your environment.
Examples The following example shows how to enable the faster downstream search algorithm on the router’s
cable interface:
Router(config)# interface cable-modem 0
Router(config-if)# cable-modem fast-search
Router(config-if)#
Cisco uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Command Modes Interface configuration and subinterface configuration (cable interface only)
Usage Guidelines TCP traffic uses a packet-acknowledge algorithm, where a group of packets must be acknowledged
before additional traffic can be sent. When a large number of packets is transmitted on the downstream,
it can result in a large number of acknowledgements on the upstream. Because the downstream
bandwidth is typically many times greater than the upstream bandwidth, certain applications can
temporarily overrun the upstream with a large volume of acknowledgement packets.
If any of those acknowledgements are dropped or lost, traffic can be backed up, and data packets might
have to be resent, even if those packets had in fact been successfully received. This can significantly
impact real-time traffic, such as voice calls.
To optimize the TCP traffic on the upstream in these circumstances, the Cisco uBR905, Cisco uBR924,
and Cisco uBR925 cable access routers and the Cisco CVA122 Cable Voice Adapters automatically
analyze the upstream traffic and drop unnecessary packet acknowledgements when traffic begins
backing up. This feature has been automatically enabled by default on the routers, starting with
Cisco IOS Release 12.0(5)T.
In some situations, however, this feature can result in packets being dropped on the upstream, which
could impact the performance of certain applications such as FTP transfers. If packet drops do occur on
the upstream, this feature can be turned off with the no cable-modem qos drop-ack command.
Examples The following example shows how to disable the TCP packet optimization feature on the cable interface,
so that all TCP packet acknowledgements are sent:
Router(config)# interface cable-modem 0
Router(config-if)# no cable-modem qos drop-ack
Router(config-if)#
The following example shows how to enable the TCP packet optimization feature on the cable interface.
This is the default configuration, so it does not need to be done unless it has been previously disabled.
Router(config)# interface cable-modem 0
Router(config-if)# cable-modem qos drop-ack
Router(config-if)#
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Examples The following example shows how to configure the cable interface for QPSK modulation on the
upstream:
Router(config)# interface cable-modem 0
Router(config-if)# cable-modem upstream preamble qpsk
Router(config-if)#
Note Cisco IOS Release 12.1(2)T removed this command from the CLI for all platforms and reserved it for
exclusive use by the DOCSIS provisioning process.
Usage Guidelines This command allows you to configure the voice traffic on a router to allow only calls having a
high-priority service identifier (SID) to be connected.
If the dynamic configuration of high-priority queues for voice traffic fails, or if the far end cannot
support the multiple SIDs and multiple classes of service required by high-priority traffic, the flag set
by this command will be checked. If enabled (the default setting), the call will be allowed to go through.
If disabled, the call will fail.
Examples The following example shows how to disable best-effort voice calls:
Router(config)# interface cable-modem 0
Router(config-if)# no cable-modem voip best-effort
Router(config-if)#
Cisco uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Command Default The default is to use the clock from the cable interface for VoIP calls.
Usage Guidelines This command enables the internal clock, allowing it to make VoIP calls over the Ethernet and USB
interfaces even when the cable interface is down or disconnected. If the CMTS is a Cisco uBR7200 series
with a Cable Clock Card, this command disables the use of that clock.
This command can be used in both DOCSIS IP bridging and routing mode. However, when operating in
DOCSIS IP bridging mode, VoIP packets are transmitted out only on the cable interface, so the router
must be operating in routing mode to transmit voice packets out the Ethernet and USB interfaces.
Examples The following example shows how to enable the internal clock for VoIP calls:
Router(config)# interface cable0
Router(config-if)# cable-modem voip clock-internal
Router(config-if)#
Command Description
cable-modem fast-search Enables a faster downstream search algorithm on the
cable interface.
cable-modem upstream preamble qpsk Enables the QPSK modulation scheme in the upstream
direction from the cable interface to the CMTS.
New Commands
Modified Commands
cable admission-control
To configure the CPU and memory thresholds for a Cisco CMTS router supporting broadband processing
engines (BPEs), use the cable admission-control command in global configuration mode. This
command sets the CPU averaging method and memory thresholds. To remove thresholds from a Cisco
CMTS router, use the no form of this command.
Syntax Description cpu-5sec This keyword sets Admission Control thresholds on the Cisco CMTS based on a
five-second average for the CPU. This setting must be combined with the additional
minor, major and critical threshold percentage values.
cpu-avg This keyword sets Admission Control thresholds on the Cisco CMTS based on a
one-minute average for the CPU. This setting must be combined with the additional
minor, major and critical threshold percentage values.
io-mem This keyword sets Admission Control thresholds for input/output (IO) memory on the
Cisco CMTS route processors and BPE processors.
proc-mem This keyword sets Admission Control thresholds according to CPU processor
memory on the Cisco CMTS.
total-memory This keyword sets Admission Control thresholds on the Cisco CMTS according to
total-memory allocation.
minor num1 Keyword sets the minor threshold level for the CPU or memory resource to be
configured. Num1 expresses a percentage and must be an integer between 1 and 100.
major num2 Keyword sets the major threshold level for the CPU or memory resource to be
configured. Num2 expresses a percentage and must be an integer between 1 and 100.
critical num3 Keyword sets the critical threshold level for the CPU or memory resource to be
configured. Num3 expresses a percentage and must be an integer between 1 and 100.
Command Default By default, admission control is disabled with no CPU or memory resource threshold settings on the
Cisco CMTS router.
Usage Guidelines The threshold counters are set to zero when the resource is reconfigured.
An important concept for system resources that are set with this command (CPU and memory) is the
concept of dampening. Without dampening, and when admission control is configured for the first time,
the system resource check is unsuccessful if the current value exceeds the critical threshold. When this
happens, the system resource check subsequently succeeds only if the current value drops below the
major threshold.
Note When the minor threshold value set with Num1 or a major threshold value set with Num2 is crossed, the
Cisco CMTS router sends an alarm (SNMP trap, when supported). When the critical threshold value set
with Num3 is crossed, the Cisco CMTS router drops the call request.
This dampening approach helps prevent significant fluctuations in the outcome of resource checks. For
example, if the critical threshold were 80 percent and the current values fluctuated between 79 and 81
percent, this scenario would lead to an alternate success then failure event without dampening. The first
check would succeed, the second check would fail, and so forth.
For additional Admission Control feature information, refer to the Admission Control for the Cisco
Cable Modem Termination System document on Cisco.com.
Examples The following example configures the Cisco CMTS router with a Quality of Service (QoS) policy that
includes admission control dampening. This example illustrates the following conditions:
• When the cpu-avg exceeds 60%, a minor alarm (SNMP trap, when supported) is sent.
• When the cpu-avg exceeds 70%, a major alarm (SNMP trap, when supported) is sent.
• When the cpu-avg exceeds 80%, the incoming call request is rejected, and additional calls are not
accepted until after the cpu-avg returns to below 60% (the minor alarm level).
Router(config)# cable admission-control cpu-avg minor 60 major 70 critical 80
Command Default Admission control is disabled by default on the Cisco CMTS router.
Usage Guidelines Downstream bandwidth settings support all interfaces on the Cisco CMTS router through global
configuration.
Downstream bandwidth settings can be further refined per-interface or per-upstream, the latter of which
provides optimal downstream Admission Control granularity on the Cisco CMTS router.
When interface-level downstream configuration is used in combination with global configuration, then
the interface configuration supersedes global configuration.
Note The critical keyword is not present for the upstream throughput resource management with the Cisco
Service Flow Admission Control feature.
Note The minor threshold level cannot be greater than the major threshold level.
Examples The following example configures downstream bandwidth in the global configuration mode, with 30%
of downstream bandwidth reserved exclusively for voice traffic. Minor and major alarms for voice traffic
are also set to be generated at 15% and 25% respectively.
Router(config)# cable admission-control ds-bandwidth voice minor 15 major 25 exclusive 30
Command Description
debug cable admission-control Enables automatic admission control troubleshooting
processes on the Cisco CMTS router.
show cable admission-control Displays the current admission control configuration and
status on the Cisco CMTS router or on a specified interface.
Syntax Description cm-registration Performs admission control checks when a cable modem registers with the Cisco
CMTS router headend. This setting can be combined with the dynamic-service
setting, in which cable modems are allowed to register but remain subject to a
Quality of Service (QoS) policy on the Cisco CMTS.
dynamic-service Performs admission control checks each time a voice call is made, and rejects
voice calls if they would impede QoS policies on the Cisco CMTS router. This
setting can be combined with the cm-registration setting.
Command Default Admission control event types are not defined on the Cisco CMTS router.
Usage Guidelines At least one event type must be configured in order to enable admission control on the Cisco CMTS
router.
For additional Admission Control feature information, refer to the Admission Control for the Cisco
Cable Modem Termination System document on Cisco.com.
Examples The following example configures each available option for the cable admission-control event
command on the Cisco CMTS router.
Router(config)# cable admission-control event cm-registration
Router(config)# cable admission-control dynamic-service
Syntax Description bw-in-kbps Maximum admission control reserved bandwidth. The value is in kbps and
is based on the RF bandwidth percent defined for the bonding group. Valid
range is from 0 to 14762.
Command Default The max-reserved-bandwidth value is 80 percent of the aggregate bandwidth of the RF channels
configured in the US or DS bonding group.
Usage Guidelines This command allows the user to define the maximum reserved bandwidth per bonding group. The
default maximum reserved bandwidth value is 80 percent. However the user can choose to configure a
higher (up to 96 percent) or lower reserved bandwidth so that there is bandwidth allocated for zero
committed information rate (CIR) best effort traffic.
Examples The following example shows a sample definition of the maximum reserved bandwidth value.
Router> enable
Router# configure terminal
Router(config)# interface c5/0/1
Router(config-if)# cable admission-control max-reserved-bandwidth 6344
Command Description
cable admission-control Configures admission control downstream bandwidth thresholds on the
ds-bandwidth Cisco CMTS router.
cable admission-control Configures admission control upstream bandwidth thresholds on the Cisco
us-bandwidth CMTS router.
debug cable Enables automatic admission control troubleshooting processes on the
admission-control Cisco CMTS router.
show cable Displays the current admission control configuration and status on the
admission-control Cisco CMTS router or on a specified interface.
Defaults Emergency 911 call preemption and service flow admission control is enabled on the Cisco CMTS
router.
Usage Guidelines By default, PacketCable Emergency 911 calls are given priority on the Cisco CMTS. This priority may
be preempted or removed from the Cisco CMTS router with non-standard configuration of the Service
Flow Admission Control feature.
For additional information for Service Flow Admission Control beginning in Cisco IOS Release
12.3(21)BC, refer to the Service Flow Admission Control for the Cisco Cable Modem Termination
System document on Cisco.com.
Examples The following example disables and then restores emergency 911 call preemption on the Cisco CMTS
router.
Router(config)# no cable admission-control preempt priority-voice
Router(config)# cable admission-control preempt priority-voice
Usage Guidelines Upstream bandwidth settings support all interfaces on a Cisco CMTS router through global
configuration.
Upstream bandwidth settings can be further refined on a per-interface or per-upstream basis using
interface configuration mode. Per-upstream settings provide the optimal upstream admission control
granularity on the Cisco CMTS router.
When interface or per-upstream configuration is used in combination with global configuration, then
interface or per-upstream configuration supersedes global configuration. Per-upstream configuration
also supersedes per-interface configuration.
Note The critical keyword is not present for the upstream throughput resource management with Cisco
Admission Control.
Note The minor threshold level cannot be greater than the major threshold level.
Examples For additional Admission Control feature information and examples, refer to the Admission Control for
the Cisco Cable Modem Termination System document on Cisco.com.
Command Description
debug cable admission-control Enables automatic admission control troubleshooting
processes on the Cisco CMTS router.
show cable admission-control Displays the current admission control configuration and
status on the Cisco CMTS router or on a specified
interface.
Syntax Description bucket-number Bucket number to which an application type is associated. Range is from
1 to 8, with 1 as the first in the sequence.
Best-effort Applies best effort committed information rate (CIR) to the specified
bucket.
multicast application-id Specifies the application identification for the multicast service flow. The
valid range is 1 to 65535.
packetcable {normal | Specifies PacketCable service flows for the designated bucket, with the
priority} following priorities:
• normal—Selects PacketCable calls with normal priority.
• priority—Selects PacketCable calls with high priority.
pcmm {app-id gate-app-id Specifies PacketCable Multimedia (PCMM) service flows for the
| priority gate-priority} designated bucket, with the following options:
• app-id gate-app-id—Selects the gate application identifier from 0 to
65535. For each bucket, up to ten application type rules may be
defined.
• priority gate-priority—Selects the priority level from 0 to 7.
sched-type type Specifies upstream scheduling types, with one of the following additional
keywords used for the DOCSIS scheduling type:
• be—Best effort.
• nrtps—Non-real-time polling service.
• rtps—Real-time polling service.
• ugs—Unsolicited Grant Service.
• ugs-ad—UGS-AD (unsolicited grant service-activity detection)
service.
service-class Specifies the name of the service class being assigned to the designated
service-class-name bucket, where service-class-name is an alphanumeric string.
Command Default Service flow admission control is enabled without the application types.
Usage Guidelines The details of this command vary according to the bucket number and application type being mapped to
a service flow on the Cisco CMTS router. This command overrides default service flow admission
control settings on the Cisco CMTS.
Best Effort
The best effort CIR service flow rule may be applicable to both upstream and downstream. However, in
the case of upstream service flows, in most cases, the same service flow may map both the rules.
For best effort, there is also the sched-type keyword option that applies to upstream service flows. This
best effort scheduling type rule is applicable only for upstream service flows.
Service Classes
DOCSIS 1.1 introduced the concept of service classes. A service class is identified by a service class
name. A service class name is a string the CMTS router associates with a QoS parameter set. One of the
objectives of using a service class is to allow the high-level protocols to create the service flows with the
desired QoS parameter set. Using a service class is a convenient way to bind the application with the
service flows. The rules provide a mechanism to implement such binding.
Note the following factors when using the service-class keyword:
• Service classes are separately configured using the cable match command to provide the QoS for
multicast traffic. This step maps a bucket using a rule to allocate bandwidth for multicast traffic.
• A named service class may be classified into any application type.
• Up to ten service class names may be configured per application type. Attempting to configure more
than ten service classes results in an error message.
For additional information, refer to the Service Flow Admission Control feature documentation on
Cisco.com.
Examples The following example maps high-priority PacketCable service flows into application bucket 5:
Router(config)# cable application-type 5 include packetcable priority
The following example maps normal PacketCable service flows into application bucket 1:
Router(config)# cable application-type 1 include packetcable normal
The following example maps the specified bucket number with PCMM service flow with a priority of 7,
then maps an application identifier of 152 for the same bucket number:
Router(config)# cable application-type 2 include pcmm priority 7
Router(config)# cable application-type 2 include pcmm app-id 152
The following example maps both UGS and UGS-AD into bucket number 1:
Router(config)# cable application-type 1 include sched-type ugs
Router(config)# cable application-type 1 include sched-type ugs-ad
The following example maps the best effort CIR flows to bucket 3:
Router(config)# cable application-type 3 include Best-effort
The following example maps the service class name with a value of service-name1 into application
bucket 3:
Router(config)# cable application-type 3 include service-class service-name1
The following example maps the multicast application type with a value of 18 into application bucket 3:
Router(config)# cable application-type 3 include multicast 18
Syntax Description bucket-number Bucket number to which the name is applied. The priority sequence of the
buckets, according to their original numeration of 1 to 8, still applies, whether
the default bucket numbers or customized alphanumeric names are used.
bucket-name Alphanumeric bucket name.
Command Default Service flow admission control and the default configuration of this command is enabled.
Usage Guidelines This bucket name appears in supporting show and debug commands along with the default bucket
number.
For additional information, refer to the Service Flow Admission Control feature documentation on
Cisco.com.
Examples The following example illustrates the use of descriptive names for the associated buckets:
Router(config)# cable application-type 2 name video
Router(config)# cable application-type 3 name gaming
cable arp
To activate cable Address Resolution Protocol (ARP), use the cable arp command in cable interface or
subinterface configuration mode. To block ARP requests for cable modems (CMs), use the no form of
this command.
cable arp
no cable arp
Usage Guidelines ARP is an Internet protocol used to map IP addresses to MAC addresses on computers and other
equipment installed in a network. You must activate ARP requests so that the Cisco CMTS router can
perform IP address resolution on the downstream path.
Occasionally, you might want to use the no cable arp and clear arp-cache commands to block out new
ARP requests and clear the existing ARP table. In this situation, the Cisco CMTS router will retain the
ARP addresses of currently online CMs (CMs with a known IP address) and will continue to send ARP
requests for those CMs when those ARP entries time out or are cleared, so that those CMs can continue
to remain online. ARP requests for CMs that are currently offline and for any other unknown IP
addresses, however, will remain blocked until ARP requests are reenabled on the downstream using the
cable arp command.
Note Using the no cable arp and no cable proxy-arp commands shifts all responsibility for the management
of the IP addresses used by CMs and CPE devices to the DHCP server and provisioning system.
Tip You can expect to see a temporary spike in CPU usage after initially giving the no cable arp command,
because of the need to verify CPE IP addresses. CPU usage drops after the router has verified and learned
all of the CPE IP addresses that are currently online. (This same situation occurs after initially enabling
the cable source-verify dhcp command, because the router must send a DHCP LEASEQUERY request
for every unknown CPE IP address.)
Examples The following example shows how to activate cable ARP requests for port 0 on the cable interface line
card installed in slot 6 of a Cisco CMTS router:
router(config)# interface cable 6/0
router(config-if)# cable arp
The following example shows how to activate cable ARP requests for port 0 on the cable interface line
card installed in slot 6, subinterface 1, of a Cisco CMTS router:
router(config)# interface cable 6/0.1
router(config-subif)# cable arp
Syntax Description reply-accept Configures the cable interface to accept only the specified
number of ARP reply packets every window-size seconds for each
active Service ID (SID) on that interface. The cable interface
drops ARP reply packets for a SID that would exceed this
number.
request-send Configures the cable interface to send only the specified number
of ARP request packets every window-size seconds for each
active SID on that interface. The cable interface drops ARP
requests for a SID that would exceed this number.
number Number of ARP reply packets that is allowed for each SID within
the window time period. The allowable range is 0 to 20 packets,
with a default of 4 packets. If number is 0, the cable interface
drops all ARP reply packets.
window-size Size of the window time period, in seconds, in which to monitor
ARP requests. The valid range is 1 to 5 seconds, with a default of
2 seconds.
Command Default ARP packets are not filtered, which means the Cisco CMTS router accepts all ARP reply packets and
sends all ARP request packets.
Usage Guidelines Viruses, worms, and theft-of-service attacks can generate a large volume of ARP requests on a cable
interface. In some situations, the volume of ARP traffic can become so large that it throttles all other
traffic.
To control the number of ARP replies and ARP requests that are allowed for each SID on a cable
interface, use the cable arp filter command. This command configures the interface so that it accepts
only a certain number of ARP reply or request packets per a specified time period. If a SID generates
more ARP packets than what is allowed, the cable interface drops the excessive traffic.
By default, no ARP filtering is done. ARP filtering is enabled on individual cable interfaces, and you
can choose to filter ARP packets only on the specific cable interfaces that require it. You can further
choose to filter only ARP request packets, only ARP reply packets, or both. You can configure different
threshold values on each interface, allowing you to customize the feature for each interface’s traffic
patterns.
If using bundled cable interfaces, the Cable ARP Filtering feature is configured separately on the master
and slave interfaces. This allows you to configure the feature only on the particular interfaces that require
it.
Note Cisco IOS Release 12.3(9a)BC introduces enhanced command option syntax for the cable arp filter
command, where number and window-size values are optional for reply-accept and request-send
settings.
Note Disabling the cable ARP filtering feature, using the no cable arp filter command, does not reset the ARP
packet counters. The ARP packet counters do not increment when cable ARP filtering is disabled, but
the counters retain their current values until the interface counters are specifically cleared, using the
clear counters command.
The following example shows how to filter cable ARP request packets, so that the cable interface sends
a maximum of 10 requests per second per SID:
Router(config)# interface cable 6/0
Router(config-if)# cable arp filter request-send 10 1
The following example shows how to enable the filtering of cable ARP request and reply packets on a
cable interface, using the default values of 4 packets per CPE per every 2 seconds:
Router(config)# interface cable 3/0
Router(config-if)# default cable arp filter reply-accept
Router(config-if)# default cable arp filter request-send
Router(config-if)# end
Router# show running-config | include filter
The following example shows how to disable the filtering of cable ARP request and reply packets on a
cable interface:
Router(config)# interface cable 1/0
Router(config-if)# no cable arp filter reply-accept
Router(config-if)# no cable arp filter request-send
cable attribute-mask
To configure an attribute for a modular cable interface, use the cable attribute-mask command in
interface configuration mode. To disable this configuration, use the no form of this command.
Syntax Description mask Specifies the mask value for the interface.
Command Default If this command is not used, the default attribute will be used for the modular cable interface. The default
attribute for a modular cable interface is zero.
Usage Guidelines The attribute mask comprises 32 attributes and each attribute represents a single bit in the mask. You can
configure a provisioned attribute mask for each channel and provisioned bonding group to assign values
to the operator-defined binary attributes, or to override the default values of the specification-defined
attributes. The operator may configure, in the CM configuration file, a required attribute mask and a
forbidden attribute mask for a service flow. Additionally, in a CM-initiated dynamic service request, the
CM can include a required attribute mask and a forbidden attribute mask for a service flow.
Examples The following example shows how to configure an attribute for a modular cable interface:
Router# configure terminal
Router(config)# interface modular-cable 1/0/0:0
Router(config-if)# cable attribute-mask 2000ff00
cable bonding-group-id
To specify a Bonding Group ID and indicate whether the bonding group is a primary or secondary
bonded channel, use the cable bonding-group-id command in wideband-cable interface configuration
mode. To remove a bonding group configuration and revert to the default bonding group (a primary
bonding group), use the no form of this command.
Syntax Description id_num A unique Bonding Group ID. Valid values are 1 to 255. The bonding group
ID must be unique for each wideband channel on the CMTS.
secondary Specifies that the bonding group is a secondary bonding group. If the
secondary keyword is not used, the bonding group is a primary bonding
group.
Command Default If the cable bonding-group-id command is not issued, Cisco IOS software assigns a default ID to the
bonding group and configures the wideband-channel cable interface as a primary bonding group.
Usage Guidelines The cable bonding-group-id command is not needed for the wideband channels that will be received
by the Scientific Atlanta DPC2505 or EPC2505 wideband cable modems.
The cable bonding-group-id command is used only for wideband channels that will be received by the
Linksys WCM300-NA, WCM300-EURO, or WCM300-JP wideband cable modems.
The primary bonded channel is the wideband channel on which the Linksys WCM300 modem receives
all of its unicast traffic and some of its multicast traffic. The cable modem may identify the primary
bonded channel and any secondary bonded channels to the CMTS at cable modem registration time. The
DOCSIS configuration file may define the primary bonded channel for the CMTS to assign to the cable
modem.
In addition to joining one primary bonded channel, the Linksys WCM300 may join up to two secondary
bonded channels simultaneously in order to receive additional data streams. The DOCSIS configuration
file may define the secondary bonded channels for the modem to pass to the CMTS. Secondary bonded
channels are intended to receive multicast traffic such as broadcast video that is not available on the
primary bonded channel.
For information on the TLV encodings that can be used in the DOCSIS configuration file to identify
primary and secondary bonded channels, see the Cisco Cable Wideband Solution Design and
Implementation Guide, Release 1.0.
Note If a wideband channel is specified as a primary or secondary bonded channel in the DOCSIS
configuration file, it must be identically defined as a primary or secondary bonded channel in the CMTS
active, running configuration file.
Note When a wideband channel is defined on a Wideband SPA, Cisco IOS software configures the wideband
channel as a primary bonding group (primary bonded channel) and assigns a default ID to the bonding
group. If a wideband channel is to be used as a secondary bonded channel, use the cable
bonding-group-id command with the secondary keyword to specify that the channel is a secondary
bonded channel.
If you specify a non-unique Bonding Group ID for the id_num argument, cable bonding-group-id
displays an error message and does not modify the ID.
Examples The following examples show how to use the cable bonding-group-id command for a variety of
purposes. The following cable bonding-group-id command specifies that wideband channel 10 on the
Wideband SPA in slot/subslot/bay 1/0/1 will be a secondary bonding group (secondary bonded channel)
having the bonding group ID 20.
Router# configure terminal
Router(config)# interface wideband-cable 1/0/1:10
Router(config-if)# cable bonding-group-id 20 secondary
The following example shows how to change a bonding group with an ID of 20 from a secondary to a
primary bonding group by omitting the secondary keyword:
The no form of the cable bonding-group-id removes the configured bonding group and reverts the
configuration to the default bonding group. For a secondary bonding group with the ID of 20, the
following no forms of the command are equivalent:
Router(config-if)# no cable bonding-group-id 20
or
Router(config-if)# no cable bonding-group-id 20 secondary
When either of the preceding commands are issued, the wideband-channel cable interface is
configured to use a default bonding group, which has a default bonding group ID assigned
by Cisco IOS software and is a primary bonding group.
cable bundle
To configure a cable interface to belong to an interface bundle, use the cable bundle command in cable
interface configuration mode. To delete a cable interface bundle definition, use the no form of this
command.
Syntax Description n Specifies the bundle identifier. Valid range is from 1 to 255.
master (Optional) Defines the specified interface as the master.
Usage Guidelines You can configure a maximum of four interface bundles. In each bundle, specify one interface as the
master interface by using the optional master keyword. The cable interface that is designated as master
is configured with Layer 3 configuration such as primary and secondary IP addresses and other Layer 3
specific configuration commands such as the cable arp command.
The following guidelines are required when using bundled cable interfaces:
• Configure an IP address only on the master interface. Any attempt to add an interface to a bundle is
rejected, if an IP address is configured and the interface is not specified as master interface.
• You must specify all generic IP networking information (IP address, routing protocols, switching
modes, and so on) on the bundle master interface. Do not specify generic IP networking information
on bundle slave interfaces.
• If you attempt to add an interface to a bundle as slave interface and an IP address is assigned to this
interface, the command fails. You must remove the IP address configuration before you can add the
interface to a bundle.
• If you have configured an IP address on a bundled interface and the interface is not the master
interface, a warning message appears.
• Do not create subinterfaces on a slave interface. In Cisco IOS Release 12.2(15)BC2 and later
releases, this is specifically prohibited. In prior releases, a warning message appeared when trying
to create a subinterface on a slave interface, but the subinterface was still created.
Specify generic (that is, not downstream or upstream) cable interface configurations, such as
source-verify or Address Resolution Protocol (ARP) handling, on the master interface. Do not specify
generic configuration on nonmaster interfaces.
If you configure an interface as part of a bundle and it is not the master interface, all generic cable
configuration for this interface is removed. This includes the IP address, access groups, PIM
configuration, and any other IP Layer 3 configurations. The master interface configuration then applies
to all interfaces in the bundle.
Tip We recommend configuring the no ip address command on all slave interfaces. This command is
optional but recommended, because the show ip interface brief command reports an interface as being
not OK if its configuration does not include some form of the ip address command. Specifying no ip
address corrects this.
When creating subinterfaces over the bundle master, the bundle master is not assigned any IP address
and only the subinterfaces are assigned IP addresses, helper addresses, and other Layer 3 configurations.
The reason the bundle master is not assigned an IP address is because CMs are associated with
subinterfaces rather than with a bundle master.
Note Cable interface bundling is applicable only in two-way cable configurations. It is not supported in
telco-return configurations.
If you shut down or remove the master interface in a bundle, no data packets is sent to any of the
interfaces in this bundle. Packets are still physically received from nonmaster interfaces that have not
been shut down, but those packets are discarded. This means that CMs connected to those interfaces are
not disconnected immediately, but CMs coming online are not able to obtain an IP address, download
their configuration file, or renew their IP address assignment if the DHCP lease expires.
If you shut down a slave interface, only this shutdown interface is affected.
Note When using bundled interfaces, the show interface cable command divides the interface counters
between the master and slave interfaces. The output for the master interface shows the upstream packets
per second count, while the output for the slave interfaces shows the downstream packets per second
count.
Examples See the following example to configure interface 25 to be the master interface:
Router(config)# interface cable 3/0
Router(config-if)# cable bundle 25 master
Router(config-if)#
07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down
07:28:18: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to up
The following example shows the error message you get if you try to configure an interface with an
IP address that is not the master interface:
Router(config)# interface cable 3/0
Router(config-if)# cable bundle 5
Please remove ip address config first then reenter this command
Router(config-if)#
The following example shows how to remove a cable interface from a bundle:
Router(config)# interface cable 5/1/0
Router(config-if)# no cable bundle 5
Router(config-if)#
Note When you remove a slave cable interface from a bundle (using the no cable bundle command), you must
manually reconfigure all of the Layer 3 IP information on the interface, before cable modems can resume
communicating on that interface.
Usage Guidelines This command resets any counters that were displayed from the last time the show controllers
clock-reference command was used.
This command supports the Cisco CMTS clock feature set, which provides a synchronized clock for
improved Voice-over-IP (VoIP) operations. The clock feature set requires one of the following
configurations:
• A Cisco uBR10012 router with one or two TCC+ cards that are connected to an external national
clock source.
Note Beginning in Cisco IOS Release 12.3(23)BC, TCC+ is replaced with the DOCSIS Timing
and Control Card (DTCC) and does not require to be connected to an extenal national clock
source.
Note The show controllers clock-reference command might display compare errors on the Cisco uBR10012
router because there could be a slight delay at system startup before the clock cards synchronize with
each other. These initial compare errors can be ignored and cleared with the cable clock clear-counters
command.
Examples The following example shows how to reset all counters that are displayed for the clock card:
Router# cable clock clear-counters
Usage Guidelines Use this command to configure DTI clocking mode. This command may be stored in NVRAM as part
of the DOCSIS Timing and Control Card (DTCC) configuration.
Syntax Description slot/subslot Specifies the slot and subslot location of the DTCC ports. Valid values are
1/1 or 2/1.
Usage Guidelines This command resets any counters that were displayed from the last time the show cable clock dti client
command was used in DTI mode.
This command supports the Cisco CMTS clock feature set, which provides a synchronized clock for
improved Voice-over-IP (VoIP) operations.
Examples The following example shows how to reset all counters that are displayed for the clock card:
Router# cable clock dti clear-counters
Syntax Description primary Forces the primary source to act as the clock reference.
secondary Forces the secondary source to act as the clock reference.
Command Default The clock card automatically uses the primary external source, if available. If the primary source fails,
the clock card enters holdover mode and, after a few seconds, switches to the secondary external source.
The clock card switches back to the primary source when it becomes available.
Usage Guidelines This command overrides the default behavior of the clock card when the clock card is in holdover mode.
If the clock card is not in holdover mode, this command is ignored. You cannot force the reference to a
port if the clock card is in free-running mode.
Note The clock card enters holdover mode if the forced reference is lost, even if the other external reference
is available.
To support the clock feature set in VoIP configurations, a Cisco uBR7246 VXR chassis, equipped with
a clock card; and a Cisco uBR-MC16S, a Cisco uBR-MC16E, or a Cisco uBR-MC28C cable interface
line card must be used running Cisco IOS Release 12.1(1a)T1 or later releases. Only these cable
interface line cards support the external clock card reference from a clock card to distribute that signal
to CMs or set-top boxes (STBs) attached to the specific network segments. You can use other cable
interface cards, such as the Cisco uBR-MC16C, with the clock card, but these other cable interfaces will
not synchronize their downstream SYNC messages with the external clock source.
Each CM or STB must also support VoIP applications and the clock feature set. For example, the
Cisco uBR924, running Cisco IOS Release 12.0(7)T or later releases, supports the clock card feature
automatically.
Examples The following example shows how to force the timing reference for the cable clock card to come from
the secondary external source, when the clock card is in holdover mode:
Router(config)# cable clock force secondary
Command Default The clock card does not get its timing reference from the midplane TDM clock.
Usage Guidelines Because the clock card automatically provides the timing reference to the midplane TDM clock, the
midplane cannot in turn act as the reference for the clock card. This means that the cable clock
source-midplane command does not take effect unless a port adapter is configured as the primary clock
reference source for the midplane.
To support the clock feature set in VoIP configurations, a Cisco uBR7246 VXR chassis, equipped with
a clock card; and a Cisco uBR-MC16S, a Cisco uBR-MC16E, or a Cisco uBR-MC28C cable interface
line card must be used running Cisco IOS Release 12.1(1a)T1 or higher releases. Only these cable
interface line cards support the external clock card reference from a clock card to distribute that signal
to CMs or set-top boxes (STBs) attached to the specific network segments. You can use other cable
interface cards, such as the Cisco uBR-MC16C, with the clock card, but these other cable interfaces will
not synchronize their downstream SYNC messages with the external clock source.
Each CM or STB must also support VoIP applications and the clock feature set. The Cisco uBR924,
running Cisco IOS Release 12.0(7)T or later releases, supports the clock card feature automatically.
Examples The following example shows how to set the primary clock reference to the midplane TDM clock:
Router(config)# cable clock source-midplane
Syntax Description slot Chassis slot number of the DTCC card. The valid slot is 1.
subslot Secondary slot number of the DTCC card. Valid subslots are 1 or 2.
Usage Guidelines In Cisco IOS Release 12.2(33) SCC and later, you can manually upgrade the FPGA image only if a single
DTCC card is installed on the Cisco uBR 10012 router. If the manual upgrade fails or is interrupted, the
DTCC card may become unusable. Do not reset or unplug the DTCC card during the manual upgrade.
We recommend that you take precaution against extended downtime if the FPGA upgrade fails
unexpectedly by having a standby DTCC card installed on the Cisco uBR10012 router.
Note You will have to enter y (yes) when the system prompts you to continue the manual upgrade.
Examples The following example shows how to start the manual FPGA upgrade process on the DTCC card:
Router# cable clock upgrade 1/1
Syntax Description time Specifies the time period, in seconds, that the Cisco CMTS router should consider the current
CM/CPE list to be valid. In Cisco IOS Release 12.2(15)BC1 and earlier releases, the valid
range is 0 to 3600 seconds, with a default value of 180 seconds (3 minutes). In Cisco IOS
Release 12.2(15)BC2 and later releases, the valid range is 0 to 86400 seconds, with a default
value of 900 seconds (15 minutes).
Command Default 180 seconds (3 minutes)—Cisco IOS Release 12.2(15)BC1 and earlier releases
900 seconds (15 minutes)—Cisco IOS Release 12.2(15)BC2 and later releases
Usage Guidelines The Cisco CMTS router maintains an internal list of CMs and CPE devices that are currently connected
on its cable interfaces. The CMTS router uses this list to provide the data for various show commands
and to respond to SNMP requests that query the entries in the cdxCmCpeTable table in the
CISCO-DOCS-EXT-MIB MIB.
By default, the Cisco CMTS router uses the current list if it is less than 3 minutes old. If the current list
is older than 3 minutes, the Cisco CMTS router considers it invalid and rebuilds a new list. This prevents
the CMTS router from having to build a new list for every query, which could impact system
performance.
You can use the cable cmcpe-list valid-time command to change the length of time that the CMTS
router considers the current CM and CPE device list to be valid. This allows you to find the optimum
time value that provides the most current information without affecting the number of CPU cycles that
are available for network processing.
A smaller time period ensures that the CM and CPE device list is more current but it requires more
processing time to maintain the list. A longer time period reduces the load on the processor but the
CM/CPE list might not be current.
If CPU usage dramatically increases when performing SNMP queries of the cdxCmCpeTable table, use
this command to increase the valid list time so that the Cisco CMTS router does not have to rebuild the
CM/CPE list more often than needed to respond to the queries.
Note To find the current valid list time, use the show running-config command and look for the cable
cmcpe-list valid-time command in the output. If the command does not appear, the valid list time is set
for its default value.
Examples The following example shows how to set the valid list time to 60 seconds (1 minute):
Router(config)# cable cmcpe-list valid-time 60
The following example shows how to find the current valid list time setting:
Router# show running-config | include cmcpe-list
cable cmcpe-list valid-time 60
no cable cm-status
Syntax Description range Specifies the CM status events you want to enable on a primary cable
interface. The valid range is 1 to 10. You can enable a single event by
specifying the event number or a group of events by specifying a range (for
example, 1-9).
The following events are enabled by default on a cable or modular cable
interface:
• Secondary channel MDD time-out
• QAM/FEC lock failure
• Sequence out of range
• MDD recovery
• QAM/FEC lock recovery
Note The default events are not displayed in the output of the show
running-config interface cable command.
Command Default The downstream related events such as secondary channel MDD time-out, QAM/FEC lock failure,
Sequence out of range, MDD recovery, and QAM/FEC lock recovery are enabled.
Note If the no version of the command is executed on the interface for specific events, then the show
running-config interface command lists the events only that are enabled. If no events are enabled then,
the show running interface cable command displays no cable cm-stauts enable with the events.
Examples The following example shows how to enable all CM status events on a primary cable interface:
Router# configure terminal
Router(config)# interface cable 8/0/0
Router(config-if)# cable cm-status enable 1-10
The following example shows the no cable cm-status enable command being configured and the
corresponding example shows show running-config interface command output:
Router(config)# interface cable 8/0/0
Router(config-if)# cable cm-status enable 1-10
Router(config-if)# no cable cm-status enable 1-2 4-5
Router(config-if) exit
The following example shows the show running-config interface cable command output when no
events are enabled on the CMTS:
Router#show running-config interface cable 8/0/0
Building configuration...
cable config-file
To create a configuration filename for a Cisco CMTS router internal CM configuration file, use the cable
config-file command in global configuration mode. To delete the configuration filename, use the no form
of this command.
Syntax Description filename Specifies the configuration filename to create and edit.
Usage Guidelines A DOCSIS CMTS router automatically downloads a DOCSIS configuration file to a CM during its initial
registration procedure. The DOCSIS configuration file configures the CM for its network operations and
includes information such as the maximum number of CPE devices that are supported, the quality of
service (QoS) options provided for the CM, and whether the CM should upgrade to a new software
image.
The DOCSIS specification defines the format of the DOCSIS configuration files, which can be created
by any number of tools. In addition to the other tools that Cisco provides for this purpose, the cable
config-file command can be used to create the DOCSIS configuration files needed for your network.
These configuration files are stored in the Flash memory on the Cisco CMTS router and can be
automatically downloaded to the CM as needed.
The cable config-file command creates the DOCSIS configuration file if it does not already exist and
then enters config-file configuration mode. You can then give one of the following subcommands to
create the configuration file:
• access-denied
• channel-id
• cpe max
• download
• frequency
• option
• privacy
• service-class
• snmp manager
• timestamp
Note When a DOCSIS shared secret is configured on the downstream interface (see the cable shared-secret
command), the cable config-file command automatically inserts the appropriate MD5 Message Integrity
Check (MIC) value at the end of the dynamically generated DOCSIS configuration file. You do not need
to specify the DOCSIS shared secret string with the cable config-file command.
After using the cable config-file subcommands, enter the exit command to leave config-file mode and
to save the configuration file in the Flash memory. After a configuration file is created, it also appears
in the running-configuration file. To delete a configuration file and remove it from Flash memory, use
the no cable config-file command.
To allow CMs to download the configuration files, you must also enable the router’s onboard TFTP
server, using the tftp-server configuration command. Unless you are running on a small lab network,
you should also remove the default limit of 10 TFTP sessions by using the service udp-small-serves
max-servers no limit command.
In addition, the following commands are also recommended:
• cable time-server—Enables the Cisco CMTS router to function as a time-of-day (ToD) server.
• ip dhcp pool—Configures the Cisco CMTS router as a DHCP server. Otherwise, you need an
external DHCP server.
• ip dhcp ping packets 0—Improves the scalability of the Cisco CMTS router DHCP server.
Note For complete information on DOCSIS configuration files, see Appendix C in the DOCSIS 1.1 Radio
Frequency (RF) Interface Specification, available on the DOCSIS Cable Labs official web site at
http://www.cablemodem.com
Examples The following example shows two DOCSIS configuration files being configured. The first configuration
file allows each CM to have up to four CPE devices and configures the QoS parameters for its traffic.
The second configuration file denies network access to the CM and its CPE devices.
Router# configure terminal
Router(config)# cable config-file test.cm
Router(config-file)# cpe max 4
Router(config-file)# service-class 1 priority 2
Router(config-file)# service-class 1 max-upstream 128
Router(config-file)# service-class 1 max-downstream 1000
Router(config-file)# timestamp
Router(config-file)# exit
Router(config)# cable config-file denied.cm
Router(config-file)# access-denied
Router(config-file)# exit
Router(config)#
The following is a portion of a typical Cisco IOS configuration file that shows the above two DOCSIS
configuration files, as well as a typical DHCP server configuration:
New Commands
Modified Commands
Obsolete Commands
The following commands have been removed from certain Cisco IOS software releases:
cable dci-response
To configure how a cable interface responds to DCI-REQ messages for CMs on that interface, use the
cable dci-response command in cable interface configuration mode.
Syntax Description success (Optional) Configures the interface so that the Cisco CMTS responds to DCI-REQ
messages from CMs on the interface by sending a DCI-RSP response with the
confirmation code of Success (0).
ignore (Optional) Configures the interface so that the Cisco CMTS ignores DCI-REQ
messages from CMs on the interface. It does not send any DCI-RSP responses.
reject permanent (Optional) Configures the interface so that the Cisco CMTS responds to DCI-REQ
messages from CMs on the interface by sending a DCI-RSP response with the
confirmation code of Reject Permanent (4).
reject temporary (Optional) Configures the interface so that the Cisco CMTS ignores the first four
DCI-REQ messages from a CM on the interface, but on the fifth DCI-REQ
message, the CMTS responds with a DCI-RSP response with the confirmation
code of Reject Temporary (3). The CMTS then continues to ignore the next seven
DCI-REQ messages and then restarts this process when it receives the twelfth
DCI-REQ message.
Command Default The Cisco CMTS router responds to DCI-REQ messages from all CMs by sending a DCI-RSP response
with the confirmation code of Success (0).
Usage Guidelines The Device Class Identification (DCI) messages are part of the Media Access Control Specification
section of the DOCSIS 1.1 specification (revision SP-RFIv1.1-I05-000714 and above). A CM can
optionally use the DCI-REQ message to inform the CMTS router of certain capabilities, such as whether
it is a CPE-controlled cable modem (CCCM).
The CMTS router then responds with one of the following confirmation codes:
• Success—Allows the CM to continue with the registration process.
• Reject Permanent—Instructs the CM to abort its registration process on this downstream channel.
The CM must try all other available downstream channels before attempting to register on this
downstream channel again.
• Reject Temporary—Instructs the CM to reset its DCI-REQ counter, to send another DCI-REQ
message, and to wait for the DCI-RSP before proceeding with the registration process.
Note The CMTS router also can respond with an Upstream Transmitter Disable (UP-DIS) message. See the
description of the cable dci-upstream-disable command for details.
Examples The following example shows how to configure the CMTS router so that it ignores all DCI-REQ
messages from CMs on the cable interface at slot 6:
Router# configure terminal
Router(config)# interface c6/0
Router(config-if)# cable dci-response ignore
The following example shows how to configure the CMTS router so that it returns to its default behavior
for the cable interface on slot 6, which is to respond to all DCI-REQ messages from CMs by sending a
DCI-RSP with a Success confirmation code:
Router# configure terminal
Router(config)# interface c6/0
Router(config-if)# cable dci-response success
Note The cable dci-response success command does not appear in a startup or running configuration file,
because it is the default configuration for a cable interface.
cable dci-upstream-disable
To configure a cable interface so that it transmits a DOCSIS 1.1 Upstream Transmitter Disable (UP-DIS)
message to a particular CM, use the cable dci-upstream-disable command in cable interface
configuration mode. To remove that configuration and return to the default configuration, use the no
form of this command.
Syntax Description mac-address Specifies the MAC physical layer address for a particular CM.
enable (Optional) Enables the UP-DIS message for the particular CM, so that when the CM
sends a DCI-REQ message, the CMTS router responds by sending an UP-DIS response.
disable (Optional) Disables the sending of UP-DIS messages to a particular CM.
Command Default The Cisco CMTS router does not transmit UP-DIS messages to any CMs.
Usage Guidelines The DOCSIS 1.1 specification (revision SP-RFIv1.1-I05-000714 and above) allows a CMTS router to
transmit an Upstream Transmitter Disable (UP-DIS) message to a CM. If the CM supports the UP-DIS
message, it responds by immediately disabling its upstream transmitter circuitry. The CM must be
power-cycled before it can begin transmitting on the upstream again.
Examples The following example shows the cable dci-upstream-disable command being used to enable the
UP-DIS message for the CM with the MAC address of 0123.4567.89ab.
Router# configure terminal
Router(config)# interface c6/0
Router(config-if)# cable dci-upstream-disable 0123.4567.89ab enable
Router(config-if)# exit
Router(config)# exit
cable default-phy-burst
To specify a value for the upstream Maximum Traffic Burst parameter for CMs that do not specify their
own value, use the cable default-phy-burst command in cable interface configuration mode. To reset
the maximum burst size to its default, use the no form of this command.
no cable default-phy-burst
Syntax Description burst-size Specifies the maximum number of bytes that are allowed in a burst. The valid range is 0 to
4096 bytes, with a default of 2000 bytes. A value of 0 specifies that CMs cannot register
unless they specify a valid burst size.
Usage Guidelines
Note The cable default-phy-burst command applies to cable modems that cannot perform fragmentation.
The value specified by the cable default-phy-burst command is used to determine the maximum total
frame burst size supported for a cable modem request. In contrast, the cable upstream fragment-force
command may be used to determine the largest single physical burst a cable modem can transmit, when
the cable modem supports fragmentation.
The DOCSIS 1.0 specification allows CMs to register without specifying a maximum upstream burst
size, or to register with a value of 0, which means an unlimited burst size. This behavior can interfere
with DOCSIS 1.1 networks because excessively large bursts on an upstream will generate unpredictable
jitter and delay in voice calls. DOCSIS 1.1 CMs can also cause this problem if they register without
enabling fragmentation of packets at the DOCSIS MAC layer.
This command allows you to specify a default burst size for CMs that register without specifying a burst
size or that register with a burst size of 0. It also specifies the maximum size of long data grants if a CM
specifies a size of 0 (unlimited) in the Upstream Channel Descriptor (UCD) packet. If a CM specifies a
long data grant that would exceed the maximum burst size, and the CM is not using DOCSIS
concatenation, the DOCSIS scheduler drops the bandwidth request.
To prevent CMs from registering without defining a burst profile, use this command with a burst-size of
zero. CMs that do not define a burst profile will not be allowed to register and come online.
Note Typically, DOCSIS 1.1 CMs set the maximum upstream transmit burst size to the larger value of 1522
bytes and maximum concatenated burst size (which can be a maximum of 4096 bytes).
The default PHY burst parameter interacts with two other parameters that are configured in the DOCSIS
configuration file:
• DOCSIS 1.1 configuration files can also specify a value for the maximum concatenation burst,
which has a default of 1522 bytes. If this parameter is greater than the default PHY burst size, the
CM can override the default PHY burst when it is using concatenation.
• DOCSIS 1.0 and 1.1 configuration files can also specify a maximum transmit burst size. In DOCSIS
1.1 configurations, this parameter defaults to 3044 bytes, with a minimum of 1522 bytes. DOCSIS
1.0 configuration files could set this parameter to a value lower than 1522 bytes, depending on what
version of the DOCSIS 1.0 specification they support. The CMTS router will enforce the lower limit
between the default phy burst and the maximum transmit burst, so you should ensure that all
configuration files in your network specify a minimum of 1522 bytes for the maximum transmit
burst size.
Examples The following example shows the default maximum burst size to 1522 bytes, which is the minimum size
required by the DOCSIS 1.1 specification:
Router(config)# interface cable 5/1
Router(config-if)# cable default-phy-burst 1522
The following example shows the default maximum burst size to 0, which means that a CM must specify
a valid burst profile before the Cisco CMTS allows it to register and come online:
Router(config)# interface cable 5/1
Router(config-if)# cable default-phy-burst 0
The following example shows the default maximum burst size being reset to its default of 2000 bytes:
Router(config)# interface cable 5/1
Router(config-if)# no cable default-phy-burst
cable device
To configure access list for a CM device or host, use the cable device command in privileged EXEC
mode. To remove an access group, use the no access-group option of this command.
Usage Guidelines For the VRF syntax portion of this command, only the IP address option is supported.
Note The cable device command is not supported on the Cisco uBR10012 universal broadband router.
Note The vrf keyword is not supported on the 12.0 SC, 12.1 EC and 12.2 BC releases.
Examples The following example shows how to assign an access list to the MAC address of a cable device:
Router# configure terminal
Router(config)# cable device 0010.7b6b.77ed acc 1
Router(config)# exit
cable dhcp-giaddr
To modify the GIADDR field of DHCPDISCOVER and DHCPREQUEST packets with a relay IP address
before they are forwarded to the DHCP server, use the cable dhcp-giaddr command in cable interface or
subinterface configuration mode. To set the GIADDR field to its default, use the no form of this
command.
no cable dhcp-giaddr
Syntax Description policy Selects the control policy, so the primary address is used for CMs and the secondary
addresses are used for hosts and other customer premises equipment (CPE) devices. This
setting is typically used when the CMs on the interface are configured for routing mode, so
that the CMs and hosts can use IP addresses on different subnets.
strict (Optional, only when the policy keyword is specified) Uses the GIADDR IP address as the
source IP address in the forwarded DHCP OFFER packet.
By default when using the policy option, the Cisco CMTS changes the source IP address in
the DHCPOFFER packet to match that of the primary address on the cable interface. Use
the strict option to prevent this behavior, which could interfere with any access lists applied
to the CM when the CM is using a different subnet from the cable interface’s primary
address space.
primary Always selects the primary address to be used for the GIADDR field for both CMs and CPE
devices. This option is typically used for the Cisco uBR-MC16E card and Cisco uBR7100E
series routers to support EuroDOCSIS operations.
Usage Guidelines You can use this command to modify the GIADDR field of DHCPDISCOVER and DHCPREQUEST
packets to provide a relay IP address before packets are forwarded to the DHCP servers. Use this
command to set a policy option such that primary addresses are used for CMs and secondary addresses
are used for hosts (such as PCs) behind the CMs.
When using multiple secondary subnets, the Cisco CMTS router uses the first secondary IP address as
the GIADDR field when forwarding a DHCPDISCOVER request to the DHCP server. If no DHCP server
responds with a DHCPOFFER message after three attempts, the Cisco CMTS router uses the next
secondary IP address, up to a maximum of 16 secondary addresses.
Note If you have configured a Cisco CM for routing mode and are also using the cable-modem dhcp-proxy
nat command on the CM, you must configure the corresponding cable interface on the Cisco CMTS with
the cable dhcp-giaddr policy [strict] command.
Caution You cannot use the strict option with the internal DHCP server that is onboard the Cisco CMTS router,
because the strict option requires the use of DHCP relay operation, which is not performed by DHCP
termination points such as the internal DHCP server.
Examples The following example shows how to set the primary address to be used always for GIADDR:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable dhcp-giaddr primary
The following example shows how to set the primary address to be used always for giaddr in the cable
subinterface mode:
Router# configure terminal
Router(config)# interface cable 6/0.1
Router(config-subif)# cable dhcp-giaddr primary
The following example shows how to configure the router so that the primary address is used for CMs
and the secondary addresses are used for hosts. In addition, the GIADDR is used as the source IP address
in forwarded DHCPOFFER packets.
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable dhcp-giaddr policy strict
Command Description
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CM must access.
ip dhcp relay information option Enables the system to insert the CM MAC address into a
DHCP packet received from a CM or host and forward the
packet to a DHCP server.
ip dhcp smart-relay Monitors client retransmissions when address pool
depletion occurs.
cable dhcp-insert
To configure the Cisco CMTS router to insert descriptors into DHCP packets using option 82, use the
cable dhcp-insert command in global configuration mode. This optional command specifies which
descriptors to append to DHCP packets. DHCP servers can then detect cable modem clones and extract
geographical information. To remove this configuration, use the no form of this command.
Syntax Description downstream-description Received DHCP packets are appended with downstream port
descriptors.
hostname Received DHCP packets are appended with the router host names.
upstream-description Received DHCP packets are appended with upstream port descriptors.
Usage Guidelines This feature enhances the DHCP security potential and the Cable Duplicate MAC Address Feature on
the Cisco CMTS router.
Note Multiple types of descriptor strings can be configured as long as the maximum relay information option
size is not exceeded.
The Cisco CMTS router can use the DHCP Relay Agent Information option (DHCP option 82) to send
particular information about a cable modem, such as its MAC address and the cable interface to which
it is connected. If the DHCP server cannot match the information with that belonging to a cable modem
in its database, the CMTS router knows that the device is a CPE device. This allows the CMTS router
and DHCP server to retain accurate information about which CPE devices are using which cable modems
and whether the devices should be allowed network access.
The DHCP Relay Agent can also be used to identify cloned modems or gather geographical information
for E911 and other applications. Using the cable dhcp-insert command, users configure the CMTS
router to insert downstream, upstream, or hostname descriptors into DHCP packets. A DHCP server can
then utilize such information to detect cloned modems or extract geographical information. Multiple
types of strings can be configured as long as the maximum relay information option size is not exceeded.
For additional information, refer to the DHCP feature documentation for the Cisco CMTS routers on
Cisco.com.
Syntax Description -optnum Specifies the DHCP option. Valid values are 43 and 60.
Command Default The CMTS does not parse the specified DHCP options.‘
Usage Guidelines To determine specific device and system information, configure cable dhcp-parse option-43 command
on the CMTS. The CMTS parses option-43 of the CPE DHCP message to determine the device and
system information of the CPE.
To determine the CPE device type, configure cable dhcp-parse option-60 command on the CMTS. The
CMTS parses option-60 of the CPE DHCP message to determine the device type of the CPE.
Examples The following example shows DHCP option 43 enabled on the CMTS:
Router(config-if)# cable dhcp-parse option-43
Router(config-if)#
cable divert-rate-limit
To set Cable-side DRL rate and limit, use the cable divert-rate-limit command in interface
configuration mode. To reset the rate and limit to the default values, use the no form of this command.
no cable divert-rate-limit
Syntax Description rate Specifies the divert rate in packets per second. Minimum rate is 1 packet per
second. Maximum rate is 65535 packets per second. The default rate is 2000
packets per second.
limit Specifies the number of packets to be diverted in an initial burst of packets.
Minimum limit is 4 packets. Maximum limit is 4194 packets. The default
limit is 2000 packets.
Command Default The default DRL configuration for every physical cable interface is 2000 packets per second and the
default limit is 2000 packets
Usage Guidelines Cable-side DRL is configured on the physical cable interface. It cannot be configured on a cable bundle
interface.
Examples The following example shows how to configure the rate and limit values for a cable interface.:
Router(config-if)# cable divert-rate-limit rate 1 limit 4
no cable docsis30-voice
Command Default The default config is req-attr-mask 0 forb-attr-mask 0. Use the no form of this command to return to
default. It will set the values for docsis30 voice downstream req-attr-mask and forb-attr-mask to 0.
Usage Guidelines This command is used to configure docsis 3.0 voice related downstream service-flow attribute-mask
number.
Examples The following example shows how to configure the downstream attribute mask for the interface cable:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable docsis30-voice downstream req-attr-mask ?
<0-FFFFFFFF> The attribute bitmap in hex
cable dot1q-vc-map
To map a cable modem to a particular Virtual Local Area Network (VLAN) on a local outbound Ethernet
interface, use the cable dot1q-vc-map command in global configuration mode. To remove this mapping,
or to remove a particular customer’s name from the internal tables, use the no form of this command.
Syntax Description mac-address Specifies the hardware (MAC) address for the cable modem whose traffic is
to be mapped.
ethernet-interface Specifies the outbound interface to which this cable modem should be
mapped. On the Cisco uBR7100 series and Cisco uBR7246VXR routers,
you can specify an Ethernet, Fast Ethernet, or Gigabit Ethernet interface,
depending on what interfaces are actually installed in the chassis.
vlan-id Specifies the ID for the IEEE 802.1Q Virtual Local Area Network (VLAN)
that should be used to tag the frames for this cable modem. The valid range
is 1 to 4095, with no default.
Note The switches acting as the bridge aggregators might support a lower
number of VLAN IDs. If so, the Cisco CMTS router should be
configured within the limits of the switches’ maximum number of
VLANs.
cust-name (Optional) Identifies the customer using this VLAN. The cust-name can be
any arbitrary alphanumeric string, up to 127 characters long.
customer cust-name (Optional) Deletes all VCs belong to this customer. The cust-name can be
any arbitrary alphanumeric string, up to 127 characters long.
Usage Guidelines This command maps a cable modem, on the basis of its hardware (MAC) address, to a particular
IEEE 802.1Q VLAN on a particular outbound Ethernet interface. This enables the cable modem’s traffic
to be part of a virtual LAN at the Layer-2 level.
Note To use this command, you must first enable the use of IEEE 802.1Q Layer 2 tunnels, using the cable
l2-vpn-service dot1q command. Then use this command to map individual cable modems to specific
VLANs.
Examples The following example shows how to enable the use of Layer 2 tunnels and then map specific CMs to
VLANs on a specific interface:
Router# config terminal
Router(config)# cable l2-vpn-service dot1q
Router(config)# cable dot1q-vc-map 000C.0e03.69f9 GigabitEthernet 1/0 4
Router(config)# cable dot1q-vc-map 0010.7bed.9c95 GigabitEthernet 1/0 5
Router(config)# exit
The following example shows the same command as above, but this time each VLAN is identified by the
customer that is using it:
Router# config terminal
Router(config)# cable l2-vpn-service dot1q
Router(config)# cable dot1q-vc-map 000C.0e03.69f9 GigabitEthernet 1/0 4 ENTERPRISE-CO1
Router(config)# cable dot1q-vc-map 0010.7bed.9c95 GigabitEthernet 1/0 5 ENTERPRISE-CO2
Router(config)# exit
The following example shows how to remove the Layer 2 mapping for a specific cable modem. This
particular cable modem’s traffic is then routed using the normal Layer 3 routing processes.
Router# config terminal
Router(config)# no cable dot1q-vc-map 000C.0e03.69f9 GigabitEthernet 1/0 4
Router(config)# exit
Syntax Description A Annex A. The downstream uses the EuroDOCSIS J.112 standard.
B Annex B. The DOCSIS-compliant cable plants that support North American channel plans use ITU
J.83 Annex B downstream radio frequency.
Command Default Annex B for all Cisco cable interface cards other than the Cisco uBR-MC16E. Annex A, if using the
Cisco uBR-MC16E cable interface line card and the Cisco uBR7111E and Cisco uBR7114E universal
broadband routers.
Usage Guidelines The MPEG framing format must be compatible with the downstream symbol rate you set. Annex B is
the North America (DOCSIS) standard and Annex A is the European (EuroDOCSIS) standard. You
should review your local standards and specifications for downstream MPEG framing to determine
which format you should use.
The Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC5X20U cable interface line cards
support both Annex A and Annex B operation. However, on the Cisco uBR-MC28U/X, both
downstreams must be configured for the same mode (either both Annex A or both Annex B).
On the Cisco uBR-MC16U and Cisco uBR-MC28U (with integrated upconverter), the IF frequency is
fixed at 44 MHz for both Annex A and Annex B modes of operation. On the Cisco uBR-MC16X and
Cisco uBR-MC28X (without integrated upconverter), the IF frequency is set to 36.125 MHz in Annex A
mode and 44 MHz in Annex B mode.
Note This command can be used to change the symbol rate, alpha, and other parameters for compliance with
EuroDOCSIS (annex A), or DOCSIS (annex B). Annex A is not supported on the Cisco uBR-MC1xC,
Cisco uBR-MC16B, Cisco uBR-MC16S, and Cisco uBR-MC28C cable interface line cards. Annex B is
not supported on the Cisco uBR-MC16E card and on the Cisco uBR7111E and Cisco uBR7114E
universal broadband routers.
Note The cable interface line card downstream ports and the CMs on the HFC network connected through
these ports must be set to the same MPEG framing format.
Caution In Cisco IOS Release 12.1, only Annex B MPEG framing format is supported.
Tip Changing the MPEG framing format affects the PHY layer on the downstream and disconnects all online
CMs. For this reason, if you are using N+1 HCCP redundancy, you should configure this command on
both the Protect and Working interfaces, so that the PHY layer is properly configured before a
switchover occurs. Otherwise, online CMs could be disconnected when a switchover occurs. (This also
applies to the cable downstream modulation and cable downstream interleave-depth commands.)
Examples The following example shows how to set the MPEG framing format to Annex A:
Router# configure terminal
Router(config)# interface cable 1/0
Router(config-if)# cable downstream annex A
The following example shows how to set the MPEG framing format to Annex B:
Router# configure terminal
Router(config)# interface cable 4/0
Router(config-if)# cable downstream annex B
Syntax Description mask Specifies the mask value for the interface.
Command Default If this command is not used, the default attribute will be used for the cable interface and the wideband
cable interface. The default attribute for the wideband cable interface is 0x80000000 (31-bit) and for the
cable interface is zero. For a wideband cable interface, 31-bit mask is always set to 1.
Usage Guidelines The attribute-mask comprises 32 attributes and each attribute represents a single bit in the mask. You can
configure a provisioned attribute mask for each channel and provisioned bonding group to assign values
to the operator-defined binary attributes, or to override the default values of the specification-defined
attributes. The operator may configure, in the CM configuration file, a required attribute mask and a
forbidden attribute mask for a service flow. Additionally, in a CM-initiated dynamic service request, the
CM can include a required attribute mask and a forbidden attribute mask for a service flow.
Examples The following example shows how to configure an attribute for a wideband cable interface:
Router# configure terminal
Router(config)# interface wideband-cable 1/0/0:0
Router(config-if)# cable downstream attribute-mask 800000ff
Syntax Description id Specifies a downstream channel ID. Valid values for releases prior to Cisco IOS Release
12.2(33)SCB are from 0 to 255 and the valid values for Cisco IOS Release 12.2(33)SCB and later
are from 1 to 255 as 0 is reserved for network management.
Command Default The unit number of the downstream device, starting with a value of 1.
Usage Guidelines Use this command to make sure that each downstream channel has a unique ID when there are multiple
Cisco CMTS routers at a headend facility.
Cisco IOS assigns the default ID number of each downstream channel in the order in which devices
connected to the downstream channels appear to the CMTS router. The downstream channel connected
to the first device that appears to the CMTS router is configured with a default ID of 1, the downstream
channel connected to the second device that appears is configured with an ID of 2, and so on.
The local downstream channel channel ID is unique across all SPA channels. When you add a channel
to the MAC domain using the downstream modular-cable rf-channel command, the channel IDs in the
MAC domain are unique. This also facilitates channel ID uniqueness when the channels are added to a
fiber node.
Table 1 shows the 12.2(33)SCB1 downstream channel ID scheme and Table 2 shows the 12.3(23)BCx
scheme. This applies to rf-channel rf-port cable downstream channel-id channel-id command also.
8/1 8/0 7/1 7/0 6/1 6/0 5/1 5/0 slot 3 slot 1
SPA Bay 0 217-2 193-2
40 16
SPA Bay 1 217-2 193-2
40 16
SPA Bay 2 217-2 193-2
40 16
SPA Bay 3 217-2 193-2
40 16
5x20 DS /0 169 145 121 97 73 49 25 1
5x20 DS /1 173 149 125 101 77 53 29 5
5x20 DS /2 177 153 129 105 81 57 33 9
5x20 DS /3 181 157 133 109 85 61 37 13
5x20 DS /4 185 161 137 113 89 65 41 17
8/1 8/0 7/1 7/0 6/1 6/0 5/1 5/0 slot 3 slot 1
SPA Bay 0 24-47 24-47
SPA Bay 1 48-71 48-71
5x20 188-1 180-1 168-1 160-1 148-1 140-1 128-1 120-1
92 84 72 64 52 44 32 24
Caution Changing the downstream channel ID of an active channel automatically disconnects all connected CMs
and forces them to go offline and reregister with the CMTS router, as required by the DOCSIS
specifications.
Examples The following example shows how to configure the downstream channel on the cable interface line card
in slot 6 of a Cisco CMTS router with a channel ID of 44:
Router(config-if)# cable downstream channel-id 44
The following example shows how to restore the downstream channel ID configuration to the default
configuration:
Router(config-if)# cable downstream channel-id
Usage Guidelines Global configuration for A-DSG must be complete before configuring interface definitions.
Examples The following example shows configuration of inclusion of DSG channel list entries in DCD messages
on a downstream cable interface on a Cisco CMTS router:
interface Cable6/0
cable downstream dsg chan-list 2
Command Description
cable downstream dsg Associates A-DSG vendor parameters to a downstream and
vendor-param includes them in the DCD message on a Cisco CMTS router.
cable dsg chan-list Configures the A-DSG downstream channel list on a CMTS
router.
Usage Guidelines Global configuration for Advanced-mode DOCSIS Set-top Gateway (A-DSG) must be complete before
configuring interface definitions. This command is used when there are no enabled rules or tunnels for
A-DSG on a Cisco CMTS router.
Examples The following example shows how to enable DCD messages on a downstream interface on a Cisco
CMTS router along with several other A-DSG interface configuration commands:
interface Cable6/0
cable downstream dsg dcd-enable
cable downstream dsg chan-list 2
cable downstream dsg timer 3
cable downstream dsg vendor-param 2
cable downstream dsg rule 1 priority 1 clients 1 tunnel 1
cable downstream dsg rule 1 vendor-param 1
cable downstream dsg rule 1 classifiers 1 5
cable downstream dsg rule 2 priority 1 clients 2 tunnel 2
Related Commands
Command Description
cable downstream dsg chan-list Associates the A-DSG channel list entry to a downstream
channel, to be included in the DCD message on a Cisco CMTS
router.
cable downstream dsg rule Defines and associates an A-DSG rule to a downstream channel
on a Cisco CMTS router.
cable downstream dsg timer Associates an A-DSG timer entry to a downstream channel and
includes the DCD message on a Cisco CMTS router.
cable downstream dsg Associates A-DSG vendor parameters to a downstream and
vendor-param includes them in the DCD message on a Cisco CMTS router.
To define and associate an Advanced-mode DOCSIS Set-top Gateway (A-DSG) rule to the downstream
channel on a Cisco CMTS router, use the cable downstream dsg rule command in interface
configuration mode. To remove the DSG rule configuration, use the no form of this command.
cable downstream dsg rule rule-id [clients clnt-list-id tunnel tun-id | priority priority |
vendor-param vsif-grp-id | ucid ucid1 | [ucid1 ucid2...ucidn] | cfr cfr-index [cfr-index...] |
disable]
no cable downstream dsg rule rule-id [clients clnt-list-id tunnel tun-id | priority priority |
vendor-param vsif-grp-id | ucid ucid1 | [ucid1 ucid2...ucidn] | cfr cfr-index [cfr-index...] |
disable]
Command Default DSG rules are disabled by default when they are created.
Usage Guidelines Global configuration for A-DSG must be complete before configuring interface definitions.
Because rules are disabled when they are created, you must enable the configuration using the no cable
downstream dsg rule disable form of the command. To disable a DSG rule configuration, use the cable
downstream dsg rule disable form of this command.
You can associate DSG clients, vendor specific parameters, classifiers, DSG tunnel address, upstream
channel identifier range, and rule priority to a downstream channel. You can apply more than one rule
to a downstream channel. All configured rules that are enabled are included in the Downstream Channel
Descriptor (DCD) message.
Examples The following example shows configuration and association of DSG rules on a downstream cable
interface on a Cisco CMTS router, followed by an example of enabling the configured DSG rules:
interface Cable6/0
cable downstream dsg rule 1 clients 1 tunnel 1
cable downstream dsg rule 1 priority 1
cable downstream dsg rule 1 vendor-param 1
cable downstream dsg rule 1 classifiers 1 5
cable downstream dsg rule 2 clients 2 tunnel 2
cable downstream dsg rule 2 priority 1
!
! Enable the DSG rule configuration
!
no cable downstream dsg rule 1 disable
no cable downstream dsg rule 2 disable
The following example shows how to disable DSG rules that were previously enabled:
interface cable6/0
cable downstream dsg rule 1 disable
cable downstream dsg rule 2 disable
Syntax Description group-id Specifies the A-DSG tunnel group identifier as a number from 1 to
65535.
channel-id Specifies the downstream channel identifier as a number from 1 to
65535.
Command Default The A-DSG tunnel group is not associated to a downstream interface.
Usage Guidelines The cable dsg tg channel global configuration command establishes the configuration of tunnels in a
tunnel group. Tunnel groups are enabled by default.
Then, you can associate the tunnel group to a downstream cable interface using the cable downstream
dsg tg channel interface configuration command.
Examples The following example shows the configuration and activation of a tunnel group with ID of 1 and channel
ID of 2 in global configuration, followed by association of the tunnel group to a downstream interface
on a Cisco CMTS router:
cable dsg tg 1 channel 2
interface cable 8/1/2
cable downstream dsg tg 1 channel 2
Related Commands
Command Description
cable downstream dsg chan-list Associates an A-DSG channel list entry to a downstream channel
and includes it in the DCD message on a Cisco CMTS router.
cable downstream dsg Enables DCD messages to be sent on a downstream channel on a
dcd-enable Cisco CMTS router.
cable downstream dsg timer Associates an A-DSG timer entry to a downstream channel and
includes the DCD message on a Cisco CMTS router.
cable downstream dsg Associates A-DSG vendor parameters to a downstream and
vendor-param includes them in the DCD message on a Cisco CMTS router.
cable dsg tunnel Associates a group of A-DSG tunnels to one or more downstream
interfaces on a Cisco CMTS router.
Syntax Description timer-index Identifier for the DSG timer setting in the index.
Usage Guidelines Global configuration for A-DSG must be complete before configuring interface definitions.
Examples The following example shows the configuration DSG timers for inclusion in DCD messages on a
downstream cable interface on a Cisco CMTS router:
interface Cable6/0
cable downstream dsg timer 3
Usage Guidelines Global configuration for A-DSG must be complete before configuring interface definitions.
Examples The following example shows configuration of A-DSG vendor parameters on a downstream interfac,
along with several other downstream interface commands on a Cisco CMTS router:
interface Cable6/0
cable downstream dsg dcd-enable
cable downstream dsg chan-list 2
cable downstream dsg timer 3
cable downstream dsg vendor-param 2
cable downstream dsg rule 1 priority 1 clients 1 tunnel 1
cable downstream dsg rule 1 vendor-param 1
cable downstream dsg rule 1 classifiers 1 5
cable downstream dsg rule 2 priority 1 clients 2 tunnel 2
Command Description
cable downstream dsg rule Defines and associates an A-DSG rule to a downstream channel
on a Cisco CMTS router.
cable downstream dsg timer Associates an A-DSG timer entry to a downstream channel and
includes the DCD message on a Cisco CMTS router.
Syntax Description down-freq-hz The known center frequency of the downstream carrier in Hz (the valid range is
55,000,000 to 858,000,000). The usable range depends on whether the downstream is
configured for DOCSIS or EuroDOCSIS operations:
• DOCSIS = 88,000,000 to 855,000,000 MHz
• Extended frequency range = 70,000,000 to 855,000,000 MHz
• EuroDOCIS = 112,000,000 to 858,000,000 MHz
The Cisco IOS supports a superset of these standards, and setting a center frequency to
a value outside these limits violates the DOCSIS or EuroDOCSIS standards. Cisco does
not guarantee the conformance of the downstream and upconverter outputs when using
frequencies outside the DOCSIS or EuroDOCSIS standards.
Command Default Disabled. On the Cisco uBR7100 series routers, the default downstream center frequency for the
integrated upconverter is 500 MHz.
Release Modification
12.3BC This command was integrated into Cisco IOS Release 12.3BC.
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 This command is either optional or required, depending on the cable interface line card being used.
• On the Cisco uBR7100 series routers using the integrated upconverter (the DS0 RF output), and on
cable interfaces that support integrated upconverters (such as the Cisco uBR-MC16U,
Cisco uBR-MC28U, and Cisco uBR-MC5X20U), this command configures the frequency for the
integrated upconverter. The no form of this command unsets the frequency and disables the output
from the integrated upconverter.
• For cable interfaces that use an external upconverter (such as the Cisco uBR-MC16S and the DS0
(IF) output on Cisco uBR7100 series routers), this command is informational-only, because it does
not affect the external upconverter. The external upconverter must be programmed separately with
the appropriate center frequency.
Note The no form of this command is supported only on the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X,
and Cisco uBR-MC5X20S/U cable interface line cards, and on the Cisco uBR7100 series universal
broadband router.
Note We recommend configuring this command on all cable interfaces, even those that are using external
upconverters. This is because this command is required to enable the downstream frequency override
feature and for N+1 line card redundant operation when using SNMP-capable external upconverters.
The downstream frequency of your RF output must be set to match the expected input frequency of your
upconverter. To do this, you enter the fixed center frequency of the downstream channel for the
downstream port. (You can also select a default that does not set a specific fixed value.) The valid range
for a fixed center frequency is 54,000,000 to 858,000,000 Hz. The center frequency is also used to
configure an IF-to-RF upconverter that must be installed in your downstream path.
The digital carrier frequency is specified to be the center of a 6.0 MHz channel. For example, EIA
channel 95 spans 90.000 to 96.000 MHz. The center frequency is 93.000 MHz, which is the digital
carrier frequency that should be configured as the downstream frequency. The typical range for current
CATV headends is 88,000,000 to 860,000,000 Hz.
In Cisco IOS software releases before Cisco IOS Release 12.2(15)BC2, the cable downstream
frequency command allowed the center frequency to be specified in 125 KHz increments. In Cisco IOS
Release 12.2(15)BC2 and later releases, this was changed to allow only 250 KHz increments, because
of the requirements of the Broadband Processing Engine cable interface line cards that use an internal
upconverter (Cisco uBR-MC16U, Cisco uBR-MC28U, and Cisco uBR-MC5X20S/U).
Note DOCSIS allows downstreams to use any center frequency within 88,000,000 to 855,000,000 MHz.
However, when most cable modems first come online, they initially start scanning the downstream for
the frequencies that are in the NTSC channel plan. If a valid downstream is not found among those
frequencies, the cable modems then beginning scanning the remaining frequencies. For the fastest and
most efficient registration times, we recommend configuring downstreams for the frequencies that are
specified in the NTSC channel plan.
Examples The following example shows how to set the downstream center frequency display value:
Router(config)# interface c6/0
Router(config-if)# cable downstream frequency 96000000
Syntax Description continuous-wave Outputs an unmodulated carrier signal on the downstream, shutting down normal
data network operations.
prbs Outputs a Pseudo Random Bit Stream (PRBS) test signal on the downstream,
shutting down normal data network operations.
Command Default The downstream interface is enabled for normal data use (cable downstream if-output).
Usage Guidelines Typically, a downstream is configured to output a modulated signal, using the cable downstream
if-output command, allowing data transmissions to be sent over the HFC cable network. However, this
command can also be used to test the cable plant or to shut down the interface completely:
• cable downstream if-output continuous-wave—Generates an unmodulated, continuous sine wave
on the downstream interface. You can use a spectrum analyzer to verify the frequency, amplitude,
and power of the wave. The test signal continues on the downstream until you resume normal
modulated operations using the cable downstream if-output command.
• cable downstream if-output prbs—Generates a PRBS test signal on the downstream interface. You
can use a spectrum analyzer to verify the frequency, amplitude, and power of the wave. The test
signal continues on the downstream until you resume normal modulated operations using the cable
downstream if-output command.
• no cable downstream if-output—Terminates all signal output and shuts down the downstream
interface. The interface remains shut down until you reactive the downstream using the cable
downstream if-output command.
Note Generating a PRBS or continuous-wave test signal or shutting down the interface automatically stops the
modulated carrier data signal and disconnects all CMs on that downstream. These commands should not
be used on a live network except as part of troubleshooting major network problems.
Examples The following example shows how to enable downstream port 0 on a cable interface:
Router# configure terminal
Router# interface c6/0
Router(config-if)# cable downstream if-output
The following example shows a PRBS test signal being generated on a downstream for a period of time.
The downstream is then shut down so that the test engineer can verify that no signal is being sent on the
downstream. After the tests have been run, the downstream is reactivated for normal modulated data use:
Router# configure terminal
Router# interface c6/0
Router(config-if)# cable downstream if-output prbs
(the signals are verified by a spectrum analyzer...)
Router#(config-if)# no cable downstream if-output
(the downstream is checked to verify no signals are being sent on it...)
Router#(config-if)# cable downstream if-output
Router#(config-if)# exit
Syntax Description 8 | 16 | 32 | 64 | 128 Indicates the downstream interleave depth in number of rows of codewords.
Command Default 32
Usage Guidelines
Note This command is not supported on the Cisco uBR-MC16E cable interface line card or on the
Cisco uBR7111E and Cisco uBR7114E universal broadband routers, because the interleave on the
EuroDOCSIS downstream is fixed.
This command sets the minimum latency of the system. A higher interleave depth provides more
protection from bursts of noise on the HFC network by spreading out the bits for each codeword over a
greater transmission time.
Interleave transmissions do not transmit each codeword by itself, but instead send bits from multiple
codewords at the same time, so that a noise burst affects the minimum number of bits per codeword,
which allows the Forward Error Correction (FEC) algorithm a greater chance of detecting and correcting
any transmission errors.
A higher interleave depth transmits bits from a greater number of codewords, increasing the efficacy of
the FEC algorithm. However, a higher depth also increases downstream latency, which might slow
TCP/IP throughput for some configurations, so you need to choose an interleave depth that is appropriate
both for your plant’s noise levels and application needs.
If your cable plant is experiencing high noise levels, consider increasing the interleave from the default
of 32 to 64. For plants with exceptionally high noise levels, increase the interleave to 128 to provide the
maximum protection from noise bursts.
Low interleave depth values typically cause some packet loss on typical HFC networks, because burst noise
lasts beyond the error correction block correctable length. However, on cable plants with exceptionally low
noise levels, Cisco recommends initially using the default value of 32, and then trying an interleave of either
16 or 8 to see if this increases performance without increasing the number of errors that result from noise.
Table 3 shows interleave characteristics and their relation to each other.
Note Table 3 does not apply to EuroDOCSIS cable plants because the interleave depth for EuroDOCSIS cable
interfaces is fixed.
Tip Changing the interleave depth affects the PHY layer on the downstream and disconnects all online CMs.
For this reason, if you are using N+1 HCCP redundancy, you should configure this command on both
the Protect and Working interfaces, so that the PHY layer is properly configured before a switchover
occurs. Otherwise, online CMs could be disconnected when a switchover occurs. (This also applies to
the cable downstream annex and cable downstream modulation commands.)
Examples The following example shows how to configure the downstream interleave depth to 128 microseconds:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable downstream interleave-depth 128
Usage Guidelines Downstream modulation defines the speed in bits per second at which data travels downstream to the
subscriber’s CM. A symbol is the basic unit of modulation. QPSK encodes 2 bits per symbol, 16-QAM
encodes 4 bits per symbol, 64-QAM encodes 6 bits per symbol, and 256-QAM encodes 8 bits per
symbol.
Note Setting a downstream modulation format of 256-QAM requires approximately a 6-dB higher
signal-to-noise ratio (SNR) than 64-QAM at the subscriber’s cable modem. If your network is marginal
or unreliable at 256-QAM, use the 64-QAM format instead.
Tip Changing the modulation format affects the PHY layer on the downstream and disconnects all online
CMs. For this reason, if you are using N+1 HCCP redundancy, you should configure this command on
both the Protect and Working interfaces, so that the PHY layer is properly configured before a
switchover occurs. Otherwise, online CMs could be disconnected when a switchover occurs. (This also
applies to the cable downstream annex and cable downstream interleave-depth commands.)
Examples The following example shows how to set the downstream modulation to 256-QAM:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable downstream modulation 256qam
Usage Guidelines This command is never needed for normal operations, because downstream frequency override is
enabled by default for DOCSIS operations. However, this command can be used to disable the frequency
override feature for test and lab use, so as to force the CMs on that interface to use a particular
downstream frequency, regardless of the signal quality.
Note Because frequency override is enabled by default, this command does not appear as part of a cable
interface’s configuration section in the Cisco CMTS router configuration file unless the no cable
downstream override command has been given.
Examples The following example shows how to disable the downstream frequency override feature on a particular
cable interface:
Router# configure terminal
Router(config)# interface cable 6/0
Router(config-if)# no cable downstream override
Router(config-if)# exit
Syntax Description weights weight Specifies the custom excess ratios for 8 priorites.
• weight1...weight8—Custom weight. Valid values range from 1 to 100.
Usage Guidelines This command configures custom DOCSIS priority to excess ratio mappings for downstream service
flows.
Examples The following example shows how to configure custom DOCSIS priority to excess ratio mappings for
downstream service flows:
Router# configure terminal
Router(config)# interface cable 8/0/0
Router(config-if)# cable downstream qos wfq weights 10 20 30 40 50 60 70 80
Syntax Description token-bucket (Optional) Specifies the token-bucket filter algorithm, which enforces an average
long-term transmission rate while permitting occasional bursts.
shaping (Optional in Release 12.1 EC, Required in Release 12.2 BC) Enables rate limiting
on the downstream port using the token-bucket policing algorithm with default
traffic shaping parameters.
granularity msec (Optional) Specifies traffic shaping granularity in milliseconds. Valid values are 1,
2, 4, 8, or 16 milliseconds.
max-delay msec (Optional) Specifies the maximum traffic-shaping buffering delay in milliseconds.
Valid values are 128, 256, 512, or 1028 milliseconds. As a general guideline, the
lower the downstream rates, the higher the delay should be to ensure full use of the
bandwidth.
weighted-discard (Optional) Specifies the weighted discard algorithm.
exp-weight (Optional) Specifies the weight for the exponential moving average of loss rate.
Valid values are from 1 to 4.
Command Default In Cisco IOS Release 12.1 EC and earlier releases, the system defaults to monitoring the traffic to and
from each CM over each 1-second period, and if the CM exceeds its bandwidth quota for that second,
the CMTS router drops packets for the rest of the second (no cable downstream rate-limit).
In Cisco IOS Release 12.2 BC and later releases, the token-bucket and shaping keywords are on by
default, and the max-delay option is set to 128 milliseconds (cable downstream rate-limit
token-bucket shaping max-delay 128).
Note In Cisco IOS Release 12.2 BC, do not use the cable downstream rate-limit token command without
specifying the shaping option, because this results in packet drops.
Release Modification
12.2(4)BC1 Support was added to the 12.2 BC train, and the defaults were changed so that
the shaping keyword is on by default, to accommodate DOCSIS 1.1
requirements.
12.3BC This command was integrated into Cisco IOS Release 12.3BC.
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA. Support for
the Cisco uBR7225VXR router was added.
Usage Guidelines The cable downstream rate-limit command specifies the type of DOCSIS rate limiting that the CMTS
router imposes on downstream traffic that is sent to the CMs. When rate-limiting is enabled, traffic to
the CM is examined to ensure it will not exceed the limit set for the CM.
For DOCSIS networks, the best rate limiting algorithm combines the token-bucket and shaping to use
keywords, which is optimized for relatively steady data rates, such as are used for web browser, without
allowing the user to exceed the maximum allowable download rate that is specified in the DOCSIS
configuration file.
Note The token-bucket and shaping options are the default in Cisco IOS Release 12.2 BC and should not be
changed. If using a 64 kbps downstream rate, you can avoid a performance impact by turning off the
shaping option, but this is not recommended for DOCSIS 1.1 operation because it can result in erratic
traffic patterns and packet drops on the downstream.
If a packet would exceed the traffic limits for a CM, the CMTS router will buffer the packet, up to the
maximum delay time given by the max-delay option, so that the traffic can be sent at a later time when
it would not violate the maximum downstream traffic limits. If the packet is still too large, or if the
volume of traffic consistently exceeds the traffic limits, even after the delay, the CMTS router begins
dropping packets.
The default behavior of the cable downstream rate-limit command was changed in Cisco IOS
Release 12.2 BC to accommodate the different requirements of DOCSIS 1.1 operation (which requires
the use of the token-bucket rate-limiting algorithm). This default is optimized for downstream traffic
rates that are higher than 84 kbps.
If you are using a 64 kbps downstream traffic rate on a Cisco CMTS router that is running Cisco IOS
Release 12.2 BC, you should set the max-delay option to 256 milliseconds to avoid a performance
impact on TCP/IP traffic that uses packets larger than 1024 bytes (such as FTP or HTTP web traffic).
Alternatively, you can set the max-burst option on the cable service class command to 3044, which is
two packets of the minimum size for DOCSIS 1.1 networks.
Decreasing the max-delay value increases how often the packets in the entire queue are processed, while
decreasing the granularity value increases the accuracy of the shaping mechanism. Decreasing these
values, however, could result in a possible increase in CPU processor usage. In most circumstances, this
increase in processor usage is negligible, but it should be monitored whenever fine-tuning the max-delay
or granularity values.
Tip For more information about the DOCSIS 1.1 rate-limiting specifications, see section C.2.2.5.2,
Maximum Sustained Traffic Rate, in the DOCSIS 1.1 specification.
Examples The following example shows how to apply the token-bucket filter algorithm on a Cisco uBR7200 series
router running Cisco IOS Release 12.1 EC:
Router(config)# interface cable 6/0
Router(config-if)# cable downstream rate-limit token-bucket
The following example shows how to apply the token-bucket filter algorithm on a Cisco uBR10012
router running Cisco IOS Release 12.2 BC:
Router(config)# interface cable 5/1/0
Router(config-if)# cable downstream rate-limit token-bucket shaping
The following example shows how to use token-bucket shaping with a max-delay of 256 milliseconds
on a Cisco uBR7100 series router:
Router(config)# interface cable 1/0
Router(config-if)# cable downstream rate-limit token-bucket shaping max-delay 256
Syntax Description power-level Desired RF output power level in dBmV. The valid range is 45 to
63 dBmV.
Note The official range for acceptable power levels in the DOCSIS
specification is 50 to 61 dBmV. Cisco cable interfaces exceed
the DOCSIS specification, but power levels outside the DOCSIS
specifications should be used only in lab and test environments.
hccp-delta diff-pwr (Protect interfaces only) When using N+1 Hotstandby
Connection-to-Connection Protocol (HCCP) redundancy, the Protect
interface adds the diff-pwr value to the current Working interface’s
power value when a switchover occurs. This allows the router to
accommodate relative differences between the RF power levels in
Working and Protect interfaces. The valid range for diff-pwr is –12 to
+12 dBmV.
hccp-override override-pwr (Protect interfaces only) When using N+1 HCCP redundancy, the
Protect interface uses the override power value instead of the Working
interface’s current power value when a switchover occurs. This allows
the router to accommodate absolute differences between the RF power
levels in Working and Protect interfaces. The valid range for
override-pwr is 45 to 63 dBmV.
Note The official range for acceptable power levels in the DOCSIS
specification is 50 to 61 dBmV. Cisco cable interfaces exceed
the DOCSIS specification, but power levels outside the DOCSIS
specifications should be used only in lab and test environments.
Usage Guidelines The Cisco IOS command-line interface (CLI) allows the hccp-delta and hccp-override options to be
configured only on a Protect interface (an interface that has been configured with the hccp protect
command). However, it is possible to manually edit a configuration file on a TFTP server so that it
includes these options on a Working interface configuration, and then download that configuration to the
router from the TFTP server.
Take care that if you manually edit Cisco IOS configuration files that you specify these options only on
Protect interfaces. If you specify the hccp-delta or hccp-override option on a Working interface, the
router will modify the configured downstream power with the given power delta or override value.
Examples The following example shows the integrated upconverter on a Cisco uBR7100 series router being
configured for an RF output power level of 45 dBmV:
Router(config)# cable interface 1/0
Router(config-if)# cable downstream rf-power 45
The following example shows the first integrated upconverter on a Cisco uBR10012 router being
configured for an RF output power level of 53 dBmV:
Router(config)# cable interface 5/1/0
Router(config-if)# cable downstream rf-power 53
The following commands shows the first integrated upconverter being set to the default power level of
55 dBmV on the Cisco uBR10012 router:
Router(config)# cable interface 5/1/0
Router(config-if)# no cable downstream rf-power
Router(config-if)# exit
The following example shows a Protect interface being configured to add 3 dBmV to the current
Working RF power level when a switchover occurs:
Router(config)# cable interface 6/0/0
Router(config-if)# cable downstream rf-power hccp-delta 3
Router(config-if)# exit
The following example shows a Protect interface being configured to use an RF power level of 48 dBmV
instead of the current Working RF power level when a switchover occurs:
Router(config)# cable interface 6/0/0
Router(config-if)# cable downstream rf-power hccp-override 48
Router(config-if)# exit
Note The hccp-delta and hccp-override commands configure the power of the Protect interface at the time
of the switchover. To display the RF power currently being used on a cable interface, use the show
controller cable command.
Usage Guidelines By default, the integrated upconverter on the Cisco uBR7100 series router, Cisco uBR-MC16U,
Cisco uBR-MC28U, and the Cisco uBR10-MC5X20S/U cable interface line cards is disabled, and the
downstream port does not output any signal. The no form of this command enables the integrated
upconverter, allowing it to output an RF signal through the downstream port.
However, before a valid DOCSIS downstream signal can be output, the following must also be done:
• A valid downstream RF frequency must be configured using the cable downstream frequency
cable interface command.
• The cable interface must be enabled using the no shutdown command on the cable interface.
Note This command does not affect the IF output from the DS0 downstream port on the Cisco uBR7100 series
router. The Cisco uBR10-MC5X20S/U, Cisco uBR-MC16U, and Cisco uBR-MC28U cable interface
line cards do not provide IF output for their downstream ports.
Examples The following example enables the integrated upconverter on the Cisco uBR7100 series router:
Router(config)# cable interface 1/0
Router(config-if)# no cable downstream rf-shutdown
The following example enables the second integrated upconverter on a Cisco uBR-MC5X20S cable
interface line card in the Cisco uBR10012 router:
Router(config)# cable interface 7/0/1
Router(config-if)# no cable downstream rf-shutdown
The following commands must also be given before the DS0 RF port can transmit a valid RF signal:
Router(config-if)# cable downstream frequency center-frequency
Router(config-if)# no shutdown
Router(config-if)# exit
router(config)#
cable dsg
Note Effective with Cisco IOS Release 12.3(13a)BC, the cable dsg command is not available in Cisco IOS
software.
To enable the DOCSIS Set-Top Gateway (DSG) on a cable interface on a Cisco CMTS router, and to
configure its tunnel-mapping parameters, use the cable dsg command in interface or subinterface
configuration mode. To remove the DSG tunnel from the interface, use the no form of this command.
Syntax Description tunnel-MAC-address Well-known MAC address for the DSG tunnel.
group-ip-address Multicast group IP address for the DSG stream.
CA-vendor-name Name for the Conditional Access (CA) vendor that owns the DSG
tunnel. This parameter is a string up to 7 characters in length and
should match the vendor of the CA server. A maximum of four vendors
per router are supported.
Command Modes Interface (config-if) and subinterface configuration (config-subif) for cable interfaces only
Usage Guidelines This command enables DSG operations on the cable interface, creating a DSG tunnel that uses the
specified IGMP multicast address and well-known MAC address.
The tunnel-MAC-address could optionally be an Internet Group Management Protocol (IGMP) multicast
address, using the algorithm for converting host group IP address to an Ethernet MAC address that is
given in RFC 1112. If the MAC address is 0000.0000.0000, the DSG tunnel uses the algorithm given in
RFC 1112 to derive the multicast address for the tunnel as follows:
An IP host group address is mapped to an Ethernet multicast address by placing the low-order 23-bits of
the IP address into the low-order 23 bits of the Ethernet multicast address 01-00-5E-xx-xx-xx (hex).
Because there are 28 significant bits in an IP host group address, more than one host group address may
map to the same Ethernet multicast address.
For example, if you specify the command cable dsg 0.0.0 228.9.9.9 AAA, the command uses the IGMP
IP address of 228.9.9.9 to generate the MAC address of 0100.5E09.0909 for the DSG tunnel. If the IGMP
address were 228.129.9.9, the resulting MAC address would be 0100.5E01.0909.
You can specify only Global Scope (224.0.1.0 through 238.255.255.255) and Administratively Scoped
(239.0.0.0 through 239.255.255.255) addresses. You cannot use Local Scope addresses (224.0.0.0
through 224.0.0.255).
Entering the cable dsg command also automatically configures the interface for the appropriate IGMP
static group, using the ip igmp static-group command. Do not manually enter another ip igmp
static-group command for this interface, because the system assumes that this IGMP configuration is
for a separate configuration that cannot be used by the DSG subsystem.
Note If any previously configured static groups exist on this interface, you should remove those other ip igmp
static-group commands on a cable interface before you can enter the cable dsg command. If you do not
remove those other groups, the cable dsg command displays a warning notifying you that you should
remove them.
The no cable dsg command automatically removes the IGMP static group from the interface by issuing
the no ip igmp static-group command. Do not manually remove this static group yourself.
In addition, you must have enabled Protocol Independent Multicast (PIM) on the cable interface, using
the ip pim interface configuration command, before enabling and configuring DSG operations. The
DOCSIS Set-Top Gateway feature supports the following PIM modes:
• ip pim sparse-mode command—Configures sparse mode of operation.
• ip pim sparse-dense-mode command—Configures the interface for either sparse mode or dense
mode of operation, depending on the mode in which the multicast group is operating.
• ip pim dense-mode command—Configures dense mode of operation.
• For best performance, fast switching of IP multicast should be enabled on incoming and outgoing
interfaces, using the ip mroute-cache command.
• You cannot use the same IP multicast groups for both DSG traffic and for other IP multicast traffic.
If an IP multicast group is being used for DSG traffic, do not use the ip igmp static-group command
to manually configure that same IP multicast group for other, non-DSG traffic.
• Different CA vendors cannot share IP multicast addresses. Each vendor must use a unique set of IP
multicast addresses, and after an IP multicast address is assigned to a DSG tunnel, that same address
cannot be used for any other purpose. However, all other multicast addresses and groups can still be
used on the interface for other multicast applications.
• DSG-related IP unicast traffic is not supported. The CMTS receives the unicast traffic from the DSG
network controllers, but it does not forward that traffic to the set-top boxes.
• DSG traffic should be less than 2.048 Mbps per vendor, so as to conform to the DSG specifications.
• DSG does not support Baseline Privacy Interface (BPI)-encrypted IP multicast streams.
Note In Cisco IOS Release 12.2(15)BC2, N+1 HCCP high availability redundancy does not preserve the DSG
traffic and configuration after a switchover. If you configure a cable interface for both N+1 HCCP
redundancy and for DSG operations, DSG traffic does not continue after a switchover.
Examples The following example shows how to configure a cable interface on a Cisco uBR7246VXR router to
enable the DSG feature on cable interface 3/0, using a well-known MAC address of 0001.0002.0003 and
a destination IP address of 225.2.3.4:
interface cable 3/0
ip pim dense-mode
ip multicast rate-limit out group-list 123 1024
cable dsg 1.2.3 225.2.3.4 CCC
Note The above configuration also automatically configures the interface with the appropriate ip igmp
static-group command (ip igmp static-group 225.3.4.5). This command will appear in the interface
configuration and should not be removed manually.
The following example shows the error message that appears if you specify a broadcast IP address that
has already been added to the router’s IGMP database. This entry typically would have been created
manually on the router or dynamically by a customer premise equipment (CPE) device that is attached
to a cable modem on the cable network.
interface cable 3/0
cable dsg 1.1.1 224.3.3.10 cisco
Multicast group 224.3.3.10 is already in use on the interface Cable3/0, please retry.
The following example shows how to delete a DSG tunnel on a cable interface:
interface cable 4/0
no cable dsg 0020.0020.0020 230.8.8.8 abc
4d17h: DSG: interface Cable5/0 left the igmp static group 230.8.8.8.
4d17h: DSG: tunnel 0020.0020.0020 is removed
4d17h: DSG: the specified DSG entry has been removed.
The following example shows the error message that appears when a unicast IP address is specified
instead of a multicast IP address:
cable dsg cfr index dest-ip ipaddr [[tunnel index] [dest-ports start end] [priority priority]] [src-ip
ipaddr [src-prefix-len length]] | [disable | enable] | [in-dcd {yes | no}]
Syntax Description index Creates the DSG index identified by a number from 1 to 65535.
dest-ip ipaddr Defines the destination multicast group IP address. Required
for a new classifier and optional for an existing classifier.
tunnel index (Optional) Defines a tunnel index identified by a number from
1 to 65535.
dest-ports start end (Optional) Defines the destination TCP/UDP starting and
ending port range from 0 to 65535.
priority priority (Optional) Defines the classifier priority.
src-ip ipaddr (Optional) Defines the source IP address and prefix length, if
desired.
src-prefix-len length (Optional) Source prefix length.
disable (Optional) Disables this classifier. This is the default.
enable (Optional) Enables this classifier.
in-dcd {yes | no} (Optional) Includes (yes) or excludes (no) classifier in the DSG
rules of the Downstream Channel Descriptor (DCD) message.
Command Default A-DSG classifiers are undefined by default on a Cisco CMTS router. When configured, A-DSG
classifiers are enabled by default.
The dest-ip keyword is required for a new classifier, but optional for an existing classifier.
Usage Guidelines A-DSG classifiers can only be mapped to one DSG tunnel, but multiple classifiers can be mapped to one
tunnel. The Cisco CMTS router applies the classifier parameters to the packets received from the DSG
server in order to assign the packet to the appropriate DSG tunnel.
When you use the in-dcd yes option, the classifiers are also included in the DSG rules as part of the DCD
message.
Examples The following example shows A-DSG classifier global configuration on a Cisco CMTS router:
cable dsg cfr 1 dest-ip 224.10.10.101 tunnel 1 dest-port 0 65535 priority 1
cable dsg cfr 2 dest-ip 224.10.10.102 tunnel 2 dest-port 0 65535 priority 1
cable dsg cfr 3 dest-ip 224.10.10.103 tunnel 3 dest-port 0 65535 priority 1
cable dsg cfr 4 dest-ip 224.10.10.104 tunnel 4 dest-port 0 65535 priority 1
cable dsg cfr 5 dest-ip 224.10.10.105 tunnel 1 dest-port 0 65535 priority 1
cable dsg cfr 6 dest-ip 224.10.10.106 tunnel 2 dest-port 0 65535 priority 1
Syntax Description list-index Defines the DSG channel list and index identifier as a number in the range 1
to 65535.
index entry-index Defines the DSG channel frequency entry index as a number in the range 1
to 65535.
freq freq Defines the center frequency of the downstream channel in the range
47000000 to 862000000 Hz.
Command Default A-DSG channel lists are disabled and undefined by default.
Usage Guidelines The channel list entry created with this command can be associated to a downstream interface and be
included in the Downstream Channel Descriptor (DCD) message by using the cable downstream dsg
chan-list command.
Examples The following example shows A-DSG channel list global configurations on a Cisco CMTS router:
cable dsg chan-list 1 index 1 freq 47000000
cable dsg chan-list 1 index 2 freq 125000000
cable dsg chan-list 1 index 3 freq 55500000
cable dsg chan-list 2 index 1 freq 47000000
cable dsg chan-list 2 index 2 freq 125000000
cable dsg chan-list 2 index 3 freq 55500000
Syntax Description client-list-id Defines an identifier for the DSG client list as a number from 1 to
65535.
id-index id Defines the DSG client index identifier as a number from 1 to 65535.
application-id app-id Defines the DSG client type application identifier as a hexadecimal
value from 1 to FFFF.
broadcast [broadcast-id] Defines an optional DSG client type broadcast value:
• 1—Contains Society of Cable Telecommunications Engineers
(SCTE) 65.
• 2—Contains SCTE 18.
• 3—Contains OpenCable Application Platform (OCAP) Object
Carousel (OCAP 1.0)
• 4—Contains OpenCable Common Download Carousel
(OC-CD).
• 5 to 55534—Reserved for future use.
• 55535 to 65535—Reserved for Multipler Service Operator
(MSO)-specific use.
ca-system-id sys-id Defines the DSG client type CA system identifier as a hexadecimal
value from 1 to FFFF.
mac-addr mac-addr Defines the DSG client type hexadecimal MAC address.
Command Default Client lists for A-DSG are not configured by default.
Release Modification
12.3(17a)BC2 The broadcast-id argument was added. Support for the same DSG client
identifier to be associated with multiple DSG tunnels was added.
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 Beginning in Cisco IOS Release 12.3(17a)BC2, the same DSG client identifer can be associated with
multiple DSG tunnels.
Examples The following example shows global configuration for four A-DSG client lists:
cable dsg client-list 1 id-index 1 broadcast
cable dsg client-list 2 id-index 2 application-id FFFF
cable dsg client-list 3 id-index 3 ca-system-id EEEE
cable dsg client-list 4 id-index 4 mac-addr 0100.5e0a.0a04
To enable keepalive messages over DOCSIS Set-Top Gateway (DSG) tunnels on all cable interfaces, use
the cable dsg keepalive command in global configuration mode. To disable DSG keepalives, use the no
form of this command.
Command Default Keepalive messages are disabled (no cable dsg keepalive).
Usage Guidelines By default, a Cisco CMTS router does not send keepalive messages on any DSG tunnels. When
keepalives are enabled using the cable dsg keepalive command, the Cisco CMTS router sends one
keepalive message each second on each DSG tunnel on each downstream. In Cisco IOS Release
12.2(15)BC2, the keepalive packet is a null packet.
Note Do not enable DSG keepalive messages unless your application and DSG set-top boxes require them.
Tip Use the show cable dsg command to display whether keepalive messages are enabled.
Examples The following example shows how to enable DSG keepalives on all cable interfaces on the router:
cable dsg keepalive
The following example shows how to disable DSG keepalives on all cable interfaces, which is the default
configuration:
cable dsg tg
To add a DOCSIS Set-Top Gateway (DSG) tunnel group to a subinterface, use the cable dsg tg command
in cable subinterface configuration mode. To remove the DSG tunnel group from the subinterface, use
the no form of this command.
Usage Guidelines You can associate a DSG tunnel group to only one subinterface within the same bundle interface. When
you remove the tunnel group from the global configuration, ensure that you remove the corresponding
DSG tunnel group from the subinterface.
Examples The following example shows how to associate a DSG tunnel group to a subinterface:.
Router# configure terminal
Router(config)# interface bundle 11.2
Router(config-subif)# cable dsg tg 61
Router(config-subif)# end
Syntax Description group-id Specifies the A-DSG tunnel group identifier as a number from 1–65535.
channel-id Specifies the downstream channel identifier as a number from 1–65535.
priority rule-priority Specifies the A-DSG rule priority as a number from 0–255.
enable Enables the specified A-DSG tunnel group.
disable Disables the specified A-DSG tunnel group. This is the default.
Usage Guidelines The cable dsg tg channel command establishes the configuration of the tunnel group. You can use the
disable and enable keyword forms of the command to deactivate and activate the tunnel group
configuration. To remove the configuration, use the no form of the command.
Examples The following example shows configuration and activation of a tunnel group with ID of 1 and channel
ID of 2:
Router(config)# cable dsg tg 1 channel 2
Command Description
cable dsg tg channel Associates a group of A-DSG tunnels to one or more downstream interfaces on
a Cisco CMTS router.
cable dsg tg channel Configures the upstream channel IDs for an A-DSG tunnel group on a Cisco
ucid CMTS router.
cable dsg tg channel Specifies a vendor-specific group for an A-DSG tunnel group on a Cisco
vendor-param CMTS router.
cable dsg timer Configures the A-DSG timer on a Cisco CMTS router.
cable dsg tunnel Creates A-DSG tunnels on a Cisco CMTS router.
cable dsg tunnel Associates a cable service class with an A-DSG tunnel on a Cisco CMTS
srv-class router.
Syntax Description group-id Specifies the A-DSG tunnel group identifier as a number from 1–65535.
channel-id Specifies the downstream channel identifier as a number from 1–65535.
upstream-id Specifies one or more upstream channel IDs as a number from 1–8.
Usage Guidelines The cable dsg tg channel command must be configured before this command is made available.
Examples The following example shows configuration of a tunnel group with ID of 1 and channel ID of 2, followed
by configuration of the upstream channel IDs associated with the tunnel group:
Router(config)# cable dsg tg 1 channel 2
Router(config)# cable dsg tg 1 channel 2 ucid 1 2 3 4 5 6 7 8
Command Description
cable dsg tg channel Specifies a vendor-specific group for an A-DSG tunnel group on a Cisco
vendor-param CMTS router.
cable dsg timer Configures the A-DSG timer on a Cisco CMTS router.
cable dsg tunnel Creates A-DSG tunnels on a Cisco CMTS router.
cable dsg tunnel Associates a cable service class with an A-DSG tunnel on a Cisco CMTS
srv-class router.
Syntax Description group-id Specifies the A-DSG tunnel group identifier as a number from 1–65535.
channel-id Specifies the downstream channel identifier as a number from 1–65535.
vendor-group Specifies the A-DSG vendor-specific group ID as a number from
1–65535.
Usage Guidelines The cable dsg tg channel command must be configured before this command is made available. You
also need to configure the vendor-specific parameter list using the cable dsg vendor-param command
before you can associate it with the tunnel group.
Examples The following example shows configuration of the vendor-specific parameter list, followed by
configuration of a tunnel group and ssociation with the defined vendor group 3:
! Configure the vendor-specific parameter list
cable dsg vendor-param 3 vendor 1 oui ABCDEC value 0101AB
!
! Configure the tunnel group and associate the vendor group to the tunnel
!
cable dsg tg 1 channel 2
cable dsg tg 1 channel 2 vendor-param 3
cable dsg timer index [Tdsg1 Tdsg1] [Tdsg2 Tdsg2] [Tdsg3 Tdsg3] [Tdsg4 Tdsg4]
no cable dsg timer index [Tdsg1 Tdsg1] [Tdsg2 Tdsg2] [Tdsg3 Tdsg3] [Tdsg4 Tdsg4]
Syntax Description index Defines the DSG timer and associates to an index for the downstream
channel as a number from 1 to 65535.
Tdsg1 Tdsg1 (Optional) DSG Initialization Timeout (Tdsg1) setting from 1 to 65535.
Tdsg2 Tdsg2 (Optional) DSG Operational Timeout (Tdsg2) setting from 1 to 65535.
Tdsg3 Tdsg3 (Optional) DSG Two-Way Retry Timer (Tdsg3) setting from 0 to 65535.
Tdsg4 Tdsg4 (Optional) DSG One-Way Retry Timer (Tdsg4) setting from 0 to 65535.
Usage Guidelines The A-DSG timer entry can associated to the downstream to encode into the DCD message.
Examples The following example shows global configuration of three A-DSG timers:
cable dsg timer 1 Tdsg1 1 Tdsg2 2 Tdsg3 3 Tdsg4 4
cable dsg timer 2 Tdsg1 2 Tdsg2 22 Tdsg3 33 Tdsg4 44
cable dsg timer 3 Tdsg1 2 Tdsg2 600 Tdsg3 300 Tdsg4 1800
Command Description
cable dsg client-list Configures the A-DSG client parameters and the associated DSG rule
on a Cisco CMTS router.
cable dsg tg channel Associates a group of A-DSG tunnels to one or more downstream
interfaces on a Cisco CMTS router.
cable dsg tg channel ucid Configures the upstream channel IDs for an A-DSG tunnel group on a
Cisco CMTS router.
cable dsg tg channel Specifies a vendor-specific group for an A-DSG tunnel group on a
vendor-param Cisco CMTS router.
cable dsg tunnel Creates A-DSG tunnels on a Cisco CMTS router.
cable dsg tunnel srv-class Associates a cable service class with an A-DSG tunnel on a Cisco
CMTS router.
cable dsg vendor param Configures vendor-specific parameters for A-DSG on a Cisco CMTS
router.
cable dsg tunnel tunnel-id mac-addr mac-addr tg tunnel-group-id clients number [disable |
enable]
Syntax Description tunnel-id Defines the DSG tunnel with an identifier as a number from 1–65535.
mac-addr mac-addr Specifies the multicast group MAC address in hexadecimal format.
tg tunnel-group-id Associates a tunnel group ID as a number from 1–65535.
clients number Specifies the client to which the configuration applies as a number
from 1–65535.
disable (Optional) Disables the specified A-DSG tunnel.
enable (Optional) Enables the specified A-DSG tunnel.
Defaults A-DSG tunnels are not configured by default, but are enabled by default once configured.
Usage Guidelines The cable dsg tunnel command establishes the configuration of the tunnel. You can use the disable and
enable keyword forms of the command to deactivate and activate the tunnel configuration. To remove
the configuration, use the no form of the command.
Each tunnel is mapped to the destination MAC address and once defined, can be associated with a
configured QoS service class name using the cable dsg tunnel srv-class command.
Examples The following example shows configuration of four A-DSG tunnels on a Cisco CMTS router:
cable dsg tunnel 1 mac-addr 0100.5e0a.0a01
cable dsg tunnel 2 mac-addr 0100.5e0a.0a02
cable dsg tunnel 3 mac-addr 0100.5e0a.0a03
cable dsg tunnel 4 mac-addr 0100.5e0a.0a04
Syntax Description tunnel-id Identifies the DSG tunnel with an identifier as a number from
1–65535.
class-name Specifies the name of a configured cable service class.
Defaults Cable service classes are not configured by default or associated with a DSG tunnel.
Usage Guidelines The A-DSG tunnel and tunnel group must be created first before the cable dsg tunnel srv-class
command becomes available to associate the tunnel with a configured QoS service class.
Examples The following example shows the configuration of a cable service class named “test” on a Cisco CMTS
router, followed by the association of that test cable service class with a DSG tunnel:
Router(config)# cable service class 1 name test
Router(config)# cable service class 1 downstream
Router(config)# cable service class 1 max-rate 20000
Router(config)# cable service class 1 min-rate 3000
Router(config)# cable dsg client-list 1 id-index 1 mac-addr 0050.4d00.0007
Router(config)# cable dsg tg 1 channel 1
Router(config)# cable dsg tunnel 1 mac-addr 0050.4d00.0007 tg 1 clients 1
Router(config)# cable dsg tunnel 1 srv-class test
When the service class name is configured without the default MQoS configuration, the following error
message is displayed and the configuration is rejected prompting the user to configure the default MQoS.
Router(config)# cable dsg tunnel 1 srv-class test
The default mqos doesn't exist, please, create one and then reconfigure service class name
to tunnel 1
Router(config)#
When the last service class name is not configured, the following error message is displayed prompting
the user to remove the default MQoS (if not needed.)
Router(config)# no cable dsg tunnel 1 srv-class test
There is no DSG tunnel associated with a service class name, so, remove the default mqos
if not needed
Router(config)#
cable dsg vendor-param group-id vendor vendor-index oui oui value value-in-TLV
no cable dsg vendor-param group-id vendor vendor-index oui oui value value-in-TLV
Syntax Description group-id Defines the DSG vendor parameter and associates with a DSG group.
vendor vendor-index Selects the DSG vendor and associated DSG index.
oui oui Selects the DSG Organizationally Unique Identifier (OUI) setting.
value value-in-TLV Sets the type/length value for the defined DSG vendor.
Usage Guidelines The vendor-specific parameters can be associated to the downstream to encode into the Downstream
Channel Descriptor (DCD) message.
To associate a vendor parameter list with a tunnel group, use the cable dsg tg channel vendor-param
command. The same vendor parameter list can be associated with multiple tunnel groups.
Examples The following sample configuration illustrates global vendor parameters for A-DSG:
cable dsg vendor-param 1 vendor 1 oui ABCDEA value 0101AB
cable dsg vendor-param 2 vendor 1 oui ABCDEB value 0101AB
cable dsg vendor-param 3 vendor 1 oui ABCDEC value 0101AB
Command Description
cable dsg client-list Configures the A-DSG client parameters and the associated DSG rule on a
Cisco CMTS router.
cable dsg tg channel Associates a vendor-specific group with an A-DSG tunnel group on a Cisco
vendor-param CMTS router.
cable dsg timer Configures the A-DSG timer on a Cisco CMTS router.
cable dsg tunnel Creates A-DSG tunnels on a Cisco CMTS router.
cable dsg tunnel Associates a cable service class with an A-DSG tunnel on a Cisco CMTS
srv-class router.
cable ds-max-burst
To enable a specialized Enhanced-Rate Bandwidth Allocation (ERBA) feature on the Cisco uBR10012
router with Performance Routing Engine 2 (PRE2) or Performance Routing Engine 4 (PRE4) modules,
use the cable ds-max-burst command in global configuration mode. To remove this configuration, use
the no form of this command.
cable ds-max-burst [burst-threshold threshold peak-rate peak-rate]
no cable ds-max-burst
Syntax Description burst-threshold Optional keyword and value defines the burst threshold in Kbytes, with a
threshold valid range from 64 Kbyte to 2 GB. By default, this setting is 1MB. This
value is used to compare with the per-service flow maximum traffic burst
value as defined in DOCSIS 2.0.
peak-rate peak-rate Peak Rate in Kbps. The default value of peak-rate is zero, which represents
the line rate.
The peak-rate value is a global value and is applied to all the service flows
created after the configuration of cable ds-max-burst command.
Defaults This configuration is disabled by default on the Cisco uBR10012 router. This command is not required
nor supported on the Cisco uBR7100 Series, Cisco uBR7225VXR and Cisco uBR7246VXR router.
Usage Guidelines Cisco IOS Release 12.3(21)BC introduces the ERBA feature on the Cisco uBR10012 CMTS with
Performance Routing Engine 2 (PRE2) modules. The ERBA feature in Cisco IOS release 12.3(21)BC is
characterized by the following enhancements:
• Enables support for the DOCSIS1.1 Downstream Maximum Transmit Burst parameter on the Cisco
CMTS by using cable ds-max-burst configuration command. This command is not supported on
the Cisco uBR7225VXR, Cisco uBR7246VXR and the Cisco uBR7100 Series routers, as this
parameter is supported by default.
• Allows DOCSIS1.0 modems to support the DOCSIS1.1 Downstream Maximum Transmit Burst
parameter by using DOCSIS QoS profile. This feature uses the cable qos pro max-ds-burst
configuration command.
Note The cable ds-max-burst and related commands are supported strictly on the Cisco uBR10012 router
with PRE2 or PRE4 modules on Cisco IOS Release 12.3(21)BC or later releases.
To displays service flows on the Cisco uBR10012 router with PRE2 or PRE4, and identifies which
service flows have maximum burst enabled, use the following command in privileged EXEC mode:
show cr10k-rp cable slot/subslot/port sid service-flow ds
– slot = 5 to 8
– subslot = 0 or 1
– port = 0 to 4 (depending on the cable interface)
For additional information about the cable qos profile command and configuring QoS profiles, refer to
the following documents on Cisco.com:
• DOCSIS 1.1 for the Cisco CMTS
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html
Examples The following example illustrates typical command sequence when using this command to configure
ERBA on the Cisco uBR10012 router, with a sample burst threshold setting:
Router> enable
Router# configure terminal
Router(config)# cable ds-max-burst burst-threshold 2048 peak-rate 1000
Router(config)# Ctrl^Z
Router# show cr10k-rp cable 7/0/0 sid service-flow ds
When this feature is enabled, new service flows with burst size larger than the burst threshold are
supported. However, the existing service flows are not affected.
When this feature is disabled, no new service flows are configured with the Downstream Maximum
Transmit Burst parameter—the cable ds-max-burst command settings. However, the existing service
flows are not affected.
The following example illustrates configuration of the ERBA maximum burst for the specified service flow:
Router# sh cr10k-rp c7/0/0 1 service-flow ds
RP SFID LC SFID Conform Exceed Conform Exceed Total QID
Xmit Pkts Xmit Pkts Drop Pkts Drop Pkts Pkts
32930 10 41 0 0 0 41 131349
Forwarding interface: Modular-Cable1/0/0:0
32931 13 0 0 0 0 0 131350
Forwarding interface: Modular-Cable1/0/0:0
cable dynamic-bw-sharing
To enable dynamic bandwidth sharing (DBS) on a specific modular cable or wideband cable interface,
use the cable dynamic-bw-sharing command in interface configuration mode. To disable DBS on the
interface and revert to static bandwidth sharing, use the no form of this command.
cable dynamic-bw-sharing
no cable dynamic-bw-sharing
Command Default Dynamic bandwidth sharing is disabled and static bandwidth sharing is enabled.
Usage Guidelines DBS may be configured on a modular cable or wideband cable interface only when the interface is
administratively down. Additionally, the interface must be administrative down when using the no form
of this command to disable dynamic bandwidth sharing.
Examples The following example enables dynamic bandwidth sharing on a modular cable interface using the
cable dynamic-bw-sharing command:
Router(config)# interface modular-cable 1/0/0:1
Router(config-if)# shutdown
Router(config-if)# cable dynamic-bw-sharing
Router(config-if)# no shutdown
The following example enables dynamic bandwidth sharing on a wideband cable interface using the
cable dynamic-bw-sharing command:
Router(config)# interface wideband-cable 1/0/0:0
Router(config-if)# shutdown
Router(config-if)# cable dynamic-bw-sharing
Router(config-if)# no shutdown
cable dynamic-secret
To enable the Dynamic Shared Secret feature, so that Data-over-Cable Service Interface Specifications
(DOCSIS) configuration files are verified with a Message Integrity Check (MIC) that has been created
with a dynamically generated shared secret, use the cable dynamic-secret command in cable interface
configuration mode. To disable this feature, use the no form of this command.
no cable dynamic-secret
Syntax Description lock Allows CMs that do not pass MIC verification to come online, but with
a restrictive quality of service (QoS) configuration that limits access to
the network. The CMTS also locks those CMs so that they must be
offline for 24 hours before being allowed to reregister with a valid
DOCSIS configuration file. (You can also manually unlock a cable
modem using the clear cable modem lock command.)
lock-qos (Optional) Specifies the QoS profile to be assigned to the CM while it
is locked. The valid range is 1 to 256. If not specified, the CM is locked
into a CMTS-created profile that limits both the upstream and
downstream to 10 Kbps.
Note The QoS profile must have already been created before it can
assigned using the lock lock-qos option.
mark Allows CMs to come online even if they do not present a DOCSIS
configuration file with a valid CMTS MIC, but the CMTS prints a
warning message and marks those CMs with an exclamation point (!)
in the show cable modem command.
reject Rejects registration for CMs with DOCSIS configuration files that
contain an invalid CMTS MIC.
nocrypt (Optional) Specifies that the filename for DOCSIS configuration files
should not be encrypted when the Cisco CMTS sends the files to CMs.
The CMTS instead transmits the files using their original filenames.
The nocrypt option slightly decreases the security provided by the
dynamic shared secret feature, but it allows the operator to poll the
DOCSIS config file name listed by the cable modem for more
convenient network management.
Note A cable modem that is running unauthorized or hacked
software can return whatever SNMP values the user desires.
This information should therefore not be trusted by the billing
and provisioning systems.
Defaults The Dynamic Shared Secret feature is disabled. When enabled, the filenames for DOCSIS configuration
files are encrypted.
Note Configuring the Dynamic Shared Secret feature on the master interface in a bundle also automatically
configures it for all interfaces in the bundle.
Usage Guidelines The cable dynamic-secret configuration command automatically creates a unique DOCSIS shared
secret on a per-modem basis, creating a one-time-use DOCSIS configuration file that is valid only for
the current session. This ensures that a DOCSIS configuration file that has been downloaded for one
cable modem can never be used by any other modem, nor can the same modem reuse this configuration
file at a later time. This patent-pending feature is designed to guarantee that all registered modems are
using only the QOS parameters that have been specified by the DOCSIS provisioning system for that
particular modem at the time of its registration.
The cable dynamic-secret configuration command enhances the existing shared secret support on the
Cisco CMTS by using a one-time, dynamically generated shared secret each time a cable modem
registers. This prevents theft-of-service attacks in which users are able to substitute a DOCSIS
configuration file that provides a higher-level of service during the registration phase.
The DOCSIS specification allows cable service providers to use a shared secret to create the CMTS MIC
value that is stored in a DOCSIS configuration file. If a user attempts to register with the CMTS using a
different or modified DOCSIS configuration file, the CMTS can compare the CMTS MIC value sent by
the cable modem with the CMTS MIC it has calculated. If the two MIC values are different, the file has
been modified.
The cable dynamic-secret command allows the CMTS to dynamically create the shared secret at the
time that the cable modem is registering, and that shared secret is valid only for that particular session
with that particular cable modem. A new dynamically generated shared secret is used each time each
cable modem registers, which prevents users from guessing the shared secret and using it again to
register with a modified DOCSIS configuration file.
If the cable modem’s DOCSIS configuration file fails the CMTS MIC verification check, one of the
following messages is displayed on the console:
%UBR7200-4-BADCFGFILE: Modem config file platinum.cm at C3/0: CMTS MIC Invalid
%UBR7200-4-BADCFGFILE: Modem config file platinum.cm at C3/0: No CMTS MIC
If the error message specifies that the reason for the failure is “CMTS MIC Invalid,” the CMTS MIC was
not encoded with the proper dynamically generated shared secret. If the reason is “No CMTS MIC,” the
DOCSIS configuration file did not contain any value for the CMTS MIC, which could indicate that the
customer has attempted to bypass the DOCSIS security checks by creating the user’s own DOCSIS
configuration file without any MIC values.
Note The Dynamic Shared Secret feature does not affect the use of the original shared secret or secondary
shared secrets that are configured using the cable shared-secondary-secret and cable shared-secret
commands. If these shared secrets are configured, the Cisco CMTS continues to use them to validate the
original DOCSIS configuration file that is downloaded from the TFTP server. If the DOCSIS
configuration file fails to pass the original or secondary shared secret verification checks, the cable
modem is not allowed to register, and the Dynamic Shared Secret feature is not invoked for that
particular cable modem.
Note The Cisco uBR7100 series router does not support the Dynamic Shared Secret feature when running in
MxU bridging mode.
The original filename for the DOCSIS configuration file is automatically encrypted by default to prevent
unauthorized parties from obtaining any useful information from the filename, or from attempting to
replace the original file with their own. This encryption can be disabled, using the nocrypt option, so
that DOCSIS configuration files are sent using their original filenames.
Note Do not use the cable dynamic-secret command along with the ip tftp-source command in Cisco IOS
Release 12.2(15)BC1, because this could result in certain models of CMs not being able to come online
but instead be stuck in the init(o) state. This restriction is removed in Cisco IOS Release 12.2(15)BC2
and later releases.
Modes of Operation
The cable dynamic-secret command offers three different possible responses to cable modems that fail
the CMTS MIC verification check:
• When the mark option is used, the CMTS allows CMs to come online even if they fail the CMTS
MIC validity check. However, the CMTS also prints a warning message on the console and marks
the cable modem in the show cable modem command with an exclamation point (!), so that this
situation can be investigated. The following message is displayed on the console when such a CM
registers with the Cisco CMTS:
06:53:57: %UBR7200-4-CMMARKED: Cable Modem 00ff.ffee.ddcc in C3/0 attempted theft of
service
• When the lock option is used, the CMTS assigns a restrictive QoS configuration to CMs that fail the
CMTS MIC validity check. If an optional lock-qos profile is specified, the CMTS assigns this profile
to the CM while it is locked.
If the lock-qos profile is not specified, the CMTS uses a special QoS configuration that limits the
network access for these CMs by restricting their downstream and upstream service flows to a
maximum rate of 10 kbps. (If you do not specify the lock-qos profile, you must also allow cable
modems to create QoS profiles, using the cable qos permission command. If you do not do this and
use the lock option without specifying a particular QoS profile, locked cable modems will not be
allowed to register until the lock clears or expires.)
If a customer resets their CM, the CM will reregister but still uses the restricted QoS profile. A
locked CM continues with the restricted QoS profile until it goes offline and remains offline for at
least 24 hours, at which point it is allowed to reregister with a valid DOCSIS configuration file. This
option frustrates users who are repeatedly registering with the CMTS in an attempt to guess the
shared secret, or to determine the details of the Dynamic Shared Secret security system.
In addition, the following message is displayed on the console when a CM is locked.
Locked cable modems are shown with an exclamation point (!) in the show cable modem displays:
Router# show cable modem
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
0010.9507.01db 144.205.151.130 C5/1/0/U5 online(pt) 1 0.25 938 1 N
0080.37b8.e99b 144.205.151.131 C5/1/0/U5 online 2 -0.25 1268 0 N
0002.fdfa.12ef 144.205.151.232 C6/1/0/U0 online(pt) 13 -0.25 1920 1 N
0002.fdfa.137d 144.205.151.160 C6/1/0/U0 !online 16 -0.50 1920 1 N
0003.e38f.e9ab 144.205.151.237 C6/1/0/U0 !online 3 -0.50 1926 1 N
Router#
Tip You can also manually clear the lock on a CM by using the clear cable modem lock command.
• When the reject option is used, the CMTS refuses to allow CMs to come online if they fail the
CMTS MIC validity check. These cable modems appear with a MAC state of “reject(m)” in the
displays generated by the show cable modem command. After a short timeout period, the CM
attempts to reregister with the CMTS. The CM must register with a valid DOCSIS configuration file
before being allowed to come online. When the CM does come online, the CMTS prints a warning
message on the console and marks the cable modem in the show cable modem command with an
exclamation point (!), so that this situation can be investigated.
Tip Cisco recommends that you initially use the mark option, so that potential problems are identified
without immediately interfering with users’ ability to come online. After you identify and resolve these
initial problems, reconfigure the cable interfaces with the reject or lock option to block problem cable
modems that attempt to come online without a valid shared secret.
Note To account for possible network problems, such as loss of packets and congestion, the Cisco CMTS will
allow a cable modem to attempt to register twice before marking it as having failed the Dynamic Shared
Secret authentication checks.
Filename Encryption
By default, the cable dynamic-secret command encrypts the original filename for a DOCSIS
configuration file when the Cisco CMTS transmits the file to the CM. This filename changes in a
semi-random manner, making it difficult for users to predict the filename for the file that should be
downloaded to the CM.
This does mean, however, that the filenames specified in the DHCP HELLO and ACK messages are
different, and that the filenames on the CM and on the TFTP server are different. This could interfere
with custom network management applications and scripts. If this is the case, you can disable the
automatic filename encryption by adding the nocrypt option to the command.
The nocrypt option does slightly decrease the security provided by this feature, so this possibility should
be weighed against the ability to more conveniently manage the network.
Spoof TFTP
MAC Address Vendor Interface Count Dnld Dynamic Secret
Router#
If the CMTS cannot obtain the DOCSIS configuration file from the TFTP server, a message similar to
the following is displayed on the console:
%UBR7200-4-NOCFGFILE: Cannot read modem config file platinum.cm from C3/0: <reason>
where the reason can be one of the following, depending on the error that the TFTP server reported:
• Compression Failed
• File too big
• Invalid Checksum
• Invalid IP address or hostname
• Uncompression Failed
• User Abort
Examples The following example shows how to configure a cable interface on a Cisco uBR7200 series router with
the mark option, so that CMs that fail the MIC verification are allowed to register but are marked in the
show cable modem displays so that their situation can be further investigated:
Router# configure terminal
Router(config)# interface cable 4/0
Router(config-if)# cable dynamic-secret mark
Router(config-if)# exit
Router(config)# exit
Router#
The following example shows how to configure the cable interface on a Cisco uBR7100 series router, so
that CMs that fail the MIC verification are locked with a QoS profile that limits upstream and
downstream service flows to 10 kbps:
Router# configure terminal
Router(config)# cable qos permission create
Router(config)# cable qos permission update
Router(config)# interface cable 1/0
Router(config-if)# cable dynamic-secret lock
Router(config-if)# exit
Router(config)# exit
Router#
Note If you do not use the cable qos permission global configuration command to allow cable modems to
create their own QoS profiles, the CMTS rejects this command and displays the following error message:
%Need permission for modems to create QoS profile
The following example shows how to configure a cable interface so that CMs that fail the MIC
verification are locked with a specific QoS profile:
Router# configure terminal
Router(config)# interface cable 1/0
Router(config-if)# cable dynamic-secret lock 31
Router(config-if)# exit
Router(config)# exit
Router#
Note If the specified QoS profile does not exist, the CMTS rejects this command and displays the following
error message:
%Profile qos-id to lock modem does not exist
The following example shows how to configure a cable interface on a Cisco uBR7200 series router, so
that CMs that fail the MIC verification are not allowed to register and must reregister with a valid
DOCSIS configuration file before being allowed to come online:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable dynamic-secret reject
Router(config-if)# exit
Router(config)# exit
Router#
The following example shows how to disable the Dynamic Shared Secret feature on a cable interface on
the Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 6/1/0
Router(config-if)# no cable dynamic-secret
Router(config-if)# exit
Router(config)# exit
Router#
Syntax Description modem mac-address Specifies the hardware (MAC) address of a specific individual cable
modem to be excluded from the Dynamic Shared Secret feature. (You
cannot specify a multicast MAC address.)
oui oui-id Specifies the organization unique identifier (OUI) of a vendor, so that
cable modems from this vendor are excluded from the Dynamic Shared
Secret feature. The OUI should be specified as three hexadecimal bytes
separated by either periods or colons.
Command Default All modems are processed by the Dynamic Shared Secret feature when the feature is enabled.
Usage Guidelines When the cable dynamic-secret configuration command is configured on a cable interface, it
automatically includes all cable modems that register on that interface. To exclude one or more cable
modems from being processed by the Dynamic Shared Secret security checks, use the cable
dynamic-secret exclude command in global configuration mode.
You might want to exclude cable modems from the Dynamic Shared Secret security checks if they need
to download additional files from the TFTP server at registration time. For example, Cisco cable CPE
devices, such as the Cisco uBR925 cable access router, can be instructed to download a Cisco IOS
configuration file after downloading the DOCSIS configuration file.
However, when Dynamic Shared Secret checks are being used, the Cisco CMTS refuses to allow the
cable modem to download any other files after the first successful download of the DOCSIS
configuration file. To allow these cable modems to download their Cisco IOS configuration files, use the
cable dynamic-secret-exclude command to exclude them from the Dynamic Shared Secret checks.
You can exclude either a specific cable modem by its MAC address, or all of a vendor’s cable modems
by their OUI value. Excluded cable modems must still register according to the normal DOCSIS
provisioning procedures, but their DOCSIS configuration files are no longer verified by the Dynamic
Shared Secret security checks.
Tip When a cable modem is excluded from the Dynamic Shared Secret feature, the Dynamic Secret field in
its show cable modem verbose display shows “Excluded”.
Examples The following example shows how to exclude a specific cable modem, with the MAC address of
00d0.45ba.b34b, from being processed by the Dynamic Shared Secret feature:
Router# configure terminal
Router(config)# cable dynamic-secret exclude modem 00d0.45ba.b34b
Router(config)# exit
Router#
The following example shows how to exclude all cable modems with a vendor OUI value 00.01.B4 from
being processed by the Dynamic Shared Secret feature:
Router# configure terminal
Router(config)# cable dynamic-secret exclude oui 00.01.B4
Router(config)# exit
Usage Guidelines The Dynamic Shared Secret feature must be configured first before you can upgrade the firmware on
cable modems. To enable this feature, execute the cable dynamic-secret command in the cable interface
configuration mode.
Examples The following example dynamically inserts the correct IPv4 or IPv6 TLV values from the DOCSIS
configuration file to upgrade firmware on the cable modems.
Router(config)# cable dynamic-secret tftp insert-upgrade-server
Router(config)# end
New Commands
Modified Commands
cable enable-trap
To permanently set four CISCO-DOCS-EXT-MIB MIB attributes that enable the sending of a trap when
a CM changes between the online and offline states, use the cable enable-trap command in cable
interface configuration mode. To return to the default settings found in the MIB, which disable the
sending of these traps, use the no form of this command.
Syntax Description cmonoff-notification Enables or disables the sending of the notification traps.
cmonoff-interval Specifies the minimum interval that must pass before sending out a
new trap for the same CM.
time-in-secs Specifies the number of seconds (0 to 86400 seconds). The default
value is 600 seconds.
Command Default The default is to use the MIB defaults, which specify that traps are not to be sent, with an interval value
of 600 seconds (10 minutes).
Usage Guidelines This command sets four attributes in the CISCO-DOCS-EXT-MIB MIB, so that the new values can be
automatically loaded whenever the CMTS router powers on or reloads. To do so, put the appropriate
commands in the configuration file and save it to the CMTS router’s Flash memory. The CMTS router
automatically sets the appropriate MIB values when it processes the configuration file at startup.
These commands affect whether the CM online/offline notification trap (cdxCmtsCmOnOffNotification)
is sent, and if so, the minimum interval that must exist between traps that are sent for the same CM
undergoing the same state changes. The following describes the relationship between these commands
and the attributes in the CISCO-DOCS-EXT-MIB MIB:
• The cable enable-trap cmonoff-notification command sets the cdxCmtsCmOnOffTrapEnable
attribute to 1 (true), which enables the sending of the CM online and offline traps.
Note Setting the cmonoff-interval option and the cdxCmtsCmOnOffTrapInterval attribute has meaning only
if cdxCmtsCmOnOffNotification traps have been previously enabled.
Examples The following commands enable the sending of CM on or off traps, with a minimum interval of 1200
seconds between traps being sent for the same CM:
router(config)# interface c6/0
router(config-if)# cable enable-trap cmonoff-notification
router(config-if)# cable enable-trap cmonoff-interval 1200
router(config-if)# exit
router(config)#
cable event priority {alert | critical | debug | emergency | error | informational | notice |
warning} flags
Syntax Description alert Sets the event reporting flag for alert system error messages. (Alert messages
indicate that some type of system or connection failure has occurred and
requires immediate attention.)
critical Sets the event reporting flag for critical system error messages. (Critical
messages indicate that an error occurred which requires immediate attention
to avoid system or connection failure.)
debug Sets the event reporting flag for debug system error messages. (Debug
messages appear only when debugging has been enabled.)
emergency Sets the event reporting flag for emergency system error messages.
(Emergency messages indicate that the system has become unusable and
requires immediate attention. This problem might also be affecting other
parts of the network.)
error Sets the event reporting flag for error system error messages. (Error
messages indicate that an error condition occurred that requires attention to
resolve. Failure to address this problem will result in some type of system or
connection failure in the near future.)
informational Sets the event reporting flag for informational system error messages.
(Informational messages might or might not be significant to the system
administrators.)
notice Sets the event reporting flag for notice system error messages. (Notice
messages indicate that a situation occurred that is normal but is significant
enough that system administrators might want to notice.)
warning Sets the event reporting flag for warning system error messages. (Warning
messages indicate that a condition occurred that indicates attention is needed
in near future to avoid potential problems. Failure to address this problem
could result in some type of system or connection failure later on.)
flags Sets the event reporting flags value, in hex, which specifies how this
particular type of event message should be reported. The valid range is 0x0
through 0xF0, which is a bitmask specifying the types of reporting that
should be done. See the Usage Guidelines for details.
Command Default The defaults are configured as per the DOCSIS 1.1 Operations Support System Interface (OSSI)
Specification:
• Emergency and alert messages = (0x10) (reported to the local volatile log)
• Critical, error, warning, and notice = (0x70) (reported to the local volatile log, and forwarded as
traps and to the SYSLOG server)
• Information and debug = 0x0 (not reported)
Usage Guidelines The DOCSIS 1.1 specifications require the CMTS to generate a set of messages for DOCSIS-specific
events. These messages can be assigned one of eight priority levels, ranging from emergency (the highest
level) to debug (the lowest level), and the CMTS can be configured to log each level of messages
differently.
The Cisco CMTS supports the following types of logging, as defined by the
DOCS-CABLE-DEVICE-MIB MIB (RFC 2669):
• none (0x0) = DOCSIS messages are not reported. (The corresponding Cisco IOS event messages,
however, continue to be logged.)
• local-volatile (0x10) = DOCSIS messages are saved in a local log on the CMTS. This log can be
limited in size and can automatically discard previous messages to make room for incoming
messages.
• syslog (0x20) = DOCSIS messages are sent to a SYSLOG server (if one has been configured, using
the cable event syslog-server command).
• traps (0x40) = DOCSIS messages are sent as SNMP traps to one or more SNMP managers.
These values can be added together to specify that the CMTS should report an event in more than one
way. For example, a value of 0x70 specifies that the CMTS should record the event in its local volatile
log, and also send it both as a trap and as a SYSLOG message.
Note If event messages are configured for traps or syslog reporting, they must also be configured for either
local volatile or local non-volatile reporting. This means that values 0x20 (syslog-only), 0x40
(trap-only), and 0x60 (syslog and trap only) are not supported.
Use the cable event priority command to set the reporting flags for each type of event. This also
configures the appropriate instance of the docsDevEvReporting attribute DOCS-CABLE-DEVICE-MIB
MIB (RFC 2669) with the same value.
Note This command affects only the DOCSIS event messages, and does not affect how the Cisco IOS software
handles event messages. If SYSLOG traps are enabled on the Cisco CMTS (using the snmp-server
enable traps syslog command), they continue to be sent, regardless of the cable event priority
configuration.
Examples The following commands configure the Cisco CMTS so that it reports all emergency, alert, and critical
messages as SNMP traps and SYSLOG messages, as well as logging it in the local volatile log:
Router# configure terminal
The following commands configure the Cisco CMTS so that it reports the lowest priority messages only
to the local volatile log and SYSLOG server:
Router# configure terminal
Router(config)# cable event priority debug 0x30
Router(config)# cable event priority informational 0x30
Router(config)# cable event priority notice 0x30
Syntax Description ip-address Specifies the IPv4 or IPv6 address for the DOCSIS SYSLOG server, which is the
docsDevEvSyslog attribute in the DOCS-CABLE-DEVICE-MIB (RFC 2669). If the IP
address is 0.0.0.0 or 0:0:0:0::0, SYSLOG service is disabled for DOCSIS events.
Usage Guidelines The DOCSIS 1.1 specifications require the CMTS router to generate a set of messages for
DOCSIS-specific events. Use the cable event syslog-server command to enable DOCSIS SYSLOG
services and to set the IP address for the DOCSIS SYSLOG server (which is the docsDevEvSyslog
attribute in the DOCS-CABLE-DEVICE-MIB).
You can also configure the server’s IP address by using SNMP commands to set the docsDevEvSyslog
attribute directly. Setting the docsDevEvSyslog attribute also creates a matching cable event
syslog-server command in the router’s configuration.
When you specify the IP address for a DOCSIS SYSLOG server, either by using the cable event
syslog-server command or by setting the docsDevEvSyslog attribute, the Cisco CMTS router begins
generating event messages that conform to the DOCSIS 1.1 specifications. This format is similar to but
not identical to the format that is used by the Cisco IOS software. For example, the following message
is in the typical Cisco IOS software format:
%UBR7200-4-DCC_ACK_REJ_MSG_SYNTAX_ERROR: DCC-ACK rejected message syntax error
The same error message appears as follows when using the DOCSIS 1.1 format:
<133>CMTS[DOCSIS]:<67040500> DCC-ACK rejected message syntax error
To disable the sending of events to the DOCSIS SYSLOG server, you can use the no cable event
syslog-server command, or you can specify an IP address of 0.0.0.0 (cable event syslog-server 0.0.0.0).
Both commands set the docsDevEvSyslog attribute to 0.0.0.0 and disable DOCSIS SYSLOG service.
This does not, however, disable the Cisco IOS SYSLOG server (if one has been configured using the
logging ip-address command).
Note You can use the same SYSLOG server for both Cisco IOS event messages and for DOCSIS-style event
messages, but it might be more convenient to use separate servers for the two different message formats.
Use the logging ip-address command in global configuration mode to set the IP address for the
Cisco IOS SYSLOG server. The DOCSIS SYSLOG server collects only event messages for DOCSIS
events, using the DOCSIS format, while the Cisco IOS server collects all event messages (including
DOCSIS events), but using the standard Cisco IOS message format.
Tip For more information about DOCSIS SYSLOG services and event messages, see Section 4.4.2.2.2,
SYSLOG Message Format, in the DOCSIS 1.1 Operations Support System Interface (OSSI)
Specification (SP-OSSIv1.1-I06-020830). For more information about all cable-related event messages
that can be generated on a Cisco CMTS router, see the Cisco CMTS System Messages guide.
Examples The following command sets the docsDevEvSyslog attribute with an IPv4 address of 192.168.100.137:
cable event syslog-server 192.168.100.137
The following commands specifies different SYSLOG servers. The server at IPv4 address
192.168.100.137 receives the DOCSIS-style event messages, and the server at IPv4 address
192.168.100.138 receives the Cisco IOS style messages.
cable event syslog-server 192.168.100.137
logging 192.168.100.138
The following command sets the docsDevEvSyslog attribute to IPv4 address 0.0.0.0, which disables
DOCSIS SYSLOG services:
no cable event syslog-server
Note You can also disable DOCSIS SYSLOG services with the cable event syslog-server 0.0.0.0 command.
The following command specifies a DOCSIS SYSLOG server with an IPv6 address:
cable event syslog-server 2001:0DB8:0:ABCD::1
Command Description
cable event throttle-interval Specifies the throttle interval, which helps control how often
the Cisco CMTS router generates SNMP traps and SYSLOG
messages for DOCSIS event messages.
cable event throttle-threshold Sets the maximum number of SNMP traps and SYSLOG
messages that the Cisco CMTS router can generate for
DOCSIS event messages during the throttle interval.
snmp-server enable traps cable Enables traps for cable-related events.
snmp-server enable traps docsis-cmts Enables traps for DOCSIS-related MAC-layer events.
Syntax Description inhibited All SNMP traps and syslog messages for DOCSIS event messages are
suppressed.
maintainBelowThreshold Throttling is performed, so that SNMP traps and syslog messages are
suppressed if they would otherwise exceed the throttle threshold. The
Cisco CMTS resumes generating traps and messages at the start of the
next throttle interval.
stopAtThreshold Throttling is performed, so that the Cisco CMTS stops generating all
SNMP traps and syslog messages if they would exceed the throttle
threshold. The Cisco CMTS does not resume generating traps and
messages until directed to do so by repeating this command.
unconstrained SNMP traps and syslog messages for DOCSIS event messages are not
throttled.
Usage Guidelines This command sets the value of the docsDevEvThrottleAdminStatus attribute in the
DOCS-CABLE-DEVICE-MIB MIB (RFC 2669), which controls whether the Cisco CMTS should
throttle SNMP traps and syslog messages that are generated for DOCSIS event messages.
The DOCS-CABLE-DEVICE-MIB MIB supports the following threshold configurations:
• inhibited—The Cisco CMTS does not generate any SNMP traps or syslog messages for DOCSIS
events.
Tip For more information about DOCSIS syslog services and event messages, see Section 4.4.2.2.2, syslog
Message Format, in the DOCSIS 1.1 Operations Support System Interface (OSSI) Specification
(SP-OSSIv1.1-I06-020830). For more information about all cable-related event messages that can be
generated on the Cisco CMTS router, see the Cisco CMTS Error Message manual.
Examples The following commands configure the Cisco CMTS router to throttle SNMP traps and syslog messages
according to the specified throttle interval and threshold:
Router# configure terminal
Router(config)# cable event throttle-interval 90
Router(config)# cable event throttle-threshold 30
Router(config)# cable event throttle adminStatus maintainBelowThreshold
The following commands configure the Cisco CMTS router for the default behavior, so that it does not
throttle SNMP traps and syslog messages. The configured throttle interval and threshold are ignored.
Router# configure terminal
Router(config)# cable event throttle adminStatus unconstrained
Syntax Description seconds Length of the throttle interval, in seconds. The valid range is 0 to 2147483647 seconds, with
a default of 60 seconds.
Usage Guidelines The DOCSIS 1.1 specifications require the CMTS to generate a set of messages for DOCSIS-specific
events. In certain situations, such as a power outage that causes a mass reregistration of cable modems,
this can generate such a large volume of event messages that it can impact system performance.
To avoid this possibility, use the cable event throttle-interval command, together with the cable event
throttle-threshold command, to specify the maximum number of SNMP traps or syslog events that the
Cisco CMTS can generate for DOCSIS events over a specific interval:
• cable event throttle-interval—Specifies the length of the throttle interval.
• cable event throttle-threshold—Specifies the maximum number of SNMP traps and syslog events
that the Cisco CMTS can generate during that period.
The threshold value counts DOCSIS events, not SNMP traps or syslog messages. If a DOCSIS event
generates both an SNMP trap and a syslog message, the Cisco CMTS counts it as only one event.
Note The cable event throttle-interval and cable event throttle-threshold commands do not have any effect
unless the cable event throttle-adminStatus has been configured to allow the throttling of DOCSIS
event messages.
Tip For more information about DOCSIS syslog services and event messages, see Section 4.4.2.2.2, syslog
Message Format, in the DOCSIS 1.1 Operations Support System Interface (OSSI) Specification
(SP-OSSIv1.1-I06-020830). For more information about all cable-related event messages that can be
generated on the Cisco CMTS router, see the Cisco CMTS Error Message manual.
Examples The following commands configure the Cisco CMTS router so that it can generate a maximum number
of 30 SNMP traps and syslog messages for DOCSIS events over a 90-second period:
Router# configure terminal
Router(config)# cable event throttle-interval 90
Router(config)# cable event throttle-threshold 30
Syntax Description number Maximum allowable number of DOCSIS events for which the Cisco CMTS can generate
SNMP traps and syslog messages during the throttle period. The valid range is 0 to
2147483647, with a default of 10.
Usage Guidelines The DOCSIS 1.1 specifications require the CMTS to generate a set of messages for DOCSIS-specific
events. In certain situations, such as a power outage that causes a mass reregistration of cable modems,
this can generate such a large volume of event messages that it can impact system performance.
To avoid this possibility, use the cable event throttle-threshold command, together with the cable event
throttle-interval command, to specify the maximum number of SNMP traps or syslog events that the
Cisco CMTS can generate for DOCSIS events over a specific interval:
• cable event throttle-interval—Specifies the length of the throttle interval.
• cable event throttle-threshold—Specifies the maximum number of SNMP traps and syslog events
that the Cisco CMTS can generate during that period.
The threshold value counts DOCSIS events, not SNMP traps or syslog messages. If a DOCSIS event
generates both an SNMP trap and a syslog message, the Cisco CMTS counts it as only one event.
Note The cable event throttle-interval and cable event throttle-threshold commands do not have any effect
unless the cable event throttle-adminStatus has been configured to allow the throttling of DOCSIS
event messages.
Tip For more information about DOCSIS syslog services and event messages, see Section 4.4.2.2.2, syslog
Message Format, in the DOCSIS 1.1 Operations Support System Interface (OSSI) Specification
(SP-OSSIv1.1-I06-020830). For more information about all cable-related event messages that can be
generated on the Cisco CMTS router, see the Cisco CMTS Error Message manual.
Examples The following commands configure the Cisco CMTS router so that it can generate a maximum number
of 25 SNMP traps and syslog messages for DOCSIS events over a two-minute period:
Router# configure terminal
Router(config)# cable event throttle-interval 120
Router(config)# cable event throttle-threshold 25
cable fiber-node
To enter cable fiber-node configuration mode to configure a fiber node, use the cable fiber-node
command in global configuration mode. To remove a fiber node configuration, use the no form of this
command.
Syntax Description fiber-node-id Specifies a unique numerical ID for the fiber node. Valid values are 1 to 256.
Usage Guidelines The cable fiber-node command allows the multiple service operator (MSO) or service provider to
configure the CMTS to be more intelligent by making Cisco IOS aware of how the cable plant is wired.
The downstream channels of the cable plant must be accurately configured in the CMTS fiber nodes.
This allows the CMTS to accurately signal the wideband modems on which wideband channels are
available to the modem.
In a cable network, a cable modem is physically connected to only one fiber node. Fiber node software
configuration mirrors the physical topology of the cable network. When configuring fiber nodes with
Cisco IOS CLI commands, a fiber node is a software mechanism to define the following:
• The set of downstream RF channels that will flow into the fiber node
• At least one primary downstream channel
Note In Cisco IOS Releases 12.3(21)BC and 12.3(21a)BC3, this is a traditional DOCSIS
downstream channel for the fiber node. Beginning in Cisco IOS Release 12.3(23)BC, either
an RF channel from the SPA or a Cisco uBR10-MC5X20 downstream channel can serve as
a primary channel in a fiber node.
• The set of upstream channel ports on the cable interface line card that are connected to the fiber node
and available as upstream channels
Use the cable fiber-node command to enter cable fiber-node configuration mode so that you can
configure a fiber node.
For a wideband channel to work correctly, each fiber node must be configured as follows:
1. Use the cable fiber-node command to create the fiber node and to enter cable fiber-node
configuration mode.
2. Use the downstream command to associate the fiber node with one or more primary downstream
channels (traditional DOCSIS downstream channels).
Note Beginning in Cisco IOS Release 12.3(23)BC, if the primary downstream channel for this
fiber node is assigned from a SPA RF downstream channel, then this command is not
required.
3. Use the upstream command to specify the upstream channel ports for a fiber node.
4. Use the downstream modular-cable rf-channel command to make one or more SPA RF channels
available for the fiber node.
5. Optionally, use the description (cable fiber-node) command to specify a description for the fiber
node.
For each fiber node, a traditional DOCSIS downstream channel on the Cisco uBR10-MC5X20 cable
interface line card is used to carry MAC management and signaling messages, and the associated
traditional DOCSIS upstream channel is used for return data traffic and signaling. The traditional
DOCSIS downstream channel used in this way is called the primary downstream channel. Beginning in
Cisco IOS Release 12.3(23)BC, either an RF channel from the SPA or a Cisco uBR10-MC5X20
downstream channel can serve as a primary channel in a fiber node. If the fiber node does not have a
Cisco uBR10-MC5X20 downstream channel, then make sure that at least one of the SPA RF channels
specified in the downstream modular-cable rf-channel command is a primary-capable downstream
channel.
Each wideband channel must be associated with at least one primary downstream channel and can be
associated with multiple primary downstream channels. A wideband channel and its associated primary
downstream channels must be belong to the same virtual bundle interface.
The maximum number of cable fiber nodes that can be configured is limited to 256 for each CMTS.
Examples The following example shows how to enter configuration mode for fiber node 5.
Syntax Description group-id Specifies a unique group ID for this filter group. The valid range is
1 to 254. 255 is reserved for use by the CMTS router.
index-num Specifies a unique index for this particular filter. The valid range is
1 to 128 on a uBR7200 series router and 1 to 255 on a uBR10012
router.
Specify one of the following options and option-values:
dest-ip ip-address (Optional) Specifies the destination IP address that should be
matched. The default IP address is 0.0.0.0. (IPv4 filters only)
dest-mac-addr mac-address (Optional) Specifies the destination MAC address that should be
matched.
dest-mac-mask mask (Optional) Specifies the mask for the destination MAC address that
should be matched.
dest-mask mask (Optional) Specifies the mask for the destination address that should
be matched. The mask is ANDed with the IP address specified by the
dest-ip option and compared to the result of ANding the mask with
the packet’s destination IP address. The filter considers it a match if
the two values are the same. (IPv4 filters only)
Note The default mask of 0.0.0.0 matches all IP addresses.
dest-port port-number (Optional) Specifies the TCP/UDP destination port number that
should be matched. The valid range is 0 to 65535. The default value
matches all TCP/UDP port numbers. (IPv4 and IPv6 filters)
eth-proto-type ethernet (Optional) Specifies the Ethernet protocol type number that should
protocol type be matched. The valid range is 0 to 65536.
eth-protocol ethernet protocol (Optional) Specifies the Ethernet protocol that should be matched.
number The valid range is 0 to 65536.
ip-proto proto-type (Optional) Specifies the IP protocol type number that should be
matched. The valid range is 0 to 256, with a default value of 256 that
matches all protocols. (IPv4 and IPv6 filters)
Some commonly-used values are:
• 1—ICMP, Internet Control Message Protocol.
• 2—IGMP, Internet Group Management Protocol.
• 4—IP in IP encapsulation.
• 6—TCP, Transmission Control Protocol.
• 17—UDP, User Datagram Protocol.
ip-tos tos-mask tos-value (Optional) Specifies a type of service (TOS) mask and value to be
matched (IPv4 and IPv6 filters):
• tos-mask—8-bit value expressed in hexadecimal notation. The
valid range is 0x00 through 0xFF.
• tos-value—8-bit value expressed in hexadecimal notation. The
valid range is 0x00 through 0xFF.
The tos-mask is logically ANDed with the tos-value and compared
to the result of ANDing the tos-mask with the packet’s actual TOS
value. The filter considers it a match if the two values are the same.
Note The default values for both parameters matches all ToS
values.
ip-version (Optional) Specifies the IP version of the filter:
• ipv4—Filter is an IP version 4 filter group (default).
• ipv6—Filter is an IP version 6 filter group.
match-action {accept | drop} (Optional) Specifies the action that should be taken for packets that
match this filter (IPv4 and IPv6 filters):
• accept—Packets that match the filter are accepted (default).
• drop—Packets that match the filter are dropped.
range-dest-port start-port (Optional) Specifies the TCP/UDP destination port start range. The
number end-port number valid range is 0 to 65535.
range-ip-tos mask against TOS (Optional) Specifies IP TOS byte range settings expressed in
start value and end value hexadecimal notation. The valid range is 0x00 through 0xFF.
range-src-port start-port (Optional) Specifies TCP/UDP source port start range. The valid
number end-port number range is 0 to 65535.
range-user-pri low-priority (Optional) Specifies the user priority.The valid range for priority is
value high-priority value 0 to 8. The Priority field indicates the frame priority level from 0
(lowest) to 8 (highest), which prioritizes different classes of traffic
(such as voice, video and data).
src-ip ip-address (Optional) Specifies the source IP address that should be matched.
The default IP address is 0.0.0.0. (IPv4 filters only)
src-mac-addr mac address (Optional) Specifies the source MAC address to be matched.
src-mask mask (Optional) Specifies the mask for the source address that should be
matched. The mask is ANDed with the IP address specified by the
src-ip option and compared to the result of ANding the mask with
the packet’s source IP address. The filter considers it a match if the
two values are the same. (IPv4 filters only)
Note The default mask of 0.0.0.0 matches all IP addresses.
src-port port-number (Optional) Specifies the TCP/UDP source port number that should
be matched. The valid range is 0 to 65535. The default value matches
all TCP/UDP port numbers. (IPv4 and IPv6 filters)
status {active | inactive} (Optional) Enables or disables the filter (IPv4 and IPv6 filters):
• active—Enables the filter immediately (default).
• inactive —Disables the filter immediately.
Note You must create a filter group using at least one of the other
options before you can use this command to enable or
disable the filter.
tcp-flags flags-mask flags-value (Optional) Specifies the TCP flag mask and value to be matched
(IPv4 and IPv6 filters):
• flags-mask—8-bit value expressed in hexadecimal notation. The
valid range is 0x0 through 0x3F.
• flags-value—8-bit value expressed in hexadecimal notation.
The valid range is 0x0 through 0x3F.
v6-dest-address ipv6-address (Optional) Specifies the IPv6 destination address that should be
matched using the format X:X:X:X::X. (IPv6 filters only)
v6-dest-pfxlen prefix-length (Optional) Specifies the length of the network portion of the IPv6
destination address. The valid range is 0 to 128. (IPv6 filters only)
v6-flow-label flow-label value (Optional) Specifies the IPv6 flow label to be used by the source to
label packets of a flow. The range is 0 to 1048575. A flow label of
zero is used to indicate packets not part of any flow.
v6-src-address ipv6-address (Optional) Specifies the IPv6 source address that should be matched
using the format X:X:X:X::X. (IPv6 filters only)
v6-src-pfxlen prefix-length (Optional) Specifies the length of the network portion of the IPv6
source address. The valid range is 0 to 128. (IPv6 filters only)
vlan-id vlan-id (Optional) Specifies the VLAN Identifier to be matched, which is a
12-bit field specfying the VLAN to which the packet belongs.The
valid range is 0 to 4094.
Command Default No filter groups are defined. When a filter group is created, it defaults to accepting all source and
destination IP addresses and TCP/UDP ports, all protocol types, and all ToS and TCP flag values.
Usage Guidelines This command implements DOCSIS 1.1 packet filtering, as defined in the DOCS-SUBMGT-MIB. Each
filter group can contain multiple filters, as defined by the different index numbers.
Note The DOCS-SUBMGT-MIB MIB is supported only on Cisco IOS Release 12.2(8)BC2 and later 12.2 BC
releases. See the description of the docsSubMgtPktFilterTable table in this MIB for further information.
When matching the source or destination addresses, the filter ANDs the mask value with the filter’s
corresponding IP address. The filter then ANDs the mask with the packet’s actual IP address and
compares the two values. If they are the same, the filter matches the packet.
For example, if you specify a src-ip of 192.168.100.0 and a src-mask of 255.255.255.0, the filter
matches all packets that have a source IP address in the range of 192.168.100.0 through
192.168.100.255. Use a mask value of 0.0.0.0 (default) to match all IP addresses. Use a mask value of
255.255.255.255 to match one specific IP address.
Similarly, when comparing TOS values, the filter ANDs the tos-mask parameter with the tos-value
parameter and compares it to the result of ANDing the tos-mask parameter with the packet’s actual TOS
value. If the two values are the same, the filter matches the packet.
Note For the filter group to work for CMs, a CM must re-register after the CMTS router is configured.
Note Since TLVs 35, 36, and 37 do not apply to DOCSIS 1.0 CM configuration files, the only way to enable
cable subscriber management for a DOCSIS 1.0 CM is to configure it explicitly on the CMTS router and
activate it by using the cable submgmt default active global configuration command.
Note When parallel eXpress forwarding (PXF) is configured on the Cisco ubR10012 router, either the
interface ACL (ip access-list command) or the cable filter group commands can be used to filter the
packets.
Consider the following restrictions and guidelines when configuring IPv6 cable filter groups:
• Chained IPv6 headers are not supported.
• If you need to support IPv4 and IPv6 filters for the same filter group, then you must use a separate
index number with the same filter group ID, and configure one index as ip-version ipv4, and the
other index as ip-version ipv6.
Examples The following example shows configuration of an IPv4 filter group that drops packets with a source IP
address of 10.7.7.7 and a destination IP address of 10.8.8.8, and a source port number of 2000 and a
destination port number of 3000. All protocol types and ToS and TCP flag values are matched:
configure terminal
cable filter group 10 index 10 src-ip 10.7.7.7
cable filter group 10 index 10 src-mask 255.255.0.0
cable filter group 10 index 10 dest-ip 10.8.8.8
cable filter group 10 index 10 dest-mask 255.255.0.0
cable filter group 10 index 10 ip-proto 256
cable filter group 10 index 10 src-port 2000
cable filter group 10 index 10 dest-port 3000
cable filter group 10 index 10 tcp-flags 0 0
cable filter group 10 index 10 match-action drop
IPv6 Example
The following example shows the configuration of an IPv6 filter group that drops traffic from a specific
IPv6 host (with source address 2001:33::20B:BFFF:FEA9:741F/128) behind a cable router to an IPv6
host on the network (with destination address 2001:1::224/128):
configure terminal
!
! Specify the filter group criteria using ID 254
!
cable filter group 254 index 128 v6-src-address 2001:33::20B:BFFF:FEA9:741F
cable filter group 254 index 128 v6-src-pfxlen 128
cable filter group 254 index 128 v6-dest-address 2001:1::224
cable filter group 254 index 128 v6-dest-pfxlen 128
!
! Specify that the filter group is IPv6
!
cable filter group 254 index 128 ip-version IPv6
!
! Specify the drop action for matching packets
!
cable filter group 254 index 128 match-action drop
!
! Apply the filter group with ID 254 to all CM upstream traffic
!
cable submgmt default filter-group cm upstream 254
Syntax Description minutes Specifies how long, in minutes, that a CM remains in the flap list. The valid range is 1 to
86400, with a default of 10080 minutes.
Command Default The default length of time that a CM is kept in the flap-list table is 10080 minutes (1 week).
Usage Guidelines Flapping refers to the rapid disconnecting and reconnecting of a CM that is having problems holding its
connection to the CMTS. A flap list is a table maintained by the Cisco CMTS for every modem (active
or not) that is having communication difficulties. The flap list contains modem MAC addresses and logs
the time of the most recent activity. You can configure the size and entry thresholds for the flap list.
Examples The following example shows how to specify that the flap-list table retain 2400 minutes (40 hours) of
performance for this CM:
Router(config)# cable flap-list aging 2400
Command Description
cable flap-list size Specifies the maximum number of CMs that can be listed in
the flap-list table.
clear cable flap-list Clears all the entries in the flap-list table.
debug cable flap Displays information about the operation of the CM flap list
that is maintained for the cable interfaces.
ping docsis Sends a DOCSIS ping to a CM and increments the flap-list
counters as appropriate.
show cable flap-list Displays the current contents of the flap list.
Syntax Description seconds Insertion time interval in seconds. Valid values are from 60 to 86,400 seconds. The default
value is 180 seconds (3 minutes).
Command Default The default insertion time interval is 180 seconds (3 minutes).
Usage Guidelines This command controls the operation of a flapping modem detector. When a CM makes two or more
initial Ranging Requests (also known as insertion or reinsertion requests) within the period of time
defined by this command, the CM is placed in the flap list. A CM is not put into the flap list if the time
between its two consecutive initial Ranging Requests is greater than the insertion time interval.
For example, if the CMTS is configured for the default insertion time of three minutes, and if the CM
reinserts itself four minutes after its last insertion, the CM is not placed in the flap list. However, if the
CM reinserts itself two minutes after its last insertion, the CM is placed in the flap list.
Also, a CM is put into the flap list only once for each insertion time interval, even if the CM reinserts
itself multiple times. For example, if the CMTS is set for the default insertion time interval of 3 minutes,
and the CM reinserts itself three times within that period, the flap list will show that the CM has flapped
once. If the CM reinserts itself three times within the first 3 minute period and three more times within
the next 3 minute period, the flap list will show that the CM has flapped twice.
Examples The following example shows how to set the insertion time interval to 62 seconds:
Router(config)# cable flap-list insertion-time 62
Syntax Description misses Specifies the number of consecutive MAC-layer keepalive (Station Maintenance) that can be
missed before a CM is placed in the flap list. The valid range is 1 to 12, with a default of 6.
Command Default The default number of station maintenance messages that can be missed is 6.
Usage Guidelines In a DOCSIS network, the CMTS regularly sends out MAC-layer keepalive messages, known as station
maintenance messages, to each CM that is online. If a CM does not respond to a station maintenance
message, the CMTS repeats sending these messages either until the CM responds or the CMTS reaches
the maximum allowable number of messages that can be sent.
The cable flap-list miss-threshold command specifies how many consecutive station maintenance
messages can be missed before the cable modem is placed in the flap list. A miss occurs when a CM does
not reply to a station maintenance message.
Note Station maintenance messages are occasionally lost due to noise or congestion in a typical DOCSIS
network, with a loss rate of approximately 8 percent considered nominal. A higher miss rate can indicate
RF plant problems, such as intermittent upstream problems, fiber laser clipping, or common-path
distortion.
Examples The following example shows how to set the miss threshold to 5:
Router(config)# cable flap-list miss-threshold 5
Syntax Description dB Specifies the minimum power adjustment, in decibels, that results in a flap-list event. Valid values
are from 1 to 10 dB.
Usage Guidelines This command controls the operation of a flapping modem detector. When the power adjustment of a
CM exceeds the configured threshold value, the modem is placed in the flap list.
Note A power adjustment threshold of less than 2 dB might cause excessive flap-list event recording. Cisco
recommends setting this threshold value to 3 dB or higher.
Note For underground HFC networks with 4 amplifier cascade length, a typical threshold value should be 3
dB. For overhead HFC networks with 4 amplifier cascade length, a typical threshold value should be 4
dB. Longer coaxial cascades without return path thermal gain control and sites with extreme daily
temperatures will have larger threshold ranges.
Examples The following example shows the power-adjust threshold being set to 5 dB:
Router(config)# cable flap-list power-adjust threshold 5
Syntax Description number Maximum number of CMs to be displayed. Valid values are from 1 to
8191 depending on the type of line cards, with a default of 100 CMs.
Usage Guidelines • The flap-list size is determined by the architecture of the CMTS and the cable line cards. Previously,
the cable flap-list tables were stored on the Route Processors and Performance Routing Engine
(PRE) modules.
• The legacy non-distributed cable line cards, Cisco uBR-MC16C/MC16E/MC16S line card and
Cisco uBR-MC28C/MC28E line card did not store the flap-list tables in the line cards.
• The distributed line cards are designed such that they store the flap-list tables on the line cards. For
a CMTS using distributed line cards, the flap-list size is the maximum size per line card.
• The distributed line cards supported on a Cisco uBR7200 router are Cisco uBR-MC28U/X and Cisco
uBR-16U/16X.
• The distributed line cards supported on a Cisco uBR10012 router are Cisco uBR10-MC5X20S/U/H.
• You can calculate the flap list sizes using the following formulas:
– For a Cisco uBR10012 router without line card high availability (LC-HA)—8191 * (Number of
cable line cards)
– For a Cisco uBR10012 router with line card high availability (LC-HA)—8191 * (Number of
cable line cards - 1)
– For a Cisco uBR72VXR router using legacy and distributed line cards—8191 * (1 + Number of
distributed cable line cards)
• The flap-list tables sizes are as follows:
– A fully loaded Cisco uBR10012 router
With distributed line cards and no LC-HA configured—8191 * 8 = 65528 CMs.
With distributed line cards and LC-HA configured—8191 * (8-1) = 57337 CMs.
Note Legacy line cards behave as the distributed line cards on a Cisco uBR10012 router. Thus, the
flap-list sizes are same as for distributed line cards.
Examples The following example shows how to display a maximum of 200 flap-list entries:
Router#configure terminal
Router(config)#cable flap-list size 200
Router(config)#
cable freq-range
To configure the Cisco CMTS router for the range of frequencies that are acceptable on upstreams, use
the cable freq-range command in global configuration mode. To restore the default value (which is
based on the cable interface and on the Annex A/B configuration), use the no form of this command.
no cable freq-range
Syntax Description european Configures the Cisco CMTS router to accept upstream frequency ranges that
conform with the EuroDOCSIS specifications (5 MHz to 65 MHz).
japanese Configures the Cisco CMTS router to accept upstream frequency ranges that
conform to the extended range used in Japan (5 MHz to 55 MHz).
north-american Configures the Cisco CMTS router to accept upstream frequency ranges that
conform to the DOCSIS specifications (5 MHz to 42 MHz).
Command Default no cable freq-range, which defaults to a frequency range based on the Annex configuration:
• Annex A = european (EuroDOCSIS, 5 MHz to 65 MHz)—Supported only on cable interfaces that
support EuroDOCSIS
• Annex B = north-american (DOCSIS, 5 MHz to 55 MHz)—All cable interfaces support the 5 MHz
to 42 MHz range. The 42 MHz to 55 MHz range is supported only on certain cable interfaces.
Usage Guidelines In Cisco IOS Release 12.2(15)BC2 and later, the Cisco CMTS router supports three different modes of
operation, depending on the cable interface line cards being used. The range of frequencies that are
allowed in each mode are as follows:
• North American DOCSIS (Annex B)—Upstreams use frequencies between 5 MHz and 42 MHz.
This range is supported by all cable interface line cards.
• European EuroDOCSIS (Annex A)—Upstreams use frequencies between 5 MHz and 65 MHz.
• Japanese Extended Range (Annex B)—Upstreams use frequencies between 5 MHz and 55 MHz.
To configure the router so that it supports the proper range of upstream frequencies, use the upstream
freq-range command. After you have configured the router with the cable freq-range command, the
cable upstream frequency and cable spectrum-group (interface configuration) commands then
accept only frequencies that are in the configured range.
Typically, the upstream freq-range command is not needed because the default behavior covers the
most common configurations. However, this command can be used in the following situations:
• This command is required to enable EuroDOCSIS operations on the Cisco uBR-MC16U/X and
Cisco uBR-MC28U/X cards.
• This command is never needed for the Cisco uBR-MC5X20U card nor for EuroDOCSIS cable
interfaces (Cisco uBR-MC16E card, and the Cisco uBR7111E and Cisco uBR7114E routers),
because these interfaces default to the EuroDOCSIS range of frequencies. However, if you have
previously used this command to restrict the allowable range of frequencies, you must use the
european option to re-enable the EuroDOCSIS range of frequencies.
• The north-american option is usually not needed, because this is the default mode of operations for
all DOCSIS cable interfaces. However, this option can be useful on the Cisco uBR-MC16U/X and
Cisco uBR-MC28U/X cards when noise exists on the frequencies above 42 MHz. In this situation,
using the north-american option filters out the higher frequencies and reduces the impact of that
noise.
• Similarly, the japanese option is not needed on those cable interface cards that support it, because
this is the default configuration on those cards. However, if you have previously used the
north-american option on an interface, you need to use the japanese option to re-enable the
extended frequency range.
• Even when the upstream freq-range command is not needed to enable a frequency range, using it
ensures that the cable upstream frequency and cable spectrum-group commands allow only
frequencies that are within the desired range. This can help operators from assigning invalid
frequencies to upstreams.
Tip If one or more cable interface line cards that are installed in the chassis do not support the frequency
range that you select with this command, the command displays an informational warning message for
each of those cable interface cards. Also, you cannot configure the router for a particular frequency range
if an upstream or spectrum group on the router is currently configured for a frequency that is invalid for
the new range. If you try to do so, the command is ignored and a warning message is printed prompting
you to reconfigure the upstream or spectrum group before retrying the command.
Note This command configures only the range of frequencies that can be configured on an upstream. It does
not configure the upstreams for the DOCSIS (Annex B) or EuroDOCSIS (Annex A) modes of operation,
which is done using the cable downstream annex interface command. (Annex C mode is not supported.)
You must configure the downstream for Annex A for EuroDOCSIS operations and Annex B for DOCSIS
operations. You can configure certain cable interface cards (such as the Cisco uBR-MC28U) for both the
DOCSIS Annex B mode and the EuroDOCSIS frequency range, but this violates the DOCSIS
specifications and should not be used on standard DOCSIS networks.
The allowable range for the upstream channel frequency depends on the cable interface line card and
Cisco IOS software release being used. See Table 4 for the currently supported values.
Note The cable freq-range command fails if any upstreams or spectrum groups on the router are currently
configured for a frequency that is outside the new range being selected. You must reconfigure those
upstreams or spectrum groups, using the cable upstream frequency or cable spectrum-group
commands, for lower frequencies, and then repeat the cable freq-range command.
Examples The following example shows how to configure the Cisco CMTS router to support the EuroDOCSIS
upstream frequency range of 5 MHz to 65 MHz. The router then displays a list of the cable interface line
cards, if any, that do not support this range. After giving this command, the cable upstream frequency
command shows the valid range of upstream frequencies as being the EuroDOCSIS range:
Router# configure terminal
Router(config)# cable freq-range european
Router(config-if)#
The following example shows how to configure the Cisco CMTS router to support the extended Japanese
upstream frequency range of 5 MHz to 55 MHz. The router then displays a list of the cable interface line
cards, if any, that do not support this range. After giving this command, the cable upstream frequency
command shows the valid range of upstream frequencies as being the extended frequency range for
Japanese networks:
Router# configure terminal
Router(config)# cable freq-range japanese
Router(config)# interface cable 6/0 ! This cable interface supports the Japanese range
Router(config-if)# cable upstream 0 frequency ?
The following example shows how to configure the Cisco CMTS router for its default configuration
(DOCSIS upstream frequency range of 5 MHz to 42 MHz). (No warning messages are displayed with
this configuration because all cable interface line cards support the basic DOCSIS frequency range.)
After giving this command, the cable upstream frequency command shows the valid range of upstream
frequencies as being the DOCSIS range:
Router# configure terminal
Router(config)# cable freq-range north-american
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 frequency ?
The following example shows all of the commands that are needed to configure the cable interface and
upstream on a Cisco uBR-MC28U/X cable interface line card to support a frequency in the EuroDOCSIS
upstream frequency range of 5 MHz to 65 MHz:
Router# configure terminal
Router(config)# cable freq-range european
Router(config)# interface 3/0
Router(config-if)# cable downstream annex a
Router(config-if)# cable upstream 0 frequency 62500000
The following example shows the cable freq-range command failing because an upstream is configured
for a frequency that is invalid for the new range. The upstream must be reconfigured before the cable
freq-range command can be given successfully.
Router# configure terminal
Router(config)# cable freq-range japanese
%%Interface Cable 3/0/U0 has invalid frequency (62500000 Hz) for specified range
%%Set upstream frequencies within range prior to changing freq-range
cable helper-address
To specify a destination IP address for User Datagram Protocol (UDP) broadcast Dynamic Host
Configuration Protocol (DHCP) packets, use the cable helper-address command in cable interface or
subinterface configuration mode. To disable this feature, use the no form of this command.
Syntax Description IP-address The IP address of a DHCP server to which UDP broadcast packets will
be sent.
cable-modem (Optional) Specifies that only CM UDP broadcasts are forwarded.
host (Optional) Specifies that only host UDP broadcasts are forwarded.
mta (Optional) Specifies that only media terminal adapter (MTA) UDP
broadcasts are forwarded.
stb (Optional) Specifies that only set-top box (STB) UDP broadcasts are
forwarded.
Defaults If no options are specified, both CM and host UDP broadcasts are forwarded.
Usage Guidelines This command enables CMs and their attached CPE devices (hosts) to use separate DHCP servers, so
that CMs and hosts receive their IP addresses from separate address pools. The cable-modem keyword
specifies that only UDP DHCP broadcasts from CMs are forwarded to that particular destination IP
address. The host keyword specifies that only UDP broadcasts from hosts (CPE devices) are forwarded
to that particular destination IP address.
Note You must specify both the cable-modem or host options in separate commands, using separate IP
addresses, if you decide to use them. If you specify only one option, then the other type of device (cable
modem or host) will not be able to connect with a DHCP server. In addition, if you use the cable-modem
or host option with the same IP address that was previously configured with this command, the new
configuration overwrites the old configuration.
The cable helper-address command is similar to the ip helper-address command, but the cable
helper-address command has been enhanced for cable interfaces and DOCSIS networks to allow
separate helper addresses for CMs and hosts. Use only the cable helper-address command on cable
interfaces, and use the ip helper-address command on all non-cable interfaces.
The cable helper-address command, as is the case with the ip helper-address command, cannot be used
on slave interfaces, so these commands are automatically removed from an interface configuration when
the interface is configured as a slave interface. Slave interfaces use the IP configuration of the master
interface, which includes not only the IP address for the interface itself, but also the helper addresses
that have been configured on the master interface.
Tip You can repeat this command to specify any number of helper addresses, but the Cisco IOS software uses
only the first 16 valid addresses that are configured on each interface (using either the cable
helper-address command or the ip helper-address command) when forwarding DHCP requests.
Examples The following example shows how to forward UDP broadcasts from both CMs and CPE devices to the
DHCP server at 172.23.66.44:
Router(config)# interface cable 1/0
Router(config-if)# cable helper-address 172.23.66.44
Router(config-if)# exit
Router(config)#
The following example shows how to forward UDP broadcasts from CMs and CPE devices to separate
DHCP servers:
Router(config)# interface cable 6/0
Router(config-if)# cable helper-address 172.23.66.143 host
Router(config-if)# cable helper-address 172.23.66.144 cable-modem
Router(config-if)# exit
Router(config)#
The following example shows that when you specify the cable-modem and host options with the same
IP address, the second command overwrites the first one:
Router(config)# interface cable 3/0
Router(config-if)# cable helper-address 10.10.10.13 host
Router(config-if)# cable helper-address 10.10.10.13 cable-modem
Router(config-if)# exit
Router(config)# exit
Router# show running-config | include helper-address
Router#
Command Description
cable source-verify Turns on CM upstream verification.
cable telco-return spd Enforces the telco-return CM to use a specific Dynamic Host
dhcp-authenticate Configuration Protocol (DHCP) server.
cable telco-return spd Identifies the IP address of the Dynamic Host Configuration Protocol
dhcp-server (DHCP) server that the telco-return CM must access.
ip dhcp relay information Enables the system to insert the CM MAC address into a DHCP
option packet received from a CM or host and forward the packet to a DHCP
server.
ip dhcp smart-relay Monitors client retransmissions when address pool depletion occurs.
Usage Guidelines For the virtual route forwarding (VRF) syntax of this command, only the IP address option is supported.
Note The cable host command, and its SNMP equivalent, cdxCmCpeAccessGroup, are not supported on the
Cisco uBR10012 universal broadband router. On this router, use the standard DOCSIS MIB,
DOCS-SUBMGT-MIB, instead.
Examples The following example shows how to assign access list number 2 to the cable host with an IP address of
10.1.1.1:
Router# cable host 10.1.1.1 access-group 2
cable high-priority-call-window
To set the call window (in minutes) during which the Cisco CMTS router maintains records of
Emergency 911 calls, use the cable high-priority-call-window command in global configuration mode.
To remove the call window configuration from the Cisco CMTS router, use the no form of this command:
no cable high-priority-call-window
Syntax Description window This value defines the length of time, in minutes, for which E911 Call History is to be
maintained.
Command Default This command and the PacketCable Emergency 911 Services Listing and History feature is disabled by
default on the Cisco CMTS.
Usage Guidelines The following command example configures the call window on the Cisco uBR10012 router to be 1
minute in length:
Router(config)# cable high-priority-call-window 1
To observe Emergency 911 calls made within the configured window, use the show cable calls command
in privileged EXEC mode:
The following command example illustrates that one Emergency 911 call was made on the Cable8/1/1
interface on the Cisco uBR10012 router during the window set for high priority calls:
Router# show cable calls
Interface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMs
Cable5/0/0 0 0 0 0
Cable5/0/1 0 0 0 0
Cable5/1/0 0 0 0 0
Cable5/1/1 0 0 0 0
Cable5/1/2 0 0 0 0
Cable5/1/3 0 0 0 0
Cable5/1/4 0 0 0 0
Cable6/0/0 0 0 0 0
Cable6/0/1 0 0 0 0
Cable7/0/0 0 0 0 0
Cable7/0/1 0 0 0 0
Cable8/1/0 0 0 0 0
Cable8/1/1 1 1 0 0
Cable8/1/2 0 0 0 0
Cable8/1/3 0 0 0 0
Cable8/1/4 0 0 0 0
Total 1 1 0 0
Command Default Cable per-physical-downstream static multicast support is not defined by default.
Usage Guidelines The Cable per-physical-downstream Static Multicast Support feature introduces the concept of a
physical IGMP static group, which is an extension of the existing logical IGMP static group. The
differences between the two IGMP static groups are:
• A cable bundle logical IGMP static group creates the IGMP static group for the logical IP domain
and forwards multicast traffics for the configured multicast group to every slave interface in the
same bundle.
• A cable bundle physical IGMP static group creates the IGMP static group on per-physical slave
interface basis and will only forwards multicast traffics to only configured slave interfaces.
When an IGMP static group is configured on a master interface, the IGMP static group will perform a
check for each slave interface in the multicast group. If the multicast group is configured as a physical
static group, then only the corresponding slave interfaces will be added to the cable bundle forwarding
table. If the multicast group is configured as a logical static group, then all slave interfaces will be added
to the cable bundle forwarding table.
Note When all remaining physical static groups are un-configured from the slave interface for a particular
multicast group on a particular bundle, the Cisco CMTS router will revert back to the logical static group
for that multicast group on that bundle.
DSG Usage
The cable igmp static-group command will only appear in the output of the show
running-configuration command if it is configured via the CLI. If it is configured by DSG, the cable
igmp static-group command CLI will remain hidden for a particular multicast group. This is done in
order to eliminate any confusion with the current DSG configurations.
Note Any multicast group being used by DSG (or CLI) within the same CMTS, should not be used for CLI
(or DSG) configuration.
Examples The following example shows the cable igmp static-group command on the Cisco CMTS router:
Router(config-if)# cable igmp static-group 230.1.1.1
The following example shows the cable igmp static-group command with the source option on the
Cisco CMTS router:
Router(config-if)# cable igmp static-group 232.1.1.1 source 10.1.1.1
cable init-channel-timeout
To specify the maximum time that a CM can spend performing initial ranging on the upstream channels
described in the Registration Response (REG-RSP) and Multipart Registration Response
(REG-RSP-MP) messages, use the cable init-channel-timeout command in cable interface
configuration mode. To disable this configuration, use the no form of this command.
Syntax Description value Channel timeout value in seconds. Valid range is from 10 to 180 seconds.
The default value is 60.
Examples The following example shows how to specify the channel timeout value on a cable interface at
slot/subslot/port 5/1/0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable init-channel-timeout 90
cable insertion-interval
To configure the interval between consecutive initial ranging slots on an upstream, use the cable
insertion-interval interface configuration command. To configure the automatic setting and ignore any
minimum or maximum time settings, use the no form of this command.
no cable insertion-interval
Syntax Description fixed-intrvl Fixed interval between initial ranging slots in milliseconds. The valid range is 100 to
2000 milliseconds.
automatic Causes the Cisco CMTS MAC scheduler for each upstream CM to vary the initial
ranging times available to new CMs joining the network.
min-intrvl (Optional) Minimum value in milliseconds between the initial ranging slots on the
upstream. The valid range is 20 to 120, with a default of 60 milliseconds.
max-intrvl (Optional) Maximum value in milliseconds between the initial ranging slots on the
upstream. The valid range is 240 to 1800, with a default of 480 milliseconds.
Command Default Automatic (dynamically varying the frequency of initial ranging upstream slots between 60 milliseconds
and 480 milliseconds)
Usage Guidelines Use this command to specify the minimum and maximum duration between initial ranging opportunities
that appear in MAP messages sent by the Cisco CMTS router. MAP messages define the precise time
intervals during which CMs can send.
The default insertion interval setting (automatic) configures the Cisco CMTS router to optimize the initial
ranging times available to new CMs that attempt to join the network. The optimization algorithm
automatically varies the initial ranging times between 60 and 480 milliseconds, depending on the number of
CMs attempting to come online.
Use the cable insertion-interval automatic command to bring a large number of CMs online quickly
(for example, after a major power failure). After the CMs have come online, you can override the
automatic keyword by giving this command again and specifying a specific insertion interval.
Examples The following example shows the default configuration, which is to specify automatic insertion
intervals, using the default initial ranging intervals:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable insertion-interval automatic
The following example shows how to set the minimum insertion interval to 100 ms:
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable insertion-interval 100
cable intercept
To allow the Cisco CMTS router to forward all traffic to and from a particular CM to a data collector located
at particular User Datagram Protocol (UDP) port, use the cable intercept command in cable interface
configuration mode. To deactivate this function, use the no form of this command.
Usage Guidelines When this command is activated, the Cisco CMTS router examines each packet for the desired MAC
address; when a matching MAC address is found (for either the origination or destination endpoint), a
copy of the packet is encapsulated into a UDP packet, which is then sent to the specified server at the
given IP address and port.
Note The data collecting system at the ip-address on the udp-port must be configured to listen for and capture
the necessary data stream. An IP route to the specified IP address must exist, and IP connectivity to that
device must be present for the traffic to be captured. Before Cisco IOS Release 12.1(11b)EC, the data
collecting system must be within two routing hops of the Cisco CMTS.
This command can be used to comply with the United States Federal Communications Assistance for
Law Enforcement Act (CALEA) and other law enforcement wiretap requirements for voice
communications. For additional information, see the PacketCable Electronic Surveillance Specification,
which is available at the following URL at the PacketCable web site:
http://www.packetcable.com
Examples The following commands specify that a copy of all traffic for the CM with the MAC address of
0080.fcaa.aabb should be forwarded to the data collector that is listening at UDP port 512 at the IP
address of 10.12.13.8. The show interface cable intercept command displays which intercepts are
currently active.
Router# configure terminal
Router#(config) interface c6/0
router(config-if)# cable intercept 0080.fcaa.aabb 10.12.13.8 512
router(config-if)# exit
router(config)# exit
router# show interface c6/0 intercept
Destination Destination
MAC Address IP Address UDP Port
0080.fcaa.aabb 3.12.13.8 512
cable ip-init
To configure the IP provisioning mode supported by the cable interface on a Cisco CMTS router, use the
cable ip-init command in interface or subinterface configuration mode. To remove the IP provisioning
configuration, use the no form of this command.
Syntax Description dual-stack Configures the interface to support both IPv4 and IPv6 addressing.
ipv4 Configures the interface to support IPv4 address only.
ipv6 Configures the inerface to support IPv6 address only.
Usage Guidelines The cable ip-init command configures the cable interface for the IP addressing mode that it supports.
This information is included in the IP initialization parameters of the MAC Domain Descriptor (MDD)
message.
Examples The following example shows how to configure a cable interface on a Cisco CMTS router to support both
IPv4 and IPv6 addressing:
interface cable 5/0/1
cable ip-init dual-stack
cable ip-broadcast-echo
To activate upstream IP broadcast echo so that the Cisco CMTS router can echo broadcast packets, use
the cable ip-broadcast-echo command in cable interface or subinterface configuration mode. To disable
the upstream IP broadcast echo, use the no form of this command.
cable ip-broadcast-echo
no cable ip-broadcast-echo
Usage Guidelines By default, broadcast IP packets that arrive on the upstream at the Cisco CMTS router are not forwarded
on the downstream ports so that they would be delivered to the other CMs and CPE devices. This
behavior prevents broadcast storms in which such packets are repeatedly looped through the network.
The cable ip-broadcast-echo command changes this behavior by forwarding such packets on the
appropriate downstream ports, so that the packet is received by all CMs and CPE devices on that segment
of the network. This allows the cable network to behave more like a standard Ethernet network, and
support direct peer-to-peer communications using IP broadcasts.
Note This command should not be used in a typical service provider network.
Examples The following example shows how to activate IP broadcast echo in the cable interface configuration
mode:
Router(config-if)# cable ip-broadcast-echo
The following example shows how to activate IP broadcast echo in the cable subinterface configuration
mode:
Router(config)# interface cable 6/0.1
Router(config-subif)# cable ip-broadcast-echo
cable ip-multicast-echo
To enable IP multicast echo so that the Cisco CMTS can echo multicast packets, use the cable
ip-multicast-echo command in cable interface or subinterface configuration mode. To disable IP
multicast echo, use the no form of this command.
cable ip-multicast-echo
no cable ip-multicast-echo
Usage Guidelines By default, multicast IP packets that arrive on the upstream at the Cisco CMTS are forwarded on the
appropriate downstream ports so that they are delivered to the other CMs and CPE devices on that
segment of the network. This allows the cable network to behave like a standard Ethernet network in
terms of its handling of multicast IP traffic.
This behavior might not be appropriate for certain applications or networks, so the no cable
ip-multicast-echo command changes this behavior by preventing the forwarding of multicast packets.
Disabling multicast traffic can prevent some types of broadcast storms in which such packets are
repeatedly looped through the network.
To verify if IP multicast echo has been activated or deactivated, enter the show running-config
command and look for the cable interface configuration information.
If IP multicast echo is enabled (the default configuration), it appears in this output.
If IP multicast echo is disabled, it is not displayed in the output configuration.
If you are having trouble, make sure that you have entered the correct slot and port numbers when you
entered cable interface configuration mode.
Note On the Cisco uBR10012 router, input access lists are not applied to the multicast traffic that is echoed
on each downstream. To control the echoed multicast traffic, you therefore need to configure an output
access list and apply it to each downstream interface.
Examples The following example shows how to disable IP multicast echo in the cable interface configuration
mode:
Router(config-if)# no cable ip-multicast-echo
The following example shows how to enable IP multicast echo in the cable subinterface configuration
mode:
Router(config)# interface cable 6/0.1
Router(config-subif)# cable ip-multicast-echo
cable ipc-stats
To enable the Cable IPC Statistics Collection tool on a Cisco CMTS router, use the cable ipc-stats
command in global configuration mode. To disable this configuration, use the no form of this command.
cable ipc-stats
no cable ipc-stats
Command Default The Cable IPC Statistics Collection tool is not enabled by default.
Usage Guidelines The Cable IPC Statistics Collection tool provides debugging information about all IPC messages. We
recommend that you enable this tool only when it is necessary as the tool consumes considerable amount
of CPU memory while running on a Cisco CMTS router.
The cable ipc-stats command is synchronized on all cable interface line cards from the active RP. You
do not have to use this command on cable interface line cards separately.
Examples The following example shows how to enable the Cable IPC Statistics Collection tool on a Cisco CMTS
router:
Router# configure terminal
Router(config)# cable ipc-stats
Usage Guidelines Typically the IPv6 source verification feature is enabled on a cable bundle interface. From there, the
cable interface or subinterface is associated with the virtual bundle interface to acquire its configuration.
When you enable IPv6 source verification on a cable line card interface or subinterface, the source
verification routine is run to verify the MAC-SID-IP binding of the packet. If the source verification
succeeds, the packet is forwarded. If the verification fails, then the packet is dropped.
When a CM is operating as a bridge modem device, then the CMTS router verifies the entire IPv6
address for that CM and the CPEs behind that CM.
When a CM is operating as a router modem device, then the CMTS router only verifies the network
prefix for that CM and the CPEs behind that CM. To be successful, this means that all cable modem
routers mut have different prefixes assigned to them.
The cable ipv6 source-verify command only controls the source verification of IPv6 packets. For
IPv4-based source verification, you must use the cable source-verify command, which also supports
different options.
Note On the Cisco uBR10012 router in Cisco IOS Release 12.2(33)SCA, source verification of IPv6 packets
occurs only on packets in the process-switched path of the route processor (RP).
Examples The following example shows how to enable IPv6 source verification on a Cisco CMTS router cable
interface by first configuring cable ipv6 source-verify at the bundle interface:
interface bundle 1
cable ipv6 source-verify
After you configure the bundle interface, you associate the bundle at the cable interface:
New Commands
Modified Commands
Replaced Commands
cable l2vpn
To enable the Ethernet Layer 2 Virtual Private Network (L2VPN) service and enter L2VPN configuration
mode, use the cable l2vpn command in global configuration mode. To disable this configuration, use the
no form of this command.
Examples The following example shows how to enable the Ethernet L2VPN service and enter L2VPN
configuration mode on the Cisco uBR10012 router:
Router# configure terminal
Router(config)# cable l2vpn 0000.396e.6a68 customer1
Router(config-l2vpn)#
Command Default The use of Layer 2 tunneling for ATM PVC mapping is disabled.
Usage Guidelines This command enables the use of Layer 2 tunnels on all cable and ATM interfaces in the router—which
in turn allows you to map cable modems, on the basis of their hardware (MAC) addresses, to particular
PVCs on an ATM interface—using the cable vc-map command.
Examples The following example shows how to enable the use of Layer 2 tunnels on a router so that cable modems
can be mapped to particular PVCs on an ATM interface:
Router# config terminal
Router(config)# cable l2-vpn-service atm-vc
To configure an Ethernet Network System Interface for Layer 2 VPN support over cable, use the cable
l2-vpn-service default-nsi command in global configuration mode. To remove the interface, use the no
form of this command.
Syntax Description type Interface type. See the Usage Guidelines section for supported types.
number Interface or subinterface number. For more information about the numbering
syntax for your networking device, use the question mark (?) online help
function.
Usage Guidelines The Cisco CMTS routers only support the configuration of a single L2VPN NSI per CMTS.
This command supports the following interface types:
• Cisco uBR100012 Universal Broadband Router—Gigabit Ethernet.
• Cisco uBR7246VXR Universal Broadband Router—Fast Ethernet or Gigabit Ethernet
Examples The following example configures the Gigabit Ethernet line card located in slot 4/0/0 as an NSI for
L2VPN using global configuration mode:
cable l2-vpn-service default-nsi GigabitEthernet4/0/0
Related Commands
Command Description
show cable l2-vpn Displays the mapping of one or all cable modems to IEEE 802.1Q VLANs
dot1q-vc-map on the router’s Ethernet interfaces.
Usage Guidelines This command enables the use of Layer 2 tunnels, using IEEE 802.1Q VLAN tagging, on all cable
interfaces in the router. This in turn allows you to map traffic to and from cable modems, on the basis of
the modems’ hardware (MAC) addresses, to a particular VLAN on a particular WAN interface, using the
cable dot1q-vc-map command.
Examples The following example shows how to enable the use of IEEE 802.1Q Layer 2 tunnels on a router so that
cable modems can be mapped to particular VLAN:
Router# config terminal
Router(config)# cable l2-vpn-service dot1q
Router(config)#
The following example shows how to disable the use of IEEE 802.1Q Layer 2 tunnels on a router. All
mapping of cable modems to IEEE 802.1Q VLANs is halted (but any other Layer 2 mapping, such as
the mapping of cable modems to ATM PVCs, is unaffected).
Router# config terminal
Router(config)# no cable l2-vpn-service dot1q
Router(config)#
Syntax
Description nsi Specifies the network side interface (NSI).
dot1q Specifies the usage of DOT1Q tunneling on the NSI for Ethernet L2VPN
traffic.
mpls Specifies the usage of MPLS tunneling on the NSI for Ethernet L2VPN
traffic.
Usage Guidelines You must enable MPLS tunnel traffic on the network side interface using the cable l2-vpn-service
xconnect command before provisioning MPLS pseudowires.
Examples The following example shows how to enable the use of Layer 2 tunnels based on an AToM pseudowire
on the Cisco uBR10012 router:
Router# configure terminal
Router(config)# cable l2-vpn-service xconnect nsi mpls
Note The default values that are set using the command apply to DOCSIS 3.0 GLBGs created thereafter.
Parameters for existing DOCSIS 3.0 GLBGs do not change.
Syntax Description disable Disables the default values of the DOCSIS 3.0 GLBG that are enabled by
default.
init-tech-list tech-list Sets the default DOCSIS 3.0 GLBG DCC and DBC initialization techniques.
docsis-policy 0-0xffffffff Sets the default DOCSIS 3.0 GLBG load balancing policy.
Usage Guidelines The group parameters in the cable load-balance d30-ggrp-default command can be set as default
values.
Examples The following is a sample output of the cable load-balance d30-ggrp-default command.
Router(config)# cable load-balance d30-ggrp-default
Router(config)# cable load-balance d30-ggrp-default disable
Router(config)# cable load-balance d30-ggrp-default docsis-policy 2
Router(config)# cable load-balance d30-ggrp-default init-tech-list 1
Router(config)#
Examples The following example shows how to enable DOCSIS load balancing on the CMTS using the cable
load-balance docsis-enable command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-enable
Config: Last Batch 0, 38 bytes
cable load-balance docsis-enable
end
Router(config)#
Syntax Description docsis-group-id DOCSIS load balance group ID. A valid DOCSIS load balance group ID
ranges from 1 to 2147483647 and does not overlap with the legacy LBG ID.
Therefore, both cable load-balance group 1 and cable load-balance
docsis-group 1 commands can be configured. The DOCSIS load balance
group ID ranging from 2147483648 to 2^32-1 is reserved for DOCSIS 3.0
general load balancing group (GLBG).
FN fn-id Specifies the fiber node (FN) where certain DOCSIS 3.0 GLBG parameters,
such as disable, docsis-policy, init-tech-list, interval, method, policy, and
threshold, can be configured.
MD cable Specifies the MAC domain interface of the fiber node.
slot/subslot/port
• slot—Slot where the line card resides. The permitted range is from 5 to
8.
• subslot—Subslot where the line card resides. The available slots are 0 or
1.
• port—The downstream controller number on the line card. The
permitted port range is from 0 to 4.
MD cable slot/port Specifies the MAC domain interface of the fiber node on the
Cisco uBR7246VXR or Cisco uBR7225VXR router.
• slot—Slot where the line card resides.
– Cisco uBR7225VXR router—The valid range is from 1 to 2.
– Cisco uBR7246VXR router—The valid range is from 3 to 6.
• port—Downstream controller number on the line card. The permitted
port values are 0 or 1.
Usage Guidelines The cable load-balance docsis-group command creates a DOCSIS LBG with the specified number and
then enters the config-lb-group configuration mode. Use the config-lb-group configuration mode to
configure the DOCSIS LBG
• disable
• docsis-policy
• downstream
• init-tech-list
• init-tech-ovr
• interval
• method
• policy
• restricted
• service-type-id
• tag
• threshold
• upstream
Examples The following example shows how to create a DOCSIS group numbered "1":
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# init-tech-list 1 ucc
Router(config-lb-group)# downstream Cable 1/1
Router(config-lb-group)# upstream Cable 1/0 2
Router(config-lb-group)# docsis-policy 0
Router(config-lb-group)# init-tech-ovr Cable 1/1 1 Cable 1/0 2 init-tech-list 1 ucc
Router(config-lb-group)# service-type-id ccc
Router(config-lb-group)# tag t1
Router(config-lb-group)# interval 10
Router(config-lb-group)# method modems us-method modems
Router(config-lb-group)# no policy us-across-ds pure-ds-load ugs
Router(config-lb-group)# restricted
Router(config-lb-group)# threshold pcmm 70 load 10 stability 50 ugs 70
Router(config-lb-group)#
The following example shows how to configure DOCSIS 3.0 GLBG parameters:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group FN 2 MD cable 1/0
cable load-balance docsis-policy policy-id [rule rule-id | tag tag name [override] ]
no cable load-balance docsis-policy policy-id [rule rule-id | tag tag name [override] ]
Usage Guidelines This command associates a rule with a policy. A policy is created only when a rule is associated with it.
Similarly, the policy is removed if you remove the last rule associated with the policy.
Examples The following example defines a DOCSIS policy, and associates a predefined rule and tag with this
policy:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-policy 1 rule 1
Router(config)# cable load-balance docsis-policy 1 tag SPG override
Router(config)#
cable load-balance exclude {modem mac-address | oui oui-value} [enforce | static | strict]
no cable load-balance exclude {modem mac-address | oui oui-value} [enforce | static | strict]
Syntax Description modem mac-address Specifies the hardware (MAC) address of an individual cable modem to be
excluded from load balancing. (You cannot specify a multicast MAC address.)
oui oui-value Specifies the organization unique identifier (OUI) of a vendor, so that cable
modems from this vendor are excluded from load balancing. The OUI must be
specified as three hexadecimal bytes separated by either periods or colons.
enforce (Optional) Excludes the cable modems from dynamic load balancing, but they
continue to participate in static load balancing.
static (Optional) Excludes the cable modems from static load balancing, but they
continue to participate in passive load balancing and dynamic load balancing.
strict (Optional) Excludes the cable modems from all forms of load balancing.
static strict (Optional) Excludes the cable modem from active and passive load balancing,
but they continue to participate in dynamic load balancing.
Command Default By default, all cable modems on an interface are automatically included in all configured load-balancing
operations when that cable interface is assigned to a load-balance group (no cable load-balance
exclude). When a cable modem is excluded without any options specified, the cable modem is excluded
from dynamic and static load balancing, but it continues to participate in passive load balancing.
Usage Guidelines The cable load-balance exclude command allows you to specify that particular cable modems should
not participate in one or more types of load-balancing operations. This might be done for cable modems
that are currently provisioned for premium services, for cable modems that do not respond appropriately
to upstream channel change (UCC) or channel override messages, or for other reasons.
In particular, you must use the cable load-balance exclude command to exclude cable modems that
require specific upstream channels or downstream frequencies. Load balancing cannot be done when
cable modems are assigned specific channels or frequencies in their DOCSIS configuration files.
You can use the cable load-balance exclude command to specify that these cable modems should not
participate in the following types of load-balancing operations:
• Static load balancing—Load balancing is done at the time a cable modem registers by specifying the
proper target channel in the Downstream Frequency Override or an Upstream Channel ID Override
field in the registration response (REG-RSP) message that the Cisco CMTS sends to the cable
modem. This is the default form of registration-based load balancing.
• Passive load balancing—Load balancing is done at the time a cable modem registers by ignoring a
cable modem’s registration request (REG-REQ) message until it uses the correct target channels.
Use the cable load-balance exclude command to specify this form of load balancing for older cable
modems that do not respond well to the active form of load balancing.
• Dynamic load balancing—A form of traffic-based load balancing, in which cable modems are
balanced among upstreams and downstreams after they come online, while they are passing traffic.
(Dynamic load balancing is enabled using the enforce option with the cable load-balance group
threshold command.)
Use the cable load-balance exclude command to exclude a cable modem from any combination of
load-balancing operations. Table 5 shows which forms of load-balancing operations are excluded and
which are enabled for each form of the cable load-balance exclude command:
Note Excluding cable modems might be required for some cable modems that are not DOCSIS-compliant.
Such cable modems can go offline for long periods of time when load balancing is attempted using
DOCSIS MAC messages. If this is the case, use the cable load-balance exclude command to exclude
such cable modems from load-balancing operations until the modem can be upgraded to
DOCSIS-compliant software.
Examples The following example shows how to exclude a particular cable modem with the MAC address of
0001.0203.0405 from active and dynamic load-balancing operations:
Router# config terminal
Router(config)# cable load-balance exclude mac 0001.0203.0405
Router(config)#
The following example shows how to exclude all cable modems with the OUI of 00.00.0C from active
and dynamic load-balancing operations:
The following example shows how to exclude all cable modems with the OUI of 00.00.0C from dynamic
load-balancing operations. These cable modems are still subject to static load-balancing operations.
Router# config terminal
Router(config)# cable load-balance exclude oui 00.00.0C enforce
Router(config)#
The following example shows how to exclude a particular cable modem from all forms of load-balancing
operations:
Router# config terminal
Router(config)# cable load-balance exclude mac 0001.0203.0405 strict
Router(config)#
Syntax Description n Specifies the number of the load-balance group. The valid range is 1 to 20.
Note You can create a maximum of 20 load-balance groups on each
chassis. However, you can reuse those load-balance groups on
different sets of cable interfaces, as long as they are in different
domains. If downstreams are not included in a load-balance group,
then each downstream can be considered a separate domain.
method modem (Optional) Specifies that the load-balance group should use the number of
active cable modems on an interface to determine the current load (default).
This method does not take into account the amount of traffic flowing
through those particular cable modems.
method service-flows (Optional) Specifies that the load-balance group should use the number of
active service flow IDs (SFIDs) on an interface to determine the current
load.
method utilization (Optional) Specifies that the load-balance group should use an interface’s
current percentage of utilization to determine the current load.
Tip The utilization method does not begin moving cable modems for
load balancing until the utilization of the interface is at 25 percent
or more. This is done to avoid the unnecessary moving of cable
modems due to temporary spikes in an interface’s utilization rates.
Command Default No load-balance groups are created. By default, a load-balance group uses the actual number of cable
modems online each interface to determine load balancing needs (modem option).
Note If you do not create any load-balance groups, the Cisco CMTS defaults to using a form of
registration-based load balancing that attempts to equally distribute cable modems among upstreams at
the time the cable modems register and come online. No load balancing is done for downstreams or for
cable modems that are already online.
Usage Guidelines The cable load-balance command creates a load-balance group, which can then be assigned to a number
of upstream and downstream cable interfaces to allow the Cisco CMTS to load balance cable modems
as needed. The Cisco CMTS can use the load-balance groups for static, passive, and dynamic load
balancing of both upstream and downstream channels. You can configure downstreams and upstreams
to use the same load balancing parameters, or you can configure upstreams and downstreams separately.
Note You can create a maximum of 20 load-balance groups on each chassis. However, you can reuse those
load-balance groups on different sets of cable interfaces, as long as they are in different domains. If
downstreams are not included in a load-balance group, then each downstream can be considered a
separate domain.
Use the cable load-balance group (global configuration) command to initially create and configure a
load-balance group. Then use the cable load-balance group (interface configuration) command to
assign this load-balance group to an upstream or downstream, so that the cable interface will begin
participating in load-balancing operations.
You can configure a load-balance group to use one of the following types of load-balancing methods:
• Modem Method—Uses the number of active cable modems on an interface.
• Service Flow Method—Uses the number of active Service Flow IDs (SFIDs) on an interface.
• Utilization Method—Uses an interface’s current percentage of utilization.
See the following sections for more information about each method.
Modem Method
The modem method of load-balancing uses the number of active cable modems on an interface to
determine the current load. This is a form of distribution-based load balancing, in which the absolute
numbers of modems are used to determine whether interfaces are load balanced.
This method does not take into account the amount of traffic flowing through the cable modems, but the
system does take into account the relative bandwidth of the channels being used, so that channels with
higher bandwidths are allocated higher numbers of cable modems. This means that when interfaces are
using different channel widths or modulation profiles, the system can assign different numbers of cable
modems to the interfaces to achieve a balanced load. For example:
• Channel widths— If two upstreams are being load balanced, and one upstream is configured with a
channel width of 1.6 MHz and the other upstream is configured for a channel width of 3.2 MHz, the
Cisco CMTS allocates twice as many cable modems to the second upstream, because its channel
width is twice as large as the first upstream’s channel width.
• Modulation profiles— If one downstream is configured for 64-QAM and the other downstream is
configured for 256-QAM, the Cisco CMTS allocates a proportionately larger number of cable
modems to the second downstream so as to achieve a balanced load.
When both the channel width and different modulation profile are set differently on two interfaces, the
system calculates a “weight” value to use as a guide to determine the relative bandwidths of the
interfaces.
Tip In a system with balanced loads, the interfaces will contain the same number of cable modems only when
the interfaces are configured with the same modulation parameters.
The service-flows method of load balancing uses the number of active service flow IDs (SFIDs) on an
interface to determine the current load. This is a form of distribution-based load balancing, in which the
absolute numbers of service flows are used to determine whether interfaces are load balanced.
This method does not take into account the amount of traffic flowing on each SFID, but the system does
take into account the relative bandwidth of the channels being used, so that channels with higher
bandwidths are allocated higher numbers of SFIDs. This means that when interfaces are using different
channel widths or modulation profiles, the system can assign different numbers of SFIDs to the
interfaces to achieve a balanced load. For example:
• Channel widths— For example, if two upstreams are being load balanced, and one upstream is
configured with a channel width of 1.6 MHz and the other upstream is configured for a channel
width of 3.2 MHz, the Cisco CMTS allocates twice as many SFIDs to the second upstream, because
its channel width is twice as large as the first upstream’s channel width.
• Modulation profiles— For example, if one downstream is configured for 64-QAM and the other
downstream is configured for 256-QAM, the Cisco CMTS allocates a proportionately larger number
of SFIDs to the second downstream so as to achieve a balanced load.
When both the channel width and different modulation profile are set differently on two interfaces, the
system calculates a “weight” value to use as a guide to determine the relative bandwidths of the
interfaces.
Tip In a system with balanced loads, the interfaces will contain the same number of SFIDs only when the
interfaces are configured with the same modulation parameters.
Utilization Method
The utilization method uses an interface’s current percentage of utilization to determine the current
load. This method uses the amount of traffic being sent over an interface, in the form of the percentage
of total bandwidth being used. (To avoid unnecessary movement of cable modems, the utilization
method does not perform load balancing until an interface is at least 25 percent of utilization.)
Note Do not use the utilization method of load balancing on cable interfaces that have a small
number of cable modems and where a single modem is responsible for the majority of the
interface load. In this condition, the Cisco CMTS could end up continually moving cable
modems from one interface to another in an endless attempt to load balance the interfaces.
To avoid this, configure the utilization threshold to a value that is higher than what can be
caused by any single cable modem.
When using the utilization method, the system takes into account the relative throughput and bandwidth
(as determined by the modulation profiles and channel widths) of each interface when evaluating the load
on those interfaces. For example, if two upstreams are being load-balanced using the utilization method,
and the first upstream has twice the bandwidth of the second upstream, the two upstreams are considered
balanced when they reach the same percentage of utilization. The first upstream is carrying more traffic
than the second upstream because it has a larger capacity for traffic, but the percentage of utilization will
be the same.
Note Certain conditions can cause a system instability that could result in the Cisco CMTS endlessly
attempting to load balance the interfaces. For example, this situation could occur in noisy environments,
where cable modems drop offline on a regular basis, or when cable modems are repeatedly trying to
register because the provisioning system has sent them the wrong DOCSIS configuration files. If the
Cisco CMTS detects such unstable situations, it does not load balance cable modems from those
interfaces until the system stabilizes. However, if the system instability persists, you should increase the
threshold values using the cable load-balance group threshold command until you can solve the
stability problems.
Use the no form of this command to delete a load-balance group. Deleting a load-balance group also
automatically removes all upstream and downstream channel associations that were made with that
group using the cable load-balance and cable upstream load-balance commands.
Tip To exclude individual cable modems from one or more types of load balancing, use the cable
load-balance exclude command.
Examples The following example shows how to create a load-balance group numbered 10, using the default method
of modem, which specifies that the Cisco CMTS uses the actual number of cable modems that are online
to determine load-balancing operations.
Router# config terminal
Router(config)# cable load-balance group 10
Router(config)#
The following example shows how to create a load-balance group numbered 1, which uses the number
of active SFIDs on an interface to determine the current load on the interface:
Router# config terminal
Router(config)# cable load-balance group 1 method service-flows
Router(config)#
Command Description
cable upstream Assigns an upstream to a load-balance group.
load-balance group
clear cable Clears the counters or state machine used to track load-balancing
load-balance operations.
show cable Displays real-time statistical and operational information for
load-balance load-balancing operations.
Syntax Description n Specifies the number of the load-balance group to which the downstream should be assigned. The
valid range is 1 to 20.
Command Default A downstream is not assigned to a load-balance group. When you use this command to add a downstream
to a group, it also automatically adds all of the associated upstreams to the same group, unless you have
also used the cable upstream load-balance group command to assign the upstreams to different groups.
Usage Guidelines After you have used the cable load-balance group (global configuration) command to initially create
and configure a load-balance group, use the cable load-balance group (interface configuration)
command to assign this load-balance group to a downstream. This enables the cable interface to begin
participating in load-balancing operations.
Tip Use the cable upstream load-balance group command to assign this load-balance group to an
upstream.
The following rules apply when creating and assigning load-balance groups:
• A downstream or upstream can belong to only one load-balance group.
• All downstreams and upstreams in a load-balance group must share physical radio frequency (RF)
connectivity to the same group of cable modems. Downstreams can be in a separate load-balance
group than upstreams, but all downstreams or all upstreams that have the same RF physical
connectivity must be members of the same load-balance group. You cannot distribute downstreams
or upstreams that share physical connectivity across multiple load-balance groups.
Note If both downstreams and upstreams are assigned to the same load-balance group, the
Cisco CMTS attempts to balance both the downstream and upstream values when it moves
cable modems.
• If the load-balance group includes downstream interfaces, you must also configure the downstream
center frequency on those interfaces, using the cable downstream frequency cable interface
command. This command is informational-only on cable interfaces that use an external upconverter,
but it is required for load balancing, so that the Cisco CMTS knows where to move cable modems
when it is load balancing downstreams.
• Load balancing is done only on a per-chassis basis—all interfaces in a load-balance group must be
in the same chassis.
Note In Cisco IOS Release 12.2(15)BC1, you can configure an interface for both load balancing and
Hot-Standby Connection-to-Connection (HCCP) N+1 redundancy, but load balancing does not continue
after a switchover from a Working to a Protect interface. Load balancing resumes when the Cisco CMTS
switches back to the Working interface.
Examples The following example shows how to assign the first downstream on the cable interface line in slot five
to load balance group 5:
Router# config terminal
Router(config)# interface cable 5/0
Router(config-if)# cable load-balance group 5
Router(config-if)#
Command Default Load balancing is not configured by default on the Cisco CMTS.
Examples The following example illustrates configuration of the initialization techniques specified for DCC:
Router(config)# cable load-balance group 1 dcc-init-technique 4
For further examples of this command, and related keywords, refer to related commands, and refer also
to Configuring Load Balancing and Dynamic Channel Change (DCC) on the Cisco CMTS.
Usage Guidelines This command is subject to the restrictions and prerequisites described in Configuring Load Balancing
and Dynamic Channel Change (DCC) on the Cisco CMTS.
Command Description
cable load-balance group threshold Sets the threshold levels for corresponding service flow types
(Supporting Dynamic Channel for the specified Load Balancing group, supporting Dynamic
Change) Channel Change (DCC)
show controllers cable Displays statistics for Dynamic Channel Change (DCC) for
load balancing.
test cable dcc (Supporting Dynamic Performs testing functions for Load Balancing with DCC
Channel Change)
Command Default By default, DCC uses the 0 initialization technique, unless otherwise specified.
Examples The following example illustrates configuration of the initialization techniques specified for DCC:
Router(config)# cable load-balance group 1 dcc-init-technique 4
Usage Guidelines This command is subject to the restrictions and prerequisites described in Configuring Load Balancing
and Dynamic Channel Change (DCC) on the Cisco CMTS.
DCC for Load Balancing supports the following types of initialization techniques:
• Initialization technique 0—reinitializes the MAC address. The cable modem needs to go offline and
reregister on the new channel.
• Initialization technique 1—broadcasts the initial ranging. The cable modems are kept online and
re-registration is avoided, but this technique requires completion of initial ranging.
• Initialization technique 2—performs periodic ranging. The cable modems are kept online and
allowed to start on the new channel with periodic ranging.
• Initialization technique 3—performs initial ranging or periodic ranging. This technique enables the
cable modem to choose a ranging method between initial ranging and periodic ranging.
• Initialization technique 4—uses the new channel directly. The cable modem may start to send data
immediately on the new channel without any initial ranging or periodic ranging.
Syntax Description n Specifies the number of the load-balance group. The valid range is 1 to 20.
interval Specifies the frequency, in seconds, for how often the Cisco CMTS should determine the
current load on each cable interface. This also determines the minimum time between when
cable modems can be moved to load balance the interfaces. One cable modem at most is
moved during each interval time period. The valid range is 0 to 3600 seconds, with a default
value of 10 seconds.
Command Default Each load-balance group defaults to a frequency of 10 seconds to determine the current load on an
interface, allowing at most one cable modem to be moved every 10 seconds.
Usage Guidelines To properly perform load balancing, the Cisco CMTS must determine the actual load on an interface on
a periodic basis. This frequency of the updates also determines how frequently cable modems can be
moved to achieve balanced loads. One cable modem, at most, is moved during each update period.
The more often these updates are performed, the more accurate the Cisco CMTS can be in performing
its load-balancing operations. As a general rule, begin with the default frequency value of 10 seconds,
and then adjust the value accordingly, in small increments, as load balancing conditions or performance
levels might require.
Note Having too small an interval could result in cable modems being constantly moved to achieve balanced
loads during peak usage times when load balance could spike to transient heavy traffic. Also, more
frequent updates can have a performance impact, especially on routers with a large number of active
interfaces and cable modems.
Examples The following example shows how to configure load-balance group 3 so that it performs a policy update
every 30 seconds:
The following example shows how to reset load-balance group 10 to its default update frequency of 10
seconds:
Router# config terminal
Router(config)# no cable load-balance group 10 interval
Router(config)#
Syntax Description ds-lb-group-id Specifies the load balancing group being configured. This downstream
group includes the upstream segment in load balancing decisions.
us-groups-across-ds Specifies the upstream group to be distributed in load balancing decisions
for the downstream group specified.
Command Default By default, this load balancing configuration is not enabled on the Cisco CMTS.
Examples The following example illustrates this command and one supported implementation:
Router(config)# cable load-balance group 1 policy 2
Router(config)#
In this example, a cable modem that comes online on the interface cable 5/0 Upstream 2 could potentially
come online on the following interfaces:
• cable 3/0 upstream 2
• cable 4/0 upstream 2
• cable 6/0 upstream 2
• nowhere else, however
With downstream load balancing prior to Cisco IOS Release 12.2(17b)BC4, having 100 cable modems
per segment would be possible in an extreme case that distributes cable modems as follows:
U0 U1 U2 U3 Downstream
3/0 97 1 1 1 100
4/0 1 97 1 1 100
5/0 1 1 97 1 100
6/0 1 1 1 97 100
Usage Guidelines This command is subject to the restrictions and prerequisites described in Configuring Load Balancing
and Dynamic Channel Change (DCC) on the Cisco CMTS.
Cisco IOS Release 12.2(17b)BC4 enables the optional operation of making downstream load balancing
decisions as follows:
• The target downstream segment is in the same downstream load balancing group as the source
downstream segment.
• The upstream load balancing group can be set for the corresponding channel on which a cable
modem is balanced.
• The Cisco CMTS automatically locates the upstream segment for a load balancing group and
processes the upstream group status on the source interface that has the lowest load.
• The target downstream segment must have an upstream channel set in the upstream load balancing
group.
• The highest target upstream segment must carry less load than any other potential target —the
highest upstream segment on other interfaces.
This command enables an alternative downstream load balancing scheme that makes use of per-upstream
loads rather than total downstream loads.
This enhancement performs downstream load balancing that accounts upstream channel loads in the
same upstream load balancing group, rather than on the basis of the entire downstream channel load.
Prior Cisco IOS releases may not have distributed cable modems evenly over individual upstream
channels, nor in a way that accounted for downstream and upstream together.
This enhancement applies when downstream load balancing occurs on a headend system with separate
upstream load balancing segments; the upstream segments are spread over multiple downstreams
segments.
This optional configuration supports output of the show cable load-balance command so that the
command displays more information about loads on channels that are configured on external or remote
cable interface line cards.
Note Defining the UGS policy in load balancing is required, in additional to UGS that is used for PCMM calls.
Syntax Description group-num Specifies the load balancing group number being configured.
pcmm Enables balancing of modems with active PCMM service flows.
ugs Enables balancing of modems with active UGS service flows.
Command Default By default, cable modems with active PCMM are not load balanced.
By default, cable modems with active UGS flows are not load balanced.
Examples The following examples illustrate configuration commands for PacketCable MultiMedia (PCMM) and
Unsolicited Grant Service (UGS) for DCC:
Router(config)# cable load-balance group 1 policy pcmm
Router(config)# cable load-balance group 1 policy ugs
Usage Guidelines This command is subject to the restrictions and prerequisites described in Configuring Load Balancing
and Dynamic Channel Change (DCC) on the Cisco CMTS.
Syntax Description n Specifies the number of the load-balance group. The valid range is 1 to 20.
Command Default Cable modems with active UGS service flows can be moved for load-balancing (cable load-balance
group n policy ugs)
Usage Guidelines The cable load-balance group policy ugs command determines whether a load-balance group can move
cable modems with UGS service flows, so as to enforce dynamic load balancing policies. Because most
voice calls use UGS service flows to allow real-time traffic, this option is primarily used to determine
whether the Cisco CMTS will move cable modems with active voice calls.
If you disable this option (no cable load-balance group policy ugs), the Cisco CMTS does not move
cable modems with active UGS service flows to a new upstream or downstream. This prevents some
possible interruptions of service to these customers, but it could result in denial of service conditions for
other customers if the interface starts becoming overloaded.
To avoid this, the default configuration (cable load-balance group policy ugs) of this command allows
the Cisco CMTS to move cable modems to a new upstream or downstream, even if they have active UGS
service flows. This enables the Cisco CMTS to perform optimum load balancing, but it could cause a
momentary interruption in the voice call—users on the voice call might hear a momentary drop during
the call, but the call should not be terminated.
Note The cable load-balance group policy ugs command affects only dynamic load-balancing operations
and does not affect static and passive load-balancing operations. Dynamic load balancing is enabled
using the enforce option with the cable load-balance group threshold command.
Examples The following example shows how to enable the UGS policy on a load-balance group (the default
configuration), so that the Cisco CMTS can move cable modems with active UGS service flows as
needed to enforce the current dynamic load balancing policy:
Router# config terminal
Router(config)# cable load-balance group 13 policy ugs
Router(config)#
The following example shows how to configure a load-balance group so that the Cisco CMTS does not
move cable modems with active UGS service flows (default configuration):
Router# config terminal
Router(config)# no cable load-balance group 100 policy ugs
Router(config)#
Syntax Description n Specifies the number of the load-balance group. The valid range is 1 to 20.
load load-value Specifies the maximum load difference, as expressed in a percentage of
total load, that can exist between interfaces in a load-balance group before
the Cisco CMTS performs load balancing. If the load between interfaces is
greater than the value specified by load-value, cable modems that are
registering are assigned to the lesser-utilized interface until the load
difference is once again below this value. The valid range for load-value is
1 to 100 percent, with a default of 10 percent.
Note The default of 10 percent is the minimum recommended threshold.
Do not set this threshold below 10 percent unless you have been
instructed to do so by Cisco TAC.
enforce threshold (Optional) Enables dynamic load balancing, which moves online cable
modems after their initial registration to achieve load balancing of the cable
interfaces in a load-balance group. Cable modems that are currently online
are moved when the load difference between two interfaces in the
load-balance group exceeds this percentage. Modems continue to be moved
until the load difference falls below this value.
The possible valid range for threshold is 1 to 100 percent, but the threshold
must be equal to or greater than the percentage specified with the load-value
option. For this reason, the actual minimum for threshold is the current
setting of the load-value option. The default is also the same value as the
load-value parameter.
load minimum number (Optional) Specifies that cable modems should be moved only if the load
between the two interfaces is greater than the specified number of cable
modems or service flows (valid only when the method is the number of
modems or service flows). The valid range is 1 to 100, with a default of 5.
stability percent Specifies the threshold to be used to determine whether a channel or
interface is unstable, in terms of the percentage of successful ranging
requests. The percent value specifies the minimum percentage of successful
ranging requests that is acceptable; otherwise, the CMTS begins moving
CMs. The valid range is 1 to 100 percent, with a default of 50 percent.
ugs band-value Specifies that the Cisco CMTS should move cable modems with active UGS
service flows when the current UGS usage reaches the percentage of total
bandwidth available that is specified by the band-value parameter. The valid
range for band-value is 0 to 100 percent, with a default of 70 percent.
Note This option is effective only when the enforce option has also been
used to enable dynamic load balancing, and the Cisco CMTS has
been authorized to move cable modems with active UGS service
flows (using the cable load-balance group policy ugs command).
Command Default The load parameter defaults to 10 percent, the load minimum parameter defaults to 5, the stability
parameter defaults to 50 percent, and the ugs parameter defaults to 70 percent. By default, only static
load balancing is done (no enforce option). If the enforce option is given without a threshold value, it
defaults to the same value as the load parameter.
Usage Guidelines The cable load-balance group threshold command configures a load-balance group for the threshold
values that it should use to determine when a cable modem should be moved to a new downstream or
upstream. You can specify the following different thresholds:
• load—Specifies the maximum load usage that can exist between interfaces in a load-balance group
before the Cisco CMTS begins static load-balancing operations. The default value of load-value is
10 percent, which means that two upstreams or two downstreams can have usage rates that vary up
to 10 percent before the Cisco CMTS begins rebalancing the load usage. This rebalancing, however,
is done only when cable modems first register with the Cisco CMTS—the Cisco CMTS does not
switch cable modems that are already online.
For example, if the load value is 10 percent, and upstream 1 is at 23 percent and upstream 2 is at 30
percent, no cable modems are moved. However, if load usage for upstream 2 reaches 35 percent, the
Cisco CMTS begins assigning new cable modems, as they register, to upstream 1 until the difference
in load usage between the two upstreams falls below 10 percent.
Note The default of 10 percent is the minimum recommended threshold. Do not set this threshold
below 10 percent unless you have been instructed to do so by Cisco TAC.
• enforce—Enables dynamic load balancing, so that the Cisco CMTS can move cable modems that
are already online. This option has its own threshold value, which specifies the difference in load
usage that must exist between two interfaces in a group before the Cisco CMTS begins moving
online cable modems. The Cisco CMTS continues to move cable modems until the difference in load
usage rates falls below the threshold value.
When using dynamic load balancing and an upstream channel is overloaded, the Cisco CMTS sends
an Upstream Channel Change (UCC) request to a cable modem to instruct it to move to another
upstream. The cable modem should move to the new upstream channel, without going offline or
having to reregister with the CMTS.
When using dynamic load balancing and a downstream channel is overloaded, the Cisco CMTS
sends an abort response to a cable modem’s ranging request (RNG-REQ) message. When the cable
modem sends a new REG-REQ message, the Cisco CMTS specifies the new downstream channel in
the Downstream Frequency Override field in its REG-RSP message. The cable modem must go
offline and reregister on the new downstream channel, so as to conform to the DOCSIS 1.0
specifications.
Note In Cisco IOS Release 12.2(15)BC1, the dynamic load balancing method results in cable
modems going offline and having to reregister whenever the modems are moved between
downstreams. This is because the DOCSIS 1.0 specification requires cable modems to
reregister whenever the downstream is changed using the Downstream Frequency Override
message. Cable modems should not go offline when moved between upstreams.
The Cisco CMTS also continues to enforce the load threshold value to perform static load balancing
as well. Therefore, the threshold percentage should be equal to or greater than the percentage
specified with the load load-value option.
For example, if you specify load 10 enforce 15, the Cisco CMTS monitors the load usage between
cable interfaces in the load-balance group. If upstream 1 reaches 33 percent and upstream 2 reaches
45 percent, the Cisco CMTS begins static load-balancing operations by assigning new cable
modems to upstream 1 when they register. If the difference still continues to grow, and upstream 2
reaches 50 percent, the Cisco CMTS also begins dynamic load-balancing operations by moving
online cable modems, until the difference in load usage falls below 15 percent. The Cisco CMTS
then continues static load-balancing operations until the difference falls below 10 percent.
Tip The enforce threshold is not displayed in the configuration file if it is the same as the load
threshold. For example, if you enter the “cable load-balance group 1 threshold load 50
enforce 50” command, it appears as “cable load-balance group 1 threshold load 50 enforce”
in the configuration file.
• load minimum—Specifies that cable modems should be moved only if the load between the two
interfaces is greater than the specified number of cable modems or service flows. This option is valid
only when you have configured the load-balance group using either the method modem or
method service-flows options with the cable load-balance group (global configuration)
command. It is not used with the utilization method.
• stability—Specifies the minimum percentage of ranging requests that are successful before the
Cisco CMTS determines that the interface or channel is unstable. When the channel has fewer than
this percentage of cable modems responding to periodic ranging requests over a one-minute period,
the Cisco CMTS begins moving modems to other channels in the load-balance group. For example,
when set to 75 percent, the Cisco CMTS begins moving modems when fewer than 75 percent of
modems are replying to ranging requests.
• ugs—Specifies a threshold for when the Cisco CMTS should move cable modems that have active
UGS service flows, which are typically used for active voice calls. This option goes into force only
when dynamic load balancing has been enabled (using the enforce option), and the Cisco CMTS has
been allowed to move cable modems with active UGS service flows (using the cable load-balance
group policy ugs command). The band-value threshold specifies the maximum usage of UGS
service flows that should exist before the Cisco CMTS begins moving calls.
For example, if the band-value threshold is at its default of 70 percent, the Cisco CMTS does not
begin moving cable modems with active UGS service flows until UGS usage on an upstream or
downstream reaches 70 percent of the total available bandwidth. The Cisco CMTS continues
moving cable modems that are online with active UGS service flows until the UGS usage on the
interface falls below 70 percent.
Note Certain conditions can cause a system instability that could result in the Cisco CMTS endlessly
attempting to load balance the interfaces. For example, this situation could occur in noisy environments,
where cable modems drop offline on a regular basis, or when cable modems are repeatedly trying to
register because the provisioning system has sent them the wrong DOCSIS configuration files. If the
Cisco CMTS detects such unstable situations, it does not load balance cable modems from those
interfaces until the system stabilizes. However, if the system instability persists, you should increase the
threshold values using the cable load-balance group threshold command until the system stabilizes.
Examples The following example shows how to configure load-balance group 2 so that it performs static load
balancing when the difference between two cable interfaces in the group is 20 percent or more.
Router# config terminal
Router(config)# cable load-balance group 2 threshold load 20
Router(config)#
The following example shows how to configure load-balance group 5 so that it performs static load
balancing when the difference in usage between two cable interfaces in the group is 20 percent or more,
and so that it performs dynamic load balancing when the difference in usage is 30 percent or more. The
Cisco CMTS will also begin moving cable modems with active UGS service flows when UGS service
flows reach 60 percent of the total bandwidth available on the upstream channel.
Router(config)# cable load-balance group 5 threshold load 20 enforce 30
Router(config)# cable load-balance group 5 threshold ugs 60
Router(config)# cable load-balance group 5 policy ugs
Router(config)#
Note You must configure the load-balance group with the cable load-balance group policy ugs command
before the Cisco CMTS begins enforcing the threshold that was set with the cable load-balance group
threshold ugs command.
Command Default Load balancing is not configured by default on the Cisco CMTS.
Examples The following command specifies the reserved bandwidth threshold. Above this level, cable modems
with active PCMM service flows participate in load balancing, and the default threshold is 70%. Note
that if UGS is used for PCMM, the UGS threshold needs to be crossed as well. The default UGS
threshold is 70%)
Router(config)# cable load-balance group 4 threshold pcmm <pcmm-value>
Usage Guidelines In Cisco IOS releases prior to Cisco IOS Release 12.3(17a)BC, the load balancing default setting is
UGS. This is not the case with Cisco IOS Release 12.3(17a)BC. In this latter release, and subsequent
releases, configuration is required if the cable modems with active UGS flows are desired to participate
in load balancing.
This command is subject to the restrictions and prerequisites described in Configuring Load Balancing
and Dynamic Channel Change (DCC) on the Cisco CMTS.
Syntax Description 0-100 Specifies the maximum number of failures before a CM is removed from the
dynamic LB. However, if you give the value 0, the cable load-balance
modem max-failures command gets disabled.
Note The CM is excluded from the dynamic load balance operations after
it has failed the specified number of times, however it still belongs
to a LBG.
Examples The following example shows how to configure CM using the cable load-balance modem max-failures
command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance modem max-failures 10
Router(config)#
Examples The following example shows how to assign a group of modems with a common MAC mask to a group
or a service type ID using the cable load-balance restrict modem command. To assign the modem to a
LBG, you can either specify the LBG ID or the service type ID.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance restrict modem 1 001a.c30c.7eee FFFF.FFFF.0000
docsis-group 100
Router(config)#
Usage Guidelines The no form of this command supports the following actions:
• Remove a defined rule.
• Remove the rule from all policies.
• Remove the policy itself if it is the last rule of that policy.
Syntax Description buffer-size Specifies the total size of the buffer that will contain the logged error messages. The valid
range is 4096 to 1048576 bytes (4 KB to 1 MB), with a default value of 4096 bytes.
Note The maximum buffer size is limited by the amount of actual unused memory that
is available on the Cisco CMTS.
Command Default Error messages for bad IP source addresses are logged to the console or current system log, if defined.
If logged is enabled, without specifying a specific buffer size, the default size is 4096 bytes (4 KB).
Usage Guidelines The cable source-verify command enables service providers to verify that the IP addresses being used
on the cable interface have been properly assigned by the provider’s DHCP servers. When a bad IP
address is detected, the Cisco CMTS generates a BADIPSOURCE error message in the console logs.
In previous Cisco IOS releases, the Cisco CMTS generated these particular error messages for every IP
packet that contained a bad IP source address. This can create a large volume of error messages that can
make it difficult to see other error messages in the console logs.
To create a separate log for these error messages, use the cable logging badipsource command. You can
also specify the size of the buffer that will contain these error messages. When the buffer becomes full,
the oldest messages are deleted to make room for newer messages, so choose a buffer size that will allow
you to retain all messages until you can examine them.
On the Cisco uBR10012 router, this command includes only the BADIPSOURCE error messages
generated by the PRE module. The cable interface line cards also generate their own error messages, but
because these error messages are typically duplicates of the ones generated by the PRE module, they are
not included in the separate log.
Tip If you find that the current buffer is too small to contain the current volume of error log messages, you
can issue this command again with a larger buffer size. However, doing so will automatically clear out
all messages currently in the buffer, so be certain that you have viewed all of the current messages before
giving a second cable logging badipsource command.
Note Be cautious when specifying the buffer size, because the Cisco CMTS could run out of memory for other
tasks. Use the show memory EXEC command to display the maximum available processor memory,
and set the buffer size for this command to a value well within that maximum value.
To display the contents of this error log, use the show cable logging command. To clear the buffer after
you have viewed the error messages, use the clear cable logging command. You can also use the service
timestamps log command to add a timestamp to the messages in the log.
To print the BADIPSOURCE messages to the console or syslog server, use the no cable logging
badipsource command (which is the default configuration). Note that this configuration does not turn
off the generation of BADIPSOURCE messages, but only configures the system for the default log
message behavior.
Tip If you do not want to see any BADIPSOURCE messages at all, use the cable logging badipsource 4096
command so that these messages go to a separate buffer with the smallest possible size. You will then
not see these error messages unless you explicitly use the show cable logging command to display them.
Examples The following example shows how to enable the logging of bad IP source address error messages, using
a buffer size of 524,288 bytes (512 KB):
Router# configure terminal
Router(config)# cable logging badipsource 524288
Router(config)#
Tip You must also use the cable source-verify command to enable verification of source IP addresses before
the buffer will contain any error messages about bad IP source addresses. If you do not use the cable
source-verify command, you can still use the cable logging badipsource command to create a buffer,
but the buffer will always remain empty.
The following example shows how to enlarge the current buffer for bad IP source address error messages
by giving the cable logging badipsource command a second time. Because this will empty out the buffer
of all current messages, be sure to display the current buffer contents before giving the command a
second time.
Router# configure terminal
Router(config)# cable logging badipsource 8192
Router(config)# exit
Router# show cable logging badipsource
The following example shows how to stop the logging of bad IP source address error messages to a
separate buffer. This clears out all error messages from the buffer and removes the buffer from memory,
and future error messages for bad IP source addresses are logged to the console or to the current system
log, if any.
Router# configure terminal
Router(config)# no cable logging badipsource
Router(config)#
Related Commands cable source-verify Enables verification of IP addresses for CMs and CPE devices on the upstream.
clear cable logging Removes all error messages about bad IP source addresses on the cable
interfaces from the error log buffer.
show cable logging Displays the log of error messages about bad IP source addresses on the cable
interfaces.
Command Default DOCSIS events are saved to the general logging buffer on the Cisco CMTS by default.
Usage Guidelines Use the show cable logging command to check whether the logging feature is enabled and the status of
the logging buffer.
Examples The following example shows how to clear the log buffer that contains a bad IP source address error
messages:
Router# show cable logging summary
New Commands
Modified Commands
cable map-advance
To configure the dynamic map advance algorithm, use the cable map-advance command in cable
interface configuration mode. Use the no form of this command to disable this function.
no cable map-advance
Syntax Description dynamic safety Enables the dynamic MAP advance algorithm that automatically tunes
lookahead time in MAPs based on the current farthest CM on a
particular upstream port. The safety argument specifies a safety factor
for the dynamic map advance algorithm in microseconds. This value
controls the amount of extra lookahead time in MAPs to account for
inaccuracies of the measurement system and internal software
latencies. The valid range is 300 to 1500 microseconds, with a default
of 1000.
Note Using larger safety factors increases the run time lookahead in
MAPs, but reduces the upstream performance.
static Enables the static map advance algorithm that uses a fixed lookahead
time value in MAPs based on the worst-case propagation delay of 100
mile HFC cable network.
max-delay Specifies the maximum round trip delay between the cable plant and
furthest CM in microseconds. The valid range is 100 to 2000
microseconds, with a default of 1800. The typical delay for a mile of
coaxial cable is approximately 7 microseconds. The typical delay for a
mile of fiber cable is approximately 8 microseconds.
Defaults Dynamic map advance with a safety factor of 1000 microseconds and a max-delay of 1800 microseconds
Usage Guidelines The max-delay option, which was introduced in Cisco IOS Release 12.1(10)EC, specifies the maximum
possible round-trip delay between the cable plant and furthest CM in the cable network. A CM will not
be allowed to exceed the maximum timing offset given by the max-delay value (in static mode) or given
by the combination of the max-delay and safety values (in dynamic mode). If a CM reports a timing
offset beyond the maximum value, the CMTS will reset its offset to the maximum value and put an
exclamation point (!) next to its offset value in the show cable modem display.
In dynamic MAP operation, Cisco IOS 12.1(10)EC also implements a regular polling of the furthest CM,
to determine if that CM is now offline. If the furthest CM has gone offline, the CMTS scans the currently
online CMs to determine which CM is now the furthest offline and updates the dynamic MAP advance
algorithm with the new value.
Examples The following example shows how to configure the dynamic map advance to 1500 microseconds:
router(config-if)# cable map-advance dynamic 1500
Related Commands show cable modem Displays statistics for the connected CMs.
Syntax Description access-list Specifies that the IP multicast streams defined by the access list be encrypted. Access lists
can be IP access list numbers or an IP access list name. Valid access list numbers are from
100 to 199.
Usage Guidelines The cable match address command binds an access-list to a cable interface, allowing multicast
encryption to be performed on traffic through that interface. To configure the access list, use the
ip access-list command.
For additional information on configuring for multicast operations, see the chapters on IP Multicast in
the Release 12.2 Cisco IOS IP Configuration Guide and in Volume 3 of the Cisco IOS IP Command
Reference.
Note This command is available only on images that support Baseline Privacy Interface (BPI) and Baseline
Privacy Interface Plus (BPI+) encryption.
Examples The following example shows how to specify that the multicast stream defined by the access list named
reno be encrypted on cable interface 3/0:
Router(config)# interface c3/0
The following example shows how to specify that the multicast stream defined by the access list number
102 be encrypted:
Router(config)# interface c3/0
Router(config-if)# cable match address 102
cable max-hosts
To specify the maximum number of hosts that can be attached to a subscriber's CM, use the cable
max-hosts command in cable interface configuration mode. Use the no form of this command to reset
the allowable number of hosts attached to a CM to the default value of 0 hosts.
cable max-hosts n
no cable max-hosts
Syntax Description n Specify the maximum number of hosts that can be attached to a CM on this interface. Valid range
is from 0 to 255 hosts. Default value is 0.
Command Default 0
Usage Guidelines The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all
CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
• cable modem max-hosts—Sets the maximum number of hosts for a particular CM.
• cable max-hosts—Sets the maximum number of hosts for all CMs on a particular cable interface.
• cable modem max-cpe—Sets the maximum number of hosts for all CMs using the Cisco CMTS
router.
The more specific commands override the settings of the less specific commands. For example, if you
use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can
still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note The CMTS assigns the MAX Host value to a cable modem at the time that the cable modem registers
with the CMTS. Changing any of the MAX Host commands affects only cable modems that register after
the change.
Tip For more information on how these commands interact to set the maximum CPE values, see the chapter
Maximum CPE or Host Parameters for the Cisco Cable Modem Termination System in the
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.
Examples The following example shows how to set the maximum hosts for CMs on this particular cable interface
to 15:
Router(config)# interface c6/0
Router(config-if)# cable max-hosts 15
Syntax Description data-per-session The number of data flows per session. The range is from 3 to 30. The default
is 5.
timer Displays the cable line card timer to wake up.
timer value The timer wake up interval value in milliseconds. The range is from 8 to 500.
The default is 100.
Command Default The cable metering data flow values will not be visible.
Usage Guidelines The cable metering data-per-session command allows users to view the number of cable metering data
flows per session. The command limits or throttles the data collection between the cable line card and
the route processor.
Examples The following example displays the number of cable metering data flows per session:
Router#configure terminal
Router(config)#cable metering data-per-session 8 timer 100
Router#show run | inc metering
cable metering destination 2.7.36.88 6789 0 15 non-secure
cable metering data-per-session 8 timer 100
cable metering destination ip-address port [ip-address2 port2] retries minutes {non-secure |
secure} [cpe-list-suppress] [flow-aggregate] [full-records]
no cable metering
Syntax Description ip-address port Address and TCP port number for the billing application on the external
server:
• ip-address—IP address for the external collection server.
• port—TCP port number for the billing collection application on the
server. The valid range is from 0 to 65535, but the port should not be
one of the widely-used TCP port numbers (0 to 1024).
ip-address2 port2 (Optional) IP address and TCP port number for a billing application on a
secondary external server that is used if the primary server fails to respond:
• ip-address2—IP address for the secondary external server.
• port2—TCP port number for the billing collection application on the
secondary server. The valid range is from 0 to 65535, but the port
should not be one of the widely-used TCP port numbers (0 to 1024).
retries Number of retry attempts that the Cisco CMTS makes to establish a secure
connection with the external server before using the secondary server (if
configured) and sending an SNMP trap about the failure. The valid range
for n is from 0 to 5, with a default of 1 retry attempt.
minutes Frequency of the billing records streamed to the external server. The valid
range is 2 to 1440 minutes (24 hours), with no default.
Note We recommend a minimum interval of 30 minutes.
non-secure Specifies that the Cisco CMTS should use an unencrypted TCP connection
when connecting with the billing application on the external server.
secure Specifies that the Cisco CMTS should use a secure socket layer (SSL) TCP
connection when connecting with the billing application on the external
server.
Note This option is available only on the Cisco CMTS software images
that support Baseline Privacy Interface (BPI) encryption.
cpe-list-suppress (Optional) Eliminates the customer premises equipment (CPE) IP addresses
from the billing records to improve performance.
Note The default is for CPE addresses to be included in the billing record,
up to a maximum of five CPE IP addresses for each cable modem.
flow-aggregate (Optional) Combines all information for an individual cable modem into
one record. Separate counters are maintained for upstream and downstream
traffic, but those counters include all service flows in that direction.
full-records (Optional) Provides information about full service flow (active and idle)
records.
Command Default Usage-based billing is disabled, by default. When enabled, CPE IP addresses (a maximum of five per
cable modem) are included in the billing records by default.
Usage Guidelines The cable metering destination command enables usage-based filling and configures it for streaming
mode, where the Cisco CMTS creates the billing records and regularly sends them to an external server
for use by the billing application.
The Cisco CMTS attempts to establish a connection with the first (primary) external server, and if this
fails, the CMTS sends an SNMP trap about the failure. The Cisco CMTS retries the connection for the
number of times specified in the cable metering destination command, and if all of those attempts fail,
the Cisco CMTS switches to the secondary external server, if configured. The Cisco CMTS repeats this
sequence at every interval, and always tries to connect to the primary server first before attempting to
use the secondary server.
Note You can enable usage-based billing using either the cable metering filesystem or cable metering
destination command, but not both. If you give these commands twice, the second command will
overwrite the first.
If the CMTS cannot transmit the billing record to the external server, and if metering traps have been
enabled using the snmp-server enable traps cable metering command, the CMTS sends an SNMP trap
to the SNMP manager describing the reason for the failure. Typically, the reason is either that a timeout
occurred with the external server, or that the billing record no longer exists on the local filesystem. An
SNMP trap is sent for each connection failure.
To disable usage-based billing, use the no cable metering command. This immediately stops the
collection of billing information, except when the billing records are currently being streamed to the
external server. If a billing operation is in progress when you give the no cable metering command, the
system displays the message “CMTS Metering in progress. Ignoring current config.” Wait until the
billing operation is finished and then reenter the no cable metering command.
Note If the show cable metering-status command displays the status of a streaming operation as “success”
but the records were not received on the billing application server, verify that the Cisco CMTS and server
are configured for the same type of communications (non-secure TCP or secure SSL). If the
Cisco CMTS is configured for non-secure TCP and the server is configured for secure SSL, the
Cisco CMTS transmits the billing record successfully, but the server discards all of the data, because it
did not arrive in a secure SSL stream.
Examples The following example shows how to enable usage-based billing for streaming mode, with the CMTS
transmitting the billing records every 60 minutes to the server at the IP address of 10.10.10.37 and TCP
port of 5215, using a secure socket layer (SSL) TCP connection. A secondary external service is also
defined. The CMTS will retry the connection three times before giving up and switching to the secondary
server, as well as sending an SNMPv3 trap to notify the SNMP management system of the failure:
U7246VXR# configure terminal
U7246VXR(config)# cable metering destination 10.10.10.37 5215 10.10.10.41 5215 3 60 secure
U7246VXR(config)#
The following example shows how to enable usage-based billing for streaming mode, with the CMTS
transmitting the billing records every 30 minutes to the server at the IP address of 10.10.10.37 and TCP
port of 8181, using an unencrypted TCP connection. No secondary server is defined. The CMTS will
retry the connection only once before giving up and sending an SNMPv3 trap to notify the SNMP
management system of the failure:
Router# configure terminal
Router(config)# cable metering destination 10.10.10.37 8181 1 30 non-secure
Router(config)#
The following example shows how to enable usage-based billing, using the same configuration as above,
except that the billing records do not include the IP addresses for the CPE devices:
Router# configure terminal
Router(config)# cable metering destination 10.10.10.37 8181 1 30 non-secure
cpe-list-suppress
Router(config)#
The following example shows how to enable usage-based billing, using an unencrypted TCP connection,
including the IP addresses for the CPE devices, and enabling the full-records option:
show cable metering-status Displays information about the most recent usage-based billing
operation.
snmp-server enable traps cable Ensures that the Simple Network Management Protocol (SNMP)
traps are sent for cable-related events.
no cable metering
Syntax Description filesystem File system where the billing record file is written. The filesys parameter
has a maximum length of 25 characters and must specify a valid file system
on the router (such as slot0, disk1, or flash).
Note The system will write the billing records to this file system using a
file name that contains the hostname of the router followed by a
timestamp when the record was written.
cpe-list-suppress (Optional) Eliminates the customer premises equipment (CPE) IP addresses
from the billing records to improve performance.
Note If this option is not selected, a maximum of five CPE IP addresses
are included in the billing record for each cable modem.
flow-aggregate (Optional) Combines all information for an individual cable modem into
one record. Separate counters are maintained for upstream and downstream
traffic, but those counters include all service flows in that direction.
full-records (Optional) Provides information about full service flow (active and idle)
records.
Command Default Usage-based billing is disabled, by default. When usage-based billing is enabled, CPE IP addresses (a
maximum of five) are included in the billing records by default.
Usage Guidelines The cable metering filesystem command enables usage-based filling and configures it for file mode,
where the CMTS writes the billing records to the local file system. The system writes the billing record
to the filesystem specified by this command, using a file name that consists of the router’s hostname
followed by a timestamp for when the file was created.
When the CMTS writes a billing record, it can also optionally send an SNMPv3 trap to notify the billing
application that a billing record is available for pickup. The billing application can then log into the
Cisco CMTS and use the File Transfer Protocol (FTP) or Secure Copy (SCP) to pick up the file.
Note You can enable usage-based billing using either the cable metering filesystem or cable metering
destination command, but not both. If you give these commands twice, the second command will
overwrite the first.
If the CMTS cannot write the billing record to the local filesystem, and if metering traps have been
enabled using the snmp-server enable traps cable metering command, the CMTS sends an SNMP trap
to the SNMP manager describing the reason for the failure. Typically, the reason is either that the disk
is full or that an disk error occurred (such as no PCMCIA card in the slot).
To disable usage-based billing, use the no cable metering command. This immediately stops the
collection of billing information, except when the billing records are currently being written to the local
file system. If a billing operation is in progress when you give the no cable metering command, the
system displays the message “CMTS Metering in progress. Ignoring current config.” Wait until the
billing operation is finished and then reenter the no cable metering command.
Examples The following example shows how to enable usage-based billing, writing the records to a file on the
disk0: device.
U7246VXR# configure terminal
U7246VXR(config)# cable metering filesystem disk0:
U7246VXR(config)#
Note Do not use nvram as the file system. For example, do not use:
Router(config)# cable metering filesystem nvram:
The following example shows how to enable usage-based billing, writing the records to files on the disk2
device on an NPE-G1 processor:
Router# configure terminal
Router(config)# cable metering filesystem disk2:
Router(config)#
The following example shows how to enable usage-based billing, writing the records to files in Flash
Memory. The IP addresses for the CPE devices are not included in the billing records.
Router# configure terminal
Router(config)# cable metering filesystem flash: cpe-list-suppress
Router(config)#
The following example shows how to enable usage-based billing, writing the records to files in Flash
Memory, and enabling the full-records option:
no cable metering
Syntax Description interval Metering data streaming interval in minutes. The valid range is from
2 to 1440 minutes (24 hours).
session session id IP Detail Records (IPDR) session ID. The valid session ID range is from
1 to 255.
flow-aggregate (Optional) Combines all information for an individual cable modem into
one record. Separate counters are maintained for upstream and downstream
traffic, but those counters include all service flows in that direction.
full-records (Optional) Provides information about full service flow (active and idle)
records.
Usage Guidelines The cable metering ipdr command configures how SAMIS data is exported. This command is used for
DOCSIS 2.0 SAMIS schema.
Examples The following example shows how to enable usage-based billing for IPDR, with the billing record
interval set to every 60 minutes with full-records and flow-aggregate options enabled:
Router# configure terminal
Router(config)# cable metering ipdr 60 session 111 full-records flow-aggregate
Router(config)#
no cable metering
Syntax Description session session id Specifies the IPDR session ID. The valid session ID range is from 1 to 255.
type type Specifies the IPDR DOCSIS 3.0 service definition type of metering. The
valid type range is from 1 to 2.
flow-aggregate (Optional) Combines all information for an individual cable modem into
one record. Separate counters are maintained for upstream and downstream
traffic, but those counters include all service flows in that direction.
full-records (Optional) Provides information about full service flow (active and idle)
records.
Usage Guidelines The cable metering ipdr-d3 command configures how the SAMIS data is exported. This command is
used for DOCSIS 3.0 SAMIS schema (including type 1 and type 2).
Examples The following example shows how to enable usage-based billing for IPDR DOCSIS 3.0, with
full-records and flow-aggregate options enabled:
Router# configure terminal
Router(config)# cable metering ipdr-d3 session 111 type 2 full-records flow-aggregate
Router(config)#
Syntax Description interface Specifies the source of the usage based billing packets originated by the
router using the cable metering source-interface command. This is often
used to set the source-interface as the ip address of the loopback interface.
Command Default Usage billing is disabled. When enabled, CPE IP addresses (a maximum of five per cable modem) are
included in the billing records by default.
Usage Guidelines The cable metering source-interface command enables the user to specify the source-interface of the
usage based billing packets. All billing packets are usually automatically assigned a source-interface,
but users using the cable metering source-interface command can set the source-interface to be the ip
address of the loopback interface.
If the user does not specify the source-interface configuration, SAMIS will pick the highest IP address
of the loopback interface as the source interface. If the loopback interface is not there, then SAMIS will
select the highest IP of the physical interface for source interface.
Refer the DDTS for more info CSCek39658.
Note If a loopback interface is specified, the mac address would be that of the management interface in the
docID in the billing packet.
Note The option of specifying the source-interface for metering is available only after the metering mode is
configured.
If the cable metering source-interface command is used when the Usage-Based Billing feature is
operating in the File Mode, the CMTS IP address in the billing packets will be changed to the ip address
of the source-interface as specified through cable metering source-interface command or through
setting the ccmtrCollectionSrcIfIndex object. The mac address in the billing packets' header will also
be changed to the mac address of the source-interface.
If the cable metering source-interface command is used when the Usage-Based Billing feature is
operating in the Streaming Mode, the CMTS IP address in the billing packets, as well as the source IP
address of the billing packets, will be changed to the ip address of the source-interface as specified
through cable metering source-interface command or through setting the ccmtrCollectionSrcIfIndex
object. The mac address in the billing packets' header will also be changed to the mac address of the
source-interface.
When defining the source-interface, the following possible error checks can be performed to determine
if the source-interface that the user has defined is a valid source-interface for metering:
1. Verify that the interface specified is up and has an ip address.
2. Verify that the ip address is in the same subnet/majornet as that of the destination address.
Note Even after performing these error checks, there are no guarantees that the billing packets will be sent out
since the TCP connection may not succeed due to the absence of a physical connection between the
CMTS and the collection server.
Examples The following is an example where the source-interface specified was a loopback interface and it had a
mac-address of 000C31F6F400 and an ip address of 1.100.100.100.
Router# configure terminal
Router(config)# cable metering source-interface loopback 1.100.100.100
<?xmlversion="1.0"encoding="UTF8"?><IPDRDocxmlns="http://www.ipdr.org/namespaces/ipdr"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="DOCSIS-3.5-A.0.xsd" docId="C7B1B20E-0000-0000-0000-000C31F6F400"
creationTime="2006-03-02T18:03:58Z" IPDRRecorderInfo="VXR3" version="3.5-A.0"><IPDR
xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-02T18:03:58Z</IPDRcreationTime><CMTShostn
ame>VXR3</CMTShostname><CMTSipAddress>1.100.100.100</CMTSipAddress><CMTSsysUpTime>185867
</CMTSsysUpTime><CMTScatvIfName>Cable4/0</CMTScatvIfName><CMTScatvIfIndex>16</CMTScatvIfIn
dex><CMTSupIfName>Ca4/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownI
fName>Ca4/0-downstream</CMTSdownIfName><CMmacAddress>00-07-0E-07-0B-0D</CMmacAddress><CMip
Address>11.11.0.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><servic
eIdentifier>0</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>1<
/serviceDirection><serviceOctetsPassed>6225</serviceOctetsPassed><servicePktsPassed>21</se
rvicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>1</serviceS
laDelayPkts><serviceTimeCreated>0</serviceTimeCreated><serviceTimeActive>0</serviceTimeAct
ive></IPDR><IPDR
xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-02T18:03:58Z</IPDRcreationTime><CMTShostn
ame>VXR3</CMTShostname><CMTSipAddress>1.100.100.100</CMTSipAddress><CMTSsysUpTime>185867
</CMTSsysUpTime><CMTScatvIfName>Cable4/0</CMTScatvIfName><CMTScatvIfIndex>16</CMTScatvIfIn
dex><CMTSupIfName>Ca4/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownI
fName>Ca4/0-downstream</CMTSdownIfName><CMmacAddress>00-07-0E-07-0B-0D</CMmacAddress><CMip
Address>11.11.0.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><servic
eIdentifier>0</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>2<
/serviceDirection><serviceOctetsPassed>12300</serviceOctetsPassed><servicePktsPassed>29</s
ervicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>13</servic
eSlaDelayPkts><serviceTimeCreated>0</serviceTimeCreated><serviceTimeActive>0</serviceTimeA
ctive></IPDR><IPDRDoc.End count="2" endTime="2006-03-02T18:03:59Z"/></IPDRDoc>
Router(config)#
The following is an example where the source-interface specified was a loopback interface and it had a
mac-address of 00027D67DC0 and an ip address of 2.90.100.100.
Router# configure terminal
Router(config)# cable metering source-interface loopback 2.90.100.10
Accept 2.90.100.100:42380
<?xmlversion="1.0"encoding="UTF8"?><IPDRDocxmlns="http://www.ipdr.org/namespaces/ipdr"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="DOCSIS-3.5-A.0.xsd" docId="C7B701D1-0000-0000-0000-00027D67DC00"
creationTime="2006-03-06T18:45:37Z" IPDRRecorderInfo="ubr7246-R7427"
version="3.5-A.0"><IPDR
xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-06T18:45:37Z</IPDRcreationTime><CMTShostn
ame>ubr7246-R7427</CMTShostname><CMTSipAddress>2.90.100.100</CMTSipAddress><CMTSsysUpTime>
372172
</CMTSsysUpTime><CMTScatvIfName>Cable3/0</CMTScatvIfName><CMTScatvIfIndex>5</CMTScatvIfInd
ex><CMTSupIfName>Ca3/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownIf
Name>Ca3/0-downstream</CMTSdownIfName><CMmacAddress>00-50-04-F9-EF-88</CMmacAddress><CMipA
ddress>11.40.1.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><service
Identifier>3</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>2</
serviceDirection><serviceOctetsPassed>228392</serviceOctetsPassed><servicePktsPassed>2216<
/servicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>0</servi
ceSlaDelayPkts><serviceTimeCreated>6500</serviceTimeCreated><serviceTimeActive>3648</servi
ceTimeActive></IPDR><IPDR
xsi:type="DOCSIS-Type"><IPDRcreationTime>2006-03-06T18:45:37Z</IPDRcreationTime><CMTShostn
ame>ubr7246-R7427</CMTShostname><CMTSipAddress>2.90.100.100</CMTSipAddress><CMTSsysUpTime>
372172
</CMTSsysUpTime><CMTScatvIfName>Cable3/0</CMTScatvIfName><CMTScatvIfIndex>5</CMTScatvIfInd
ex><CMTSupIfName>Ca3/0-upstream0</CMTSupIfName><CMTSupIfType>129</CMTSupIfType><CMTSdownIf
Name>Ca3/0-downstream</CMTSdownIfName><CMmacAddress>00-50-04-F9-EF-88</CMmacAddress><CMipA
ddress>11.40.1.2</CMipAddress><CMdocsisMode>1.0</CMdocsisMode><Rectype>1</Rectype><service
Identifier>4</serviceIdentifier><serviceClassName></serviceClassName><serviceDirection>1</
serviceDirection><serviceOctetsPassed>200134</serviceOctetsPassed><servicePktsPassed>2197<
/servicePktsPassed><serviceSlaDropPkts>0</serviceSlaDropPkts><serviceSlaDelayPkts>0</servi
ceSlaDelayPkts><serviceTimeCreated>6500</serviceTimeCreated><serviceTimeActive>3648</servi
ceTimeActive></IPDR><IPDRDoc.End count="2" endTime="2006-03-06T18:45:37Z"/></IPDRDoc>
Closing socket 2.90.100.100:42380
Router(config)#
Note The cable modem access-group command is not supported on the Cisco uBR10012 universal
broadband router.
Examples The following example shows the cable modem access-group command assigning access-list 1 to the
CM with the MAC address of abcd.ef01.2345:
Router# cable modem abcd.ef01.2345 access-group 1
Router#
Usage Guidelines This command allows the CMTS administrator to change the downstream frequency for a CM,
overriding the DOCSIS configuration file setting. This command is not applicable on Cisco IOS
Release 12.1(3a)EC.
Examples The following example shows how to change the downstream frequency of the CM having IP address
172.172.172.12 to 570 MHz:
Router# cable modem 172.172.172.12 change-freq 57000000
Router#
Syntax Description n Specifies the configuration file value. Valid range is 1 to 255.
unlimited Specifies the maximum CPE value to be unlimited.
Command Default The max-cpe value provided in the configuration file will be used by the CMTS to limit the number of
hosts connected to a single CM (no cable modem max-cpe).
Examples The following example shows how to override the max-cpe setting in a CM configuration file:
Router(config)# cable modem max-cpe unlimited
Usage Guidelines The CMTS enables up to n number of hosts for a modem.When set to unlimited, or n is larger than the
max-cpe value in the configuration file of a CM, this command overrides the configuration file value.
Note When setting to unlimited or n is greater than the max-cpe value in the configuration file of a CM, the
CM has to control the maximum number of hosts, and the DHCP server has to control the number of IP
addresses assigned to hosts behind a single CM.
Caution Use of this command might open a security hole in the system by enabling denial of service attacks.
Specifically, it might enable a user to obtain a large number of IP addresses, thereby taking down the
entire network, after all the available IP addresses have been reserved by this single user.
Cisco recommends that, if this command is enabled, the number of IP addresses assigned to hosts behind
a single modem be strictly controlled by the DHCP server.
The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all
CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
• cable modem max-hosts—Sets the maximum number of hosts for a particular CM.
• cable max-hosts—Sets the maximum number of hosts for all CMs on a particular cable interface.
• cable modem max-cpe—Sets the maximum number of hosts for all CMs using the Cisco CMTS
router.
The more specific commands override the settings of the less specific commands. For example, if you
use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can
still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note The CMTS assigns the MAX Host value to a cable modem at the time that the cable modem registers
with the CMTS. Changing any of the MAX Host commands affects only cable modems that register after
the change.
Tip For more information on how these commands interact to set the maximum CPE values, see the chapter
Maximum CPE or Host Parameters for the Cisco Cable Modem Termination System in the
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.
Note The “Number of CPES” field in the show cable modem command shows the maximum CPE value for
the CM, not the value for the CMTS that is set by the cable modem max-cpe command.
Command Default 0
Usage Guidelines The Cisco CMTS uses three commands set the maximum number of hosts for a particular CM, for all
CMs on a particular cable interface, or for all CMs using the Cisco CMTS router:
• cable modem max-hosts—Sets the maximum number of hosts for a particular CM.
• cable max-hosts—Sets the maximum number of hosts for all CMs on a particular cable interface.
• cable modem max-cpe—Sets the maximum number of hosts for all CMs using the Cisco CMTS
router.
The more specific commands override the settings of the less specific commands. For example, if you
use the cable modem max-cpe command to set the maximum number of hosts to 2 for all CMs, you can
still use the cable modem max-hosts command to give a particular CM a larger maximum host value.
Note The CMTS assigns the MAX Host value to a cable modem at the time that the cable modem registers
with the CMTS. Changing any of the MAX Host commands affects only cable modems that register after
the change.
Tip For more information on how these commands interact to set the maximum CPE values, see the chapter
Maximum CPE or Host Parameters for the Cisco Cable Modem Termination System in the
Cisco CMTS Feature Guide, available on Cisco.com and the Documentation CD-ROM.
Examples The following example shows sets the CM with the IP address of 172.172.172.12 to a maximum of 40
attached CPE devices:
Router# cable modem 172.172.172.12 max-hosts 40
Usage Guidelines On a Cisco CMTS running DOCSIS 1.0 software, the cable modem qos profile command forces a CM
to use a specific QoS profile.
On a Cisco CMTS running DOCSIS 1.1 software, the cable modem qos profile command temporarily
forces a DOCSIS 1.0 or DOCSIS 1.0+ CM to use a specific QoS profile, without forcing the CM to first
go off-line and re-register. For DOCSIS 1.0+ CMs, this command affects only the primary SID on the
CM.
Note In Cisco IOS Release 12.2(15)BC1, this command has an effect only when the profile that it specifies
and the original QoS profile on the CM have been created already on the Cisco CMTS, using the cable
qos profile command. In Cisco IOS Release 12.2(15)BC2 and later releases, this restriction is removed
and this command can also be used to change the profile for a CM even when it is using a CM-created
QoS profile.
This command does not affect DOCSIS 1.1 CMs, which support dynamic service change messages that
allow the QoS profile to be changed dynamically.
Note This command acts as a toggle. Give the cable modem qos profile command once to enforce a QoS
profile. Give the same command again with the same parameters to cancel the enforcement of that profile
(the CM will return to using its registered profile.)
When the no-persistence option is specified, the QoS profile is not applied when a cable modem reboots.
Instead, the Cisco CMTS allows the cable modem to use the QoS profile that is specified in its DOCSIS
configuration file.
The no-persistence option can be used when initially when identifying potential problem applications
and users. When repeat offenders are identified, the service provider can remove the no-persistence
option, so that these users continue to use the specified QoS profile even if they reboot their cable
modems.
Examples The following example shows how to specify a QoS profile index to a CM:
Router# cable modem qos profile 255
Router#
Syntax Description polling-interval Specifies the delay between each poll that the CMTS makes to collect the CM
statistics. When the CMTS completes one remote-query poll, the CMTS waits this
time period before beginning another poll. Valid range is from 1 to 86,400 seconds,
with a recommended default value of 30 seconds.
community-string Defines the Simple Network Management Protocol (SNMP) community string.
Note If resetting a configured SNMP community string value, first disable the
remote query feature with the no form of this command, then set the new
community string using the cable modem remote-query command when
the polling delays is timed out.
src-ip ip-address Specifies the source IP address for SNMP requests.
Note You should enable the remote-query feature before configuring src-ip
option.
Usage Guidelines To use the remote-query feature, you must configure the CM and Cisco CMTS as follows:
• Configure a read-only SNMP community string on the CM for use with the remote-query feature.
This typically should be a separate community string from the read-write string used to remotely
monitor and configure the CM.
• Configure a matching community string on the Cisco CMTS using the snmp-server community
community-string and snmp-server manager commands.
• Enable the remote-query feature on the Cisco CMTS with the cable modem remote-query
polling-interval community-string command. The polling-interval should be chosen so that the
statistics can be obtained in a timely manner without seriously impacting system performance. Cisco
recommends initially setting the polling-interval to 30 seconds and adjusting that time period as
needed.
Note The polling-interval time period determines only how long the Cisco CMTS waits after
completing one polling cycle before beginning a new polling cycle. It does not indicate how
long the Cisco CMTS spends in each polling cycle, which depends on the number of cable
modems being polled. To calculate the approximate time for a polling cycle, assume 4 to 5
CMs per second (100 to 200 milliseconds per CM). Also take into account the possibility
that one or more cable modems might not respond, with an approximate timeout period of
90 seconds.
You must specify matching community strings for the CM, the snmp-server community
community-string command, and the cable modem remote-query command.
Note You can reissue the cable modem remote-query command to change the polling interval at any time,
and the change becomes effective immediately. However, to change the SNMP community string, you
must first disable remote polling with the no snmp manager and no cable modem remote-query
commands. Then reconfigure the new community string with the snmp-server community
community-string, snmp-server manager, and cable modem remote-query commands.
You must configure the remote-query feature before configuring the scr-ip option.
Tip After enabling the remote-query feature, you can display the collected statistics with the show cable
modem remote-query command. You can also display these statistics by querying the attributes in the
CISCO-DOCS-REMOTE-QUERY-MIB MIB.
Examples The following example illustrates how to set the polling interval to 5 seconds and the SNMP community
string to private:
Router# configure terminal
Router(config)# cable modem remote-query 5 private
Router(config)# snmp-server community private
Router(config)# snmp-server manager
The following example demonstrates how to change the remote-query configuration, by first deleting the
existing configuration and then giving the new configuration:
Router# configure terminal
Router(config)# no cable modem remote-query
Router(config)# no snmp-server manager
Router(config)# cable modem remote-query 10 public
Router(config)# snmp-server community public
Router(config)# snmp-server manager
Syntax Description ip-address Specifies the IP address of the CM to be assigned the named service class.
mac-address Specifies the MAC address of the CM to be assigned the named service class.
name Specifies the name of the QoS service class.
Examples The following example changes the QoS parameter set for the CM with MAC address aaaa.bbbb.cccc to
the service class named “test”:
Router# cable modem aaaa.bbbb.cccc service-class-name test
Syntax Description OUI Specifies the Organizational Unique Identifier (OUI). An OUI is the first 3 octets (3
bytes, 6 hexadecimal digits) of the CM MAC address and typically indicates the vendor for
the CM. The octets can be specified as one string (for example: 000102), or each octet can
be separated by a hyphen, period, or colon (for example: 00-01-02 or 00:01:02 or 00.01.02).
Note You can use either a period or colon as the separator between octets when
manually entering this command, but the command that is written to the running
and startup configuration files will always use a period.
vendor-name (Optional) Specifies an arbitrary string identifying the vendor for this OUI.
Command Default A default database contains approximately 300 OUIs associated with approximately 60 vendor names.
Usage Guidelines The cable modem vendor command allows you to associate an arbitrary string with an OUI to identify
the vendor of the associated CM. The vendor name is then displayed as part of the show cable modem
vendor command.
The show cable modem vendor command uses a default database of approximately 300 OUIs. If the
OUI and vendor are not in that database, the show cable modem vendor command displays the OUI as
the vendor name, but you can use the cable modem vendor command to associate a vendor name with
the new OUI.
If you specify an OUI with the cable modem vendor command that already exists in the OUI database,
the previous value is overwritten with the new value. You can use the default prefix to restore the
original value for an OUI in the default database.
You can also use the no cable modem vendor command to remove the association between an OUI and
a vendor name. The show cable modem vendor command then displays only the OUI as the vendor
name.
Tip The Institute of Electrical and Electronics Engineers (IEEE) is the official issuer of OUI values. The
IEEE OUI web site is at http://standards.ieee.org/regauth/oui/index.shtml.
Examples The following shows several examples of the cable modem vendor command using Cisco OUIs:
Router(config)# cable modem vendor 00:01:42 Cisco
Router(config)# cable modem vendor 00:01:43 Cisco
Router(config)# cable modem vendor 00:01:63 Cisco
Router(config)# cable modem vendor 00:01:64 Cisco
Router(config)# cable modem vendor 00:0A:41 Cisco
Router(config)# cable modem vendor 00:0A:42 Cisco
Router(config)#
The following shows an example of the default cable modem vendor command being used to restore
the original association between Cisco and its company OUI of 00:00:0C. Any previous user-defined
vendor name is deleted from the OUI database.
Router(config)# default cable modem vendor 00000C
The following shows an example of the no cable modem vendor command being used to remove the
association between Cisco and an OUI of 00:0A:42. If any CMs exist with that OUI, the show cable
modem vendor command will display the OUI (“00:0A:42”) as the vendor name.
Router(config)# no cable modem vendor 00:0A:42
Router(config)#
cable modulation-profile
To define a modulation profile for use on the router, use the cable modulation-profile command in
global configuration mode. To remove the entire modulation profile or to reset a default profile to its
default values, use the no form of this command.
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff
pre-len last-cw uw-len
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff
pre-len last-cw uw-len
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff
pre-len last-cw uw-len
cable modulation-profile profile iuc fec-tbytes fec-len burst-len guard-t mod scrambler seed diff
pre-len last-cw uw-len
Syntax Description profile Specifies the modulation profile number. The valid values for the profile number
depend on the cable interface being used and the upstream’s mode of operation.
See Table 6 for a list of valid ranges based on cable interface and modulation type.
In Cisco IOS Release 12.2(15)CX and later releases, you can create a maximum
of 10 profiles for each mode of operation, for a total of 30 profiles. In earlier
software releases, you can create a maximum of 8 profiles only for DOCSIS 1.0
and DOCSIS 1.1 mode.
mix (DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM mix
modulation profile where short and long grant bursts are sent using 16-QAM,
while request, initial ranging, and station maintenance bursts are sent using
QPSK). The burst parameters are set to their default values for each burst type.
mix-high (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default
QPSK/64-QAM modulation profile.
mix-low (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 modes only) Creates a default
QPSK/16-QAM modulation profile.
mix-mid (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a
default QPSK/32-QAM modulation profile.
mix-qam (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a
default 16-QAM/64-QAM modulation profile.
qam-8 (DOCSIS 2.0 A-TDMA mode only) Creates a default 8-QAM modulation profile.
This modulation profile is available in hidden and internal mode only from Cisco
IOS Release 12.2(33)SCC onwards.
qam-16 Creates a default 16-QAM modulation profile.
qam-32 (DOCSIS 2.0 A-TDMA mode only) Creates a default 32-QAM modulation
profile.
This modulation profile is available in hidden and internal mode only from Cisco
IOS Release 12.2(33)SCC onwards.
qam-64 (DOCSIS 2.0 A-TDMA mode only) Creates a default 64-QAM modulation
profile.
This modulation profile is available in hidden and internal mode only from Cisco
IOS Release 12.2(33)SCC onwards.
qpsk Creates a default QPSK modulation profile.
robust-mix (DOCSIS 1.0 and DOCSIS 1.1 mode only) Creates a default QPSK/16-QAM
modulation profile with a longer preamble that is more robust and more able to
deal with noise on the upstream better than the mix profile.
robust-mix-high (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a
default QPSK/64-QAM mixed modulation profile with a longer preamble that is
more robust and more able to deal with noise on the upstream better than the
mix-high profile.
robust-mix-low (DOCSIS 2.0 A-TDMA mode only) Creates a default QPSK/16-QAM
modulation profile with a longer preamble that is more robust and better able to
deal with noise on the upstream than the mix-low profile.
robust-mix-mid (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only) Creates a
default QPSK/32-QAM modulation profile with a longer preamble that is more
robust and better able to deal with noise on the upstream than the mix-mid
profile.
robust-mix-qam (DOCSIS 1.x/2.0 mixed mode only) Creates a default 16-QAM/64-QAM mixed
modulation profile with a longer preamble that is more robust and better able to
deal with noise on the upstream than the mix-qam profile.
iuc Interval usage code. Valid entries depend on the mode of operation:
• If the upstream is configured for DOCSIS 1.0 and DOCSIS 1.1 modulation
profiles, the valid values are initial, long, request, reqdata, short, or
station.
• If the upstream is configured for DOCSIS 1.x and DOCSIS 2.0 mixed
modulation profiles, the valid values are a-long, a-short, a-ugs, initial, long,
request, reqdata, short, or station.
• If the upstream is configured for DOCSIS 2.0 A-TDMA modulation profiles,
the valid values are a-long, a-short, a-ugs, initial, long, request, reqdata,
short, or station.
The reqdata burst type is included as a placeholder for scripts that might
reference it, but the DOCSIS MAC scheduler on the Cisco CMTS does not use
this type of burst.
When you are using the initial and station bursts for DOCSIS 2.0 A-TDMA
mode, qam-8, qam-32, and qam-64 modulation profiles are available in hidden
mode only.
preamble (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and
a-short options) Specifies the preamble format. Valid values are qpsk0 and
qpsk1.
rs-interleave-depth (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and
a-short options) Specifies the RS interleave depth. The valid range is from 0 to
114.
rs-interleave-block (DOCSIS 1.x/2.0 mixed and DOCSIS 2.0 A-TDMA modes only, for a-long and
a-short options) Specifies the RS interleave block size. The valid range is from
18 to 2048.
fec-tbytes The number of bytes that can be corrected per FEC code word. For DOCSIS 1.0
and DOCSIS 1.1 mode, valid values are from 0 to 10 (decimal), where 0 means
no FEC. For DOCSIS 2.0 A-TDMA mode, the valid values are from 0 to 16
(decimal), where 0 means no FEC.
fec-len FEC code-word length. Valid values are from 16 to 253.
burst-len Maximum burst length in minislots. Valid values are from 0 to 255, where 0
means no limit.
guard-t Guard time in symbols. The time between successive bursts, with a range from 22
to 255. (In Cisco IOS Release 12.2(15)BC2 and earlier releases, the minimum
guard time was 0 symbols, but we do not recommend using a guard time smaller
than 22 symbols.)
mod Modulation. Valid entries are 16qam and qpsk for DOCSIS 1.0 and DOCSIS 1.1
upstreams. Valid entries are 8qam, 16qam, 32qam, 64qam, and qpsk for
DOCSIS 2.0 upstreams.
The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and
internal modes only from Cisco IOS Release 12.2(33)SCC onwards.
scrambler Enable or disable scrambler. Valid entries are scrambler and no-scrambler.
seed (Required if scrambler option used) Scrambler seed in hexadecimal format.
Valid values are from 0x0 to 0x7FFF.
diff Enable or disable differential encoding. Valid entries are diff and no-diff.
In DOCSIS 2.0 mode, differential encoding cannot be enabled for the 8-QAM,
32-QAM, and 64-QAM modulations.
The qam-8, qam-32, and qam-64 modulation profiles are available in hidden and
internal modes only from Cisco IOS Release 12.2(33)SCC onwards.
pre-len Preamble length in bits. Valid values are from 2 to 256.
last-cw Handling of FEC for last code word. Valid entries are fixed for fixed code-word
length and shortened for shortened last code word.
uw-len Upstream unique word length. Enter uw8 for 8-bit unique code words or uw16
for 16-bit unique code words.
Command Default Modulation profile 1 is defined as a qpsk Time Division Multiple Access (TDMA) profile.
In Cisco IOS Release 12.2(15)CX, Release 12.2(15)BC2 and later releases, additional modulation
profiles are defined as the default mixed TDMA/A-TDMA profile and the default Advanced TDMA
(A-TDMA) profile. See Table 6 for a list of valid ranges based on cable interface and modulation type.
Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA. Support for the
Cisco uBR7225VXR router was added.
12.2(33)SCC This command was modified. Moved qam-8, qam-32, and qam-64 options to hidden
and internal mode only. Support was added for Synchronous Code Division Multiple
Access (S-CDMA) modulation profiles.
Usage Guidelines A modulation profile is a collection of at least six burst profiles that are sent out in an upstream channel
descriptor (UCD) message to configure a modem’s transmit parameters.
You can use the no cable modulation-profile command to remove all modulation profiles except the
default modulation profiles (1, 21, 41, 101, 121, 201, 221, 241, and 321, depending on the cable interface
line cards being used). In the case of the default modulation profiles, the no cable modulation-profile
command resets the default profile to its default values.
We recommend that you use the predefined profiles instead of manually specifying the individual bursts
for a modulation profile. The predefined profiles are optimized for the default of 32 symbols per minislot
for each particular modulation scheme. The robust predefined profiles use a longer preamble for better
handling of noise on the upstream, but at the cost of consuming more PHY layer bandwidth than the
other non-robust profiles.
If you want to manually specify the individual bursts, enter a line with all parameters for each upstream
burst type. Then repeat this command for each burst type, which also must be fully specified. A profile
with incomplete or missing bursts can cause unreliable operation or loss of modem connectivity.
Caution Changes to modulation profiles causes changes to the physical layer. Because changing physical layer
characteristics affects router performance and function, this task should be reserved for expert users who
have a thorough understanding of DOCSIS systems and how each parameter affects the network.
Note The reqdata burst type is included as a placeholder for SNMP scripts that might reference it, but it has
no effect. You can use this command (and SNMP commands) to specify the reqdata types, but the
DOCSIS MAC scheduler on the Cisco CMTS does not use this type of burst.
From Cisco IOS Release 12.2(33)SCC onwards, the qam-8, qam-32, and qam-64 modulation profiles
are available in hidden and internal modes only. When you are using the initial and station bursts for
DOCSIS 2.0 A-TDMA mode, qam-8, qam-32, and qam-64 modulation profiles are available in hidden
mode only. However, these modulation profiles are available for a-long, a-short, a-ugs, long, request,
reqdata, and short.
Cable Interface DOCSIS 1.X (TDMA) Mixed DOCSIS 1.X/2.0 DOCSIS 2.0 (A-TDMA) DOCSIS 2.0 (S-CDMA)
1
Cisco uBR7100 series 1 to 10 , default=1 N/A N/A N/A
Cisco uBR-MC16C 1 to 10, default=1 N/A N/A N/A
Cisco uBR-MC16S 1 to 10, default=1 N/A N/A N/A
Cisco uBR-MC28C 1 to 10, default=1 N/A N/A N/A
Cisco uBR-MC5X20S, 21 to 30, default=21 121 to 130, 221 to 230, default=221 321 to 330 (default is
Cisco uBR-MC5X20U, default=121 321)
Cisco uBR-MC5X20H
Cisco uBR-MC16U/X, 41 to 50, default=41 141 to 150, 241 to 250, default=241 N/A
Cisco uBR-MC28U/X default=141
1. Only 8 modulation profiles are supported in Cisco IOS software releases before 12.2(15)BC1, so in these releases the valid range is from 1 to 8.
Note Do not use the qam-16 mode unless you have verified that your cable plant can support that modulation
profile. Most cable plants should instead use the qpsk or mix modulation profile for the primary profile.
Caution Turning the scrambler off can cause packet loss and is used only in lab testing environments.
Errors or incompatible configurations in the burst profiles cause cable modems to drop connectivity, to
drop short or long data packets, or to fail to connect to the network. It is possible to build a burst profile
set for which no implementation of a DOCSIS receiver is capable of receiving the modem’s
transmission.
Data rates of 160 Ksymbol/sec and 2560 Ksymbol/sec are highly sensitive to unique word length,
preamble length, and FEC sizing. Incorrect choices for these values can cause poor, or no, connectivity
at these symbol rates.
Examples The following example shows how to create a mixed modulation profile, using 16-QAM for the short
and long grant bursts and QPSK for the request, initial ranging, and station maintenance bursts. The burst
parameters are set to their default values for each burst type.
Router(config)# cable modulation-profile 8 mix
Router(config)# exit
Mod IUC Type Preamb Diff FEC FEC Scrambl Max Guard Last Scrambl Preamb
length enco T CW seed B time CW offset
BYTES size size size short
8 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 0
8 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0
8 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0
8 short qam 144 no 0x6 0x4B 0x152 6 8 yes yes 0
8 long qam 160 no 0x8 0xDC 0x152 0 8 yes yes 0
Router#
Note The above example shows the default values for the burst parameters. The main differences in the default
values between 16-QAM and QPSK bursts are in the Type and Preamble Length fields.
The following example shows how to define the burst parameters for profile 2 with the following
parameters: 0 fec-tbytes, 16 kbytes fec-len, a burst-len of 1, a guard time of 8, a mod value of qpsk,
scrambler enabled with a seed value of 152, differential encoding disabled, a preamble length of 64 bits,
a fixed code-word length, and 8-bit unique words for upstream unique word length.
Router(config)# cable modulation-profile 2 request 0 16 1 8 qpsk scrambler 152 no-diff 64
fixed uw8
Router(config)# cable modulation-profile 2 reqdata 0 16 1 8 qpsk scrambler 152 no-diff 64
fixed uw8
Router(config)# cable modulation-profile 2 initial 5 34 0 48 qpsk scrambler 152 no-diff
128 fixed uw16
Router(config)# cable modulation-profile 2 station 5 34 0 48 qpsk scrambler 152 no-diff
128 fixed uw16
Router(config)# cable modulation-profile 2 short 6 75 6 8 16qam scrambler 152 no-diff 144
fixed uw8
Router(config)# cable modulation-profile 2 long 8 220 0 8 16qam scrambler 152 no-diff 160
fixed uw8
Note You must create all of the bursts (request, initial, station, short and long) for this modulation profile,
using the cable modulation-profile command. The reqdata burst is optional.
The following example shows an example of a DOCSIS 1.X/DOCSIS 2.0 mixed modulation profile:
Router# configure terminal
Router(config)# cable modulation-profile 142 request 0 16 0 8 qpsk scrambler 152 no-diff
64 fixed uw8
The following example shows an example of a DOCSIS 2.0 A-TDMA modulation profile:
Router# configure terminal
Router(config)# cable modulation-profile 242 request qpsk0 0 0 0 16 0 8 qpsk scrambler 152
no-diff 64 fixed uw8
Router(config)# cable modulation-profile 242 initial qpsk0 0 0 5 34 0 48 qpsk scrambler
152 no-diff 32 fixed uw16
Router(config)# cable modulation-profile 242 station qpsk0 0 0 5 34 0 48 qpsk scrambler
152 no-diff 32 fixed uw16
Router(config)# cable modulation-profile 242 short qpsk0 0 0 5 75 6 8 qpsk scrambler 152
no-diff 72 shortened uw8
Router(config)# cable modulation-profile 242 long qpsk0 0 0 8 220 0 8 qpsk scrambler 152
no-diff 80 shortened uw8
Router(config)# cable modulation-profile 242 a-short qpsk0 0 18 5 99 10 8 64qam scrambler
152 no-diff 128 shortened uw8
Router(config)# cable modulation-profile 242 a-long qpsk0 0 18 15 200 0 8 64qam scrambler
152 no-diff 128 shortened uw8
Router(config)#
The following example shows an example of a DOCSIS 2.0 S-CDMA modulation profile:
Router# configure terminal
Router(config)# cable modulation-profile 324 request 0 16 10 16qam scrambler 152 no-diff
64 fixed qpsk0 spreader 12 12 no-tcm
Router(config)# cable modulation-profile 324 initial 0 16 10 16qam scrambler 152 no-diff
64 fixed qpsk0 off-spreader 12 12 no-tcm
Router(config)# cable modulation-profile 324 station 0 16 10 16qam scrambler 152 no-diff
64 fixed qpsk0 off-spreader 12 12 no-tcm
Router(config)# cable modulation-profile 324 a-short 0 16 10 16qam scrambler 152 no-diff
64 fixed qpsk0 off-spreader 12 12 no-tcm
Router(config)# cable modulation-profile 324 a-long 16 10 16qam scrambler 152 no-diff 64
fixed qpsk0 off-spreader 12 12 no-tcm
Router(config)# cable modulation-profile 324 a-ugs 16 10 16qam scrambler 152 no-diff 64
fixed qpsk0 off-spreader 12 12 no-tcm
Router(config)#
See the show cable modulation-profile command for a description of the output display fields.
Syntax Description profile Modulation profile number. The valid values for the profile number range from 1
to 400.
Usage Guidelines Using the global modulation profile scheme, you can assign any number between 1 to 400 to any
modulation profiles. It eliminates the number space restriction and increases the number of modulation
profiles that can be created per DOCSIS mode. The global modulation profile mode allows you to create
and configure DOCSIS 3.0 channel type 4SR (scdma-d3). When an upstream DOCSIS mode is changed
to scdma-d3 , it is initially assigned to the system created default modulation profile as shown in Table 7.
Note Though you can assign any number between 1 to 400 to any modulation profile, the default modulation
profile number assigned to an upstream channel for a given channel type will remain the same. That is,
modulation profile numbers 21, 121, 221, 321, and 381 will be applicable for TDMA, mixed, A-TDMA,
S-CDMA, and DOCSIS 3.0 S-CDMA channel types.
All the existing and previously defined modulation profiles are converted to the new format. However,
all the newly created modulation profiles, which are outside of the legacy number space range, are lost
when you revert to the legacy modulation profile.
Note The default profiles cannot be deleted. Using the no cable modulation global command on the default
profiles resets them to their original, default values.
Examples The following example shows how to create a global modulation profile scheme:
Router(config)# cable modulation-profile global-scheme
cable monitor
To enable the forwarding of selected packets on the cable interface to an external LAN analyzer, use the
cable monitor command in cable interface configuration mode. To disable this function, use the no form
of this command.
no cable monitor
Syntax Description incoming Forwards only packets being received on the upstream.
outbound Forwards only packets being transmitted on the downstream.
timestamp Enables packet time-stamping by appending a four-byte value to the
forwarded packets. The timestamp value is in hundredths of a second.
interface interface Specifies the WAN interface to which an external LAN analyzer is
attached, and to which packets should be forwarded. You can forward
packets only to an Ethernet, Fast Ethernet, Gigabit Ethernet, or Ten Gigabit
Ethernet interface.
access-list name| number Specifies the IP access list name or number (1 to 2699).
mac-address address Specifies the MAC address of the device being monitored.
sid sid-number Specifies the service ID for the packets that should be forwarded
(1 to 16384).
Note This option is supported only in Cisco IOS releases that support
DOCSIS 1.1 operations.
packet-type (Optional) Specifies whether data or MAC packets are forwarded.
data docsis Specifies that complete DOCSIS packets (both the DOCSIS header and the
complete Ethernet frame) should be forwarded.
Note Enabling this option can result in %LINK-4-TOOBIG messages
being generated if the original Ethernet frame is at or near the
maximum Ethernet size of 1500 bytes. This is because this option
adds additional bytes (the DOCSIS header) to the Ethernet frame,
which can result in a total frame size that exceeds the maximum
size that is allowed for standard Ethernet frames.
data ethernet Specifies that the DOCSIS header should be stripped from the packet and
that only the Ethernet frame should be forwarded.
mac [type type] Specifies that only DOCSIS MAC-layer packets should be forwarded. If
you are using the sid option, you can also optionally specify the type
option with one of the following keywords to indicate that only the specific
type of MAC-layer traffic should be forwarded:
dsa—Dynamic service addition
dsc—Dynamic service change
dsd—Dynamic service deletion
map-grant—Grants
map-req—Requests
Command Default Both upstream (incoming) and downstream (outbound) traffic is forwarded.
Usage Guidelines The cable monitor command allows an external LAN packet analyzer to monitor inbound and outbound
data packets for specific types of traffic between the Cisco CMTS and the CMs on a cable interface. This
feature enables the CMTS administrator to analyze traffic problems with customer data exchanges.
The interface used for forwarding packets can be used only for the external LAN analyzer; and cannot
be used for other purposes. For complete information on configuring and using this feature, see the
Cable Monitor for the Cisco CMTS chapter in the Cisco CMTS Feature Guide or the Cisco IOS CMTS
Cable Software Configuration Guide, available on Cisco.com and the Customer Documentation
CD-ROM.
Tip One possible software utility you can use for decoding the DOCSIS MAC frames is release 0.9.6 or later
of the Ethereal software, which is available for Windows and Unix systems at http://www.ethereal.com.
For additional information about the Cable Monitor feature, and enhanced support for broadband
processing engines and other DOCSIS support, refer to the following document on Cisco.com:
• Cable Monitor and Intercept Features on the Cisco CMTS Routers
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_mon_intrcpt_ps2209_TSD_
Products_Configuration_Guide_Chapter.html
Examples The following example shows how to configure the Cisco CMTS so that it monitors incoming
MAC-layer packets for the CM with the MAC address of 0123.4567.89ab and forwards copies of the
packets to the LAN analyzer on the Ethernet interface in slot 1, port 2:
The following example shows how to configure a Cisco CMTS running DOCSIS 1.1 software so that it
monitors incoming MAC-layer packets of type DSA for the CM identified by SID 173 and forwards
copies of the packets to the LAN analyzer on the Ethernet interface in slot 1, port 2:
Router(config-if)# cable monitor incoming interface e1/2 sid 173 packet-type mac type dsa
cable mrc-mode
To enable Multiple Receive Channel (MRC) mode for a Media Access Control (MAC) interface during
or after the cable modem (CM) registration, use the cable mrc-mode command in cable interface
configuration mode. To disable this configuration, use the no form of this command.
cable mrc-mode
no cable mrc-mode
Command Default The MRC mode is enabled by default on a downstream bonding capable cable interface line card.
Usage Guidelines When you enable or disable the MRC mode, cable modems switch the operation to or from the MRC
mode only after the reinitialization of cable modems. You cannot enable the MRC mode on a
non-upstream bonding capable cable interface line card.
Examples The following example shows how to enable the MRC mode for a MAC interface:
Router# configure terminal
Router(config)# interface cable 7/1/0
Router(config-if)# cable mrc-mode
cable mtc-mode
To enable Multiple Transmit Channel (MTC) mode for a Media Access Control (MAC) interface during
or after the cable modem (CM) registration, use the cable mtc-mode command in cable interface
configuration mode. To disable this configuration, use the no form of this command.
Syntax Description required-attribute Specifies the per-CM basis MTC mode configuration.
Command Default The MTC mode is enabled by default with the required attribute. With this default configuration, the
Cisco CMTS router enables the MTC mode on a per-CM basis by looking at the configuration file of
each cable modem.
Usage Guidelines Multiple Transmit Channel mode is a CM capability that enables CMs to send upstream traffic on
multiple upstream channels. You can enable the MTC mode on a cable interface line card in two ways:
• MTC mode on a per-CM basis—By default, the MTC mode is enabled with the required attribute.
With this default configuration, the Cisco CMTS router enables MTC mode on a per-CM basis by
looking at each CM’s configuration file. When the CM configuration file has the bonded-bit (bit-31)
on in type-length-value (TLV) 43.9.3 (cable modem upstream required attribute mask), the
Cisco CMTS router lets the CM come online in the MTC mode. If the CM configuration file does
not have the bonded-bit on, the CM comes online in non-MTC mode.
• MTC mode for all cable modems in a MAC domain—The MTC mode for all cable modems in a
MAC domain is disabled by default on an upstream bonding capable cable interface line card. You
can enable the MTC mode for all cable modems in a MAC domain using the cable mtc-mode
command in cable interface configuration mode.
Note You do not have to use the required-attribute keyword to enable the MTC mode for all cable modems
in a MAC domain. You can use the no form of this command with the required-attribute keyword to
disable the default per-CM basis configuration.
You cannot enable the MTC mode on a non-upstream bonding capable cable interface line card.
Examples The following example shows how to enable the MTC mode for all cable modems in a MAC domain:
Router# configure terminal
Router(config)# interface cable 7/1/0
Router(config-if)# cable mtc-mode
Usage Guidelines This command is used to enable cable multicast authorization profile feature and defines the default
value. However, it does not define the actual authorization files.
Examples The following example shows how to enable the default multicast authorization profile:
Router(config)# cable multicast auth enable default-action deny max-sessions 10
Syntax Description name Specifies the name of the authorization profile to be used.
default (Optional) Specifies that the profile name should be treated as the default
profile.
Usage Guidelines This command defines a cable multicast authorization profile, and optionally sets it as the default profile.
If the default keyword is not used while modifying the profile, the profile is automatically converted to
a non-default profile. Similarly, if the default keyword is added while modifying a profile, the profile is
treated as a default profile.
Examples The following example shows how to use the selected multicast authorization profile:
Router(config)# cable multicast auth profile-name GOLD default
Syntax Description number Specifies the number of a specific cable multicast QoS group encryption
profile. The valid range is 1–255.
algorithm 56bit-des Specifies that the data encryption standard (DES) is 56 bits.
Usage Guidelines To apply encryption rules to a cable multicast QoS group, you must first enable and identify an
encryption group.
Examples The following example enables encryption, identifies encryption group 12, and applies the encryption
rule to QoS group 2:
Router(config)# cable multicast group-encryption 12 algorithm 56bit-des
Router(config)# cable multicast qos group 2 priority 7 global
Router(config-mqos)# group-encryption 12
Syntax Description number Specifies the QoS profile number for the cable multicast QoS group. The
valid range is 1–255. If a multicast group does not match the group QoS
classifiers, a default group-QoS option is applied to the multicast flow.
scn service-class-name Specifies a service class name for the QoS profile.
control Specifies the type of control to the service flow.
single Specifies that a separate service flow is created for each session.
aggregate Specifies that service flows are grouped for sessions in the same multicast
QoS group.
limit max-sessions (Optional) Specifies the Internet Group Management Protocol (IGMP)
session limit for aggregate service flows. The valid range is 1–255.
Command Default The QoS profile for a QoS group is not enabled.
Usage Guidelines If a QoS profile number is not specified, a default QoS profile is applied. The default group QoS
configuration creates a default multicast service flow for each cable interface that is used when a
multicast session does not match any classifiers of a GC on the interface.
Examples The following example configures QoS profile 5 with a service name of name1 and a control of single
to indicate that a separate service flow is created for each session. QoS profile 5 is then assigned to QoS
group 2.
Router(config)# cable multicast group-qos 5 scn name1 control single
Router(config)# cable multicast qos group 2 priority 7 global
Router(config-mqos)# cable multicast group-qos 5
Syntax Description scn service-class-name Specifies a service class name for the QoS profile.
aggregate Specifies that service flows are grouped for sessions in the same MQoS
group.
Usage Guidelines If you configure the service class name with the DOCSIS Setup Gateway (DSG) tunnel when no default
MQoS exists, the configuration is rejected and you are prompted to configure the default MQoS.
The CMTS selects the primary downstream channel to forward the multicast traffic when the default
MQoS is configured and there is no matching MQoS group configuration. Otherwise, the wideband
interface is used to forward the multicast traffic.
Note If you configure or unconfigure the default MQoS while the CMTS is sending multicast traffic, duplicate
traffic is generated for approximately 3 minutes (or 3 times the query interval).
Examples The following example configures the default MQoS profile with the service class name name1.
Router(config)# cable multicast group-qos default scn name1 aggregate
Command Description
show interface bundle Displays multicast session information for a specific virtual cable bundle.
multicast-sessions
show interface cable Displays multicast session information for a specific cable interface.
multicast-sessions
Syntax Description id Specifies the number of the cable multicast QoS group. The valid range is
1–255.
priority value Specifies the priority of the cable multicast QoS group. The valid range is
1–255.
global (Optional) Specifies that the multicast QoS group configuration is applied to
all cable interfaces.
Usage Guidelines You must configure a group QoS profile (cable multicast group-qos) and a group encryption profile
(cable multicast group-encryption) before you configure a cable multicast QoS group.
Examples The following example specifies multicast QoS group 2 with a priority of 6 and global application.
Application ID, group encryption, group QoS, session range, ToS, and VRF options are configured for
QoS group 2.
Router(config)# cable multicast qos group 2 priority 6 global
Router(config-mqos)# application-id 44
Router(config-mqos)# group-encryption 4
Router(config-mqos)# group-qos 3
Router(config-mqos)# session-range 224.10.10.01 255.255.255.254
Router(config-mqos)# tos 1 6 15
Router(config-mqos)# vrf name1
New Commands
Modified Commands
cable power
To manually power a cable interface line card on or off on a Cisco uBR10012 router, use the cable power
command in privileged EXEC mode.
Syntax Description on Turns on power to the specified cable interface line card.
off Turns off power to the specified cable interface line card. Power to that
particular card slot remains off until power is turned back on using the
cable power on version of this command.
slot/card Specifies the slot and card number for the desired cable interface card
number. The valid range for slot is 5 to 8 and for card is 0 or 1.
Defaults Cable interface line cards are powered on by default when the card is inserted into the chassis slot.
Usage Guidelines This command is typically not used during normal operations, but it can be used for lab, diagnostic, and
troubleshooting purposes. For example, using this command to first power off and then power on a card
is functionally equivalent to performing an online insertion and removal (OIR) of the card.
Be aware of the following points when using this command:
• Using the cable power off command is functionally equivalent to disconnect the cables from the
card’s upstream and downstream connectors and then removing the card from the chassis. When you
use this command to turn off power to a card, the output for the show interface cable command for
that card will display the message “Hardware is not present.”
Note You can also use the LC Power off Status Reg and Line Card Presence Status Reg fields in
the show controllers clock-reference command to determine whether a cable interface line
card is actually present in the chassis and whether it has been powered on or off.
• Powering off a cable interface line card automatically drops all sessions with the cable modems that
are using that card’s upstreams and downstreams. Do not use this command on a live network unless
this is what you intend.
• All cards are powered on when you upgrade to a new software image for the Cisco uBR10012 router,
even if a card had previously been powered off using the cable power off command.
• You can turn power both on and off to a cable interface line card slot, even if a card is not physically
present in the slot.
• This is the only CLI command that actually powers off a card. The hw module reset command
appears to perform a similar function, but it performs only the equivalent of issuing the shutdown
and no shutdown commands on the card.
• When power is turned off for a cable interface line card, the power to that card slot will remain off
until the cable power on command is used to turn the power back on. If you insert a cable interface
card in to a slot that had been previously powered down, you will have to use the cable power on
command to turn on power before being able to use the card.
• This command requires that a working TCC+ card be present because the TCC+ card controls and
monitors the operation of the cable interface line cards. In Cisco IOS Release 12.2(8)BC1 and later,
this command is disabled if a working TCC+ card is not present in the router.
Note The Cisco uBR10012 router requires a working TCC+ card for normal operations. Using the
router without a working TCC+ card is not a supported configuration.
Examples The following example shows how to power off the first cable interface card in a Cisco uBR10012
chassis (card 5, slot 0). It also shows the output from the show interface cable command, with a line
that indicates that the hardware is not present.
router# cable power off 5/0
Line Card 5/0 is POWERED OFF
router# show int c5/0/0
Cable5/0/0 is down, line protocol is down
Hardware is not present
Hardware is UBR10012 CLC, address is 0005.00e0.2f14 (bia 0005.00e0.2f14)
Internet address is 10.20.42.1/24
MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec,
reliability 255/255, txload 1/255, rxload 1/255
...
router#
Note The show interface cable command will not display output for a card that is not physically present, so
if you can use the show interface cable command but it indicates that the hardware is not present, this
usually means that power to the card has been turned off using the cable power off command.
The following example shows the error message that results when you attempt to power on or off a cable
interface card that is not physically present in the chassis:
router# cable power off 6/1
Line Card 6/1 is not present
router#
Note Power is still turned on or off to a cable interface line card slot, even when the card is not physically
present in that slot.
Syntax Description modem mac-addr Excludes the cable modem with the specified MAC address from
pre-equalization during cable modem registration.
oui id Excludes the specified Organizational Unique Identifier (OUI) from
pre-equalization during cable modem registration.
Command Default Pre-equalization is disabled by default on a Cisco CMTS router, and for cable modems that have a valid
and operational DOCSIS configuration file.
Usage Guidelines Use the cable pre-equalization exclude command to disable pre-equalization for DOCSIS 1.1 CMs that
claim pre-equalization support but do not properly implement pre-equalization functions.
To enable pre-equalization, use the cable upstream equalization-coefficient interface configuration
command. Pre-equalization starts when a cable modem that supports DOCSIS 1.1 or above sends the
CMTS router a ranging request message indicating that pre-equalization is possible.
The following example of output from the show cable modem verbose command shows which modems
are indicating pre-equalizer support during the DOCSIS registration process. In this example, the first
two modems are capable of pre-equalization support, and the last two modems support DOCSIS 1.0,
which does not support pre-equalization. You do not need to use the cable pre-equalization exclude
command for DOCSIS 1.0 CMs.
Router# show cable modem verbose | include MAC Address|Equalizer
MAC Address : 0019.474a.c4b0
Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24}
MAC Address : 0019.474a.c498
Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24}
MAC Address : 0020.40dc.4ce4
Transmit Equalizer Support : {Taps/Symbol= 0, Num of Taps= 0}
MAC Address : 0020.4077.21a0
Exclusion is supported for a specified DOCSIS 1.1 cable modem, or for a specified OUI value for the
entire interface. Removing the cable pre-equalization exclude configuration returns the cable modem
or interface to normal pre-equalization processes during cable modem registration.
Examples The following example configures pre-equalization to be excluded for the specified cable modem.
Pre-equalization data is not sent for the corresponding cable modem:
Router(config)# cable pre-equalization exclude modem 1111.2222.3333
The following example configures pre-equalization to be excluded for the specified OUI value of the
entire interface. Pre-equalization data is not sent for the corresponding OUI value of the entire interface:
Router(config)# cable pre-equalization exclude oui 00.09.04
The following series of commands configures pre-equalization on the Cisco uBR10012 router with
MC5X20U BPEs. On the PRE Console, configure the following commands.
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable pre-equalization exclude oui 00.09.04
Router(config)# end
Router# show run
Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04
Router#
On the line card console for the same Cisco uBR10012 router, verify the configuration with the following
command:
Linecard# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04
The following series of commands configures pre-equalization on the Cisco uBR72436VXR router with
MC28U cable interface line cards. On the Network Processing Engine (NPE) console, configure and
verify with the following commands.
Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable pre-equalization exclude oui 00.09.24
Router(config)# end
Router#show run
02:58:10: %SYS-5-CONFIG_I: Configured from console by consolen
Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24
On the line card console for the same Cisco uBR7246VXR router, verify the configuration with the
following command:
Linecard# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24
After either of these exclusion methods for pre-equalization are configured, you can verify that all
ranging messages do not include pre-equalization data. Use the following debug commands in global
configuration mode:
• debug cable range
• debug cable interface cx/x/x mac-addr
Verify the ranging message for the non-excluded cable modems include pre-equalization data, and for
the excluded cable modems, the ranging messages do not include such data.
The following example removes pre-equalization exclusion for the specified OUI and interface. This
results in the cable modem or OUI to return to normal pre-equalization functions. Ranging messages
resume sending pre-equalization data.
Router(config)# no cable pre-equalization exclude {modem mac-addr | oui id}
You can verify removal of this feature using the debug cable interface command.
Syntax Description all Preserves all primary service flow traffic counters when a DOCSIS 1.1-provisioned CM
goes offline. This includes the counters displayed by CLI commands and counters that are
obtained through SNMP requests.
snmp-only Preserves only the primary service flow traffic counters that are obtained through SNMP
requests. The counters displayed by CLI commands are reset to zero when a DOCSIS
1.1-provisioned CM goes offline.
Command Default Primary service flow traffic counters are not preserved after a DOCSIS 1.1-provisioned CM goes offline
(no cable primary-sflow-qos11 keep). Service-flow information is always preserved for
DOCSIS 1.0-provisioned CMs, regardless of the configuration of this command.
Usage Guidelines By default, when a CM that is provisioned for DOCSIS 1.1 quality of service (QoS) service flows goes
offline, the CMTS deletes all service flow information, including traffic counters, that correspond to that
CM. The cable primary-sflow-qos11 keep command preserves the service flow traffic counters after a
DOCSIS 1.1-provisioned CM goes offline and then comes back online. This allows service providers to
track the total usage of CMs over a period of time, regardless of the number of times the CMs go offline
and reboot.
Note This command affects only CMs that are provisioned for DOCSIS 1.1 operations and that are currently
online all cable interfaces on the Cisco CMTS. Information is not preserved for DOCSIS
1.1-provisioned CMs that went offline before this command was given. The service-flow information for
CMs that are provisioned for DOCSIS 1.0 operations is always preserved, regardless of how this
command is configured.
Examples The following example shows how to preserve both the CLI and SNMP service flow counters when a
DOCSIS 1.1-provisioned CM goes offline:
Router(config)# cable primary-sflow-qos11 keep all
Router(config)#
The following example shows how to preserve only the SNMP-based service flow counters when a
DOCSIS 1.1-provisioned CM goes offline. The CLI-based counters are still reset to zero when this CM
goes offline.
Router(config)# cable primary-sflow-qos11 keep snmp-only
Router(config)#
The following example shows how to disable this command and return to the default behavior, which is
to reset all CLI-based and SNMP-based counters when a DOCSIS 1.1-provisioned CM goes offline.
Router(config)# no cable primary-sflow-qos11 keep
Router(config)#
cable privacy
To enable and configure BPI or BPI+ encryption, use the cable privacy command in cable interface
configuration mode. To disable privacy or to remove a particular configuration, use the no form of this
command.
Syntax Description accept-self-signed-certificate (Optional) Allows cable modems to register using self-signed
manufacturer certificates, as opposed to a manufacturer certificate
that is chained to the DOCSIS root certificate.
authenticate-modem (Optional) Uses AAA protocols in conjunction with BPI to
authenticate all CMs.
authorize-multicast (Optional) Uses AAA protocols with baseline privacy interface (BPI)
to authorize all multicast stream (IGMP) join requests.
mandatory (Optional) Requires baseline privacy be active for all CMs with
BPI/BPI+ enabled in their DOCSIS configuration files or the CMs are
forced to go offline.
If a CM does not have BPI enabled in its DOCSIS configuration file,
it will be allowed online without BPI.
oaep-support (Optional) Enables Optimal Asymmetric Encryption Padding (OAEP)
BPI+ encryption.
dsx-support (Optional) Enables encryption for dynamic services SIDs.
retain-failed-certificates (Optional) Allows to retain failed certificates.
skip-validity-period (Optional) Enables to skip certificate validity period.
Command Default The encryption priority defaults to 128bit AES, 56bit DES, 40bit DES depending on modem capability.
The CMTS treats self-signed manufacturer certificates as untrusted. Untrusted certificates are not
retained by the CMTS.
Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA.
12.2(33)SCC This command was modified. Added the retain-failed-certificates and
skip-validity-period keywords. Removed the 40-bit-des keyword.
Usage Guidelines This command is applicable only on images that support BPI or BPI+ encryption.
Note The cable privacy accept-self-signed-certificate command affects only those CMs that register after
you give the command. For example, if you give the no cable privacy accept-self-signed-certificate
command so that CMs cannot register using self-signed certificates, you must then issue the clear cable
modem all reset command to force all CMs reregister using certificates that are chained to the DOCSIS
root certificate.
Examples The following example shows how to force baseline privacy interface (BPI) to be used for all CMs on a
particular cable interface:
Router(config)# interface cable 3/1
Router(config-if)# cable privacy mandatory
The following example shows how to turn on the BPI modem authentication for an interface:
Router(config)# interface cable 5/1/1
Router(config-if)# cable privacy authenticate-modem
The following example shows how to turn on BPI multicast authorization on a particular cable interface:
Router(config)# interface cable 1/0
Router(config-if) cable privacy authorize-multicast
The following example shows how to allow CMs to register with self-signed certificates on a particular
cable interface:
Router(config)# interface cable 7/1/0
Router(config-if) cable privacy accept-self-signed-certificate
The following example shows how to allow CMs to enable privacy DSX support on a particular cable
interface:
Router(config)# interface cable 3/1
Router(config-if) cable privacy dsx-support
The following example shows how to allow CMs to enable OAEP support on a particular cable interface:
Router(config)# interface cable 3/1
Router(config-if) cable privacy oaep-support
The following example shows how to allow CMs to retain failed certificates on a particular cable
interface:
Router(config)# interface cable 3/1
Router(config-if) cable privacy retain-failed-certificates
The following example shows how to allow CMs to skip certificate validity period on a particular cable
interface:
Router(config)# interface cable 3/1
Router(config-if) cable privacy skip-vailidity-period
Syntax Description manufacturer Specifies the serial number of the manufacturer CA certificate.
serial-number
root serial-number Specifies the serial number of the root CA certificate.
Usage Guidelines This command is applicable only on images that support BPI or BPI+ encryption.
Examples The following example adds a manufacturer CA certificate serial number to the CMTS list of trusted
certificates:
Router(config)# cable privacy add-certificate manufacturer 35c14635
Router(config)#
The following example adds a root CA certificate serial number to the CMTS list of trusted certificates:
Router(config)# cable privacy add-certificate root 00908300
Router(config)#
Note Non-DOCSIS-compliant cable modems that are commonly available contain an option to force
registration in DOCSIS BPI as opposed to DOCSIS BPI+ mode even in DOCSIS 1.1-provisioned
networks.
Command Default The cable privacy bpi-plus-enforce command is not enabled by default, but must be configured for
optimal DOCSIS BPI+ security. There is no legitimate reason for a cable modem provisioned with
DOCSIS 1.1 QOS to register with DOCSIS 1.0 BPI. Such behavior is not compliant with the DOCSIS
1.1 specification.
Usage Guidelines If the cable modem is not provisioned to use DOCSIS BPI or BPI+ security certificates, as characterized
by not coming online with the above initialization states, then the existing behavior of the Cisco CMTS
remains unchanged. The Cisco CMTS does not attempt to distinguish between two cable modems if
neither is provisioned for BPI+ security.
Because this feature is enabled by default on the Cisco CMTS, the Cisco CMTS issues security breach
notice in a log message in the generic system log or syslog if cable logging layer2events is not
configured on the Cisco CMTS.
For additional information about the Cable Duplicate MAC Address Reject feature on the Cisco CMTS,
or enforced DOCSIS 1.1 security, refer to the following document on Cisco.com:
• Cable Duplicate MAC Address Reject for the Cisco CMTS
Examples The following brief example illustrates logging messages that are created with the detection of cloned
cable modems behind the configuration in the above procedure.
SLOT 7/0: Nov 14 12:07:26: %UBR10000-6-CMMOVED: Cable modem 0007.0e03.3e71 has been moved
from interface Cable7/0/1 to interface Cable7/0/0.
Usage Guidelines Use this command to enable or disable the clone modem functionality.
Examples The following example shows how to enable the clone modem functionality, so that the cloned cable
modems cannot register with the CMTS:
Router# configure terminal
Router(config)# cable privacy clone-detect
Syntax Description cm-mac-address Hardware (MAC) address of a specific cable modem to be added to the EAE
exclusion list.
mask (Optional) Mask value for the cable modem.
Command Default The EAE exclusion list does not contain any MAC address.
Usage Guidelines The exclusion list is mainly used to debug issues with specific cable modems.
Examples The following example shows how to add a CM with the MAC address of 00C0.8345.de51 to the EAE
exclusion list, so that this particular CM cannot register with the CMTS:
Router# configure terminal
Router(config)# cable privacy eae-exclude 00C0.8345.de51
Router(config)#
Usage Guidelines The EAE policy is applied on a MAC domain and the policies are mutually exclusive. The CMTS
enforces EAE only on CMs that initialize on a downstream channel on which the CMTS is transmitting
MAC Domain Descriptor (MDD) messages.
The EAE exclusion list is a global list and is created on all line cards as part of the DOCSIS 3.0
specifications. Cable modems in the EAE exclusion list are always exempted from EAE enforcement. If
the CMTS receives an authorization request before the CM is registered in the EAE exclusion list, the
CMTS rejects that request.
Examples The following example shows how to enforce EAE policy on capable modems:
Router(config)# interface cable 3/1
Router(config-if)# cable privacy eae-policy capability-enforcement
The following example shows how to disable EAE policy so that the CMTS does not enforce EAE policy
on any cable modem:
Router(config)# interface cable 3/1
Router(config-if)# cable privacy eae-policy disable-enforcement
The following example shows how to enforce EAE policy on DOCSIS 3.0 modems only:
Router(config)# interface cable 3/1
Router(config-if) cable privacy eae-policy ranging-enforcement
The following example shows how to enforce EAE policy on all cable modems:
Router(config)# interface cable 3/1
Router(config-if) cable privacy eae-policy total-enforcement
Syntax Description aes128-des40-des56 Specifies the order of the encryption algorithm priority.
AES with a 128-bit block is given the highest priority, followed by DES with
40-bit block size, and DES with 56-bit block size.
aes128-des56-des40 Specifies the order of the encryption algorithm priority.
AES with a 128-bit block size is given the highest priority, followed by DES
with 56-bit block size, DES with 40-bit block size.
des40-aes128-des56 Specifies the order of the encryption algorithm priority.
DES with 40-bit block size is given the highest priority, followed by AES with
a 128-bit block size, and DES with 56-bit block size.
des40-des56-aes128 Specifies the order of the encryption algorithm priority.
DES with 40-bit block size is given the highest priority, followed by DES with
56-bit block size and AES with 128-bit block size.
des56-aes128-des40 Specifies the order of the encryption algorithm priority.
DES with 56-bit block size is given the highest priority, followed by AES with
a 128-bit block size, and DES with 40-bit block size.
des56-des40-aes128 Specifies the order of the encryption algorithm priority.
DES with 56-bit block size is given the highest priority, followed by DES with
40-bit block size, and AES with a 128-bit block size.
Usage Guidelines Use this command to specify the order of the encryption algorithm priority.
Examples The following example shows how to assign AES the highest priority, followed by 40-bit DES, and
56-bit DES.
Router# configure terminal
Router(config)# cable privacy encrypt-alg-priority aes128-des40-des56
Router(config)#
Syntax Description cm mac-address Specifies the MAC address for the CM certificate to be added to the hotlist. The
mac-address should be specified as a hexadecimal string, without periods or other
separators. In Cisco IOS Release 12.2(15)BC2 and later releases, you can also
specify it as three sets of hexadecimal digits, separated by periods.
manufacturer Specifies the serial number for the particular manufacturer CA certificate. The
cert-serial-number cert-serial-number should be specified as a hexadecimal string up to 32 bytes in
length. Enter multiple lines as needed, and use a blank line to terminate the string.
Command Default The CMTS hotlist does not contain any certificates.
Usage Guidelines This command is applicable only on images that support BPI or BPI+ encryption.
Note The cable privacy hotlist command is not supported on the Cisco uBR10012 router running Cisco IOS
releases prior to Cisco IOS release 12.3(23)BC9, Cisco IOS release 12.2(33)SCB5, and Cisco IOS
release12.2(33)SCC.
To add a manufacturer’s or CM certificate to the hotlist on the Cisco uBR10012 router, use SNMP
commands to set the appropriate attributes in DOCS-BPI-PLUS-MIB. For more information see the
Configuring DOCSIS 1.1 on the Cisco CMTS chapter in the CMTS Feature Guide.
Examples The following command adds the CM certificate with the MAC address of 00C0.8345.de51 to the hotlist,
so that this particular CM cannot register with the CMTS:
Router# config t
Router(config)# cable privacy hotlist cm 00C08345de51
Router(config)#
The following example adds a manufacturer CA certificate into the BPI+ hotlist, so that the CMTS will
reject any CM attempting to register with a certificate from that particular manufacturer:
Router# config t
Router(config)# cable privacy hotlist manufacturer
3435414631413439383335453731423733333643
Note This command is applicable only on images that support BPI or BPI+ encryption.
Syntax Description life-time seconds (Optional) Length of the key encryption life-time in seconds.Valid range is 300
to 604,8000. The default is 604,800 seconds (7 days).
Usage Guidelines Baseline privacy on an HFC network is configured with key encryption keys (KEKs) and traffic
encryption keys (TEKs). The encryption is based on 40-bit or 56-bit data encryption standard (DES)
encryption algorithms.
A KEK is assigned to a CM based on the CM service identifier (SID) and permits the CM to connect to
the Cisco CMTS when baseline privacy is activated. KEKs can be set to expire based a life-time value.
The life-time keyword is used to assign a more permanent key to a CM.
A CM that has a life-time key assigned by the Cisco CMTS requests a new key before the current one
expires.
Examples The following example shows how to set the KEK privacy life-time to 750,000 seconds:
Router(config)# interface cable c3/0
Router(config-if)# cable privacy kek life-time 750000
Router(config-if)#
Usage Guidelines The cable privacy revocation crl skip-sig-check command allows you to use the CRL response from
the CRL server without validating the signature of the response.
Examples The following example shows how to skip the CRL response signature check:
Router(config)# cable privacy revocation crl skip-sig-check
Usage Guidelines This command allows you to quickly enable or disable revocation checking. When you enable revocation
checking, it creates the trustpoints for both the EU and US certificates.
Usage Guidelines The cable privacy revocation ocsp skip-sig-check command allows you to use the OCSP response from
the OCSP responder without validating the signature of the response.
Examples The following example shows how to skip the OCSP response signature check:
Router(config)# cable privacy revocation ocsp skip-sig-check
Usage Guidelines The cable privacy revocation skip-cm-cert command allows you to disable checking of CM
certificates.
Note Checking CM certificates requires a lot of processing power, which impacts the router performance.
Note This command is applicable only on images that support BPI or BPI+ encryption.
Syntax Description life-time seconds (Optional) Length of the traffic encryption life-time in seconds. Valid range is
180 to 604,8000. Default is 43,200 seconds (12 hours).
Usage Guidelines Baseline privacy on an HFC network is configured with key encryption keys (KEKs) and traffic
encryption keys (TEKs). The encryption is based on 40-bit or 56-bit data encryption standard (DES)
encryption algorithms.
The TEK is assigned to a CM when its KEK has been established. The TEK is used to encrypt data traffic
between the CM and the Cisco CMTS. TEKs can be set to expire based a life-time value.
The life-time keyword is used to assign a more permanent key to a CM.
A CM that has a life-time key assigned by the Cisco CMTS requests a new key before the current one
expires.
Examples The following example shows how to set the traffic encryption key life-time to 800000 seconds:
Router(config)# interface cable c3/0
Router(config-if)# cable privacy tek life-time 800000
Router(config-if)#
Usage Guidelines This command only takes effect if cable privacy revocation enable command is configured. The
timeout value for authorization “reply” or “reject” messages in the CM configuration file must be greater
than the revocation timeout value.
Examples The following example shows how to set the timeout value for CRL or OCSP response:
Router(config)# cable privacy revocation timeout 15
cable proxy-arp
To activate cable proxy Address Resolution Protocol (ARP) on the cable interface or subinterface, use
the cable proxy-arp command in cable interface or subinterface configuration mode. To disable this
feature, use the no form of this command.
cable proxy-arp
no cable proxy-arp
Usage Guidelines This command enables or disables direct host-to-host communications over the same cable subnet.
Because the downstream and upstream are separate interfaces, CMs cannot directly perform address
resolution with other CMs on the cable plant. This means that the CMs must send all traffic through the
CMTS, even if the destination CM is on the same subnet.
The cable proxy-arp command enables the Cisco CMTS to act as a proxy for ARP requests generated
by the CMs, which allows CMs on the same cable subnet to communicate directly which each other,
without the traffic having to be routed first through the CMTS. The no cable proxy-arp command
disables this feature, preventing CMs on the same subnet from communicating with each other without
routing the traffic through the CMTS.
Note Using the no cable arp and no cable proxy-arp commands shifts all responsibility for the management
of the IP addresses used by CMs and CPE devices to the DHCP server and provisioning system.
Examples The following example shows how to activate proxy ARP for host-to-host communications:
Router(config-subif)# cable proxy-arp
The following example shows how to activate proxy ARP for host-to-host communications, on the cable
subinterface:
Router(config)# interface cable 6/0.1
Router(config-subif)# cable proxy-arp
Syntax Description rule-name Name of the enforce-rule to be created and configured. This name can be any arbitrary and
unique string from 1 to 15 characters in length.
Usage Guidelines The cable qos enforce-rule command creates an enforce-rule with the specified name and then enters
enforce-rule configuration mode. After entering enforce-rule configuration mode, use the following
commands to configure the enforce-rule:
• activate-rule at-byte-count
• enabled (enforce-rule)
• enforced qos-profile
• monitoring-duration
• penalty-period
• registered qos-profile
At the very minimum, you must use the activate-rule at-byte-count and registered qos-profile
commands to configure an enforce-rule, and the enabled command to activate it, before it takes effect.
Note Effective with Cisco IOS Release 12.3(9a)BC, the activate-rule at-byte-count command is not
available in Cisco IOS software.
Note The maximum number of enforce-rules is counted as the total number of rules created on both the
upstreams and downstreams combined.
Examples The following example shows the creation of an enforce-rule named “residential.” The system then
enters the enforce-rule configuration mode.
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# ?
The following example shows the error message that is displayed if you try to create more than 20
enforce-rules in Cisco IOS Release 12.3(23)BC1 and earlier:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
The following example shows the error message that is displayed when you try to name an enforce-rule
with a name that is larger than 15 characters. An error message is displayed, and the name is truncated
to the first 15 characters.
Router# configure terminal
Router(config)# cable qos enforce-rule reallyreallyreallylongname
Syntax Description create Permits creation of QoS table entries by Simple Network Management Protocol
(SNMP).
enforce index The enforce keyword overrides the provisioned QoS profile of the CM and enforces a
specific CMTS-local QoS profile. The index argument specifies the number of the QoS
profile to be enforced on all CMs connecting to the CMTS. Valid values are from 1 to
255.
Note Both the originally provisioned QoS profile and the enforced QoS profile must
be created on the Cisco CMTS. This option does not support profiles that are
created by the CM.
modems Permits creation of QoS table entries by modem registration requests.
update Permits dynamic update of QoS table entries by SNMP.
Usage Guidelines If the QoS profile to be enforced does not exist at the CMTS during registration, the CMTS uses the QoS
profile configured for the registering CM.
If you disable the use of CM-created profiles, using the no cable qos permission command, any CMs
using such a profile go offline immediately and the CM-created profiles are removed.
This no cable qos permission command is similar to the docsIfCmtsQosProfilePermissions attribute in
the DOCS-IF-MIB, as both prohibit CMs from creating their own QoS profiles in the future. However,
the no cable qos permission command also immediately deletes QoS profiles that have been created by
the cable modems and takes those modems offline. The docsIfCmtsQosProfilePermissions method does
not affect QoS profiles that are currently in use, but only unused profiles and profiles that are created in
the future.
Examples The following example shows how to enable CMs to request arbitrary QoS parameters:
Router(config)# cable qos permission modems
The following example shows how a CM with a QoS profile 4 created by the CM is reset to use QoS
profile 225 enforced by the cable router (management):
CMTS01# show cable modem
Syntax Description us-priority Specifies the upstream priority to be assigned to the pre-registration traffic.
priority-value Priority value of the QoS profile-2.
The valid range is from 0 to 7.
Note When a cable modem begins initializing, its default upstream
service flow is assigned a QoS profile-2 priority of zero. Zero is the
lowest priority scheduled.
Command Default Zero is the default QoS profile-2 priority of the initializing cable modem.
Usage Guidelines The cable qos pre-registration command allows the Cisco CMTS operators to enforce a profile on all
cable modems that have not yet begun initialization. However, this command has no affect on cable
modems that have already started initialization and may be having difficulties getting [w-]online.
Examples The following example shows how to set the priority of the QoS profile-2.
Router# configure terminal
Router(config)# cable qos pre-registration us-priority 2
Router(config)#
Syntax Description burst-size The QoS profile’s downstream burst size in bytes.
Usage Guidelines To display ERBA settings as applied to DOCSIS 1.0 cable modems and QoS profiles on the Cisco
CMTS, use the show cable qos profile command in Privileged EXEC mode.
The following example of the cable qos profile command in global configuration mode illustrates
changes to the cable qos profile command. Fields relating to the ERBA feature are shown in bold for
illustration:
Router(config)# cable qos pro 10 ?
grant-interval Grant interval
grant-size Grant size
guaranteed-upstream Guaranteed Upstream
max-burst Max Upstream Tx Burst
max-ds-burst Max Downstream Tx burst (cisco specific)
max-downstream Max Downstream
max-upstream Max Upstream
name QoS Profile name string (cisco specific)
priority Priority
privacy Cable Baseline Privacy Enable
tos-overwrite Overwrite TOS byte by setting mask bits to value
The following example of the show cable qos profile command illustrates that the maximum
downstream burst has been defined, and is a management-created QoS profile:
Router# show cable qos pro
ID Prio Max Guarantee Max Max TOS TOS Create B IP prec.
upstream upstream downstream tx mask value by priv rate
bandwidth bandwidth bandwidth burst enab enab
1 0 0 0 0 0 0xFF 0x0 cmts(r) no no
2 0 64000 0 1000000 0 0xFF 0x0 cmts(r) no no
3 7 31200 31200 0 0 0xFF 0x0 cmts yes no
4 7 87200 87200 0 0 0xFF 0x0 cmts yes no
The following example illustrates the maximum downstream burst size in sample QoS profile 10 with
the show cable qos prof verbose command in privileged EXEC mode:
Router# show cable qos pro 10 ver
Profile Index 10
Name
Upstream Traffic Priority 1
Upstream Maximum Rate (bps) 90000
Upstream Guaranteed Rate (bps) 0
Unsolicited Grant Size (bytes) 0
Unsolicited Grant Interval (usecs) 0
Upstream Maximum Transmit Burst (bytes) 1522
Downstreamam Maximum Transmit Burst (bytes) 100000
IP Type of Service Overwrite Mask 0x1
IP Type of Service Overwrite Value 0xA0
Downstream Maximum Rate (bps) 90000
Created By mgmt
Baseline Privacy Enabled no
Usage Guidelines If a cable modem registers with a QoS profile that matches one of the existing QoS profiles on the Cisco
CMTS, then the maximum downstream burst size, as defined for that profile, is used instead of the
default DOCSIS QoS profile of 1522.
For example, a DOCSIS 1.0 configuration that matches QoS profile 10 in the previous examples would
be as follows:
03 (Net Access Control) = 1
The maximum downstream burst size (as well as the ToS overwrite values) are not explicitly defined in
the QoS configuration file because they are not defined in DOCSIS. However, because all other
parameters are a perfect match to profile 10 in this example, then any cable modem that registers with
these QoS parameters has a maximum downstream burst of 100000 bytes applied to it.
For further illustration, consider a scenario in which packets are set in lengths of 1000 bytes at 100
packets per second (pps). Therefore, the total rate is a multiplied total of 1000, 100, and 8, or 800kbps.
To change these settings, two or more traffic profiles are defined, with differing downstream QoS
settings as desired. Table 0-8 provides two examples of such QoS profiles for illustration:
Table 0-8 Sample QoS Profiles with Differing ERBA (Maximum Downstream) Settings
In this scenario, both QoS profiles are identical except for the max-ds-burst size, which is set to 5000 in
QoS profile 101 and 5000 in QoS profile 102.
cable qos profile groupnum [grant-interval interval | grant-size size | guaranteed-upstream rate
| ip-precedence value | max-burst rate | max-downstream rate | max-upstream rate |
name string | priority value | privacy | tos-overwrite tos-mask tos-value]
Syntax Description groupnum QoS profile group number. The valid range is 1 to 255.
QoS profiles 1 and 2 are required by the system; they are preconfigured
and cannot be modified nor removed. QoS profile 1 is used during
registration; QoS profile 2 is the default QoS profile.
grant-interval interval The periodic interval in microseconds at which the CM wants to send the
fixed-sized upstream MAC frames. It is used to compute the period in
between constant bit rate (CBR) slots for the CM. Valid range is from 0
to 65535. The default is 0.
grant-size size The size of the DOCSIS MAC frame the CM wants periodically to send
on the upstream transmission. This value in bytes does not include any
PHY layer overhead. It includes the complete fixed MAC frame size
starting from the frame control byte to the CRC of the protocol data unit
(PDU). This parameter is used by the CMTS to set the size of the periodic
CBR slot for the CM after adding the PHY overhead. Valid range is from
0 to 65535. The default is 0.
guaranteed-upstream rate Guaranteed minimum upstream rate in kilobytes per second. Valid values
are from 0 to 100000. Default value is 0 (no reserved rate).
ip-precedence value Bits in the type-of-service (ToS) byte that enable you to configure
individual data rate limits on a per modem basis. Valid values are from 0
to 7. The default is 0.
Note This option has been deprecated and removed from the CLI,
because its function should be accomplished through the
DOCSIS configuration file.
max-burst rate Maximum upstream transmit burst size in bytes that the modem can send
for any single transmit burst. Valid values are from 0 to 65,535 bytes.
Default value is 0 (no limit). The recommended value range is 1600 to 1800
bytes. Using a value of 0 or greater than 1800 bytes can cause latency issues
for Voice-over-IP. A value of less than 1500 bytes can prevent the upstream
transmission of large Ethernet frames for any modem or CMTS not
implementing fragmentation.
Note The CM enforces the maximum upstream transmit burst limit.
The Cisco CMTS does not enforce this limit, but this command
can still be used for documentation and troubleshooting
purposes.
max-downstream rate Maximum downstream data rate in kilobits per second that a modem
using this QoS profile receives. Valid values are from 0 to 100,000.
Default value is 0 (no downstream rate limit).
Note This option has been deprecated and removed from the CLI,
because its function should be accomplished through the
DOCSIS configuration file.
maximum-upstream rate Maximum upstream data rate in kilobits per second that a modem using
this QoS profile receives. Valid values are from 0 to 100,000. Default
value is 0 (no upstream rate limit).
name string Arbitrary, unique string to identify this QoS profile. The maximum
length is 32 characters before Cisco IOS Release 12.2(11)BC2, and
80 characters in Cisco IOS Release 12.2(11)BC2 and later.
priority value Relative priority number assigned to upstream traffic by this QoS profile.
Valid values are from 0 to 7, with 7 being the highest priority. Default
value is 0.
privacy Enables Baseline Privacy Interface (BPI) encryption. The default is to
disable BPI encryption.
tos-overwrite tos-mask Overwrite the ToS field in the IP datagrams received on the upstream
tos-value before forwarding them downstream (or IP backbone). This parameter
sets the hexadecimal mask bits to the hexadecimal values for the ToS
mask and ToS value, thereby helping the CMTS identify datagrams for
QoS on the backbone.
Each parameter is an 8-bit hexadecimal value that ranges from 0x00 to
0xFF. The default value is 0xFF starting with Cisco IOS Release
12.2(15)BC2 and later, and the default is 0x00 in earlier releases. The
new TOS value is calculated using the following formula:
New ToS = ((Original ToS) AND (NOT tos-mask)) OR tos-value
Note This formula is how the TOS was calculated in DOCSIS 1.0+
networks before the DOCSIS 1.1 specification was finalized. For
information on the new method of calculating the TOS in
DOCSIS 1.1 networks, see the cable service class command.
Command Default If the cable qos profile command is given without any options, it creates a profile with all default values:
Baseline Privacy Interface is disabled, and all other values are set to 0.
Release Modification
12.0(5)T The ip-precedence option was added, and the range for the max-downstream
option was increased.
12.0(7)XR2 The output was reorganized and name, grant-size, and grant-interval parameters
were added.
12.1(4)CX This command was deprecated for DOCSIS 1.1 use, because DOCSIS 1.1 replaces
the QoS profile model with a service flow model. See the cable service class
command for details.
12.2(11)CY, The maximum length of the name string was increased from 32 characters to 80
12.2(11)BC2 characters.
12.2(15)BC21 The ip-precedence and max-downstream options were removed, because their
functions can be better accomplished through the DOCSIS configuration file.
Usage Guidelines The cable qos profile command configures the quality of service (QoS) settings for a particular class of
service on a DOCSIS 1.0 or DOCSIS 1.0+ network. This command cannot be used on DOCSIS 1.1 and
DOCSIS 2.0 networks, which use the cable service class command instead.
In Cisco IOS Release 12.2(15)BC21, the ip-precedence and max-downstream options were removed.
If you are supporting DOCSIS 1.0+ CMs that require these parameters for voice over IP (VoIP) traffic
and other real-time traffic, use the following Cisco Vendor-Specific Fields (VSIF) in the CM’s DOCSIS
configuration file:
Table 9 Cisco VSIF Fields for IP Precedence and Max Downstream Rate
Examples The following example shows how to configure QoS profile 4 with a guaranteed upstream rate of 8 kbps,
a maximum transmission burst of 1800 bytes, a maximum downstream rate of 128 kbps, a priority of 4,
cable baseline privacy set, and a tos-overwrite mask and value byte (in hex) of 0x2:
Router(config)# cable qos profile 4 guaranteed-upstream 8
Router(config)# cable qos profile 4 max-burst 1800
Router(config)# cable qos profile 4 max-downstream 128
Router(config)# cable qos profile 4 privacy
Router(config)# cable qos profile 4 priority 4
Router(config)# cable qos profile 4 tos-overwrite 0xE0 0xE0
cable rcc-template
To define a receive channel configuration (RCC) template, use the cable rcc-template command in
global configuration mode.
Command Default If an RCC template is not assigned to a cable interface, the CMTS will use the wideband cable interface
generated RCC for a receive channel profile (RCP).
Usage Guidelines A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive
channel (RC) entry.
First, you define an RCC template for an RCP, and then assign the template to a cable interface to
generate RCCs based on the actual DS channel configuration.
Note When assigning an RCC template to a cable interface, use this command in interface configuration
mode.
cable rcp-control
To enable the receive channel profile (RCP) reporting with verbose description, use the cable
rcp-control command in interface configuration mode. To revert to the default simple RCP reporting,
use the no form of this command.
no cable rcp-control
Syntax Description verbose Enables RCP reporting with verbose description that contains complete
subtype encodings defined in DOCSIS 3.0.
Command Default If this command is not used, cable modems use the default RCP reporting method that contains only the
RCP identifiers.
Usage Guidelines Use this command to enable a CM to send detailed RCP data in the registration request. This detailed
RCP data can be verified using the debug cable registration command. This verbose RCP data is useful
while configuring a receive channel configuration (RCC) template.
Examples The following example shows how to enable RCP reporting with verbose description on a cable interface
on the Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 8/0/0
Router(config-if)# cable rcp-control verbose
Related
Commands Command Description
debug cable Displays debug messages for the CM registration process.
registration
cable rcc-template Defines a Receive Channel Configuration (RCC) template.
Syntax Description hash_id Unique ID for the shared hash filter. Multiple (differently named) hash
filters are supported in the same Cisco DDC Redundancy scheme at the
same time, though only one hash filter can be enabled at any one time.
Supported range is 1 to 3.
type namestring Alphanumeric hash filter name. Only the namestring of default is supported
at this time.
mac-mask mac-mask Specifies the number of bits in the cable modem’s MAC address to be used
by the hashing algorithm.
mac-map mac-address A manually configured MAC address for the DDC node (overrides any
default MAC address configured on the router).
node node_id This value overrides the node that all cable modems with the shared
mac-address or oui value will use, and updates the MAC address mapping
in the hash filter.
oui-map oui This value overrides the node that all cable modems with the shared OUI
value will use, and updates the OUI address mapping in the hash filter.
Command Default • Cable redundancy hash filters are disabled (not configured) by default.
• Only the hash filter name of default is supported at this time.
Usage Guidelines This command is used in the early stages of configuring DDC Redundancy on all DDC nodes (routers)
in the scheme. For additional information in context, refer to the “Configuring Cisco DDC Redundancy
on the Cisco uBR7246VXR Universal Broadband Router” feature documentation on Cisco.com.
Note This configuration must be present and identical on each CMTS router participating in the DDC
redundancy scheme.
Examples The following example implements the cable redundancy hashfilter command in four sequential steps,
completing the entire mapping information required for one DDC node in a redundancy scheme of two
routers:
Router# cable redundancy hashfilter 1 type default
Router# cable redundancy hashfilter 1 macmask FFFF.FF00.0000
Router# cable redundancy hashfilter 1 macmap 0007.0e03.68ad node 2
Router# cable redundancy hashfilter 1 ouimap 00070e node 1
Syntax Description node_id A unique identifier for the Cisco DDC node currently being configured. The
value must be 1 or greater (not to exceed the value used for nodes). This
value must be unique on each CMTS that participates in the scheme.
nodes Total number of Cisco CMTS routers participating in the DDC redundancy
scheme (range 1 to 3). This value must be identical on all DDC nodes
(routers).
Command Default DDC Redundancy is disabled and DDC nodes (routers) are not configured for DDC redundancy by
default.
Usage Guidelines This configuration must be present (identical except node_id) on all DDC nodes (routers) participating
in the scheme.
This command is used in the early stages of configuring DDC Redundancy on all DDC nodes (routers)
in the scheme. For additional information in context, refer to the “Configuring Cisco DDC Redundancy
on the Cisco uBR7246VXR Universal Broadband Router” feature documentation on Cisco.com.
Examples The following example configures the DDC node (router) ID to be 2 in a scheme in which there are three
DDC nodes total.
Router# cable redundancy myid 2 nodes 3
Syntax Description node_id DDC node (router) with which the subinterface is associated. The range is
the number of DDC nodes in the scheme.
force Optional keyword forces the subinterface into the standby state regardless
of the number of active voice or E911 calls.
Command Default DDC switchover events are disabled by default and must be manually initiated on a case-by-case basis.
Usage Guidelines This command can be used in the context of DDC configuration, testing or forced switchover events.
Refer to earlier procedures in this document for additional information.
Note Use of this command is subject to additional constraints described in the “Active Voice Call Protection
in Cisco DDC Redundancy” section of the “Configuring Cisco DDC Redundancy on the Cisco
uBR7246VXR Universal Broadband Router” feature documentation on Cisco.com..
Examples The following command sequence sets the DDC node states in a scheme with two DDC nodes (routers),
then forces a switchover event on DDC node 1 that puts it into standby state.
Router(config-subif)# cable redundancy node 2 active
Router(config-subif)# cable redundancy node 1 standby
Router(config-subif)# cable redundancy node 1 standby force
Syntax Description node_id DDC target node ID for which the frequency is being set.
frequency Downstream frequency of the target interface.
Usage Guidelines This command must be present on each cable interface participating in the scheme, regardless of its
bundle status.
Examples The following example configures the downstream frequency of DDC node 1 to be 435000000.
Router(config-if)# cable redundancy node 1 frequency 435000000
Syntax Description node_id Target node ID (in relation to the current DDC node)
Command Default When this command is not present, the default target node is the next higher node in the scheme.
Usage Guidelines The downstream frequency that is used in a DDC switchover event is the frequency set on the respective
target DDC node, as set with this command.
Note This command may be present on each participating cable interface, regardless of its bundle status.
When this command is not present, the default target node is the next higher node in the scheme (the
next higher node_id value in the scheme). For example, if there are three participating nodes, the default
target nodes are as follows (respectively):
• If the current node is 1, the target node is 2.
• If the current node is 2, the target node is 3.
• If the current node is 3, the target node is 1.
Examples The following example configures the target node on the current router to be DDC node 1, often referred
to as CMTS A in additional sections of this document.
Router(config-if)# cable redundancy target 1
Command Description
cable redundancy node Configures the DDC scheme by setting the DS frequencies for each
frequency node in the scheme other than the current DDC node (router).
cable redundancy threshold Configures the DDC node by setting the active voice call threshold on
the current DDC node (router).
show cable redundancy Displays the current DDC redundancy configurations and status.
Syntax Description max-calls The threshold value for the number of active voice calls.
Command Default The threshold for maximum calls is not set by default.
Usage Guidelines If the number of active voice calls exceeds this value, a DDC switchover does not take place unless it is
forced by using the cable redundancy node node_id standby force subinterface configuration
command.
If the command is configured on a bundle master, the threshold is used to compare with the total number
of voice calls in the bundle. This command is not accepted on interfaces configured as bundle slaves.
If this threshold is not configured, this check does not occur and the DDC switchover proceeds regardless
of how many voice calls are active. This is subject to additional constraints described in the “Call Priority
in Cisco DDC Redundancy” section of the “Configuring Cisco DDC Redundancy on the Cisco
uBR7246VXR Universal Broadband Router” feature documentation on Cisco.com.
Examples The following example configures DDC redundancy not to take place if there are more than 20 active or
E911 calls at the time a DDC switchover event is attempted or requested.
Router(config-if)# cable redundancy threshold 20
cable registration-timeout
To set the value of the DOCSIS registration timeout timer (T9 timer) on a particular interface, use the
cable registration-timeout command in cable interface configuration mode. To reset the timeout value
to the default, use the no form of this command.
no cable registration-timeout
Syntax Description minutes Sets the value of the DOCSIS CM registration timeout timer (T9 timer). Valid range is from
2 to 60 minutes. The default is 3 minutes.
Usage Guidelines The DOCSIS 1.1 specification states that the CMTS should enforce the T9 timer, which is a registration
timeout timer that specifies the maximum time allowed between the CMTS sending a successful Ranging
Response (RNG-RSP) message and the CM replying with a Registration Request (REG-REQ) message.
If this timer expires, the CMTS must remove the CM from its list of active CMs, and the CM must restart
the registration process.
The cable registration-timeout command can be used to customize the value of the T9 timer for each
cable interface, to accommodate the CMs using that interface.
Examples The following example shows the registration timeout value being increased from 3 minutes to
10 minutes:
Router# configure terminal
Router (config)# interface c6/0
Router(config-if)# cable registration-timeout 10
Router(config-if)# exit
Router(config)#
cable relay-agent-option
To enable the system to insert the CM MAC address into a Dynamic Host Configuration Protocol
(DHCP) packet received from a CM or host and forward the packet to a DHCP server, use the cable
relay-agent-option command in cable interface configuration mode. To disable MAC address insertion,
use the no form of this command.
cable relay-agent-option
no cable relay-agent-option
Usage Guidelines This functionality enables the use of DHCP Option 82 to allow a DHCP server to identify the CM
sending the request and to initiate the appropriate action based on this information. On Cisco IOS
Release 12.0 and later releases, use the ip dhcp relay information option command to enable Option 82
processing.
Examples The following example shows how to enable the insertion of DHCP relay agent information into DHCP
packets:
Router(config-if)# cable relay-agent-option
Command Description
cable telco-return spd dhcp-authenticate Enforces the telco-return CM to use a specific DHCP
server.
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CM must access.
ip dhcp relay information option Enables the system to insert the CM MAC address into a
DHCP packet received from a CM or host and forward the
packet to a DHCP server.
ip dhcp smart-relay Monitors client retransmissions when address pool
depletion occurs.
cable rf-bandwidth-percent
To enable either static or dynamic bandwidth sharing for a modular cable (MC) interface, use the cable
rf-bandwidth-percent command in interface configuration mode. To remove bandwidth sharing for the
MC interface, use the no form of this command.
no cable rf-bandwidth-percent
Syntax Description percent-value Specifies static bandwidth allocation of a downstream RF channel. The
range is 1–96. The default is 0.
remaining ratio (Optional) Specifies the ratio of the remaining or excess bandwidth that can
be allocated to the modular cable channel.
Note This option is only available when dynamic bandwidth sharing is
enabled.
excess-value Specifies the value of excess bandwidth that can be allocated to the modular
cable channel. The range is 1–100. The default value is 1.
Command Default The default static bandwidth percentage for a modular cable interface is 0.
Usage Guidelines The total percentage of the RF channel bandwidth allocated to both the modular cable (MC) and
wideband interfaces must not exceed 96 percent. The remaining 4 percent of the bandwidth is reserved
for minislot allocation packet (MAP) and other MAC management messages (MMM) DOCSIS traffic
using this RF channel as its primary channel.
When dynamic bandwidth sharing (DBS) is enabled on the MC interface, the bandwidth percentage is
converted to a committed information rate (CIR) value for the corresponding link queue. By
re-interpreting the bandwidth percentage value as a CIR value for the MC interface, the interface
receives, at minimum, the configured percent of bandwidth and more when the RF channel’s bandwidth
is not consumed by other interfaces sharing the same RF channel. The remaining ratio option is only
available when DBS is enabled using the cable dynamic-bw-sharing command.
If the cable rf-bandwidth-percent command is not configured and DBS is enabled, no bandwidth is
reserved for the MC interface and it is effectively in the protocol down state—the MC link queue is not
created. Static bandwidth sharing (the default) or DBS can be configured on an MC interface, but you
cannot have both on the same interface.
cable rf-channel
To associate an RF channel on a Wideband SPA with a wideband interface and allocate bandwidth, use
the cable rf-channel command in interface configuration mode. To remove an association of an RF
channel to a wideband interface, use the no form of this command.
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA
field-programmable gate array (FPGA).
Note Valid values for rf-port depend on the configuration set with the
annex modulation command (see the “Usage Guidelines”
section).
bandwidth-percent (Optional) Specifies the percent of bandwidth from this RF channel that
bw-percent will be used for the wideband interface. The range is 0 to 100. If
bandwidth-percent is not used, the default bandwidth value is
100 percent.
remaining ratio (Optional) Specifies the ratio of the excess bandwidth that can be
excess-value allocated to the wideband interface. The default value is 1. The range is 1
to 100.
Note This option is only available when dynamic bandwidth sharing
(DBS) is enabled.
Command Default No default RF channel association with a wideband interface is configured. If the cable rf-channel
command is used without specifying bandwidth-percent, the default bandwidth value is 100 percent.
Usage Guidelines The cable rf-channel command associates an RF channel (port) on a Wideband SPA with a wideband
interface. Optionally, you can specify the percent of bandwidth from this RF channel that will be used
for the specified wideband interface.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command. For annex A
and 256 QAM modulation, each Wideband SPA supports up to 18 RF channels at full rate and up to 24
RF channels at less than full rate. For all other cases, the SPA supports 24 RF channels.
Note The command changes in Cisco IOS releases 12.3(23)BC and 12.3(23)BC1 are not supported in Cisco
IOS release 12.2(33)SCA.
Note In Cisco IOS Releases 12.3(21)BC and 12.3(21a)BC3, the cable rf-channel command is not available
on the Cisco IOS command line until annex and modulation have been set with annex modulation
command.
Effective with Cisco IOS Release 12.3(23)BC, the annex modulation command is obsolete and annex
and modulation are included as keyword options in the rf-channel frequency command.
Each Wideband SPA supports up to 32 wideband channels. A wideband interface cannot consist of RF
channels from two different Wideband SPAs. The number of RF channels that can be aggregated into a
wideband interface is determined by the capability of the wideband cable modem.
• The Linksys WCM300-NA, WCM300-EURO, and WCM300 JP wideband cable modems can
receive a wideband interface consisting of up to eight downstream RF channels at 6 MHz per
channel, or up to six downstream RF channels at 8 MHz per channel. The modem requires that the
channels be received in a 50-MHz capture window.
• The Scientific Atlanta DPC2505 and EPC2505 wideband cable modems support the receiving of one
wideband interface. The wideband channel consists of three downstream RF channels at either 6
MHz per channel or 8 MHz per channel.
An RF channel can be associated with multiple wideband interfaces as long as the wideband interfaces
belong to the same virtual bundle interface (cable bundle) and the RF channel’s total allocated bandwidth
does not exceed 100 percent. As an example, Table 10 shows that a single RF channel can be associated
with multiple wideband interfaces as long as the total allocated bandwidth for the RF channel does not
exceed 100 percent.
Wideband Bandwidth
RF Channel Interface Allocated
10 0 30 percent
10 1 30 percent
10 2 40 percent
Total Bandwidth Percent: 100 percent
Table 11 shows that a single RF channel can be associated with a narrowband and multiple wideband
interfaces as long as the total allocated bandwidth for the RF channel does not exceed 100 percent.
Note Each RF channel on the CMTS can be mapped to a specific QAM port on an edge QAM device. Traffic
from different Wideband SPAs cannot be mixed on the same QAM port.
When dynamic bandwidth sharing (DBS) is enabled, the bandwidth percentage is converted to a
committed information rate (CIR) value that provides the level of guaranteed bandwidth for the
wideband interface. The reserved bandwidth for the wideband interface is the sum of its link queue CIR
values and is used for admission control of the service flows with minimal reserved rate. With DBS
enabled and the cable rf-channel command configured, the corresponding link queue can have 100
percent of the CIR value. The excess-value is the percent of excess bandwidth that can be allocated to
the wideband channel.
Static bandwidth sharing (the default) or DBS can be configured on a wideband interface, but you cannot
have both on the same interface.
Examples The following example shows how to associate RF channel 10 and RF channel 11 with wideband
interface 0:
Router(config)# interface wideband-cable 1/0/0:0
Router(config-if)# cable rf-channel 10 bandwidth-percent 50
Router(config-if)# cable rf-channel 11
In the preceding example, because no bandwidth-percent is specified in the second cable rf-channel
command, the default value (100 percent of bandwidth) applies; that is, 100 percent of RF channel 11
bandwidth is used for wideband interface 0.
The following example shows bandwidth allocation when DBS is enabled:
Router(config)# interface wideband-cable 1/0/0:0
Router(config-if)# shutdown
Router(config-if)# cable dynamic-bw-sharing
Router(config-if)# no shutdown
Router(config-if)# cable rf-channel 10 bandwidth-percent 50 remaining ratio 5
In the preceding example, because DBS is enabled, the wideband interface is guaranteed 50 percent of
the bandwidth and 5 as the value for allocating excess bandwidth.
cable rf-change-dampen-time
To configure the amount of time a radio frequency (RF) channel must remain in its new state (either up
or down), use the cable rf-change-dampen-time command in global configuration mode. To restore the
default value, use the no form of this command.
no cable rf-change-dampen-time
Syntax Description seconds Specifies the amount of time in seconds for a non-primary RF channel to
remain in its new state. The valid range is 1 to 65535. The default value is 30.
Command Default If this command is not used, the default value of 30 seconds will be restored.
Examples The following example shows how to specify the amount of time for a non-primary RF channel to remain
in its new state:
Router# configure terminal
Router(config)# cable rf-change-dampen-time 10
Usage Guidelines The cable rsvp default-scn command allows users to specify the default service class that enables the
RSVP created service flows to inherit characteristics.
cable rf-change-trigger
To specify the amount of time an event must persist before it triggers an action for the reporting cable
modem (CM), use the cable rf-change-trigger command in global configuration mode. To restore the
default value, use the no form of this command.
Syntax Description percent value (Optional) Indicates the percentage of cable modems that must report that a
particular non-primary RF channel is down before that channel is removed
from the bonding group. The valid range is 1 to 100. The default value is 0.
count number (Optional) Specifies the number of cable modems reporting an impairment
for a non-primary downstream channel. The default value is 0.
Command Default If this command is not used, the default value (0) will be used.
Usage Guidelines This command applies to all non-primary RF channels on a CMTS. The default value of 0 will prevent
any bonding group modifications. In order to dampen the change of logical state for an RF channel, the
trigger for the channel can be set to one half of the number used for the logical state. For example, if you
enter cable rf-change-trigger percent 20, when 20 percent of the CMs report an RF channel is down,
the RF channel’s logical state is changed to down. And when 10 percent of the CMs report that the
affected RF channel is back, the logical state is changed to up.
In the case of a small number of wideband modems, you can specify an absolute value for triggering an
event in addition to the percentage. Both values must be true in order to trigger the suspension of an RF
channel. When both values are 0, the CM is reset if the CM reports an RF failure through a CM status
message. Also, if you set thresholds to 0, then all CMs with RF failures are reset and any RFs suspended
from a bonding group are reactivated.
Examples The following example shows how to specify the amount of time an event must persist before it triggers
an action for the reporting CM:
Router# configure terminal
Router(config)# cable rf-change-trigger percent 50 count 1
New Commands
Modified Commands
Syntax Description enforce Enforces bonding-capable modems to register only on bonded RF channels.
Command Default A bonding-capable modem is allowed to register on the primary channel selected by the modem for
initiation even if the channel is not part of a bonding group.
Usage Guidelines For bonding capable cable modems, the primary channel selection that is done by the CMTS depends on
whether the modems can resolve its MAC Domain Downstream Service Group ID (MD-DS-SG). The
CM must attempt to determine its MAC Domain Downstream Service Group ID (MD-DS-SG-ID) if an
MDD is present on the downstream. If a modem has resolved its MD-DS-SG, the CMTS selects a bonded
primary channel, the primary channel that is part of an operational wideband channel, from the RF
channel set corresponding to the MD-DS-SG determined by the modem. The bonded primary channel
selected by the CMTS needs to be hosted by an interface on the same uBR10-MC5X20 cable interface
line card as the modem’s initial primary channel. If there are multiple primary capable channels that
meet the above criteria, the final primary channel will be randomly selected among the eligible channel
set.
If a modem has not resolved its MD-DS-SG and the enforce option is configured, the CMTS selects a
bonded primary channel based on MAP group associated with the modem’s upstream channel. Typically,
an upstream channel is configured into a single fiber node and the CMTS infers the topology information
based on the downstream channels associated with the upstream. If the enforce option is not configured
or the CMTS cannot find a target primary channel, the modem will be allowed to register on the primary
channel currently selected by the modem for initialization.
Note The CMTS will only try to move the modem with MD-DS-SG unresolved if the enforce option is
configured.
By default, changing the primary channel to select a wideband channel is not enforced and modems are
allowed to operate on a primary channel even if they are not included in any load balancing groups. At
any time after the system is up, enabling the primary channel selection for bonding capable modems will
not affect existing modems in the system. The operator has to manually reset the bonding capable
modems using the clear cable modem command either globally or at per-MAC Domain level.
Note Enabling primary channel selection for wideband modems will not affect existing modems in the system.
Related Commands cable service attribute voice-enabled Restricts voice services to only to the uBR10-MC5x20 line
cards for high availability.
cable service attribute non-ds-bonded Forces the non-bonding-capable modems to register only on
downstream-type bonding-disabled non-bonded RF channels on the CMTS.
Command Default The non-bonding-capable modem registers on its current primary channel.
Usage Guidelines A modem is identified as a non-bonding-capable modem if the modem reports a Multiple Receive
Channel Support value of 1 for TLV 5.29 or an RCP ID unknown to the CMTS during the modem’s
registration request.
The non-bonding capable modem, identified at registration, will be moved to a non-bonded primary
channel through downstream frequency override, if its current primary channel is part of a bonding
group. The target non-bonded primary channel will be selected among primary capable channels that are
associated to the modem’s current upstream channel, however not included in any wideband channels
associated to any host interfaces on the local line card. Once this option is enabled, the bonded primary
channels will be taken out of load balancing group, to prevent non-bonding capable modems to be moved
back to bonded primary channels for load balancing purpose.
Note Enabling primary channel selection for wideband modems will not affect existing modems in the system.
The operator has to reset the existing non-bonding capable modems using the clear cable modem
command.
Related Commands cable service attribute voice-enabled Restricts voice services to only to the uBR10-MC5x20 line
cards for high availability.
cable service attribute ds-bonded Forces a downstream bonding-capable modem to initialize on
downstream-type bonding-disabled a bonded primary-capable downstream channel.
clear cable modem Removes all modems or modems hosted by a uBR10-MC5x20
downstream interface under a specific category.
Syntax Description frequency freq Specifies the downstream channel frequency to which modems that access the
CMTS with legacy INIT-RNG-REQ are moved.
Command Default The non-bonding-capable modem continues the ranging process on the primary channel currently
selected by the modem for initialization.
Usage Guidelines The cable service attribute non-ds-bonded command provides the ability to prevent potential
non-bonding-capable modems that access CMTS with legacy INIT-RNG-REQ at initialization to register
on a CMTS that supports bonding-capable modem. These modems that use legacy initial ranging will be
redirected to a specified downstream channel frequency.
Note If the frequency option is used and if the frequency is modified, then the new frequency setting will only
impact new modems trying to initialize after the frequency is modified. To enforce the downstream
channel selection policy on existing modems, each modem has to be manually reset either globally or at
the individual primary channel level using the clear cable modem command.
Related Commands cable service attribute voice-enabled Restricts voice services only to the uBR10-MC5x20 line cards
for high availability.
cable service attribute ds-bonded Forces a downstream-bonding capable modem to initialize on
downstream-type bonding-enabled a bonded primary-capable downstream channel.
cable service attribute Forces the non-bonding-capable modems to register only on
non-ds-bonded downstream-type non-bonded RF channels on the CMTS.
bonding-disabled
clear cable modem Removes all modems or modems hosted by a uBR10-MC5x20
line card downstream interface under a specific category.
Command Default All primary-capable downstream channels on the uBR10-MC 5x20 line card and the SPA can support
downstream voice service flows.
Usage Guidelines A voice-enabled cable modem is identified either at registration by decoding DHCP TLV 122 in the
modem's DHCP-ACK, or at its first voice call if DHCP TLV 122 is not exchanged. If a voice-enabled
modem is detected at registration on a SPA downstream channel, it will be moved to the uBR10-MC5x20
downstream channel in the CGD via downstream frequency override. If the voice-enabled modem is
detected at its first voice call after registration, it will be moved after the call is over to the
uBR10-MC5x20 channel in the CGD via DCC. If the voice enabled modem fails to come up on the target
uBR10-MC5x20 channel, the CMTS will continue to move the modem until three retries (the maximum
number of allowed retries) has been reached, when the modem will be allowed to stay on the SPA
downsream channel until another set of retries is attempted by the CMTS every 24 hours. A voice
enabled modem on the uBR10-MC5x20 channel will be excluded from being load balanced to a SPA
downstream channel. If this option is configured at any time after the system if up, voice enabled
modems that have been identified on the SPA dowsntream channel without active voice calls will be
gradually moved to the uBR10-MC5x20 downstream channel in the CGD at the rate of one modem per
five seconds.
Related Commands cable service attribute non-ds-bonded Forces a non-bonding-capable modem to register only on
non-bonded RF channels.
cable service attribute ds-bonded Forces a downstream-bonding capable modem to initialize
on a bonded primary-capable DS channel.
Syntax Description class-index Specifies the class ID for the class to be modified. Valid range is 1
to 255.
activity-timeout Specifies the activity timeout (0 to 65,535).
admission-timeout Specifies the admitted timeout (0 to 65,535).
downstream Specifies that the service class is for the downstream direction
(from the CMTS to the CM). (The default direction is upstream.)
grant-interval Specifies the grant interval (0 to 4,294,967,295 microseconds).
grant-jitter Specifies the grant jitter (0 to 4,294,967,295 microseconds).
grant-size Specifies the grant size (0 to 65,535 bytes).
grants-per-interval Specifies the grants per interval (0 to 127 grants).
max-burst Specifies the maximum transmission burst (1522 to 4,294,967,295
bytes).
Note The recommended value range is 1600 to 1800 bytes. Using
a value of 0 or greater than 1800 bytes can cause latency
issues for Voice-over-IP. A value of less than 1522 bytes can
prevent the upstream transmission of large ethernet frames
for any CM or CMTS not implementing fragmentation.
max-concat-burst Specifies the maximum concatenation burst (0 to 65,535 bytes).
max-latency Specifies the maximum latency allowed (0 to 4,294,967,295
microseconds).
max-rate Specifies the maximum rate (0 to 4,294,967,295 bps).
min-packet-size Specifies the minimum packet size for reserved rate (0 to 65,535
bytes).
min-rate Specifies the minimum rate (0 to 4,294,967,295 bps).
name Specifies the service class name string.
peak-rate Specifies the peak rate (0 to 4,294,967,295 bps). Default value is
zero, which represents the line rate.
Note The peak-rate option is not supported on the DOCSIS 1.0
modems.
poll-interval Specifies the poll interval (0 to 4,294,967,295 microseconds).
poll-jitter Specifies the poll jitter (0 to 4,294,967,295 microseconds).
priority Specifies the priority (0 to 7, where 7 is the highest priority).
req-trans-policy Specifies the request transmission policy bit field (0 to FFFFFFF in
hexadecimal).
Command Default Values that are not specified are set to their DOCSIS 1.1 defaults, if applicable to the service-class
schedule type. See Section C.2.2, Service Flow Encodings, in the DOCSIS 1.1 specification.
Usage Guidelines The sched-type option must always be specified for each class. When a certain scheduling type is
selected, take care that the mandatory parameters for that scheduling type are explicitly entered, while
nonapplicable parameters must be explicitly removed.
The default direction is upstream. We recommend that you do not change the direction of a service class
after you have created it, because some of the existing service class parameters might not be appropriate
for the new direction. Instead, delete the current service class and create a new service class with the
correct upstream or downstream direction.
If the service class is newly created, a service-class name must be defined before entering the parameters
for the service class.
Note Section C.2.2.6.10, IP Type of Service Overwrite, of the DOCSIS 1.1 specification changed the operation
of tos-overwrite option. In DOCSIS 1.1 networks, the new TOS value is calculated by the following
formula: New IP TOS = ((Original TOS value AND and-mask) OR or-mask). (For a description of the
previous method of calculating the TOS value, see the cable qos profile command.) The default is to
leave the TOS value unchanged (no overwrite).
Examples The following examples show configurations that use the cable service class command to create service
classes. Based on the scheduling type specified, some command lines are mandatory, while others are
optional.
Each example shown here is a complete configuration set for creating a service class.
Configuring a Service Class for Unsolicited Grant Scheduling with Activity Scheduling
Router(config)# cable service class 2 name UP_UGSAD
Router(config)# cable service class 2 sched-type 5
Router(config)# cable service class 2 grant-size 100
Router(config)# cable service class 2 grant-interval 20000
Router(config)# cable service class 2 grant-jitter 4000
Router(config)# cable service class 2 grants-per-interval 1
Router(config)# cable service class 2 poll-interval 10000
Router(config)# cable service class 2 poll-jitter 4000
Router(config)# cable service class 2 min-packet-size 100
Router(config)# cable service class 2 req-trans-policy 0x1FF
Router(config)# cable service class 2 tos-overwrite 0x1F 0xE0
Router(config)# cable service class 2 activity-timeout 30
Router(config)# cable service class 2 admission-timeout 30
Command Description
cable qos profile Creates a DOCSIS 1.0 QoS profile.
show cable service-class Displays the service classes that have been created.
Syntax Description n The timeout length in seconds. Valid range is 0 - 65535 seconds. Setting this value to 0 configures
the service flow to never timeout.
Command Default The default timeout length for a DOCSIS 1.0+ cable service flow is 300 seconds (five minutes).
Usage Guidelines Dynamic service flows in DOCSIS 1.0+ are created with a default activity timeout of 300 seconds. This
enables the deletion of idle service flows after five minutes. This new command enables such functions
within DOCSIS 1.1 environments with a wide range of timeout length options.
In DOCSIS 1.1, the default inactivity timeout is often set by the application that triggers the creation of
dynamic service flows. PacketCable frequently performs this function when supported on the Cisco
CMTS. However, this new command configures inactivity timeout where PacketCable is not active on
the Cisco CMTS.
Note When PacketCable is supported, PacketCable sets the inactivity timeout from the PacketCable gate, and
the PacketCable activity overrides timeout values set with this command. This is the case even where the
inactivity timeout is set to zero, which configures the service flow to never timeout.
Apart from PacketCable, this command enables the cable modemto control the setup of the dynamic
service flows, and to remove inactive service flows. During the creation of service flows, all Upstream
and Downstream flows in the request are checked to see if the configured activity timeout needs to be
applied.
Note The cable service flow activity-timeout command affects new calls only; it does not clear any existing
hung flows. To clear existing flows, use the test cable dsd <mac-add> <sid> command.
Examples The following example in global configuration mode configures the cable modems connected to the
Cisco CMTS to use activity timeout of zero, which means that related service flows do not timeout in a
non-PacketCable environment:
Router(config)# cable service flow activity-timeout 0
Syntax Description n Specifies the threshold limit in seconds, with 10 seconds as the default. Configurable limits are 1 to
3600 seconds.
Command Default The default is to enable the inactivity timer, with a default value of 10 seconds.
Usage Guidelines DOCSIS 1.1 allows a CM to request Unsolicited Grant Service (UGS) for an upstream, allowing the CM
to reserve a certain amount of Constant Bit Rate (CBR) bandwidth for real-time traffic, such as
Voice-over-IP (VoIP) calls. The UGS-AD variation allows the CMTS to switch a service flow to Real
Time Polling Service (RTPS) after a certain period of inactivity, so that bandwidth is not reserved when
it is not needed. The CM can then request UGS service when the flow again becomes active.
Note This command replaced the cable service-flow inactivity-timeout command, which was used in
DOCSIS 1.0 operation to enable or disable watchdog cleanup of dynamic service flows that are not
sending any packets on the upstream.
The cable service flow inactivity-threshold command sets the inactivity timer for how long a service
flow must be inactive before the CMTS can switch it from UGS-AD to RTPS. The no cable service flow
inactivity-threshold command disables the timer and resets it to its default value of 10 seconds, so that
the CMTS always provides UGS service to the service flow, even when the flow is idle.
Caution The no cable service flow inactivity-threshold command effectively disables the use of RTPS and
USG-AD services and configures the CMTS to provide only UGS services. This will prevent a CM that
registered for USG-AD services from being able to obtain upstream transmission opportunities, resulting
in a significant loss of bandwidth when a large number of CMs are requesting UGS-AD service flows.
Examples The following example shows the inactivity timer being set to 20 seconds:
Router(config)# cable service flow inactivity-threshold 20
Router(config)#
The following command disables the inactivity timer, so that the service flow remains UGS, even during
periods of inactivity:
Router(config)# no cable service flow inactivity-threshold
Router(config)#
Syntax Description minutes Specifies service-flow inactivity-timeout in minutes. Valid range is 1 to 120 minutes. Default
value is 30 minutes.
Usage Guidelines Resources such as service identifiers (SIDs) and bandwidth are dynamically allocated by a CM using
Dynamic Service Addition (DSA) transaction. If the CM fails to release these resources by issuing a
Dynamic Service Deletion (DSD), then the resources might be locked indefinitely. Use this command to
release unused resources.
Examples The following example shows how to set the inactivity timeout for dynamic service flows to 2 minutes.
Once this setting is specified, any dynamic SID that does not show any activity in 2 minutes will be
deleted.
Router(config)# cable service-flow inactivity-timeout 2
The following example shows how to set the inactivity timeout back to the default value of 30 minutes:
Router(config)# cable service-flow inactivity-timeout
Command Description
cable qos profile Configures a QoS profile.
show controllers cable Displays QoS profiles.
Usage Guidelines This command will redirect the CMs matching a particular service-type identifier to downstream
frequency. Multiple service types can be redirected to one frequency. However, one service type cannot
be redirected to multiple DS frequencies.
Examples The following example shows how to redirect the CMs matching the service type to downstream
frequency:
Router(config)# cable service type commercial ds-frequency 519000000
Syntax Description value Experimental bit for MPLS labels. Valid values are from 0 to 7.
Command Default If this command is not used, the experimental bits on the MPLS label are set to zero.
Usage Guidelines The experimental bits are set for all inner and outer MPLS labels for the egress Layer 2 VPN traffic on
the WAN interface.
Examples The following example shows how to set an experimental bit for MPLS labels on a Cisco uBR10012
router:
Router# configure terminal
Router(config)# cable l2vpn 0000.396e.6a68 customer1
Router(config-l2vpn)# service instance 2000 Ethernet
Router(config-ethsrv)# xconnect 101.1.0.2 221 encapsulation mpls pw-type 4
Router(config-ethsrv)# cable set mpls-experimental 7
cable sflog
To enable service flow logging and to configure the number and duration of entries in the log, use the
cable sflog command in global configuration mode. To disable service flow logging, use the no form of
the command.
no cable sflog
Syntax Description max-entry number Specifies the maximum number of entries in the service flow log. When the
log becomes full, the oldest entries are deleted to make room for new entries.
The valid range is 0 to 59999, with a default of 0 (which disables service
flow logging).
Note The max-entry value applies to the entire chassis on the
Cisco uBR7100 series and Cisco uBR7200 series routers, but applies
to individual cable line cards on the Cisco uBR10012 router.
entry-duration time Specifies how long, in seconds, entries can remain in the service flow log.
The CMTS deletes entries in the log that are older than this value. The valid
range is 1 to 86400 seconds, with a default value of 3600 seconds (1 hour).
Defaults max-entry = 0 (service flow logging is disabled) and entry-duration = 3600 seconds
Usage Guidelines A DOCSIS specification currently being developed requires the DOCSIS CMTS to maintain a log table
that contains entries of deleted service flows. The cable sflog command enables the logging of deleted
service flows in this table and also sets the maximum number of entries in the log. When the log becomes
full, the oldest entries are deleted to make room for the newest ones.
This command also configures how long each entry can remain in the log. When an entry has been in the
table for the specified time, the CMTS deletes it, even if the log is not currently full.
To display the service flow log, use SNMP commands to display the docsQosServiceFlowLogEntry
entries in the docsQosServiceFlowLogTable table. These attributes are defined in the Data Over Cable
System Interface Specification Quality of Service Management Information Base (DOCSIS-QOS MIB)
internet draft.
Cisco IOS Release 12.2(15)BC1 supports version 4 of this DOCSIS-QOS MIB draft, which is available
on the IETF Internet-Drafts web site:
http://http://www.ietf.org/ID.html
Note At the time of this document’s release, the DOCSIS-QOS MIB is still in draft form and is therefore
subject to change in future releases of Cisco IOS software.
The max-entry value specified by this command applies to the entire chassis for the Cisco uBR7100
series and Cisco uBR7200 series routers, but to individual line cards on the Cisco uBR10012 router.
However, the Cisco uBR10012 router still maintains only one log table for all deleted service flows.
For example, if the max-entry value is set to 10,000 on a Cisco uBR7200 series router, the service flow
log table holds a maximum of 10,000 entries for all cable line cards in the chassis. If the max-entry value
is set to 10,000 on a Cisco uBR100012 router that has four cable line cards installed, the service flow
log table holds a maximum of 40,000 entries, with each cable line card having a maximum of 10,000
entries each.
Examples The following example shows how to enable service flow logging with a maximum of 2,000 entries in
the log, and with each entry remaining in the log for a maximum of 2 hours (7200 seconds):
Router(config)# cable sflog max-entry 2000 entry-duration 7200
The following example shows how to set the max-entry value to its default of 0 and disable service flow
logging:
Router# configure terminal
Router(config)# no cable sflog
Router(config)# exit
Router#
cable shared-secondary-secret
To configure one or more secondary shared-secret keys that CMs can use to successfully process the
DOCSIS configuration file and register with the CMTS, use the cable shared-secondary-secret
command in cable interface configuration mode. To remove the secondary shared secrets, use the no
form of this command.
Syntax Description index index-num Specifies the order in which the CMTS will use the secondary shared-secrets
to verify the CM during the registration process. The valid range is 1 to 16.
0 (Optional) Specifies that an unencrypted message will follow.
7 (Optional) Specifies that an encrypted message will follow.
Note As a general rule, the 7 option is not used by users at the command
line because it requires a pre-encrypted password. Typically, the 7
option is useful only when cutting and pasting commands from
another router’s configuration file.
authentication-key Text string specifying the shared secret string. When you also use the service
password-encryption command, the key is stored in encrypted form. The
text string can be any arbitrary string up to 80 characters in length.
Defaults No secondary shared secret is used. If no encryption option is specified, the key is stored in the
configuration file as encrypted text if the service password-encryption command has also been given.
Usage Guidelines The cable shared-secondary-secret command can be used to supplement the cable shared-secret
command so as to prevent unauthorized interception and alteration of the DOCSIS configuration file that
is downloaded to the CM during the registration process. The DOCSIS specification allows for a CM
and CMTS to use a shared secret (a secret encryption string) to calculate the MD5 Message Integrity
Check (MIC) value for the DOCSIS configuration file that is downloaded to the CM.
The CM must use the proper shared secret encryption string to successfully decrypt and process the
configuration file, and then register with the CMTS. If the CM does not have the proper encryption
string, it will be unable to calculate the proper MIC value, and the show cable modem command will
show reject(m) for the modem to indicate a MIC authentication failure.
Note At any particular time, the majority of CMs should use the primary shared secret to avoid
excessive registration times.
• Create DOCSIS configuration files that use the shared-secret encryption string to create the MD5
MIC value. This can be done using the Cisco DOCSIS Configurator tool by entering the
shared-secret string in the CMTS Authentication field in the Miscellaneous parameters.
Tip The shared-secret string itself is not saved in the DOCSIS configuration file, so you must re-enter the
string in the CMTS Authentication field whenever you create or edit a DOCSIS configuration file using
the Cisco DOCSIS Configurator tool.
• Use the cable shared-secondary-secret command to configure the cable interfaces with one or
more matching shared-secret strings. The string configured on an interface must match the string
used to create the DOCSIS configuration files downloaded to the CMs on that interface, or the CMs
will not be able to register. You can use different shared secrets for each interface, if you are also
using a different set of configuration files for each interface.
• To encrypt the shared-secret strings in the CMTS configuration, you must include the service
password-encryption global configuration command in the router’s configuration.
Note You cannot use the shared secret feature with the files created by the internal DOCSIS configuration file
editor (cable config-file command).
Examples The following example shows how to specify multiple secondary shared-secret string using encrypted
keys:
Router# config t
Router(config)# service password-encryption
Router(config)# int c6/0
Router(config-if)# cable shared-secret n01jk_1a
Router(config-if)# cable shared-secondary-secret index 1 cabl3-x21b
Router(config-if)# cable shared-secondary-secret index 2 dasc9_ruld55ist5q3z
Router(config-if)# cable shared-secondary-secret index 3 j35u556_x_0
Router(config-if)# exit
Router(config)# exit
Router# show running-config | include shared
cable shared-secret 7 1407513181A0F13253920
cable shared-secondary-secret 7 14031A021F0D39263D3832263104080407
cable shared-secondary-secret 7 071B29455D000A0B18060615142B38373F3C2726111202431259545D6
cable shared-secondary-secret 7 0501555A34191B5F261D28420A555D
Router#
Note In this example, the shared-secret strings are initially entered as clear text, but because the service
password-encryption command has been used, the strings are encrypted in the configuration file.
cable shared-secret
To configure an authentication shared-secret encryption key that CMs must use to successfully process
the DOCSIS configuration file and register with the CMTS, use the cable shared-secret command in
cable interface configuration mode. To disable the use of a shared-secret key during the CM registration
phase, use the no form of this command.
no cable shared-secret
Syntax Description 0 (Optional) Specifies that an unencrypted message (clear text) will follow.
7 (Optional) Specifies that an encrypted message will follow.
Note As a general rule, the 7 option is not used by users at the command
line because it requires a pre-encrypted password. Typically, the 7
option is useful only when cutting and pasting commands from
another router’s configuration file.
authentication-key Text string specifying the shared secret string. When you also use the service
password-encryption command, the key is stored in encrypted form. The
text string can be any arbitrary string up to 80 characters in length.
Defaults No shared-secret encryption key is used during registration, only the default DOCSIS MD5-encrypted
checksum. When cable shared-secret is given without specifying an encryption option, the key is stored
in the configuration file as an encrypted password if the service password-encryption command has
also been given.
Usage Guidelines The cable shared-secret command can be used to prevent unauthorized interception and alteration of
the DOCSIS configuration file that is downloaded to the CM during the registration process. The cable
shared-secret command specifies a secret encryption string that the CMTS uses to calculate the MD5
Message Integrity Check (MIC) value that is appended to every DOCSIS configuration file and that the
CM and CMTS use to verify the file’s integrity.
The CM must use the shared secret encryption string to successfully decrypt and process the
configuration file, and then register with the CMTS. If the CM does not have the proper encryption
string, it will be unable to calculate the proper MIC value, and the show cable modem command will
show reject(m) for the modem to indicate a MIC authentication failure.
Note The shared-secret string itself is not saved in the DOCSIS configuration file, so you must
re-enter the string in the CMTS Authentication field whenever you create or edit a DOCSIS
configuration file using the Cisco DOCSIS Configurator tool.
• Use the cable shared-secret command to configure the cable interfaces with a matching
shared-secret string. The string configured on an interface must match the string used to create the
DOCSIS configuration files downloaded to the CMs on that interface, or the CMs will not be able
to register. You can use different shared secrets for each interface, if you are also using a different
set of configuration files for each interface.
• To encrypt the shared-secret string in the CMTS configuration, you must include the service
password-encryption global configuration command in the router’s configuration.
Note You cannot use the shared secret feature with the files created by the internal DOCSIS configuration file
editor (cable config-file command).
Note In Cisco IOS Release 12.2(8)BC2 and later releases, you can also use the cable
shared-secondary-secret command to specify multiple shared-secret strings, so that you can gradually
phase in a new shared secret string.
Note This change affects only the encryption of the passwords that are stored in the configuration file. It does
not affect the actual encryption that is used between the CMTS and CMs, so you do not need to change
the shared secret in the DOCSIS configuration files for the CMs.
Examples The following example shows how to specify a shared-secret string using an encrypted key:
Router# config t
Router(config)# service password-encryption
Router(config)# int c6/0
Router(config-if)# cable shared-secret password
Router(config-if)# exit
Router(config)# exit
Router# show running-config | include shared
cable shared-secret 7 1407513181A0F13253920
Router#
Note In this example, the shared-secret string is initially entered as clear text, but because the service
password-encryption command has been used, the string is encrypted in the configuration file.
The following example shows how to remove the use of a shared-secret encryption key on a cable
interface. That particular interface then ignores any shared-secret that is used when calculating the MD5
checksum:
Router# config t
Router(config)# int c6/0
Router(config-if)# no cable shared-secret
Router(config-if)# end
Router#
cable sid-cluster-group
To configure a SID cluster group on a cable interface line card, use the cable sid-cluster-group
command in cable interface configuration mode. To disable the configuration, use the no form of this
command.
Syntax Description dynamic If specified, the SID cluster is dynamically derived based on the service flow
rate.
req-multiplier value Specifies the queue-depth request byte multiplier. Valid values are 1, 2, 4, 8,
and 16. A cable modem uses queue-depth based requesting for all bandwidth
requests, if the Multiple Transmit Channel mode is enabled.
num-of-cluster number Specifies the number of SID clusters. Valid values are from 1 to 8. The
default value is 1.
Usage Guidelines The SID cluster configuration may impact overall system performance. So we recommend not to
customizing SID cluster values unless justified. The default SID cluster configuration will meet most of
the requirements.
If the cable sid-cluster-group command is not used, the router accepts the default SID cluster
configuration. By default, only one SID cluster is configured.
Examples The following example shows how to configure a SID cluster on a cable interface in slot 5, subslot 1,
and port 0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable sid-cluster-group
Router(config-if)# cable sid-cluster-group dynamic
Router(config-if)# cable sid-cluster-group req-multiplier 8
Router(config-if)# cable sid-cluster-group num-of-cluster 3
cable sid-cluster-switching
To specify Service ID (SID) cluster switchover criteria on a cable interface line card, use the
cable sid-cluster-switching command in cable interface configuration mode. To disable the
configuration, use the no form of this command.
Syntax Description max-outstanding-byte (Optional) Specifies the total size, in bytes, for outstanding requests using
value the SID cluster. The valid values are from 0 to 4294967295.
max-request value (Optional) Specifies the maximum number of requests that can be made
using the SID cluster. The valid values are from 0 to 255. The default value
is 1.
max-time milliseconds (Optional) Specifies the total time, in milliseconds, that a service flow can
continue to use the SID cluster for bandwidth requests. The valid values are
from 0 to 65535.
max-total-byte value (Optional) Specifies the total number of bytes that can be requested using the
SID cluster. The valid values are from 0 to 4294967295.
Usage Guidelines If the service flow has only one SID cluster and the SID cluster switchover criterion limit is met, the
cable modem stops sending bandwidth requests until the SID cluster is cleared.
The SID cluster configuration along with switchover criterion may impact overall system performance.
So we recommend not to customizing switchover criterion unless justified. The default switchover
criterion will meet most of the requirements. If the cable sid-cluster-switching command is not used,
the router accepts the default SID cluster switchover criterion. That is only one request can be made
using the SID cluster.
Examples The following example shows how to specify SID cluster switchover criteria on a cable interface in slot
5, subslot 1, and port 0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable sid-cluster-switching
Router(config-if)# cable sid-cluster-switching max-outstanding-byte 4444
Router(config-if)# cable sid-cluster-switching max-request 222
Router(config-if)# cable sid-cluster-switching max-time 444
Router(config-if)# cable sid-cluster-switching max-total-byte 67890
cable source-verify
To enable verification of IP addresses for CMs and CPE devices on the upstream, use the cable
source-verify command in cable interface or subinterface configuration mode. To disable verification,
use the no form of this command.
no cable source-verify
Syntax Description dhcp (Optional) Specifies that queries will be sent to verify unknown source
IP addresses in upstream data packets.
Note Do not enable the local DHCP server on the Cisco CMTS and
configure local DHCP address pools, using the ip dhcp pool
command, when using this option, because this prevents DHCP
address validation.
leasetimer value (Optional) Specifies the time, in minutes, for how often the router
should check its internal CPE database for IP addresses whose lease
times have expired. The valid range for value is 1 to 240 minutes, with
a default of 60 minutes.
Note The leasetimer option takes effect only when the dhcp option
is also used on an interface. Also, this option is supported only
on the master interface and cannot be configured on
subinterfaces. Configuring it for a master interface
automatically applies it to all subinterfaces.
Command Default Disabled. When the dhcp option is specified, the leasetimer option defaults to 60 minutes.
Note Configuring the cable source-verify command on the master interface of a bundle will
configure it for all of the slave interfaces in the bundle as well.
Release Modification
12.2(15)BC2 Support for verifying CMs and CPE devices that are on a different subnet
than the cable interface was enhanced to use Reverse Path Forwarding
(RFP).
12.3(9a)BC Cisco IOS Release 12.3(9a)BC adds the option of using a per SID basis for
deriving lease queries from CPE devices. This release also introduces a
global rate limit for lease queries initiated by downstream traffic.
Usage Guidelines The cable source-verify command helps to prevent the spoofing of IP addresses by CMs or their CPE
devices by verifying that the upstream packets coming from each CM are known to be associated with
the IP address in that packet. Packets with IP addresses that do not match those associated with the CM
are dropped.
In order to protect the Cisco CMTS from denial of service attacks, Cisco IOS Release 12.3(9a)BC adds
the option of using a per SID basis for deriving lease queries from CPE devices. This release also
introduces a global rate limit for lease queries initiated by downstream traffic. These enhancements
reduce the CPU utilization of DHCP Receive and ISR processes when the Cisco CMTS is configured
with the cable source-verify dhcp and no cable arp commands.
Caution In current Cisco IOS Release 12.1 EC and 12.2 BC software images, the Cisco CMTS can crash with a
“bus error exception” when the cable source-verify command is configured on a cable interface, and the
routing configuration of that interface is being changed while traffic is passing through the interface. To
avoid this problem, temporarily disable this feature (using no cable source-verify) on the interface
before you configure the routing parameters. Then after you have finished the routing configuration,
reenable the feature using the cable source-verify command. Alternatively, you can also change the
routing parameters when the interface is not passing traffic (such as when the interface is shut down).
Caution In Cisco IOS Release 12.2(15)BC1 and earlier releases, you cannot use the cable source-verify
command on a Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, or Cisco uBR-MC5X20S/U cable
interface line card that is using an MPLS/VPN configuration when you are also using duplicate or
overlapping IP address ranges for CPE devices on different cable interfaces/subinterfaces. To use the
cable source-verify command, you must assign unique IP addresses for each cable interface or
sub-interface. This is being tracked as caveat CSCed53355.
The Cisco CMTS maintains a database that links the MAC and IP addresses of known CPE devices with
the CMs that are providing network access for those CPE devices. The CMTS typically populates this
database with information obtained by examining the Dynamic Host Configuration Protocol (DHCP)
packets sent between the CPE devices and the DHCP server. Other IP traffic provides information about
which CMs service which CPE devices.
After the cable source-verify command is issued, every IP upstream packet is examined. If the IP and
MAC addresses of the CPE device are already associated with a known, online CM, it is allowed through.
If not, the source IP address is examined to determine if it belongs to the cable network. If so, and if the
dhcp option is not used, the packet is allowed through.
Note The dhcp option automatically blocks all statically-assigned IP addresses unless the DHCP server has
been configured to recognize those addresses and respond with the appropriate LEASEQUERY
response.
The cable source-verify command by itself prevents someone from stealing another customer’s IP
address. The cable source-verify dhcp command adds another level of security by refusing access to
any CPE device with an IP address that has not been assigned by the DHCP server.
Note This dhcp option requires that the DHCP server support the LEASEQUERY message. The
Cisco Network Registrar (CNR) supports LEASEQUERY in version 3.01(T) and above. The
LEASEQUERY message is currently defined in an IETF draft, which is dated October, 2003 and
available at the following URL:
http://www.ietf.org/internet-drafts/draft-ietf-dhc-leasequery-06.txt
Caution Do not enable the local DHCP server on the Cisco CMTS and configure local DHCP address pools, using
the ip dhcp pool command, when you are also enabling the cable source-verify dhcp command,
because the DHCP server on the Cisco CMTS can intercept the LEASEQUERY messages and prevent
them from reaching the external DHCP server. This in turn prevents address validation from succeeding
because the DHCP server on the Cisco CMTS does not support LEASEQUERY messages.
Note When the cable source-verify dhcp feature is enabled, and a statically-defined IP address has been
added to the CMTS for a CM using the cable trust command to override the cable source-verify dhcp
checks for this device, packets from this CM will continue to be dropped until an entry for this CM is
added to the ARP database of the CMTS. To achieve this, disable the cable source-verify dhcp feature,
ping the CMTS from the CM to add an entry to the ARP database, and re-enable the cable source-verify
dhcp feature.
from communicating until it makes another DHCP request. This prevents users from treating
DHCP-assigned addresses as static addresses, as well as from using IP addresses that were previously
assigned to other devices.
Note The leasetimer option is active only if you have also specified the cable source-verify dhcp command
for the cable interface. If the dhcp option is not used, the leasetimer option has no effect. In addition,
the leasetimer option can be configured only on an interface, not a subinterface. Applying it to a master
interface automatically applies it to all subinterfaces.
The leasetimer option allows you to configure how often the timer checks the lease times, so as to
specify the maximum amount of time a CPE device can use an IP address that was previously assigned
by the DHCP server but whose lease time has since expired. The time period can range from 1 minute
to 240 minutes (4 hours), with a grace period of 2 minutes to allow a PC enough time to make a DHCP
request to renew the IP address. To turn off the timer, so that the CMTS no longer checks the lease times,
issue the cable source-verify command without the dhcp option, or turn off the feature entirely with the
no cable source-verify command.
Note You must enable RPF before running the cable source-verify command to verify IP addresses on
subinterfaces.
Examples The following example shows how to enable RPF before running the cable source-verify command to
verify IP addresses on subinterfaces:
Router# configure terminal
Router(config)# ip cef
Router(config)# interface cable 4/0
Router(config-if)# ip verify unicast source reachable-via rx
Note Beginning with Cisco IOS Release 12.2(33)SCA, ip verify unicast source reachable-via rx command
must be used with the allow-default keyword.
The following example shows how to turn on CM upstream verification and configures the Cisco CMTS
router to send DHCP LEASEQUERIES to verify unknown source IP addresses in upstream data packets:
Router# configure terminal
Router#(config) interface cable 4/0
Router(config-if)# cable source-verify dhcp
Router(config-if)#
The following example shows how to enable the leasetimer feature so that every two hours, the CMTS
checks the IP addresses in the CPE database for that particular interface for expired lease times:
Router# configure terminal
Router#(config) interface c1/0
Router(config-if)# cable source-verify dhcp
Router(config-if)# cable source-verify leasetimer 120
Router(config-if)#
The following example shows how to configure the cable interface so that the CMTS can verify IP
addresses that are on a different subnet than the one that the cable interface is using:
Router# configure terminal
Router(config)# ip cef
Router#(config) interface c7/0/0
Router(config-if)# ip verify unicast source reachable-via rx
Router(config-if)# cable source-verify dhcp
Router(config-if)#
The following example shows the error message that is displayed if you try to configure the leasetimer
option on a subinterface, instead of an interface:
Router# configure terminal
Router#(config) interface c1/0.1
Router(config-subif)# cable source-verify dhcp
Router(config-subif)# cable source-verify leasetimer 120
% Invalid input detected at '^' marker.
Router(config-subif)#
Syntax Description threshold Maximum number of DHCP lease queries allowed per SID for each interval period. The
valid range is 0 to 255 lease queries.
interval Time period, in seconds, over which lease queries should be monitored. The valid range is
1 to 10 seconds.
Usage Guidelines When the cable source-verify dhcp and no cable arp commands are configured on a cable interface,
the Cisco CMTS router sends a DHCP LEASEQUERY request to the DHCP server to verify unknown
IP addresses that are found in packets to and from customer premises equipment (CPE) devices that are
using the cable modems on the cable interface. The DHCP server returns a DHCP ACK message with
the MAC address of the CPE device that has been assigned this IP address, if any. The router can then
verify that this CPE device is authorized to use this IP address, which prevents users from assigning
unauthorized IP addresses to their CPE devices.
Problems can occur, though, when viruses, denial of service (DoS) attacks, and theft-of-service attacks
scan ranges of IP addresses, in an attempt to find unused addresses. This type of activity can generate a
large volume of DHCP LEASEQUERY requests, which can result in high CPU utilization and a lack of
available bandwidth for other customers.
To prevent such a large volume of LEASEQUERY requests on all downstreams in the Cisco CMTS
router, use the cable source-verify leasequery-filter downstream command. After configuring this
command, the Cisco CMTS allows only a certain number of DHCP LEASEQUERY requests in the
downstream direction within each interval time period.
For example, the cable source-verify leasequery-filter downstream 5 10 command configures the
router so that it allows a maximum of 5 DHCP LEASEQUERY requests every 10 seconds for each SID
on the downstream direction. This command applies to all downstream cable interfaces in the router.
Note The cable source-verify leasequery-filter downstream command enables DHCP lease query filtering
on all downstreams, but the actual filtering does not begin until the cable source-verify dhcp command
and the no cable arp command are configured on a particular downstream. You can configure these
commands on either the downstream’s main interface, or on a subinterface for the downstream. If these
commands are configured on a subinterface, however, the lease query filtering occurs only for cable
modems using that subinterface.
Tip Use the cable source-verify leasequery-filter upstream command to filter DHCP LEASEQUERY
requests in the upstream direction.
Examples The following example shows how to configure the Cisco CMTS router so that it allows a maximum of
10 DHCP lease query requests per SID over each five-second interval on all downstream cable interfaces.
This example also shows the configuration of cable source-verify dhcp and no cable arp commands on
a cable interface, which are required to use this feature.
Router# configure terminal
Router(config)# cable source-verify leasequery-filter downstream 10 5
Router(config)# interface cable 5/1/0
Router(config-if)# cable source-verify dhcp
Router(config-if)# no cable arp
Router(config-if)#
Syntax Description threshold Maximum number of DHCP lease queries allowed per SID for each interval
period. The valid range is 0 to 20 lease queries.
interval Time period, in seconds, over which lease queries should be monitored. The
valid range is 1 to 5 seconds.
Usage Guidelines When the cable source-verify dhcp and no cable arp commands are configured on a cable interface,
the Cisco Cable Modem Termination System (CMTS) router sends a DHCP LEASEQUERY request to
the DHCP server to verify unknown IP addresses that are found in packets to and from customer
premises equipment (CPE) devices that are using the cable modems on the cable interface. The DHCP
server returns a DHCP ACK message with the MAC address of the CPE device that has been assigned
this IP address, if any. The router can then verify that this CPE device is authorized to use this IP address,
which prevents users from assigning unauthorized IP addresses to their CPE devices.
Problems can occur, though, when viruses, denial of service (DoS) attacks, and theft-of-service attacks
scan ranges of IP addresses, in an attempt to find unused addresses. This type of activity can generate a
large volume of DHCP LEASEQUERY requests, which can result in high CPU utilization and a lack of
available bandwidth for other customers.
To prevent such a large volume of LEASEQUERY requests on the upstreams on a cable interface, use
the cable source-verify leasequery-filter upstream command. After configuring this command, the
Cisco CMTS allows only a certain number of DHCP LEASEQUERY requests in the upstream direction
within each interval time period.
For example, the cable source-verify leasequery-filter upstream 5 5 command configures the router
so that it allows a maximum of 5 DHCP LEASEQUERY requests every 5 seconds for each SID on the
upstream direction. This command applies to all upstreams on the cable interface.
Note The cable source-verify leasequery-filter upstream command enables DHCP lease query filtering on
all upstreams on a cable interface, but the actual filtering does not begin until the cable source-verify
dhcp command and the no cable arp command are configured on the upstream’s associated downstream
interface. You can configure these commands on either the downstream’s main interface, or on a
subinterface for the downstream. If these commands are configured on a subinterface, however, the lease
query filtering occurs only for cable modems using that subinterface.
Note If using cable interface bundling, configure the cable source-verify leasequery-filter upstream
command on all master and slave interfaces.
Tip Use the cable source-verify leasequery-filter downstream command to filter DHCP LEASEQUERY
requests in the downstream direction.
Examples The following example shows how to configure the Cisco CMTS router so that it allows a maximum of
five DHCP lease query requests per SID over each two-second interval on all upstreams on a particular
cable interface. This example also shows the configuration of cable source-verify dhcp and no cable
arp commands on the cable interface, which are required to use this feature.
Router# configure terminal
Router(config)# interface cable 6/0
Router(config-if)# cable source-verify dhcp
Router(config-if)# cable source-verify leasequery-filter upstream 5 2
Router(config-if)# no cable arp
Router(config-if)#
Syntax Description group-number Specifies the spectrum group for which you are specifying a parameter
value or specifies the number of the spectrum group you wish to
remove from your router configuration. Valid range is from 1 to 32, or
from 1 to 40, depending on the Cisco IOS software release.
time day hh:mm:ss (Optional) for scheduled spectrum groups, enter the day of the week
(Sun—Sat) and the time of day that the frequency and input power
level should change.
frequency up-freq-hz Specifies a center frequency for the upstream group. The valid range is
5,000,000 Hz to 42,000,000 Hz (DOCSIS), 55,000,000 Hz (Japan), or
65,000,000 (EuroDOCSIS).
Note You can enter this command multiple times for the same
spectrum group to create a group of individual frequencies to
be used for frequency hopping.
band up-freq1-hz up-freq2-hz Specifies a range of center frequencies the Cisco CMTS can scan to
find an acceptable channel to which the spectrum group may hop. The
valid range for up-freq1-hz is 5,000,000 Hz to 42,000,000 Hz
(DOCSIS), 55,000,000 Hz (Japan), or 65,000,000 (EuroDOCSIS), but
up-freq2-hz must be greater than up-freq1-hz.
Note When creating spectrum groups for cable line cards that
support Advanced Spectrum Management (Cisco
uBR10-MC16S, uBR10-MC16U/X, uBR10-MC28U/X, and
uBR10-MC5X20S/U), use the band option. The frequency
option is not supported for these types of line cards.
pwr-lvl-dbmv (Optional) Specifies the nominal input power level. The valid range is
–10 to +25 dBmV, with a default of 0 dBmV. Some cable plants might
want to change only the input power level, and not the frequency, on a
daily time schedule.
Command Default If not specified, the group is set for a nominal input power level of 0 dBmV and the group is not
scheduled for automatic frequency or power changes.
Usage Guidelines Frequency agility is configured and activated using spectrum groups that are controlled by the spectrum
manager. You can create from 1 to 32, or from 1 to 40, spectrum groups for each cable modem card
upstream port, depending on the Cisco IOS software release.
To create spectrum groups, specify a list of upstream frequencies and nominal power levels that each
spectrum group can use when an upstream frequency change is necessary. Each spectrum group should
have its own list of upstream frequencies. At 1.6 MHz, the valid range is –10 dBmV to 25 dBmV. The
power level value should be changed only if you want to change only the power level as part of spectrum
management. The standard power level is 0 dBmV.
The the cable spectrum-group command sets the center frequency for the upstream, but the total
frequency bandwidth that is actually used depends on the channel width. Table 0-12 shows the possible
center frequencies for each channel width, for both DOCSIS and EuroDOCSIS cable interfaces.
The allowable range for the upstream channel frequency depends on the cable interface line card and
Cisco IOS software release being used. See Table 2-11 for the currently supported values.
Table 0-13 Allowable Frequency Range for the cable upstream frequency Command
Table 0-13 Allowable Frequency Range for the cable upstream frequency Command
Note If both an Cisco uBR-MC16E cable interface line card and a Cisco uBR-MC16C or a
Cisco uBR-MC16S cable interface line card are present in the chassis, a spectrum group in the 42-MHz
to 65-MHz range should not be assigned.
Tip Cisco cable interface line cards always program the upstream’s center frequency in 16 KHz increments,
and this is the frequency displayed by the show controller cable upstream command. For example, if
you use the cable upstream frequency command to specify a center frequency of 27 MHz (cable
upstream x frequency 27000000), the actual center frequency will be 27.008 MHz, which is the next
highest 16 KHz boundary.
You must repeat this command for each frequency or power level that you want to add to a spectrum
group’s list of valid values.
After you have created one or more spectrum groups for your cable network, you can add characteristics
to them, providing you with more definitive control over frequency usage and frequency hopping.
The cable interface does not operate until you either create and configure a spectrum group or set a fixed
upstream frequency. See the cable upstream channel-width command.
Examples The following example shows how to configure spectrum group 1 with an upstream frequency of
6,500,000 Hz and a default power level of 0 dBmV:
Router(config)# cable spectrum-group 1 frequency 6500000
The following example shows how to add the upstream frequency 7,000,000 Hz to the list of valid
frequencies with a default power level of 0 dBmV for spectrum group 1:
Router(config)# cable spectrum-group 1 frequency 7000000
The following example shows how to configure spectrum group 2 with an upstream frequency
7,500,000 Hz and change the power level to 5 dBmV:
Router(config)# cable spectrum-group 2 frequency 7500000 5
The following example shows how to configure spectrum group 3 with an upstream band of 12,000,000
to 18,000,000 Hz and default power level of 0 dBmV:
Router(config)# cable spectrum-group 3 band 12000000 18000000
The following example shows how to add the upstream band 20,000,000 to 24,000,000 Hz to the list of
valid bands with a change in the power level of 13 dBmV for spectrum group 3:
Router(config)# cable spectrum-group 3 band 20000000 24000000 13
The following example shows how to configure a continuous band between 5,000,004 and
40,000,000 Hz for scheduled spectrum group 4 with a default power level of 0 dBmV. The spectrum
group will be available to the spectrum group starting at 12:00 p.m. local time each Monday:
Router(config)# cable spectrum-group 4 time Monday 12:00:00 band 5000004 40000000
The following example shows how to add the upstream frequency 9,500,000 Hz to the list of valid
frequencies and change the nominal power level to 5 dBmV. The spectrum manager adjusts frequencies
and power levels on this group at 2:00 a.m. local time each day:
Router(config)# cable spectrum-group 3 time 02:00:00 frequency 9500000 5
The following example shows how to remove a specified spectrum group from your configuration:
Router(config)# no cable spectrum-group 3
Router(config)#
Syntax Description group-number Specifies the spectrum group that should be used as the default group for the upstreams
on this cable interface. The valid range is from 1 to 32, or from 1 to 40, depending on
the Cisco IOS software release.
Usage Guidelines This command assigns a default spectrum group to all of the upstreams on the cable interface. All
upstreams on the interface use this spectrum group unless you override this configuration, using one of
the following commands:
• To assign a different spectrum group to a particular upstream, use the cable upstream
spectrum-group command.
• To assign a new frequency to a particular upstream, use the cable upstream frequency command.
These two commands override the cable spectrum-group command for the particular upstreams to
which they are applied. The remaining upstreams in the interface, however, continue to use the default
configuration that is specified by the cable spectrum-group command.
Tip You must first create and configure the spectrum groups before you can assign them to an interface. To
create and configure spectrum groups, use the set of cable spectrum-group commands that are available
in global configuration mode.
Examples The following example shows how to assign spectrum group 1 to all of the upstreams on the cable
interface in slot 3/0:
Router(config)# interface cable 3/0
Syntax Description groupnum Spectrum group number. Valid values are from 1 to 32, or from 1 to 40, depending on the
Cisco IOS software release.
seconds Specifies the frequency-hop time period in seconds. Valid values are from 1 to 3600
seconds (before Cisco IOS Release 12.2(8)BC1), or from 1 to 300 seconds (Cisco IOS
Release 12.2(8)BC1 or later).
Usage Guidelines The cable spectrum-group hop period command defines the minimum amount of time that must pass
between upstream frequency hops. If ingress noise becomes excessive on a particular upstream, you can
set this time period to a smaller value, so as to allow frequency hopping to continue more rapidly until a
clear channel is found. Conversely, if the problem appears to be a transient condition, such as a defective CM
generating a large volume of errored packets, this time period can be increased to a larger value, so as to avoid
excessive frequency hopping by allowing more time between frequency hops.
On the Cisco uBR-MC1xC cards, the maximum recommended hop period is 20 seconds. On the
Cisco uBR-MC16S and Cisco uBR-MC5X20S/U cards, the minimum recommended hop period is 25
seconds and the maximum recommended hop period is 35 seconds.
In Cisco IOS Release 12.2(15)BC2, the Cisco CMTS adaptively increases the hop period from the
user-defined value to the maximum value (300 seconds) whenever an upstream does not currently have
any CMs ranging on it, so as to avoid unnecessary frequency hopping. The user-defined value is restored
when a CM starts ranging on the upstream.
Note The hop period should be set to at least 25 seconds on the Cisco uBR-MC16S and
Cisco uBR-MC5X20S/U cards so that transient network problems that are unrelated to ingress noise do
not generate unnecessary frequency hops.
Examples The following example shows how to change the minimum frequency-hop interval to 60 seconds. This
means that frequency hops for this spectrum group cannot occur more quickly than once every 60
seconds, even if other characteristics, such as exceeding the CNR or FEC threshold values, would
normally trigger the hop.
Router# configure terminal
Router(config)# cable spectrum-group 1 hop period 60
Router(config)#
Syntax Description groupnum Spectrum group number. Valid values are from 1 to 32, or from 1 to 40, depending on the
Cisco IOS software release.
percent (Optional) Specifies the frequency hop threshold as a percentage of station maintenance
messages that are lost. Valid range is from 1 to 100 percent.
Usage Guidelines The Cisco CMTS sends a station maintenance message to each CM at least once every 25 to 30 seconds.
If a CM does not respond to a station maintenance message within that time period, the CMTS then
resends station maintenance messages at a faster rate (typically one second apart) in an attempt to restore
connectivity with the CM.
Station maintenance messages can be lost because CMs have lost connectivity with the CMTS, or
because ingress noise and other factors are causing dropped and errored packets. Downstream noise can
also affect the delivery of station maintenance messages. When a user-configurable percentage of station
maintenance messages are lost, the CMTS hops to a new upstream frequency to improve connectivity
and sends out an Upstream Channel Descriptor (UCD) update to the CMs to inform them of the change.
The optimal hop threshold value depends on several factors, including the quality of the upstream return
path and the number of CMs on the upstream. In addition, the hop threshold works together with the hop
period so that transient network problems do not generate an unnecessary number of frequency hops.
Ideally, the hop threshold should be set low enough so that the frequency hop can occur before a
significant number of CMs go offline, but not so low that it generates frequency hops that are not needed.
For example, if the hop threshold is at its default of 20 percent and an upstream has 100 active CMs, a
power outage that affected 20 CMs would usually cause a frequency hop since this is a 20 percent loss
of CMs, which in turn would be responsible for at least 20 percent loss of station maintenance messages.
But in this situation, the frequency hop would be unneeded because changing the upstream frequency
could not correct the original problem (the power outage). If this were a common situation on this
upstream, the network administrator might increase the hop threshold so that the repeated power outages
would not generate unneeded frequency hops.
If, on the other hand, the power outage affected only 10 CMs, a frequency hop would not occur unless
another factor, such as ingress noise, created a sufficient loss of station maintenance messages to reach
the 20 percent threshold. In this situation, the default threshold of 20 percent might be sufficient.
Downstream problems can also generate frequency hops. For example, if 20 CMs were on a particularly
noisy downstream, over time they could miss a sufficient number of station maintenance messages to
generate a frequency hop. The network administrator could increase the hop threshold to limit the
possibility of frequency hops due to downstream impairments.
Also, faulty CMs could generate a frequency hop under certain conditions. For example, if a number of
faulty CMs generated a large number of uncorrectable forward error correction (FEC) errors or
otherwise missed 50 to 60 percent of their station maintenance messages, without actually going offline,
over time they could miss a sufficient number of station maintenance messages to cause a frequency hop
or modulation change. The network administrator could increase the hop threshold to prevent the CMTS
from generating a frequency hop or modulation change for problems such as these, which are unrelated
to actual noise on the upstream.
Note If a previous frequency hop had already occurred within the user-configurable hop period, the CMTS
will not immediately frequency hop. Instead, the CMTS would wait until the hop period expires, and if
the percentage of station maintenance messages still exceeds the hop threshold, the CMTS would
perform another frequency hop.
Tip When an upstream has 25 or fewer CMs (which is typical with lab and test environments), the CMTS
increases the rate at which it sends station maintenance messages to the CMs. This higher polling rate,
along with the small number of CMs, means that frequency hopping can occur more quickly than with
a normally loaded upstream, especially when a small number of CMs are powered down or generate
noisy traffic.
Note The DOCSIS specification states that when a CM misses 16 sequential station maintenance messages,
the CMTS should consider the CM offline and should stop sending station maintenance messages to that
CM. The CM must then reregister with the CMTS to resume connectivity.
Examples The following example shows how to set the threshold that triggers frequency hop to 25 percent of
station maintenance messages on the upstream that is assigned to spectrum-group 4:
Router# configure terminal
Router(config)# cable spectrum-group 4 hop threshold 25
Router(config)#
Syntax Description groupnum Spectrum group number. Valid values are from 1 to 32, or from 1 to 40, depending on the
Cisco IOS software release.
Command Default Upstream port frequency is the same for all ports in the spectrum group.
Usage Guidelines Because this command forces upstream ports to use the same spectrum, you must ensure that you do not
configure spectrum groups that have overlapping frequencies. To use shared spectrum groups, each
group must be using a discrete set of frequencies.
Caution Depending on the frequencies being used, and how cable modems are distributed across those
frequencies and among spectrum groups, switching from a group from shared to non-shared, or from
non-shared to shared, could cause CMs in the spectrum group to go offline and begin reranging
procedures. You should therefore use this command only during regularly schedule maintenance times,
so that a minimum number of online customers are affected.
Note This command does not enable any sort of load balancing on the shared upstreams.
Examples The following example shows how to specify that all the upstream ports for spectrum group 4 share the
same upstream frequency, and that these upstream frequencies are not assigned to other upstream
interfaces:
Router(config)# cable spectrum-group 4 shared
Router(config)#
cable submgmt default filter-group {cm | cpe | mta | stb | ps} {downstream | upstream} group-id
no cable submgmt default filter-group {cm | cpe| mta | stb | ps} {downstream | upstream}
group-id
Syntax Description no When used with the active and learnable options, the no form of the command sets
the default attributes to false. When used with the max-cpe and filter-group
options, the no form of the command sets the attribute to 0.
active (Optional) Sets the docsSubMgtCpeActiveDefault attribute, which controls
whether the CMTS manages the CPE devices for a particular CM—when set to
TRUE, the CMTS enforces the MAX-CPE value and the implemented filters. The
no cable submgmt default active command sets the default value to FALSE (the
original default), which turns off CPE management at the CMTS.
learnable (Optional) Sets the docsSubMgtCpeLearnableDefault attribute, which controls
whether the CMTS learns the CPE IP addresses for a particular CM—when set to
TRUE (the original default), the CMTS learns IP addresses up to the MAX-CPE
value. The no cable submgmt default learnable command sets the default value
to FALSE, which means that the IP address for each allowable CPE device must be
specified in the DOCSIS configuration file.
max-cpe cpe-num (Optional) Sets the docsSubMgtCpeMaxIpDefault attribute, which specifies the
default number of simultaneous IP addresses (CPE devices) permitted for the CM.
The possible range is 0 to 1024, where 0 specifies that all CPE traffic from the CM
is dropped. The default is 16.
filter-group Specifies a filter group, which can be applied to either upstream or downstream
traffic for either a CM or its CPE devices.
cm Specifies that the filter group applies to traffic to or from a CM.
cpe Specifies that the filter group applies to traffic to or from a CPE device.
mta Specifies that the filter group applies to traffic to or from a multimedia terminal
adaptor (mta.)
stb Specifies that the filter group applies to traffic to or from a Set-Top Box (stb.)
ps Specifies that the filter group applies to traffic to or from a portal server (ps.)
downstream Specifies that the filter group applies to the downstream traffic that is going to the
specified CM or CPE device.
upstream Specifies that the filter group applies to the upstream traffic that is coming from
the specified CM or CPE device.
group-id Specifies the filter group ID (0 to 254) to be applied for the CM or CPE,
downstream or upstream filter. This ID references the filter indexes that are used
for rows in the docsSubMgtPktFilterTable. A value of 0 indicates that no filtering
is used for this particular type of traffic.
Command Default The Subscriber Management MIB defaults to the following default values:
• The active parameter defaults to FALSE (the CMTS does not actively manage CPE devices).
• The learnable parameter defaults to TRUE (the CMTS learns the IP addresses for CPE devices).
• The max-cpe parameter defaults to 16 IP addresses.
• The filter group ID for each type of filter group defaults to 0, which means that no filtering is done
on that type of traffic.
Usage Guidelines This command enables field technicians to add a temporary CPE device behind the subscriber’s cable
modem. The temporary CPE device shares the same SID settings as the original CPE device, even though
the temporary CPE device has a different MAC address. The original CPE device automatically changes
from dhcp cpe to static cpe in the CMTS host routing tables, and the CPE device continues to receive
service with the same SID.
To disable Cisco CMTS Static CPE Override on the Cisco CMTS, use the no form of this command. This
automatically updates the routing tables and enables the MAC address from the technician’s laptop for
a future field service connection at a different location.Prior to using this command, the first (existing)
DHCP CPE device maintains its DHCP dynamic MAC address behind the cable modem. The SID is
assigned to this IP address.
However, by enabling Static CPE override, you gain the following states and options on two CPE devices
behind the cable modem.
• The SID definition on the first CPE device is assigned a different static IP address. This enables you
to change the existing (dynamic) DHCP IP address to a static IP address without first clearing the
DHCP CPE host entries from the Cisco CMTS. The CPE IP state changes from dhcp to static cpe.
• This static override allows a second CPE device with a second MAC address behind the same cable
modem with SID1 to be assigned same IP address as the first CPE device.
Note The second CPE device changes from dhcp cpe to static CPE in the CMTS host tables.
The DOCSIS 1.1 Subscriber Management MIB (DOCS-SUBMGT-MIB) creates and maintains a number
of tables that describe the state of subscriber management for the CMs and CPE devices being serviced
by the Cisco CMTS. The CMTS creates rows in these tables for each CM and CPE device when the CM
registers with the CMTS, and if the CM does not specify a value for an attribute in this table, the CMTS
uses the defaults specified by the cable submgmt default command.
Timesaver The DOCS-SUBMGT-MIB MIB contains its own default values for these attributes, and those defaults
can be overridden by giving the appropriate SNMP SET commands. The cable submgmt default
command, however, allows the new defaults to be included in the Cisco IOS configuration file so that
the defaults are automatically reconfigured whenever the CMTS reboots or reloads.
Note The cable submgmt default command sets only the default value for these attributes. These default
values are used only if the CM does not specify other values when it registers with the CMTS. If the CM
does specify different values at registration time, those values are used instead of these default values.
The attributes in DOCS-SUBMGT-MIB control how the CMTS manages the CPE devices behind a CM
and the filters that are applied to the traffic to and from a particular CM and its CPE devices. The
following sections describe the relationship between the different forms of the cable submgmt default
commands and the attributes in DOCS-SUBMGT-MIB.
CPE Management
The first form of the cable submgmt default command controls the default values for the entries in the
docsSubMgtCpeControlTable, which controls how the CMTS manages the CPE devices for each CM:
cable submgmt default active
Sets the docsSubMgtCpeActiveDefault attribute, which is the default value for the
docsSubMgtCpeControlActive attribute in docsSubMgtCpeControlTable. This attribute controls
whether the CMTS performs CPE management for a particular CM.
• The cable submgmt default active command sets the default to TRUE, which specifies that the
CMTS is to manage CPE devices by enforcing the MAX-CPE number and the implemented filters.
• The no cable submgmt default active command sets the default to FALSE (the default value),
which specifies that the CMTS is not to perform CPE management for the particular CM.
cable submgmt default learnable
Sets the docsSubMgtCpeLearnableDefault attribute, which is the default value for the
docsSubMgtCpeControlLearnable attribute in docsSubMgtCpeControlTable. This attribute controls
whether the CMTS learns the IP addresses for CPE devices behind a particular CM.
• The cable submgmt default learnable command sets the default to TRUE (the default value),
which specifies that the CMTS is to learn the IP addresses for the CPE devices behind the CM, up
to the value specified by the MAX-CPE parameter. The CMTS learns the IP addresses by monitoring
the traffic sent by the CPE devices, and the first CPE devices to transmit traffic are the first CPE
devices to be learned.
• The no cable submgmt default learnable command sets the default to FALSE, which specifies that
the CMTS does not learn the IP addresses for the CPE devices behind a particular CM. Instead, the IP
addresses for each CM that is to be allowed access must be specified in the DOCSIS configuration file.
Note The MAX-CPE attribute is used only when the CMTS is actively managing CPE devices for the CM.
The second form of the cable submgmt default command controls the default values for the entries in
the docsSubMgtCmFilterTable, which assigns the CM to one or more filter groups. A filter group
specifies what filters are applied to the traffic going to or coming from each particular CM or CPE
device. Filter groups can be numbered 0 to 1024, where 0 specifies that no filtering is done for that
particular traffic type.
Note The actual filters specified in these commands must be created by setting the appropriate attributes in
the DOCS-SUBMGT-MIB MIB using SNMP SET commands.
Note For more information about using static CPE override, see the Cisco CMTS Static CPE Override feature
on Cisco.com.
Examples The following commands specify that the CMTS defaults to actively managing the CPE devices for each
CM that registers, allowing and learning up to four IP addresses for the CPE devices behind that CM.
Router# configure terminal
Router(config)# cable submgmt default active
Router(config)# cable submgmt default learnable
Router(config)# cable submgmt default max-cpe 4
The following commands specify that the CMTS defaults to actively managing the CPE devices for each
CM that registers. Each CM, however, must specify its own MAX-CPE value; otherwise, that value
defaults to 0 and all traffic to and from the CPE devices for that CM is blocked.
Router# configure terminal
Router(config)# cable submgmt default active
Router(config)# cable submgmt default max-cpe 0
The following commands specify that the CMTS defaults to not actively managing the CPE devices for
each CM that registers. However, if the CM at registration time indicates that the CMTS is to actively
manage the CPE devices, the CMTS defaults to allowing only one CPE device. Learning also is disabled,
so that one CPE device, therefore, must be specified in the DOCSIS configuration file that the CM uses
to register.
Router# configure terminal
Router(config)# no cable submgmt default active
Router(config)# no cable submgmt default learnable
Router(config)# cable submgmt default max-cpe 1
The following commands specify that the CMTS defaults to assigning three filter groups to each CM that
registers. Unless the CM indicates otherwise at registration time, downstream and upstream traffic for
the CPE devices behind the CM is filtered according to the rules for filter groups 20 and 21, respectively.
Filter group 1 is applied to the downstream traffic addressed to the CM. Upstream traffic sent by the CM,
however, is not filtered.
Router# configure terminal
Router(config)# cable submgmt default filter-group cpe downstream 20
Router(config)# cable submgmt default filter-group cpe upstream 21
Router(config)# cable submgmt default filter-group cm downstream 1
Router(config)# cable submgmt default filter-group cm upstream 0
Note The above example assumes that filter groups 1, 20, and 21 have already been created on the CMTS using
the appropriate SNMP commands.
cable sync-interval
To specify the interval between successive sync message transmissions from the Cisco CMTS, use the
cable sync-interval command in cable interface configuration mode. To return the sync message interval
to its default value, use the no form of this command.
no cable sync-interval
Syntax Description msec Specifies the interval in milliseconds (ms) between successive sync message transmissions from
the Cisco CMTS. Valid values are from 1 to 200 ms. Default value is 10 ms.
Command Default 10 ms
Usage Guidelines To verify whether or not a sync message interval has been configured, enter the show running-config
command and look for the cable interface configuration information. If a sync message interval has been
configured, it appears in this output. If the sync message interval has been deactivated or reset to its
default value, no sync interval command line appears in the output.
Examples The following example shows how to specify the interval for the sync message transmissions to 100 ms:
Router (config-if)# cable sync-interval 100
New Commands
cable tag
To configure a tag for a DOCSIS load balancing group on the CMTS, use the cable load-balance
docsis-group command in the global configuration mode. To delete the tag and remove it from the
CMTS configuration, use the no form of this command.
Usage Guidelines The cable tag command creates a tag with the specified number and then enters the cmts-tag
configuration mode. Use the following commands in the cmts-tag configuration mode to configure the
tag:
• docsis-version
• exclude
• exit
• name
• oui
• override
• service-class
• service-type-id
Examples The following example shows how to create a tag numbered as “1' following which the system enters the
cmts-tag configuration mode:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# name CSCO
Router(cmts-tag)# service-type-id commercial
Router(cmts-tag)# service-class work
Router(cmts-tag)# docsis-version docsis20
Router(cmts-tag)# oui 00.1a.c3
Router(cmts-tag)# override
The following example shows how to configure the tag to exclude a DOCSIS version, a MAC address,
a service class name, or a service type ID.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# exclude docsis-version docsis10
Router(cmts-tag)# exclude oui 00.1a.c3
Router(cmts-tag)# exclude service-class work
Router(cmts-tag)# exclude service-type-id commercial
telco-return enable
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD message.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description seconds Number of seconds between intervals for sending TCD and TSI messages. Valid range is 2
through 60 seconds.
Examples The following example shows how to set the TCD and TSI message interval to 40 seconds:
Router(config-if)# cable telco-return interval 40
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description ip-address Registration IP address that is sent in Termination System Information (TSI) messages.
Value is any of the cable interface’s IP addresses.
Command Default The downstream channel IP address of the Cisco CMTS is used.
Usage Guidelines This command sets the Registration IP Address parameter in TSI messages. By default, the downstream
channel IP address of the Cisco CMTS is also used for the registration IP address. When this cable
telco-return registration-ip command is configured, telco-return CMs send their registration requests
to this IP address instead of to the downstream channel IP address.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to send the CM’s registration requests to IP address 172.16.1.1:
Router(config-if)# cable telco-return registration-ip 172.16.1.1
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the service provider descriptor (SPD) that the
telco-return CM uses during the initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is set. Valid range is
1 through 5.
Usage Guidelines This command sets the DHCP Authenticate parameter to TRUE (1) for the specified SPD in the
Telephony Channel Descriptor (TCD) messages. It indicates that the CM must use the DHCP server that
is specified with the cable telco-return spd dhcp-server command.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example indicates that for SPD 2, CMs must use the DHCP server identified by IP address
192.168.255.255:
Router(config-if)# cable telco-return spd 2 dhcp-authenticate
Router(config-if)# cable telco-return spd 2 dhcp-server 192.168.255.255
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during the
initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
ip-address IP address of the DHCP server that CMs must use.
Usage Guidelines This command sets the DHCP Server parameter in the specified SPD in Telephony Channel Descriptor
(TCD) messages. Telco-return CMs use the DHCP server that is identified by this IP address if the cable
telco-return spd dhcp-authenticate command is configured. If the cable telco-return spd
dhcp-authenticate command is not configured, the CMs use any available DHCP server.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example indicates that for SPD 2, CMs must use the DHCP server identified by IP address
192.168.255.255:
Router(config-if)# cable telco-return spd 2 dhcp-authenticate
Router(config-if)# cable telco-return spd 2 dhcp-server 192.168.255.255
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
seconds Number of seconds that a connection is idle before the CM
disconnects the call. Valid range is 0 through 4,294,967,295. The
default of 0 means that the dial-timer is not used.
Command Default The dial-timer is set to 0, which means that inactive telephone connections are not disconnected.
Usage Guidelines This command sets the Demand Dial Timer parameter for the specified SPD in Telephony Channel
Descriptor (TCD) messages. This enables the CM to emulate true dial-on-demand functionality by
monitoring inactive networking time and allowing it to disconnect any telephone connection that exceeds
the timer.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to set the timer to 2 hours:
Router(config-if)# cable telco-return spd 2 dial-timer 7200
Syntax Description spd-number Service provider descriptor (SPD) that contains the set of telephony
attributes used by the CM during initialization. Valid range is 1
through 5.
Command Default The Factory Default Flag in the SPD is set to 0, which means that this SPD is not used for the
initialization process.
Usage Guidelines This command sets the Factory Default parameter in the specified SPD in Telephony Channel Descriptor
(TCD) messages. This determines the set of telephony attributes, as defined by the SPD, that are used
for the initialization process when the CM is powered on or is reset to its factory default.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to set the telco-return CM to use SPD 2 during the initialization
procedure:
Router(config-if)# cable telco-return spd 2 factory-default
cable telco-return spd dhcp-authenticate Indicates that telco-return CMs must use a specific
Dynamic Host Configuration Protocol (DHCP) server.
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection
is idle before the telco-return CM disconnects the call.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM
dials when connecting to the headend’s network access
server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
Usage Guidelines This command sets the Manual Dial vendor-specific parameter in the specified SPD in Telephony
Channel Descriptor (TCD) messages.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to set manual-dial mode for SPD 1:
Router(config-if)# cable telco-return spd 1 manual-dial
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection
is idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during
the initialization process.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
password-string Login password that the CM uses for authentication during the
initialization procedure.
Usage Guidelines This command sets the Login Password parameter for the specified SPD in Telephony Channel
Descriptor (TCD) messages.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to set the password to 9JwoKd7 in service provider descriptor 2:
Router(config-if)# cable telco-return spd 2 password 9JwoKd7
cable telco-return spd dhcp-authenticate Indicates that telco-return CMs must use a specific DHCP
server.
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during the
initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
dial-string Telephone number that the CM uses to connect to the headend’s
network access server.
Usage Guidelines This command sets the Phone Number parameters in the specified SPD in Telephony Channel Descriptor
(TCD) messages. You can repeat this command, entering as many as three telephone numbers for the
CM to use when attempting to establish a PPP connection with the network access server. The phone
numbers are mapped to the parameters Phone Number1, Phone Number2, Phone Number3 in the order
in which you enter them. The CM attempts to connect using Phone Number1 first. If it fails to connect,
and its number of retries exceeds the limit set with the cable telco-return spd threshold command, the
CM dials the next number in the list.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows how to set the primary phone number to 9255551212. If the CM fails to
connect using that number, it tries the next phone number, 9255551234:
Router(config-if)# cable telco-return spd 2 phonenum 9255551212
Router(config-if)# cable telco-return spd 2 phonenum 9255551234
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
both Challenge Handshake Authentication Protocol (CHAP) is used if the
network access server supports CHAP. Password Authentication
Protocol (PAP) is used only if the network access server does not
support CHAP.
chap CHAP authentication is used.
pap PAP authentication is used.
Command Default The default is both; either CHAP or PAP is used depending on the methods supported by the network
access server.
Usage Guidelines This command sets the PPP Authentication parameter for the specified SPD in Telephony Channel
Descriptor (TCD) messages.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
string Alphanumeric string identifying a RADIUS server domain.
Usage Guidelines This command sets the RADIUS Realm parameter for the specified SPD in Telephony Channel
Descriptor (TCD) messages. When this command is configured, telco-return CMs use this realm string
to construct a domain name for the login username when responding to a PPP login query.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
cable telco-return spd dhcp-authenticate Indicates that telco-return CMs must use a specific DHCP
server.
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during
the initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor number for which this parameter is set.
Valid range is 1 through 5.
spd-string Alphanumeric string that identifies the service provider.
Usage Guidelines This command sets the Service Provider Name parameter for the specified SPD in the Telephony
Channel Descriptor (TCD) messages.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows the service provider name being set to “san_jose” for SPD 2:
Router(config-if)# cable telco-return spd 2 service-provider san_jose
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during
the initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable telco-return spd username Sets the username that the telco-return CM uses for
authentication when establishing a PPP connection.
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
threshold-number Number of dial-up attempts that fail before the CM declares a
connection failure. Valid range is 1 through 255.
Usage Guidelines This command sets the Connection Threshold parameter for the specified SPD in the Telephony Channel
Descriptor (TCD) messages. A dial-up attempt is considered a connection failure if an answer
connection is not made after ten rings. The CM continues to try to connect until the connection threshold
is reached. If multiple phone numbers are configured using the cable telco-return spd phonenum
command, the CM dials each phone number until it makes a connection or exceeds the configured
threshold.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows the connection threshold being set to 20:
Router(config-if)# cable telco-return spd 2 threshold 20
Syntax Description spd-number Service provider descriptor (SPD) number for which this parameter is
set. Valid range is 1 through 5.
login-string Username that the CM uses for authentication during the initialization
procedure.
Usage Guidelines This command sets the Login Username parameter for the specified SPD in the Telephony Channel
Descriptor (TCD) messages.
Note This command is available only in images that support telco-return. These images have a “t” as part of
the image name.
Examples The following example shows the username being set to “sandy” for SPD 3:
Router(config-if)# cable telco-return spd 3 username sandy
cable telco-return spd dhcp-authenticate Indicates that telco-return CMs must use a specific DHCP
server.
cable telco-return spd dhcp-server Identifies the IP address of the DHCP server that the
telco-return CMs must use.
cable telco-return spd dial-timer Sets the number of seconds that a telephone connection is
idle before the telco-return CM disconnects the call.
cable telco-return spd factory-default Indicates the SPD that the telco-return CM uses during the
initialization process.
cable telco-return spd manual-dial Enables the telco-return CM to operate in manual-dial
mode.
cable telco-return spd password Sets the password that the telco-return CM uses for
authentication when establishing a PPP connection.
cable telco-return spd phonenum Sets the telephone numbers that the telco-return CM dials
when connecting to the headend’s network access server.
cable telco-return spd ppp-authenticate Selects the authentication procedure to use when the
telco-return CM is establishing a PPP connection.
cable telco-return spd radius-realm Selects a RADIUS server domain to use for the login
response string.
cable telco-return spd service-provider Includes the service provider name in the SPD.
cable telco-return spd threshold Sets the number of failed dial-up connections that can
occur before the CM indicates a connection failure.
cable tftp-enforce
To require that all CMs on a cable interface attempt to download a DOCSIS configuration file using the
Trivial File Transfer Protocol (TFTP) through the cable interface before being allowed to register and
come online, use the cable tftp-enforce command in cable interface configuration mode. To disable this
feature, use the no form of this command.
Syntax Description mark-only (Optional) Allow CMs to come online without attempting to download
a DOCSIS configuration file through the Cisco CMTS cable interface,
but prints a warning message and marks those CMs with a pound sign
(#) in the show cable modem command.
Command Default TFTP downloads through the Cisco CMTS are not required (no cable tftp-enforce).
Usage Guidelines The cable tftp-enforce cable interface configuration command requires all cable modems on a cable
interface to attempt a TFTP request for the DOCSIS configuration file through the cable interface with
the Cisco CMTS router before being allowed to register and come online. This can help prevent the
following situations from occurring:
• Users who attempt theft-of-service by reconfiguring their local networks to allow the downloading
of an unauthorized DOCSIS configuration file from a local TFTP server. Typically, some users do
this to obtain services that they have not paid for, such as higher guaranteed bandwidths or a higher
priority Quality of Service (QoS) profile.
• Some brands or models of cable modems might be running older software releases that cache the
DOCSIS configuration file and use the cached version instead of downloading the actual file from
a TFTP server during the registration process. Although this can marginally speed up the registration
process, it also violates the DOCSIS requirements and could create a situation in which the cable
modem is not using the proper DOCSIS configuration file. A user might then be mistakenly accused
of theft-of-service, when in reality the problem is the non-DOCSIS-compliant cable modem.
The cable tftp-enforce command identifies these situations and can block these cable modems from
registering and coming online. This command also has a mark-only option that allows these cable
modems to come online, but it also identifies the cable modems so that the network administrators can
investigate the situation further before taking any action.
When the command is used without the mark-only option, cable modems that do not download a TFTP
file through the cable interface are blocked from registering and coming online. The following message
is displayed on the console when such a cable modem attempts to register:
06:53:57: %UBR7200-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:
Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <00ff.ff66.12fb>
The mark-only option allows cable modems that do not download the TFTP file to come online, but it
also prints a warning message on the console and marks the cable modem in the show cable modem
command with a pound sign (#). The following message is displayed on the console when such a cable
modem registers with the Cisco CMTS.
06:53:57: %UBR7200-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:
Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <00ff.ff66.12fb>
Tip Cisco recommends that you initially configure cable interfaces with the mark-only option, so that
potential problems are identified without immediately interfering with users’ ability to come online.
After you identify and resolve these initial problems, reconfigure the cable interfaces without the
mark-only option to block problem cable modems that attempt to come online without downloading a
valid DOCSIS configuration file.
The default behavior is not to require the TFTP download through the cable interface with the
Cisco CMTS router. Each cable interface must be configured with this command to require the TFTP
download.
Note The cable tftp-enforce command cannot be used on subinterfaces or on non-cable interfaces.
Note In the above situation, cable modems that do not download a DOCSIS configuration file are marked as
“offline” instead of “reject(c)” by the show cable modem command. The console still displays the
%UBR10000-4-REGISTRATION_BEFORE_TFTP error message, however, to allow you to identify
these cable modems as TFTP violators.
Examples The following example shows how to enforce TFTP downloads for all of the cable modems on cable
interface 3/0. These cable modems must attempt a TFTP download of the DOCSIS configuration file
through the cable interface with the Cisco CMTS. If they do not, they are not allowed to register or come
online, and they are marked as having either a registration error—reject(c)—in the show cable modem
command.
Note The initial version of this feature marked CMs that failed the TFTP check as having a Message Integrity
Check (MIC) failure—reject(m). The command was changed to show reject(c) in Cisco IOS Release
12.2(8)BC2 and Release 12.1(19)EC.
Router#
Note DOCSIS-compliant cable modems that are rejected with a MIC failure go into the offline state for a short
period of time and then retry the registration process.
The debug cable registration command can be used to display additional information:
Router# debug cable interface c3/0 verbose
Router# debug cable registration
CMTS registration debugging is on
Cable Modem did not attempt TFTP. Registration Rejected. CM Mac Addr <00ff.ff66.12fb>
Registration failed for Cable Modem 00ff.ff66.12fb on interface Cable3/0/U0:
CoS/Sflow/Cfr/PHS failed in REG-REQ
Jun 6 23:27:15.859: REG-RSP Status : failure (2)
Jun 6 23:27:15.859: Registration Response:
Jun 6 23:27:15.859: 0x0000: C2 00 00 1B 00 00 00 50 73 4E B4 19 00 05 00 E0
Jun 6 23:27:15.859: 0x0010: 56 AC 00 09 00 00 03 01 07 00 00 02 02
Jun 6 23:27:15.859: Registration Response Transmitted
The following example of the mark-only option shows how that cable modems that do not attempt a
TFTP download through the Cisco CMTS are allowed to register and come online, but they are marked
with a pound sign (#) when using the show cable modem command.
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable tftp-enforce mark-only
Router(config-if)# exit
Router(config)#
Router#
The debug cable registration command can be used to display additional information:
Jun 6 23:27:15.859: Registration request from 00ff.ff66.12fb, SID 7 on Cable3/0/U1
Jun 6 23:27:15.859: Found a network access control parameter: Ok
Jun 6 23:27:15.859: Found a class of service block: Ok
Jun 6 23:27:15.859: Found Baseline Privacy config: Ok
Jun 6 23:27:15.859: Found Max CPE: Ok
Jun 6 23:27:15.859: Found CM MIC: Ok
Jun 6 23:27:15.859: Found CMTS MIC: Ok
Jun 6 23:27:15.859: Found modem ip: Ok
Jun 6 23:27:15.859: Found modem capabilities: Ok
Jun 6 23:27:15.859: Finished parsing REG Request
Jun 6 23:27:15.859: Cable Modem sent Registration Request without attempting required
TFTP
23:27:15: %UBR7200-4-REGISTRATION_BEFORE_TFTP: Registration request unexpected:
Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <00ff.ff66.12fb>
Jun 6 23:27:15.859: Sec sids obtained for all requested classes of service
Jun 6 23:27:15.859: Performing connection admission control (CAC) for each Sid
Jun 6 23:27:15.859: CAC Status for ClassID:1 is CAC_SUCCESS
Jun 6 23:27:15.859: Registration Status: ok (0)
Jun 6 23:27:15.859: Registration Response Transmitted
Tip You can also use the show interface cable sid and show cable qos profile commands to examine the
SID and service classes in use, to determine whether a CM has registered using unauthorized QoS
parameters.
cable throttle-ranging
To enable faster cable modem registration times, use the cable throttle-ranging command in global
configuration mode. To disable faster cable modem registration times, use the no form of this command.
cable throttle-ranging
no cable throttle-ranging
Usage Guidelines The cable throttle-ranging command enables faster cable modem registration times on the CMTS.
Reload the Cisco CMTS with a Cisco IOS Release 12.3(21)BC image and configure the cable
throttle-ranging command on the CMTS. Once the cable throttle-ranging has been configured, save
the new configuration and reload the Cisco CMTS again. Faster cable modem registration times will now
be enabled on the Cisco CMTS.
Examples The following example shows how to enable Fast CM registration feature on a Cisco CMTS:
Router(config)# cable throttle-ranging
cable time-server
To enable the integrated time-of-day (ToD) server on the Cisco CMTS series, enter the cable
time-server command in global configuration mode. To disable the time-of-day server function, use the
no form of this command.
cable time-server
no cable time-server
Usage Guidelines Per the DOCSIS specifications, the ToD server uses the UDP protocol, so UDP minor servers must also
be enabled using the service udp-small-servers max-servers no-limit command.
Examples The following example shows how to enable the time-of-day server:
Router# configure terminal
Router(config)# service udp-small-servers max-servers no-limit
Router(config)# cable time-server
Router(config)#
cable trust
To enable packets from trusted source MAC addresses in DHCP, use the cable trust command in global
configuration mode. To remove a trusted MAC address from the MAC exclusion list, use the no form of
this command. Removing a MAC address from the exclusion list subjects all packets from that source to
standard DHCP source verification.
cable trust mac-address
no cable trust mac-address
Syntax Description mac-address The MAC address of a trusted DHCP source, and from which packets will
not be subject to standard DHCP source verification.
Defaults Disabled
Usage Guidelines Per the DOCSIS specifications, the ToD server uses the UDP protocol, so UDP minor servers must also
be enabled using the service udp-small-servers max-servers no-limit command.
Usage Guidelines This command and capability are only supported in circumstances in which the Cable Source Verify
feature is first enabled on the Cisco CMTS.
When this feature is enabled in addition to cable source verify, a packet’s source must belong to the MAC
Exclude list on the Cisco CMTS. If the packet succeeds this exclusionary check, then the source IP
address is verified against Address Resolution Protocol (ARP) tables as per normal and previously
supported source verification checks. The service ID (SID) and the source IP address of the packet must
match those in the ARP host database on the Cisco CMTS. If the packet check succeeds, the packet is
allowed to pass. Rejected packets are discarded in either of these two checks.
Any trusted source MAC address in the optional exclusion list may be removed at any time. Removal of
a MAC address returns previously trusted packets to non-trusted status, and subjects all packets to
standard source verification checks on the Cisco CMTS.
Note When the cable source-verify dhcp feature is enabled, and a statically-defined IP address has been
added to the CMTS for a CM using the cable trust command to override the cable source-verify dhcp
checks for this device, packets from this CM will continue to be dropped until an entry for this CM is
added to the ARP database of the CMTS. To achieve this, disable the cable source-verify dhcp feature,
ping the CMTS from the CM to add an entry to the ARP database, and re-enable the cable source-verify
dhcp feature.
For additional information about the enhanced Cable Source Verify DHCP feature, and general
guidelines for its use, refer to the following documents on Cisco.com:
• Filtering Cable DHCP Lease Queries on the Cisco CMTS
• DHCP and Time-of-Day Services on the Cisco CMTS
• IP Address Verification for the Cisco uBR7200 Series Cable Router
• CABLE SECURITY, Cable Source-Verify and IP Address Security, White Paper
Examples The following example shows how to enable the time-of-day server:
Router# configure terminal
Router(config)# cable trust 0007.0e03.69f9
Router(config)# Ctrl^Z
Router#
New Commands
Modified Commands
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
active-code Specifies the number of active codes. Valid values are from 64 to 128,
with a default value of 112, when ingress noise cancellation is enabled;
and a default value of 128, when ingress noise cancellation is disabled.
Command Default The active-code setting cannot be applied if the Synchronous Code Division Multiple Access (S-CDMA)
is not configured.
Usage Guidelines This command is applicable only for S-CDMA channels. You should configure S-CDMA to apply the
active-code setting.
Examples The following example sets the active code to 128 on upstream port 0:
Router(config)# interface cable 7/0/4
Router(config-if)# cable upstream 0 active-codes 128
Router(config-if)#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
percentage Specifies the percentage overbooking rate to limit overbooking. Valid
values are from 10 to 1000 percent, with a default of 100 percent.
Usage Guidelines This command limits the maximum number of CMs for a given upstream port by looking at the minimum
guaranteed upstream bandwidth allocated to each CM. Cable modems providing residential services and
commercial services can be given different weights according to their traffic needs. This command
affects only whether CMs can register with the CMTS—it does not affect CMs that have already come
online.
The CMTS uses the minimum guaranteed upstream bandwidth field from the CM’s DOCSIS
configuration file to calculate whether the CM can come online or not. If the CM’s minimum guaranteed
upstream bandwidth would exceed the total upstream bandwidth multiplied by the overbooking
percentage specified by this command, the CM cannot come online on that upstream. The CM will
attempt to find another upstream, and if it cannot register on any upstreams, it will attempt to lock on to
a new downstream.
Note A CM with a guaranteed upstream bandwidth does not consume that bandwidth unless it has active
traffic. By guaranteeing a CM a minimum upstream bandwidth, individual customers are assured of
never being totally shut out from network access in a very high-traffic situation.
Table 14 shows the approximate bandwidth for each upstream channel, depending on channel width,
symbol rate, and modulation type, when admission control is used at 100 percent. When setting
admission control to other values, scale the bandwidth values in Table 14 accordingly, so as to plan for
the maximum number of CMs effectively allowed per upstream port.
For example, with a 3.2 MHz channel width and QPSK modulation, the total bandwidth is approximately
5 Mbps. This is the maximum allowable bandwidth that can be allocated to CMs at the default admission
rate of 100%. If each CM is allocated a minimum upstream bandwidth of 128 kbps, this means a
maximum of 40 CMs will be allowed to come online.
To verify whether or not upstream admission control is configured and activated, use the show interface
command for a cable upstream to display its configuration information. If upstream admission control
is configured and enabled, the output contains an entry stating “CIR admission control enforced.” If
upstream admission control is disabled, no admission control entry is displayed in the output.
Note Setting the admission control limit to below the current total reserved bandwidth for the channel does
not immediately force any CMs offline, but may prevent CMs from reconnecting if they drop offline at
a later time. Increasing the admission control limit allows more CMs to connect.
When an upstream becomes overbooked, use the test cable ucc command to move a cable modem that
is currently online from one upstream port to another. For example, the following example shows that
the cable modem with the IP address of 10.128.1.128 is being moved from port C3/0/U0 to C3/0/U1:
Router# show cable modem 10.128.1.128
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
Cable3/0/U0 101 online 1919 5.25 7 0 10.128.1.128 0030.1976.7067
Examples The following example shows overbooking on upstream port 4 being limited to 125 percent:
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 4 admission-control 125
Router(config-if)#
Use the show interface cable upstream command to display the current status of admission control on
an interface. For example, the following command output shows that this upstream has allocated a total
bandwidth of 2.5 Mbit/sec to those online CMs that were assigned a guaranteed upstream bandwidth in
their DOCSIS configuration files.
This displays also shows that the admission control is being enforced at a subscription level of 125
percent. The Virtual channel BW field is computed by multiplying channel bandwidth by the admission
control limit. The Admissions requests rejected counter shows the number of cable modems that
attempted to register but were refused because of the admission control policy.
Router# show interface c3/0 u4
Cable3/0: Upstream 4 is up
Received 11585 broadcasts, 11854 multicasts, 3222651 unicasts
0 discards, 829 errors, 0 unknown protocol
3246090 packets input, 5 uncorrectable
557 noise, 0 microreflections
Total Modems On This Upstream Channel : 69 (68 active)
Default MAC scheduler
Queue[Rng Polls] 0/64, fifo queueing, 0 drops
Queue[Cont Mslots] 0/52, fifo queueing, 0 drops
Queue[CIR Grants] 0/64, fair queueing, 0 drops
Queue[BE Grants] 0/64, fair queueing, 0 drops
Queue[Grant Shpr] 0/64, calendar queueing, 0 drops
Reserved slot table currently has 0 CBR entries
Req IEs 205196036, Req/Data IEs 0
Init Mtn IEs 7604617, Stn Mtn IEs 422496
Long Grant IEs 4848, Short Grant IEs 1646196
Avg upstream channel utilization : 1%
Avg percent contention slots : 94%
Avg percent initial ranging slots : 1%
Avg percent minislots lost on late MAPs : 0%
Total channel bw reserved 2500000 bps
CIR admission control enforced
Subscribtion level 125%
Virtual channel bw 6400000 bps
Admission requests rejected 32
Current minislot count : 5200298 Flag: 0
Scheduled minislot count : 5200420 Flag: 0
Router#
If a CM is denied access due to the admission control policy, its entry in the show cable modem
command output shows “reject(c)”:
Router# show cable modem
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
Cable2/0/U0 1 online 2288 0.50 4 0 10.16.30.66 0010.7bb3.fb45
Cable2/0/U0 2 online 2288 0.50 4 0 10.16.30.68 0010.7bb3.fb7b
Cable2/0/U0 3 init(i) 2280 0.00 2 0 10.16.30.69 0010.9500.05e
. . .
Cable3/0/U1 113 online 3921 0.00 5 0 10.128.1.108 0030.9433.c38b
Cable3/0/U1 114 online 3920 0.25 6 0 10.128.1.87 0030.1976.6ebf
Cable3/0/U0 115 reject(c) 3922 0.25 2 0 10.128.1.75 0030.1976.703b
Cable3/0/U0 116 online 3919 0.75 5 0 10.128.1.57 0030.1976.6fa1
show cable modem Displays statistics for a CM, including its upstream port and primary
SID.
show interface cable upstream Displays the interface configuration, which for an upstream includes
the current admission control policy, if any.
Usage Guidelines This command sets the attribute mask of upstream channel.
Examples The following example shows how to set upstream attribute mask in hexadecimal format:
Router(config-if)# cable upstream 0 attribute-mask ffff
Syntax Description id Bonding group ID on the cable interface. Valid values are from 1 to 65535.
Usage Guidelines You can configure up to 32 static upstream bonding groups for each Media Access Control (MAC)
domain. If you delete an upstream bonding group using the no form of the command, the Cisco CMTS
router enforces the bonded upstream service flows associated with the deleted upstream bonding group
to readmit.
Under the upstream bonding configuration submode, you can specify the following for an upstream
bonding group:
• Upstream channels
• Bandwidth reservation
• Provisioned attribute masks
Examples The following example shows how to configure an upstream bonding group on a cable interface in slot 7,
subslot 1, and port 0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 7/1/0
Router(config-if)# cable upstream bonding-group 235
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
first-choice-width Specifies the upstream channel width in hertz (Hz). Valid values for all
cards are displayed in Table 15.
last-choice-width (Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and
Cisco uBR-MC5X20S/U/H only)
The upstream channel width in hertz. The valid values are the same as
those for the first-choice-width parameter, but for proper operation, the
last-choice-width should be equal to or less than the first-choice-width
value. Use this parameter with supported cards to enable symbol rate
management algorithms.
Command Default The first-choice-width value and the last-choice-width value default to 1,600,000 Hz. When an upstream
channel is configured to operate in DOCSIS 2.0 A-TDMA or DOCSIS 3.0 S-CDMA-mode, only three
channel width options (1.6 Mhz, 3.2 Mhz, and 6.4 Mhz) are available.
Usage Guidelines The last-choice-width parameter is supported only by the Cisco uBR-MC16S, Cisco uBR-MC16U/X,
Cisco uBR-MC28U/X, and Cisco uBR-MC5X20S/U cable interface line cards. When one of these
particular cards is installed, the system attempts to increase the channel width from the smallest channel
width value to the largest channel width value.
When you specify both channel width values, the smaller value is taken as the last-choice-width
parameter and the larger value is taken as the first-choice-width parameter. In the event of noise in the
channel, the symbol rate automatically steps down to a value that is lower than the first-choice-width and
greater or equal to the last-choice-width to maintain a stable channel.
Table 15 Supported Channel Widths and DOCSIS Modes for Cable Interfaces
Mixed
Channel DOCSIS 1.X DOCSIS DOCSIS 2.0 DOCSIS 2.0 DOCSIS 3.0
Cable Interface Width (TDMA) 1.X/2.0 (A-TDMA) (S-CDMA) (S-CDMA)
Cisco uBR-MC16U/X1, 6.4 MHz 41 to 50 141 to 150 241 to 250 N/A N/A
Cisco uBR-MC28U/X 3.2 MHz (default is 41) (default is (default is
1.6 MHz 141) 241)
800 kHz
400 kHz
200 kHz
Cisco uBR-MC5X20S/U/H 6.4 MHz 21 to 30 121 to 130 221 to 230 N/A N/A
3.2 MHz (default is 21) (default is (default is
1.6 MHz 121) 221)
800 kHz
400 kHz
200 kHz
Cisco uBR-MC20X202 6.4 MHz 21 to 30 121 to 130 221 to 230 321 to 330 1 to 400
3.2 MHz (default is 21) (default is (default is (default is (default is
1.6 MHz 121) 221) 321) 381)
800 kHz
400 kHz
200 kHz
1. Supports 6,400,000 Hz (5,120,000) symbols/sec) while operating in the DOCSIS 2.0 (A-TDMA-only) mode.
2. The DOCSIS 3.0 S-CDMA modulation profiles do not support 200 kHz, 400 kHz, and 800 kHz channel widths.
Note The UBR-MC20X20V cable interface line card has three variants, UBR-MC20X20V-0D,
UBR-MC20X20V-5D, and UBR-MC20X20V-20D. The UBR-MC20X20V-0D line card supports 20
upstreams and zero (no) downstreams. The UBR-MC20X20V-5D line card supports 20 upstreams and
five downstreams, and the UBR-MC20X20V-20D line card supports 20 upstreams and 20 downstreams.
Note In Cisco IOS Release 12.2(15)BC1 and later releases, changing the channel width could force a
frequency hop, if the current frequency does not fit within the new channel width parameters, or if the
system needs to reset the fixed frequency or shared frequency group parameters to match the new
channel width.
Caution In DOCSIS 1.X networks, do not change the channel width more than one step at a time on an interface
that has cable modems that are currently online. The DOCSIS 1.X specifications require that cable
modems remain online when the channel width is changed in single step increments (such as 800,000 to
1,600,000 Hz), but cable modems can go offline when you change the channel width in larger amounts
(such as changing it from 800,000 to 3,200,000 Hz). To check if the DOCSIS 2.0 cable modems support
changing the channel width by two steps, test each brand of modem before attempting it on a live
network. Also, after changing the channel width, do not change the channel width again until all cable
modems have performed their ranging adjustments for the new width (which could take up to a minute,
depending on the number of cable modems).
Note To specify only one channel width for the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, or
Cisco uBR-MC5X20S/U/H card, specify the same value for both the first-choice-width and
last-choice-width parameters. For example:
cable upstream 0 channel-width 800000 800000
When using this command to change channel-widths for an upstream interface on the
Cisco uBR-MC5X20S cable interface line card, some DOCSIS 1.1 CMs can go offline if you do not
change the minislot size to the corresponding value. See the following examples for the correct
channel-width and minislot pairings:
Router(config-if)# cable upstream 0 channel-width 3200000
Router(config-if)# cable upstream 0 minislot 4
Note This limitation does not affect DOCSIS 1.1-compliant CMs. Also, in Cisco IOS Release 12.2(15)CX,
Cisco IOS Release 12.2(15)BC2, and later releases, there is no need to manually change the minislot size
on the Cisco uBR-MC16U/X, Cisco uBR-MC28C, and Cisco uBR-MC28U/X cards. These cards
automatically change the minislot size when the channel width is changed, to produce 32 symbols per
minislot.
PacketCable Limitations
The 200,000 Hz channel width cannot be used on:
• Upstreams that support PacketCable voice calls
• Upstreams that use Unsolicited Grant Service (UGS) or UGS with Activity Detection (UGS-AD)
service flows.
Using this small channel width with voice and other UGS/UGS-AD service flows results in rejected calls
because of “DSA MULTIPLE ERRORS”.
Examples The following example shows the upstream port 2 on a Cisco uBR-MCXXC card being configured with
a channel width of 200,000 Hz (which is equivalent to a symbol rate of 160 kilosymbols/second):
Router(config-if)# cable upstream 2 channel-width 200000
Router(config-if)#
The following example shows the upstream port 2 on a Cisco uBR-MC16U/X, Cisco uBR-MC28U/X,
or Cisco uBR-MC5X20S card being configured with a channel width of 200,000 Hz (which is equivalent
to a symbol rate of 160 kilosymbols/second):
Router(config-if)# cable upstream 2 channel-width 200000 200000
Router(config-if)#
The following example shows the upstream port 3 being configured to step from a channel width of
1,600,000 Hz to a channel width of 3,200,000 Hz in increments of 200,000 Hz:
Router(config-if)# cable upstream 3 channel-width 1600000 3200000
Router(config-if)#
The following example shows an upstream port on a Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, or
Cisco uBR-MC5X20S card being configured with a channel width of 6.4 MHz, which is supported only
in DOCSIS 2.0 A-TDMA-only mode:
Router(config-if)# cable upstream 0 channel-width 6400000
Router(config-if)#
The following example shows an upstream port on a Cisco uBR-MC5X20H card being configured with
a channel width of 6.4 MHz in DOCSIS 3.0 S-CDMA mode:
Router(config-if)# cable upstream 0 channel-width 6400000
Router(config-if)#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
code Specifies the number of codes-per-minislot. Valid values range from 2
to 32.
Command Default The codes-per-minislot setting cannot be applied if the Synchronous Code Division Multiple Access
(S-CDMA) is not configured. The default value of codes-per-minislot depends on the setting of the
cable upstream spreading-interval command.
Usage Guidelines This command limits the maximum number of codes-per-minislot for a given upstream port. You should
configure S-CDMA to apply the active-code setting.
Examples The following example sets the codes-per-minislot to 8 on the upstream port 0:
Router(config)# interface cable 7/1/0
Router(config-if)# cable upstream 0 codes-per-minislot 8
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
Usage Guidelines Concatenation is part of DOCSIS 1.0 extension support. Concatenation provides for improved
bandwidth efficiency but must be supported at both the headend CMTS and the CM.
DOCSIS concatenation combines multiple upstream packets into one packet to reduce packet overhead
and overall latency and increase transmission efficiency. Using concatenation, a DOCSIS CM needs to
make only one bandwidth request for a concatenated packet, compared to making bandwidth requests
for each individual packet. This technique is especially effective for bursty real-time traffic such as voice
calls.
Concatenation support improves upstream per CM data throughput. The Cisco CMTS radio frequency
(RF) line card driver can receive only one MAC frame in a data burst. Thus the CM must make explicit
bandwidth requests for every packet it sends upstream. This limits the maximum upstream data
throughput received by the CM due to the inherent request-to-grant round-trip latency of the hybrid
fiber-coaxial (HFC) cable system incurred by every packet. To increase this per-CM upstream
throughput, the Cisco CMTS driver has been enhanced to receive a concatenated burst of multiple MAC
frames from the same CM.
Note Concatenation is not supported on the Cisco uBR-MC11 FPGA and Cisco uBR-MC16B cable interface
line cards.
Examples The following example shows how to enable concatenation for CMs on upstream port 2 on the cable
interface in slot 3/0:
Router(config)# interface c3/0
Router(config-if)# cable upstream 2 concatenation
Syntax Description logical-port Specifies the upstream port number for the logical port assignment. The
number of logical ports is configured with the cable modulation-profile
command, and the valid range is from 0 to one less than the current value
set with the cable modulation-profile command.
Tip The default value for max-ports command is 4, which means the
default range for logical-port is 0 to 3.
physical-port Specifies the upstream port number for the actual physical port to be
assigned. The valid range is 0 to 19, with no default.
Defaults By default, the Cisco uBR-MC5X20S/U cable interface line card uses a fixed configuration, in which
each downstream is allocated four upstream ports.
Usage Guidelines The cable upstream connector command changes the default assignment of upstream ports to MAC
domains on the Cisco uBR-MC5X20S/U card. This command creates a virtual upstream for a
downstream and assigns it to a particular physical port.
The default port mapping assigns four upstream ports to each of the downstream ports (MAC domains).
The ports are assigned sequentially, in the order in which they appear on the card’s front panel.
The no version of this command removes the upstream port mapping and shuts down the upstream port.
The port must be remapped to another physical port before it can come online again.
Tip Use the cable upstream max-ports command to set the maximum number of upstream ports per
downstream before using the cable upstream connector command.
Table 0-16 Default Upstream Port Assignments for the Cisco uBR-MC5X20S/U Cable Interface Line Card
The physical upstream ports can be assigned in any combination to a downstream, up to a maximum of
8 upstreams per downstream. If you have previously mapped an upstream port to a physical port using
the cable upstream connector command, you must first remove that mapping, using the no form of the
command, before changing it.
Examples The following example shows how to configure a downstream (MAC domain) on the
Cisco uBR-MC5X20S card for 8 upstream ports:
Router# configure terminal
Router(config)# interface cable c8/1/0
Router(config-if)# cable upstream max-ports 8
Router(config-if)# cable upstream 0 connector 16
Router(config-if)# cable upstream 1 connector 17
Router(config-if)# cable upstream 2 connector 18
Router(config-if)# cable upstream 3 connector 12
Router(config-if)# cable upstream 4 connector 13
Router(config-if)# cable upstream 5 connector 14
Router(config-if)# cable upstream 6 connector 15
Router(config-if)# cable upstream 7 connector 11
Router(config-if)# exit
Router(config)# exit
Router#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
automatic Specifies automatic data backoff start and stop values. It enables
dynamic variation in the start and end values.
start Binary exponential algorithm. Sets the start value for data backoff.
Valid values are from 0 to 15.
end Binary exponential algorithm. Sets the end value for data backoff. Valid
values are from 0 to 15.
Usage Guidelines The DOCSIS-specified method of contention resolution for CMs used to send data or requests on the
upstream channel is a truncated binary exponential backoff with the initial backoff window and the
maximum backoff window controlled by the CMTS. The Cisco CMTS router specifies backoff window
values for both data and initial ranging, and sends these values downstream as part of the Bandwidth
Allocation Map (MAP) MAC message.
The values specified in this command are exponential power-of-two values. For example, a value of 4
indicates a window between 0 and 15; a value of 10 indicates a window between 0 and 1023.
Cisco recommends that you use the automatic settings for data backoff. If you decide to manually specify
the data-backoff values, use the following formula as a guideline for the start and end binary exponents:
0.33 = (2**stop - 2**start)/n
where n is the number of CMs on the upstream. Choose start and stop values that come closest to the
value of 0.33 (which is the optimal probability to transmit on a contention-based system).
Examples The following example shows how to set the automatic data backoff values for upstream 2 on a cable
interface card:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 2 data-backoff automatic
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
label An arbitrary string, up to 80 characters long, that describes this
upstream for management and tracking purposes. If the string contains
any spaces, enclose the string within quotes.
Usage Guidelines Use the cable upstream description command to assign arbitrary labels to the upstreams on the cable
interfaces. These labels can contain any information that identifies the upstream and that could aid in
network management or troubleshooting.
Tip Use the show interface cable upstream command to display the labels that are assigned to a particular
upstream.
Examples The following example shows how to assign descriptions to the first two upstreams on the cable interface
in slot 3:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 description "SJ-Node1-Upstream 0"
Router(config-if)# cable upstream 1 description "SJ-Node1-Upstream 1 (Unused)"
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
Usage Guidelines To verify whether or not upstream differential encoding is activated, enter the show running-config
command and look for the cable interface configuration information. If upstream differential encoding
is enabled, a differential encoding entry is displayed in the output of the show running-config
command. If upstream differential encoding is disabled, no differential encoding entry is displayed in
the output.
If you are having trouble, make sure that the cable connections are not loose or disconnected; the cable
interface line card is firmly seated in its chassis slot; the captive installation screws are tight; you have
entered the correct slot and port numbers; and you selected a valid frequency for your router.
Examples The following example shows how to enable differential encoding for upstream port 2:
Router(config-if)# cable upstream 2 differential-encoding
Router(config-if)#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
atdma Configures the upstream only for DOCSIS 2.0 Advanced Time Division
Multiple Access (A-TDMA) modulation profiles.
scdma Configures the upstream for DOCSIS 2.0 Synchronous Code Division
Multiple Access (S-CDMA) modulation profiles only.
scdma-d3 Configures the upstream for DOCSIS 3.0 S-CDMA modulation
profiles. The scdma-d3 option uses channel type 4SR mode.
tdma Configures the upstream only for DOCSIS 1.0/DOCSIS 1.1 Time
Division Multiple Access (TDMA) modulation profiles (default).
tdma-atdma Configures the upstream for both A-TDMA and TDMA operations
(mixed mode). If you are using abbreviations at the command line, you
must specify at least the tdma to select the mixed mode. If you choose
a shorter abbreviation, you select TDMA-only mode.
Command Default All upstreams are configured TDMA-only mode (DOCSIS 1.0/DOCSIS 1.1).
Usage Guidelines The DOCSIS 2.0 specification builds on the existing TDMA to support advanced modulation profiles
that increase potential upstream bandwidth. The A-TDMA profiles support higher QAM rates of up to
64-QAM and wider channel widths of up to 6.4 MHz (5.12 Msymbols).
Note The advanced hardware-based spectrum management features for the Cisco uBR-MC16S/U/X,
Cisco uBR-MC28U/X, and Cisco uBR-MC5X20S/U cards are supported only in the DOCSIS 1.0/1.1
TDMA-only mode. They cannot be used in the mixed or A-TDMA-only modes.
The DOCSIS 2.0 specification allows an upstream to be configured in one of the following three modes:
• A-TDMA only mode—Upstreams only support cable modems that register using A-TDMA
modulation profiles. The CMTS does not allow DOCSIS 1.0 and DOCSIS 1.1 cable modems to
register and come online on these upstreams. The Cisco uBR-MC5X20S/U, Cisco uBR-MC16U/X,
and Cisco uBR-MC28U/X cards also support 6,400,000 Hz (5,120,000 symbols/sec) when
operating in DOCSIS 2.0 (A-TDMA-only) mode.
Changing the DOCSIS mode to A-TDMA only mode automatically changes the symbol rate to
5.12 megasymbols per second and the channel width to 6.4 MHz. It also automatically disables the
dynamic upstream modulation.
In addition, the following are required to support the DOCSIS 2.0 A-TDMA features:
– Cable modems must be DOCSIS 2.0 compliant.
– The DOCSIS configuration file for the cable modem must either omit the DOCSIS 2.0 Enable
field (TLV 39), or it must set TLV 39 to 1 (enable). If you set TLV 39 to 0 (disable), a
DOCSIS 2.0 CM uses the TDMA mode.
– The upstream must be configured for either A-TDMA-only or mixed TDMA/A-TDMA mode.
• TDMA-only mode—Upstreams only support cable modems that register using TDMA modulation
profiles. DOCSIS 2.0 cable modems can register on these upstreams only by using a
DOCSIS 1.0/DOCSIS 1.1 modulation profile (which typically would happen only when a
DOCSIS 2.0 cable modem cannot find an A-TDMA channel in its DOCSIS domain).
Changing the DOCSIS mode to TDMA-only mode automatically changes the symbol rate to 1.28
megasymbols per second and the channel width to 3.2 MHz. It also automatically disables the
dynamic upstream modulation.
• Mixed mode—Upstreams support both DOCSIS 1.0/DOCSIS 1.1 cable modems using TDMA
modulation profiles and DOCSIS 2.0 cable modems using A-TDMA modulation profiles. (The
maximum channel width in mixed mode is 3.2 MHz.)
Changing the DOCSIS mode to mixed mode also automatically changes the symbol rate to
1.28 megasymbols per second and the channel width to 3.2 MHz. Dynamic upstream modulation is
also automatically disabled.
Note Mixed mode upstreams do not support the 6.4 MHz channel width.
The DOCSIS 3.0 specification allows an upstream to be configured in one of the following modes:
• SCDMA-d3 mode—Upstreams only support cable modems that register using DOCSIS 3.0
S-CDMA modulation profiles.
• SCDMA mode—Upstreams only support cable modems that register using DOCSIS 2.0 S-CDMA
modulation profiles.
Note The DOCSIS 3.0 option scdma-d3 (4SR) is available only when the CMTS is configured to operate in
the global modulation profile format and is not available in the default mode. This option is available
only for the Cisco UBR-MC20X20V cable interface line card, and not for other legacy line cards.
Refer to the cable upstream channel-width command for valid values of supported channel widths and
DOCSIS modes for cable interfaces.
Note Changing the DOCSIS Mode for an Upstream Port Forces the Cable Modems on That Upstream to Go
Offline and Reregister
When you switch the DOCSIS mode of an upstream between the TDMA-only and mixed
TDMA/A-TDMA modes, cable modems that are currently online on that upstream are taken offline and
are forced to reregister. This helps the CMTS to determine the capabilities of the cable modems on the
new channels.
If you change an upstream port to A-TDMA only mode, DOCSIS 1.x cable modems will not be able to
come online on that upstream. If you change an upstream to TDMA only mode, DOCSIS 2.0-compliant
cable modems are expected to attempt to come online on another upstream that is configured for
A-TDMA or mixed mode. If no such upstreams are configured, or if the cable modem is configured to
use only that particular upstream, it comes online in the DOCSIS 1.x mode.
Note DOCSIS 2.0-compliant cable modems that are already online on a TDMA-only upstream do not
automatically reregister on another upstream that has been configured for mixed-mode operations. The
cable modem must either be reset or the CMTS must send an Upstream Channel Change (UCC) message
to instruct the cable modem to move to the new channel.
If you change an upstream port to the mixed TDMA/A-TDMA mode, and some cable modems remain
offline, or appear to come online but cannot pass traffic, upgrade the modem software to a
DOCSIS-compliant software version.
Note The cable physical plant must support the higher upstream bandwidths and symbol rates to be able to
use the A-TDMA or mixed mode modulation profiles.
Examples The following example configures the first four upstreams for the first downstream on the
Cisco uBR-MC28U/X cable interface line card in slot 5/0. The first two upstreams are configured for
A-TDMA mode and the last two upstreams are configured for mixed TDMA/A-TDMA mode.
Router# config terminal
Router(config)# interface cable 5/0/0
Router(config-if)# cable upstream 0 docsis-mode atdma
%%Docsis mode set to ATDMA only, 1.x CMs will go offline.
%%The following defaults will be set:
%%Channel Width 6.4MHz
%%Minislot Size 1 tick
%%Modulation Profile 241
Router(config-if)# exit
Router(config)# exit
Router#
The following example shows the abbreviations needed to configure TDMA-only and mixed
TDMA/A-TDMA modes.
Router# config terminal
Router(config)# interface cable 4/0
Router(config-if)#
Command Description
show cable modulation-profile Displays the modulation profile information for a
Cisco CMTS.
show interface cable mac-scheduler Displays the current time-slot scheduling state and
statistics.
Syntax Description n Specifies the upstream port number. Valid range is from 0 to 7 for
upstream ports in the cable interface line card.
Usage Guidelines The DOCSIS 1.1 and 2.0 specifications allow a CMTS to specify a pre-equalization coefficient in the
DOCSIS ranging response (RNG-RSP) MAC management messages it forwards to the cable modems
(CM)s. When this is enabled, a CM can engage in transmit-side equalization (pre-equalization) to
mitigate the effects of certain impairments in the cable plant, such as in-channel tilt, and group delay.
These impairments are more significant with higher order modulation formats such as 64-QAM or
16-QAM, and near the first octave break-point of the diplex filters (34 MHz to 38 MHz). This
break-point exists predominantly as a time-domain group delay issue, and becomes severe for longer
amplifier cascades.
Each amplifier causes the DOCSIS upstream signal to traverse two diplex filters. All diplex filter
frequency splits (5-42 MHz, 5-65 MHz, or 5-88 MHz) share this characteristic, which is not visible in a
frequency response measurement or sweep test.
Note For more information about the use of pre-equalization, see the DOCSIS 2.0 RFI specification section
6.2.15, Transmit Pre-Equalizer, and section 8.3.6 Ranging Response (RNG-RSP) MAC Management
Messages.
DOCSIS 1.1 specifies the Type 4 type length value (TLV), and an 8-tap equalizer. DOCSIS 2.0 adds the
Type 9 TLV, and increases the equalizer to support 24 taps to compensate for more complex impairments.
The cable upstream equalization-coefficient command configures the CMTS to send Type 4 TLV or
Type 9 TLVs in the DOCSIS RNG-RSP MAC management messages to the CMs.
The no form of the command disables the CMTS from sending Type 4 TLV or Type 9 TLVs in the
DOCSIS RNG-RSP MAC management messages to the CMs.
After the CMTS stops sending pre-equalization TLVs to the CM, the CM must retain these values until
the modem’s cable interface resets, or a modification is made to the upstream channel descriptor (UCD),
which would make the stored equalization coefficients invalid.
You can reset the equalizer coefficient of all CMs on an upstream by:
• Changing the upstream center frequency. A 16-kHz or 32-kHz change is sufficient and unlikely to
take many CMs offline.
• Briefly changing the periodic ranging messages in the modulation profile between 16-QAM and
Quadrature Phase Shift Keying (QPSK), or 64-QAM and 16-QAM.
A CMTS operating in a pure DOCSIS 2.0 upstream mode sends equalizer data supporting 24 taps to all
modems during initial ranging.
The cable up 0 docsis-mode atdma command configures a DOCSIS 2.0-only upstream mode on the
CMTS.
A CMTS operating in a DOCSIS 1.1 or mixed TDMA-ATDMA upstream mode sends equalizer data
supporting 8 taps to all modems during initial ranging. The CMTS cannot send data supporting 24 taps
until it is notified by the CM, that it is DOCSIS 2.0 compliant in the Registration Request (REG-REQ)
message, immediately preceding the online state.
This can be configured on the CMTS using the cable up 0 docsis-mode tdma-atdma command.
When a CM receives a Type 4 TLV in the RNG-RSP MAC management message from the CMTS, it must
combine the previously stored values with the new values from the CMTS. Under certain HFC plant
conditions, a dynamic impairment occurs that require the CM to adjust its main equalizer tap. The
DOCSIS standard specifies a convolution function that is sometimes unable to adjust for dynamic
impairments. The result, is a CM whose signal-to-noise ratio (SNR) value as received by the CMTS, is
quite low compared to other CMs on the same upstream.
In a mixed modulation profile, where station maintenance is of a lower order modulation format than the
data grants, it is possible for the modem to enter a steady state where the SNR estimate is:
• Below the required estimate for data grants to be processed by the CMTS
• Above the requirement for station maintenance
This results in a modem that responds to DOCSIS Layer 2 pings, but not to Layer 3 traffic. The following
commands can be used to check status:
• ping docsis {cm-mac address | cm ip address}—succeeds
• ping ip {cm IP address | CPE IP address}—fails
A cable modem whose SNR estimate is in this condition may enter the expired(pt) state when baseline
privacy interface plus (BPI+) is enabled. A modulation profile where station maintenance and data grants
are of the same order modulation, prevents this condition.
The CMTS may be configured to enable cable upstream pre-equalization on a per upstream port basis,
and may be configured to disable the sending of upstream equalization-coefficients on a per modem
MAC address or Organizational Unique Identifier (OUI) basis, using the related global exclude
commands.
Note Some DOCSIS 2.0 compliant CMs / embedded media terminal adapters (EMTA)s have been known to
report as DOCSIS 1.1 compliant to the CMTS, unless connected to a DOCSIS 2.0 format upstream.
These CMs are treated by the CMTS as DOCSIS 1.1, and only send 8-tap equalizer coefficients. A
firmware or SNMP set may be used on these cable modems to enable the proper reporting of DOCSIS
2.0 compliance under a DOCSIS 1.1-style upstream (for example, 3.2 MHz, 16-QAM, TDMA format).
Some older DOCSIS cable modem firmware versions will incorrectly process the transition from 8 to 24
taps when in a mixed TDMA-ATDMA mode, and will experience degrading or low SNR MER as
displayed with show cable modem phy command. Upgrade the CM firmware, and temporarily move
these modems to a pure DOCSIS 1.1 or 2.0 channel or disable pre-equalization for these devices with
the exclude command.
Examples The example shows how to enable the use of the pre-equalization coefficient on upstream port 0 in the
cable interface line card in slot 5/1 on the Cisco uBR10012 router, while excluding the equalization
coefficient messaging to a modem with MAC address aaaa.bbbb.cccc, and all modems with the OUI of
00aa.bb:
Router# configure terminal
Router# cable pre-equalization exclude aaaa.bbbb.cccc
Router# cable pre-equalization exclude 00aa.bb
Router(config)# interface cable 5/1/0
Router(config-if)# cable upstream 0 equalization-coefficient
Router(config-if)#
Command Description
show cable modem [verbose] Displays detailed information about the cable modem. Lines
with the string Equalizer describe modem specific equalizer
data.
debug cable range Debugging commands to display the equalizer coefficients being
sent by the CMTS to the cable modem in the DOCSIS RNG-RSP
MAC management messages.
debug cable interface {interface} Debugging commands to display the equalizer coefficients being
{cm-mac-address}[verbose] sent by the CMTS to the cable modem in the DOCSIS RNG-RSP
MAC management messages.
Syntax Description port number Specifies an upstream port number on a cable interface. Valid range is 0 to 7.
Usage Guidelines The pre-equalizer direct load mechanism is enabled by default. However, to use this direct load
mechanism, you must enable the pre-equalization coefficient on an upstream port using the cable
upstream equalization-coefficient command.
The cable upstream equalization-error-recovery command enables the CMTS to send
Type-Length-Value (TLV) Type 9 in the DOCSIS RNG-RSP MAC management messages. This
mechanism helps CMs come online when TLV Type 4 convolved method causes CMs to go offline.
Note The TLV Type 9, called pre-equalizer direct load, supports only the DOCSIS 2.0 or 3.0-certified
modems. When a CM receives TLV Type 9, the CM replaces its data with the new data provided in the
DOCSIS RNG-RSP MAC management messages.
Examples The example shows how to enable the pre-equalizer direct load mechanism on a cable interface line card
in slot 8/0 on the Cisco uBR10012 router.
Router# configure terminal
Router(config)# interface cable 8/0/0
Router(config-if)# cable upstream 0 equalization-error-recovery
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
Usage Guidelines The Cisco CMTS uses FEC to attempt to correct any upstream data that might have been corrupted. To
use this feature, you need to activate FEC on the upstream RF carrier. When FEC is activated, the
Cisco CMTS commands all CMs on the network to activate FEC.
Examples The following example shows how to activate upstream forward error correction:
Router (config-if)# cable upstream 0 fec
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
t-bytes Overrides the FEC strength specified in the modulation profile for this
upstream channel. Valid values are from 0 to 10, where:
• 0 disables FEC.
• 1 is the lowest FEC strength.
• 10 is the highest FEC strength.
Examples The following example shows how to configure the cable upstream fec-strength command:
Router(config-if)# cable upstream 2 fec-strength 3
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
Command Default By default, fragmentation is enabled for all upstream ports on ASIC line cards (Cisco uBR-MC11C,
Cisco uBR-MC12C, Cisco uBR-MC14C, Cisco uBR-MC16C, Cisco uBR-MC16S, and
Cisco uBR-MC28C) and disabled for all upstream ports on old FPGA line cards.
Note Cisco IOS Release 12.1 CX supports the Multiple Grant Mode of DOCSIS 1.1 fragmentation.
Usage Guidelines This command enables and disables DOCSIS layer 2 fragmentation, which reduces run-time jitter
experienced by constant bit rate (CBR) slots on the corresponding upstream. Disabling fragmentation
increases the run-time jitter, but also reduces the fragmentation reassembly overhead for fragmented
MAC frames. For ports running CBR traffic, fragmentation should be enabled (the default).
Examples The following command shows DOCSIS fragmentation being enabled on upstream 0 on the cable
interface in slot 2/0:
Router# configure terminal
Router(config)# interface c2/0
Router(config-if)# cable upstream 0 fragmentation
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
fragment-threshold (Optional) Number of bytes for the threshold at which DOCSIS frames are
fragmented. The valid value ranges from 1,500 to 3,500 bytes, with the
default value of 2,000 bytes.
For Cisco uBR10-MC5X20S cable interface line card running Cisco IOS
Release 12.3(23)BC1, the valid value ranges from 0 to 1,987 bytes, with the
default value of 1,600 bytes.
number-of-fragments (Optional) Number of fragments that the cable interface line card should
create when fragmenting DOCSIS frames. The card attempts to create this
many equal-sized fragments when fragmenting. The valid value ranges from
1 to 10 fragments, with the default value of 3 fragments.
The number-of-fragments option has been deprecated. See Usage Guidelines
section for more details.
Usage Guidelines DOCSIS 1.1 allows the CMTS to fragment DOCSIS frames to improve performance, especially in
networks that combine real-time traffic, such as voice, with data traffic. The cable upstream
fragment-force command allows you to specify the size of frames that should be fragmented, as well as
the number of fragments that should be created when fragmenting.
Tip This command takes effect only when fragmentation has been enabled on the upstream using the cable
upstream fragmentation command (which is the default configuration).
In the default configuration, the Cisco CMTS fragments DOCSIS frames that are 2,000 bytes or larger
in size, and it fragments these frames into equally-sized fragments. Starting from Cisco IOS Release
12.2(21a)BC, 12.2(33)SCB, and later releases, the larger frames are fragmented by the threshold. Instead
of dividing frames into equal number of fragments as before, the concatenated frames are cut into many
fragments, as defined in the threshold size, with the last one being the shortest. For example, the previous
form of the cable upstream fragment-force command fragments a concatenated frame of 9000 into 5
frames of 1800. The new form of the cable upstream fragment-force command fragments a
concatenated frame of 9000 into frames of 2000, 2000, 2000, 2000, and 1000.
Do not use a fragment size greater than 1,600 bytes on the Cisco uBR10-MC5X20S cable interface line
card running Cisco IOS Release 12.3(23)BC1. Do not use a fragment size greater than 2,000 bytes on
the Cisco uBR10-MC5X20U cable interface line card, and do not use a fragment size greater than 3,500
bytes on all other cable interface line cards, unless otherwise instructed by a Cisco TAC engineer.
When using DOCSIS concatenation, you might need to change the cable default-phy-burst command
from its default size, so that multiple frames can be concatenated into a maximum-sized burst. If you set
the cable default-phy-burst command to zero, the max burst then becomes the lowest of 255 mini-slots,
the maximum concatenated burst setting in the DOCSIS configuration file, or the value of the long data
grant burst that is specified in the upstream’s profile.
When you set the cable default-phy-burst command to zero, the CMTS fragments large requests into
big chunks and the cable modems will not be able to register on specific groupings of upstream interfaces
due to the large fragment size. We recommend the use of a fragment size of 2,000 bytes, if you want to
set the cable default-phy-burst command to zero to provide upstream speed of above 5 Mbps.
Caution Ensure that the number-of-fragments parameter is large enough to keep the size of each fragment of a
maximum-sized burst less than the 1,600 bytes or 2,000 bytes or 3,500 bytes specified above. If
fragments are too large, the cable modem might not be able to come online or pass traffic.
Note The number-of-fragments option has been deprecated from Cisco IOS Release 12.2(21a)BC,
12.2(33)SCB, and later releases.
Examples The following example shows how to enable DOCSIS fragmentation on frames that are 1,500 bytes or
larger, using four fragments per frame:
Router# configure terminal
Router(config)# interface c2/0
Router(config-if)# cable upstream 0 fragment-force 1500 4
Router(config-if)#
The following example shows how to disable the forced fragmentation of DOCSIS frames on an
upstream. This also resets the fragment-threshold parameter to default value.
Router# configure terminal
Router(config)# interface c5/1/0
Router(config-if)# no cable upstream 0 fragment-force
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
% of frequency adjustment Specifies the percentage of frequency-adjustment packets required to
switch from the regular power-adjustment method to the noise
power-adjustment method. Valid range is from 10 to 100 percent.
Examples The following example shows how to change the power-adjustment method when the
frequency-adjustment packet count reaches 50 percent:
Router(config-if)# cable upstream 0 freq-adj averaging 50
Syntax Description n Specifies the upstream port number on the cable interface line card for
which you want to assign an upstream frequency. Valid values start with 0
for the first upstream port on the cable interface line card.
up-freq-hz The upstream center frequency is configured to a fixed Hertz (Hz) value.
The valid upstream frequency range is 5 MHz (5000000 Hz) to 42 MHz
(42000000 Hz), 55 MHz (55000000 Hz), or 65 MHz (65000000 Hz),
depending on the cable interface line card being used. If you wish to have
the Cisco CMTS dynamically specify a center frequency for the given
upstream interface, do not enter any frequency value.
Usage Guidelines The upstream channel frequency of your RF output must be set to comply with the expected input
frequency of your cable interface line card. To configure an upstream channel frequency, you may:
• Configure a fixed frequency between the allowable ranges and enable the upstream port,
or
• Create a global spectrum group, assign the interface to it, and enable the upstream port.
The allowable range for the upstream channel frequency depends on the cable interface line card and
Cisco IOS software release being used. See Table 17 for the currently supported values.
Table 17 Allowable Frequency Range for the cable upstream frequency Command
Note In Cisco IOS Release 12.2(15)BC2 and later releases, the allowable range of frequencies that you can
select with the cable upstream frequency command is determined by the configuration of the upstream
freq-range command.
Tip If both a Cisco uBR-MC16E cable interface line card and a Cisco uBR-MC16C and/or a
Cisco uBR-MC16S cable interface line card are present in the chassis, a spectrum group in the 42 MHz
to 65 MHz range should not be assigned.
To configure the default upstream frequency (which is no fixed frequency), enter the cable upstream n
frequency command without specifying a center frequency.
Examples The following example shows how to configure the upstream center frequency for port 0, located in slot
6, to 5,700,000 Hz:
Router(config-if)# cable upstream 0 frequency 5700000
Router(config-if)# exit
Router(config)# exit
Router# show running-config | include frequency
cable upstream 0 frequency 5696000
Router#
Note Cisco cable interface line cards always program the upstream’s center frequency in 16 KHz increments,
and this is the frequency displayed by the lines added to the router’s configuration and by the show
controllers cable upstream command. For example, if you use the cable upstream frequency
command to specify a center frequency of 27 MHz (cable upstream x frequency 27000000), the actual
center frequency will be 27.008 MHz, which is the next highest 16 KHz boundary. The configuration file
will therefore show the line cable upstream 0 frequency 27008000.
The following example shows how to configure the upstream center frequency to a frequency
(54,700,000 Hz) within the extended Japanese frequency range:
Router# configure terminal
Router(config)# upstream freq-range japanese
The following example shows how to allow the Cisco CMTS to dynamically specify a center frequency
for the upstream port 0:
Router(config-if)# no cable upstream 0 frequency
The following command example from Cisco IOS Release 12.3 BC illustrates the allowable upstream
frequency range in Hz:
Syntax Description n Specifies the upstream port for which blind frequency hopping will be
activated. Valid values start with 0 for the first upstream port on the
cable interface line card.
Usage Guidelines Enter this command to override the hardware spectrum manager’s decision to optimize hopping.
Note Do not use this command unless you have a specific reason to disable optimum hopping configurations.
For example, if you are experimenting with a Cisco uBR-MC16S or Cisco uBR-MC5X20S/U card, you
can use this command to enforce blind hopping on individual upstream channels.
Examples The following example shows how to specify hopping blind on the upstream port 0:
Router(config-if)# cable upstream 0 hopping blind
Command Description
cable upstream power-level Specifies the upstream cable interface receive power
level in dBmV.
cable upstream shutdown Activates or shuts down a specified upstream cable
interface.
Syntax Description n Specifies the upstream port. Valid values start with 0 for the
first upstream port on the cable interface line card.
frequency, modulation, channel-width Specifies the priority of corrective actions to be taken when
ingress noise occurs on a downstream.
Note The channel-width option must come after the
frequency option, either immediately or after the
modulation option, as shown in the above examples.
Usage Guidelines This command specifies the priority of the corrective actions that should be taken when a frequency hop
is necessary to correct excessive ingress noise on an upstream. For example, if the upstream on a
Cisco uBR-MC16S card is set for the default settings (frequency, modulation, and channel-width), the
following occurs when the upstream noise exceeds the CNR threshold value for the current modulation
profile:
1. The Cisco uBR-MC16S changes to a new frequency, if a clean frequency is available in its spectrum
group.
2. If no clean frequency is available, the Cisco uBR-MC16S uses the Dynamic Upstream Modulation
feature to switch the upstream to the secondary modulation profile.
3. If the noise levels still exceed the CNR threshold value for the secondary modulation profile, and if
the upstream has been configured for a range of channel widths, the Cisco uBR-MC16S narrows the
channel width of the upstream by half. If the noise levels are still excessive, the channel width is
again cut in half, and this process continues until a clean upstream is found or the bandwidth is
reduced to the minimum channel width that has been configured using the cable upstream
channel-width command.
Allowable DOCSIS channel widths are 3.2 MHz, 1.6 MHz, 800 KHz, 400 KHz, and 200 KHz. If the
channel width drops to 200 KHz, but the noise still exceeds the SNR threshold, the CMs go offline.
Note The default specifies only a single channel width of 1.6 MHz. If this is not changed to
specify a range of allowable channel widths (using the cable upstream channel-width
command), the Cisco uBR-MC16S does not attempt to change the channel width.
To use the Dynamic Upstream Modulation feature, you must first create two modulation profiles (using
the cable modulation-profile command) and assign them to the upstream (using the cable upstream
modulation-profile command).
Examples The following example shows that when ingress noise on the upstream exceeds the threshold allowed for
the primary modulation profile, the Cisco uBR-MC16S line card should first switch to the secondary
modulation profile, then try frequency hopping, and if that fails to correct problem, to finally try
narrowing the channel width:
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 hop-priority modulation frequency channel-width
Router(config-if)# exit
Router(config)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
interval Triggering interval, in milliseconds. The valid range is 10 to 3000
milliseconds, with a default value of 200 milliseconds.
Usage Guidelines
Note This command is available only on the Cisco uBR10-MC5X20H BPE, Cisco uBR-MC16U/X, and
Cisco uBR-MC28U/X cable interface line cards. It cannot be used on other cable interface line cards.
Cable interface line cards, such as the Cisco uBR-MC28U/X cards, contain advanced hardware-based
noise cancellation circuitry that digitally removes in-channel impairments such as ingress, common path
distortion, and certain types of impulse noise. To configure how often these line cards should train their
noise cancellation circuity, so as to adapt to changes in the noise types and levels, use the cable
upstream ingress-noise-cancellation command.
When you enable ingress noise cancellation on an upstream, the Cisco CMTS periodically schedules a
256-symbol idle slot on the upstream channel. The interval option specified in the cable upstream
ingress-noise-cancellation command determines how often this idle slot is generated.
The default for BPE cards is for the card to train its circuitry every 200 milliseconds. The smaller the
triggering interval, the faster the card can adjust to changes in ingress noise, which makes the upstream
more robust to noise problems, but at the cost of decreasing bandwidth on the upstream channel. To
determine the bandwidth cost, in percentage of raw bandwidth, use the following formula:
(256/interval)/channel-symbol-rate
where interval is the time period in milliseconds specified by the cable upstream
ingress-noise-cancellation command, and channel-symbol-rate is the symbol rate in kilohertz. For
example, if the upstream is using a 2.56 MHz channel rate and a noise cancellation interval of 10
milliseconds, the bandwidth cost is 1% of the total raw bandwidth:
(256/10)/2560 = 0.01 (1% of bandwidth)
Examples The following example shows how to configure the first upstream on a Cisco uBR-MC16U/X or
Cisco uBR-MC28U/X card to perform ingress noise cancellation every 300 milliseconds:
interface cable 5/0
cable upstream 0 ingress-noise-cancellation 300
Related Commands cable modulation-profile Defines a modulation profile for use on the router.
cable upstream channel-width Specifies an upstream channel width for an upstream port.
cable upstream docsis-mode Configures an upstream to use either DOCSIS 1.x or DOCSIS
2.0 modulation profiles.
cable upstream frequency Enters a fixed frequency of the upstream RF carrier for an
upstream port.
cable upstream minislot-size Specifies the minislot size (in ticks) for a specific upstream
interface.
cable upstream modulation-profile Assigns one or two modulation profiles to an upstream port.
cable upstream power-level Sets the input power level for the upstream RF carrier in decibels
per millivolt (dBmV).
show cable hop Displays CM configuration settings.
show cable modulation-profile Displays the modulation profile information for a Cisco CMTS.
show interface cable mac-schedule Displays the current time-slot scheduling state and statistics.
show interface cable sid Displays cable interface information.
Syntax Description uport Specifies the upstream port that should be assigned to the load-balance
group. Upstream port values start with 0 and end with a value that depends
on the number of upstream ports on the cable interface line card.
n Specifies the number of the load-balance group to which the upstream should
be assigned. The valid range is 1 to 255.
Command Default An upstream is not assigned to any load-balance groups. If you use the cable load-balance group
(interface configuration) command to assign a downstream interface to a load-balance group, all its
upstreams are automatically assigned to the same group until you use the cable upstream load-balance
group command to reassign an upstream to a different group.
Usage Guidelines After you have used the cable load-balance group (global configuration) command to initially create
and configure a load-balance group, use the cable upstream load-balance group command to assign
this load-balance group to an upstream. This enables the cable interface to begin participating in
load-balancing operations.
Tip Use the cable load-balance group (interface configuration) command to assign this load-balance
group to a downstream.
The following rules apply when creating and assigning load-balance groups:
• A downstream or upstream can belong to only one load-balance group.
• All downstreams and upstreams in a load-balance group must share physical radio frequency (RF)
connectivity to the same group of cable modems. Downstreams can be in a separate load-balance
group than upstreams, but all downstreams or all upstreams that have the same RF physical
connectivity must be members of the same load-balance group. You cannot distribute downstreams
or upstreams that share physical connectivity across multiple load-balance groups.
• Load balancing is done only on a per-chassis basis—all interfaces in a load-balance group must be
in the same chassis.
Examples The following example shows how to assign the first four upstreams for cable interface 5/1 to load
balance group 14:
Router# config terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable upstream 0 load-balance group 14
Router(config-if)# cable upstream 1 load-balance group 14
Router(config-if)# cable upstream 2 load-balance group 14
Router(config-if)# cable upstream 3 load-balance group 14
Router(config-if)#
Syntax Description uport Specifies the upstream port to be configured. Upstream port values start with
0 and end with a value that depends on the number of upstream ports on the
cable interface line card.
Command Default Cable modems are not required to maintain their power spectral density after a modulation rate change
(no cable upstream maintain-psd)
Note In Cisco IOS Release 12.2(15)BC2 and later releases, this command is automatically removed from the
configuration when you configure an upstream for a TDMA-only or mixed TDMA/A-TDMA
configuration.
Usage Guidelines Use this command to specify whether DOCSIS 2.0 CMs should maintain their power spectral density
when the Cisco CMTS changes their upstream modulation rate in an upstream channel descriptor (UCD)
message. When you configure an upstream with the cable upstream maintain-psd command, the
Cisco CMTS sets TLV 15 (Maintain Power Spectral Density) to ON in the UCD messages it sends to the
CMs on that upstream.
When TLV 15 is on, and when the new UCD specifies a new upstream modulation rate for the CM, the
CM must change its transmit power level to keep its power spectral density as close as possible to what
it was before the modulation rate change. The CM must maintain this power spectral density until the
CMTS sends a power adjustment command in a Ranging-Response (RNG-RSP) message.
The default configuration (no cable upstream maintain-psd) configures TLV 15 to OFF, and CMs are
not required to maintain their power spectral density after a modulation rate change. However, per the
DOCSIS specifications, the CMs continue to maintain constant total input power on the upstream.
Note This command affects only DOCSIS 2.0 CMs that are online an upstream that is configured for the
DOCSIS 2.0 A-TDMA-only mode. This command has no effect on DOCSIS 1.0 and DOCSIS 1.1 CMs,
which will continue to maintain constant total input power on the upstream, per the DOCSIS 1.x
specifications.
Examples The following example shows how to configure four upstreams on a cable interface line card to require
cable modems to maintain a constant power spectral density after a modulation rate change.
Router# configure terminal
Router(config)# interface cable c6/1/0
Router(config-if)# cable upstream 0 maintain-psd
Router(config-if)# cable upstream 1 maintain-psd
Router(config-if)# cable upstream 2 maintain-psd
Router(config-if)# cable upstream 3 maintain-psd
Router(config-if)# exit
Router(config)# exit
Router#
The following example shows how to configure an upstream for the default behavior, which is that CMs
are not required to maintain a constant power spectral density after a modulation rate change, but do
continue to maintain constant total input power levels on the upstream.
Router# configure terminal
Router(config)# interface cable c5/1/0
Router(config-if)# no cable upstream 0 maintain-psd
Router(config-if)# exit
Router(config)# exit
Router#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
code Specifies the number of codes-per-subframe. Valid values range from 1
to 128, with a default value of 2.
Command Default The maximum codes per subframe setting cannot be applied if the Synchronous Code Division Multiple
Access (S-CDMA) is not configured.
Usage Guidelines This command is applicable only for S-CDMA channels. You should configure S-CDMA to apply the
the maximum codes-per-subframe setting. The number of codes-per-subframe should not exceed the
number of active codes.
Examples The following example sets the number of codes-per-subframe to 128 on the upstream port 0:
Router(config)# interface cable 7/0/4
Router(config-if)# cable upstream 0 max-codes-per-subframe 128
Router(config-if)#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
max-interleave-step Specifies the maximum number of interleave steps. Valid values range
from 1 to 31, with a default value of 1.
Command Default The maximum interleave step setting cannot be applied if the Synchronous Code Division Multiple
Access (S-CDMA) feature is not configured.
Usage Guidelines This command is applicable only for S-CDMA channels and the command limits the maximum number
of interleave steps for a given upstream port. The max-interleave-step value should be less than the
spreading-interval value specified using the cable upstream spreading-interval command.
Examples The following example sets the number of interleave steps to 31 on the upstream port 0:
Router(config)# interface cable 7/0/4
Router(config-if)# cable upstream 0 max-interleave-steps 31
Router(config-if)#
cable upstream Specifies the upper limit and the maximum value of
max-codes-per-subframe codes-per-subframe defined in the individual modulation profile
setting for an upstream channel.
cable upstream Specifies the spreading interval for SCDMA on an upstream channel.
spreading-interval
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
code Specifies the number of logical channels per port. Valid values are 1 and
2.
Command Default The maximum logical channels setting cannot be applied if the Synchronous Code Division Multiple
Access (S-CDMA) is not configured.
Usage Guidelines The cable upstream max-logical-chans command limits the number of logical channels per port on an
upstream channel. The default value is 1.
When two logical channels are configured through cable upstream max-logical-chans command, both
logical channels are mapped to the same physical port specified and the physical upstream bandwidth is
shared between the two logical channels. However, from the cable modem perspective, each logical
channel appears as an independent upstream channel.
When multiple logical channels are configured, the upstream related commands are categorized into two
groups: physical port level and logical channel level.
Note Multiple logical channels and Spectrum groups cannot be configured on the same upstream port.
Note The above logical channel level commands are not available at the physical port level, when logical
channels are configured. However, the cable upstream shutdown and cable upstream threshold
commands operate both at the physical and at the logical channel level.
The physical upstream port level commands such as cable upstream frequency and cable upstream
channel-width affects all logical channels configured under a physical port.
Examples The following example sets two logical channels on the upstream port 0:
Router(config)# interface cable 7/0/4
Router(config-if)# cable upstream 0 max-logical-chans 2
Router(config-if)#
Command Default 4
Command Modes
Release Modification
12.2(15)BC1 This command was introduced to support the Cisco uBR-MC5X20S
cable interface line card.
12.2(15)BC2 Support was added for the Cisco uBR-MC5X20U cable interface line
card.
Usage Guidelines Use this command to specify how many upstreams a downstream (MAC domain) will support on the
Cisco uBR-MC5X20S card, before using the cable upstream connector command to assign upstreams
to physical ports on the card. The downstreams on a card can be configured for different maximum
upstream values.
After using this command, the valid range for upstreams on that cable interface will be from 0 to one
less than the maximum port value. For example, if you use the cable upstream max-ports 6 command
to specify a maximum of 6 upstreams for the downstream, the valid range for upstreams will be 0 to 5.
Examples The following example shows how to configure all of the downstreams on a Cisco uBR-MC5X20S card
for a maximum number of 6 upstreams.
Router# configure terminal
Router(config)# interface cable c6/1/0
Router(config-if)# cable upstream max-ports 6
Router(config-if)# interface cable c6/1/1
Router(config-if)# cable upstream max-ports 6
Router(config-if)# interface cable c6/1/2
Router(config-if)# cable upstream max-ports 6
Router(config-if)# interface cable c6/1/3
Router(config-if)# cable upstream max-ports 6
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
size Specifies the minislot size in time ticks. Valid minislot sizes are:
• 1—(32 symbols at 6.4MHz channel width) Supported by the
Cisco uBR-MC16U/X, Cisco uBR-MC28U/X and
Cisco uBR-MC5X20S/U cable interface line cards when operating
in Advanced TDMA (A-TDMA) DOCSIS 2.0 only mode.
• 2 (32 symbols at at 3.2 MHz channel width)
• 4 (64 symbols at 3.2 MHz channel width)
• 8 (128 symbols at 3.2 MHz channel width)
• 16 (256 symbols at 3.2 MHz channel width)
• 32 (512 symbols at 3.2 MHz channel width)
• 64 (1024 symbols at 3.2 MHz channel width)
• 128 (2048 symbols at 3.2 MHz channel width)
Command Default The default settings vary, depending on the upstream’s channel width. The default values were changed
in Cisco IOS Release 12.2(15)BC1 and later releases to better optimize data and voice traffic on the
upstream. Table 18 on page 605 lists the default minislot values for each channel width for Cisco IOS
releases before and after Cisco IOS Release 12.2(15)BC1.
Release Modification
12.2(15)BC1 The default minislot size was reduced to optimize the upstream for data and
Voice-over-IP (VoIP) traffic. The previous defaults produced 16 bytes per
minislot when using QPSK modulation and a 1.6 MHz channel width, and the
new defaults produce 8 bytes per minislot with the same configuration.
12.2(15)BC2 Support was added for the minislot size of 1 to support DOCSIS 2.0
A-TDMA and mixed modulation profiles on the Cisco uBR-MC5X20S/U
cable interface line cards.
Usage Guidelines The minislot size determines the minimum amount of information that can be transmitted on the
upstream. How much a particular minislot size can contain depends on the modulation profile and
channel width being used, with higher-bandwidth settings allowing larger amounts of data.
Because DOCSIS specifications require that the minislot size contain at least 32 symbols, you might
need to change the minislot size whenever you change the channel width or modulation of an upstream,
to meet the DOCSIS requirements.
Note In Cisco IOS Release 12.2(15)CX, Cisco IOS Release 12.2(15)BC2, and later releases, manually
changing the minislot size is not needed on the Cisco uBR-MC16U/X, Cisco uBR-MC28C, and
Cisco uBR-MC28U/X cards, because these cards automatically change the minislot size when the
channel width is changed, to produce 32 symbols per minislot, as required by the DOCSIS
specifications.
Table 18 lists the default minislot sizes for each channel width for Cisco IOS releases before and after
Cisco IOS Release 12.2(15)BC1.
Releases Earlier than Cisco IOS Release Cisco IOS Release 12.2(15)BC1 and Later
12.2(15)BC1 (creates 64 symbols and 16 bytes Releases (creates 32 symbols and 8 bytes per
per minislot) minislot)
Default Minislot Size (in Default Minislot Size (in
Channel Width Ticks) Channel Width Ticks)
0.2 MHz 64 0.2 MHz 32
0.4 MHz 32 0.4 MHz 16
0.8 MHz 16 0.8 MHz 8
1.6 MHz 8 1.6 MHz 4
3.2 MHz 4 3.2 MHz 2
6.4 MHz 11
(DOCSIS 2.0 only)
1. You must be using a 6.4 MHz channel width if using a minislot size of 1 tick. Otherwise, you will violate the DOCSIS
requirements that each minislot should contain 32 symbols.
Caution Using values of 64 or 128 for higher symbol rates such as 1280 kilosymbols/second or
2560 kilosymbols/second can cause performance problems. Depending on your current setting’s symbol
rate, you should select the minislot size (in ticks) that yields a minislot size of 32 or 64 symbols.
Examples The following example shows how to set the minislot size on upstream port 4 to 16:
Router# configure terminal
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 4 minislot-size 16
Router(config-if)# exit
Router(config)# exit
Router#
Related Commands cable modulation-profile Defines a modulation profile for use on the router.
cable upstream channel-width Specifies an upstream channel width for an upstream port.
cable upstream docsis-mode Configures an upstream to use either DOCSIS 1.x or
DOCSIS 2.0 modulation profiles.
cable upstream equalization-coefficient Enables the use of a DOCSIS 1.1 pre-equalization
coefficient on an upstream.
cable upstream modulation-profile Assigns one or two modulation profiles to an upstream
port.
show cable hop Displays CM configuration settings.
show cable modulation-profile Displays the modulation profile information for a
Cisco CMTS.
show interface cable mac-schedule Displays the current time-slot scheduling state and
statistics.
show interface cable sid Displays cable interface information.
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
primary-profile number Specifies the number identifying the primary modulation profile for the
upstream port. The primary modulation profile is used when the
upstream is operating with nominal noise conditions. The valid values
depend on the cable interface being used and the mode of operation.
See Table 19 for a list of valid ranges according to cable interface and
modulation type.
secondary-profile-number (Optional) Specifies the secondary modulation profile for the upstream
port, which is used when noise on the upstream increases to the point
that the primary modulation profile can no longer be used. The valid
values are the same ranges as the primary modulation profile.
The secondary modulation profile should specify a more robust
performance profile (in terms of coping with noise) than the primary
profile. The secondary profile is used for both basic and advanced
dynamic modulation.
tertiary-profile-number (Optional) Specifies the tertiary modulation profile for the upstream
port, which is used when noise on the upstream increases to the point
that the secondary modulation profile can no longer be used.
The tertiary modulation profile is only available for the basic dynamic
modulation. You cannot use the tertiary modulation profile when a
spectrum group is defined for the upstream.
Command Default Default modulation profiles are created, using profile numbers 1, 21, 41, 101, 121, 201, 221, 241, 321,
and 381 depending on the DOCSIS mode and the cable interface line cards being used. See Table 19 for
a list of the valid ranges for the individual cable interface cards.
Usage Guidelines The cable upstream modulation-profile command assigns up to three modulation profiles to an
upstream port, depending on the type of cable interface and Cisco IOS software release being used. The
third modulation profile is only available for the basic dynamic modulation and is unavailable when a
spectrum group is defined for the upstream.
Note For more information on this form of the Dynamic Upstream Modulation feature, see the
chapter, Spectrum Management for the Cisco Cable Modem Termination System, in the
Cisco CMTS Feature Guide.
When Dynamic Upstream Modulation is enabled and spectrum groups are configured on the same
interface, the line cards respond to excessive noise by first switching to the secondary modulation
profile. If the noise conditions worsen, the line card changes the modulation or frequency hopping
in an attempt to find a new upstream channel, and if that fails, the line card reduces the channel
width.
Note The default priority of switching modulation profile is frequency (F), modulation (M), and
channel-width (C). However, it is user configurable and can be changed to MFC or FCM.
• The upstream port is on a Cisco uBR-MC16U/X line card that is used on Cisco CMTS routers using
Cisco IOS Release 12.1(7)CX1 or later release, or on a Cisco uBR-MC5X20S/U/H line card.
The Dynamic Upstream Modulation feature on the Cisco uBR-MC16U/X line card is identical to
other line cards except that the spectrum management hardware onboard the Cisco uBR-MC16U/X
or Cisco uBR-MC5X20S/U/H line card uses the CNR value (you can use only the CNR value for a
dual profile configuration) in conjunction with the SNR value. The CNR value is a more accurate
description of noise conditions on the upstream. Because of this, these line cards switch back to the
primary modulation profile when noise conditions improve to a CNR value that is only 3 dB greater
than the threshold value (assuming FEC counters are also below the threshold values).
Note If the Cisco CMTS router is running Cisco IOS Release 12.1(3a)EC1 or a later Cisco IOS
release, the Dynamic Upstream Modulation feature on the Cisco uBR-MC16U/X line card
operates the same as it does on the other line cards.
When Dynamic Upstream Modulation is enabled and spectrum groups are configured on the same
interface, the line cards take corrective action in response to excessive noise, as determined by the
cable upstream hop-priority command (either frequency hopping or changing to the secondary
modulation profile). If the noise conditions worsen, the line card takes the second corrective action
that has been defined, and if that fails, the line card takes the last corrective action.
Note The Dynamic Upstream Modulation feature uses the SNR, CNR, and FEC thresholds for 64-QAM,
16-QAM, and QPSK operation to determine when to switch modulation profiles. We recommend the use
of 64-QAM, 16-QAM, and QPSK for primary, secondary, and tertiary profiles in a Three Step Dynamic
Upstream Modulation.
For dual profile configuration, we recommend the use of 16-QAM or mixed 16-QAM and QPSK
modulation for primary profile and QPSK modulation for the secondary profile. However, this is
optional. Both modulation profiles can be either QPSK or QAM. It is not mandatory that one is QAM
and the other QPSK, but modulation profile switchover is tied to the QAM and QPSK thresholds.
Tip Modulation profiles must be first created using the cable modulation-profile command before they can
be assigned using the cable upstream modulation-profile command.
Table 19 Supported Channel Widths and DOCSIS Modes for Cable Interfaces
2. The UBR-MC20X20V cable interface line card has three variants, UBR-MC20X20V-0D, UBR-MC20X20V-5D, and UBR-MC20X20V-20D. The
UBR-MC20X20V-0D line card supports 20 upstreams and zero (no) downstreams. The UBR-MC20X20V-5D line card supports 20 upstreams and five
downstreams, and the UBR-MC20X20V-20D line card supports 20 upstreams and 20 downstreams.
In addition to the legacy modulation profile number schemes, the new global modulation profile scheme
introduced in Cisco IOS Release 12.2(33)SCC, allows you to assign any modulation profile number to
any DOCSIS-mode up to 400, without any restrictions.
The global modulation profile mode allows you to create and configure DOCSIS 3.0 channel type 4SR
(scdma-d3). When an upstream's DOCSIS mode is changed into scdma-d3 , it is initially assigned to the
system created default modulation profile as shown in Table 19.
Note Though you can assign any number between 1 to 400 to any modulation profile, the default modulation
profile number assigned to an upstream channel for a given channel type will remain the same. That is,
modulation profile numbers 21, 121, 221, 321, and 381 will be applicable for TDMA, mixed, A-TDMA,
S-CDMA, and DOCSIS 3.0 S-CDMA channel types.
All the existing and previously defined modulation profiles are converted to the new format. However,
all the newly created modulation profiles, which are outside of the legacy number space range, will be
lost when you revert to the legacy modulation profile.
For more details on the new global modulation profile scheme, refer to the cable modulation-profile
global-scheme command.
Examples The following example assigns the primary modulation profile 2, the secondary modulation profile 1,
and the tertiary modulation profile 4 to the upstream port 0 on the cable interface line card in slot 3. This
automatically enables the Dynamic Upstream Modulation feature for all CMs using that upstream.
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 modulation-profile 2 1 4
Router(config-if)#
The following example assigns the primary modulation profile 2 and the secondary modulation profile 1,
to the upstream port 0 on the cable interface line card in slot 3. This automatically enables the Dynamic
Upstream Modulation feature for all CMs using that upstream.
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 modulation-profile 2 1
Router(config-if)#
Command Description
cable upstream hop-priority Determines the order of the corrective actions to be taken when
ingress noise exceeds the allowable value for an upstream.
This command is related to the cable upstream modulation-profile
command only when using advanced dynamic modulation
configuration, that is, when spectrum group is defined for the
upstream channel.
show cable modulation-profile Displays the cable modulation profiles that have been created.
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
continue pwr-level Specifies the power threshold value that determines the value of the
Ranging Status field in the Ranging Response (RNG-RSP) messages
that the CMTS sends to the CM. The valid range is from 2 to 15 dB,
with a default of 2 dB.
threshold value Specifies the power adjustment threshold. The threshold range is from
0 to 10 dB, with a default of 1 dB.
noise perc-pwr-adj Specifies the percentage of power adjustment packets that is required
to change the adjustment method from the regular power-adjustment
method to the noise power-adjustment method, which uses an
averaging algorithm to smooth out wide jumps in the power level. The
valid range is 10 to 100 percent, with a default of 30 percent.
Command Default The continue option defaults to 2 dB, the noise option defaults to 30 percent, and the threshold option
defaults to 1 dB.
Usage Guidelines When a CM comes online, it sets itself for the optimal power level, as determined by the CMTS. As the
CMTS periodically polls each CM, the CMTS examines the CM’s power level and orders the CM to
adjust its power level to adapt to current total attenuation between it and the CMTS. These power
adjustments can be required because of temperature variations, upstream frequency hopping, or
increased attenuation that has been added either intentionally or unintentionally. The cable upstream
power-adjust command controls how the CMTS makes these power adjustments.
Note To set the upstream power level on the CMTS, see cable upstream power-level, page 617.
Note The threshold parameter can be set from 0 dB to 10 dB with a default of 1 dB. However, do not set the
threshold to 0 dB because this means that the CMTS will command all CMs to continually change their
power levels until the CMTS measures the power levels at exactly 0 dBmV. Cisco recommends that you
set the threshold parameter to a minimum of its default value of 1 dB so that the CMs do not change
their power levels continually for minuscule RF plant variations.
Note Cisco recommends designing the network so that CMs are at least 6 dB from the CM’s maximum
transmit power level. This will accommodate new services, changing modulation schemes, different
channel widths, customer-installed passives, temperature variations, and other non-linearities. DOCSIS
specifies a minimal power range of +8 dBmV to +55 dBmV for 16-QAM operation and +8 dBmV to
+58 dBmV maximum power level for QPSK operation. Cisco CMs typically have a maximum power
level of +60 dBmV, which exceeds the DOCSIS standards.
Tip If a number of CMs are transmitting close to their maximum transmit power, try increasing the continue
range to allow the CMTS to continue adjusting the CM’s power levels. This situation can happen when
systems use high value taps, such as 29 dB taps, in the design of the plant.
Note When the CM requires 16 successive power adjustments that are greater than the value of the continue
option, the CMTS reinitializes the CM and starts to rescan downstream carriers, as per the DOCSIS
specification.
Note A CM that shows an exclamation point (!) in the show cable flap-list and show cable modem displays
is typically more prone to packet loss than other CMs.
Tip The cable upstream power-adjust noise command is typically not needed during normal operations,
but it can help in certain situations where the cable plant is experiencing ingress noise and other
interference that is forcing many CMs to frequently re-range. If the show cable flap-list and show cable
modem commands show a large number of CMs with asterisks (*), experiment with the noise option, so
that the CMTS will average its CM power readings before sending any power adjustments to the CMs.
Note When a CM is in power averaging mode, the show cable flap-list and show cable modem commands
shows an asterisk (*) for that particular CM.
Examples The following example shows the commands needed so that the CMTS will begin using the power
averaging adjustment method when 50 percent of Ranging Requests result in a power adjustment beyond
the threshold level of 2 dB:
Router(config)# interface c6/0
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
dbmv Decibels per millivolt designating the upstream signal input power level. Valid
range is –16 dBmV to +26 dBmV, depending on the cable interface and the
upstream’s symbol rate (channel width).
Usage Guidelines The Cisco CMTS controls the output power levels of the CMs to meet the desired upstream input power
level. The nominal input power level for the upstream RF carrier is specified in decibels per millivolt
(dBmV). The default setting of 0 dBmV is the optimal setting for the upstream power level.
The valid range for the input power level depends on the data rate, as expressed as the symbol rate and
channel width. Table 20 shows the valid power levels for each allowable rate, as given in the DOCSIS
specification. Higher (more positive) values cause the CMs to increase their transmit power, achieving
a greater carrier-to-noise ratio (CNR).
Note Some cable interfaces might allow smaller ranges of either –10 to +10 or –10 to +25 dBmV.
Tip You can use inline attenuators to force CMs to transmit at higher power levels and to achieve a higher
CNR value on the network.
Caution If you increase the input power level or add inline attenuators before the CMTS, the CMs on your HFC
network increase their transmit power level. Be careful if you adjust this parameter. You might violate
the upstream return laser design parameters or exceed the CM’s maximum transmit power level.
Note Do not adjust your input power level by more than 5 dB in a 30-second interval. If you increase the
power level by more than 5 dB within 30 seconds, you will disrupt CM service on your network. If you
decrease the power level by more than 5 dB within 30 seconds, the CMs on your network will be forced
to re-range.
Tip When setting upstream power levels, Cisco recommends that the adjacent channels of equal bandwidth
not have a large variation. The recommended maximum input power variance is 5 to 6 dB.
Examples The following example shows how to set the input power level for upstream port 0 to -5 dBmV:
Router(config)# interface cable 5/1/0
Router(config-if)# cable upstream 0 power-level -5
Router(config-if)#
Examples The following example shows how to configure WFQ parameters on a cable interface in slot 7, subslot 1,
and port 0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 7/1/0
Router(config-if)# cable upstream qos wfq class
Router(config-if)# cable upstream qos wfq activity
Router(config-if)# cable upstream qos wfq weights 10 20 30 40 50 60 70 80
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
automatic Specifies the fixed data backoff start and end values.
Note The automatic setting is not supported on
Cisco uBR-MC5X20S/U cable interface line cards, which
should use manually configured ranging backoff instead.
start Binary exponential algorithm. Sets the start value for initial ranging
backoff. Valid values are from 0 to 15.
end Binary exponential algorithm. Sets the end value for initial ranging
backoff. Valid values are from 0 to 15.
Usage Guidelines The DOCSIS-specified method of contention resolution for CMs used to send data or requests on the
upstream channel is a truncated binary exponential back-off with the initial backoff window and the
maximum backoff window controlled by the CMTS. The Cisco CMTS router specifies backoff window
values for both data and initial ranging and sends these values downstream as part of the Bandwidth
Allocation Map (MAP) MAC message. The values are power-of-two values. For example, a value of 4
indicates a window between 0 and 15; a value of 10 indicates a window between 0 and 1023.
The automatic setting is optimized for a maximum of 250 CMs per upstream port. Set manual values
for data backoff windows only when operating with more than 250 CMs per upstream port. (The
automatic setting is not supported on Cisco uBR-MC5X20S/U cable interface line cards, which should
use manually configured ranging backoff instead.)
Tip Use the show controllers cable upstream command to display the current Ranging Backoff settings.
Examples The following example shows how to set the range backoff to automatic for upstream port 2:
Router(config)# interface cable 4/0
Router(config-if)# cable upstream 2 range-backoff automatic
Router(config-if)#
Syntax Description interval value (Optional) Specifies the ranging poll interval in milliseconds. Valid values
are from 20000 to 30000. The default value is 20000.
t4-multiplier (Optional) Specifies T4 timeout multiplier value for the cable modems that
timeout_value are in the MTC mode. The valid range is from 1 to 10.
Usage Guidelines T4 multiplier is the T4 timeout multiplier value for cable modems that are in the MTC mode. The default
value is derived from the number of channels in the modem transmit channel set. You can change the
default T4 multiplier value using the cable upstream ranging-poll command in cable interface
configuration mode. For example, DOCSIS 2.0 defines T4 timeout for the modem at 30 seconds. If the
T4 multiplier value is equal to one, the cable modem will T4 time out in every 30 seconds. If you change
the T4 multiplier to four, then the new T4 timeout value will be 120 seconds (4 x 30 = 120).
In the MTC mode, you can increase the T4 timeout value in order to reduce the router overhead
associated with processing of ranging request (RNG-REQ) slots and ranging response (RNG-RSP)
messages. If an RNG-RSP message does not contain a T4 timeout multiplier value, then the cable
modem uses the default T4 timeout value.
Note We recommend that you do not modify the default ranging poll interval unless required. With the default
configuration, a DOCSIS 2.0 cable modem in non-MTC mode performs ranging on one upstream
channel every 20 seconds.
Examples The following example shows how to change the default ranging poll interval and the T4 timeout
multiplier value on a cable interface line card:
Router# configure terminal
Router(config)# interface cable 7/1/0
Router(config-if)# cable upstream ranging-poll interval 24000 t4-multiplier 4
Usage Guidelines If upstream utilization optimization is globally enabled, activated service flows are configured for
upstream utilization optimization. The command also turns on local upstream utilization optimization so
specific local upstreams can be configured to be rate-adapt enabled. Using the priority or rate option
allows you to restrict upstream utilization optimization to service flows that meet or exceed specified
levels for priority or rate.
Examples The following example enables upstream utilization optimization globally on all upstream flows.
Router(config)# cable upstream rate-adapt
cable upstream port rate-adapt [bcs slots | duration millisecs | fcms-off | priority value |
rate number]
no cable upstream port rate-adapt [bcs slots | duration millisecs | fcms-off | priority value |
rate number]
Syntax Description port Identifies the specific upstream flow to be optimized and configured.
bcs slots (Optional) Specifies the number of broadcast contention minislots (BCS).
MAPs that have gaps are filled with BCS. You can override the default of 10
with a larger or smaller number using the bcs option. The valid range
is 0–80. The default is 10 BCS.
duration millisecs (Optional) Specifies the length of time, in milliseconds, that a flow
rate-adapts. This keyword overrides the default duration. The default is 1.
The valid range is 0–2000.
fcms-off (Optional) Disables the forced broadcast contention minislot at the end of a
filled MAP.
priority value (Optional) Specifies the minimum priority required to enable rate-adapt on
a flow. This keyword overrides any globally configured rate-adapt priority.
The valid range is 0–7.
rate number (Optional) Specifies the minimum max-rate required to enable rate-adapt on
a flow. This keyword overrides any globally configured rate-adapt rate. The
valid range is 0–30000000.
Usage Guidelines If eligible, local upstream flows can utilize upstream utilization optimization.
Examples The following example enables and configures rate-adapt on upstream 0 with a priority of 6 and a rate
of 200.
Router(config-if)# cable upstream 0 rate-adapt priority 6 rate 200
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
token-bucket shaping (Optional) Enables rate limiting for the specified upstream cable
interface using the token-bucket policing algorithm. The shaping
option enables token-bucket shaping.
Usage Guidelines Upstream rate limiting allows upstream bandwidth requests from rate-exceeding CMs to be buffered
without incurring TCP-related timeouts and retransmits. This enables the Cisco CMTS to enforce the
peak upstream rate for each CM without degrading overall TCP performance for the subscriber CPE
devices. Upstream grant shaping is per cable modem (SID).
When the token-bucket algorithm is configured, the Cisco CMTS automatically drops packets in
violation of allowable upstream bandwidth.
Use of the default value (the upstream port’s rate limit) enforces strict DOCSIS-compliant rate limiting.
Cisco highly recommends to using the default setting of token-bucket with the shaping option.
Examples The following example shows how to configure the token bucket filter algorithm with traffic shaping on
upstream port 4:
Router(config-if)# cable upstream 4 rate-limit token-bucket
Syntax Description channel-down-detect Specifies the threshold (number of consecutive ranging misses) to determine
number if a channel is down. The valid values are from 8 to 64.
modem-offline-detect Specifies the threshold (number of consecutive ranging misses) to determine
number if a CM is offline. The valid values are from 4 to 16.
on-failure Allows you to specify what should be done if the channel is down and the
CM is offline.
disable-channel Allows the CMTS to mark the channel as unusable when a failure is detected.
extended-ranging Allows the CMTS to continue ranging when a failure is detected.
reset-modem Enforces the CM to go offline when a failure is detected.
Examples The following example shows how to configure upstream resiliency with different keywords on a cable
interface in slot 5, subslot 1, and port 0 on a Cisco uBR10012 router:
Router# configure terminal
Router(config)# interface cable 5/1/0
Router(config-if)# cable upstream resiliency channel-down-detect 30
Router(config-if)# cable upstream resiliency modem-offline-detect 16
Router(config-if)# cable upstream resiliency on-failure disable-channel
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first upstream
port on the cable interface line card.
ugs (Optional) Selects scheduling for UGS.
rtps (Optional) Selects scheduling for rtPS.
mode Enables the selection of packet-based Low Level Queueing (LLQ) or
TDM-based DOCSIS scheduling.
llq (Optional) Selects LLQ scheduling.
docsis (Optional) Selects DOCSIS scheduling.
Usage Guidelines Any combination of ugs, rtps, llq, and docsis is allowed.
Note the following restrictions:
• To ensure proper operation, Call Admission Control (CAC) must be enabled. When the Low Latency
Queueing (LLQ) option is enabled, it is possible for the upstream path to be filled with so many calls
that it becomes unusable, making voice quality unacceptable. CAC must be used to limit the number
of calls to ensure acceptable voice quality, as well as to ensure traffic other than voice traffic.
• Even if CAC is not enabled, the default (DOCSIS) scheduling mode blocks traffic after a certain
number of calls.
Examples The following example shows how to enable LLQ-type (packet-based) scheduling for UGS services on
upstream port 4 on a Cisco CMTS interface:
Router(config-if)# cable upstream 4 scheduling type ugs mode llq
The following example shows how to enable standard DOCSIS (TDM-based) scheduling for rtPS
services on upstream port 4 on a Cisco CMTS interface:
Router(config-if)# cable upstream 4 scheduling type rtps mode docsis
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
Usage Guidelines This command causes CMs to enable their pseudo-random scrambler circuitry to improve the robustness
of the upstream receiver on the line card.
The scrambler on the upstream radio frequency (RF) carrier enables CMs on the HFC network to use
built-in scrambler circuitry for upstream data transmissions. The scrambler circuitry improves reliability
of the upstream receiver on the cable interface line card. The upstream scrambler is activated by default
and should not be disabled under normal circumstances.
Caution Scrambler must be activated for normal operation. Deactivate only for prototype CMs that do not support
scrambler.
Examples The following example shows how to activate the upstream scrambler:
Router(config-if)# cable upstream 0 scrambler#
Command Description
cable upstream power-level Sets the input power level for the upstream RF carrier in decibels
per millivolt (dBmV).
cable upstream shutdown Disables the upstream port.
Physical Channel
Logical Channel
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
m Specifies the logical channel index of 0 or 1.
Usage Guidelines The cable upstream shutdown command shuts down a single upstream physical or logical port without
affecting any of the other upstream or downstream ports on the cable interface.
Note The cable upstream shutdown command exists at both physical and logical channel level with minor
variations in the command syntax.
When multiple logical channels are configured, the upstream related CLIs are categorized into two
groups: physical port level and logical channel level. Logical channel level commands use the format
of cable upstream n m shutdown, where n denotes the physical port number, and m denotes the logical
channel index number.
When multiple logical channels are configured, the cable upstream shutdown command at the physical
level shuts down the upstream physical port and all the logical channles configured under that physical
port. To shut down the entire interface, use the shutdown command in cable interface configuration
mode.
Examples The following example shows how to disable the upstream port for the physical channel:
Router(config-if)# cable upstream 0 shutdown
The following example shows how to disable the upstream port for the logical channel:
Router(config-if)# cable upstream 0 0 shutdown
Note This command can be used only on upstreams on the Cisco uBR-MC16S cable interface line cards.
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
interval-in-ms The valid range is 1000 to 25000 milliseconds, with a default of 15000
milliseconds.
Usage Guidelines The Cisco uBR-MC16S cable interface line cards contain digital signal processors (DSPs) that perform
hardware spectrum management. Use the cable upstream snr-polling command to determine how often
that hardware should examine an upstream’s signal to determine the current CNR value.
Examples The following example shows how to configure the sixth upstream on a Cisco uBR-MC16S cable
interface card so that the DSP samples the upstream signal every 10 seconds (10,000 milliseconds):
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 5 snr-polling 10000
Router(config-if)#
Command Description
show cable hop Displays the current hop period and threshold for an upstream, along with
other statistics.
show cable Displays the cable modulation profiles that have been created.
modulation-profile
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first upstream
port on the cable interface line card.
group-number Specifies the spectrum group for which you are specifying a parameter value or
specifies the number of the spectrum group you wish to remove from your router
configuration. Valid range is from 1 to 32, or from 1 to 40, depending on the
Cisco IOS software release.
Usage Guidelines This command assigns a spectrum group to a single upstream on the cable interface line card. To
configure the spectrum groups, use the set of cable spectrum-group commands in global configuration
mode.
Note You can also spectrum groups to all of the upstreams on the cable interface using the cable
spectrum-group (interface configuration) command.
Examples The following example shows how to assign spectrum group 12 to the first upstream on the cable
interface line card in slot 5/0:
Router(config)# interface cable 5/0
Router(config-if)# cable upstream 0 spectrum-group 12
Router(config-if)# exit
Router(config)#
Syntax Description n Specifies the upstream port. Valid values start with 0 for the first
upstream port on the cable interface line card.
spreading-interval Specifies the spreading interval for S-CDMA channels. Valid values
range from 1 to 32, with a default value of 16.
Command Default The spreading-interval setting cannot be applied if S-CDMA is not configured.
Usage Guidelines This command is applicable only for S-CDMA channels. You should configure S-CDMA to apply the
spreading-interval.
Examples The following example sets the spreading interval to 32 on the upstream port 0:
Router(config)# interface cable 7/0/4
Router(config-if)# cable upstream 0 spreading-interval 32
Router(config-if)#
Physical Channel
Logical Channel
snr-threshold1 SNR threshold for the primary modulation profile specified for the
upstream.
Valid values range from 5 to 35 dB, with a default value of 25 dB.
You can bypass the primary SNR threshold (snr-threshold1) by setting
it to 0.
snr-threshold2 SNR threshold for the secondary modulation profile specified for the
upstream.
Valid values range from 5 to 35 dB, with a default value of 15 dB. The
secondary threshold value must be lesser than the primary threshold.
Though, you can bypass the primary SNR threshold (snr-threshold1) by
setting it to 0, you must enter the second parameter (snr-threshold2).
hysteresis hysteresis-value Specifies the hysteresis value to be used in conjunction with the
dynamic modulation upgrade thresholds.
The threshold is specified in dB, with a valid range of 0 to 10 dB, and a
default value of 3 dB.
You can bypass the hysteresis threshold by setting the value to 0.
corr-fec fec-corrected Specifies the allowable number of correctable FEC errors for the
upstream.
The fec-corrected parameter is given as a percentage of total packets
received on the upstream during the polling period, with a valid range
of 1 to 30, and a default of 3.
You can bypass the corr-fec threshold by setting the value to 0.
uncorr-fec fec-uncorrected Specifies the allowable number of uncorrectable FEC errors for the
upstream.
The fec-uncorrected parameter is given as a percentage of total packets
received on the upstream during the polling period, with a valid range
of 1 to 30, and a default of 1.
You can bypass the uncorr-fec threshold by setting the value to 0.
Command Default The ranges and defaults for the correctable and uncorrectable FEC error thresholds were changed in
Cisco IOS Release 12.2(8)BC2.
Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA.
12.2(33)SCC This command was modified with the addition of snr-profiles
keyword option and support was added for Cisco uBR-MC5X20H
cable interface line card. Also, this command is used at both physical
and logical channel level with slight variations in the command syntax
for the uBR10012 router.
Usage Guidelines Separate CNR or SNR thresholds are assigned to the primary and secondary modulation profiles. Both
profiles, however, are assigned the same correctable and uncorrectable FEC values.
Note The uncorrectable FEC error count includes packets that have header checksum errors and “no unique
word detected” errors.
The hysteresis keyword of the cable upstream threshold command configures a hysteresis value to
prevent upstream channels from becoming unstable and continuously changing between modulation
profiles.
• The hysteresis value is used in dynamic modulation, frequency hopping, and dynamic channel-width
changes.
• The hysteresis value is used in conjunction with CNR or SNR thresholds to determine channel
configuration upgrade criteria for both advanced and basic spectrum management features.
From Cisco IOS Release 12.2(33)SCC onwards, you can configure two logical channels on a single
physical port for the uBR10012 router. When you configure logical channels, the upstream related
commands are categorized into two groups: physical port level and logical channel level.
The following restrictions and conditions applies to both physical and logical channel configurations:
• You can bypass both the primary and secondary CNR thresholds by setting the first parameter to 0.
This disallows the second parameter, enabling you to bypass both the CNR thresholds.
• If you provide the primary CNR threshold, then you must enter the secondary CNR threshold also.
• You can bypass the primary SNR threshold by setting it to 0. However, you must enter the second
parameter. This is required as each threshold is used independently in Three Step Dynamic
Upstream Modulation feature.
• You can bypass the hysteresis, corr-fec, and uncorr-fec thresholds by setting their values to 0.
• For normal plant use, we recommend that the uncorrectable FEC threshold remain at its default of
1 percent to avoid an unacceptable number of errors on the channel.
The following example shows upstream 5 configured with the SNR threshold for the primary modulation
profile set to 20 dB, the SNR threshold for the secondary modulation profile set to 10 dB, the correctable
FEC error rate set to 5 percent of total packets received on the upstream, and the uncorrectable FEC error
rate set to 1 percent of total packets received on the upstream:
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 5 threshold snr-profiles 20 10
Router(config-if)# cable upstream 5 threshold corr-fec 5
Router(config-if)# cable upstream 5 threshold uncorr-fec 1
Router(config-if)#
Command Description
cable upstream Configures an upstream for one modulation profile (static profile) or
modulation-profile two modulation profiles (dynamic upstream modulation).
show cable hop Displays the current hop period and threshold for an upstream, along
with other statistics.
show cable modulation-profile Displays the cable modulation profiles that have been created.
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
hysteresis-in-dB Specifies the hysteresis value to be used in conjunction with the
dynamic modulation upgrade thresholds.
The valid values are from 0 to 10 dB.
Usage Guidelines The cable upstream threshold hysteresis command can be used to configure a hysteresis value to
prevent upstream (US) channels from becoming unstable and continuously changing between
modulation profiles.
• The hysteresis value is used in dynamic modulation, frequency hopping, and dynamic channel-width
changes.
• The hysteresis value is used in conjunction with carrier-to-noise ratio (CNR) or signal-to-noise ratio
(SNR) thresholds to determine channel configuration upgrade criteria for both advanced and basic
spectrum management features.
Examples The following example configures a hysteresis value to be used in conjunction with the SNR and CNR
thresholds for dynamic modulation upgrade.
Router(config)# interface cable 3/0
Router(config-if)# cable upstream 0 threshold hysteresis 5
Router(config-if)#
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the
first upstream port on the cable interface line card.
continue sec Sets the minimum timing adjustment that sets continue ranging status
in seconds. The range for sec is 2 to 64 seconds. Default value is
2 seconds.
threshold sec Sets the timing adjustment threshold in seconds. Valid threshold value
is 1 to 32 seconds. Default is 1 second.
Usage Guidelines To verify whether or not upstream timing adjustment is configured and activated, enter the show
running-config command and look for the cable interface configuration information. If upstream timing
adjustment is enabled, either or both of the continue and threshold timing adjustment entries are
displayed in the show running-config output. If both the continue and threshold upstream timing
adjustments are disabled, no timing adjustment entry is displayed in the show running-config output.
If you are having trouble, make sure that the cable connections are not loose or disconnected; the cable
interface line card is firmly seated in its chassis slot; the captive installation screws are tight; and you
have entered the correct slot and port numbers.
Note The cable timing-adjust command is applicable only on Cisco IOS Release 12.0(12)SC and Cisco IOS
Release 12.1(3)T. It is deprecated and removed on Cisco IOS Release 12.1(3a)EC, 12.1(4)CX, and later
releases.
Examples The following example shows how to set the upstream time adjustment ranging value to 5 seconds:
CMTS01(config-if)# cable upstream 0 time-adjust continue 5
The following example shows how to set the threshold value to the default of 12 seconds:
CMTS01(config-if)# cable upstream 0 time-adjust threshold 12
Syntax Description n Specifies the upstream port number. Valid values start with 0 for the first
upstream port on the cable interface line card.
limit jitter Specifies the allowable jitter limit caused by unfragmentable slots, in
microseconds (0 to 4,294,967,295).
cac-enforce Rejects service flows requesting jitter less than the fragmentable slot jitter.
Command Default By default, the limit is 0 microseconds and the cac-enforce option is enabled.
Usage Guidelines This command controls how much jitter due to unfragmented slots is to be tolerated on each port. If the
specified value for the tolerated limit is less than the size of a maximum unfragmentable slot, the MAC
scheduler automatically blocks the slots in the scheduling table so that the unfragmentable slot can be
accommodated in the blocked space and avoid causing excessive jitter to CBR slots.
The cac-enforce option enforces the rule that service flows requesting run-time jitter less than
unfragmentable slot jitter should be rejected.
Examples The following example shows the jitter being set to 10 milliseconds (10,000 microseconds) for upstream
port 0 on cable interface 2/0:
Router# configure terminal
Router(config)# interface c2/0
Router(config-if)# cable upstream 0 unfrag-slot-jitter limit 10000
Router(config-if)#
cable util-interval
To set the load and utilization interval of upstream and downstream physical channels, use the
cable util-interval command in global configuration mode. To remove the utilization interval, use the
no form of this command.
Syntax Description interval Utilization interval for the upstream and downstream channels. The valid
range is from 1 to 86400 seconds.
Usage Guidelines The cable util-interval command configures the same value as the
docsIfCmtsChannelUtilizationInterval and ccwbRFChanUtilInterval objects.
The unit of interval is seconds and it is not recommended to set a smaller value as it may cause frequent
utilization calculation that will consume more resources on both, the PRE and cable line card.
A value between 60 to 300 seconds or greater is recommended.
Examples The following example shows how to set the utilization interval for the upstream and downstream
channels:
Router# configure terminal
Router(config)# cable util-interval 22
Router(config)#
cable vc-map
To map a cable modem to a particular permanent virtual connection (PVC) on an Asynchronous Transfer
Mode (ATM) interface, use the cable vc-map command in global configuration mode. To remove this
mapping, use the no form of this command.
Syntax Description mac-address Specifies the hardware (MAC) address for the cable modem whose traffic is to
be mapped.
atm-interface Specifies the outbound ATM interface to which this cable modem should be
mapped.
vpi/vci Specifies the virtual path identifier (VPI) and virtual channel identifier (VCI) on
the ATM interface to which this cable modem should be mapped.
cust-name (Optional) Identifies the customer for this PVC. The cust-name can be any
arbitrary alphanumeric string, up to 127 characters long.
customer cust-name (Optional) Deletes all PVCs belong to this customer. The cust-name can be any
arbitrary alphanumeric string, up to 127 characters long.
Usage Guidelines This command maps a cable modem, on the basis of its hardware (MAC) address, to a particular PVC
on an ATM interface.
Note To use this command, you must first enable the use of Layer 2 tunnels, using the cable l2-vpn-service
atm-vc command. Then use the cable vc-map command to enable the mapping of individual cable
modems to specific PVCs.
Examples The following example shows how to enable the use of Layer 2 tunnels and then map specific CMs to
specific PVCS:
Router# config terminal
Router(config)# cable l2-vpn-service atm-vc
Router(config)# cable vc-map 0007.0e03.69f9 ATM2/0 1/1
Router(config)# cable vc-map 0010.7bed.9c95 ATM2/0 1/2
Router(config)# exit
Router#
The following example shows the same configuration as above, but with the addition of a customer name
that identifies the customer that is using each particular PVC:
Router# config terminal
Router(config)# cable l2-vpn-service atm-vc
Router(config)# cable vc-map 0007.0e03.69f9 ATM2/0 1/1 ENTERPRISE-CO1
Router(config)# cable vc-map 0010.7bed.9c95 ATM2/0 1/2 ENTERPRISE-CO2
Router(config)# exit
Router#
Usage Guidelines Use this command to enable wideband auto-reset mode on the CMTS. If wideband auto-reset mode is
enabled, wideband cable modems registered on a cable interface as traditional DOCSIS modems
(DOCSIS 1.x/2.0 modems) are auto-reset when the cable interface becomes wideband-capable. When a
wideband cable modem auto-resets, it deregisters on the CMTS as a traditional DOCSIS cable modem
and immediately attempts to re-register as a wideband cable modem.
A cable interface is considered wideband-capable when at least one fully configured and operational
wideband channel has been associated with the interface’s traditional DOCSIS (narrowband) channel.
For a fully configured wideband CMTS, wideband cable modems may register as traditional DOCSIS
modems for a variety of reasons, such as cable interface line card boot order or line card online insertion
and removal (OIR). Rather than defer wideband cable modem registration, wideband cable modems are
permitted to register as traditional DOCSIS modems.
If a wideband-capable modem registers as a traditional DOCSIS modem, it registers on a primary
downstream channel that has been assigned with the downstream cable command to the modem’s fiber
node if the fiber node is configured. If the modem’s fiber node is not configured, the wideband-capable
modem can register on any downstream channel that is visible to it (as a traditional cable modem does).
Note In Cisco IOS Release12.3(21)BC, the primary downstream channel is a traditional DOCSIS downstream
channel for the fiber node. Beginning in Cisco IOS Release 12.3(23)BC, either an RF channel from the
SPA or a Cisco uBR10-MC5X20 downstream channel serves as a primary channel in a fiber node.
Beginning in Cisco IOS Release12.3(23)BC if the primary downstream channel for this fiber node is
assigned from a SPA downstream, then the downstream cable command is not required.
When and if a cable interface becomes wideband capable, wideband cable modems that have registered
as traditional DOCSIS modems are reset for CMTS routers with wideband auto-reset mode enabled.
These modems are only reset when the interface first becomes wideband-capable and are not reset again
if they subsequently fail to register as wideband cable modems.
Examples The following example shows how to enable wideband auto-reset mode:
Router# configure terminal
Router(config)# cable wideband auto-reset
New Commands
Modified Commands
Replaced Commands
card
To preprovision a router slot for a particular interface card so that you can configure the interface without
that card being physically present in the slot, use the card command in global configuration mode. To
remove the preprovisioning for a card so that the physical slot reports being empty, use the no form of
this command.
no card slot/subslot
Syntax Description slot/subslot Identifies the chassis slot and subslot for the card. The following are
the valid values:
• slot—1 to 8
• subslot—0 or 1
slot/subslot/bay (Cisco uBR100012 router) Identifies the chassis slot and subslot for
the Cisco Wideband SIP, and the bay number in the SIP where the
Cisco Wideband SPA is located. The following are the valid values:
• slot—1 to 3
• subslot—0 or 1 (0 is always specified)
• bay—0 (upper bay) or 1 (lower bay)
card-type Specifies the type of card for which to preprovision the slot. See
Table 0-21 for a list of the supported cards, which varies by platform.
lchoc12-1 Preprovisions a line card slot for a 1-Port Channelized OC-12/STM-4
line card.
lgigethernet-l Preprovisions a line card slot for a 1-Port Gigabit Ethernet line card.
1gigethernet-hh-1 Preprovisions a line card slot for a 1-Port Gigabit Ethernet Half-Height
line card.
loc12atm-1 Preprovisions a line card slot for a 1-Port OC-12 ATM line card.
loc12pos-1 Preprovisions a line card slot for a 1-Port OC-12 Packet over SONET
line card.
1oc48dpt-pos-1 Preprovisions a line card slot for a 1-Port OC-48/STM-16 Packet over
SONET line card.
24che1t1-1 Preprovisions a line card slot for a 24-Port Channelized E1/T1 line
card.
4chstm-1 Preprovisions a line card slot for a 4-Port Channelized OC-3/STM-1
line card.
4cht3-hh-1 Preprovisions a line card slot for a 4-port Channelized Half-Height line
card.
4oc3atm-1 Preprovisions a line card slot for a 4-Port OC-3/STM-1 ATM line card
with intermediate-reach optics.
4oc3atm_lr-1 Preprovisions a line card slot for a 4-Port OC-3/STM-1 ATM line card
with long-reach optics.
4jacket-1 Preprovisions a line card slot in the Cisco 10000 series router to accept
a Cisco 10000 SIP-600.
6cht3-1 Preprovisions a line card slot for a 6-Port Channelized T3 line card.
6oc3pos-1 Preprovisions a line card slot for a 6-Port OC-3/STM-1 Packet over
SONET line card.
8e3ds3-1 Preprovisions a line card slot for an 8-Port Unchannelized E3/T3 line
card.
8e3ds3atm-1 Preprovisions a line card slot for an 8-Port E3/DS3 ATM line card.
8fastethernet-1 Preprovisions a line card slot for an 8-Port Fast Ethernet Half-Height
line card.
mode {e1 | t1} Indicates the mode of operation of the 24-Port Channelized E1/T1 line
card.
spa-type Specifies the SPA type to preprovision a SPA interface.
Command Default An empty card slot is not preprovisioned and cannot be configured or displayed.
The default mode of operation for the 24-Port Channelized E1/T1 line card is E1.
Release Modification
12.2(4)BC1 Support was added for the Cisco uBR10-SRP-OC12SML DPT WAN uplink
line card.
12.2(8)BC1 Support was added for the Cisco LCP2 line card processor, and all of its
combinations with the supported cable interface line cards.
12.2(11)BC3 Support was added for the Cisco uBR10012 OC-48 DPT/POS Interface
Module uplink line card and Cisco uBR-MC5X20S cable interface line card.
12.2(15)BX This command was integrated into Cisco IOS Release 12.2(15)BX.
12.2(15)CX1 Support was added for the Cisco uBR-MC16U/X and Cisco uBR-MC28U/X
cable interface line cards.
12.2(15)BC2 Support was added for the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X,
and Cisco uBR-MC5X20U cable interface line cards.
12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB. This
command was modified to support the 4-port Channelized Half-Height line
card and the 4-Port OC-3/STM-1 ATM line card with long-reach optics by
adding the 4cht3-hh-1 and the 4oc3atm_lr-1 keywords.
12.3(7)XI1 This command was integrated into Cisco IOS Release 12.3(7)XI1.
12.3(21)BC Support was added for the Cisco Wideband SIP and Wideband SPA.
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA. Support
for the Cisco uBR7225VXR router was added.
12.2(33)SB This command was enhanced to provide the 4jacket-1 keyword and the
spa-type option, which enable you to preprovision a line card slot to accept
a Cisco 10000 SIP-600 and a SPA interface, respectively. This enhancement
was implemented on the Cisco 10000 series router for the PRE3 and PRE4.
12.2(33)SCB This command was integrated into Cisco IOS Release 12.2(33)SCB. Support
for the Cisco SIP-600 was added. This command was modified to change the
addressing format for:
• SIPs—From slot/subslot to slot
• SPAs—From slot/subslot/bay to slot/bay
Usage Guidelines This command is supported on the Cisco uBR10012 Universal Broadband Router and the Cisco 10000
series routers. For platform-specific information about using this command, see the other
platform-specific sections of this topic.
Use this command to preprovision a slot in the router to accept a particular line card, so that you can
configure the interface without the card being physically present in the chassis. This command allows
system administrators to plan for future configurations, without having to wait for the physical hardware
to first arrive. When the line card does arrive, the installer can bring the card online by inserting the card
into the chassis and connecting the necessary cables, without having to do any further configuration
using the command-line interface.
The type of card must be appropriate for the slot being specified. The list of supported card types
depends on the Cisco IOS software release in use and your platform. For the latest information about
supported hardware for your platform, see the release notes that correspond to your Cisco IOS software
release and platform.
Table 0-21 lists the types of cards that are supported as card-types for the card command:
• Slots 1/1 and 2/1 are reserved for TCC+ utility cards. A utility card and a SPA can co-exist on a
Cisco uBR10012 router with an index of 1/1.
• Slots 1/0 through 4/0 are reserved for network uplink line cards.
• Slots 1 and 3 can be used for SIPs. Each SIP occupies two physical slots in a Cisco uBR10012 router
(slot pair 1/2 or slot pair 3/4). Slot 1 is recommended for the Cisco Wideband SIP.
• Slot 5/0 through 8/1 are reserved for cable interface line cards.
Tip When a card has been preprovisioned and is not physically present in the chassis, the show interface
command for that slot displays the message “Hardware is not present.” Some show commands might also
list the preprovisioned card in their displays. In addition, using the card command does not change the
output of the ENTITY-MIB, which shows only the equipment that is physically installed in the router.
When a line card is inserted in the Cisco uBR10012 chassis, the router performs the following actions,
depending on whether the card slot is preprovisioned for the card:
• If the inserted line card matches the type of line card preprovisioned for the slot, the system applies
the preprovisioned configuration to the line card.
• If the line card slot was not preprovisioned, the system applies a basic configuration to the line card
and adds that configuration to the running configuration file.
• If the line card slot was preprovisioned for one type of line card, but another type of line card has
been inserted, the system replaces the preprovisioned configuration (in the running configuration
file) with a basic configuration for the line card that was actually inserted. The startup configuration
file is not changed.
Tip Use the show running-config | include card command to display which slots, if any, are preprovisioned
for a particular card type.
The no version of the command removes the preprovisioning information from the given card slot. This
also removes all configuration information for that card slot, as well as any information in the SNMP
MIB database about the card and its card slot.
The following example shows how to preprovision a Cisco Wideband SIP in Cisco IOS Release
12.2(33)SCB:
Router# configure terminal
Router(config)# card 1 2jacket-1
The following example shows how to preprovision a Cisco Wideband SPA on a Cisco Wideband SIP in
Cisco IOS Release 12.2(33)SCB:
Router# configure terminal
Router(config)# card 1/0 24rfchannel-spa-1
The following example shows how to preprovision a Cisco SIP-600 in Cisco IOS Release 12.2(33) SCB:
Router# configure terminal
Router(config)# card 3 4jacket-1
The following example shows how to preprovision a Cisco Wideband SPA on a Cisco SIP-600 in
Cisco IOS Release 12.2(33) SCB:
Router# configure terminal
Router(config)# card 3/0 24rfchannel-spa-1
The following example shows how to change the provisioning for line card slot 5 from the 1-Port Gigabit
Ethernet Half-Height line card to the 4-Port OC-3/STM-1 ATM line card.
Router(config)# hw-module subslot 5/0 shut
Aug 22 21:52:19.619 UTC: %IPCOIR-3-TIMEOUT: Timeout waiting for a response from slot 5/0.
Aug 22 21:52:19.619 UTC: %IPCOIR-2-CARD_UP_DOWN: Card in slot 5/0 is down. Notifying
1gigethernet-hh-1 driver.
Aug 22 21:52:21.627 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet5/0/0, changed state to
down
Aug 22 21:52:22.627 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet5/0/0, changed state to down
Router(config)# no card 5/0 1gigethernet-hh-1
Aug 22 21:53:20.008 UTC: %C10K-3-DEACTIVATED: card in slot [5/0] disabled.
Router(config)# card 5/0 4oc3atm-1
[ Remove the 1-Port Gigabit Ethernet Half-Height line card and
insert the 4-Port OC-3/STM-1 ATM line card ]
channel-group
To add an interface (Gigabit Ethernet or Fast Ethernet) to an EtherChannel Group, and to associate that
interface with an EtherChannel link, use the channel-group command in interface configuration mode.
To remove an EtherChannel interface from the EtherChannel group, use the no form of this command.
channel-group n
no channel-group n
Syntax Description n The identifying number for the EtherChannel group with which to associate this interface.
An EtherChannel group can be identified in the range of 1 to 64, and each group can have
up to four interfaces, only one of which is the master.
Usage Guidelines The no form of this command also removes the associated EtherChannel ports within the EtherChannel
group. For additional information, refer to the EtherChannel on the Cisco CMTS Routers feature
document on Cisco.com.
Examples The following example creates an EtherChannel link with a channel group identifier of 1 on the specified
port. If this is the first port assigned to EtherChannel group 1, it becomes the master in that EtherChannel
group.
Router(config-if)# channel-group etherchannel 1
channel-id upstreamchan-id
no channel-id
Syntax Description upstreamchan-id Specifies the upstream channel ID. Valid range is 0 to 255, depending on the
number of actual upstream ports on the cable interface being used.
Defaults If no upstream channel ID is specified, the CM uses the upstream channel from the Upstream Channel
Description (UCD) messages it receives on the downstream channel.
Usage Guidelines This command sets the Upstream Channel ID Configuration Setting field in the DOCSIS configuration
file. Typically, the CM uses the upstream channel ID that is specified by the CMTS during the
registration process, but this command overrides that setting and forces the CM to use the upstream
channel specified in the DOCSIS configuration file. If that upstream does not exist, or if the upstream
cannot be obtained for some reason, the CM cannot come online.
Note If you are using a telco-return CM, the upstream channel must be 0.
Examples The following example shows how to set the upstream channel ID for the configuration file to 3. If the
CM cannot obtain this upstream channel, it does not come online.
Router(config)# cable config-file channeloverride.cm
Router(config-file)# channel-id 3
Router(config-file)# exit
Usage Guidelines The counters are also set to zero when a given resource is reconfigured. Counters can be displayed using
the show cable admission-control command.
For additional information, refer to the Admission Control for the Cisco CMTS feature documents on
Cisco.com.
Examples The following example resets configured admission control counters to zero, whether configured in
global or interface configuration mode:
Router# clear cable admission control counters
Syntax Descriptionc bundle number Resets the ARP filter statistics for the specified virtual bundle interface,
where number is a value from 1 to 255.
cable slot/port (Cisco uBR7100 and Cisco uBR7200 Series Routers) Specifies removal
of CMs on the specified cable interface and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Cisco uBR10012 Router) Specifies removal of CMs on the specified
cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
Usage Guidelines Use the clear cable arp-filter command to clear the ARP filter statistics that are displayed using the
show cable arp-filter command.
Examples This example shows cable ARP filter statistics for virtual bundle interface number 10, followed by a
clearing of the ARP filter statistics on that bundle and the resulting display of cleared statistics.
Usage Guidelines DSG operation is disabled using the no cable dsg command, but this does not clear out the DSG-related
counter (“mapping entry is used”), so that you can retain its value in case you intend to restart DSG
operations again. If, however, you want to reset those counters to zero, use the clear cable dsg command.
Note This command resets the “mapping entry is used” counters for all DSG tunnels and interfaces on the
router.
Examples The following example shows how to clear the DSG counters for all cable interfaces on the router, and
shows an example of the show cable dsg command showing the counters after they have been cleared.
Router# show cable dsg stats
Syntax Description mac-addr Specifies the 48-bit MAC address (hardware address) of an individual
CM to be cleared from the flap-list table.
all Removes all CMs from the flap-list table.
save-counters (Optional) Preserves the flap-list counters that are displayed by the
show cable flap-list command and by using SNMP requests to access
the CISCO-CABLE-SPECTRUM-MIB MIB.
Usage Guidelines Cable modems are removed from the flap-list table after the number of days (between 1 and 60) specified
by the cable flap-list aging global configuration command. Use the clear cable flap-list command to
remove individual CMs from the flap-list while retaining flapping activity for other CMs, or to clear the
entire flap-list table.
Examples The following example shows how to remove all the CMs from the flap-list table:
Router# clear cable flap-list all
Syntax Description cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers)
Specifies removal of CMs on the specified cable interface and
downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies removal of CMs on
the specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
upstream uport (Optional) Clears the hop counters on a specific upstream port on a
specific cable interface. The valid values for uport start with 0 for the
first upstream port on the cable interface line card.
Usage Guidelines The clear cable hop command clears the correctable and uncorrectable forward error corrections (FEC)
counters that are displayed by the show cable hop command. You can clear the counters for all interfaces
on the Cisco CMTS, for one specific interface (one downstream and its associated upstreams), or for a
specific upstream on a cable interface.
Examples The following example shows how to clear the frequency hop counters on all cable interfaces on the
Cisco CMTS, along with sample output from the show cable hop command that shows the counters
being cleared:
Router# show cable hop
Upstream Port Poll Missed Min Missed Hop Hop Corr Uncorr
Port Status Rate Poll Poll Poll Thres Period FEC FEC
(ms) Count Sample Pcnt Pcnt (sec) Errors Errors
Cable3/0/U0 15.008 Mhz 1000 * * *set to fixed frequency * * * 2238 133
Cable3/0/U1 admindown 1000 * * * frequency not set * * * 0 0
Cable3/0/U2 admindown 1000 * * * frequency not set * * * 0 0
Cable3/0/U3 admindown 1000 * * * frequency not set * * * 0 0
Upstream Port Poll Missed Min Missed Hop Hop Corr Uncorr
Port Status Rate Poll Poll Poll Thres Period FEC FEC
(ms) Count Sample Pcnt Pcnt (sec) Errors Errors
Cable3/0/U0 15.008 Mhz 1000 * * *set to fixed frequency * * * 0 0
Cable3/0/U1 admindown 1000 * * * frequency not set * * * 0 0
Cable3/0/U2 admindown 1000 * * * frequency not set * * * 0 0
Cable3/0/U3 admindown 1000 * * * frequency not set * * * 0 0
Router#
The following example shows how to clear the frequency hop counters on a specific cable interface on
the Cisco CMTS:
Router# clear cable hop c5/0
Router#
The following example shows how to clear the frequency hop counters on a specific upstream on the
Cisco CMTS:
Router# clear cable hop c5/1/0 upstream 2
Router#
Syntax Description ip-address IPv4 or IPv6 address for the device to be cleared.
mac-address MAC address for the device to be cleared.
name fqdn Specifies the fully qualified domain name (FQDN) of the cable device
to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to
update the cable DNS cache on the CMTS router.
Usage Guidelines This command removes a host’s IP, MAC address, or domain name from the router’s internal address
tables. This might be necessary to allow a new host to come online from the previous host’s CM.
Note If the cleared host continues communicating through the CM, the Cisco CMTS adds the host back to its
internal address tables, and the show interface cable interface modem command shows it as having a
“static” address. To block the host from any further access, use the cable source-verify dhcp command,
so that the host cannot access the network unless it obtains an IP address from an authorized DHCP
server.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Examples The following example shows how to remove a host’s MAC address from the internal address tables on
the Cisco CMTS router:
Router# clear cable host 0050.7366.17ab
The following example shows how to remove a host’s domain name from the internal address tables on
the Cisco CMTS router:
Router# clear cable host cisco
Usage Guidelines You must enable the Cable IPC Statistics Collection tool using the cable ipc-stats command before
using the clear cable ipc-stats command.
Examples The following example shows how to clear the active database using the clear cable ipc-stats command
on a Cisco CMTS router:
Router# clear cable ipc-stats
Examples The following example shows how to clear all of the counters that track load-balancing operations,
resetting them all to zero:
Router# clear cable load-balance counters
The following example shows how to clear the state machine that is used for load-balancing operations.
Router# clear cable load-balance state
Command Description
cable load-balance group policy ugs Configures how the Cisco CMTS should load
balance cable modems with active unsolicited
grant service (UGS) service flows.
cable load-balance group threshold Configures the threshold values that a
load-balance group should use for
load-balancing operations.
cable upstream load-balance group Assigns an upstream to a load-balance group.
show cable load-balance Displays real-time statistical and operational
information for load-balancing operations.
Usage Guidelines The cable logging badipsource command creates a circular buffer that contains the BADIPSOURCE
error messages that the Cisco CMTS generates when it discovers a CM or CPE device using an
unauthorized IP address. When the buffer becomes full, the oldest messages are deleted to make room
for newer messages.
When you have viewed all of the error messages in the current buffer, use the clear cable logging
command to clear out the buffer to make room for newer messages.
Examples The following example shows how to clear the log buffer that contains the bad IP source address error
messages:
Router# show cable logging summary
Cable logging: BADIPSOURCE Enabled
Total buffer size (bytes): 1000000
Used buffer size (bytes) : 36968
Logged messages : 231
Router# clear cable logging badipsource
Router# show cable logging summary
Cable logging: BADIPSOURCE Enabled
Total buffer size (bytes): 1000000
Used buffer size (bytes) : 0
Logged messages : 0
Router#
Related Commands cable logging badipsource Logs error messages about bad IP source addresses on the cable
interfaces.
cable source-verify Enables verification of IP addresses for CMs and CPE devices on the
upstream.
show cable logging Displays the log of error messages about bad IP source addresses on
the cable interfaces.
clear cable modem {mac-addr | ip-addr | cable slot/port {all | oui string | reject} } attribute-masks
clear cable modem {mac-addr | ip-addr | cable slot/subslot/port {all | oui string | reject} }
attribute-masks
Syntax Description mac-addr Specifies the MAC address for the CM.
ip-addr Specifies the IP address for the CM.
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers) Specifies
removal of CMs on the specified cable interface and downstream port,
where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies removal of CMs on the
specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
all Resets the flapping counters for all CMs.
oui string Resets the flapping counters for all CMs that match the specified
Organization Unique Identifier (OUI). The string parameter can be either the
three-byte hexadecimal string (such as 00.00.0C).
reject Resets the flapping counters for all CMs that are currently in one of the reject
states.
attribute-masks Specifies the attribute mask bitmap in hexadecimal format.
Example: 0-FFFFFFFF
Usage Guidelines This command clears the cable modem attribute masks.
Examples The following example shows how to clear cable modem attribute masks for CMs:
Router# clear cable modem all attribute-masks
Router# clear cable modem oui SA attribute-masks
Router# clear cable modem c5/0/0 offline attribute-masks
clear cable modem [ip address | mac address | cable slot/port] cm-status
clear cable modem [ip address | mac address | cable slot/subslot/port] cm-status
Syntax Description ip-address (Optional) IP address of a CM to be displayed. If you specify the IP address
for a CPE device behind a CM, information for that CM is displayed.
mac-address (Optional) MAC address of a CM to be displayed. If you specify the MAC
address for a CPE device behind a CM, information for that CM is displayed.
cable slot/subslot/port (Optional) Cable interface on the Cisco uBR10012 router. The following are
the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port on the Cisco uBR7225VXR and Cisco uBR7246VXR
routers, where:
• slot—Slot where the line card resides.
Cisco uBR7246VXR router—The valid range is from 3 to 6
Cisco uBR7225VXR router—The valid range is from 1 to 2
• port—Specifies the downstream port number.
cm-status Resets the CM status events to zero on the specified cable interface.
To reset the cable modem (CM) flap-list counters to zero, use the clear cable modem counters
command in privileged EXEC mode.
clear cable modem {mac-addr | ip-addr | [cable {slot/port | slot/subslot/port]{all | oui string |
reject}} counters
Syntax Description mac-addr Specifies the 48-bit hardware address (MAC address) of an individual
CM.
ip-addr Specifies the IP address of an individual CM.
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers)
Specifies removal of CMs on the specified cable interface and
downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies removal of CMs on the
specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
all Resets the flapping counters for all CMs.
oui string Resets the flapping counters for all CMs that match the specified
Organization Unique Identifier (OUI). The string parameter can be
either the three-byte hexadecimal string (such as 00.00.0C) or a vendor
name that has been defined using the cable modem vendor command.
reject Resets the flapping counters for all CMs that are currently in one of the
reject states. (See the show cable modem command for a description of
these states.)
Examples The following example shows how to clear the counters for the CM at IP address 172.16.23.45:
Router# clear cable modem 172.16.23.45 counters
The following example shows how to clear the counters for all CMs that have an OUI that has been
defined as having the vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco counters
The following example shows how to clear the counters for all CMs that are currently in one of the reject
states:
Router# clear cable modem reject counters
Note If running Cisco IOS Release 12.2(15)BC1 or later, use the clear cable modem flap-counters command
to clear the CM flap-list counters.
Syntax Description ip-addr Specifies removal of an individual CM by its IPv4 or IPv6 address.
mac-addr Specifies removal of an individual CM by its 48-bit hardware address
(MAC address).
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers)
Specifies removal of CMs on the specified cable interface and
downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies removal of CMs on the
specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
all Specifies removal of all CMs or all CMs associated with a specified
cable interface.
non-bonding-capable Specifies removal of all narrowband CMs that are not capable of
downstream channel bonding or all such CMs associated with a
specified interface.
legacy-ranging (Optional) Specifies removal of narrowband CMs that are accessed with
legacy initial ranging or all such CMs associated with a specified
interface.
offline Specifies removal of all offline CMs or all such CMs associated with a
specified interface.
oui string Specifies removal of all CMs that match the specified Organization
Unique Identifier (OUI) or all such CMs associated with a specified
interface. The string parameter can be either the three-byte hexadecimal
string (such as 00.00.0C) or a vendor name that has been defined using
the cable modem vendor command.
reject Specifies removal of all CMs that are currently in one of the reject states
or all such CMs associated with a specified interface. (See the show
cable modem command for a description of these states.)
wideband Specifies removal of all wideband CMs or or all such CMs associated
with a specified interface.
registered-traditional-docs (Optional) Specifies removal of all wideband CMs that are registered as
is traditional DOCSIS CMs or all such CMs associated with a specified
interface.
Usage Guidelines This command removes one or more CMs from the CMTS router memory, which causes the CMTS
router to stop all DOCSIS station maintenance messages for the specified CMs until they time out and
reattempt initial ranging.
Caution The clear cable modem all delete command should normally be used only on a test or lab network. If
used on a large network, it could impact service for a significant period of time, as it would force all
CMs to simultaneously reset and reregister with the Cisco CMTS. In addition, if HCCP N+1 redundancy
has also been configured, using the clear cable modem delete command can trigger a switchover to one
or more Protect interfaces, unless no keepalive has also been configured on the cable interfaces.
Examples The following example shows how to delete the CM at IP address 172.23.45.67:
Router# clear cable modem 172.23.45.67 delete
The following example shows how to delete all CMs that have a OUI that has been defined as having the
vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco delete
The following example shows how to delete all CMs that are currently in one of the reject states:
Router# clear cable modem reject delete
clear cable modem [cable {slot/port | slot/subslot/port}] {all | offline | oui string | reject}
flap-counters
Syntax Description ip-addr Resets the flap-list counters for an individual CM by its IPv4 or IPv6
address.
mac-addr Resets the flap-list counters for an individual CM by its 48-bit hardware
address (MAC address).
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers) Resets
the flap-list counters for all CMs on the specified cable interface and
downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Resets the flap-list counters for
all CMs on the specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
all Resets the flap-list counters for all CMs or all CMs associated with a
specified cable interface.
offline Resets the flap-list counters for all offline CMs or for all such CMs
associated with a specified interface.
oui string Resets the flap-list counters for all CMs that match the specified
Organization Unique Identifier (OUI) or for all such CMs associated
with a specified interface. The string parameter can be either the three
byte hexadecimal string (such as 00.00.0C) or a vendor name that has
been defined using the cable modem vendor command.
reject Resets the flap-list counters for all CMs that are currently in one of the
reject states or for all such CMs associated with a specified interface.
(See the show cable modem command for a description of these states.)
Usage Guidelines Use the clear cable modem flap-counters command to reset the flap-list counters associated with the
show cable flap-list command.
This command only resets flap-list counters. To reset other cable interface counters and those counters
associated with the show cable modem counters command, use the clear counters command.
Examples The following example shows how to reset the flap-list counters for the CM at IP address 172.16.23.45:
Router# clear cable modem 172.16.23.45 flap-counters
The following example shows how to reset the flap-list counters for all CMs that have a OUI that has
been defined as having the vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco flap-counters
The following example shows how to reset the flap-list counters for all CMs that are currently in one of
the reject states:
Router# clear cable modem reject flap-counters
clear cable modem [cable {slot/port | slot/subslot/port] {all | oui string} lock
Syntax Description ip-addr Resets the lock for an individual CM by its IPv4 or IPv6 address.
mac-addr Resets the lock for an individual CM by its 48-bit hardware address
(MAC address).
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers) Resets
the lock for all CMs on the specified cable interface and downstream
port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Resets the lock for all CMs on the
specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
all Resets the lock for all CMs or all CMs associated with a specified cable
interface.
oui string Resets the lock for all CMs that match the specified Organization
Unique Identifier (OUI) or for all such CMs associated with a specified
interface. The string parameter can be either the three-byte hexadecimal
string (such as 00.00.0C) or a vendor name that has been defined using
the cable modem vendor command.
Usage Guidelines When you have configured the cable dynamic-secret lock command on a cable interface, the CMTS
“locks” CMs that use a DOCSIS configuration file that fails the CMTS verification check. These CMs
are allowed to come online, but with a restrictive QoS configuration that limits their service flows to
10 kbps.
Locked CMs are not allowed to reregister with a valid DOCSIS configuration file until they have been
offline, without attempting to reregister, for at least 24 hours. You can manually clear the lock on a CM
by using the clear cable modem lock command in privileged EXEC mode.
The clear cable modem lock command also automatically resets the CMs, so that they will reregister
with the CMTS. If the CMs then reregister with a valid DOCSIS configuration file, the CMTS allows the
CMs to come online with the requested QoS profiles. If the CMs violate the DOCSIS specifications
again, they will be locked again.
Note If a CM is not manually unlocked, it remains locked until it stays offline, without attempting to
reregister, for 24 hours. It can also be unlocked by using the clear cable modem delete command to
manually remove the CM from all of the CMTS internal databases.
Examples The following example shows how to reset the lock for the CM with the MAC address of
0000.0C01.0203:
Router# clear cable modem 0000.0C01.0203 lock
The following example shows how to reset the lock for the CM at IP address 172.16.23.45:
Router# clear cable modem 172.16.23.45 lock
The following example shows how to reset the locks for all CMs that have an OUI that has been defined
as having the vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco lock
Command Description
clear cable modem name Removes or resets CMs by domain name.
clear cable modem reset Removes one or more CMs from the Station Maintenance List
and resets them.
Syntax Description fqdn Specifies the fully qualified domain name (FQDN) of the cable device
to be displayed. This option is only available if the show cable modem
domain-name command has been run for the first time to update the
cable Domain Name System (DNS) cache on the CMTS router.
delete Removes the CM with the specified domain name from the Station
Maintenance List.
reset Removes the CM with the specified domain name from the Station
Maintenance List and resets it.
Usage Guidelines In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Examples The following example shows how to delete a CM with the domain name “example”:
Router# clear cable modem name example delete
Command Description
clear cable modem reset Removes one or more CMs from the Station Maintenance List
and resets them.
show cable modem Displays information for the registered and unregistered CMs.
Command Description
clear cable modem Removes or resets CMs by domain name.
name
clear cable modem Removes one or more CMs from the Station Maintenance List and resets
reset them.
Syntax Description ip-addr Specifies removal of an individual CM by its IPv4 or IPv6 address.
mac-addr Specifies removal of an individual CM by its 48-bit hardware address
(MAC address).
cable slot/port (Optional—Cisco uBR7100 and Cisco uBR7200 Series Routers)
Specifies removal of all CMs on the specified cable interface and
downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies removal of all CMs on
the specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface
line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
all Specifies removal of all CMs or all CMs associated with a specified
cable interface.
non-bonding-capable Specifies removal of all narrowband CMs that are not capable of
downstream channel bonding or all such CMs associated with a
specified interface.
legacy-ranging (Optional) Specifies removal of narrowband CMs that are accessed with
legacy initial ranging or all such CMs associated with a specified
interface.
oui string Specifies removal of all CMs that match the specified Organization
Unique Identifier (OUI) or all such CMs associated with a specified
interface. The string parameter can be either the three-byte hexadecimal
string (such as 00.00.0C) or a vendor name that has been defined using
the cable modem vendor command.
reject Specifies removal of all CMs that are currently in one of the reject states
or all such CMs associated with a specified interface. (See the show
cable modem command for a description of these states.)
wideband Specifies removal of all wideband CMs or all such CMs associated with
a specified interface.
registered-traditional-docs (Optional) Specifies removal of all wideband CMs that are registered as
is traditional DOCSIS CMs or all such CMs associated with a specified
interface.
Usage Guidelines This command instructs the Cisco CMTS to stop sending DOCSIS station maintenance messages to one
or more CMs, which effectively terminates the link to those CMs until those CMs time out and reattempt
initial ranging. A CM responds to this by resetting itself. Depending on when the CM received the last
station maintenance message, it can take up to 30 seconds before the CM detects the missing station
maintenance messages and resets itself.
If the clear cable modem {ip-address | mac-address} reset form of the command is used to reset an
individual modem, the CMTS router sends a ranging abort message to the specified modem in order to
command the modem to reset itself and begin initial ranging more quickly without having to wait for up
to 30 seconds to realize it is no longer receiving station maintenance keep-alive opportunities. This
behavior is only seen when using the clear cable modem reset command for a specific CM.
Tip You can also specify the MAC address or IP address for a CPE device or host, and the Cisco CMTS resets
the CM that is associated with that CPE device in its internal database.
In some circumstances, the customer premises equipment (CPE) device behind a CM stops receiving
traffic after the CM is reset. This is because the CMTS still has the CPE device listed in its address tables,
but the CM does not after being reset, so the traffic passes through the CMTS but is dropped by the CM.
To resolve this situation, the CPE device should simply send some type of traffic to the CM, such as a
ping packet. (You can also resolve this situation by using the clear arp-cache command on the
Cisco CMTS router to clear the router’s address table, but this is not recommended because it
temporarily interrupts all traffic on the router.)
Caution The clear cable modem all reset command should normally be used only on a test or lab network. If
used on a large network, it could impact service for a significant period of time, as it would force all
CMs to simultaneously reset and reregister with the Cisco CMTS.
Note The clear cable modem all reset command can result in the CPU utilization temporarily reaching
100 percent for a couple of minutes, as the CPU processes the command for all CMs. The CPU
utilization will return to normal within a couple of minutes.
Examples The following example shows how to reset the CM at IP address 172.23.45.67:
Router# clear cable modem 172.23.45.67 reset
The following example shows how to reset all CMs that have an OUI that has been defined as having the
vendor name of Cisco using the cable modem vendor command:
Router# clear cable modem oui Cisco reset
The following example shows how to reset all CMs that are currently in one of the reject states:
Router# clear cable modem reject reset
For the Cisco uBR10012 router, the following example shows how to reset all wideband CMs that are
registered as traditional DOCSIS modems:
Router# clear cable modem wideband registered-traditional-docsis reset
clear cable modem {ip | mac | name domain name | [interface] {all | offline | oui oui | reject |
wideband | none-bounding-capable }} service-type-id
Usage Guidelines This command clears the CM’s service type id.
Examples The following example shows how to clear cable modem service type id:
Router# clear cable modem all service-type-id
clear cable modem [cable slot/subslot/port] {all | offline | oui string | reject} voice{retries | tag}
Syntax Description ip-addr Specifies removal of an individual CM by its IPv4 or IPv6 address.
mac-addr Specifies removal of an individual CM by its 48-bit hardware address (MAC
address).
retries Clears the CM downstream retries record.
tag Clears the CM voice tag.
cable slot/subslot/port (Optional—Cisco uBR10012 Router) Specifies clearing of voice tags for
CMs on the specified cable interface, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
all Specifies clearing of voice tags for all CMs or all CMs associated with a
specified cable interface.
offline Specifies clearing of voice tags for all offline CMs or all such CMs
associated with a specified interface.
oui string Specifies clearing of voice tags for all CMs that match the specified
Organization Unique Identifier (OUI) or all such CMs associated with a
specified interface. The string parameter can be either the three byte
hexadecimal string (such as 00.00.0C) or a vendor name that has been
defined using the cable modem vendor command.
reject Specifies clearing of voice tags for all CMs that are currently in one of the
reject states or all such CMs associated with a specified interface. (See the
show cable modem command for a description of these states).
Examples The following example shows how to clear the voice tag and retries record for the CM at IP
address 172.16.23.45:
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
nb-channel-number Represents the narrowband channel number.
Related
Commands Command Description
clear cable flap-list Resets the flap-list table for a specific CM or for all CMs.
clear cable modem Removes one or more CMs from the internal address and routing tables on a
delete CMTS router and stops DOCSIS station maintenance messages.
clear cable modem Resets the lock on one or more CMs.
lock
clear cable modem Removes or resets CMs by domain name.
name
clear cable modem Removes one or more CMs from the Station Maintenance List and resets
reset them.
clear cable secondary-ip interface cable {slot/port | slot/subport/port}[all | sid sid [ip-address]]
Syntax Description slot/port (Cisco uBR7100 and Cisco uBR7200 Series Routers) Specifies the
cable interface and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface
line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS
router and cable interface line card. Refer to the hardware
documentation for your router chassis and cable interface line card
for supported slot and port numbering.
slot/subslot/port Cisco uBR10012 Router) Specifies the cable interface, where:
• slot—Specifies the chassis slot number of the cable interface
line card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0
to 4, depending on the cable interface line card.
all Specifies that all IP addresses in the secondary IP address table
should be cleared.
sid sid Specifies that all IP addresses for a particular Service ID (SID)
should be cleared. The valid range is 1 to 8191.
ip-address (Optional) Specifies that the IP address for a particular CM or CPE
device should be cleared.
Release Modification
12.3BC This command was integrated into Cisco IOS Release 12.3BC.
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 To support BPI and BPI+ operations with CMs and CPE devices that use secondary IP addresses, the
CMTS maintains a database that links the known secondary IP addresses to the SIDs used by those
devices. When the CMTS and CM need to renew their public keys, the CMTS uses this database to
ensure that all IP addresses are sufficiently updated to allow proper routing and fast switching.
Tip You can display the list of known IP addresses per SID by using the show interface cable sid command.
If you encounter apparent problems with secondary IP addressing, or if you want to manually clear the
table of IP addresses for a particular SID, use the clear cable secondary-ip command.
Tip One possible situation that might occur is if a CM first assigns a secondary IP address to one CPE device,
but later that same IP address is assigned to another CPE device behind a different CM. If this happens,
the IP address will continue to show up as a secondary IP address for the original CM until that CM
renews its public keys. This will not affect network connectivity for either CPE or CM. You can,
however, clear the unneeded secondary IP address from the CMTS database using the clear cable
secondary-ip command.
Examples The following example shows how to clear all of the secondary IP addresses for a particular cable
interface:
Router# clear cable secondary-ip interface cable 3/0 all
The following example shows how to clear the secondary IP addresses for all CM and CPE devices on
cable interface 1/0 that are using SID 5:
Router# clear cable secondary-ip interface cable 1/0 sid 5
The following example shows how to clear the secondary IP addresses for the CM and CPE devices on
cable interface 5/0 that are using SID 113 and IP address 10.10.17.3:
Router# clear cable secondary-ip interface cable 5/0 sid 113 10.10.17.3
clear cable modem {ip | mac | name domain name | [interface] {all | offline | oui oui | reject |
wideband | none-bounding-capable }} service-type-id
Usage Guidelines This command clears the CM’s service type id.
Examples The following example shows how to clear cable modem service type id:
Router# clear cable modem all service-type-id
Syntax Description slot slot/subslot (IPsec VPN SPA only—Optional) Chassis slot number and secondary slot
number on the SPA Interface Processor (SIP) where the SPA is installed.
Refer to the appropriate hardware manual for slot information. For SIPs,
refer to the platform-specific SPA hardware installation guide or the
corresponding “Identifying Slots and Subslots for SIPs and SPAs” topic in
the platform-specific SPA software configuration guide.
Resets platform statistics for the corresponding IPsec VPN SPA to zero.
This output will not include network interface controller statistics.
all (IPsec VPN SPA only—Optional) Resets platform statistics for all IPsec
VPN SPAs on the router to zero. This reset will not include network
interface controller statistics.
detail (IPsec VPN SPA only—Optional) Resets platform statistics for the IPsec
VPN SPA and network interface controller statistics to zero.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA
to support the IPsec VPN SPA on Cisco 7600 series routers and
Catalyst 6500 series switches.
12.2(33)SXH This command was integrated into Cisco IOS Release
12.2(33)SXH.
The following example shows the platform statistics for all IPsec VPN SPAs on the router being cleared
to zero:
Router# clear crypto engine accelerator counter all
Command Description
crypto map Creates and modifies a crypto map for a session.
debug crypto engine Displays each control command as it is given to the crypto engine.
accelerator control
debug crypto engine Displays information about each packet sent for encryption and
accelerator packet decryption.
show crypto engine accelerator Displays the contents of command and transmits rings for the crypto
ring engine.
show crypto engine accelerator Displays the active (in-use) entries in the crypto engine SA
sa-database database.
show crypto engine accelerator Displays the current run-time statistics and error counters for the
statistic crypto engine.
show crypto engine brief Displays a summary of the configuration information for the crypto
engine.
show crypto engine Displays the version and configuration information for the crypto
configuration engine.
show crypto engine Displays a list of the current connections maintained by the crypto
connections engine.
Syntax Description name (Optional) Identifies the IPSec virtual private network (VPN) tunnel to be
disconnected or cleared with a unique, arbitrary name. If no name is
specified, all existing tunnels are disconnected or cleared.
Defaults If no tunnel name is specified, all active tunnels on the machine are cleared.
Usage Guidelines The clear crypto ipsec client ezvpn command resets the Cisco Easy VPN remote state machine,
bringing down the current Cisco Easy VPN remote connection and bringing it back up on the interface.
If you specify a tunnel name, only that tunnel is cleared. If no tunnel name is specified, all active tunnels
on the machine are cleared.
If the Cisco Easy VPN remote connection for a particular interface is configured for autoconnect, this
command also initiates a new Cisco Easy VPN remote connection.
Examples The following example shows the Cisco Easy VPN remote state machine being reset:
Router# clear crypto ipsec client ezvpn
clear facility-alarm
To clear alarm conditions and rest the alarm contacts, use the clear facility-alarm command in
privileged EXEC mode.
Usage Guidelines The clear facility-alarm command clears the contacts to an external alarm panel. Only a reoccurrence
of the original alarm source after the original alarm condition is removed can restart the audible alarm.
These alarms are displayed by the show facility-alarm status command.
The alarm LEDs remain lit on the Performance Routing Engine (PRE) as long as the alarm condition
continues and is not cleared by the clear facility-alarm command. An alarm can only be removed from
the list by correcting the issue that is triggering the alarm.
Examples The following example shows how to clear all facility alarms on the router:
Router# clear facility-alarm
Clearing all alarms
The following example shows how to clear all critical facility alarms on the router:
Router# clear facility-alarm critical
Clearing critical alarms
The following example shows how to clear minor facility alarms only:
Router# clear facility-alarm minor
Clearing minor alarms
Syntax Description group Clears the counters for the specified group number. The valid range is 1 to
255.
all Clears the counters for all HCCP groups.
Usage Guidelines This command clears the counters that are displayed by the show hccp and show hccp interface
commands. You can clear the counters for a single HCCP group, or all HCCP groups.
Examples The following example shows the counters for group 1 being reset to 0:
Router# clear hccp 1 counters
The following example shows the counters for all groups being reset to 0:
Router# clear hccp all counters
Syntax Description ip_addr ip_addr Indicates the IP address of the RKS server to be cleared.
port Indicates the UDP port of the RKS server to be cleared.
all Indicates that information about all RKS servers will be cleared.
Usage Guidelines The clear packetcable rks command is used to clear the unwanted IP addresses of the RKS servers from
the RKS server group list.
Note This command clears the IP addresses of only those RKS servers that are currently not being used. In
other words, if the reference count of an RKS server is a non-zero value, that entry will not cleared from
the RKS server group list.
Tip You can verify the value of reference count (ref-cnt) by executing the show packetcable event command
with the rks-group keyword.
Examples The following sample shows how to clear the the RKS server with IP address 2.39.26.8 on port 1816:
router# clear packetcable rks ip_addr 2.39.26.8 1816
The following sample shows how to clear the entries of all RKS servers:
router# clear packetcable rks all
Command Default The committed gate counter is reset to zero by default with router restart, and gates are not cleared
periodically by default.
Usage Guidelines This command is used to reset the gate counter being used to track the total number of committed gates.
The CMTS router maintains a count of the total number of gates committed from the router’s last startup.
This command can be used to either clear all the gate commit counts, or to specifically clear the counts
for DQoS- or multimedia-based gates.
A show command is used to display the total number of gates committed on the CMTS.
Examples The following example shows the committed gate counter being reset to zero:
Router# clear packetcable gate counter commit
Command Description
packetcable multimedia Enables and displays PacketCable Multimedia processing on
the Cisco CMTS.
packetcable timer multimedia T1 Sets the default timeout value for T1timer used in PCMM gate
processing.
clear pxf
To clear Parallel eXpress Forwarding (PXF) counters and statistics, use the clear pxf command in
privileged EXEC mode.
clear pxf [dma counters | interface interface | statistics {context | diversion | drop | ip | ipv6} | xcm
counters]
Syntax Description dma counters (Optional) Clears the direct memory access (DMA) PXF counters.
interface interface (Optional) Clears the PXF counters on the specified interface.
statistics (Optional) Type of PXF statistics to clear. The options are:
• context—Current and historical loads on the PXF.
• diversion—Traffic diverted from the PXF.
• drop—Dropped packets and bytes.
• ip— IP and ICMP statistics.
• ipv6—IPv6 statistics.
xcm counters Clears the PXF Error Code Correction (ECC) counters.
Usage Guidelines If no interface is specified, the command clears PXF counters on all interfaces. The clear pxf command
clears counters associated with the show pxf dma, show pxf interface, show pxf statistics, and show
pxf xcm commands.
Examples The following example clears PXF statistics for serial interface 1/0/0:
Router# clear pxf interface serial 1/0/0
Usage Guidelines This command sets the drop count to zero for all entries in the PXF DRL cable/wan-ip statistics table. It
does not change any other value.
Usage Guidelines This command sets the drop count to zero for all entries in the PXF DRL wan-non-ip statistics table.
Examples The following example shows how to clear the PXF statistics in wan-non-ip:
Router# clear pxf statistics drl wan-non-ip
clear redundancy
To clear the counters and history information that are used by the Redundancy Facility (RF) subsystem,
use the clear redundancy command in privileged EXEC mode.
Syntax Description counters Clears the RF counters that are maintained by the RF subsystem.
history Clears the history of RF activity that is maintained by the RF subsystem.
Usage Guidelines The clear redundancy command clears the following information, which is shown by the show
redundancy command:
• counters—Number of messages sent and received, buffers used, and synchronization errors.
• history—RF subsystem activity, such as checkpoint messages sent between RF clients.
Examples The following example shows how to clear the RF counters that are displayed by the show redundancy
command:
Router# clear redundancy counters
The following example shows how to clear the RF history information that is displayed by the show
redundancy command:
Router# clear redundancy history
controller integrated-cable
To enter controller configuration mode to configure the controller interface for an integrated
DOCSIS 3.0 cable interface line card, use the controller integrated-cable command in global
configuration mode.
Syntax Description integrated-cable Identifies the cable interface on the Cisco uBR10012 router.
slot/subslot/port
• slot—Slot where the line card resides. The valid range is from 5 to 8.
• subslot—Subslot where the line card resides. Available slots are 0 or 1.
• port—Downstream controller number on the line card. Valid port values
are from 0 to 4.
integrated-cable Identifies the cable interface on the Cisco uBR7246VXR or
slot/port Cisco uBR7225VXR router.
• slot—Slot where the line card resides.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
• port—Downstream port number on the line card. The valid port value is
0 or 1.
Examples The following example shows how to enter controller configuration mode to configure the controller
interface in slot 5, subslot 1, and port 0 of the Cisco uBR10012 router:
Router# configure terminal
Router(config)# controller integrated-cable 5/1/0
controller modular-cable
To enter controller configuration mode to configure the SPA controller, use the
controller modular-cable command in global configuration mode.
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0 is
always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
Usage Guidelines This command indicates where the SPA is located and enters controller configuration mode.
Examples The following example shows how to enter controller configuration mode for the Cisco Wideband SPA
in slot 1, subslot 0, and bay 0.
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
cops ip dscp
To specify the Common Open Policy Service (COPS) Differentiated Services Code Point (DSCP)
markings for COPS messages that are transmitted by the Cisco router, use the cops ip dscp command in
global configuration mode. To remove this configuration, use the no form of this command.
cops ip dscp [0-63 | default | af11-af43 | cs1-cs7]
no cops ip dscp [0-63 | default | af11-af43 | cs1-cs7]
The values for this command specify the markings with which COPS messages are transmitted. The
following values are supported for the Cisco CMTS router.
Usage Guidelines This feature allows you to change the Differentiated Services Code Point (DSCP) marking for COPS
messages that are transmitted or received by the Cisco router. Cisco IOS Release 12.3(13a)BC supports
this function with the cops ip dscp command. The cops ip dscp command changes the default IP
parameters for connections between the Cisco router and COPS servers in the cable network.
DSCP values are used in Quality of Service (QoS) configurations on a Cisco router to summarize the
relationship between DSCP and IP precedence. This command allows COPS to remark the packets for
either incoming or outbound connections.
The default setting is 0 for outbound connections. On default incoming connections, the COPS engine
takes the DSCP value from the COPS server initiating the TCP connection.
Note This feature affects all TCP connections with all COPS servers.
• The cops ip dscp command allows the Cisco router to re-mark the COPS packets for either incoming
or outbound connections.
• This command affects all TCP connections with all COPS servers.
• This command does not affect existing connections to COPS servers. Once you issue this command,
this function is supported only for new connections after that point in time.
• For messages transmitted by the Cisco router, the default DSCP value is 0.
• For incoming connections to the Cisco router, the COPS engine takes the DSCP value used by the
COPS server that initiates the TCP connection, by default.
For additional information about this feature and related commands, refer to the “COPS Engine
Operation on the Cisco CMTS Routers” feature document on Cisco.com.
Examples The following basic example illustrates the use of this command:
The following example illustrates the cops ip dscp command with supported command variations:
Router(config)# cops ip dscp ?
<0-63> DSCP value
af11 Use AF11 dscp (001010)
af12 Use AF12 dscp (001100)
af13 Use AF13 dscp (001110)
af21 Use AF21 dscp (010010)
af22 Use AF22 dscp (010100)
af23 Use AF23 dscp (010110)
af31 Use AF31 dscp (011010)
af32 Use AF32 dscp (011100)
af33 Use AF33 dscp (011110)
af41 Use AF41 dscp (100010)
af42 Use AF42 dscp (100100)
af43 Use AF43 dscp (100110)
cs1 Use CS1 dscp (001000) [precedence 1]
cs2 Use CS2 dscp (010000) [precedence 2]
cs3 Use CS3 dscp (011000) [precedence 3]
The following example specifies the COPS server and enables COPS for RSVP on the server. Both of
these functions are accomplished by using the ip rsvp policy cops command. By implication, the default
settings for all remaining COPS for RSVP commands are accepted.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# ip rsvp policy cops servers 161.44.130.168 161.44.129.6
Router(config)# exit
The following examples display three views of the COPS for RSVP configuration on the router, which
can be used to verify the COPS for RSVP configuration.
The following example displays the policy server address, state, keepalives, and policy client
information:
Router# show cops servers
COPS SERVER: Address: 161.44.135.172. Port: 3288. State: 0. Keepalive: 120 sec
Number of clients: 1. Number of sessions: 1.
COPS CLIENT: Client type: 1. State: 0.
The following example displays the policy server address, the ACL ID, and the client/server connection
status:
Router# show ip rsvp policy cops
The following example displays the ACL ID numbers and the status for each ACL ID:
Router# show ip rsvp policy
Command Description
debug packetcable subscriber Enables and displays debugging processes for PacketCable
subscribers.
show cops servers Displays COPS server addresses, port, state, keepalives, and policy
client information.
show debug Displays current debugging information that includes PacketCable
COPS messages on the Cisco CMTS.
show ip rsvp policy Displays policy server addresses, ACL IDs, and client/server
connection status.
Syntax Description acl-num Alphanumeric identifier of up to 30 characters, beginning with a letter that
identifies the ACL to apply to the current interface.
acl-name Numeric identifier that identifies the access list to apply to the current
interface. For standard access lists, the valid range is 1 to 99; for extended
access lists, the valid range is 100 to 199.
Command Default Access lists are not configured by default on the Cisco router.
Usage Guidelines When using ACLs with cable monitor and the Cisco uBR10012 router, combine multiple ACLs into one
ACL, and then configure cable monitor with the consolidated ACL. For more information about cable
monitor, refer to the “Cable Monitor and Intercept Features for the Cisco CMTS” documentation on
Cisco.com.
Examples The following example illustrates a short access list configuration for the COPS listener feature:
Router# cops listeners access-list 40
Command Description
debug packetcable gate Enables and displays debugging processes for PacketCable gate
control control.
debug packetcable subscriber Enables and displays debugging processes for PacketCable
subscribers.
show cops servers Displays COPS server addresses, port, state, keepalives, and policy
client information.
show debug Displays current debugging information that includes PacketCable
COPS messages on the Cisco CMTS.
show ip rsvp policy Displays policy server addresses, ACL IDs, and client/server
connection status.
Syntax Description bytes This is the TCP window size setting in bytes. This value can range from 516
to 65535 bytes.
Usage Guidelines This command does not affect existing connections to COPS servers. Once you issue this command, this
function is supported only for new connections after that point in time.
Examples The following example configures the TCP window size to be 64000 bytes.
Router(config)# cops tcp window-size 64000
Command Description
debug packetcable subscriber Enables and displays debugging processes for PacketCable
subscribers.
show cops servers Displays COPS server addresses, port, state, keepalives, and policy
client information.
show debug Displays current debugging information that includes PacketCable
COPS messages on the Cisco CMTS.
show ip rsvp policy Displays policy server addresses, ACL IDs, and client/server
connection status.
cpd
To enable the Control Point Discovery (CPD) feature, use the cpd command in global configuration
mode. To disable CPD, use the no form of this command.
cpd
no cpd
cpd cr-id
To configure a Control relationship identifier (CR ID), the the cpd cr-id command in global
configuration mode. To disable the CR ID, use the no form of this command.
no cpd cr-id
Syntax Description cr id number Control relationship identifier. The valid range is 1 to 65535.
Examples The following example shows the control relationship identifier configured as 236:
Router(config)# cpd cr-id 236
cpe max
To create a DOCSIS configuration file that specifies the maximum number of CPE devices that can use
the CM to connect to the cable network, use the cpe max command in cable config-file configuration
mode. To remove the CPE specification, use the no form of this command.
no cpe max
Syntax Description cpe-num Specifies the number of CPEs. Valid range is 1 to 254.
Command Default A maximum of one CPE device can use the CM to connect to the cable network.
Usage Guidelines The CM enforces the limitation imposed by the cpe max command, but the CMTS might enforce its own
lower number of CPE devices. On Cisco CMTS routers, a cpe-num value of 0 enables an unlimited
number of hosts, but on some CMs, this value provides only 0 hosts.
Examples The following example shows how to set the maximum CPE value for the configuration file:
Router(config)# cable config-file channeloverride.cm
Router(config-file)# cpe max 3
Router(config-file)# exit
Command Description
privacy Specifies privacy options for baseline privacy images.
service-class Specifies service class definitions for the configuration file.
snmp manager Specifies Simple Network Management Protocol (SNMP) options.
timestamp Enables time-stamp generation.
Command Default The hardware accelerator for IPSec encryption is enabled by default.
Usage Guidelines This command is not normally needed for typical operations because the router’s onboard hardware
accelerator for IPSec encryption is enabled by default. The hardware accelerator should not be disabled
except on instruction from Cisco TAC personnel.
Examples The following example shows how to enable the router’s onboard hardware accelerator for IPSec
encryption. This is normally needed only after the accelerator has been disabled for testing or debugging
purposes.
Router# crypto engine accelerator
Router#
The following example shows how to disable the router’s onboard hardware accelerator. If IPSec
encryption is configured, all current connections are brought down. Future encryption is performed by
the Cisco IOS software, which has the same functionality as the hardware accelerator, but performance
is significantly slower.
Router# no crypto engine accelerator
Warning! all current connections will be torn down.
Do you want to continue? [yes/no]: y
...Crypto accelerator in slot 0 disabled
Note A separate crypto ipsec client ezvpn command exists in interface configuration mode that assigns a
Cisco Easy VPN Remote configuration to the interface.
Syntax Description name Identifies the Cisco Easy VPN Remote configuration with a unique,
arbitrary name.
Command Default Newly created Cisco Easy VPN Remote configurations default to client mode.
Usage Guidelines The crypto ipsec client ezvpn command creates a Cisco Easy VPN Remote configuration and then
enters the Cisco Easy VPN Remote configuration mode, at which point you can enter the following
subcommands:
• connect [auto | manual]—To manually establish and terminate an IPSec VPN tunnel on demand.
– The auto option is the default setting, because it was the initial Phase I functionality. The IPSec
Virtual Private Network (VPN) tunnel is automatically connected when the Cisco Easy VPN
Remote feature is configured on an interface.
– The manual option specifies the manual setting to direct the Cisco Easy VPN Remote to wait
for a command or API call before attempting to establish the Cisco Easy VPN Remote
connection. When the tunnel times out or fails, subsequent connections have to wait for the
command to reset to manual or an application program interface (API) call.
• default—Sets the following command to its default values.
• exit—Exits the Cisco Easy VPN configuration mode and returns to global configuration mode.
• group group-name key group-key—Specifies the group name and key value for the VPN
connection.
• local-address interface-name—To inform the Cisco Easy VPN router which interface is used to
determine the public IP address, which is used to source the tunnel. This applies only to the
Cisco uBR905 and Cisco uBR925 cable access routers.
– The value of interface-name specifies the interface used for tunnel traffic.
After specifying the local address used to source tunnel traffic, the IP address can be obtained in two
ways:
– The local-address subcommand can be used with the cable-modem dhcp-proxy {interface
loopback number} command to obtain a public IP address and automatically assign it to the
loopback interface.
– The IP address can be manually assigned to the loopback interface.
• mode {client | network-extension}—Specifies the router’s VPN mode of operation:
– The client option (default) automatically configures the router for Cisco Easy VPN client mode
operation, which uses NAT/PAT address translations. When the Cisco Easy VPN client
configuration is assigned to an interface, the router automatically creates the NAT/PAT and
access-list configuration needed for the VPN connection.
– The network-extension option specifies that the router should become a remote extension of
the enterprise network at the other end of the VPN connection. The PCs that are connected to
the router typically are assigned an IP address in the enterprise network’s address space.
• no—Removes the command or sets it to its default values.
• peer {ipaddress | hostname}—Sets the peer IP address or hostname for the VPN connection. A
hostname can be specified only when the router has a DNS server available for hostname resolution.
Note The Cisco Easy VPN Remote feature attempts to resolve the hostname when the peer
command is given, not when the VPN tunnel is created. If the hostname cannot be resolved
at that time, the peer command is not accepted.
After configuring the Cisco Easy VPN Remote configuration, use the exit command to exit the
Cisco Easy VPN Remote configuration mode and return to global configuration mode.
Note You cannot use the no crypto ipsec client ezvpn command to delete a Cisco Easy VPN Remote
configuration that is assigned to an interface. You must remove that Cisco Easy VPN Remote
configuration from the interface before you can delete the configuration.
Examples The following example shows a Cisco Easy VPN Remote configuration named telecommuter-client
being created on a Cisco uBR905 or Cisco uBR925 cable access router and being assigned to cable
interface 0:
Router# config t
Router(config)# crypto ipsec client ezvpn telecommuter-client
Router(config-crypto-ezvpn)# group telecommute-group key secret-telecommute-key
Router(config-crypto-ezvpn)# peer telecommuter-server
Router(config-crypto-ezvpn)# mode client
Router(config-crypto-ezvpn)# exit
Router(config)# interface c0
Router(config-if)# crypto ezvpn telecommuter-client
Router(config-if)# exit
Router(config)#
Note Specifying the mode client option as shown above is optional, because this is default configuration for
these options.
The following example shows the Cisco Easy VPN Remote configuration named telecommuter-client
being removed from the interface and then deleted:
Router# config t
Router(config)# int e1
Router(config-if)# no crypto ipsec client ezvpn telecommuter-client
Router(config-if)# exit
Router(config)# no crypto ipsec client ezvpn telecommuter-client
Router(config)#
Note A separate crypto ipsec client ezvpn command exists in global configuration mode that creates a
Cisco Easy VPN Remote configuration.
Syntax Description name Specifies the Cisco Easy VPN Remote configuration to be assigned to the
interface.
outside (Optional) Specifies the outside interface of the IPSec client router. This is
optional for outside interfaces. You can add up to four outside tunnels, one
tunnel per outside interface, for all platforms.
inside (Optional) Specifies the inside interface of the IPSec client router. The
Cisco 1700 series has no default inside interface and any inside interface
must be configured. The Cisco 800 series routers, and Cisco uBR905 and
Cisco uBR925 cable access routers have default inside interfaces. However,
you can configure any inside interface. You can add up to three inside
interfaces for all platforms.
Command Default The default inside interface is the Ethernet interface on Cisco 800 series routers and Cisco uBR905 and
Cisco uBR925 cable access routers.
Usage Guidelines The crypto ipsec client ezvpn command assigns a Cisco Easy VPN Remote configuration to an
interface, enabling the creation of a virtual private network (VPN) connection over that interface to the
specified VPN peer. If the Cisco Easy VPN Remote configuration is configured for the client mode of
operation, this also automatically configures the router for network address translation (NAT)/port
address translation (PAT) and an associated access list.
Cisco IOS Release 12.2(8)YJ and Cisco IOS Release 12.2(15)T enhanced the command to allow you to
configure multiple outside and inside interfaces. To configure multiple outside and inside interfaces, you
must use the interface interface-name command to first define type of interface on the IPSec client
router.
• In client mode for the Cisco Easy VPN Remote feature, a single security association (SA)
connection is used for encrypting and decrypting the traffic coming from all the inside interfaces. In
network extension mode, one SA connection is established for each inside interface.
• When a new inside interface is added or an existing one is removed, all established security
association (SA) connections are deleted and new ones are initiated.
• Configuration information for the default inside interface is shown with the crypto ipsec client
ezvpn name inside command. All inside interfaces, whether they belong to a tunnel, are listed in
interface configuration mode, as an inside interface, along with the tunnel name.
The following Cisco IOS Release 12.2(4)YA restrictions apply to the crypto ipsec client ezvpn
command:
• In Cisco IOS Release 12.2(4)YA, the Cisco Easy VPN Remote feature supports only one tunnel, so
the crypto ipsec client ezvpn command can be assigned to only one interface. If you attempt to
assign it to more than one interface, an error message is displayed. You must use the no form of this
command to remove the configuration from the first interface before assigning it to the second
interface.
• The crypto ipsec client ezvpn command should be assigned to the outside interface of the NAT/PAT
translation. This command cannot be used on the inside NAT/PAT interface. On some platforms, the
inside and outside interfaces are fixed.
For example, on Cisco uBR905 and Cisco uBR925 cable access routers, the outside interface is
always the cable interface. On Cisco 1700 series routers, the Fast Ethernet interface defaults to being
the inside interface, so attempting to use the crypto ipsec client ezvpn command on the Fast
Ethernet interface displays an error message.
Note You must first use the global configuration version of the crypto ipsec client ezvpn command to create
a Cisco Easy VPN Remote configuration before assigning it to an interface.
Examples The following example shows a Cisco Easy VPN Remote configuration named telecommuter-client
being assigned to the cable interface on a Cisco uBR905/uBR925 cable access router:
Router# config t
Router(config)# interface c0
Router(config-if)# crypto ipsec client ezvpn telecommuter-client
Router(config-if)# exit
Router(config)#
The following example first shows an attempt to delete the Cisco Easy VPN Remote configuration
named telecommuter-client, but the configuration cannot be deleted because it is still assigned to an
interface. The configuration is then removed from the interface and then deleted:
Router# config t
Syntax Description name Identifies the IPSec VPN tunnel with a unique, arbitrary name.
Usage Guidelines This command is used with the connect [auto | manual] subcommand. After the manual setting is
designated, the Cisco Easy VPN Remote feature waits for a command or API call before attempting to
establish the Cisco Easy VPN Remote connection.
If the configuration is manual, then the tunnel is connected only after the crypto ipsec client ezvpn
connect name command is entered in privileged EXEC mode, and after the connect [auto] | manual
subcommand is entered.
Examples The following example shows how to connect an IPSec VPN tunnel named ISP-tunnel on a
Cisco uBR905/uBR925 cable access router:
Router# crypto ipsec client ezvpn connect ISP-tunnel
Command Description
crypto ipsec client (Interface configuration mode) Assigns a Cisco Easy VPN Remote
ezvpn (interface configuration to an interface.
configuration)
ip http ezvpn Enables the Cisco Easy VPN Remote web server interface.
Syntax Description name Identifies the IPSec VPN tunnel with a unique, arbitrary name.
Usage Guidelines If the tunnel name is not specified, the authorization request is made on the active tunnel. If there is more
than one active tunnel, the command fails with an error requesting that you specify the tunnel name.
When making a VPN connection, individual users might also be required to provide authorization
information, such as a username or password. When the remote end requires this information, the router
displays a message on the router’s console instructing the user to enter the crypto ipsec client ezvpn
xauth command. The user then uses the CLI to give this command and reply to the following prompts
to provide the required information.
Note If the user does not respond to the Authentication notification, the message is repeated every ten seconds.
Examples The following example shows the user being prompted to enter the crypto ipsec client ezvpn xauth
command. The user then enters the requested information and continues.
Router#
20:27:39: EZVPN: Pending XAuth Request, Please enter the following command:
20:27:39: EZVPN: crypto ipsec client ezvpn xauth
Router#
New Commands
Modified Commands
Replaced Commands
The following commands have been replaced by new commands beginning in the following Cisco IOS
software releases:
description description
no description
Syntax Description description Specifies a description for the cable fiber node. The character-string can be
up to 80 characters long.
Command Default If the description command is not issued, a description does not exist.
Usage Guidelines The description command adds a comment to the configuration to provide information about the fiber
node.
Examples The following example shows how to specify a description for fiber node 5:
Router# configure terminal
Router(config)# cable fiber-node 5
Router(config-fiber-node)# description Branch office 5
depi-class
To create a template of Downstream External PHY Interface (DEPI) control plane configuration settings,
which different pseudowire classes can inherit, and to enter the DEPI class configuration mode, use the
depi-class command in global configuration mode. To remove a specific DEPI class configuration, use
the no form of this command.
depi-class depi-class-name
no depi-class depi-class-name
Syntax Description depi-class-name Name of the DEPI class. The depi-class-name argument must be specified to
configure multiple sets of DEPI control parameters.
Usage Guidelines The depi-class depi-class-name command allows you to configure a DEPI class template that consists
of configuration settings used by different pseudowire classes. The depi-class command enters DEPI
class configuration mode, where DEPI control plane parameters are configured.
You must use the same DEPI class in the pseudowire configuration at both ends of a Layer 2 control
channel.
Examples The following example shows how to enter DEPI class configuration mode to create a DEPI class
configuration template for the class named SPA0:
Router# configure terminal
Router(config)# depi-class SPA0
Router(config-depi-ctrl SPA0)#
Command Description
show depi tunnel Displays all active control connections.
show depi session Displays established DEPI data sessions.
depi-tunnel
To create a template of Downstream External PHY Interface (DEPI) tunnel configuration settings, which
different pseudowire classes can inherit, and to enter the DEPI data session configuration mode, use the
depi-tunnel command in the global configuration mode or subinterface configuration mode. To remove
a configured DEPI tunnel, use the no form of this command.
depi-tunnel depi-tunnel-name
no depi-tunnel depi-tunnel-name
Usage Guidelines The depi-tunnel creates a template of DEPI tunnel configuration settings. The DEPI data session
inherits the control plane configuration settings of a depi-control template.
The following depi data session configuration options are available in this mode:
• l2tp-class
• depi-class
• dest-ip
• tos
Examples The following example shows how to create a template of DEPI tunnel configuration settings in the
global configuration mode and enter the DEPI data session configuration mode:
Router# configure terminal
Router(config)# depi-tunnel rf6
Router(config-depi-tunnel)#
The following example shows how to create a template of DEPI tunnel configuration settings in the
subinterface configuration mode:
Router(config)# interface qam 6/4.1
Router(config-subif)# depi-tunnel 0
dest-ip
To assign an IP address to the edge quadrature amplitude modulation (EQAM), use the dest-ip command
in DEPI tunnel configuration mode. To remove a specific destination IP address, use the no form of this
command.
dest-ip dest-ip-address
no dest-ip dest-ip-address
Usage Guidelines The dest-ip dest-ip-address command allows you to configure the IP address of the EQAM.
Examples The following example shows how to assign 1.3.4.155 as the destination IP address:
Router# configure terminal
Router(config)# depi-tunnel rf6
Router(config-depi-tunnel)# dest-ip 1.3.4.155
diagnostic load
To load a Field Diagnostic image to the line card for field diagnostic testing, enter the diagnostic load
command.
diagnostic load {slot slot | subslot slot/subslot} image-url [autostart test {all [port port-number
| WORD]}| basic | default | per-port port-number}]
Syntax Description slot Specifies that the line card downloading the Field Diagnostic image is in a full slot
as opposed to a subslot.
subslot Specifies that the line card downloading the Field Diagnostic image is in a subslot
(in other words, a half-height line card) as opposed to a full slot.
slot Specifies the number of the slot where the line card downloading the Field
Diagnostic image is located on the router.
subslot Specifies the number of the subslot where the line card downloading the Field
Diagnostic image is located on the router.
image-url Specifies the path where the Field Diagnostic image is being downloaded from.
• If the Field Diagnostic image was saved to the router’s Flash file system, enter
the file system (such as disk0: or disk1:) as the image-url.
• If the Field Diagnostic image was saved to a server, the image-url will include
server-type://path, where server-type is the type of server (typically either
FTP or TFTP) and path is the path to the file on the TFTP server where the
Field Diagnostic image has been saved.
autostart If autostart is specified, the diagnostic testing process for the line card will begin
automatically once the Field Diagnostic image has been loaded onto the line card.
test The test option is used to specify which type of testing will occur. If the test
option is not entered, the default test is used.
all When used after the test option, specifies that all Field Diagnostic tests will be run
during the testing period, including the external loopback test.
When used after the port option, specifies that external loopback tests should be
run on all ports on the line card.
port port-number Specifies the port number on the interface that should perform the external
loopback test.
WORD Specifies a range of ports.
basic Specifies that the basic Field Diagnostic test suite will be run. The basic test suite
will catch most hardware problems but not run each individual test like the all test
suite option. The advantage of running the basic test suite is that it takes less time
to run than the other test suites.
default Specifies that the default test suite will be run. The default test suite will run all
Field Diagnostic tests for the particular line card with the exception of the external
loopback test.
If no test suite or test is specified when requesting a test, the default test suite is
run.
per-port Specifies that an external loopback test should be run on a specific port.
port-number
Command Default If the autostart option is entered but no test is specified, the default test suite is the suite used to test the
line card.
Usage Guidelines Entering this command and successfully downloading the Field Diagnostic image will disrupt normal
line card operation. To remove the Field Diagnostic image from a line card and restore normal line card
operation, use the diagnostic unload command.
If the autostart option is not specified, diagnostic tests can be run on the line card after the Field
Diagnostic image has been loaded by entering the diagnostic start command.
Examples In the following example, the diagnostic load command is used to download the Field Diagnostic image
in TFTP server 127.1.1.1/mytftpfolder to the line card in slot 2. If yes is entered at the prompt below, the
router will be placed in Field Diagnostic mode.
Router# diagnostic load slot 2 tftp://127.1.1.1/mytftpfolder/c10k-fdiagslc-mz.1.1.bin
******************************************************************************
WARNING:The specified line card will be taken offline, please ensure that
all traffic has been redirected before executing this command.
% Are you sure that you want to perform this operation? [no]:
Syntax Description continue failure-limit Specifies that Field Diagnostic testing should continue on the line
card after a failed test occurs. The failure-limit specifies the number
of failed tests that can be detected before testing on the line card
should stop. A failure-limit of 0 means testing should continue
regardless of the number of failed tests.
Note The failure-limit is the number of failed tests, not errors
within a single test. For example, if four errors occur during
a single test, the failure-limit for that individual test would
be 1, not 4.
stop Specifies that Field Diagnostic testing should stop when an error
event occurs.
Command Default If this command is not entered, a default failure-limit of 0 is used. Therefore, testing will continue
regardless of the number of errors unless the diagnostic ondemand action-on-failure command is used
to change the default setting.
Usage Guidelines The diagnostic ondemand action-on-failure settings cannot be saved to a Cisco IOS configuration file.
Therefore, the diagnostic ondemand action-on-failure command will need to be re-entered each time
a router is reset or power cycled if the action-on-failure settings should be maintained.
The show diagnostic ondemand settings command can be used to verify the diagnostic ondemand
action-on-failure setting.
The show diagnostic events event-type error command can be used to gather additional information
about an error event.
Examples In the following example, the diagnostic on-demand iteration and action-on-failure settings are changed
using diagnostic ondemand iterations and diagnostic ondemand action-on-failure. The changed
settings are then confirmed using show diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2
Test iterations = 2
Syntax Description iteration-count The number of tests to be run each time a Field Diagnostic test is
started. For instance, if the iteration-count is set at 2 and the Field
Diagnostic test specifies that tests 1, 5, and 10 will be run, tests 1, 5,
and 10 will all be run twice. If basic or default testing is specified
and the iteration-count is 2, all basic or default tests will be run
twice.
Usage Guidelines The diagnostic ondemand iterations settings cannot be saved to a Cisco IOS configuration file.
Therefore, the diagnostic ondemand iterations command will need to be re-entered each time a router
is reset or power cycled if a nondefault setting needs to be maintained.
The show diagnostic ondemand settings command can be used to verify the diagnostic ondemand
iterations setting.
Examples In the following example, the diagnostic on-demand iteration and action-on-failure settings are changed
using diagnostic ondemand iterations and diagnostic ondemand action-on-failure. The changed
settings are then confirmed using show diagnostic ondemand settings.
Router# diagnostic ondemand iterations 2
Router# diagnostic ondemand action-on-failure stop
Router# show diagnostic ondemand settings
Test iterations = 2
Action on test failure = stop
In the following example, the diagnostic ondemand iterations command is first used to change the
number of iterations per test to 2. Therefore, a Field Diagnostic test is run twice (note that the output of
the diagnostic start command reflects the test being run twice).
After the initial test, the iteration-count is then changed to 3 and the same test is run. Note that the output
of diagnostic start shows each test being run three times as opposed to two after the iteration-count was
changed using the diagnostic ondemand iterations 3 command.
Router# diagnostic ondemand iterations 2
Router# diagnostic start slot 8 test 1
Slot 8: Running test(s) 1 may generate packets out of the card interface.
FDIAG [slot 8]> Field Diagnostics passed with the selected test(s)
FDIAG [slot 8]> Field Diagnostics passed with the selected test(s)
Command Description
diagnostic ondemand Sets the number of times each specific Field Diagnostic test will be run
iterations when a Field Diagnostic test is initiated.
diagnostic start Starts Field Diagnostic testing on the line card.
diagnostic stop Stops an in-progress Field Diagnostic test.
show diagnostic content Shows the Field Diagnostic test list for a particular line card.
show diagnostic events Displays the history of Field Diagnostic events since the last system
reload.
show diagnostic Shows the diagnostic on-demand settings.
ondemand settings
show diagnostic result Shows the results of the Field Diagnostic test.
show diagnostic Displays various status information, such as line card slot and name,
ood-status Field Diagnostic image status, and previous Field Diagnostic test results.
diagnostic unload
To unload the Field Diagnostic on the line card and resume normal line card operation, enter the
diagnostic unload command.
Syntax Description slot Specifies that the line card unloading the Field Diagnostic image is
in a full slot as opposed to a subslot.
subslot Specifies that the line card unloading the Field Diagnostic image is
in a subslot as opposed to a full slot.
slot-number Specifies the number of the slot where the line card unloading the
Field Diagnostic image is located on the router.
subslot-number Specifies the number of the subslot where the line card unloading the
Field Diagnostic image is located on the router.
Usage Guidelines The show diagnostic result output will be lost once a Field Diagnostic image is successfully unloaded
off a line card. If you want to retain the results of the Field Diagnostic test, enter show diagnostic result
and copy the output into a separate file before entering diagnostic unload to unload the Field Diagnostic
image off the line card.
Entering this command successfully will resume normal line card operation.
If a line card needs to be placed back online immediately and a Field Diagnostic test is in progress, enter
diagnostic stop to stop the in-progress Field Diagnostic test before entering diagnostic unload to
unload the Field Diagnostic image off the line card.
Examples In the following example, the Field Diagnostic image is unloaded off of the line card in slot 2. Note that
the command is not successfully executed until confirmed at the screen prompt.
Router# diagnostic unload slot 2
******************************************************************************
WARNING:All Field Diagnostics test results and information will be
unavailable to both the "show diagnostic result <target>" and
"show diagnostic content <target>" commands.
To save the test results, cancel the unloading process and enter
% Are you sure that you want to perform this operation? [no]:y
FDIAG [slot 2]> Unloading the Field Diagnostics image and restoring the original run-time
image, please wait ...
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Syntax Description codeAccessStart start-time Specifies the code Access Start Time as a UTC time value
(YYMMDDhhmmssZ) in Greenwich Mean Time.
cvcAccessStart start-time Specifies the CVC Access Start Time as a UTC time value
(YYMMDDhhmmssZ) in Greenwich Mean Time.
organization name Specifies the name of the manufacturer of the code file. Use quotes if the
name value contains more than one word.
Command Default The codeAccessStart and cvcAccessStart times default to 011219000000Z (midnight on December 19,
2001 Greenwich Mean Time). The organization defaults to Cisco Systems.
Note Typically, the default values should not be changed unless you are instructed to do so by Cisco TAC or
field service engineers.
Usage Guidelines This command configures the access start times and organization name that are required by Appendix D
in the DOCSIS BPI+ specification. The time values are specified as UTC time values in Greenwich Mean
Time, with a two-digit year. If the year is between 50 and 99, it is interpreted as 1950 to 1999. If the year
is between 00 and 49, it is interpreted as 2000 to 2049.
The router uses the codeAccessStart value to verify the Code Verification Signature (CVS) that is
affixed to the code file downloaded using the secure software download feature. The router uses the
ccvAccessStart value to verify the CVC for the code file. The router also uses the organization value
to verify that the code file has been created by the proper manufacturer.
Tip These values are the same that are set using the docsBpi2CodeMfgCodeAccessStart,
docsBpi2CodeMfgCvcAccessStart, and docsBpi2CodeMfgOrgName attributes in the BPI+ MIB
(DOCS-BPI2-MIB).
Examples The following example shows the default configuration for the docsis cvc mfg commands:
Router(config)# docsis cvc mfg organization "Cisco Systems"
Router(config)# docsis cvc mfg codeAccessStart 011219000000Z
Router(config)# docsis cvc mfg cvcAccessStart 011219000000Z
Router(config)#
Note You must set the organization name using the docsis cvc mfg organization command before you can set
either access start time.
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Syntax Description codeAccessStart start-time Specifies the code Access Start Time as a UTC time value
(YYMMDDhhmmssZ) in Greenwich Mean Time.
cvcAccessStart start-time Specifies the CVC Access Start Time as a UTC time value
(YYMMDDhhmmssZ) in Greenwich Mean Time.
organization name Specifies the name of the manufacturer of the code file. Use quotes if the
name value contains more than one word.
Usage Guidelines This command configures the optional cosigner access start times and organization name that are
specified by Appendix D in the DOCSIS BPI+ specification. The time values are specified as UTC time
values in Greenwich Mean Time, with a two-digit year. If the year is between 50 and 99, it is interpreted
as 1950 to 1999. If the year is between 00 and 49, it is interpreted as 2000 to 2049.
You do not need to use this command unless the MSO or service provider is digitally signing the
Cisco IOS software images that it plans to download to the Cisco cable modems. If so, then this
command must be used to set the appropriate access times and organization name, so that the cable
modem can properly authenticate the software images during a secure software download.
The router uses the codeAccessStart value to verify the cosigner’s Code Verification Signature (CVS)
that is affixed to the code file downloaded using the secure software download feature. The router uses
the ccvAccessStart value to verify the cosigner’s CVC that is affixed to the code file. The router also
uses the organization value to verify that the code file has been signed by the proper MSO or cable
operator.
Tip These values are the same that are set using the docsdocsBpi2CodeCoSignerCodeAccessStart,
Bpi2CodeCoSignerCvcAccessStart, and docsBpi2CodeCoSignerOrgName attributes in the BPI+ MIB
(DOCS-BPI2-MIB).
Examples The following example shows the docsis cvc mso commands being used to configure the router for a
cosigned CVC from an organization named “MSO Organization” and with certificate access times of
midnight on March 1, 2002 Greenwich Mean Time:
Router(config)# docsis cvc mfg organization "MSO Organization"
Router(config)# docsis cvc mfg codeAccessStart 020301000000Z
Router(config)# docsis cvc mfg cvcAccessStart 020301000000Z
Router(config)#
Note You must set the organization name using the docsis cvc mso organization command before you can set
either access start time.
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command verifies that the root CA public key and the private key that are installed in the router at
the factory are valid. The command uses the root CA public key to encrypt a string, and then it uses the
router’s private key to decrypt the key.
Typically, the root CA public key and private key are installed at the factory and never need to be
updated. However, DOCSIS allows the keys to be updated as part of the secure software download
procedure. If this occurs, you can use the docsis cvc test command to verify that the keys are valid and
are properly installed.
Examples The following example shows a typical successful result of the docsis cvc test command:
Router# config terminal
Router(config)# docsis cvc test
Encrypted sting: This is a test
Encrypt result: xxxxxxxxxxxxxxxxxxxxxxxxxxx
Note If the decrypt result is not “This is a test,” then the test failed, which indicates that either the public key
or the private key is not valid.
docsis-policy
To assign a policy to a DOCSIS load balancing group, use the docsis-policy command in the
config-lb-group configuration mode. The policy becomes the default policy assigned to the CM, if the
CM does not choose a different policy. To remove the assigned policy, use the no form of this command.
docsis-policy n
no docsis-policy
Syntax Description n Load balancing group policy number. The policy number can range from 0
to 4294967295.
Examples The following example shows how to assign a policy to a DOCSIS load balancing group on the CMTS,
using the docsis-policy command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# docsis-policy 1
Config: Last Batch 0, 63 bytes
cable load-balance docsis-group 1 index 81
docsis-policy 1
end
docsis-version
To configure the DOCSIS version of the CM for the CMTS tag, use the docsis-version command in the
cmts-tag configuration mode. To remove the configured DOCSIS version from the CMTS tag, use the
no form of this command.
no docsis-version docsis-version
Syntax Description exclude (Optional) Configures the CMTS tag to exclude the specified DOCSIS
version.
docsis-version DOCSIS version for the CMTS tag. You can select one of the following
DOCSIS versions to match the DOCSIS modems:
• docsis10 - Matches DOCSIS 1.0 modems
• docsis11 - Matches DOCSIS 1.1 modems
• docsis20 - Matches DOCSIS 2.0 modems
• docsis30 - Matches DOCSIS 3.0 modems.
Examples The following example shows how to configure the specified DOCSIS version for the CMTS tag using
the docsis-version command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# docsis-version docsis10
download
To create a DOCSIS configuration file that instructs the CM to download a new software image, use the
download command in cable config-file configuration mode. To disable the specification, use the no
form of this command.
Note Because of conflicts with other Cisco IOS commands, you cannot abbreviate the no form of this
command. You must specify the complete command name and option, such as no download image or
no download server.
Usage Guidelines This command sets the Software Upgrade Filename and Software Upgrade TFTP Server fields in the
DOCSIS configuration file. The DOCSIS specification allows the DOCSIS configuration file to specify
that the CM must be running a particular software image. If the CM is not currently using that image, it
must then download the image before continuing the registration process. For security, performance, and
scalability reasons, a particular TFTP server can be specified from which the CM must download the
new software image.
The filename specified by download image command must be a fully qualified file and pathname that
exactly matches the file and pathname as they exist on the TFTP download server. For example, if the
software image is named ubr920-k1v4y556i-mz and is in a subdirectory named cisco_cms on the TFTP
server, the filename specified with this command should be cisco_cms/ubr920-k1v4y556i-mz.
If the oui-list parameter is specified, the download image filename is provided only to the CMs that
contain those particular OUIs. This helps ensure that the CM does not download a software image that
is intended for another vendor’s CMs.
Note For each configuration file, multiple download images can be specified. Because each filename can be
listed only once, entering a different list of OUIs for a single filename clears the old list. To support more
than eight OUIs with the same file, use a different download software image name, and create a duplicate
file or alias on the TFTP server.
The download server command is not required. If it is not specified, the CM uses the same server that
provided its DOCSIS configuration file. However, the download server command requires that the
image filename also be specified using the download image command.
Examples The following command shows how to setup a DOCSIS configuration file so that the cable modem will
upgrade its software image:
Router(config)# cable config-file upgrade.cm
Router(config-file)# download image ubr920-k1v4y556i-mz.121-3a.T1 oui 00.50.73 00.D0.BA
00.D0.58 00.01.96
Router(config-file)# download server 10.15.24.33
Router(config-file)# exit
Router(config)#
downstream
To set downstream radio frequency (RF) channels, use the downstream command in the config-lb-group
configuration mode. To reset the downstream RF channels, use the no form of this command.
Syntax Description cable {slot/port} Specifies the CMTS interface slot and port numbers.
cable Specifies the CMTS interface slot, subslot, and port numbers.
{slot/subslot/port}
Integrated-Cable Specifies the integrated cable interface with the list of port numbers that
{rf-channel group range in the associated RF channel. Slot, subslot, and bay numbers of the
list}{slot/subslot/bay} integrated cable interface is also specified.
Modular-Cable Specifies the modular cable interface with the list of port numbers that range
{rf-channel group in the associated RF channel. It also specifies slot, subslot, and bay numbers
list}} {slot/subslot/bay} of the modular cable interface.
Examples The following example shows how to set downstream RF channels to a DOCSIS load balancing group
on the CMTS, using the downstream command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# downstream cable 1/1
Router(config-lb-group)# downstream Integrated-Cable 5/0/0 rf-channel 2
Router(config-lb-group)# downstream Modular-Cable 1/0/0 rf-channel 4
downstream cable
To assign a primary downstream channel for a fiber node, use the downstream cable command in cable
fiber-node configuration mode. To remove a primary downstream channel for a fiber node, use the no
form of the command.
Syntax Description slot The slot used for the cable interface line card. Valid values are 5 to 8.
subslot The subslot used for the cable interface line card. Valid values are 0 or 1.
port The downstream port that can be used as a primary downstream channel.
Valid values are 0 to 4.
Command Default If the downstream cable command is not issued, no primary downstream channel is assigned to the fiber
node.
Usage Guidelines For each fiber node, a traditional DOCSIS downstream channel is used to carry MAC management and
signaling messages, and the associated traditional DOCSIS upstream channel is used for return data
traffic and signaling. The traditional DOCSIS downstream channel used in this way is called the primary
downstream channel.
The downstream cable command assigns a primary downstream channel for a fiber node. Each fiber
node must be assigned at least one primary downstream channel and can be assigned multiple primary
downstream channels. Cisco IOS software decides which primary downstream channel to use for the
fiber node from the set of channels assigned with downstream cable. Assigning more than one primary
channel to a fiber node with the downstream cable command can be useful for load-balancing purposes.
Note If the primary downstream channel for the fiber node is assigned from a SPA downstream, then the
downstream cable command is not required.
If the modem’s fiber node has not been assigned a primary downstream channel with the downstream
cable command, the modem can register on any downstream channel that is visible to it.
For more information on using this command, refer to the Cisco uBR10012 Universal Broadband Router
SIP and SPA Software Configuration Guide.
Examples The following example shows how to assign a primary downstream channel for fiber node 5. The primary
downstream channel is the downstream port located on the cable interface line card at slot/subslot/port
6/0/0.
Router# configure terminal
Router(config)# cable fiber-node 5
Router(config-fiber-node)# downstream cable 6/0/0
Syntax Description grouplist Specifies the number of upstreams associated with the
Cisco uBR10-MC5X20 downstream channels.
Command Default All upstreams under the cable interface are associated with the Cisco uBR10-MC5X20 downstreams.
Usage Guidelines Use this command to restrict a set of Cisco uBR10-MC5X20 upstreams to Cisco uBR10-MC5X20
downstreams. This restricts MAC management messages (MMM) to be sent to the specified upstreams
only.
Examples The following example shows how the downstream local upstream command is used in the
Cisco uBR10012 router.
Router# configure terminal
Router (config)# interface cable 5/1/0
Router(config-if)# downstream local upstream 0-1
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0 is
always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
rf-channel Specifies the association of a continuous range of RF channels within the
SPA downstream.
rf channels Range of RF channel physical ports on the SPA FPGA.
upstream Specifies a set of ranges of upstream to allow association of a noncontiguous
list of upstreams to one or more SPA downstreams.
grouplist Specifies the number of upstreams with the modular cable downstream
channel.
Command Default No default upstream channels are configured with the modular downstream channels.
Usage Guidelines Use this command to create primary-capable channels by associating a single or a set of
Cisco uBR10-MC 5X20 upstream channels with individual modular downstream channels on a fiber
node. When a primary-capable channel is created, the same modular downstream channel cannot be used
as a primary-capable channel in another MAC domain. However, it can be used as non-primary-capable
channel in another MAC domain.
Examples The following example shows how the downstream modular-cable rf-channel command is used in the
Cisco uBR10012 router.
Router# configure terminal
Router (config)# interface cable 5/1/0
Router(config-if)# downstream modular-cable 1/0/0 rf-channel 0-2 upstream 0-1 4-5
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0 is
always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
rf-port Specifies the RF channel physical port on the Wideband SPA FPGA. Valid
values for rf-port depend on the configuration set with the annex modulation
command.
low-high A range of RF channel physical ports on the Wideband SPA FPGA. The low
and high values are separated by a hyphen.
Command Default If the downstream modular-cable rf-channel command is not issued, no RF channels are configured
for wideband channels on the fiber node.
Usage Guidelines The downstream modular-cable rf-channel command makes RF channels available for use on a fiber
node. Fiber node software configuration mirrors the physical topology of the cable network. The cable
rf-channel command configures the RF channels that will be used for a wideband channel on a
Wideband SPA.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command.
Note Effective with Cisco IOS Release 12.3(23)BC, the annex modulation command is obsolete and annex
and modulation are included as keyword options in the rf-channel frequency command.
• For annex A and 256 QAM, each Wideband SPA supports 18 RF channels. In this case, valid values
for the rf-port argument are 0 to 17.
• For all other cases, the SPA supports 24 RF channels. In these cases, valid values for the rf-port
argument are 0 to 23.
A fiber node can be configured to have RF channels from one or both Wideband SPAs. However, a
wideband channel cannot be comprised of RF channels from two different SPAs.
Each time the downstream modular-cable rf-channel command is issued for a fiber node, the set of
RF channels that are available for use on that fiber node is added to in a cumulative manner. For example,
if the following downstream modular-cable rf-channel commands were issued, the set of RF channels
available for fiber node 1 is RF channels 0 to 10 on the Wideband SPA in slot/subslot/bay 1/0/0.
Router# configure terminal
Router(config)# cable fiber-node 1
Router(config-fiber-node)# downstream modular-cable 1/0/0 rf-channel 0-5
Router(config-fiber-node)# downstream modular-cable 1/0/0 rf-channel 6-10
Examples The following example shows how to specify that RF channels 0 to 7 on a Wideband SPA will be
available for use on fiber node 5. The Wideband SPA is located in slot/subslot/bay 1/0/0.
Router# configure terminal
Router(config)# cable fiber-node 5
Router(config-fiber-node)# downstream modular-cable 1/0/0 rf-channel 0-7
dtmf-relay
To configure the router so it transmits Dual-Tone Multifrequency (DTMF) tones as out-of-band signals
during H.323 voice calls, use the dtmf-relay command in dial-peer voice configuration mode. To return
to the default configuration of transmitting DTMF tones as part of the voice traffic, use the no form of
this command.
Cisco uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
no dtmf-relay
Syntax Description cisco-rtp (Optional) Forwards DTMF tones using the Real-Time Transport Protocol
(RTP) with a Cisco proprietary payload type.
Note RTP is a proprietary Cisco protocol that interoperates only between
two Cisco access servers or routers running Cisco IOS images that
support the RTP protocol. The RTP protocol typically requires
Cisco IOS 12.0(5)T or later releases; see the router’s release notes
for complete information.
h245-alphanumeric (Optional) Forwards DTMF tones using the H.245 Alphanumeric User
Input Indication method. This option transmits each tone using a fixed
duration of 500 milliseconds. Supports tones 0-9, *, #, and A-D.
h245-signal (Optional) Forwards DTMF tones using the H.245 Signal User Input
Indication method. This option transmits each tone using the original
duration and supports tones 0-9, *, #, and A-D.
Defaults By default, DTMF tones are transmitted inband, as part of the voice traffic.
Usage Guidelines DTMF tones are generated when you press the keypad digits on a touch-tone phone. DTMF tones are
most commonly used to dial calls, but they can also be used during a call to interact with an Interactive
Voice Response (IVR) system, such as voicemail, automated banking services and so on. By default,
DTMF tones are transmitted along with the regular voice traffic, but this can cause problems with some
IVR systems.
In particular, IVR systems might not recognize DTMF tones when using highly compressed CODECs
such as G.729a. These CODECs are highly optimized for voice frequencies, but they can distort DTMF
tones, preventing IVR systems from recognizing the tones. To avoid this problem, use one or more of
the following methods of transmitting DTMF tones in an out-of-band channel, separately from the voice
traffic:
• Cisco RTP—This option transmits the DTMF tones using a proprietary encoding that allows them
to use the same RTP channel as the voice traffic. This method accurately transports DTMF tones but
requires the use of Cisco gateways at both the originating and terminating endpoints of the H.323
call.
• H.245 Alphanumeric—This option transmits DTMF tones through a separate H.245 signaling
channel using H.245 User Input Indication messages. Tones are transmitted as alphanumeric digits
with a fixed duration of 500 milliseconds. This method is required for all H.323v2 compliant
systems.
• H.245 Signal—This option transmits DTMF tones through a separate H.245 signaling channel using
H.245 User Input Indication messages. This method preserves both the tone information and the
original duration of the tone, which allows the caller to use services that require you to press a key
for a particular length of time. For example, a popular calling card feature allows you to break out
of an existing call by pressing the pound (#) key for more than two seconds and then make a second
call without having to hang up in between.
You can enable more than one DTMF relay option for a particular dial peer to support multiple
destinations that might use different methods. If you enable more than one option, and if the peer is
capable of receiving DTMF in more than one of these formats, the router selects the DTMF format with
the highest priority:
1. Cisco RTP (highest priority)
2. H.245 Signal
3. H.245 Alphanumeric
4. None—DTMF is sent inband
Examples The following example shows how to configure an outgoing dial peer so that DTMF tones to that
destination are transmitted using the Cisco RTP protocol, if it is supported by the remote end; otherwise,
the DTMF tones are transmitted using the H.245 signaling protocol.
Router(config)# dial-peer voice 100 voip
Router(config-dial-peer)# destination-pattern 555-1212
Router(config-dial-peer)# session target ipv4:192.168.100.110
Router(config-dial-peer)# dtmf-relay cisco-rtp h245-signal
Router(config-dial-peer)# exit
The following example shows how to reconfigure the above dial peer and disables out-of-band DTMF
signaling, so that the DTMF tones are sent inband, as part of the voice traffic:
Router(config)# dial-peer voice 100 voip
Router(config-dial-peer)# no dtmf-relay
Router(config-dial-peer)# exit
duration
To specify the time period and sample rate to be used for monitoring subscribers, use the duration
command in enforce-rule configuration mode. To reset an enforce-rule to its default values, use the no
form of this command.
no duration
Syntax Description minutes Specifies the size of the sliding window (in minutes) during which
subscriber usage is monitored. The valid range is 10 to 44640 with a
default of 360 (6 hours).
avg-rate rate Specifies the average sampling rate in kilobits per second for the
specified duration. The valid range is 1 to 400000 kilobits with no
default.
sample-interval minutes Specifies how often (in minutes) the CMTS router should sample a
service flow to get an estimate of subscriber usage. The valid range is 1
to 30, with a default value of 15.
penalty minutes (Optional) Specifies the period (in minutes) during which a cable
modem (CM) can be under penalty. The valid range is 1 to 10080.
upstream Specifies monitoring of traffic in the upstream direction.
downstream Specifies monitoring of traffic in the downstream direction.
enforce (Optional) Specifies that the enforce-rule QoS profile should be applied
automatically if a user violates their registered QoS profile.
Command Default The duration value defaults to 360 minutes (6 hours), and the sample-interval value defaults to 15
minutes.
Usage Guidelines
Note This command is applicable only after the monitoring-basics command is configured with the keyword
legacy.
When you enable an enforce-rule, the CMTS router periodically checks the bandwidth being used by
subscribers to determine whether any subscribers are consuming more bandwidth than that specified by
the avg-rate configured in enforce-rule. The CMTS router keeps track of subscribers using a sliding
window that begins at each sample interval and continues for the duration period and average rate.
For example, with the default sample interval of 15 minutes and the default sliding window period of
360 minutes, the CMTS router samples the bandwidth usage every 15 minutes and counts the total bytes
transmitted at the end of each 360-minute period. Each sample interval begins a new sliding window
period for which the CMTS router keeps track of the total bytes transmitted.
Note Changing the duration minutes, avg-rate rate, or sample-interval minutes values resets the byte
counters for that particular enforce-rule and begins a new sliding window period.
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.
The penalty duration, which is configured using this command, is unique to weekdays, and takes
precedence over the global penalty duration configured using the penalty-period command.
When you use the show running-configuration command to display the configuration, the keyword
options for the duration command are truncated. In the following example, “pen” represents penalty,
“do” represents downstream, and “enf” represents enforce:
Router# show running-configuration
.
.
.
duration 10 avg-rate 1 sample-interval 10 pen 11 do enf
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 sliding window that is 20 minutes
in length, an avg-rate of 1 kilobit per second, and a sampling interval of every 10 minutes.
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# duration 20 avg-rate 1 sample-interval 10 penalty 11 do enf
Command Description
debug cable Displays enforce-rule debug messages for subscriber traffic
subscriber-monitoring management on the Cisco CMTS routers.
monitoring-basics Specifies the type of monitoring for subscriber traffic management
on a Cisco CMTS router.
peak-time1 Specifies peak and offpeak monitoring times on a Cisco CMTS
router.
penalty-period Specifies the period for which an enforced quality of service (QoS)
profile should be in force for subscribers who violate their
registered QoS profile.
qos-profile registered Specifies the registered QoS profile that should be used for this
enforce-rule. This command is applicable only for DOCSIS 1.0
cable modems.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate
their registered QoS profile. This command is applicable only for
DOCSIS 1.0 cable modems.
service-class (enforce-rule) Specifies a service class (enforced or registered) that should be used
for cable modem monitoring in an enforce-rule. This command is
applicable for DOCSIS 1.1 or later cable modems.
show cable qos enforce-rule Displays the QoS enforce-rules that are currently defined.
show cable subscriber-usage Displays subscribers who are violating their registered QoS
profiles.
weekend duration Configures different subscriber monitoring options over weekends
on a Cisco CMTS router.
enabled (enforce-rule)
To activate an enforce-rule and begin subscriber traffic management on a Cisco CMTS router, use the
enabled command in enforce-rule configuration mode. To disable the enforce-rule without deleting it,
use the no form of this command.
enabled
no enabled
Usage Guidelines An enforce-rule is created and configured using the cable qos enforce-rule command, but it is not
activated until you run the enabled command. Use the no enabled command to disable an enforce-rule
without removing it from the CMTS configuration. When you disable an enforce-rule, all cable modems
with that rule’s registered QoS profile are no longer tracked by the Subscriber Traffic Management
feature and all cable modems in penalty are moved to their registered QoS profile.
The following example shows an enforce-rule being disabled. The rule remains in the CMTS
configuration file.
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# no enabled
Related Commands
Command Description
cable qos enforce-rule Creates an enforce-rule to enforce a particular QoS profile for subscriber
traffic management and enters enforce-rule configuration mode.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate their
registered QoS profiles.
duration Specifies the time period and sample rate to be used for monitoring
subscribers.
penalty-period Specifies the time period that an enforced QoS profile should be in effect for
subscribers that violate their registered QoS profiles.
qos-profile registered Specifies the registered QoS profile that should be use for this enforce-rule.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
enforced qos-profile
Note Effective with Cisco IOS Release 12.3(9a)BC, the enforced qos-profile command is replaced by the
qos-profile enforced command.
To specify a quality of service (QoS) profile that should be enforced when users violate their registered
QoS profiles, use the enforced qos-profile command in enforce-rule configuration mode. To delete the
enforced QoS profile from the enforce-rule, use the no form of this command.
Syntax Description profile-id Specifies the QoS profile to be enforced. The valid range is 0 to 16383,
with a default of 0.
no-persistence (Optional) Specifies that the enforced QoS profile should not remain
in force when a cable modem reboots. Instead, when a cable modem
(CM) that is in the penalty period reboots, it is automatically removed
from the penalty period and assigned the QoS profile that is specified
in its DOCSIS configuration file.
The default is without this option, so that enforced QoS profiles remain
in effect for cable modems across reboots.
Command Default The profile ID defaults to 0, and enforced QoS profiles are persistent across cable modem reboots.
Usage Guidelines Both the originally provisioned QoS profile and the enforced QoS profile must be created on the
Cisco CMTS router. This command does not support profiles that are created by the cable modem.
An enforce-rule can specify an enforced QoS profile, which is automatically applied to subscribers that
transmit more traffic than what is allowed by their registered QoS profile. The enforced QoS profile
remains in effect during the penalty time period (see the penalty-period command). At the end of the
penalty period, the subscriber returns to their registered QoS profile.
If a cable modem reboots while it is in its penalty time period, it continues using the enforced QoS
profile, unless the service provider has manually changed the cable modem’s registered QoS profile
using the cable modem qos profile command.
When you change the enforced QoS profile for a currently active enforce-rule, any cable modems using
this rule that are currently in the penalty period continue using the previously configured enforced QoS
profile. Any cable modems that enter the penalty period after this configuration change, however, use
the new enforced QoS profile.
An enforced QoS profile must already have been created on the Cisco CMTS router before you can
assign it to an enforce-rule. If the rule does not exist, the system displays an error message.
When the no-persistence option is specified, the enforced QoS profile is still automatically applied to
subscribers that violate their bandwidth requirements. However, when the cable modem reboots, the
Cisco CMTS router allows the cable modem to use the QoS profile that is specified in its DOCSIS
configuration file.
The no-persistence option can be used when initially using subscriber traffic management to identify
potential problem applications and users. When repeat offenders are identified, they can then be assigned
enforce-rules that do not use the no-persistence option, so that they remain in the penalty period even
if they reboot their cable modems.
Note In software releases prior to Cisco IOS Release 12.3(9a)BC, the system automatically applies the
enforced QoS profile to violators only if the enforce keyword has been used with the activate-rule
at-byte-count command.
Examples The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# enforced qos-profile 12
The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule,
but with the no-persistence option specified, so that the enforced QoS profile does not remain in force
if the cable modem reboots:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# enforced qos-profile 12 no-persistence
The following example shows the error message that is displayed when the specified QoS profile does
not exist on the CMTS:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# enforced qos-profile 98
Command Description
duration Specifies the time period and sample rate to be used for monitoring
subscribers.
penalty-period Specifies the time period that an enforced QoS profile should be in effect for
subscribers that violate their registered QoS profiles.
qos-profile registered Specifies the registered QoS profile that should be used for this enforce-rule.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
exception pxf
To control the core dumps that are generated when an exception occurs in one of the Parallel eXpress
Forwarding (PXF) columns, use the exception pxf command in global configuration mode. To disable
the creation of core dumps during PXF exceptions, use the no form of this command.
exception pxf {core-file filename | flash device | style {full | localized | minimal | smart} }
Syntax Description core-file filename Sets the filename for the core-dump file generated during a PXF exception.
flash device Specifies the Flash memory device on which to save the core-dump file
generated during a PXF exception.
style Specifies the type of core-dump file to be generated during a PXF
exception.
full Creates a full core-dump file of all PXF columns.
localized Creates a core-dump file of the PXF column that failed, along with its
neighboring columns.
minimal Creates a minimal core-dump file of the PXF exception.
smart Creates a core-dump file that contains the data related to the PXF exception.
Usage Guidelines
Caution Use the exception pxf command only under the direction of a technical support representative. Creating
a core dump can disrupt network operations. The core dump is a large binary file that can be interpreted
only by technical personnel who have access to source code and detailed memory maps.
Examples The following example shows how to specify that the Cisco uBR10012 router should create a minimal
core-dump file for PXF exceptions, and that this file should be named ubr10k-pxf and be written to the
disk1 device:
Router# configure terminal
Router(config)# exception pxf style minimal
Router(config)# exception pxf core-file ubr10k-pxf
facility-alarm (ubr10012)
To set the temperature thresholds at which the Performance Routing Engine (PRE) module generates a
critical, major, or minor alarm to warn of potential equipment damage, use the facility-alarm command
in global configuration mode. To disable the temperature alarms, use the no form of this command.
Syntax Description core-temperature Specifies the temperature threshold for the temperature sensors near the
center of the PRE module.
intake-temperature Specifies the temperature threshold for the temperature sensors at the air
intake slots.
critical exceed-action In Cisco IOS Release 12.2(11)BC1 and later releases, specifies that a
shutdown critical temperature alarm should shut down the router after two minutes.
This was the default behavior in previous releases.
major [temp] Specifies the temperature, in degrees Centigrade, at which the PRE module
generates a major alarm to warn of potential damage from excessive
temperatures.
The valid range for temp is 20 to 67 degrees Centigrade, with a default of
58 for the core temperature threshold and 54 for the intake-temperature
threshold.
minor [temp] Specifies the temperature, in degrees Centigrade, at which the PRE module
generates a minor alarm to warn of potential damage from excessive
temperatures.
The valid range for temp is 20 to 67 degrees Centigrade, with a default of
50 for the core temperature threshold and 45 for the intake-temperature
threshold.
Defaults If no specific temperature is given, that particular facility alarm is reset to its default value. The default
core temperature thresholds are 85 (critical), 58 (major), and 50 (minor). The default intake-temperature
thresholds are 72 (critical), 54 (major), and 45 (minor) degrees Centigrade.
In Cisco IOS releases previous to Cisco IOS Release 12.2(11)BC1, a critical alarm automatically shuts
down the router after two minutes to prevent temperature damage. In Cisco IOS Release 12.2(11)BC1
and later, a critical alarm by default does not shut down the router.
Note The default temperature thresholds for the critical core and intake temperatures were changed in
Cisco IOS Release 12.2(11)BC1.
Usage Guidelines
The PRE module on the Cisco uBR10012 router contains temperature sensors that monitor the
temperature at the air intake slots and on the PRE module itself. The facility-alarm command configures
the router for the temperature thresholds that will generate a minor, major, or critical alarm, so as to
notify the system operators of the temperature problem before excessive heat can damage the router or
any of its components.
Before Cisco IOS Release 12.2(11)BC1, a critical alarm would also automatically shut down the router
after two minutes. Cisco IOS Release 12.2(11)BC1 made this automatic shutdown a configurable option,
so that the system operators can decide whether or not a critical alarm should power down the router.
As a general rule, do not disable the automatic shutdown of the router unless you have a systems operator
available to immediately respond to any critical temperature alarms, because this could result in system
damage. Typically, the primary reason to disable the automatic shutdown would be if you are replacing
the fan tray assembly and want to ensure that the router does not power down if the procedure takes
longer than expected.
Note A line card also automatically shuts itself down if the temperature exceeds operational levels. In
addition, the AC and DC PEMs also automatically power down if they exceed their operational
temperature. However, high temperatures could still cause damage to other components if the problem
is not quickly resolved.
Examples The following example shows how to configure the Cisco uBR10012 router so that it generates a minor
alarm when the intake temperature exceed 55°C:
Router# configure terminal
Router(config)# facility-alarm intake-temperature minor 55
The following example shows how to configure the Cisco uBR10012 router to automatically shut down
if the high temperature continues for more than two minutes:
Router# configure terminal
Router(config)# service internal
Router(config)# facility-alarm core-temperature critical exceed-action shutdown
The following example shows how to disable the automatic shutdown feature for both the core and intake
temperatures. A critical alarm is still generated when the default critical temperatures are exceeded, but
the router does not automatically shut itself down:
Router# configure terminal
Router(config)# no facility-alarm core-temperature critical exceed-action shutdown
Router(config)# no facility-alarm intake-temperature critical exceed-action shutdown
The following commands disable major and minor alarms for both the core and intake temperature
thresholds (but critical alarms are still generated):
Router# configure terminal
Router(config)# no facility-alarm core-temperature major
Router(config)# no facility-alarm core-temperature minor
Router(config)# no facility-alarm intake-temperature major
Router(config)# no facility-alarm intake-temperature minor
flowcontrol
To set the method of data flow control between the terminal or other serial device and the router, use the
flowcontrol command in line configuration mode. To disable flow control, use the no form of this
command.
Catalyst 6500 Series Switches, Cisco 7600 Series Routers, and Cisco uBR10012 Universal Broadband Router
Interface configuration
Usage Guidelines When software flow control is set, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and
XON). You can change them using the stop-character and start-character commands.
If a remote Telnet device requires software flow control, the remote system should not be able to turn it
off. Using the lock option makes it possible to refuse “dangerous” Telnet negotiations if they are
inappropriate.
If a Gigabit Ethernet port receive buffer becomes full, the port transmits a “pause” packet that tells
remote ports to delay sending more packets for a specified period of time. All Ethernet ports
(1000 Mbps, 100 Mbps, and 10 Mbps) can receive and act upon “pause” packets from other devices.
You can configure non-Gigabit Ethernet ports to ignore received pause frames (disable) or to react to
them (enable).
When used with receive, the on and desired keywords have the same result.
All the Gigabit Ethernet ports on the Catalyst 6500 series switches and the Cisco 7600 series routers can
receive and process pause frames from remote devices.
To obtain predictable results, follow these guidelines:
• Use send on only when remote ports are set to receive on or receive desired.
• Use send off only when remote ports are set to receive off or receive desired.
• Use receive on only when remote ports are set to send on or send desired.
• Use send off only when remote ports are set to receive off or receive desired.
Cisco uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Syntax Description ip-address Specifies the IP address to be used for outgoing H.323 traffic, which
includes H.225, H.245, and RAS messages. This IP address typically is the
IP address assigned to the Ethernet interface.
Defaults No defaults assigned. By default, H.323 traffic is transmitted with the IP address assigned to the cable
interface.
Usage Guidelines The h323-gateway voip bind srcaddr command can be used with any interface, but it is primarily used
with the cable access router’s Ethernet interface when configuring a virtual private network (VPN). In
this configuration, the h323-gateway voip bind srcaddr command configures the router so that VoIP
traffic is sent using the IP address of the Ethernet interface (as opposed to the default behavior, which is
to use the IP address of the default outgoing interface, which is the cable interface).
The h323-gateway voip bind srcaddr command allows the enterprise network to maintain the H.323
gatekeeper and gateway in the enterprise network’s address space. Without the h323-gateway voip bind
srcaddr command, outgoing voice traffic uses the IP address of the cable interface. This method requires
that the H.323 gatekeeper and gateway be maintained in the cable service provider’s address space,
which is not desirable if the enterprise needs to control the voice network and VPN configuration.
Note The h323-gateway voip bind srcaddr command can be used only when the cable access router is
operating in routing mode. This command has no effect when the router is operating in DOCSIS bridging
mode.
Examples The following example shows how to configure the Ethernet interface with the IP address of
192.168.100.94, and then how to configure the interface so that H.323 traffic will be transmitted using
that IP address:
Router(config)# interface ethernet0
Router(config-if)# ip address 192.168.100.94 255.255.255.0
Router(config-if)# h323-gateway voip bind srcaddr 192.168.100.94
Router(config-if)#
The following example shows how to remove the H.323 binding, so that H.323 voice traffic is
transmitted using the cable interface’s IP address:
Router(config-if)# no h323-gateway voip bind srcaddr
Router(config-if)#
hccp authentication
To specify the authentication algorithm on a working or protect cable interface, or both use the hccp
authentication command in cable interface configuration mode. To disable authentication on a Working
CMTS or Protect CMTS, use the no form of this command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
md5 Authentication algorithm. In Cisco IOS Release 12.1(3a)EC, MD5 is the
only authentication algorithm supported.
text Unencrypted text specification. Rather than automatically encrypting the
authentication key-chain when using the MD5 authentication algorithm,
Cisco IOS software simply passes the authentication key-chain as standard,
unencrypted text.
Usage Guidelines Use this command together with the hccp authentication key-chain command to enable and specify the
type of N+1 redundancy authentication you will use in your protection scheme.
Examples The following example shows how to specify MD5 as the authentication algorithm for group 1:
Router(config-if)# hccp 1 authentication md5
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
key-chain A text string matching a key chain in the Working CMTS or Protect CMTS
configuration file. A key chain must have at least one key and can have up to
2,147,483,647 keys.
Usage Guidelines Use this command in conjunction with the hccp authentication command to enable and specify the type
of 1+1 redundancy authentication you will use in your protection scheme.
Note You cannot perform authentication on a specified group until you have first defined at least one
authentication key chain in global configuration mode.
Examples The following excerpt from a configuration file enables authentication using the MD5 algorithm and
defines the authentication key “cisco1” for group 1:
!
key chain cisco1
key 1
key-string abcdefg
key 2
key-string 123456789
!
...
!
interface cable 3/0
hccp 1 authentication md5
hccp 1 authentication key-chain cisco1
!
Syntax Description group The group number for the specified interface. The valid range is 1 to 255.
Command Default Normal HCCP operations (hccp group check version), where hardware and software version checks are
made between the Working and Protect cable interface line cards.
Usage Guidelines By default, the Cisco CMTS verifies that the Working and Protect cable interfaces are using the same
versions of software and hardware, so as to avoid potential incompatibilities during a switchover. The
hardware check verifies that the Working and Protect cable interface line cards are compatible. The
software check verifies that the two cards are running the same major versions of software. If either of
these two conditions is not true, the CMTS by default does not perform the switchover.
You can override these version checks for a particular HCCP group by using the hccp bypass version
command. After you give this command, the Cisco CMTS does not check the hardware or software
versions of the two cable interfaces before performing a switchover. To return to normal HCCP
operations, so that version checks are made for a group, use the hccp check version command.
Note Two cable interface line cards are compatible when the Protect card has at least the same number of
upstreams or downstreams as the Working card. The exceptions to this are that the Cisco uBR-MC16E
card can be protected only by another Cisco uBR-MC16E card. Also, the DOCSIS versions of the
Cisco uBR-MC16 card can be protected only by another Cisco uBR-MC16C card. You cannot use the
Cisco uBR-MC28C card to protect a Cisco uBR-MC16B/C/S card.
Examples The following example shows how to disable the hardware and software version checks for HCCP group
number 20. After giving this command, the Cisco CMTS will switchover from the Working to Protect
interface in group 20 without first verifying the cards’ compatibility:
Router# hccp 20 bypass version
Router#
hccp channel-switch
To configure the Cisco CMTS so that a Cisco RF Switch or Vecima (Wavecom) upconverter becomes a
Hot Standby Connection-to-Connection Protocol (HCCP) member in a particular HCCP group, use the
hccp channel-switch command in cable interface configuration mode. To remove the configuration for
the Cisco RF Switch or upconverter, use the no form of this command.
hccp group channel-switch member-id switch-name tty-switch [aux | console | vty] line-number
port
Syntax Description group The group number for the specified interface. The valid range is 1 to 255.
member-id The member number within the specified group. The valid range is 1 to 255.
switch-name (Optional) Alpha-numeric string specifies the name of the
Cisco RF Switch.
rfswitch-group Specifies that this is the configuration for a Cisco RF Switch group.
rfswitch-module Specifies that this is the configuration for a Cisco RF Switch module.
rfswitch-ip-address Specifies the IP address of the Cisco RF Switch to which the CMTS is
connected.
module-bitmap Specifies the module-bitmap in hexadecimal. The valid range is 0 to
FFFFFFFF.
Tip See the TAC-authored N+1 Tips and Configuration document on
Cisco.com for more information on the format of the bitmap, and for
a worksheet that can be used to calculate the bitmap.
module-number Specifies the module number on the Cisco RF Switch. The valid range is 1 to
255.
Note This setting must be configured on the Cisco RF Switch as well as the
Cisco CMTS.
position Specifies the position for the Working channel on the Cisco RF Switch. The
valid range is 1 to 8.
tty-switch Specifies the configuration of a Cisco RF Switch that is controlled by its TTY
line. You can further specify the type of port being used to control the switch.
By default, one of the Cisco RF Switch’s serial ports is used, or you can use
the aux, console, or vty lines.
Note Ensure that the switch’s DIP switch is set to 00.
aux (Optional) Specifies that the auxiliary port is being used to control the
Cisco RF Switch.
console (Optional) Specifies that the console port is being used to control the
Cisco RF Switch.
vty (Optional) Specifies that a Virtual Terminal connection (Telnet connection)
is being used to control the Cisco RF Switch.
line-number Specifies the line number on which the Cisco RF Switch is receiving control
information for this CMTS. The valid range is 0 to 17 for the default serial
port, 0 for the aux port, 0 for the console port, and 0 to 99 for the vty port.
port Specifies the port number being used on the Cisco RF Switch. The valid
range is 1 to 255.
wavecom-hd Specifies that this is the configuration for a Vecima (Wavecom) HD4040 and
QHD4040 upconverter.
wavecom-ma Specifies that this is the configuration for a Vecima (Wavecom)
DUAL4040D, MA4040D, or UC4040D upconverter.
prot-ip-address Specifies the IP address for the upconverter used for the Protect interface
used for this cable interface.
protect-module Specifies the module number on the upconverter used for the Protect
interface to be used for this cable interface. The valid range is 1 to 255.
work-ip-address Specifies the IP address for the upconverter used for the Working interface
used for this cable interface.
work-module Specifies the module number on the upconverter used for the Working
interface to be used for this cable interface. The valid range is 1 to 255.
Command Default The CMTS is not configured to use a Cisco RF Switch by default, and no cable interfaces are configured
for N+1 redundancy by default.
Usage Guidelines You must configure each Working and Protect cable interface for use with the Cisco RF Switch, typically
specifying one hccp channel-switch command to configure the Cisco RF Switch information, and
another hccp channel-switch command to configure the upconverter.
The Protect interface is configured with the same hccp channel-switch commands as those that are used
on the Working interface. However, typically, the same Protect interface is configured with multiple
hccp channel-switch commands to protect multiple Working interfaces.
Examples The following example shows the cable interface 8/1/0 being configured as member 1 for the Working
interface of HCCP group 1. This interface is configured to use the Wavecom HD4040 upconverter with
the IP address of 10.97.1.21. The upconverter’s module number 2 (B) is used for the Protect interface,
and module number 16 (P) is used for the Working interface. The interface uses the Cisco RF Switch at
IP address 10.97.1.20, using a module bitmap of AA200000 in switch slot 1.
Router# configure terminal
Router(config)# interface cable8/1/0
Router(config-if)# hccp 1 working 1
Router(config-if)# hccp 1 channel-switch 1 uc wavecom-hd 10.97.1.21 2 10.97.1.21 16
Router(config-if)# hccp 1 channel-switch 1 rfswitch rfswitch-group 10.97.1.20 AA200000 1
The following example shows the corresponding configuration for the Protect interface for member 1 of
HCCP group 1, which is cable interface 5/1/0 on the same chassis. The hccp channel-switch commands
are identical to those used for cable interface 8/1/0.
Router# configure terminal
Router(config)# interface cable5/1/0
Router(config-if)# hccp 1 protect 1 10.97.1.8
Router(config-if)# hccp 1 channel-switch 1 uc wavecom-hd 10.97.1.21 2 10.97.1.21 16
Router(config-if)# hccp 1 channel-switch 1 rfswitch rfswitch-group 10.97.1.20 AA200000 1
Typically, the same Protect interface is used to protect multiple Working cable interfaces. For example,
this same interface could be configured as follows to protect a Working interface that is using module
number 14 (N) on the same Wavecom HD4040 upconverter, using slot 2 in the RF Switch.
Router# configure terminal
Router(config)# interface cable5/1/0
Router(config-if)# hccp 1 protect 2 10.97.1.8
Router(config-if)# hccp 1 channel-switch 2 uc wavecom-hd 10.97.1.21 2 10.97.1.21 14
Router(config-if)# hccp 1 channel-switch 2 rfswitch rfswitch-group 10.97.1.20 AA200000 2
Syntax Description group The group number for the specified interface. The valid range is 1 to 255.
Command Default Normal HCCP operations (hccp group check version), where hardware and software version checks are
made between the Working and Protect cable interface line cards.
Usage Guidelines By default, the Cisco CMTS verifies that the Working and Protect cable interfaces are using the same
versions of software and hardware, so as to avoid potential incompatibilities during a switchover. The
hardware check verifies that the Working and Protect cable interface line cards are compatible. The
software check verifies that the two cards are running the same major versions of software. If either of
these two conditions is not true, the CMTS by default does not perform the switchover.
You can override these version checks for a particular HCCP group by using the hccp bypass version
command. After you give this command, the Cisco CMTS does not check the hardware or software
versions of the two cable interfaces before performing a switchover. To return to normal HCCP
operations, so that version checks are made for a group, use the hccp check version command.
Note Two cable interface line cards are compatible when the Protect card has at least the same number of
upstreams or downstreams as the Working card. The exceptions to this are that the Cisco uBR-MC16E
card can be protected only by another Cisco uBR-MC16E card. Also, the DOCSIS versions of the
Cisco uBR-MC16 card can be protected only by another Cisco uBR-MC16C card. You cannot use the
Cisco uBR-MC28C card to protect a Cisco uBR-MC16B/C/S card.
Examples The following example shows how to cancel a previous hccp bypass version command for HCCP
group 1 and to return to normal HCCP operations:
Router# hccp 1 check version
Router#
hccp ds-switch
To specify the downstream upconverter module for a Working CMTS or Protect CMTS, use the hccp
ds-switch command in cable interface configuration mode. To negate a downstream upconverter
assignment, use the no form of this command.
Note This command has been deprecated in current Cisco IOS releases and has been replaced by the hccp
channel-switch command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
member The member number within the specified group.
make The maker of the specified upconverter. Currently, only the Wavecom
upconverter is supported (wavecom).
host-ipaddr The IP address of the upconverter module1 to which the host CMTS is
connected.
host-module The upconverter module number to which the host CMTS is connected. This
location is expressed as a simple numeric designation.
peer-ipaddr The IP address of the upconverter module to which the peer (or remote)
CMTS is connected.
peer-module The upconverter module number1 to which the peer (or remote) CMTS is
connected. This location is expressed as a simple numeric designation.
1. The identification of the upconverter module is important to define when the host or peer CMTS is connected to a channel
switch housing multiple modules. For example, the Wavecom MA4040D upconverter chassis offers a maximum of 10
independent frequency agile upconverters.
Command Default Upconverter specification and activation is disabled by default and must be specified before switching
can take place.
Usage Guidelines It is necessary to configure the downstream upconverter module for all Protect CMTS and Working
CMTS systems. If you do not specify the downstream upconverter module for all Protect CMTS and
Working CMTS systems, you cannot switch between a Protect CMTS and Working CMTS.
Examples The following excerpt from a configuration file specifies module 2 on a Wavecom upconverter at IP
address 1.1.11.3 as the host switch module connected to Working CMTS 1 and module 1 on the same
Wavecom upconverter (with the same IP address location) as the peer or remote switch module
connected to the Protect CMTS:
hccp 1 working 1
hccp ds-switch 1 wavecom 1.1.11.3 2 1.1.11.3 1
hccp lockout
To prevent a Working CMTS from automatically switching to a Protect CMTS in the same group, use
the hccp lockout command in privileged EXEC mode.
Note This command is applicable only to Working CMTS in a given group. Issuing this command on a Protect
CMTS has no effect.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
member The member number within the specified group.
Usage Guidelines Typically the hccp lockout command is used to disable HCCP switchovers before removing the HCCP
configuration on the Working interface. Otherwise, when you remove the HCCP configuration from the
Working interface, the Protect interface assumes the Working interface has failed and switches over.
You might also want to prevent a Working CMTS from automatically switching back to a Protect CMTS
for testing or additional configuration purposes. For example, you might want to fully test protecting
cable interfaces on your Cisco CMTS before returning it to protect status.
Examples The following example shows how to activate the lockout feature of a Working CMTS in group 1:
Router# hccp 1 lockout
hccp protect
To configure a particular cable interface to protect another cable interface in the same group, use the
hccp protect command in cable interface configuration mode. To undo a particular host cable interface
protection assignment, use the no form of this command.
Syntax Description group The group number of both the Working and Protect cable interfaces. Valid
values are any number from 1 to 255, inclusive.
member The member number of the specified Working cable interface. Valid values
are any number from 1 to 255, inclusive.
ipaddr An IP address for any working interface (other than protected cable
interfaces) installed in the Working CMTS that can transmit and receive
redundancy status messages.
Usage Guidelines The protect cable interface must be configured identically to the working cable interface, which typically
means the interfaces must be the same card type. However, when the Cisco uBR-MC16S card is used, it
can be used with either another Cisco uBR-MC16S card or a Cisco uBR-MC16C card.
Table 22 shows how a switchover affects the enhanced spectrum management features of the
Cisco uBR-MC16S card.
Examples The following example configures host cable interface 4/0 to protect member 2 of group 2 at
IP address 1.1.11.2:
Router(config)# interface cable 4/0
Router(config-if)# hccp 2 protect 2 1.1.11.2
hccp resync
To manually synchronize the Inter-database between the Working and Protect interfaces for a particular
member in an Hot Standby Connection-to-Connection Protocol (HCCP) group, use the hccp resync
command in privileged EXEC mode.
Syntax Description group The group number for the specified interface. The valid range is 1 to 255.
member The member ID to be resynchronized. The valid range is 1 to 255.
Usage Guidelines The Cisco CMTS automatically synchronizes the Working and Protect interfaces to ensure that when a
switchover occurs, the Protect interface will run with a configuration that is identical to that of the
Working interface. However, if you are troubleshooting HCCP problems, you can manually
resynchronize the databases using the hccp resync command before performing any switchover tests.
Note When a SYNC event command is occurring, CLI commands might be very slow to respond. In particular,
if you enter a show command at the same time a SYNC event is occurring, the command might respond
produce a blank display, or it might display an error message similar to the following:
Examples The following example shows how to manually resynchronize the Inter-database between the Working
and Protect interfaces for member 4 in HCCP group 13:
Router# hccp 13 resync 4
Router#
hccp revertive
To configure a cable interface on a Protect CMTS that has assumed working capacity to automatically
revert back to the Working CMTS, use the hccp revertive command in cable interface configuration
mode. To disable the ability for the specified cable interface to automatically revert back to protect
status, use the no form of this command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
Usage Guidelines Using this command in conjunction with the hccp reverttime command gives you the ability to set up
your protecting cable interfaces to automatically switch between working and protecting capacity
without your intervention. Otherwise, whenever a switchover has occurred, you must manually
reactivate the failed Working CMTS and manually return the Protect CMTS to protect status using the
hccp switch command.
Tip If you are using the hccp revertive command on a cable interface, do not also configure the hccp track
command. Configuring both commands on the same interface can cause multiple switchovers on the
same fault.
Examples The following example shows cable interface 4/0 on a Protect CMTS in group 2 being configured to
automatically revert to protect status after the Working CMTS peer has returned to active duty:
router(config)# interface cable 4/0
router(config-if)# hccp 2 revertive
hccp reverttime
To specify the amount of time a Protect interface waits before automatically reverting back to a Working
interface following a system switchover, use the hccp reverttime command in cable interface
configuration mode on the Working CMTS. To set the revert-time back to its default value, use the no
form of this command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
revert-time The amount of time (in minutes) that a Protect interface waits before
automatically switching back to a Working interface following a system
switchover. The allowable range is 1 to 65,535 minutes, with a default of 30
minutes.
Command Modes Interface configuration (cable interface only, on the Working CMTS)
Usage Guidelines Use this command to configure the revert-time on the cable interfaces on the Working CMTS so that the
Working CMTS will automatically resume normal operations and the Protect CMTS will automatically
resume normal protect operations, in case an operator forgets to manually switch the Working CMTS
back into operation after fixing the original problem.
The Working CMTS first counts down two minutes of suspend time before starting to count down the
revert-time. Any failures that occur within this two-minute suspend time are considered part of the same
failure.
This means that the actual time that the Working CMTS will attempt to switch back after a switchover
is two minutes plus the revert-time. For example, if the revert-time is set to its default of 30 minutes, the
Working CMTS will attempt to switch back into operation 32 minutes after the initial switchover to the
Protect CMTS.
After the suspend time has occurred, a failure in the Protect CMTS will cause a switchover to the
Working CMTS, regardless of whether the revert-time has expired or not. You can force such a failure
in the Protect CMTS, and restore the Working CMTS to operation without waiting for the revert-time,
by using the cable power off and cable power on commands to turn off and turn on the protect interface
on the Protect CMTS.
When choosing a revert-time, take into account all possible sources of failures, including third-party
equipment. For example, an upconverter failure can trigger a switchover to the Protect CMTS. You
should configure the revert-time so that the Working CMTS does not switch back into operation until
technicians have had sufficient time to fix the equipment failure.
Tip To disable the revert-time feature, use the no version of the hccp revertive command on the Protect
CMTS.
Examples The following example shows cable interface 3/0 on a Working CMTS in group 2 being configured to
wait 15 minutes before automatically reverting back to working status after a system switchover:
router(config)# interface cable 3/0
router(config-if)# hccp 2 reverttime 15
The following example shows how to give the no form of this command, which resets the interface back
to its default value of 30 minutes.
router(config)# interface cable 5/1/0
router(config-if)# no hccp 2 reverttime
hccp switch
To manually switch a Protect CMTS with its Working CMTS peer (or vice versa), use the hccp switch
command in privileged EXEC mode.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
member The member number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
Usage Guidelines This command overrides any configuration you may have made on your Protect CMTS and Working
CMTS using the hccp revert and hccp reverttime commands. In addition, you can issue the hccp
switch command on either a Protect CMTS or a Working CMTS to force it to change places with its peer.
Examples The following example shows the host Protect CMTS being configured to assume traffic responsibility
for member 2 Working CMTS in group 2:
Router# hccp 2 switch 2R
hccp timers
To configure HELLO packet interval and hold time for a specified group on a Protect CMTS, use the
hccp timers command in cable interface configuration mode. To erase the HELLO interval and hold
time configuration and to assume the default values for each parameter, use the no form of this
command.
Note Issuing the no form of this command erases any manual HELLO interval and hold time values and
automatically resets them to their default values.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
hello-time The HELLO packet interval (in milliseconds) between subsequent HELLO
packet transmissions. The acceptable range is 1666 to 5,000 milliseconds,
inclusive.
hold-time The time (in milliseconds) that a Protect CMTS will wait before assuming
control of voice traffic for a Working CMTS that has failed to acknowledge
a series of HELLO packets. The acceptable range is 5,000 to 25,000
milliseconds, inclusive.
Command Default The default HELLO interval is 2,000 milliseconds, and the default hold time is 6,000 milliseconds.
Examples The following example shows the HELLO interval and hold time on a Protect CMTS in group 2 being
configured to 1,750 and 3,000 milliseconds, respectively:
Router(config)# interval c4/0
Router(config-if)# hccp 2 timers 1750 3000
hccp track
To configure a cable interface on a Working CMTS or Protect CMTS to enable automatic switchover
based on the interface state, use the hccp track command in cable interface configuration mode. To
disable the automatic switchover based on interface state, use the no form of this command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
interface Specifies another cable interface (the default is the current cable interface).
Usage Guidelines This command enables automatic switchover of one interface when a tracked interface switches over
from “up” to “down.”
Typically, this command is used to allow all interfaces on one card to track one another, so that if one
interface goes down and switches over to the Protect, all other interfaces can also switch over, allowing
the Protect card to assume full operation for these interfaces. This allows support engineers to
troubleshoot the problem on the Working interface, or to remove and replace the Working card, if
necessary, without interfering with traffic.
Examples The following example shows switchover behavior being enabled on a Cisco CMTS in group 2:
Router(config)# interface c3/0
Router(config-if)# hccp 2 track
Router(config-if)# keepalive
Router(config-if)#
The following example shows two Cisco uBR-LCP2-MC28C cards being used in a Cisco uBR10012
router, with each downstream being configured for a separate HCCP group. The card in slot 5/1 is being
configured as the Working interfaces and the card in slot 6/1 is being configured as the Protect interfaces.
The two downstreams on each card track each other, so if one downstream fails and switches over, the
other can do so as well, allowing the Protect card to assume full control of both interfaces. Similarly,
when the Working interfaces come back into service, both Protect interfaces switch back at the same
time.
Router(config)# interface cable c5/1/0
Router(config-if)# hccp 1 working 1
Router(config-if)# hccp 1 track c5/1/1
Router(config-if)# keepalive 3
Router(config-if)# exit
Router(config)# interface cable c5/1/1
Router(config-if)# hccp 2 working 1
Router(config-if)# hccp 2 track c5/1/0
Router(config-if)# keepalive 3
Router(config-if)# exit
Router(config)# interface cable c6/1/0
Router(config-if)# hccp 1 protect 1 ip-address-of-mgmt-lan
Router(config-if)# hccp 1 track c6/1/1
Router(config-if)# keepalive 3
Router(config-if)# exit
Router(config)# interface cable c6/1/1
Router(config-if)# hccp 2 protect 1 ip-address-of-mgmt-lan
Router(config-if)# hccp 2 track c6/1/0
Router(config-if)# keepalive 3
Router(config-if)#
hccp unlockout
To reverse the effects of the hccp lockout command—that is, to make a Working CMTS available for
automatic switchover to Protect CMTS, use the hccp unlockout command in privileged EXEC mode.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
member The member number within the specified group.
Command Default By default, the hccp unlockout command is active for all groups and members.
Usage Guidelines This command reverses the effect of the hccp lockout command. Once you have reconfigured or tested
your Protect CMTS, issuing this command manually reintroduces the CMTS back into your 1+1
redundancy protection scheme.
Note This command is applicable only on a Working CMTS in a given group. Issuing this command on a
Protect CMTS has no effect.
Examples The following example shows the lockout feature of a Working CMTS in group 1 being deactivated:
hccp 1 unlockout
hccp working
To designate a cable interface on a CMTS in the specified group to be a Working CMTS, use the hccp
working command in cable interface configuration mode. To remove a Working CMTS assignment, use
the no form of this command.
Syntax Description group The group number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
member The member number for the specified interface. Valid values are any number
from 1 to 255, inclusive.
Usage Guidelines When N+1 HCCP redundancy is configured, the Protect interface switches over and becomes the active
interface when it detects a situation similar to the following:
• The Working interface is removed from the chassis, is powered down, or is reset
• The Working interface crashes
• The Working interface no longer sends out regular keepalive messages
• The Working interface loses connectivity with the cable network
The Protect cable interface must be configured identically to the Working cable interface, which
typically means the interfaces should be the same card type. However, when the Cisco uBR-MC16S is
used, it can be used with either another Cisco uBR-MC16S card or a Cisco uBR-MC16C card.
Table 25 shows how a switchover affects the enhanced spectrum management features of the
Cisco uBR-MC16S card.
Examples The following example shows cable interface 4/0 being designated as a Working CMTS interface as
member number 2 of group 2:
Router(config)# interface cable 4/0
Router(config-if)# hccp 2 working 2
hold-queue
To limit the size of the IP output queue on an interface, use the hold-queue command in interface
configuration mode. To restore the default values, use the no form of this command.
Syntax Description length Integer that specifies the maximum number of packets in the queue. The range of
valid values is from 0 to 65535.
in Specifies the input queue. The default is 75 packets. For asynchronous interfaces,
the default is 10 packets.
out Specifies the output queue. The default is 40 packets. For asynchronous interfaces,
the default is 10 packets.
Caution Increasing the hold queue can have detrimental effects on network routing and response times. For
protocols that use seq/ack packets to determine round-trip times, do not increase the output queue.
Dropping packets instead informs hosts to slow down transmissions to match available bandwidth.
This is generally better than having duplicate copies of the same packet within the network (which can
happen with large hold queues).
Examples The following example shows how to set a small input queue on a slow serial line:
Router(config)# interface serial 0
Router(config-if)# hold-queue 30 in
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0
is always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
Usage Guidelines The hw-module bay reload command reloads the software and restarts a SPA.
Examples The following example shows how to reload the software for the Cisco Wideband SPA in slot 1, subslot
0, and bay 1.
Router# hw-module bay 1/0/1 reload
Router#
Usage Guidelines Before using this command, you must use the hw-module slot image global configuration command to
specify a high availability Cisco IOS image to run on the standby RSP. After the high availability image
is loaded in the active RSP, use the hw-module sec-cpu reset command to reset and reload the standby
RSP with the specified Cisco IOS image and to execute the image. To load the standby RSP with the
default micro-IOS software contained in the active RSP image instead of a high availability Cisco IOS
image, use the no form of the hw-module slot image command followed by the hw-module sec-cpu
reset command.
Examples The following example shows a Cisco 7513 router with the standby RSP loaded in slot 7. The standby
RSP is reset and reloaded with the rsp-pv-mz high availability Cisco IOS image. Both RSPs have slot 0
flash memory cards.
Router(config)# hw-module slot 7 image slot0:rsp-pv-mz
Router(config)# end
Router# hw-module sec-cpu reset
Syntax Description main-cpu Shuts down the PRE1 module that is currently acting as the active PRE1
module.
pre {A|B} Shuts down the PRE1 module that is physically in either PRE slot A (left
slot) or PRE slot B (right slot).
sec-cpu Shuts down the PRE1 module that is currently acting as the standby PRE1
module.
slot slot-number Shuts down the line cards that are physically present in the specified
slot-number (valid range is 1 to 8).
subslot slot/subslot Shuts down the line card or SIP that is physically present in the slot with the
specified slot and subslot numbers. The following are the valid values:
• slot = 1 to 8
• subslot = 0 or 1
bay slot/subslot/bay Shuts down the SPA in the location specified by the slot/subslot/bay
argument. The following are the valid values:
• slot = 1 to 3
• subslot = 0 or 1 (0 is always specified)
• bay = 0 (upper bay) or 1 (lower bay)
unpowered Used with the Wideband SPA, shuts down the SPA and its interfaces, and
leaves them in an administratively down state without power.
Usage Guidelines The hw-module shutdown (ubr10012) command shuts down in a controlled manner a particular
Performance Routing Engine (PRE1) module, line card, Wideband SIP or Wideband SPA. To activate a
specific PRE1, line card, Wideband SIP, or Wideband SPA, use the no form of this command.
Caution Shutting down the active PRE1 module will trigger a switchover, so that the standby PRE1 module
becomes the active PRE1 module.
Examples The following example shows the standby PRE1 module being shut down:
Router(config)# hw-module sec-cpu shutdown
Router(config)#
The following example shows the active PRE1 module being shut down (which will trigger a switchover
to the standby PRE1 module):
Router(config)# hw-module main-cpu shutdown
Router(config)#
The following example shows the PRE1 module in PRE1 slot B being shut down:
Router(config)# hw-module pre B shutdown
Router(config)#
Note The hw-module pre B shutdown command shuts down the PRE1 module that is physically present in
slot B, regardless of whether the module is the active or standby PRE1 module.
The following example shows how to deactivate and verify deactivation for the Cisco Wideband SPA
located in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the
“admin down” in the Operational Status field.
Router# configure terminal
Router(config)# hw-module bay 1/0/0 shutdown unpowered
%SPAWBCMTS-4-SFP_MISSING: Wideband-Cable 1/0/0, 1000BASE-SX SFP missing from port 0
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:1, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:2, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:3, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:4, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:5, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:6, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:7, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:8, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:9, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:10, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:11, changed state to down
...
Router# show hw-module bay 1/0/0 oir
The following example shows how to activate and verify activation for the Cisco Wideband SPA located
in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the “ok” in
the Operational Status field.
Router# configure terminal
Router(config)# no hw-module bay 1/0/0 shutdown
Syntax Description slot-number Resets the line cards that are physically present in the specified slot-number
(valid range is 1 to 8).
Usage Guidelines You must first use the hw-module slot pos command to preconfigure a line card slot for POS operation
of the Cisco uBR10012 OC-48 DPT card before you can configure the card with any further commands.
You must also use the card 1oc48dpt/pos-1 command to configure the card slot for the proper card type.
Note If you have previously used the hw-module slot srp command to configure line card slots for Spatial
Reuse Protocol (SRP) operation, you must first cancel that configuration using the no hw-module slot
srp command before you can configure the slots for POS operation using the hw-module slot pos
command.
Examples The following example shows the Cisco uBR10012 OC-48 DPT line card in slot 3 being configured for
POS operation:
Router# hw-module slot 3 pos
Router# card 3/0 1oc48dpt/pos-1
The following example shows the Cisco uBR10012 OC-48 DPT line cards in slots 3 and 4 being
reconfigured from SRP operation to POS operation:
Router# no hw-module slot 3 srp
Router# no hw-module slot 4 srp
Router# hw-module slot 3 pos
Router# card 3/0 1oc48dpt/pos-1
Router# hw-module slot 4 pos
Syntax Description slot-number Resets the line cards that are physically present in the specified slot-number
(valid range is 1 to 8).
Usage Guidelines You must first use the hw-module slot srp command to preconfigure a line card slot for SRP operation
of a pair of Cisco uBR10012 OC-48 DPT cards before you can configure the cards with any further
commands. You must also use the card 1oc48dpt/pos-1 command to configure each card slot for the
proper card type.
Tip The Cisco uBR10012 OC-48 DPT line cards support SRP operation only when installed in adjacent odd-
and even-numbered slots (such as slots 1 and 2 or 3 and 4). You need to use the hw-module slot srp
command only for the lower-numbered (odd-numbered) slot to preconfigure both slots of the SRP pair.
Note If you have previously used the hw-module slot pos command to configure line card slots for Packet
over SONET (POS) operation, you must first cancel that configuration using the no hw-module slot pos
command before you can configure the slots for POS operation using the hw-module slot srp command.
Examples The following example shows the Cisco uBR10012 OC-48 DPT line cards in slots 1 and 2 being
configured for POS operation:
Router# hw-module slot 1 srp
Router# card 1/0 1oc48dpt/pos-1
Router# card 2/0 1oc48dpt/pos-1
The following example shows the Cisco uBR10012 OC-48 DPT line cards in slots 3 and 4 being
reconfigured from POS operation to SRP operation:
Router# no hw-module slot 3 pos
Router# no hw-module slot 4 pos
Router# hw-module slot 3 srp
Router# card 3/0 1oc48dpt/pos-1
Router# card 4/0 1oc48dpt/pos-1
New Commands
Modified Commands
init-tech-list
To set the DCC initialization techniques that the CMTS can use to load balancing cable modems, use the
init-tech-list command in the config-lb-group configuration mode. To reset the DCC initialization
techniques, use the no form of this command.
no init-tech-list
Examples The following example shows how to set the DCC initialization techniques on a DOCSIS load balancing
group on the CMTS, using the init-tech-list command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# init-tech-list 1 ucc
Router(config-lb-group)#
init-tech-ovr
To set DCC initialization techniques that override the physical upstream channel pair, use the
init-tech-ovr command in the config-lb-group configuration mode.
init-tech-ovr cable slot/port upstream cable slot/port upstream init-tech-list 0-4 [ucc]
Syntax Description cable slot/subslot/port Specifies the CMTS interface slot, subslot, port number, and upstream
upstream parameters that are to be overridden.
• slot—Slot where the line card resides. Ther permitted range is from 5 to
8.
• subslot—Subslot where the line card resides. The available slots are 0 or
1.
• port—The downstream controller number on the line card. The
permitted port range is from 0 to 4.
cable slot/subslot/port Specifies the CMTS interface slot, subslot, port number, and upstream
upstream channel ID parameters that will override the CMTS interface and upstream
channel.
cable slot/port Specifies the CMTS interface slot, port number, and upstream parameters
upstream that are to be overridden.
• slot—Slot where the line card resides.
– Cisco uBR7225VXR router—The valid range is from 1 to 2.
– Cisco uBR7246VXR router—The valid range is from 3 to 6.
• port—Downstream controller number on the line card. The permitted
port values are 0 or 1.
cable slot/port Specifies the CMTS interface slot, port number, and upstream parameters
upstream that will override the CMTS interface and upstream channel.
init-tech-list 0-4 Specifies the DCC initialization technique list ranging from 0 to 4 for the
upstream channel pair.
ucc Determines whether Upstream Channel Change (UCC) can be used for
modems during dynamic upstream load balancing.
Usage Guidelines The init-tech-list command accepts an upstream that is not added into the load balancing group. The
upstream channel pair is invalid until the upstream is added. When the load balancing group is removed,
all upstream channel pairs are also removed.
Examples The following example shows how to set DCC initialization techniques that override the physical
upstream channel pair to a DOCSIS load balancing group on the CMTS, using the init-tech-ovr
command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# init-tech-ovr cable 1/0 1 cable 1/1 2 1
interface cable
To configure a cable interface, use the interface cable command in global configuration mode.
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 terminal
Router(config)# interface cable 8/0/0
The following example shows how to configure a cable interface in slot 5, and port 0 on a
Cisco uBR7246VXR or Cisco uBR7225VXR router:
Router# configure terminal
Router(config)# interface cable 5/0
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
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 0
Router(config-if)# cable-modem ?
compliant Enter compliant modes for interface
downstream Downstream channel characteristics
fast-search Enable/disable the DS fast search
upstream upstream channel characteristics
voip Options for Voice over IP traffic over the cable interface
Router(config-if)#
cable-modem upstream Enables the QPSK modulation scheme in the upstream direction
preamble qpsk from the cable interface to the CMTS.
cable-modem voip best-effort Allows voice traffic to be transmitted on the upstream using a
best-effort QoS.
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.
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and 3
can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0 is
always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the interface number on the SPA.
nb-channel-number Represents the narrowband channel number.
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 terminal
Router(config)# interface modular-cable 1/0/0:0
Related Commands
Command Description
cable attribute-mask Specifies an attribute mask value for a modular cable interface.
interface Specifies a wideband cable interface.
wideband-cable
interface cable Specifies a cable interface.
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.
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 1
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
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
Router(config-if)#
interface wideband-cable
To configure a wideband cable interface, use the interface wideband-cable command in global
configuration mode.
Syntax Description slot The slot where a SIP or line card resides.
Cisco uBR7246VXR router—The valid range is from 3 to 6.
Cisco uBR7225VXR router—The valid range is from 1 to 2.
Cisco uBR10012 router—The valid range is from 5 to 8, and slots 1 and 3
can be used for SIP.
subslot The subslot where a SIP or line card resides. On the Cisco uBR10012 router,
subslot 0 is always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay) and
1 (lower bay).
port Specifies the port number.
Cisco uBR7246VXR router and Cisco uBR7225VXR router—The valid
range is from 0 to 1.
Cisco uBR10012 router—The valid range is from 0 to 4 (depending on the
cable interface).
wideband-channel Represents the wideband channel number. The valid range is from 0 to 11.
On the Cisco uBR7246VXR and Cisco uBR7225VXR routers, the valid
values are from 0 to 5.
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 terminal
Router(config)# interface wideband-cable 1/0/0:0
The following example shows how to configure a wideband cable interface in slot 1, and port 0 on a
Cisco uBR7225VXR or Cisco uBR7246VXR router:
Router# configure terminal
Router(config)# interface wideband-cable 1/0:0
interval
To set the duration of time the CMTS waits before checking the load on an interface, use the
init-tech-list command in the config-lb-group configuration mode. To reset the duration of time, use the
no form of this command.
interval 1-1000
no interval
Syntax Description 1-1000 Specifies the interface polling interval for the CMTS, ranging from 1 to 1000
seconds
Examples The following example shows how to set the duration of time that the CMTS waits before checking the
load on the interface, using the interval command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# interval 20
Router(config-lb-group)#
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
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/0
Router(config-controller)# ip-address 192.168.200.6
Command Description
rf-channel description Specifies the description for each RF channel.
rf-channel cable downstream channel-id Assigns a downstream channel ID to an RF channel.
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.
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
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/0
ip accounting mac-address input
ip accounting mac-address output
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.
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 Earlier Cisco IOS software releases for the cable access routers used either the ip address negotiated
or the ip address dhcp command to specify that the cable interface should obtain its IP address from a
DHCP server. These commands should no longer be used to configure the router’s cable interface.
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 0
Router(config-if)# ip address docsis
Router(config-if)# exit
Router(config)#
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.
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:
• Filtering Cable DHCP Lease Queries on the Cisco CMTS
• DHCP and Time-of-Day Services on the Cisco CMTS
Examples The following example of the show version command illustrates configuration of this feature on the
Cisco CMTS:
version 12.1
no service pad
! provides nice timestamps on all log messages
service timestamps debug datetime msec localtime
service timestamps log uptime
!
hostname Router
!
boot system disk0:
!
no cable qos permission create
no cable qos permission update
cable qos permission modems
!
! 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.cm
service-class 1 max-upstream 128
service-class 1 guaranteed-upstream 10
service-class 1 max-downstream 10000
service-class 1 max-burst 1600
cpe max 8
timestamp
!
! Medium performance DOCSIS config file, additional options may be added
! 5 Mbit/sec download, 128 Kbit/sec upload speed
!
cable config-file gold.cm
service-class 1 max-upstream 64
service-class 1 max-downstream 5000
service-class 1 max-burst 1600
cpe max 3
timestamp
!
! Low performance DOCSIS config file, additional options may be added
! 1 Mbit/sec download, 64 Kbit/sec upload speed
!
cable config-file silver.cm
service-class 1 max-upstream 64
service-class 1 max-downstream 1000
service-class 1 max-burst 1600
cpe max 1
timestamp
!
! 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.cm
access-denied
service-class 1 max-upstream 1
service-class 1 max-downstream 1
service-class 1 max-burst 1600
cpe max 1
timestamp
!
ip subnet-zero
! Turn on cef switching / routing, anything but process switching (no ip route-cache)
ip cef
ip cef accounting per-prefix
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 name The name can be either an arbitrary string, such as service, or a number, such as 1.
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:
• Filtering Cable DHCP Lease Queries on the Cisco CMTS
• DHCP and Time-of-Day Services on the Cisco CMTS
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-platinum
network 10.128.4.0 255.255.255.0
bootfile platinum.cm
next-server 10.128.4.1
default-router 10.128.4.1
option 2 hex ffff.8f80
option 4 ip 10.1.4.1
option 7 ip 10.1.4.1
lease 7 0 10
!
ip dhcp pool cm-gold
network 10.129.4.0 255.255.255.0
bootfile gold.cm
next-server 10.129.4.1
default-router 10.129.4.1
option 2 hex ffff.8f80
option 4 ip 10.1.4.1
option 7 ip 10.1.4.1
lease 7 0 10
!
ip dhcp pool cm-silver
network 10.130.4.0 255.255.255.0
bootfile silver.cm
next-server 10.130.4.1
default-router 10.130.4.1
option 2 hex ffff.8f80
option 4 ip 10.1.4.1
option 7 ip 10.1.4.1
lease 7 0 10
!
ip dhcp pool DisabledModem(0010.aaaa.0001)
host 10.128.1.9 255.255.255.0
client-identifier 0100.10aa.aa00.01
bootfile disable.cm
!
ip dhcp pool DisabledModem(0020.bbbb.0002)
host 10.128.1.10 255.255.255.0
client-identifier 0100.20bb.bb00.02
bootfile disable.cm
!
ip dhcp pool DisabledModem(1010.9581.7f66)
host 10.128.1.11 255.255.255.0
client-identifier 0100.1095.817f.66
bootfile disable.cm
!
ip dhcp pool hosts
network 10.254.1.0 255.255.255.0
default-router 10.254.1.1
dns-server 10.254.1.1 10.128.1.1
domain-name ExamplesDomainName.com
lease 7 0 10
!
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 terminal
Router(config)# ip dhcp relay information option
Command Description
cable relay-agent-option Enables the system to insert the CM MAC address into a DHCP
packet received from a CM or host and forward the packet to a DHCP
server.
cable source-verify Turns on CM upstream verification.
cable telco-return spd Enforces the telco-return CM to use a specific Dynamic Host
dhcp-authenticate Configuration Protocol (DHCP) server.
cable telco-return spd Identifies the IP address of the Dynamic Host Configuration Protocol
dhcp-server (DHCP) server that the telco-return CM must access.
ip dhcp smart-relay Monitors client retransmissions when the IP DHCP address pool
depletion occurs.
ipdr type
To configure the IPDR session type, use the ipdr type command in global configuration mode. The
IPDR session types that can be defined using this command are event type, time-interval type, and the
ad hoc type.
Use the no form of the command to reset the session type to the default "event" type.
Syntax
Description session id IPDR session ID. Range is from 1 to 255.
ad-hoc The ad hoc session type.
event The event session type.
time-interval value The time-interval session type. Interval range is from 15 to 1440 minutes.
Usage Guidelines This command allows the user to define the specific IPDR session type.
Note Once the IPDR session type is configured, the templates supported by this IPDR type are automatically
associated with it.
Examples The following example shows how to configure the IPDR “time-interval” session type for a time interval
of 15 minutes.
Router> enable
Router# configure terminal
Router(config)# ipdr type 1 time-interval 15
Related Commands
Command Description
cable ipdr Displays a cable modem’s upstream channel status information.
cm-us-status interval
cable ipdr Sets the interval between different spectrum measurements’ data for a
docs-spectrum CMTS.
interval
cable ipdr diaglog Sets the time interval between different diagnostic logs’ data for a CMTS.
interval
cable ipdr cm-status Displays the CMTS and cable modem registration status information.
interval
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
no ip http cable-monitor
Syntax Description basic Displays only the basic status and performance pages.
advance Displays all status and diagnostic pages.
Note The Cable Monitor should not be used in advanced mode without
first implementing a secure password strategy on the cable access
router. Enabling the Cable Monitor in advanced mode without
setting an encrypted enabled password could provide information
that would allow remote users to change the router’s configuration.
url-ip-address (Optional) Specifies the IP address for the Cable Monitor. This argument,
along with the url-mask argument, also defines the network that provides
the IP address pool used by the temporary DHCP server when the cable
interface goes down.
url-mask (Optional) Specifies the subnet mask for the Cable Monitor. This argument,
along with the url-ip-address argument, also defines the network that
provides the IP address pool used by the temporary DHCP server when the
cable interface goes down.
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:
• When the cable access router has established connectivity with the CMTS over the cable interface,
a service technician can use a web browser to remotely access the router and display the desired
information.
• When the cable network is not operational and the cable access router is not online, the subscriber
can access the tool with a PC connected to the router’s Ethernet ports. Technicians can then prompt
the user for the information they need to determine the source of the problem.
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 When the Cable Monitor is enabled in the startup configuration file, the messages “Starting DNS
process” and “Terminating DNS process” can appear in the messages displayed during boot-up on the
console. These messages are normal and can be ignored.
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 The Cable Monitor web interface does not work with the Cisco Easy VPN Remote web interface. To
access the Cable Monitor web interface, you must first disable the Cisco Easy VPN Remote web
interface with the no ip http ezvpn command, and then enable the Cable Monitor with the ip http
cable-monitor command.
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 advance
Router(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-monitor
Router(config)#
Note The ip http command also supports two options, access-class and authentication, that should not be
used when the Cable Monitor is enabled.
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.
ip http ezvpn
no ip http ezvpn
Command Default The Cisco Easy VPN Remote web interface is disabled by default.
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 The Cisco Easy VPN Remote web interface does not work with the Cable Monitor web interface in
Cisco IOS Release 12.2(8)YJ. To access the Cable Monitor web interface, you must first disable the
Cisco Easy VPN Remote web interface with the no ip http ezvpn command, and then enable the Cable
Monitor with the ip http cable-monitor command.
Examples The following example shows how to enable the Cisco Easy VPN Remote web server interface:
Router# configure terminal
Router(config)# ip http server
Router(config)# ip http ezvpn
Router(config)# exit
Router# copy running-config startup-config
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
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/0
Router(config-controller)# ip-address 192.168.200.6
Command Description
rf-channel network delay Specifies the CIN delay for each RF channel.
rf-channel description Specifies the description for each RF channel.
rf-channel cable downstream channel-id Assigns a downstream channel ID to an RF channel.
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.
Syntax
Description session_id The unique IPDR session ID.
collector_name The collector name. The name should not contain extra spaces.
priority The priority value between the session and the collector. The value range is
1 to 10. A value of 1 indicates that the highest priority.
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 The collector and the session should be configured before running this command.
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.
Syntax
Description collector_name The collector name. The name should not contain extra spaces.
ip_addr The collector IP address.
port (Optional) The collector port value. The default port number will be
considered if the value is not entered.
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.
Command Default By default, the IPDR exporter process will not be started.
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 terminal
Router(config)#ipdr exporter start
ipdr session
To start or stop a specific session, use the ipdr session command in the privileged EXEC mode.
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 The user has to stop the session before configuring any tasks if the session is active.
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.
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 You can not update template details or other details when a session already created.
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.
Syntax
Description session_id The unique IPDR Session ID.
template_name The template name.
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 User can only add the system supported templates. The list can be viewed by entering a “?” at
the command prompt.
Note This command is used to abort or roll back the versions on redundant line cards only.
Syntax
Description all All redundant line cards.
lc_slot The line card slot number.
subslot The line card sub slot number.
forced (Optional) The ISSU would ignore potential service outage and line card
incompatibility errors and proceed with abortversion instead of stopping and
error handling.
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 issu linecard reloadversion command is used to reload a line card with the original version
of images.
The following example aborts the specific redundant line card’s image version.
Router# configure terminal
Router(config)#issu linecard abortversion
Command Description
issu linecard reloadversion Reloads the new loaded image on a working or a primary line
card.
issu linecard runversion Runs the new loaded image on a working or a primary line card.
issu linecard changeversion Starts the upgrade or downgrade activity of the image version for
a single line card or multiple line cards.
Syntax
Description lc_slot The line card slot number.
subslot The line card sub slot number.
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 terminal
Router(config)#issu linecard acceptversion 7/0
Syntax
Description all All redundant line cards.
slot_1 The slot number for the first line card.
subslot_1 The sub slot number for the first line card.
slot_n The slot number for the nth line card.
subslot_n The sub slot number for the nth line card.
forced (Optional) The ISSU would ignore potential service outage and line card
incompatibility errors and proceed with changeversion instead of
stopping and error handling.
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 terminal
Router(config)#issu linecard changeversion all
The following example displays the command and uses the slot value of 6.
Router# configure terminal
Router(config)#issu linecard changeversion 6/0
Related Commands
Command Description
issu linecard abortversion Rolls back to the prior image on working/primary line card.
issu linecard acceptversion Accepts the new image version on the working line card.
issu linecard loadversion Loads a specific image version on the primary line card.
issu linecard prepareversion Determines if the image version on the line card has to be
upgraded or downgraded to the route processor’s image version.
issu linecard reloadversion Reloads the new loaded image on a working or a primary line card.
issu linecard runversion Runs the new loaded image on a working or a primary line card.
Syntax
Description slot The line card slot number.
subslot The line card sub slot number.
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 terminal
Router(config)#issu linecard loadversion 7/0
Syntax
Description lc_slot The line card slot number.
subslot The line card sub slot number.
forced (Optional) The ISSU would ignore potential service outage and line card
incompatibility errors and proceed with prepareversion instead of stopping
and error handling.
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 terminal
Router(config)#issu linecard prepareversion 7/0
Command Description
issu linecard runversion Runs the new loaded image on a working or a primary line card.
issu linecard changeversion Starts the upgrade or downgrade activity of the image version for
a single line card or multiple line cards.
Syntax
Description original The original image version.
all All redundant line cards.
slot_1 The slot number for the first line card.
subslot_1 The sub slot number for the first line card.
slot_n The slot number for the nth line card.
subslot_n The sub slot number for the nth line card.
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.
• Line cards that are not configured with redundancy, and do not support Minimal Disruptive Restart
(MDR.)
• Line cards which are capable of line card redundancy which were rolled back due to an unsuccessful
changeversion command.
Examples The following example shows the command executed with the original keyword.
Router# configure terminal
Router(config)#issu linecard reloadversion original 8/0
The following example shows the command executed with the target keyword.
Router# configure terminal
Router(config)#issu linecard reloadversion target 8/0
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 terminal
Router(config)#issu linecard runversion 7/0
Syntax Description syslog-level level (Optional) Configures the level of syslog messages inclusive of and above
the specified level which will be stored in the SEA log file.
Possible values for level Emergency security level indicates system is unusable. The default severity
are: level for emergency syslog messages is 0.
level=emergencies
level=alerts Alerts severity level indicates that immediate action is needed. The default
severity level for alerts syslog messages is 1.
level=critical Critical severity level indicates the critical condition of the system. The
default severity level for critical syslog messages is 2.
level=errors Errors severity level indicates the error conditions. The default severity
level for errors syslog messages is 3.
level=warnings Warning severity level warns the network administrator. The severity level
for warning syslog messages is 4.
level=notifications Notification severity level indicates normal but significant condition of the
system. By default severity level for syslog messages is configured as
‘normal’. The default severity level for notification syslog messages is 5.
level=informational Informational severity level provides additional information about the
system. The default severity level for informational syslog messages is 6.
level=debugging Debugging severity level provides debugging messages. The default
severity level for debugging syslog messages is 7.
Command Default By default, storing of syslog messages to SEA log file is enabled, with the severity-level of syslog
messages being set to ‘notification’.
Usage Guidelines Use the logging cmts sea command is used to enable the logging of syslog messages to SEA log file. To
change the severity-level of syslog messages inclusive of and above the level to be stored in SEA log
file, specify the command logging cmts sea [syslog-level level].
Examples The following example shows how to enable logging of syslog messages to SEA log file on the Cisco
uBR10012 router:
Router(config)# logging cmts sea
The following example shows how to disable logging of syslog messages to SEA log file on the Cisco
uBR10012 router:
Router(config)# no logging cmts sea
The following example shows how to change the severity-level of syslog messages inclusive of and
above the level being stored in the SEA log file:
Router(config)# logging cmts sea syslog-level warning
Related Commands clear logging system Clears the event records stored in the SEA.
copy logging system Copies the archived system events to another location.
logging system Enables or disables the SEA logging system.
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 ieee-address 48-bit IEEE MAC address written as a dotted triple of four-digit
hexadecimal numbers.
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).
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 0
mac-address 5000.5axx.xxxx
The 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
Command Description
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
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 t
Router(config)# redundancy
Router(config-r)# main-cpu
Router(config-r-mc)# ?
Router(config-r-mc)#
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
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 The maintenance-mode command disables the ability of the Cisco uBR10012 router to switchover
PRE1 modules and should be used only while upgrading the router or troubleshooting network problems.
Examples The following example shows how to disable the automatic PRE1 module synchronization on the
Cisco uBR10012 router and enter maintenance mode:
Router# config t
Router(config)# redundancy
Router(config-r)# maintenance-mode
Router(config-r)# exit
Router(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 t
Router(config)# redundancy
Router(config-r)# no maintenance-mode
Router(config-r)# exit
Router(config)#
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]
Syntax Description match rule [ipv4 | ipv6] Specifies the matching source rule.
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 rule1
member subslot
To configure the redundancy role of a line card, use the member subslot command in line card
redundancy group mode.
Note Use the revertive command in line card redundancy group mode to
enable the revert operation on a protect card in Cisco IOS Release
12.2(33)SCA and later.
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 terminal
Router(config)# redundancy
Router(config-red)# linecard-group 1 y-cable
Router(config-red-lc)# member subslot 2/1 primary
Router(config-red-lc)# member subslot 2/0 secondary
method
To select the method the CMTS uses to determine the load, use the method command in the
config-lb-group configuration mode. To reset the method, use the no form of this command.
no method
Syntax Description modems Specifies the load balancing method for the number of modems on the
CMTS.
service-flows Specifies the load balancing method for the number of service flows on the
CMTS.
utilization Specifies the load balancing method for the interface utilization on the
CMTS.
us-method {modems | Specifies the load balancing method for upstream (US) channels on modems,
service-flows | service-flows, or utilization.
utilization}
Usage Guidelines The upstream channel uses the same method as the downstream channel. Change the method of the
upstream channel using the method command.
Examples The following example shows how to select the method the CMTS uses to determine the load, using the
method command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# method modems us-method service-flows
Router(config-lb-group)#
Related Commands
Command Description
cable load-balance Configures a DOCSIS load balancing group on the CMTS.
docsis-group
show cable Displays real-time configuration, statistical, and operational information
load-balance for load balancing operations on the router.
docsis-group
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.
Syntax Description pxf Reloads the microcode for the PXF processors on the Performance Routing
Engine (PRE1) module.
filename Specifies the microcode software image for the PXF processors by device
name and filename.
reload Reloads the microcode for all PRE1 modules and other line cards that
support downloadable microcode software images.
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 You can also reload the microcode on the PXF processors or on all cards using the microcode reload
command in privileged EXEC mode. In particular, use the microcode reload command to reload the
PXF processors with the default microcode that was loaded along with the Cisco IOS software image.
Examples The following example shows how to reload the microcode on all PRE processors and line cards that
support downloadable microcode:
Router# configure terminal
Router(config)# microcode reload
Reload microcode? [confirm] yes
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 terminal
Router(config)# microcode pxf flash:pxf/ubr10k-ucode.122.1.2.3
Reload microcode? [confirm] yes
Router(config)#
Syntax Description all Reloads the microcode for all Performance Routing Engine (PRE1)
modules and other line cards that support downloadable microcode
software images.
pxf Reloads the microcode for the Parallel eXpress Forwarding (PXF)
processors on the PRE1 module.
device:[filename] (Optional) Loads the PXF processors with the microcode software image
that has the specific filename on the specific device. If no filename is
specified, the first image found on the device is loaded by default.
Command Default For microcode reload pxf, defaults to loading the microcode image that was originally loaded when the
Cisco IOS software image was loaded.
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 You can also reload the microcode on the PXF processors or on all cards using the microcode command
in global configuration mode.
Examples The following example shows how to reload the microcode on all PRE processors and line cards that
support downloadable microcode:
Router# microcode reload all
Reload microcode? [confirm] yes
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 ?
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.4
Reload microcode? [confirm] yes
Router#
mode (redundancy)
To configure the redundancy mode of operation, use the mode command in redundancy configuration
mode.
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.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA.
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-plus
The following example sets the mode to HSA on a Cisco 7500 series router:
Router# mode hsa
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.
Command Default No modular-host line card is configured for DOCSIS 3.0 downstream or downstream channel bonding
operations.
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/0
Router(config-controller)# modular-host subslot 7/0
Command Description
rf-channel ip-address Sets the IP address, MAC address and UDP port for each RF channel.
mac-address udp-port
rf-channel network delay Specifies the CIN delay for each RF channel.
rf-channel description Specifies the description for each RF channel.
rf-channel cable downstream Assigns a downstream channel ID to an RF channel.
channel-id
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.
Syntax Description legacy Provides only one threshold and one monitoring duration.
peak-offpeak Allows the selection of two peak durations within a day.
docsis10 Specifies application of the enforce-rule to DOCSIS 1.0 cable modems.
docsis11 Specifies application of the enforce-rule to DOCSIS 1.1 cable modems.
Command Default The default for this command is legacy and docsis10.
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 docsis11
Command Description
duration Specifies the time period and sample rate to be used for monitoring
subscribers.
peak-time1 Specifies peak and offpeak monitoring times.
qos-profile registered Specifies the registered QoS profile that should be used for this enforce-rule.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate the
registered QoS profiles.
service-class Identifies a particular service class for cable modem monitoring in an
(enforce-rule) enforce-rule.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
monitoring-duration
Note Effective with Cisco IOS Release 12.3(9a)BC, the monitoring-duration command is replaced by the
duration command.
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.
no monitoring-duration
Syntax Description minutes Specifies the time (in minutes). The valid range is 10 to 10080, with a
default of 360 (6 hours).
sample-rate minutes (Optional) Rate of sampling, in minutes. The valid range is 1 to 30,
with a default value of 15.
Defaults The monitoring-duration value defaults to 360 minutes (6 hours), and the sample-rate value defaults
to 15 minutes.
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 The sample-rate interval must be less than or equal to the monitoring-duration period. If you attempt
to set the sample-rate interval to a value greater than the monitor-duration period, the command is
ignored and the parameters are unchanged.
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 terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# monitoring-duration 20 sample-interval 10
The 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 terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# monitoring-duration 20 sample-interval 30
Monitoring duration cannot be less than the Sampling interval -- so the values
would remain unchanged
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
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.
%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.
Note For the Gigabit Ethernet SPAs on the Cisco uBR10012 router, the default MTU size is 1500 bytes. When
the interface is being used as a Layer 2 port, the maximum configurable MTU is 9000 bytes. The SPA
automatically adds an additional 22 bytes to the configured MTU size to accommodate some of the
additional overhead.
name
To specify the name of the CMTS tag, use the name command in the cmts-tag configuration mode. To
remove the name, use the no form of this command.
name tag-name
no name tag-name
Syntax Description tag-name Name of the CMTS tag. The configured name is added to the DOCSIS load
balancing group and policies.
Examples The following example shows how to give name to a CMTS tag using the name command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# name cisco
negotiation
, use the negotiation command in interface configuration mode. To disable automatic negotiation, use
the no negotiation auto command.
no negotiation auto
Syntax Description forced Disables flow control and configures the Gigabit Ethernet interface in
1000/full-duplex mode.
This keyword is not supported on the 2-port 10/100/1000 Gigabit Ethernet
SPA on the Cisco 7304 router.
auto Enables the autonegotiation protocol to configure the speed, duplex, and
automatic flow control of the Gigabit Ethernet interface. This is the default.
Defaults auto
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.
Note Autonegotiation is not supported on the 1-Port 10-Gigabit Ethernet SPA in Cisco IOS Release
12.2(33)SCB.
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/1
Router(config-if)# media-type gbic
Router(config-if)# negotiation auto
The 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/1
Router(config-if)# no negotiation auto
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]
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 To create an address pool with a single IP address, use the host command instead of network.
For additional information about DHCP support on the Cisco CMTS, refer to the following document
on Cisco.com:
• DHCP and ToD Servers on the Cisco CMTS
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 ip dhcp pool name Creates a DHCP address pool and enters DHCP pool configuration file mode.
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]
Usage Guidelines It is recommended that NLS message authentication is enabled all the time.
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.
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.
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.
Examples The following example shows configuring the NLS response timeout:
Router(config)#nls rssp-timeout 35
oui
To configure the Organizational Unique Identifier (OUI) of the CM for the CMTS tag, use the oui
command in the cmts-tag configuration mode. To remove the configured OUI from the CMTS tag, use
the no form of this command.
no oui oui-of-CM
Syntax Description exclude (Optional) Configures the tag to exclude the specified OUI.
oui-of-CM MAC address prefix of the vendor.
Examples The following example shows how to configure the OUI for the CMTS tag using the oui command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# oui 00.1a.c3
output-rate
To specify a custom-defined output line rate to a WAN interface instead of the default output line rate,
use the output-rate command in interface configuration mode. Use the no form of this command to use
the default output line rate.
output-rate rate
no output-rate
Syntax Description rate Output rate to the WAN interface, in kilobits per second. Valid values range
from 1 to 1,000,000.
Usage Guidelines This command specifies a custom-defined output line rate for the WAN interface.
Examples The following example shows how to specify a custom-defined output line rate for the WAN interface:
Router# configure terminal
Router(config)# interface gigabitethernet 1/0/0
Router(config-if)# output-rate 100
override
To override the Type/Length/Value (TLV) or SNMP when assigning a restricted load balancing group
(RLBG) to CM, use the override command in the cmts-tag configuration mode. To reenable the TLV or
SNMP when assigning a RLBG to CM, use the no form of this command.
override
no override
Command Default TLV or SNMP are effective when assigning a RLBG to CM.
Examples The following example shows how to override the TLV or SNMP when assigning a RLBG using the
override command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# override
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.
no option n
Syntax Description n Specifies the configuration file option code. Valid range is 5 to 254.
Note Certain values between 5 and 254 are not allowed. See Table 0-27 for
more information.
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 The hex option must be used to specify the data in the DOCSIS
Type/Length/Value (TLV) format when using the vendor-specific
option (option 43).
ip ip-address Specifies an IP address.
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-27 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.
Table 0-27 Invalid Option Codes for the cable config-file option Command
Note For complete information on the other parameters and fields in DOCSIS configuration files, see
Appendix C in the DOCSIS 1.1 Radio Frequency (RF) Interface Specification, available on the DOCSIS
Cable Labs official web site at http://www.cablemodem.com/
Note Each option 43 command must specify one and only one vendor ID, and the vendor ID must be the first
TLV in the hex data string.
Note When using the option 43 command, you must manually calculate the length value for each TLV that
you specify in the hex data string. However, you do not have to calculate the length for entire option 43
command, because that is calculated automatically by the CMTS.
Caution Be certain that you have correctly entered the TLV data when using the hex option. Incorrectly entered
data could cause CMs to reset, go offline, or hang, requiring a power cycle before being able to continue.
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.cm
router(config-file)# option 43 hex 08:03:00:00:0C:01:04:05:7F:9F:90
router(config-file)# exit
router(config)#
The hexadecimal data shown in this command consists of the two TLVs shown in Table 0-28:
Note Both the Cisco vendor-specific option for a static downstream frequency and the frequency command
instruct the CM to move to a specific downstream frequency, overriding the frequency the CM found
during its initial downstream scanning. However, the vendor-specific option requires the CM to use the
specified frequency—if the CM loses its lock on that frequency or can never lock on to that specific
frequency, the CM cannot go online. In contrast, the frequency command allows the CM to scan the
downstream for the next available frequency if the CM loses its lock on the originally specified
frequency.
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.cm
router(config-file)# option 43 hex 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67:0A:01:02
router(config-file)# exit
router(config)#
The hexadecimal data shown in this command consists of the three TLVs shown in Table 0-29:
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:65
router(config-file)#
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:90
router(config-file)# option 43 instance 2 hex 08:03:00:00:0C:80:07:69:6F:73:2E:63:66:67:
0A:01:02
router(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:65
router(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 manually
router(config-file)# option 9 ascii newsoftware.file
%Option 9 must be specified directly (not as raw option)
router(config-file)#
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
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 PacketCable operations can be configured together with HCCP N+1 redundancy, but the PacketCable
states are not synchronized between the Working and Protect interfaces. If a switchover occurs, existing
voice calls continue, but when the user hangs up, PacketCable event messages are not generated because
the Protect interface is not aware of the previous call states. However, new voice calls can be made and
proceed in the normal fashion.
Command Default Non-PacketCable UGS service flows are not allowed when PacketCable operations are enabled.
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 terminal
Router(config)# packetcable
Router(config)# packetcable authorize vanilla-docsis-mta
Router(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 global
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.
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 terminal
Router(config)# packetcable element-id 12456
Pktcbl: Configured element ID 12456
Router(config)#
Syntax Description n Maximum number of gate IDs to be allocated in the gate database on the
CMTS. The valid range is 512 through 2097152, with a default value of
2097152 (8 * 512 * 512), which is sufficient to support 8 cable interface line
cards.
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 Each cable interface line card supports a maximum of 512*512 (262,144) PacketCable gates, so ensure
that you set the maximum number of gates to accommodate all installed cable interface line cards.
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 terminal
Router(config)# packetcable gate maxcount 524288
Router(config)#
Command Default No subscriber identification information is provided in the GATE-OPEN and GATE-CLOSE gate control
messages.
Examples The following example enables gate control subscriber identification information using the packetcable
gate send-subscriberID command:
Router(config)# packetcable gate send-subscriberID
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.
Syntax Description hour | hour:minutes Specifies the time of day, in either hh or hh:mm format, during which
monitoring occurs for the peak time.
If the time is specified in hour (hh), the valid range is 1 to 23 using a 24-hour
clock.
If the time is specified in hour:minutes (hh:mm), the valid range for hour is
1 to 23 using a 24-hour clock, and the valid range for minutes is 0 to 59.
duration minutes Specifies the size of the sliding window (in minutes) during which the
subscriber usage is monitored for the first peak time, and optionally for a
second peak time when used with the peak-time2 keyword. The valid range
is 60 to 1440.
avg-rate rate Specifies the average sampling rate in kilobits per second for the specified
duration. The valid range is 1 to 400000 kilobits with no default.
duration (Optional) Specifies the size of the sliding window (in minutes) during
offpeak-minutes which the subscriber usage is monitored for the remaining offpeak time
(time not specified for peak monitoring). The valid range is 60 to 1440.
avg-rate offpeak-rate Specifies the average sampling rate in kilobits per second for the specified
offpeak duration. The valid range is 1 to 400000 kilobits with no default.
peak-time2 hour | (Optional) Specifies the time of day during which monitoring occurs for a
hour:minutes second peak time. The time can be specified either in hour or hour:minutes
format. The valid range for hour is 1 to 23 using a 24-hour clock, and the
valid range for minutes is 0 to 59.
sample-interval Specifies how often (in minutes) the CMTS router should sample a service
minutes flow to get an estimate of subscriber usage. The valid range is 1 to 30, with
a default value of 15.
penalty minutes (Optional) Specifies the period (in minutes) during which a cable modem can
be under penalty. The valid range is 1 to 10080.
downstream Specifies monitoring of traffic in the downstream direction.
upstream Specifies monitoring of traffic in the upstream direction.
enforce (Optional) Specifies that the enforce-rule QoS profile should be applied
automatically if a user violates their registered QoS profile.
Command Default Peak and offpeak monitoring is disabled. The only default value for the peak-time1 command is the
15-minute sample interval.
Usage Guidelines
Note This command is applicable only after the monitoring-basics command is configured with the keyword
peak-offpeak.
You can monitor two peak monitoring periods using the initial peak-time1 command and its options,
followed by the peak-time2 keyword and the corresponding options. The remaining hours are
considered offpeak and can be monitored by configuring the optional duration keyword and the
corresponding options.
The penalty duration, which is configured using the peak-time1 command, is unique to weekdays, and
takes precedence over the global penalty duration configured using the penalty-period command.
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, “pen” represents penalty, “do” represents downstream, and “enf” represents enforce:
Router# show running-configuration
.
.
.
peak-time1 1 d 60 avg 2 d 60 avg 40 sa 10 pen 11 do enf
Examples The following example shows an enforce-rule that defines two peak monitoring periods for upstream
traffic:
Router(enforce-rule)# peak-time1 10:30 duration 120 avg-rate 10 peak-time2 23 duration 60
avg-rate 10 sample-interval 10 penalty 11 upstream enforce
Related Commands
Command Description
cable qos enforce-rule Creates an enforce-rule to enforce a particular QoS profile for subscriber
traffic management and enters enforce-rule configuration mode.
debug cable Displays enforce-rule debug messages for subscriber traffic management on
subscriber-monitoring the Cisco CMTS routers.
duration Specifies the time period and sample rate to be used for monitoring
subscribers.
monitoring-basics Specifies the type of monitoring for subscriber traffic management on a
Cisco CMTS router.
penalty-period Specifies the period during which an enforced quality of service (QoS)
profile should be in force for subscribers who violate their registered QoS
profile.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate their
registered QoS profiles. This command is applicable for DOCSIS 1.0 cable
modems
qos-profile registered Specifies the registered QoS profile that should be used for this enforce-rule.
This command is applicable for DOCSIS 1.0 cable modems
service-class Identifies a particular service class for cable modem monitoring in an
(enforce-rule) enforce-rule. This command is applicable for DOCSIS 1.1 or later cable
modems.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
weekend peak-time1 Configures peak and offpeak subscriber monitoring over weekends on a
Cisco CMTS router.
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.
no penalty-period
Syntax Description minutes Specifies a time period (in minutes) during which a cable modem (CM)
can be under penalty. The range is 1 to 10080, with a default value of
10080 (7 days).
time-of-day {hour | (Optional) Specifies the time of day (in hh or hh:mm format) when:
hour:minutes}
• A CM that is under penalty is released from the penalty period.
• A CM that is not under penalty has its subscriber monitoring
counters reset.
If the time of day is specified in hour (hh), the valid range is 1 to 23
using a 24-hour clock.
If the time of day is specified in hour:minutes (hh:mm), the valid range
for hour is 1 to 23 using a 24-hour clock, and the valid range for
minutes is 0 to 59.
monitoring-on (Optional) Specifies that monitoring should be turned on after the
penalty release time. If this keyword is not specified, by default,
monitoring is turned off after the release time, until the end of the day,
that is 00:00 hrs.
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 time duration
configured with the penalty-period command. When the penalty period expires, the Cisco CMTS router
restores the subscriber to their registered QoS profile.
The penalty duration specified in the penalty-period command is a global configuration. This penalty
duration is overridden if the individual penalty duration is already configured using the duration,
weekend duration, peaktime1 or weekend peaktime1 commands. Similarly, if the individual penalty
duration is not configured, the global penalty duration is used. Table 31 explains in detail the criteria for
choosing the penalty duration:
Weekend
Penalty-Period
Weekday Configuration
Penalty-Period (CLI: weekend
Global Penalty- Configuration duration, or Applied Penalty
Period (CLI: duration or weekend Duration for Applied Penalty
Configured peaktime1) peaktime1) Weekdays Duration for Weekends
Yes Yes Yes Weekday Penalty Weekend Penalty
Configuration Configuration
Yes Yes No Weekday Penalty Global Penalty
Configuration Configuration
Yes No Yes Global Penalty Weekend Penalty
Configuration Configuration
Yes No No Global Penalty Global Penalty
Configuration Configuration
If the keyword monitoring-on is specified, monitoring starts immediately after the cable modems are
released from penalty. However if this keyword is not specified, by default, all the cable modems using
the enforce-rule are not monitored until the end of day, that is, 00:00 hrs.
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 users who consistently exceed the allocated maximum
bandwidth.
Note To manually move a DOCSIS 1.0 cable modem back to its registered profile before the end of the penalty
period, use the cable modem qos profile command. To manually move a DOCSIS 1.1(or later) cable
modem back to its registered profile before the end of the penalty period, use the cable modem
{ip-address | mac-address} service-class-name command.
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 Before making any changes to an active enforce-rule, we recommend that you first disable the enforce
rule using the no enabled command.
A cable modem consists of two service flows, Primary upstream and Primary downstream. If a DOCSIS
1.0 cable modem enters the penalty period because one of its service flows has exceeded its allowed
bandwidth, the QoS profile of the entire modem is changed. However, if a DOCSIS 1.1 or later cable
modem enters the penalty period because its upstream or downstream service flow has exceeded the
allowed bandwidth threshold, the service class name is changed only for the upstream or downstream
service flow.
Examples The following example shows an enforce-rule named “test”, which is configured with a penalty period
of 1440 minutes (1 day):
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# penalty-period 1440
The following example shows an enforce-rule named “test”, which is configured with a penalty period
of 1440 minutes (1 day), but allowing the removal of the cable modems in penalty at 23:00. Monitoring
will be turned off by default at 23:00, to 00:00 (1 hour):
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# penalty-period 1440 time-of-day 23
The following example shows an enforce-rule named “test”, which is configured with a penalty period
of 1440 minutes (1 day), allowing the removal of the cable modems in penalty at 23:00. However, after
the cable modems are released from penalty, fresh monitoring starts, with all the subscriber monitoring
counters reset to 0:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# penalty-period 1440 time-of-day 23 monitoring-on
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] [repeat queue-intervals] [verbose]
Syntax Description mac-addr The 48-bit hardware (MAC) address of the CM. If you specify the MAC address
of a CPE device, the command will resolve it to the MAC address of the CM
servicing that CPE device and send the DOCSIS ping to the CM.
ip-addr IPv4 or IPv6 address of the CM. If you specify the IP address of a CPE device,
the command will resolve it to the IP address of the CM servicing that CPE
device and send the DOCSIS ping to the CM.
name fqdn Specifies the fully qualified domain name (FQDN) of the cable device to be
displayed. This option is only available if the show cable modem domain-name
command has been run for the first time to update the cable DNS cache on the
CMTS router.
repeat (Optional) Specifies the number of maintenance intervals for a queue. Valid
queue-intervals values are from 1 to 2147483647.
verbose (Optional) Specifies verbose mode for the output, giving additional details about
the packets transmitted and received.
Command Default If no count is specified, five DOCSIS ping packets are sent.
Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA, with the
following changes:
• Support for the Cisco uBR7225VXR router was added.
• Support for specifying the IPv6 address of a CM or CPE device was added.
• The name keyword option was added for specifying the fully-qualified
domain name of a CM.
12.2(33)SCC The repeat keyword was added to specify maintenance intervals for queues.
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:
• A DOCSIS ping uses only 1/64 of the bandwidth of an IP ping.
• A DOCSIS ping can be used with CMs that have not yet acquired an IP address. This allows cable
operators to ping CMs that were not able to complete registration or that were improperly configured
at the IP layer.
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:
• The CM is still in the registration process and has not yet come completely online. In particular, the
CM could be waiting for the DHCP server to assign it an IP address.
• Severe interference or other faults on the physical layer (either the upstream or downstream).
• Significant upstream signal error, distortion, or amplitude errors, often resulting in frequent power
adjustments (which are shown in the cable flap list).
• A non-DOCSIS compliant upstream carrier-to-noise power ratio (C/N) that is between 14 and
21 dB, along with a mixed modulation profile, such as ranging request/response messages being sent
in QPSK mode and short and long data grants in 16-QAM mode.
Note The ping docsis command is a DOCSIS-compliant process that can be used with any two-way
DOCSIS-compliant CM; the CM does not require any special features or code. The ping docsis
command cannot be used with telco-return CMs.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Table 32 explains the different characters that can appear in the output for the ping docsis command:
Note If a CM is already in the flap list, the ping docsis command increments the hit, miss, and
power-adjustment fields for it in the cable flap list.
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.7595
Router#
The following example shows the verbose output for the same command:
Router# ping docsis 00d0.ba77.7595 verbose
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.10
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.111
Cable modem with IP address 192.168.100.111 not registered.
Please try using MAC address instead.
The following example shows the output of the ping docsis command with the repeat keyword:
router# ping docsis 192.168.100.10 repeat 22
Related Commands
Command Description
cable flap-list aging Specifies the number of days to keep a CM in the flap-list table before
aging it out of the table.
cable flap-list insertion-time Sets the insertion time interval that determines whether a CM is
placed in the flap list.
cable flap-list Specifies miss threshold for recording a flap-list event.
miss-threshold
cable flap-list power-adjust Specifies the power-adjust threshold for recording a CM flap-list
threshold event.
cable flap-list size Specifies the maximum number of CMs that can be listed in the
flap-list table.
clear cable flap-list Clears all the entries in the flap-list table.
ping Outputs one or more IP ping requests to a particular IP address.
show cable flap-list Displays the current contents of the flap list.
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 tc-value queue low-latency | mpls exp exp-value queue low-latency
Syntax Description cos enable Enables classification of ingress VLAN traffic according to the 802.1Q
priority bits.
Note This command can only be applied to VLAN interfaces.
cos cos-value queue Classifies incoming VLAN traffic on a subinterface according to the
low-latency 802.1Q priority bits and places the traffic into the appropriate queue. By
default, traffic with 802.1Q priority bits set to 6 or 7 are placed in the
high-priority queue and all other traffic is placed in the low-priority queue.
cos-value specifies the IEEE 802.1Q/ISL CoS value from 0 to 7.
Note When you configure a class of service (CoS) value on a QinQ
subinterface, the CoS value applies to all QinQ subinterfaces with
the same outer VLAN ID.
ipv6 tc tc-value queue Classifies ingress IPv6 traffic based on the value of the traffic-class bits and
low-latency places the traffic into the appropriate queue. By default, IPv6 traffic with a
traffic-class value equal to ef uses the high-priority queue and all other
traffic uses the low-priority queue. Only the most significant six bits of the
traffic-class octet is used for the classification.
Note This command applies only to physical interfaces.
tc-value is the value of the traffic class bits. You can specify a range of
values separated by a dash or a list of values. For a list of valid values, see
the Usage Guidelines.
low-latency specifies the high priority queue.
mpls exp exp-value Classifies incoming MPLS traffic according to the value of the EXP bits and
queue low-latency places the traffic into the appropriate queue. By default, traffic with the EXP
bits set to 6 or 7 uses the high-priority queue and all other traffic uses the
low-priority queue.
Note This command applies only to physical interfaces.
exp-value is the value of the EXP bits (0 to 7). You can specify a range of
values separated by a dash or a list of values.
low-latency specifies the high priority queue.
Defaults Disabled
Usage Guidelines The plim qos input map command separates high-priority traffic from low-priority traffic and places
the traffic in the appropriate interface queue. The command separates priority and non-priority traffic at
the SPA interface processor (SIP) to prevent the dropping of high priority traffic in an oversubscription
case. Each shared port adaptor (SPA) supports one priority queue.
The router supports the following classification types for the prioritization of ingress traffic on the
Gigabit Ethernet SPAs:
• VLAN 802.1Q priority bits
• IP DSCP bits
• IP precedence bits
• IPv6 traffic class bits
• MPLS experimental (EXP) bits
For the plim qos input map ip dscp dscp-value queue low-latency command, valid values for
dscp-value are one of the following:
• 0 to 63—Differentiated services codepoint value
• af11—001010
• af12—001100
• af13—001110
• af21—010010
• af22—010100
• af23—010110
• af31—011010
• af32—011100
• af33—011110
• af41—100010
• af42—100100
• af43—100110
• cs1—Precedence 1 (001000)
• cs2—Precedence 2 (010000)
• cs3—Precedence 3 (011000)
• cs4—Precedence 4 (100000)
• cs5—Precedence 5 (101000)
• cs6—Precedence 6 (110000)
• cs7—Precedence 7 (111000)
• default—000000
• ef—101110
For the plim qos input map ipv6 tc tc-value queue low-latency command, valid values for tc-value are
one of the following:
• 0 to 63—Differentiated services codepoint value
• af11—001010
• af12—001100
• af13—001110
• af21—010010
• af22—010100
• af23—010110
• af31—011010
• af32—011100
• af33—011110
• af41—100010
• af42—100100
• af43—100110
• cs1—Precedence 1 (001000)
• cs2—Precedence 2 (010000)
• cs3—Precedence 3 (011000)
• cs4—Precedence 4 (100000)
• cs5—Precedence 5 (101000)
• cs6—Precedence 6 (110000)
• cs7—Precedence 7 (111000)
• default—000000
• ef—101110
Examples The following example enables DSCP-based classification on the SPA that is located in subslot 0 of the
SIP in slot 1 of the Cisco 10000 series router:
Router(config)# interface gigabitethernet 3/0/1
Router(config-if)# plim qos input map ip dscp-based
policy
To select modems based on the type of service flow that is balanced, use the policy command in the
config-lb-group configuration mode. To reset the selection, use the no form of this command.
Syntax Description pcmm Enables balancing of modems with active PCMM service flows.
ugs Enables balancing of modems with active UGS service flows.
us-across-ds Sets load balancing on upstream (US) groups across downstream (DS) and
DS group methods are ignored.
pure-ds-load Considers DS load and not US load when calculating DS utilization.
Examples The following example shows how to select the modems on the CMTS based on the type of service flow
that is balanced using the policy command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# policy pure-ds-load
Router(config-lb-group)#
port (dial-peer)
To associate a dial peer with a specific voice port, use the port dial-peer configuration command. To
cancel this association, use the no form of this command.
Cisco uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
port number
no port number
Note For complete details on this command for all supported platforms, see the Cisco IOS Voice, Video, and
Fax Command Reference, Release 12.2, available on Cisco.com.
Syntax Description: number Specifies one of the RJ-11 voice port connectors installed in the router. Valid
entries are 0 (which corresponds to the RJ-11 connector labeled V1) and 1
(which corresponds to the RJ-11 connector labeled V2).
Usage Guidelines This command is used for calls incoming from a telephony interface to select an incoming dial peer and
for calls coming from the VoIP network to match a port with the selected outgoing dial peer.
Examples The following example shows how to associate a POTS dial peer 10 with voice port 1 (connector V2) on
the Cisco uBR924 or Cisco uBR925 cable access router or on the CVA122 Cable Voice Adapter:
dial-peer voice 10 pots
port 1
The following example shows how to associate a POTS dial peer 30 with voice port 0 (connector V1) on
the Cisco uBR924 or Cisco uBR925 cable access router or on the CVA122 Cable Voice Adapter:
dial-peer voice 30 pots
port 0
profile-description
To provide a profile description for each profile in the selected cable multicast authorization profile, use
the profile-description command in multicast authorization profile configuration mode. To remove the
profile description, use the no form of this command.
profile-description profile-description
no profile-description profile-description
Syntax Description profile-description Specifies profile description for the selected profile. You can use up to 128
characters to describe the profile.
Usage Guidelines This command is available only from the cable multicast authorization profile mode.
Examples The following example shows how to enter a profile description for a multicast authorization profile
name:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable multicast auth profile-name
Router(config)# cable multicast auth profile-name gold
Router(config-mauth)# profile-description gold-configured-may
Command Description
show cable multicast Displays the list of defined multicast authorization profiles and all CMs
authorization associated with corresponding profiles.
show running-config Displays the running configuration for each of the cable interfaces.
interface cable
privacy
To create a DOCSIS configuration file that enables and configures the DOCSIS Baseline Privacy
Interface (BPI) option, use the privacy command in cable config-file configuration mode. To disable BPI
for the CM, use the no form of this command.
privacy timeout {authorize value| operational value| re-authorize value| reject value| rekey
value}
Syntax Description authorization value Authorization grace time in seconds. Valid values are 1 to 1800 seconds.
Default value is 600 seconds.
tek value TEK grace time in seconds. Valid range is 1 to 1800 seconds. Default is 600
seconds.
authorize value Authorize wait timeout in seconds. Valid range is 1 to 30 seconds. Default
value is 10 seconds.
operational value Operational Wait timeout in seconds. Valid range is 1 to 10 seconds. Default
is 1 second.
re-authorize value Re-authorize wait timeout in seconds. Valid range is 1 to 20 seconds.
reject value Authorize reject wait timeout in seconds. Valid range is 1 to 600 seconds.
Default is 60 seconds.
rekey value Rekey wait timeout in seconds. Valid range is 1 to 10 seconds. Default is 1
second.
Usage Guidelines Specifying the privacy command without any of the keywords and arguments enables BPI encryption
and decryption for the CM. In addition to this command, you must also specify the service-class privacy
command to enable BPI operations on the cable modem.
Note The privacy command appears and is supported only in images with support for BPI or BPI+ encryption.
This option configures the CM for BPI or BPI+ encryption. To use BPI encryption, the Cisco CMTS
must also be configured for BPI or BPI+ encryption, using the cable privacy command.
Examples The following example shows how to set the CM privacy TEK gracetime to 1200 seconds and enables
BPI operations for the cable modem.
router(config)# cable config-file bpi.cm
router(config-file)# privacy grace-time tek 1200
router(config-file)# service-class 1 privacy
router(config-file)# exit
router(config)#
New Commands
Modified Commands
Removed Commands
qos-profile enforced
To specify a quality-of-service (QoS) profile that should be enforced when users violate their registered
QoS profiles, use the qos-profile enforced command in enforce-rule configuration mode. To delete the
enforced QoS profile from the enforce-rule, use the no form of this command.
Syntax Description profile-id Specifies the QoS profile to be enforced. The valid range is 0 to 16383,
with a default of 0.
no-persistence (Optional) Specifies that the enforced QoS profile should not remain
in force when a cable modem reboots. Instead, when a cable modem
that is in the penalty period reboots, it is automatically removed from
the penalty period and assigned the QoS profile that is specified in its
DOCSIS configuration file.
The default behavior is that enforced QoS profiles remain in force for
cable modems across reboots.
Command Default The value of profile-id defaults to 0, and enforced QoS profiles are persistent across cable modem
reboots.
Usage Guidelines Both the originally provisioned QoS profile and the enforced QoS profile must be created on the
Cisco CMTS router. The profile-id does not support QoS profiles that are created by the cable modem.
An enforce-rule can specify an enforced QoS profile, which is automatically applied to subscribers who
transmit more traffic than allowed by their registered QoS profile. The enforced QoS profile remains in
effect during the penalty time period (see the penalty-period command). At the end of the penalty
period, the subscriber returns to the registered QoS profile.
If a cable modem reboots while it is in its penalty time period, it continues using the enforced QoS
profile, unless the service provider has manually changed the cable modem’s registered QoS profile
using the cable modem qos profile command.
When you change the enforced QoS profile for a currently active enforce-rule, any cable modems using
this rule that are currently in the penalty period continue using the previously configured enforced QoS
profile. Any cable modems that enter the penalty period after this configuration change, however, use
the new enforced QoS profile.
An enforced QoS profile must already have been created on the Cisco CMTS router before you can
assign it to an enforce-rule. If the rule does not exist, the system displays an error message.
When the no-persistence option is specified, the enforced QoS profile is still automatically applied to
subscribers who violate their bandwidth requirements. However, when the cable modem reboots, the
Cisco CMTS router allows the cable modem to use the QoS profile that is specified in its DOCSIS
configuration file.
The no-persistence option can be used when initially using the Subscriber Traffic Management feature
to identify potential problem applications and users. When repeat offenders are identified, they can then
be assigned enforce-rules that do not use the no-persistence option, so that they remain in the penalty
period even if they reboot their cable modems.
Note The system automatically applies the enforced QoS profile to violators only if the enforce keyword has
been used with the activate-rule-at-byte-count command.
Examples The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# qos-profile enforced 12
The following example shows profile 12 being assigned as the enforced QoS profile to an enforce-rule,
but with the no-persistence option specified, so that the enforced QoS profile does not remain in force
if the cable modem reboots:
Router# configure terminal
Router(config)# cable qos enforce-rule residential
Router(enforce-rule)# qos-profile enforced 12 no-persistence
The following example shows the error message that is displayed when the specified QoS profile does
not exist on the CMTS:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# qos-profile enforced 98
Command Description
enabled (enforce-rule) Activates an enforce-rule and begins subscriber traffic management
on a Cisco CMTS router.
monitoring-basics Specifies the type of monitoring for subscriber traffic management on
a Cisco CMTS router.
peak-time1 Specifies peak and offpeak monitoring times on a Cisco CMTS router.
qos-profile registered Specifies the registered QoS profile that should be used for this
enforce-rule.
service-class (enforce-rule) Identifies a particular service class for cable modem monitoring in an
enforce-rule.
show cable qos enforce-rule Displays the QoS enforce-rules that are currently defined.
show cable subscriber-usage Displays subscribers who are violating their registered QoS profiles.
qos-profile registered
To specify the registered quality of service (QoS) profile that should be used for this enforce-rule, use
the qos-profile registered command in enforce-rule configuration mode. To remove the registered QoS
profile from the enforce-rule, use the no form of this command.
Syntax Description profile-id Specifies the QoS profile to be monitored. This profile must be created
on the Cisco CMTS router. If you want to manage a cable modem that
uses a modem-created QoS profile, you must first create that exact QoS
profile on the CMTS router before using this command. The valid
range is 0 to 16383, with a default of 0.
Usage Guidelines You must specify a registered QoS profile for each enforce-rule. The Cisco CMTS router then uses the
registered profile ID to match subscribers’ service flows to the proper enforce-rules.
When you change the registered QoS profile for an active rule, the cable modems that had been using
the previous registered QoS profile are no longer managed by the Subscriber Traffic Management
feature. Instead, the rule begins managing those cable modems that use the new registered QoS profile.
Note The registered QoS profile must be created on the Cisco CMTS router before you can assign it to an
enforce-rule. If the rule does not exist, the system displays an error message. If you want to manage a
cable modem that is currently using a modem-created QoS profile, you must first manually create a new
QoS profile on the CMTS router that has the same QoS parameters as the modem-created profile. Then
allow the modem to come online using the manually created profile, before using the qos-profile
registered command.
Examples The following example shows profile 50 being assigned as the registered QoS profile to an enforce-rule:
Router# configure terminal
Router(config)# cable qos enforce-rule enforce-rule
Router(enforce-rule)# qos-profile registered 50
The following example shows the error message that is displayed when the specified QoS profile does
not exist on the CMTS:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# qos-profile registered 99
rcp-id
To assign a receive channel profile (RCP) ID to a receive channel configuration (RCC) template, use the
rcp-id command in RCC template configuration mode. To remove the RCP ID, use the no form of this
command.
rcp-id rcp-id
no rcp-id rcp-id
Syntax Description rcp-id Specifies an RCP ID for the RCC template. The valid range is from 00 00 00
00 00 to FF FF FF FF FF.
Command Default By default the RCP ID is set to 00 00 00 00 00. However, you must change the default value to a non-zero
RCP ID.
Usage Guidelines A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive
channel (RC) entry.
First, you define an RCC template for an RCP, and then assign the template to a cable interface to
generate RCCs based on the actual DS channel configuration.
Examples The following example shows how to assign an RCP ID to an RCC template:
Router# configure terminal
Router(config)# cable rcc-template 1
Router(config-rcc-template)# rcp-id 00 10 00 00 03
receive-channel
To associate a receive channel to a receive module (RC), use the receive-channel command in RCC
template configuration mode. To restore the default value, use the no form of this command.
Syntax Description index Specifies the index value for the receive channel. The valid range is 1 to 10.
center-frequency Specifies the center frequency for the receive channel.
Hz Specifies the center frequency value in Hz. The valid range is
55000000-858000000.
connected-receive-mo Specifies a nested receive module in the RCC template.
dule Generally, only one receive module is configured for an RCC template.
index Specifies the index value for the connected receive module. The valid range
is 1 to 10.
Primary (Optional) Indicates that it is a CM primary channel and an RCC can be
derived from this channel.
Usage Guidelines A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive
channel (RC) entry. First, you define an RCC template for an RCP, and then assign the template to a cable
interface to generate RCCs based on the actual DS channel configuration.
An RCC template configures the physical layer components described by an RCP, including receive
modules and receive channels to specific downstream frequencies, and specifies the interconnections
among receive modules or between receive modules and receive channels.
A receive module can include multiple receive channels. So we need to specify which receive channel
belongs to which receive module.
Examples The following example shows how to associate a receive channel to a receive module:
Router# configure terminal
Router(config)# cable rcc-template 1
Router(config-rcc-template)# rcp-id 00 10 00 00 03
Router(config-rcc-template)# receive-module 1 first-channel-center-frequency 555000000
Router(config-rcc-template)# receive-channel 1 center-frequency 555000000
connected-receive-module 1 primary
Router(config-rcc-template)# receive-channel 2 center-frequency 561000000
connected-receive-module 1
receive-module
To associate a receive module (RC) to a Receive Channel Configuration (RCC) template, use the
receive-module command in RCC template configuration mode. To restore the default value, use the no
form of this command.
Syntax Description index Specifies the index value for the receive module. The valid index range is 1
to 10.
first-channel-center-fr Specifies the center frequency of the first channel of the receive module
equency channel block.
Hz Specifies the center frequency value in Hz. The valid range is 55000000 to
858000000.
connected-receive-mo (Optional) Specifies a nested receive module in the RCC template.
dule
Generally, only one receive module is configured for an RCC template.
index (Optional) Specifies the index value for the connected receive module. The
valid range is 1 to 10.
Usage Guidelines A valid RCC template consists of a configured RCP ID, a receive module (RM) entry, and a receive
channel (RC) entry. First, you define an RCC template for an RCP, and then assign the template to a cable
interface to generate RCCs based on the actual DS channel configuration.
An RCC template configures the physical layer components described by an RCP, including receive
modules and receive channels to specific downstream frequencies, and specifies the interconnections
among receive modules or between receive modules and receive channels.
A receive module can include multiple receive channels. So we need to specify which receive channel
belongs to which receive module.
Examples The following example shows how to associate a receive module to an RCC template:
Router# configure terminal
Router(config)# cable rcc-template 1
Router(config-rcc-template)# rcp-id 00 10 00 00 03
Router(config-rcc-template)# receive-module 1 first-channel-center-frequency 555000000
Router(config-rcc-template)# receive-channel 1 center-frequency 555000000
connected-receive-module 1 primary
Router(config-rcc-template)# receive-channel 2 center-frequency 561000000
connected-receive-module 1
redundancy
To enter redundancy configuration mode, use the redundancy command in global configuration mode.
redundancy
Usage Guidelines Use the redundancy command to enter redundancy configuration mode, where you can define aspects
of redundancy such as shelf redundancy for the Cisco AS5800 universal access server.
The following restrictions apply to line card redundancy on the Cisco 10000 series router:
• Port-level redundancy is not supported.
• Redundant cards must occupy the two subslots within the same physical line card slot.
• The line card that will act as the primary line card must be the first line card configured, and it must
occupy subslot 1.
The following example assigns the configured router shelf to the redundancy pair designated as 25. This
command must be issued on both router shelves in the redundant router-shelf pair:
Router(config)# redundancy
Router(config-red)# failover group-number 25
Router(config)# redundancy
Router(config-r)# ?
Usage Guidelines The redundancy force-failover main-cpu command initiates a manual switchover, so that the standby
PRE1 module becomes the active PRE1 module and assumes full responsibilities for router operations.
This command requires that both PRE1 modules are running a Cisco IOS software image that supports
the Route Processor Redundancy (RPR) feature.
Note The terms failover and switchover are interchangeable, but switchover is the term used across all Cisco
platforms capable of high-availability operation.
Tip Do not perform a switchover immediately after you change the configuration and save it to the NVRAM.
Instead, wait a few minutes to allow the two PRE1 modules to synchronize the new configuration, and
then perform the switchover.
Tip Wait two to three minutes after a switchover before switching the system back to the original PRE1
module, so as to allow the system to stabilize and so that both PRE1 modules are ready for the switch.
In Cisco IOS Release 12.2(11)BC3 and later releases, the active PRE1 module will not initiate a new
switchover until a current switchover is complete and the system has stabilized.
Note Pressing enter or y confirms the action and begins the switchover. Pressing any other key aborts the
switchover and returns control to the current active PRE1 module.
The following example shows a switchover being attempted but failing because the standby PRE1
module is either not ready, not available, or not installed:
Router# redundancy force-failover main-cpu
Note In some versions of Cisco IOS software, a failed software switchover will show the following message:
redundancy force-switchover
To force the standby Route Processor (RP) to assume the role of the active RP, use the redundancy
force-switchover command in privileged EXEC mode.
Usage Guidelines Use the redundancy force-switchover command to switch control of a router from the active RP to the
standby RP. Both the active and standby RPs must have a high availability Cisco IOS image installed and
must be configured for Route Processor Redundancy (RPR) mode before the redundancy
force-switchover command can be used. Before the system switches over, it verifies that the standby RP
is ready to take over.
When you use the redundancy force-switchover command and the current running configuration is
different from the startup configuration, the system prompts you to save the running configuration before
the switchover is performed.
Note Before using this command in Cisco 7600 series routers, refer to the “Performing a Fast Software
Upgrade” section of the Cisco 7600 Series Router Cisco IOS Software Configuration Guide for
additional information.
On Cisco 7600 series routers, the redundancy force-switchover command conducts a manual
switchover to the redundant supervisor engine. The redundant supervisor engine becomes the new active
supervisor engine running the new Cisco IOS image. The modules are reset and the module software is
downloaded from the new active supervisor engine.
The active and redundant supervisor engines do not reset on a Route Processor Redundancy Plus (RPR+)
switchover. The old active supervisor engine reboots with the new image and becomes the redundant
supervisor engine.
Beginning with Cisco IOS Release 12.2(33)SCA, you can force a Performance Routing Engine (PRE)
switchover using the redundancy force-switchover main-cpu command from either the primary or
standby PRE. If you force a switchover from the active PRE, both PREs synchronize and the active PRE
reloads normally. When you force a switchover from the standby PRE, a crash dump of the active PRE
occurs for troubleshooting purposes. Forcing a switchover from the standby PRE should only be done if
you cannot access the active PRE.
Examples The following example shows a switchover from the active RP to the standby RP on a Cisco 7513 router
with RPR configured:
Router# configure terminal
Router(config)# hw-module slot 7 image slot0:rsp-pv-mz
Router(config)# hw-module slot 6 image slot0:rsp-pv-mz
Router(config)# slave auto-sync config
Router(config)# redundancy
Router(config-r)# mode rpr
Router(config-r)# end
Router# copy running-config startup-config
Router# redundancy force-switchover
The following example shows how to perform a manual switchover from the active to the standby RP
when the running configuration is different from the startup configuration:
Router# redundancy force-switchover
00:07:35:%SYS-5-SWITCHOVER:Switchover requested
The following example shows how to perform a manual switchover from the active to the standby RP
when the running configuration is the same as the startup configuration:
Router# redundancy force-switchover
redundancy reload
To reset the standby PRE module or to reset both the active and standby PRE modules, use the
redundancy reload command in privileged EXEC mode.
Usage Guidelines The redundancy reload peer command reloads the Cisco IOS software on the standby PRE1 module,
which does not have an impact on router operations, assuming a switchover is not required while the
standby module is resetting. The redundancy reload shelf command reloads the Cisco IOS software on
both the active and standby PRE1 modules, which will interrupt services on the router until all PRE1
modules and line cards initialize and come back online.
Examples The following example shows a switchover being manually initiated, overriding any checks that might
prevent or delay the switchover:
Router# redundancy reload peer
Reload peer? [confirm] y
Preparing to reload peer
Note Pressing enter or y confirms the action and begins the reload. Pressing any other key aborts the reload
and returns control to the current active PRE1 module.
The following example shows the system’s response when a standby PRE1 module is not installed in the
router:
Router# redundancy reload peer
Note Pressing enter or y confirms the action and begins the reload of both modules. Pressing any other key
aborts the reload and returns control to the current active PRE1 module.
redundancy switch-activity
To force a switchover to the standby PRE module, use the redundancy switch-activity command in
privileged EXEC mode.
Note The terms failover and switchover are interchangeable, but switchover is the term used across all
Cisco platforms capable of high-availability operation.
Syntax Description force (Optional) Forces a switchover immediately, overriding any checks in the
code or configuration that might prevent or delay a switchover.
Usage Guidelines The redundancy switch-activity command is similar to the redundancy force-failover main-cpu
command, except that it includes an option to force the switchover, overriding any configuration checks
or other checks in the software that could prevent the switchover. In all cases, this command verifies that
the standby PRE module is available and capable of performing the switchover before it transfers control
to that PRE module. This command also synchronizes the current running-config and client data before
initiating the switchover.
Examples The following example shows a switchover being manually initiated, overriding any checks that might
prevent or delay the switchover:
Router# redundancy switch-activity force
Proceed with switchover to standby PRE? [confirm] y
Note Pressing enter or y confirms the action and begins the switchover. Pressing any other key aborts the
switchover and returns control to the current active PRE1 module.
registered qos-profile
Note Effective with Cisco IOS Release 12.3(9a)BC, the registered qos-profile command is replaced by the
qos-profile registered command.
To specify the registered quality of service (QoS) profile that should be used for this enforce-rule, use
the registered qos-profile command in enforce-rule configuration mode. To remove the registered QoS
profile from the enforce-rule, use the no form of this command.
Syntax Description profile-id Specifies the QoS profile to be monitored. This profile must be created
on the Cisco CMTS router. If you want to manage a cable modem that
uses a modem-created QoS profile, you must first create that exact QoS
profile on the CMTS router before using this command. The valid
range is 0 to 16383, with a default of 0.
Usage Guidelines You must specify a registered QoS profile for each enforce-rule. The Cisco CMTS router then uses the
registered profile ID to match subscribers’ service flows to the proper enforce-rules.
When you change the registered QoS profile for an active rule, the cable modems that had been using
the previous registered QoS profile are no longer managed by the Subscriber Traffic Management
feature. Instead, the rule begins managing those cable modems that use the new registered QoS profile.
Note The registered QoS profile must be created on the Cisco CMTS router before you can assign it to an
enforce-rule. If the rule does not exist, the system displays an error message. If you want to manage a
CM that is using a CM-created QoS profile, you must first create a QoS profile on the Cisco CMTS
router that matches the CM-created profile exactly. Then use the registered qos-profile command to
assign that profile to this enforce-rule.
Examples The following example shows profile 50 being assigned as the registered QoS profile to an enforce-rule:
Router# configure terminal
Router(config)# cable qos enforce-rule enforce-rule
Router(enforce-rule)# registered qos-profile 50
The following example shows the error message that is displayed when the specified QoS profile does
not exist on the CMTS:
Router# configure terminal
Router(config)# cable qos enforce-rule test
Router(enforce-rule)# registered qos-profile 99
restricted
To convert a general load balancing group (GLBG) to a restricted load balancing group (RLBG) for
DOCSIS load balancing, use the restricted command in the config-lb-group configuration mode. To
revert to the general group type for DOCSIS load balancing, use the no form of this command.
restricted
no restricted
Command Default By default, the general group type is selected for load balancing.
Examples The following example shows how to convert a GLBG to a RLBG using the restricted command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# restricted
Router(config-lb-group)#
revertive
To enable the revert operation on a protect card, use the revertive command in line card redundancy
group mode.
revertive time
no revertive time
Syntax Description time Specifies the revert operation time in minutes. The valid values are 1 to
35791.
Examples The following example shows how to specify the revert operation time for a protect card on a uBR10012
router:
Router# configure terminal
Router(config)# redundancy
Router(config-red)# linecard-group 1 cable
Router(config-red-lc)# revertive 30
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA FPGA. Valid
values for rf-port depend on the configuration set with the annex modulation
command.
channel-id A unique channel ID. Valid values for releases prior to Cisco IOS Release
12.2(33)SCB are from 0 to 255 and the valid values for Cisco IOS Release
12.2(33)SCB and later are from 1 to 255 as 0 is reserved for network
management.
Command Default If the rf-channel cable downstream channel-id command is not issued, Cisco IOS software assigns a
unique downstream channel ID to the RF channel.
Usage Guidelines For the wideband channel to work correctly, each RF channel on the fiber node that the wideband
channel uses must have a unique downstream channel ID. By default, Cisco IOS software assigns a
unique downstream channel ID to the RF channel. Use the rf-channel cable downstream channel-id
command to change the default channel ID.
The downstream channel ID that is assigned to the RF channel must be unique on the fiber node.
• The ID cannot be the same ID as is used for another RF channel on the fiber node.
• The ID cannot be the same ID as is used for a primary downstream channel on the fiber node.
You can check downstream channel IDs that are being used by examining the CMTS router configuration
file.
Refer to cable downstream channel-id id command for the updated downstream channel ID scheme
table.
Note If you assign a downstream channel ID that is not unique on the fiber node, the rf-channel cable
downstream channel-id command displays an error message. The command does assign the channel
ID, but the status of the fiber node becomes invalid.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command.
• For annex A and 256 QAM, each Wideband SPA supports 18 RF channels. In this case, valid values
for the rf-port argument are 0 to 17.
• For all other cases, the SPA supports 24 RF channels. In these cases, valid values for the rf-port
argument are 0 to 23.
Note Effective with Cisco IOS Release 12.3(23)BC, the annex modulation command is obsolete and annex
and modulation are included as keyword options in the rf-channel frequency command. Also, for
annex A and 256 QAM, each Wideband SPA supports up to 18 RF channels at full rate or up to 24 RF
channels at less than full rate.
Examples The following example shows how to assign a downstream channel ID of 123 to RF channel 3 on the
Wideband SPA located in slot/subslot/bay 1/0/1.
Router# configure terminal
Router(config)# controller modular-cable 1/0/1
Router(config-controller)# rf-channel 3 cable downstream channel-id 123
rf-channel depi-tunnel
To bind the depi-tunnel, which inherits the configuration of the specified l2tp-class and depi-class, to an
rf-channel on a shared port adapter (SPA), use the rf-channel depi-tunnel command in controller
configuration mode. The tsid keyword is used to associate the logical rf-channel of the SPA to a physical
quadrature amplitude modulation (QAM) on the radio frequency gateway (RFGW-10). To unbind the
depi-tunnel, use the no form of this command.
Syntax Description rf-channel RF channel physical port on the Wideband SPA. The allowed range is from
0 to 3.
depi-tunnel-name Name of the DEPI tunnel.
tsid id (Optional) TS ID value.
Usage Guidelines To configure DEPI on the M-CMTS, bind the depi-tunnel to an rf-channel on a SPA using the rf-channel
depi-tunnel command in controller configuration mode. To associate the logical rf-channel on the SPA
to a QAM on the RFGW, use the tsid keyword.
Examples The following example shows how to bind the depi-tunnel SPA0 to rf-channel 0 on a SPA:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 depi-tunnel SPA0
The following example shows how to bind the depi-tunnel SPA0 to rf-channel 0 on a SPA and associate
tsid 100 to the QAM:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 depi-tunnel SPA0 tsid 100
rf-channel description
To configure the description of an RF channel on a Wideband SPA, use the rf-channel description
command in controller configuration mode. To remove an RF channel configuration, use the no form of
this command.
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA FPGA.
Allowed range is 0 to 23. Valid values for rf-port depend on the
configuration set with the annex modulation command (see the Usage
Guidelines section).
description Specifies a description for the RF channel.
Command Default No default RF channel configuration values are set for the description.
Usage Guidelines The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command. For annex A
and 256 QAM, each Wideband SPA supports up to 18 RF channels at full rate and up to 24 RF channels
at less than full rate. For all other cases, the SPA supports 24 RF channels.
Note In Cisco IOS Release 12.3(21)BC, annex and modulation parameters were set globally for each SPA
using the annex modulation command.
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel
using the rf-channel frequency command. The annex modulation command is obsolete.
Examples The following example shows how to configure the description of the RF channel characteristics for RF
port 0:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 description Primary downstream channel
rf-channel frequency
To configure the frequency of an RF channel on a Wideband SPA, use the rf-channel frequency
command in controller configuration mode. To remove the frequency of an RF channel configuration,
use the no form of this command.
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA FPGA.
Allowed range is 0 to 23. Valid values for rf-port depend on the
configuration set with the annex modulation command (see the
Usage Guidelines section).
freq Sets the center frequency for the RF channel. Allowed range is
55000000 to 1050000000 MHz.
annex {A|B} Specifies the MPEG framing format for each RF channel:
• A–Annex A. The downstream is compatible with the European
MPEG framing format specified in ITU-TJ.83 Annex A.
• B–Annex B. The downstream is compatible with the North
American MPEG framing format specified in ITU-TJ.83 Annex
B.
modulation {64|256} Specifies the modulation rate for each RF channel:
• 64–64-QAM
• 256–256-QAM
interleave-depth{8 | 12 | 16 | Indicates the downstream interleave depth. The default value is 32.
32 | 64 |128}
Command Default No default RF channel configuration values are set for frequency, annex, and modulation. The default
value for interleave-depth is 32.
Usage Guidelines Cisco IOS Release 12.3(21)BC and Cisco IOS Release 12.2(33)SCA
This command configures the frequency for an RF channel on a Wideband SPA.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command. For annex A
and 256 QAM, each Wideband SPA supports up to 18 RF channels. For all other cases, the SPA supports
up to 24 RF channels.
Note In Cisco IOS 12.3(21)BC and 12.3(21a)BC3 releases, annex and modulation parameters were set
globally for each SPA using the annex modulation command.
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel
using the rf-channel frequency command. The annex modulation command is obsolete.
Note Be certain to verify that the RF channel values set with rf-channel frequency match the values
configured for the QAM outputs on the edge QAM device.The frequency value must match. If the value
does not match, the Wideband SPA will not successfully communicate with the edge QAM device.
Examples The following example shows how to configure RF channel frequency for RF port 0:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 frequency 699000000 annex A modulation 256
interleave-depth 64
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA FPGA.
Allowed range is 0 to 23. Valid values for rf-port depend on the
configuration set with the annex modulation command (see the
Usage Guidelines section).
ip-address Specifies the IP address of the Gigabit Ethernet interface on the edge
QAM device for this RF channel.
mac-address Specifies the MAC address of the next-hop interface or of the edge
QAM device for this RF channel.
portnum Specifies the UDP port number for the edge QAM device that will be
used for this RF channel. Allowed range is 0 to 65535.
session-id Specifies the DEPI remote session ID to be used for encapsulation of
frames in DOCSIS-MPT mode.
Usage Guidelines For each RF channel, use the rf-channel ip-address mac-address udp-port command in controller
configuration mode to configure RF-channel characteristics.
The Cisco uBR10012 router supports two Wideband SPAs. Each Wideband SPA supports up to 24 RF
channels depending on how the SPA is configured with the annex modulation command. For annex A
and 256 QAM, each Wideband SPA supports up to18 RF channels. For all other cases, the SPA supports
up to 24 RF channels.
Note In the Cisco IOS Release 12.3(21)BC and 12.3(21a)BC3 releases, annex and modulation parameters
were set globally for each SPA using the annex modulation command.
Beginning in Cisco IOS Release 12.3(23)BC, annex and modulation values are set for each RF channel
using the rf-channel frequency command. The annex modulation command is obsolete.
For each RF channel (rf-port), the following items must be configured with rf-channel ip-address
mac-address udp-port command:
Cisco IOS Release 12.3(21)BC and Cisco IOS Release 12.2(33)SCA
• IP address
• MAC address
• UDP port
• Associated wideband channel (see the cable rf-channel command)
Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB
• IP address
• MAC address
• UDP port or DEPI remote ID
• Associated wideband channel (see the cable rf-channel command)
The value used for mac-address in the mac-address argument is as follows:
• If a Gigabit Ethernet router or Layer 3 switch is used between the Wideband SPA and the edge QAM
device, the value specified for mac-address is the MAC address for the next-hop interface on the
router or Layer 3 switch.
• If a Gigabit Ethernet router or Layer 3 switch is not used, the value specified for mac-address is the
MAC address for the Gigabit Ethernet interface on the edge QAM device.
The UDP port number set for the RF channel allows mapping an input UDP session to a specific QAM
output port. Wideband traffic from different Wideband SPAs cannot be mixed on the same QAM output
ports.
Note Be certain to verify that the RF channel values set with rf-channel frequency match the values
configured for the QAM outputs on the edge QAM device. IP address, MAC address, UDP port, and
DEPI remote ID must match. If any of these values do not match, the Wideband SPA will not
successfully communicate with the edge QAM device.
Examples The following example shows how to configure the RF channel IP address, MAC address UDP port and
DEPI remote ID characteristics for RF port 0:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
rf-channel network-delay
To configure the network delay for an RF channel on a Wideband SPA, use the rf-channel network
delay command in controller configuration mode. To remove the network delay configuration for an RF
channel, use the no form of this command.
Syntax Description rf-port RF channel physical port on the Wideband SPA FPGA.
The allowed range is from 0 to 23. The valid values for
rf-port depend on the configuration set with the annex
modulation command (see the Usage Guidelines section).
delay Converged Interconnect Network (CIN) delay. The default
value is 550 us. The allowed range is from 0 to 3000 us.
The delay value auto determines the delay through DEPI
Latency Measurement (DLM) packets.
sampling-rate (Optional) Specifies how often the DLM is sent. The
allowed range is from 1 to 500 sec. The default value is 10
sec. This option is available only when the delay value is
set to auto.
rate Sampling-rate value.
Command Default No default RF channel network delay configuration values are set.
Usage Guidelines The Cisco uBR10012 universal broadband router supports two Wideband SPAs. Each Wideband SPA
supports up to 24 RF channels depending on how the SPA is configured with the annex modulation
command. For annex A and 256 QAM, each Wideband SPA supports up to18 RF channels. For all other
cases, the SPA supports up to 24 RF channels.
Note In Cisco IOS releases 12.3(21) BC and 12.3(21a)BC3, annex and modulation parameters were set
globally for each SPA using the annex modulation command.
From Cisco IOS Release 12.3(23)BC onwards, annex and modulation values are set for each RF channel
using the rf-channel frequency command. The annex modulation command is obsolete.
Examples The following example shows how to configure the RF channel network delay characteristics for RF port
0:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 network-delay 1000
The following example shows how to configure the RF channel network delay characteristics for RF port
0 with a sampling-rate of 1sec:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 network-delay auto sampling-rate 1
rf-channel rf-power
To set the RF power output level on Cisco UBR-MC20X20V and Cisco uBR-MC88V cable interface
line cards, use the rf-channel rf-power command in controller configuration mode. To reset the RF
output power level to its default value, use the no form of this command.
Syntax Description rf-port RF channel physical port on the Wideband SPA FPGA. The valid
range is from 0 to 3. Valid values for rf-port depend on the
configuration set with the annex modulation command.
power-level Desired RF output power level in dBmV. The valid range is dependent
on the cable interface line card. The format is XY.Z. By default, .Z is
added as .0.
Usage Guidelines For the Cisco UBR-MC20X20V cable interface line card, all the channels within a controller must have
the same RF power value. When the RF power value is changed on any one channel, the same value is
applied to all the channels within the controller. The recommended RF power range depends on the mode
of the upconverter. The mode of the upconverter is decided by the highest numbered channel that is
enabled.
Note RF power value outside the recommended RF power range is accepted but is automatically adjusted. If
the input value exceeds the recommended RF power range, it is adjusted to a value lower than the upper
limit of the range and if it is less than the recommended range, it is adjusted to a value higher than the
lower limit of the range. The RF power level can be configured in decimals too.
Table 33 lists the recommended RF power range for different channel settings on the
Cisco UBR-MC20X20V line card.
Table 34 lists the recommended RF power range for different channel settings on the Cisco uBR-MC88V
line card.
Examples The following example shows how to configure RF power for RF port 0 in modular-cable controller
mode:
Router# configure terminal
Router(config)# controller modular-cable 1/0/0
Router(config-controller)# rf-channel 0 rf-power 50.6
The following example shows how to configure RF power for RF port 0 in integrated-cable controller
mode:
Router# configure terminal
rf-channel rf-shutdown
To disable the RF output on a wideband SPA, use the rf-channel rf-shutdown command in controller
integrated-cable or controller modular-cable mode. To enable the RF output, use the no form of this
command.
Syntax Description rf-port Specifies the RF channel physical port on the Wideband SPA FPGA.
Allowed range is 0 to 3. Valid values for rf-port depend on the
configuration set with the annex modulation command.
Usage Guidelines For muting and unmuting the QAM on the Cisco RFGW-10, use the rf-channel rf-shutdown command
in the M-CMTS.
rf-channel stacking
To suppress a carrier or mute a radio frequency (RF) channel on the Cisco uBR-MC88V cable interface
line card, use the rf-channel stacking command in controller configuration mode. To remove the
configuration, use the no form of this command.
Syntax Description stacking-number RF channel stacking number. The valid range is from 1 to 4. The default value
is 4.
Usage Guidelines If you change the default stacking number configuration, traffic loss may occur on the active channels.
For example, if you change the stacking number from 4 to 2, traffic is interrupted on the RF channels 0
and 1. However, traffic loss does not occur if you do not change the stacking number configuration when
shutting down an RF channel using the rf-channel rf-shutdown command.
Note We recommend that you do not change the default stacking number configuration. You can change the
default configuration when you want RF diagnostics performed on a particular channel. For example, if
you want to perform RF diagnostics on RF channel 2, you need to change the default stacking number
configuration to 2 to completely mute this channel.
Examples The following example shows how to configure the RF channel stacking number for the
Cisco uBR-MC88V cable interface line card:
Router# configure terminal
Router(config)# controller integrated-cable 5/1
Router(config-controller)# rf-channel stacking 3
secondary aux
To enable the auxiliary port on the standby PRE1 module, use the secondary aux command in
redundancy configuration (main-cpu) mode. To disable the auxiliary port, use the no form of this
command.
secondary aux
no secondary aux
Command Default The auxiliary port on the standby PRE1 module is disabled.
Examples The following example shows how to enable the auxiliary port on the standby PRE1 module.
Router# config t
Router(config)# redundancy
Router(config-r)# main-cpu
Router(config-r-mc)# secondary aux
Router(config-r-mc)# exit
Router(config-f)# exit
Router(config)#
service-class (cmts-tag)
To configure the specified service class name for the CMTS tag, use the service-class command in the
cmts-tag configuration mode. To remove the configured service class name from the CMTS tag, use the
no form of this command.
no service-class service-class-name
Syntax Description exclude (Optional) Configures the CMTS tag to exclude the specified service class
name.
service-class-name Service class name with matching rule
Examples The following example shows how to configure the specified service class name for the CMTS tag using
the service-class command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# service-class uBR
service-class (enforce-rule)
To identify a particular service class for cable modem monitoring in an enforce-rule, use the
service-class (enforce-rule) command in enforce-rule configuration mode. To remove the service class
from the enforce-rule, use the no form of this command.
Usage Guidelines The service-class (enforce-rule) command allows operators to identify the name of the initial registered
service class for a CM in an enforce-rule, and also the name of a new service class to be enforced if the
CM violates its registered service parameters.
Examples The following example shows specification of the enforced service class called “test” in an enforce-rule:
Router(enforce-rule)# service-class enforced test
Command Description
monitoring-basics Specifies the type of monitoring desired for subscriber traffic management
on a Cisco CMTS router.
peak-time1 Specifies peak and offpeak monitoring times on a Cisco CMTS router.
qos-profile registered Specifies the registered QoS profile that should be used for this enforce-rule.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
service divert-rate-limit
Note Effective with Cisco IOS Release 12.2(33)SCB, the service divert-rate-limit fib-rp-glean command is
replaced on the WAN-side by the service divert-rate-limit ip fib-rp-glean command. See the
service divert-rate-limit ip command for more information. The service divert-rate-limit fib-rp-glean
command is replaced on the WAN-side non-IP by service divert-rate-limit non-ip fib-rpf-glean
command. See the service divert-rate-limit non-ip command for more information. For cable-side DRL
configuration, see the cable divert-rate-limit command.
Syntax Description divert-code rate Configures the PXF Divert-Rate-Limit for the any of the following packets:
• fwd-glean—Packets that hit a glean adjacency in the FIB.
• rpf-glean—Packets that hit a glean adjacency during the RPF check.
The minimum rate is 1 packet-per-second and the maximum rate is 255
packets-per-second.
The default rate is 20 packets-per-second.
limit limit (Optional) Sets the limit for the number of packets that will be diverted in an
initial burst of packets.
The minimum limit is 4 packets and the maximum limit is 255 packets.
The default limit is 5 packets.
Note Setting the limit has a limited effect on the behavior of the algorithm,
so this part of the CLI is hidden.
Command History 12.3(17a)BC The command was introduced for the Cisco uBR7246VXR and
Cisco uBR10012 universal broadband routers.
12.2(33)SCA This command was integrated into Cisco IOS release 12.2(33)SCA.
Support for the Cisco uBR7225VXR router was added.
12.2(33)SCB This command was replaced by the service divert-rate-limit ip
fib-rp-glean command and service divert-rate-limit non-ip fib-rpf-glean
command.
Usage Guidelines The service divert-rate-limit command is used to configure the PXF Divert-Rate-Limit for fwd-glean
and rpf-glean packets in order to identify packet streams that will cause congestion of the FP-to-RP
interface.
Examples The following example shows how to configure rate-limiting for fib-rp-glean, with a rate of 10
packets-per-second and a limit of 20 packets:
Router(config-if)# service divert-rate-limit fib-rp-glean 10 limit 20
The following example shows how to return rate-limiting for fib-rp-glean to the default values:
Router(config-if)# no service divert-rate-limit fib-rp-glean
Pass and fail counters are kept for fwd-glean, rpf-glean, and cable-ARP packets. To show the statistics
for the pass and fail counter, use the show pxf cpu statistics drl command:
Router(config-if)# show pxf cpu statistics drl
Divert-Rate-Limit statistics
code total diverted dropped
fib_rpf_glean 500 59 441
fib_rp_glean 500 54 446
arp_filter 0 0 0
Note The arp_filter stats shown above are global stats for PXF ARP Filtering. These stats cannot be cleared
by the CLI. However, they will reset to zero upon reload.
Packets dropped by Divert-Rate-Limit and the ARP Filter will be recorded in the regular PXF drop
statistics:
Router(config-if)# show pxf cpu statistics drop c5/0/0
FP drop statistics for Cable5/0/0
packets bytes
vcci undefined 0 0
vcci C
...
divert_rate_limit 441 28224
arp_filter_reply 0 0
arp_filter_request 0 0
service divert-rate-limit ip
To set DRL rate and limit for WAN-side IP packet streams, use the service divert-rate-limit ip
command in global configuration mode. To reset the rate and limit to the default values for all IP
divert-codes, use the no form of this command. Using no service divert-rate-limit ip divert-code will
reset rate and limit to the default values for the specified divert code.
no service divert-rate-limit ip
Command Default For WAN-side IP packet streams, the default rate is 4000 packets per second and default limit is 4000
packets. These defaults apply to each uniquely identified IP packet stream.
Usage Guidelines You can configure a rate and limit for a particular IP divert-code for WAN-side IP packets. However,
each IP packet-stream is uniquely identified (using a hash of the VRF, the IP source address, and the
divert-code), and then packets in that stream are sent through a rate-limiter with the configured rate and
limit.
Examples The following example shows how to set the rate and limit for the specified divert code:
Router(config)# service divert-rate-limit ip fib-rp-glean rate 1 limit 4
Related Commands
Command Description
service This command configures DRL for WAN-side non-IP packet streams.
divert-rate-limit
non-ip
service This command adds entries to the trusted site list.
divert-rate-limit
trusted-site
service divert-rate-limit ip trusted-site ip-address mask ip-address tos tos-value mask tos-mask
vrf vrf-name
Syntax Description ip-address Specifies the source IP address that should be matched.
Example: 64.12.13.0
mask ip-address The mask to apply to the source IP address of the packet before testing if it
matches. There are no restrictions on the mask value.
Example: 255.255.0.255
tos tos-value The ToS value of the trusted site. There are no restrictions on the tos_value.
Example: 0xD0
mask tos-mask The mask to apply to the IP ToS value and the trusted-site tos_value before
testing if it matches. There are no restrictions on the tos_mask value.
Example: 0xF3
Note The ToS value can be wild-carded by setting the tos_mask to 0x00
vrf vrf-name The VRF that this trusted site applies to.
For the global VRF, use the global keyword. To apply the trusted-site to all
VRFs (including the global VRF), hit enter after specifying the tos-mask.
If a non-existent VRF is specified, the table entry is filled, but the
information is not written to toaster memory. If the specified VRF is
subsequently created, the information is written to toaster at that time.
Usage Guidelines The service divert-rate-limit ip trusted-site command is used to configure trusted site list that contains
a source IP address and mask, IP ToS value and mask, and a VRF. If no IP address is specified, the entire
trusted site list is cleared. The trusted site list contains a source IP address and mask, IP ToS value and
mask, and a VRF. The trusted site list applies only to WAN-IP IPv4 packets. There is a limitation of four
trusted sites.
Examples The following example shows how to configure trusted site list:
Router(config)# service divert-rate-limit trusted-site 64.12.13.0 255.255.0.255
tos 0xD0 mask 0xF3 vrf name1
Command Default For WAN-side non-IP packets, the default rate is 2000 packets per second and default limit is 2000
packets.
Usage Guidelines You can configure a rate and limit for a particular non-IP divert-code, and all packets arriving with that
divert-code are sent through a single rate-limiter with the configured rate and limit. but the explanation
is fairly straightforward: there is a single rate-limiter for each non-IP divert-code. No attempt is made to
uniquely identify the source of the attacking packet stream.
Examples The following example shows how to set and limit default values for the specified divert code:
Router(config)# service divert-rate-limit non-ip fib-rpf-glean rate 5 limit 25
Related Commands
Command Description
service This command configures DRL rate and limit for WAN-side IP packet
divert-rate-limit ip streams.
Syntax Description ip-address Specifies the source IP address that should be matched.
Example: 64.12.13.0
mask ip-address The mask to apply to the source IP address of the packet before testing if it
matches. There are no restrictions on the mask value.
Example: 255.255.0.255
tos tos-value The ToS value of the trusted site. There are no restrictions on the tos_value.
Example: 0xD0
mask tos-mask The mask to apply to the IP ToS value and the trusted-site tos_value before
testing if it matches. There are no restrictions on the tos_mask value.
Example: 0xF3
Note The ToS value can be wild-carded by setting the tos_mask to 0x00
vrf vrf-name The VRF that this trusted site applies to.
For the global VRF, use the global keyword. To apply the trusted-site to all
VRFs (including the global VRF), hit enter after specifying the tos-mask.
If a non-existent VRF is specified, the table entry is filled, but the
information is not written to toaster memory. If the specified VRF is
subsequently created, the information is written to toaster at that time.
Usage Guidelines The service divert-rate-limit ip trusted-site command is used to configure trusted site list that contains
a source IP address and mask, IP ToS value and mask, and a VRF. The trusted site list contains a source
IP address and mask, IP ToS value and mask, and a VRF. The trusted site list applies only to WAN-IP
IPv4 packets. There is a limitation of four trusted sites.
To remove specified entry from the trusted site list, use no service divert-rate-limit trusted-site
ip-address mask ip-address tos tos-value mask tos-mask [global | vrf vrf-name]. If no IP address is
specified, the entire trusted site list is cleared.
Examples The following example shows how to configure trusted site list:
Router(config)# service divert-rate-limit trusted-site 64.12.13.0 255.255.0.255
tos 0xD0 mask 0xF3 vrf name1
service instance
To configure an Ethernet service instance, use the service instance command in Layer 2 VPN
configuration mode. To disable this configuration, use the no form of this command.
Usage Guidelines You must provision a Multiprotocol Label Switching (MPLS) pseudowire before configuring an Ethernet
service instance in Layer 2 VPN configuration mode.
Examples The following example shows how to configure an Ethernet service instance on a Cisco uBR10012
router:
Router # configure terminal
Router(config) # cable l2vpn 001e.6bfb.0f9e customer2
Router(config-l2vpn) # service instance 7000 ethernet
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.
These are the only commands required to enable the ToD server.
Usage Guidelines The max-servers no-limit option allows a large number of cable modems to obtain the ToD server at
one time, in the event that a cable or power failure forces many cable modems offline. When the problem
has been resolved, the cable modems can quickly reconnect.
Note Do not disable the minor UDP servers if you are also enabling the other DHCP or TFTP servers.
For additional information about DHCP configuration on the Cisco CMTS, refer to the following
documents on Cisco.com:
• Filtering Cable DHCP Lease Queries on the Cisco CMTS
• DHCP and Time-of-Day Services on the Cisco CMTS
service-class
To create a DOCSIS configuration file that specifies the quality-of-service (QoS) service-class options
for the CM configuration file, use the service-class command in cable config-file configuration mode.
To disable the specification, use the no form of this command.
no service-class
Syntax Description class Specifies service class number. Valid range is 1 to 16. Default value is 1.
guaranteed-upstream Specifies the guaranteed upstream bandwidth in kbps. Valid range for
us-bandwidth us-bandwidth is 0 to 100000 kbps. Default value is 0.
max-burst burst-size Specifies the maximum upstream burst size in bytes. Valid range for
burst-size is 0 to 65535. Default value is 0, unlimited burst length.
Recommended value range is 1600 to 1800 bytes. Using a value of 0 or greater
than 1800 bytes can cause latency issues for Voice-over-IP. A value of less than
1500 bytes prevents upstream transmission of large Ethernet frames for any
modem or CMTS not implementing fragmentation (an optional feature in
DOCSIS 1.0).
max-downstream Specifies the downstream bandwidth in kbps. Valid range for
max-dsbandwidth max-dsbandwidth is 0 to 100000 kbps. Default value is 0.
max-upstream Specifies the upstream bandwidth in kbps. Valid range for max-usbandwidth
max-usbandwidth is 0 to 100000 kbps. Default value is 0.
priority priority-num Specifies the service class priority. Valid range for priority-num is 0 to 7,
where 7 is the highest-priority service-class setting.
privacy Enables baseline privacy interface (BPI).
Command Default Service-class is not set by default. A CM cannot register on a Cisco CMTS unless at least one parameter in
a service class is specified.
Usage Guidelines Default values can be used only if service-class class is specified. A single configuration file should not
contain multiple service-class ID numbers. Thus, all parameters should be set using a single service-class ID.
However, different configuration files can reuse the same service-class ID.
Note To enable Baseline Privacy Interface (BPI) operations on the cable command, you must specify both the
service-class privacy and privacy commands for the cable modem’s DOCSIS configuration file.
Examples The following example shows how to specify the service-class command for a DOCSIS configuration
file:
router(config)# cable config-file upgrade.cm
router(config-file)# service-class 1 priority 0
router(config-file)# service-class 1 max-upstream 3247
router(config-file)# service-class 1 max-downstream 10000
router(config-file)# service-class 1 max-burst 1600
router(config-file)# service-class 1 privacy
router(config-file)# privacy
router(config-file)# exit
service-type-id
To add a service type ID that is compared against the cable modem provisioned service type ID, to
determine an appropriate restricted load balancing group (RLBG), use the service-type-id command in
the config-lb-group configuration mode. To remove the service type ID, use the no form of this
command.
service-type-id string
no service-type-id string
Syntax Description string Identifier of the service type that gets added to the load balancing group.
Usage Guidelines You can use the service-type-id command to add a service type ID only to a RLBG.
Examples The following example shows how to add a service type ID on the CMTS, using the service-type-id
command.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable load-balance docsis-group 1
Router(config-lb-group)# restricted
Router(config-lb-group)# service-type-id commercial
Router(config-lb-group)# no service-type-id commercial
Router(config-lb-group)#
service-type-id (cmts-tag)
To configure the specified service type ID for the CMTS tag, use the service-type-id command in the
cmts-tag configuration mode. To remove the service type ID, use the no form of this command.
no service-type-id service-type-id
Syntax Description exclude (Optional) Configures the CMTS tag to exclude the specified service type
ID.
service-type-id Sets a matching rule with the specified service type ID.
Examples The following example shows how to configure the specified service type ID for the CMTS tag using the
service-type-id command:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable tag 1
Router(cmts-tag)# service-type-id commercial
session-range
To identify the multicast QoS group session range, use the session-range command in multicast QoS
configuration mode. To disable the QoS group session range, use the no form of this command.
Syntax Description ip-address Specifies the IP address of the multicast QoS group.
ip-mask Specifies the IP mask of the multicast QoS group.
Command Default A session range IP address and IP mask are not defined for a specific multicast QoS group.
Usage Guidelines Use the session-range command to configure the session range to specify the number of multicast
sessions to be admitted on a particular service flow. CMTS does not admit new sessions (no forwarding)
if the current number of sessions has reached the defined limit, and waits until a session ends to free up
a slot for new sessions. You can configure multiple session ranges.
Examples The following example defines a session range IP address and IP mask using the session-range
command:
Router(config)# cable multicast qos group 20 priority 55 global
Router(config-mqos)# session-range 224.10.10.01 255.255.255.254
set clock
To set the system clock on the Cisco CMTS, use the set clock command in global configuration mode.
set clock time-date
Syntax Description time-date Time and date for which to set the clock on the Cisco CMTS.
Command Default Time-of-Day, DHCP, and TFTP server configuration not defined on the Cisco CMTS by default.
Usage Guidelines To supply an accurate clock, the system clock on the Cisco CMTS should be configured for the correct
time, either by using the set clock command or by configuring the Cisco CMTS to act as a Network Time
Protocol (NTP) or Simple Network Time Protocol (SNTP) client.
For proper operation of the DOCSIS network, especially a DOCSIS 1.1 network using BPI+ encryption
and authentication, the system clock on the Cisco CMTS must be set accurately. You can achieve this by
manually using the set clock command, or by configuring the CMTS to use either the Network Time
Protocol (NTP) or the Simple Network Time Protocol (SNTP).
For additional information about the set clock command, refer to the following documents on Cisco.com:
• Time-of-Day Server for the Cisco CMTS
• DHCP, ToD, and TFTP Services for the Cisco Cable Modem Termination System
Command Description
ip dhcp relay information Configures the DHCP server to validate the relay agent information option
option in forwarded BOOTREPLY messages.
ip dhcp smart-relay Enables the DHCP relay agent on the CMTS to automatically switch a
cable modem or CPE device to a secondary DHCP server or address pool
if the primary DHCP server does not respond to three successive requests.
New Commands
Modified Commands
Replaced Commands
show application-buckets
To displays rules for any or all buckets supporting Service Flow Admission Control on the Cisco CMTS,
use the show application-buckets command in privileged EXEC mode. The configured rules for any
given bucket are displayed in order of precedence in the Rule field.
show application-buckets [ bucket-no n ]
Syntax Description bucket-no n You may specify a specific bucket number on the Cisco CMTS to display
parameters for that bucket and no others. Valid range is 1 to 8, or all buckets if
no specific bucket is designated.
Command Default No default behavior or values for this command. However, Cisco IOS Release 12.3(21)BC supports
default operation and non-default configuration for feature on the Cisco CMTS.
Usage Guidelines For additional information for Service Flow Admission Control, commencing in Cisco IOS Release
12.3(21)BC, refer to the following document on Cisco.com:
• Service Flow Admission Control for the Cisco Cable Modem Termination System
Examples The following example illustrates sample output of the show application-buckets command.
Router# show cable application-type
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Examples The following example shows sample output for this show bridge cable-modem command:
Router# show bridge cable-modem 0
Field Description
Total of 300 station blocks Total number of forwarding database elements in the system. The
memory to hold bridge entries is allocated in blocks of memory
sufficient to hold 300 individual entries. When the number of free
entries falls below 25, another block of memory sufficient to hold
another 300 entries is allocated. Thus, the total number of forwarding
elements in the system is expanded dynamically, as needed, limited by
the amount of free memory in the router.
Bridge Group The number of the bridge group to which this interface is assigned.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Usage Guidelines This command offers flexible syntax that enables display of Admission Control as specifically
configured on the Cisco CMTS. Refer to examples for additional information.
Examples The following example illustrates upstream and downstream Admission Control information for the
specified cable interface:
Router# show cable admission-control interface 7/0/0
Interface Cable7/0/0
Table 36 show cable admission-control Field Descriptions for Upstream and Downstream
Throughput
Field Description
Sched Type Available for upstream only. This field displays the following information:
• UGS—UGS thresholds configured and traffic rates.
• RTPS—RTPS thresholds configured and traffic rates.
• BE—Best Effort thresholds configured and traffic rates.
Flow Type Available for Downstream only. This field displays voice and data information:
• voice—Voice thresholds configured and traffic rates.
• data—Data thresholds configured and traffic rates.
Table 36 show cable admission-control Field Descriptions for Upstream and Downstream
Throughput (continued)
Field Description
Class Name Available for upstream only,
Minor Level Minor threshold as currently defined in a percentage on the Cisco CMTS.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Major Level Major threshold as currently defined in a percentage on the Cisco CMTS.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Exclusive Level Percentage of exclusive throughput that is reserved for the corresponding
traffic type on the Cisco CMTS. Applies to downstream or upstream traffic.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Non-Excls Level Percentage of non-exclusive throughput configured on the Cisco CMTS.
Commonly used with Best Effort (lowest priority) traffic.
Curr Reserv Percentage of throughput reserved exclusively for the corresponding flow type.
Conf Level Configuration level that indicates the scope of configuration is actually applied
for that US/ DS (whether the global, interface, or the upstream level is applied).
Values in this field can be as follows:
• U—Upstream
• I—Interface
• G—Global
The following example illustrates all Admission Control information for the specified upstream port:
Router# show cable admission-control interface c8/0/1 upstream all
The following example illustrates upstream and downstream Admission Control information for the
specified interface:
Router# show cable admission-control interface c8/0/1
Interface c8/0/1:
Type Level Times Level Times Level Times Level Reserv Level
voice 35 10 40 8 45 6 0 38 I
The following example illustrates all Admission Control information for the specified upstream port:
Router# show cable admission-control interface w1/0/0:5
Configured AC Max Reservable Bandwidth = 14000000 bps
Table 37 show cable admission-control Field Descriptions for Upstream and Downstream
Throughput
Field Description
Bucket No Specific bucket number.
Names Bucket name.
Minor Level Minor threshold as currently defined in a percentage on the Cisco CMTS.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Major Level Major threshold as currently defined in a percentage on the Cisco CMTS.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Excls Level Percentage of exclusive throughput that is reserved for the corresponding
traffic type on the Cisco CMTS. Applies to downstream or upstream traffic.
# of Times Number of times traffic has crossed this threshold since the counters on the
Cisco CMTS were last cleared.
Non-Ex Level Percentage of non-exclusive throughput configured on the Cisco CMTS.
Commonly used with Best Effort (lowest priority) traffic.
Curr Resv Percentage of throughput reserved exclusively for the corresponding flow type.
Conf Level Configuration Level that indicates the scope of configuration is actually
applied for that US/ DS (whether the global, interface, or the upstream level is
applied). Values in this field can be as follows:
• U—Upstream
• I—Interface
• G—Global
# of Rejec Number of rejections.
The following example illustrates upstream and downstream Admission Control information with the
global keyword:
Router# show cable admission-control global
Table 38 describes the significant fields for the global keyword used in the example above.
Field Description
CM-Registration event Counter increments once for every cable modem that crosses a threshold
during its registration. For example, if the minor, major, and critical
thresholds on the Cisco CMTS are 60%, 70%, and 80% respectively, and a
cable modem tries to register when the current value is 80%, then the cable
modem is allowed to register, but the counters for minor, major and critical
thresholds are each incremented by one.
Voice-Call event Counter increments if the resource check fails when a voice-call is made. For
example, assume both the MTAs are on the same Cisco CMTS, and minor,
major, and critical thresholds for I/O memory are 50%, 60%, and 70%,
respectively. Then assume the current I/O memory value is 75%. In this
scenario, before the gate creation, Admission Control performs an I/O
memory check. This results in the counters for minor, major, and critical
thresholds each being incremented by one, and the voice call fails. No
packetcable gates are created because the voice calls fail.
Command Description
cable Configures Admission Control downstream bandwidth thresholds on the
admission-control Cisco CMTS.
ds-bandwidth
cable Defines the maximum reserved bandwidth per bonding group for all service
admission-control flows that are allowed by the Cisco CMTS.
max-reserved-bandwi
dth
cable Configures Admission Control upstream bandwidth thresholds on the Cisco
admission-control CMTS.
us-bandwidth
clear cable admission Clears all Admission Control resource counters on the Cisco CMTS.
control counters
debug cable Enables automatic Admission Control troubleshooting processes on the
admission-control Cisco CMTS.
Syntax Description cable slot/port Displays information for all CMs on the specified cable interface and
downstream port on the Cisco uBR7246VXR router.
On the Cisco uBR7246VXR router, slot can range from 3 to 6, and port can
be 0 or 1, depending on the cable interface.
cable slot/subslot/port Displays information for all CMs on the specified cable interface on the
Cisco uBR10012 router. The following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
[ip-requests-filtered (Optional) Displays the Service IDs (SIDs) that are generating or forwarding
number] more filtered ARP requests for IP packets than the specified minimum
number of packets. The valid range for number is 1 to 65535, with no default.
Note This field shows the modems that are forwarding IP traffic that could
be an part of an attack, such as TCP SYN floods, ping scans, and so
forth.
[requests-filtered (Optional) Displays the Service IDs (SIDs) that are generating or forwarding
number] more filtered ARP requests than the specified minimum number of packets.
The valid range for number is 1 to 65535, with no default.
[replies-filtered (Optional) Displays the Service IDs (SIDs) that are generating or filtering
number] more filtered ARP replies than the specified minimum number of packets.
The valid range for number is 1 to 65535, with no default.
Usage Guidelines The cable arp filter command enables the filtering of ARP request and reply packets on a cable
interface. ARP packets might need to be filtered when a user on the cable network generates a large
volume of ARP traffic as part of a theft-of-service or denial-of-service attack, or when a virus is using
ARP requests to find other computers that it might infect.
The show cable arp-filter command displays the total number of ARP reply packets that have been
received and the number of ARP request packets that have been sent on the cable interface, as well as
the number of such packets that have been filtered.
Tip To clear the counters on all interfaces, use the clear counters command. To clear the counters on a
specific interface, use the clear counters cable interface command.
Examples The following example shows the typical output from the show cable arp-filter command on a
Cisco uBR10012 router. The displays for other Cisco CMTS platforms are similar.
Router# show cable arp-filter Cable5/0/0
Router#
Field Description
Replies Rcvd
Total Total number of ARP reply packets received on the cable interface since
power-on.
Unfiltered Number of ARP reply packets that the cable interface received and accepted
while filtering was enabled using the cable arp filter reply-accept
command.
Filtered Number of ARP reply packets that the cable interface dropped while filtering
was enabled, because they would have otherwise exceeded the allowable
threshold value that was configured for the interface using the cable arp
filter reply-accept command.
Requests Sent For IP
Total Total number of ARP request packets that the cable interface was asked to
forward since power-on.
Unfiltered Number of ARP request packets that the cable interface sent while filtering
was enabled using the cable arp filter request-send command.
Filtered Number of ARP request packets that the cable interface dropped, because
they would have otherwise exceeded the allowable threshold value that was
configured for the interface using the cable arp filter request-send
command.
Field Description
Requests Forwarded
Total Total number of ARP request packets that the cable interface was asked to
forward to the ARP proxy since power-on.
Unfiltered Number of ARP request packets that the cable interface sent to the ARP
proxy while filtering was enabled using the cable arp filter request-send
command.
Filtered Number of ARP request packets for the ARP proxy that the cable interface
dropped, because they would have otherwise exceeded the allowable
threshold value that was configured for the interface using the cable arp
filter request-send command.
Note All counters are 16-bit counters, with a maximum value of 65,535 packets. If the number of
packets exceeds this amount, the counter wraps back to zero and begins incrementing again.
Note The Total counts in the show cable arp-filter command continue to increment, regardless of whether
ARP filtering has been enabled. The Unfiltered and Filtered counts increment only when ARP filtering
has been enabled using the cable arp filter command. When cable ARP filtering is disabled, these
counters retain their current values until manually reset, using the clear counters command.
The following example shows how to display the devices that are generating or filtering more than 100
ARP requests per reporting period. Repeat the command to see how quickly the device is generating
ARP packets.
Router# show cable arp-filter c7/0/0 requests-filtered 100
Router#
The following example shows how to display the devices that are generating or filtering more than 200
ARP replies per reporting period. Repeat the command to see how quickly the device is generating ARP
packets.
Router# show cable arp-filter c5/0/0 replies-filtered 200
Router#
The following example shows how to display the devices that are generating or filtering more than 10
ARP requests for IP packets per reporting period. Repeat the command to see how quickly the device is
generating ARP packets.
Router# show cable arp-filter c3/0 ip-requests-filtered 10
Router#
Field Description
SID Service ID (SID) of the device.
MAC Address Hardware (MAC-layer) address of the cable modem or CPE device.
IP Address IP address of the cable modem or CPE device.
Req-Filtered Total number of ARP requests that the device has generated or forwarded.
Req-For-IP-Filtered Total number of ARP requests that the device has generated or forwarded for
IP packets.
Rep-Filtered Total number of ARP replies that the device has generated or forwarded.
Note The Req-Filter and Rep-Filtered counters are 16-bit counters, with a maximum value of 65,535
packets. If the number of packets exceeds this amount, the counter wraps back to zero and
begins incrementing again.
Router#
Note The clear counters command clears all of the packet counters on an interface, not just the ARP packet
counters.
Syntax Description n Specifies the bundle identifier. Valid range is from 1 to 255.
forwarding-table Displays the forwarding table for the specified interface.
Usage Guidelines • Beginning with Cisco IOS Release 12.3(21)BC, all cable bundles are automatically converted and
configured to be in a virtual bundle after loading the software image.
• In releases prior to Cisco IOS Release 12.3(21)BC, if you delete the virtual bundle interface, the
virtual bundle disappears.
• Beginning with Cisco IOS Release 12.3(21)BC, standalone cable interfaces must be manually
configured to be in a virtual bundle to operate properly.
• The virtual bundle interface accumulates the counters from members; counters on member links are
not cleared when they are added to the bundle. If a bundle-only counter is desired, clear the bundle
counter on the members before adding them to the bundle, or before loading the image (for
Cisco IOS Release 12.3(21)BC and later).
Refer to the following document on Cisco.com for additional information about cable interface bundling
and virtual interface bundling on the Cisco CMTS:
• Cable Interface Bundling and Virtual Interface Bundling on the Cisco CMTS
Examples The following is a typical example of the show cable bundle command:
Router# show cable bundle 1 forwarding-table
Table 0-41 describes the fields shown in the show cable bundle command display.
Field Description
MAC address Identifies the MAC (hardware) address for each interface in the bundle.
Interface Identifies the cable interface slot and port number.
Flag The current value of the flag byte for this bundle entry. The following bits can be
set:
• Bit 0 (0x01) = Bundle is active.
• Bit 1 (0x02) = Bundle is a static multicast group.
Note If more than one bit is set, add the values together. For example, 3
indicates an active, static multicast group.
Location The location in the router’s memory for the flags byte for this bundle entry. This
value is useful only to TAC engineers during debugging.
link The value of the link pointer for this bundle entry. This value is useful only to
TAC engineers during debugging.
sublink The value of the sublink pointer for this bundle entry. This value is useful only
to TAC engineers during debugging.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
The following example shows typical output for the show cable bundle fowarding-table command,
supporting virtual interface bundling on the Cisco CMTS in later 12.3 BC Cisco IOS releases:
Router# show cable bundle 1 forwarding-table
Syntax Description bundle# The alphanumeric identifier for the virtual interface bundle.
group Multicast group membership identifier.
MAC addr Optional parameter specifies the MAC address for which to return
information.
IP addr Optional parameter specifies the IP address for which to return information.
Usage Guidelines • Beginning with Cisco IOS Release 12.3(21)BC, all cable bundles are automatically converted and
configured to be in a virtual bundle after loading the software image.
• In releases prior to Cisco IOS Release 12.3(21)BC, if you delete the virtual bundle interface, the
virtual bundle disappears.
• Beginning with Cisco IOS Release 12.3(21)BC, standalone cable interfaces must be manually
configured to be in a virtual bundle to operate properly.
• The virtual bundle interface accumulates the counters from members; counters on member links are
not cleared when they are added to the bundle. If a bundle-only counter is desired, clear the bundle
counter on the members before adding them to the bundle, or before loading the image (for
Cisco IOS Release 12.3(21)BC and later).
Refer to the following document on Cisco.com for additional information about cable interface bundling
and virtual interface bundling on the Cisco CMTS:
• Cable Interface Bundling and Virtual Interface Bundling on the Cisco CMTS
Examples The following example illustrates this new command. This command translates the bundle’s multicast
MAC address to Multicast IP address information, including the associated multicast source.
Router# show cable bundle bundle1.1 multicast
The following example illustrates multicast information for the specified virtual bundle:
Router# sh cable bundle 1 multicast
CableBundle Interface Source IP Multicast IP MAC Address
1 Bundle1 * 239.0.0.100 0100.5e00.0001
To translate a MAC address back to Multicast IP address, use the following optional syntax:
show cable bundle bundle# multicast [ <MAC addr | IP addr >]
The following example illustrates this enhanced show command:
Router# show cable bundle bundleID multicast 0100.5e00.0001
MAC address Interface Flags Location link sublink
0100.5e00.0001 Bundle1 1 646FE4D8 0 646FE4EC
0100.5e00.0001 Cable6/0/0 1 646FE4EC 0 0
^^^^^^^^^^^^^^
Note This command has been deprecated and removed in the current versions of the Cisco IOS software for
all Cisco CMTS routers.
Usage Guidelines This command displayed configuration of the cable burst profiles, which were what DOCSIS initially
used to control the data, ranging, and station maintenance bursts. The Cisco CMTS routers now support
a more comprehensive set of modulation profiles, which are displayed by the show cable
modulation-profilecommand.
Note The show cable burst-profile command displayed fields and values that were supported only in the
initial versions of the DOCSIS specification. The current DOCSIS 1.0 and 1.1 specifications use
different parameters and values, as shown by the show cable modulation-profile command.
Examples The following example shows typical output from the show cable burst-profile command:
Router# show cable burst-profile
Burst Type Preamb Diff FEC err FEC Scrambl Max Guard Last Scrambl profile
number length size size shortened
1 1 48 no 0x0 0x6 0x152 1 16 1 yes
2 1 48 no 0x0 0x6 0x152 1 12 1 no
3 1 48 no 0x5 0x2C 0x152 0 48 1 yes
4 1 48 no 0x5 0x2C 0x152 0 48 1 yes
5 1 48 no 0x5 0x32 0x152 0 20 1 yes
6 1 48 no 0x0 0x32 0x152 0 20 1 no
Router#
Table 0-42 describes the fields shown in the show cable burst-profile command display.
Field Description
Burst profile number The number of the burst profile.
Type Type of burst profile.
Preamb length Length of the preamble.
Diff encode Shows if there is a diff encode.
FEC err correct Shows the forward error correction.
FEC codeword length Shows the length of the forward error correction codeword.
Scrambl seed Shows the seed of the scrambler.
Max size Designates the maximum burst size.
Guard size Indicates the guard time size.
Last codeword shortened Shows the last codeword shortened.
Scrambl Indicates whether scramble is enabled (yes) or not (no).
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description interface Selects the interface for which to enable PacketCable E911 call history.
slot | slot/subslot Designates the slot or slot and port for a particular cable interface on the
Cisco router.
The following are the valid values for the Cisco uBR7246VXR router:
• slot can range from 3 to 6
The following are the valid values for the Cisco uBR10012 router:
• slot = 5 to 8
• subslot = 0 or 1
Usage Guidelines This command supports the PacketCable Emergency 911 Services Listing and History feature on the
Cisco CMTS. Cisco IOS release 12.3(13a)BC introduces enhanced informational support for
PacketCable Emergency 911 calls on the Cisco CMTS, to include the following information and related
history:
• active Emergency 911 calls
• recent Emergency 911 calls
• regular voice calls
• voice calls made after recent Emergency 911 calls
To set the call window (in minutes) during which the Cisco CMTS maintains records of Emergency 911
calls, use the cable high-priority-call-window command in global configuration mode. To remove the
call window configuration from the Cisco CMTS, use the no form of this command:
cable high-priority-call-window minutes
no cable high-priority-call-window
The following command example configures the call window on the Cisco uBR10012 router to be one
minute in length:
Router(config)# cable high-priority-call-window 1
Additional information for voice call support with PacketCable and PacketCable MultiMedia (PCMM)
is available in the following document on Cisco.com:
• PacketCable and PacketCable Multimedia for the Cisco CMTS
Examples The following example illustrates call status on the Cisco CMTS:
Router# show cable calls
Total 0 0 0 2
Router #
The following command example illustrates that one Emergency 911 call was made on the Cable8/1/1
interface on the Cisco uBR10012 router during the window set for high priority calls:
Router# show cable calls
Interface ActiveHiPriCalls ActiveAllCalls PostHiPriCallCMs RecentHiPriCMs
Cable5/0/0 0 0 0 0
Cable5/0/1 0 0 0 0
Cable5/1/0 0 0 0 0
Cable5/1/1 0 0 0 0
Cable5/1/2 0 0 0 0
Cable5/1/3 0 0 0 0
Cable5/1/4 0 0 0 0
Cable6/0/0 0 0 0 0
Cable6/0/1 0 0 0 0
Cable7/0/0 0 0 0 0
Cable7/0/1 0 0 0 0
Cable8/1/0 0 0 0 0
Cable8/1/1 1 1 0 0
Cable8/1/2 0 0 0 0
Cable8/1/3 0 0 0 0
Cable8/1/4 0 0 0 0
Total 1 1 0 0
Syntax Description slot (Optional) Identifies a TCC interface on the Cisco RF Gateway 10. Valid
TCC slots are 13 and 14.
client port id Specifies the DTI client port ID. Valid port values are 1 and 2.
server port id Specifies the DTI server port ID. Valid port values are 1 and 2.
counters Specifies the DTI client counters.
Command Default Information on the TCC DTI client and server is displayed. Counters are not displayed.
Usage Guidelines This command supports the Cisco CMTS clock feature set, which provides a synchronized clock for
improved Voice-over-IP (VoIP) operations. The clock feature set requires one of the following
configurations:
• A Cisco uBR10012 router with one or two TCC+ cards that are connected to an external national
clock source.
Note Beginning in Cisco IOS Release 12.3(23)BC, TCC+ is replaced with DOCSIS Timing and
Control Card (DTCC).
Only these cable interface cards support the external clock card reference from a clock card to distribute
that signal to CMs or set-top boxes (STBs) attached to the specific network segments. You can use other
cable interface cards, such as the Cisco uBR-MC16C, with the clock card, but these other cable
interfaces will not synchronize their downstream SYNC messages with the external clock source.
Each CM or STB must also support VoIP applications and the clock feature set. For example, the
Cisco uBR924, running Cisco IOS Release 12.0(7)T or later, supports clock card feature automatically.
Note This command does not appear if a clock card is not installed in the system.
Examples The following sample output from the show cable clock command on a Cisco uBR7246VXR router
shows that both external sources are available and the clock card is providing the clock reference:
Router# show cable clock
The following sample output from the show cable clock command on a Cisco uBR10012 router shows
that both external sources are available and that the TCC+ card in slot 1/1 is providing the clock
reference:
Router# show cable clock
Number of TCCplus Cards in the Chassis: 2
Active TCCplus Card is in slot: 1 subslot: 1
Backup TCCplus Card is in slot: 2 subslot: 1
Clock reference used by the active card is Primary T1
External T1 References:
Card: 1/1
Primary T1 : Available
Secondary T1: Available
Card: 2/1
Primary T1 : Available
Secondary T1: Available
The following sample output from the show cable clock command on a Cisco uBR10012 router shows
that the TCC+ card in slot 1/1 is in maintenance mode, and that the TCC+ card in slot 2/1 is providing
the clock reference:
Router# show cable clock
Number of TCCplus Cards in the Chassis: 2
TCCplus card in 1/1 under maintenance
Active TCCplus Card is in slot: 2 subslot: 1
Clock reference used by the active card is Primary T1
External T1 References:
Card: 2/1
Primary T1 : Available
Secondary T1: Available
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
The following sample output from the show cable clock command on a Cisco uBR10012 router shows
that the DTCC card in slot 1/1 is in DTI mode.
Router# show cable clock
Cisco RF Gateway 10
The following example shows the TCC DTI client and server statistic counts information:
Router# show cable clock
DTI Client status: TCC 13
-----------------
Client status : normal
Client clock type : ITU type 1
Client firmware version : 7
Client dti version : 0
Client timestamp : 657519453
Client phase correction : 65535
Client normal time : 65535
Client holdover time : 0
Client transition t3 count : 0
Client transition t4 count : 1
Client transition t6 count : 0
Client transition t7 count : 0
Client port switch count : 1
Client Integral Frequency Term : 64518
Client EFC Value : 63282
The following is sample output of a TCC card in slot 13 on a Cisco RF Gateway 10:
Router#show cable clock 13 client 1
DTI Client Port 1 Status:
-------------------------
Port Status : Inactive
Signal detected : no
CRC error count : 63006
Frame error rate : > 5%
Cable advance : 0x0000
Field Description
Port status Indicates the current status of the DTI port on the TCC card.
Signal detected Indicates whether the DTI signal was detected.
CRC error count The number of cyclic redundancy check (CRC) errors. It can
indicate intermittent upstream, laser clipping, or
common-path distortion.
The following example shows the server status of the TCC card in slot 13 on a Cisco RFGW-10:
Router#show cable clock 13 server 2
TCC Card 13 port 2 DTI Server status:
--------------------------------------
Server signal detected : yes
Server status : free-run
Root Server clock type : ITU type 3
Root Server source : none
Server Type : Root
Client Performance Stable : yes
Client Cable advance Valid : yes
TOD Setting Mode : Short
TOD gpssec : 902825745
TOD leap seconds : 14
Field Description
Server signal detected Indicates whether the server was detected.
Server status Indicates the state in which the serer is functioning. The
states are warm-up, free-run state, fast mode, normal,
holdover, or bridge mode.
Root server source The server source such as internal, external, GPSor none.
Root server clock type The clock type. The types are 1, 2, 3 or ITU Stratum 3 or DTI
Min. clock.
TOD setting mode Displays the time (user time, NTP, GPS) mode such as short
or long.
The following is a sample output showing the counters on TCC card 13 on Cisco RFGW-10:
Router#show cable clock 13 counters
TCC Card 13 DTI counters:
-------------------------
Client Normal time : 0x1EB6
Client Holdover time : 0x0000
Client Phase Correction : 0
Client Freq Correction : 63213
Client EFC Correction : 61039
Client transition count t3 : 0
Client transition count t4 : 1
Syntax Description slot/subslot Specifies the slot and subslot location of the DTCC ports. Valid values are 1/1 or
2/1.
Examples The following is a sample output from the show cable clock dti counters command in user EXEC mode:
Router> show cable clock dti counters 1/1
TCC Card 1/1 DTI counters:
-------------------------------------------
Client Normal time : 0xFFFF
Client Holdover time : 0x0000
Client Phase Correction : 0x0000
Client Freq Correction : 0xFBD7
Client EFC Correction : 0xF7AD
Client transition count t3 : 0x00
Client transition count t4 : 0x01
Client transition count t6 : 0x00
Client transition count t7 : 0x00
Usage Guidelines Use this command to display information on the DTI Client status.
Examples The following is a sample output from the show cable clock dti command:
Router# show cable clock dti status
Status of DTI component:
Active TCC card in slot 1/1
TCC Card 1/1 DTI status:
-------------------------------------------
Active Client port : 2
Active Client status : normal
Active Client Server status : freerun
Active Client frame error rate : < 2%
Active Client CRC error count : 0x06
Standby Client Signal detected : no
Note The show cable device access-group command is not supported on the Cisco uBR10012 universal
broadband router.
Syntax Description ip-addr (Optional) Specifies the IP address for a particular CM or host.
Usage Guidelines This command displays information about both CMs and their associated CPE devices. To display
information only for hosts and other CPE devices, use the show cable host access-group command. To
display information only for CMs, use the show cable modem access-group command.
If an SNMP manager is requesting information about CM or CPE devices at the same time that this
command is given, the command displays the following error message:
No information is available, please try later.
Wait until the SNMP retrieval is done and retry the CLI command.
Examples The following example shows how to display a list of the CMs and their hosts:
Router# show cable device access-group
Router#
Table 0-45 describes the fields that are shown in the show cable device access-group display:
Table 0-45 Descriptions for the show cable device access-group Fields
Field Description
MAC Address The MAC address for the CM or CPE device.
IP Address The IP address that the DHCP server has assigned to the CM or CPE device.
Type Identifies the type of device:
• host = CPE device
• modem = cable modem
Access-group Displays the access group name or number in use (if any) for this CM or CPE
device.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Command Description
clear cable host Clears the host from the table.
show cable host access-group Displays the hosts behind the CMs in the network, along with
their access groups.
show cable modem access-group Displays the access groups for the CMs on a particular cable
interface.
Syntax Description stats Displays configuration and run-time statistics about the
currently-defined DSG tunnels.
tunnel Displays the mapping of DSG tunnels to vendors or well-known MAC
addresses.
vendor CA-vendor-name (Optional) Displays information about a specific Conditional Access
(CA) vendor. This parameter can be any arbitrary string up to 8
characters in length.
tunnel-MAC-address (Optional) Displays information for the specified well-known MAC
address for the DSG tunnel. If you specify a MAC address of
0000.0000.0000, the command displays information for all DSG
tunnels, which is the default display.
Examples The following example shows a typical display for the show cable dsg tunnel form of the command:
Router# show cable dsg tunnel
Router#
The following example shows a typical display for the show cable dsg stats command:
Router# show cable dsg stats
Router#
The following example shows a typical display for the show cable dsg stats command for an individual
vendor:
Router# show cable dsg stats vendor CCC
Router#
Note The packet counters for both the stats and tunnel options for a particular DSG tunnel continue to
increase as long as traffic is received over that tunnel. If the tunnel does not receive any traffic for three
minutes or more, the counters are automatically reset to 0.
The following example shows a typical display for the show cable dsg stats command for an individual
vendor when the associated cable interface is shut down. The Received, Forwarded, and Dropped
counters are not displayed when an interface is shut down.
Router(config)# interface c5/1
Router(config-if)# shutdown
Router(config-if)# exit
Router(config)# exit
Router# show cable dsg stats vendor CCC
Router#
Table 46 describes the major fields shown in the show cable dsg command:
Field Description
DSG keepalive is set If keepalive messages have been enabled for an IP multicast group,
using the cable dsg keepalive command, this message is displayed.
Dest-ip, Group address Multicast group IP address for the DSG stream.
Src-ip, Source address Source IP address for the DSG stream. If an asterisk (*) appears as
the source IP address, it indicates that the source IP address is
0.0.0.0, which allows any IP address as the source IP address.
Mapped-MAC, Tunnel-MAC Well-known MAC address used for the DSG tunnel. If you
configured the DSG tunnel with a MAC address of 0000.0000.0000
using the cable dsg command, this field shows the MAC address
that the CMTS derived using the MAC to IP multicast addressing
mapping that is specified in RFC 1112.
Interface Cable interface on which this DSG tunnel is configured.
mapping entry is used Number of times that this particular DSG tunnel mapping has been
used to resolve the well-known MAC address from the tunnel’s
group address. This can be used as a very rough approximation of
the number set-top boxes (STBs) that have been mapped to this
DSG tunnel since the last time the counter was cleared.
Note Use the clear cable dsg command to clear this counter.
Packets Number of packets transmitted over the DSG tunnel.
CA-vendor Name for the Conditional Access (CA) vendor that owns this tunnel.
Received Number of packets received by the multicast group. This counter
includes all interfaces that are receiving traffic for the multicast
group. The field is not shown when an interface is shut down, but
the counter continues to increase as long as the multicast group is
receiving traffic. When the interface is reenabled, the counter shows
the latest number of packets received.
Field Description
Forwarded Number of packets forwarded on the cable interface for the
multicast group. This counter is reset to 0 whenever an interface is
shut down and reenabled. The field is not shown when an interface
is shut down.
Dropped Number of packets that were dropped that were for the multicast
group. This counter includes all interfaces that are receiving traffic
for the multicast group. The field is not shown when an interface is
shut down, but the counter continues to increase as long as the
multicast group is receiving traffic and dropping packets. When the
interface is reenabled, the counter shows the latest number of
packets dropped.
Note The Received and Dropped counters reflect activity for the multicast group and are not affected when a
cable interface is shut down and reenabled, as long as the multicast group continues to receive traffic.
The Forwarded counter reflects activity for the particular cable interface and is reset to zero whenever
the interface is shut down and reenabled. All packet counters are also automatically reset to zero if the
DSG tunnel does not receive traffic for three minutes or more.
show cable dsg tunnel tunnel-id [cfrs | clients | interfaces | statistics | verbose]
Usage Guidelines This command replaces the show cable dsg form of command available in Cisco IOS
Release 12.3(9a)BC.
Examples The following example displays CLI help for show cable dsg tunnel command syntax.
Router# show cable dsg tunnel 1 ?
tunnel tunnel tunnel cfr cfr tunnel in rule rule client service
id state mac-addr id state interface id state listId class
1 en 0100.5e01.0114 1 en Cable6/0 1 en 2 SI
5 en 7 en 10
11 en 8 en 2
14 en 20 en 2
Cable6/1 1 en 4
3 en 3
4 en 4
11 en 2
2 en 0100.5e01.011e 2 en Cable6/0 2 en 2 NDS-CA
10 en
3 en 0100.5e01.0128 3 en Cable6/0 3 en 3 NDS-APP
4 en 0100.5e01.0132 4 en Cable6/0 4 en 4 MOTO-CA
5 en 0100.5e01.013c 9 en Cable6/0 5 en 5 MOTO-APP
Cable6/1 5 en 5
6 dis 0100.5e01.0146 Cable6/0 6 en 6 SA-CA
Cable6/1 6 en 6
7 dis 0100.5e01.0150 7 en Cable6/1 8 en 7 SA-APP
13 dis
8 en 0100.5e01.0119 8 en NDS-DNLD
9 en 0100.5e01.0133 MOTO-DNLD
10 en 0100.5e01.0147 SA-DNLD
11 en 2222.2222.2222
12 en 3333.3333.3333 12 en
Beginning in Cisco IOS Release 12.3(17a)BC, this output was modified to add the tunnel group ID (“TG
id”) field in support of A-DSG version 1.2 as shown below:
Router# show cable dsg tunnel
tunnel TG cfr tunnel rule client service
id state mac-addr id id state I/F id state listId class
1 en 0100.5e01.0001 1 1 en C5/0 1 en 1 DSG-Rate1
6 en
7 en
8 en
2 en 0100.5e01.0002 1 2 en C5/0 2 en 2
3 en 0100.5e01.0003 1 3 en C5/0 3 en 3
4 en 0002.0002.0001 2 4 en C5/0 4 en 1
C5/1 1 en 1
5 en 0002.0002.0002 2 5 en C5/0 5 en 2 DSG-Rate2
C5/1 2 en 2
6 en 0002.0002.0003 2 9 en C5/0 6 en 21
C5/1 3 en 21
tunnel tunnel tunnel cfr cfr tunnel in rule rule client service
id state mac-addr id state interface id state listId class
1 en 0100.5e01.0114 1 en Cable6/0 1 en 2 SI
5 en 7 en 10
11 en 8 en 2
14 en 20 en 2
Cable6/1 1 en 4
3 en 3
4 en 4
11 en 2
Beginning in Cisco IOS Release 12.3(17a)BC, this output was modified to add the tunnel group ID (“TG
id”) field in support of A-DSG version 1.2 as shown below:
Router# show cable dsg tunnel 1
tunnel TG cfr tunnel rule client service
id state mac-addr id id state I/F id state listId class
1 en 0100.5e01.0001 1 1 en C5/0 1 en 1 DSG-Rate1
6 en
7 en
8 en
1 2 1 CA System ID 0X951
3 Broadcast
8 MAC Addr 1111.1111.1111
3 1 Application ID 0X1
4 1 CA System ID 0X701
10 1 Application ID 0X6
Beginning in Cisco IOS Release 12.3(17a)BC, this output was modified to add the “vendor group” field
in support of A-DSG version 1.2 as shown below:
Router# show cable dsg tunnel 1 clients
tunnel client client client client vendor
id listId id id type address group
1 1 1 MAC Addr 0100.5e00.0001
2 Application ID 0x0951
3 Broadcast Unspecified
4 Broadcast 4
Beginning in Cisco IOS Release 12.2(33)SCC, this output was modified to display the cable interfaces
in the MAC domain, and their SF ID values and dropped packet count.
Router# show cable dsg tunnel 1 statistics
Load for five secs: 1%/0%; one minute: 2%; five minutes: 1%
Time source is hardware calendar, *20:07:32.543 UTC Wed Sep 14 2009
Tunnel ID : 1
MAC Addr : 0100.5e01.0114
State : enable
Cfr Id : 1
State : enable
Priority : 1
Dest IP : 230.1.1.20
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 5
State : enable
Priority : 1
Dest IP : 230.1.1.60
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 11
State : enable
Priority : 1
Dest IP : 224.25.25.134
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 14
State : enable
Priority : 0
Dest IP : 230.1.1.20
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 1000
Dest Port End : 2000
Forwarded : 0
Received : 0
Client List Id : 2
Client Id : 1
Client Id Type : CA System ID: 0951
Client Id : 3
Client Id Type : Broadcast
Client Id : 8
Client Id Type : MAC Addr: 1111.1111.1111
Client List Id : 3
Client Id : 1
Client Id Type : Application ID: 0001
Client List Id : 4
Client Id : 1
Client Id Type : CA System ID: 0701
Client List Id : 10
Client Id : 1
Interface : Cable6/0
Rule Id : 1
Rule Id : 7
Rule Id : 8
Rule Id : 20
Interface : Cable6/1
Rule Id : 1
Rule Id : 3
Rule Id : 4
Rule Id : 11
Beginning in Cisco IOS Release 12.3(17a)BC, this output was modified to add the “TG id” field in
support of A-DSG version 1.2. The “State” and “MAC Addr” fields also switched positions in the output.
Router# show cable dsg tunnel 1 verbose
Tunnel ID : 1
State : enable
MAC Addr : 0100.5e01.0001
TG Id : 1
Cfr Id : 1
State : enable
Priority : 0
Dest IP : 230.1.0.1
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 6
State : enable
Priority : 0
Dest IP : 231.1.1.6
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 7
State : enable
Priority : 0
Dest IP : 231.1.1.7
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Cfr Id : 8
State : enable
Priority : 0
Dest IP : 231.1.1.8
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 0
Dest Port End : 65535
Forwarded : 0
Received : 0
Client List Id : 1
Client Id : 1
Client Id Type : MAC Addr 0100.5e00.0001
Client Id : 2
Client Id Type : Application ID 0x0951
Client Id : 3
Client Id Type : Broadcast Unspecified
Client Id : 4
Client Id Type : Broadcast 4
Interface : Cable5/0
Rule Id : 1
Syntax Description fiber-node-id Specifies a fiber node ID. Valid values range from 1 to 256.
spectrum Displays upstream channel frequency assignment information and the
spectrum group number.
Usage Guidelines Use the show cable fiber-node command to display information about a fiber node, such as the fiber
node status. If you specify the spectrum parameter, the command displays upstream channel frequency
assignment information and the spectrum group number.
For each fiber node, a traditional DOCSIS downstream channel on a Cisco uBR10-MC5X20 cable
interface line card is used to carry MAC management and signaling messages. This traditional DOCSIS
downstream channel used for a MAC domain is called the primary downstream channel. The associated
traditional DOCSIS upstream channel is used for return data traffic and signaling.
Examples The following is a sample output of the show cable fiber-node command:
Router# show cable fiber-node 2
Fiber-Node Config Status
Fiber-Node 2
downstream Modular-Cable 1/0/0: 0-3
downstream Cable 7/1/0
upstream Cable 7/1: 10-19
FN Config Status: Configured (status flags = 0x01)
MDD Status: Valid
Router#
Table 47 describes the fields shown in the show cable fiber-node command display.
Field Description
Fiber-Node Displays the fiber nodes configured on the CM.
Config Status Displays the configuration status of the fiber node. Status flags are as
follows:
• 0x01 - CMTS_FN_CONFIG
• 0x02 - CMTS_FN_FREQ_INVALID
• 0x04 - CMTS_FN_CHID_INVALID
• 0x08 - CMTS_FN_BUNDLE_INVALID
• 0x10 - CMTS_FN_BOND_CHID_INVALID
• 0x20 - CMTS_FN_US_FREQ_INVALID
• 0x40 - CMTS_FN_NO_US_CONFIGURED
MDD Status Displays the MAC Domain Descriptor (MDD) status. MDD status of a fiber
node is set as invalid in the following cases:
• Frequency is not unique.
• Channel ID is not unique.
• Bonding group ID is not unique.
• Bundle is mismatched.
Table 48 describes the fields shown in the show cable load-balance command display when the
spectrum keyword is used.
Field Description
Upstream Port Displays the upstream port associated with the fiber node.
Physical Port Displays the physical port of the upstream channel.
Frequency Displays the upstream channel frequency of the CM.
Spectrum Group No. Displays the spectrum group number of the fiber node. A spectrum group is
a list of upstream frequencies and nominal power levels. Spectrum groups
ranging from 1 to 32 can be created for each cable modem upstream port.
Syntax Description group group-id (Optional) Specifies the filter group to be displayed. The valid range is
1 to 256.
index index-num (Optional) Specifies the index of the particular filter within a group to
be displayed. The valid range is 1 to 128 on a uBR7200 series router
and 1 to 255 on a uBR10012 router.
verbose (Optional) Displays complete information about the filter groups in a
format that is easier to read than the default display.
Examples The following example shows a typical display of the show cable filter command:
Router# show cable filter
Filter SrcAddr/Mask DestAddr/Mask Prot ToS SPort DPort TCP Action Status
Grp Id Flags
The following shows typical output for the verbose form of this command:
Router# show cable filter group 10 index 10 verbose
Filter Group : 1
Filter Index : 1
Matches : 0
Match action : accept
Status : active
Filter Group : 10
Filter Index : 10
Matches : 0
Source IP Address : 10.7.7.7/16
Destination IP Address : 10.8.8.8/16
IP Protocol type : 256
IP ToS (Mask, Value) : 1, 2
TCP/UDP Source Port : 2000
TCP/UDP Destination Port : 3000
TCP Flags (mask, value) : 0, 0
Match action : accept
Status : active
Router#
IPv6 Examples
The following examples show examples of output for the show cable filter commands with changes
beginning in Cisco IOS Release 12.2(33)SCA in support of IPv6 cable filter groups. Table 49 describes
the output fields.
Router# show cable filter
Filter SrcAddr/Mask DestAddr/Mask Prot ToS SPort DPort TCP Action Status
Grp Id v6 Flags
Field Description
Filter Gp ID number of the filter group. Defined by the group-id argument of the cable
filter group command.
Filter Id Index number of the filter group. Defined by the index-num argument of the
cable filter group command.
v6 IP version 6 filter group type indicator. Defined by the ip-version keyword of
the cable filter group command. Possible values are Y or N.
SrcAddr/Mask • IP version 4—Filter source IP address and mask to be matched by the
filter. Defined by the src-ip and src-mask keywords of the cable filter
group command..
• IP version 6—“Use Verbose” appears because IPv6 addresses will not fit
in the output display area; need to use the show cable filter group
verbose command to view IPv6 addresses.
DestAddr/Mask • IP version 4—Filter destination IP address and mask to be matched by the
filter. Defined by the dest-ip and dest-mask keywords of the cable filter
group command.
• IP version 6—“Use Verbose” appears because IPv6 addresses will not fit
in the output display area; need to use the show cable filter group
verbose command to view IPv6 addresses.
Prot IP protocol number(s) to be matched by the filter. Defined by the ip-proto
keyword of the cable filter group command.
ToS Type of Service mask and value to be matched by the filter. Defined by the
ip-tos keyword of the cable filter group command.
SPort TCP/UDP source port number to be matched by the filter. Defined by the
src-port keyword of the cable filter group command.
DPort TCP/UDP destination port number to be matched by the filter. Defined by the
dest-port keyword of the cable filter group command.
TCP Flags TCP flag mask and value to be matched by the filter. Defined by the tcp-flags
keyword of the cable filter group command.
Action Action to be taken on packet (accept or drop) when filter match occurs.
Defined by the match-action keyword of the cable filter group command.
Status Filter group status (active or inactive). Defined by the status keyword of the
cable filter group command.
Field Description
Filter Group ID number of the filter group. Defined by the
group-id argument of the cable filter group
command.
Filter Index Index number of the filter group. Defined by the
index-num argument of the cable filter group
command.
Filter Version IP version of the filter group. Defined by the
ip-version keyword of the cable filter group
command. Possible values are IPv4 or IPv6.
Matches: Source IP address or • Source IP address—IPv4 source IP address
Matches: Source IPv6 address and mask to be matched by the filter. Defined
by the src-ip and src-mask keywords of the
cable filter group command.
• Source IPv6 address—IPv6 source IP address
and prefix to be matched by the filter. Defined
by the v6-src-address and v6-src-pfxlen
keywords of the cable filter group command.
Matches: Destination IP address or • Destination IP address—IPv4 destination IP
Matches: Destination IPv6 address address and mask to be matched by the filter.
Defined by the dest-ip and dest-mask
keywords of the cable filter group command.
• Destination IPv6 address—IPv6 destination
IP address and prefix to be matched by the
filter. Defined by the v6-dest-address and
v6-dest-pfxlen keywords of the cable filter
group command.
Matches: IP Protocol type IP protocol number(s) to be matched by the filter.
Defined by the ip-proto keyword of the cable
filter group command.
Matches: IP ToS (Mask, Value) Type of Service mask and value to be matched by
the filter. Defined by the ip-tos keyword of the
cable filter group command.
Matches: TCP/UDP Source Port TCP/UDP source port number to be matched by
the filter. Defined by the src-port keyword of the
cable filter group command.
Matches: TCP/UDP Destination Port TCP/UDP destination port number to be matched
by the filter. Defined by the dest-port keyword of
the cable filter group command.
Matches: TCP Flags (mask, value) TCP flag mask and value to be matched by the
filter. Defined by the tcp-flags keyword of the
cable filter group command.
Field Description
Matches: Match action Action to be taken on packet (accept or drop) when
filter match occurs. Defined by the match-action
keyword of the cable filter group command.
Matches: Status Filter group status (active or inactive). Defined by
the status keyword of the cable filter group
command.
show cable flap-list [cable slot/port | cable slot/subslot/port] [upstream port] [sort-flap |
sort-time]
Syntax Description cable slot/port (Optional) Displays information for all CMs on the specified cable
interface and downstream port on the Cisco uBR7100 series and
Cisco uBR7200 series routers:
• slot—Chassis slot number of the cable interface line card.
• port—Downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable
interface on a Cisco uBR10012 router:
• slot—Chassis slot number of the cable interface line card. Valid
slots are from 5 to 8.
• subslot—Secondary slot number of the cable interface line card.
Valid subslots are 0 or 1.
• port—Downstream port number. Valid ports are 0 to 4, depending
on the cable interface line card.
upstream port (Optional) Displays the flap list for a particular upstream on the
selected cable interface.
sort-interface (Optional) Displays the flap list for all cable interfaces, sorted by
interface.
sort-flap (Optional) Sorts the list by the number of times the CM has flapped.
sort-time (Optional) Sorts the list by the most recent time the CM is detected to
have flapped.
Release Modification
12.0(7)XR and The output of this command was enhanced to show that the Cisco CMTS has
12.1(1a)T1 detected an unstable return path for a particular CM and has compensated
with a power adjustment. An asterisk (*) appears in the power adjustment
field for a modem when a power adjustment has been made; an exclamation
point (!) appears when the CM has reached its maximum power transmit
level and cannot increase its power level further.
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA. Support
for the Cisco uBR7225VXR router was added.
12.2(33)SCC The output of this command was modified to show the aggregated data
across all upstream channels for each flap detector for CMs in the Multiple
Transmit Channel (MTC) mode on a Cisco uBR10012 router.
Usage Guidelines The sort options operate differently on the different Cisco CMTS routers. On the Cisco uBR7100 series
and Cisco uBR7200 series routers, the sort options apply to all cable interface line cards and merge the
output into a single display.
On the Cisco uBR10012 router, the sort options apply to individual cable interface line cards. For
example, the sort-time option sorts all of the flap entries on the first cable interface line card (c5/0/0),
then the entries on the second card (c5/1/0), and so forth.
Note Occasionally, the show cable flap-list command might temporarily show duplicate entries for the same
cable modem. This can occur after a cable modem has gone offline and before it has completed the
registration process and come back online. When the cable modem does reach the online state, the
duplicate entries disappear.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows the output of the show cable flap-list command:
router# show cable flap-list
MAC Address Upstream Ins Hit Miss CRC P-Adj Flap Time
0010.7bb3.fd19 Cable5/0/U1 0 2792 281 0 *45 58 Jul 27 16:54:50
0010.7bb3.fcfc Cable5/0/U1 0 19 4 0 !43 43 Jul 27 16:55:01
0010.7bb3.fcdd Cable5/0/U1 0 19 4 0 *3 3 Jul 27 16:55:01
Note The asterisk (*) in the P-Adj field indicates that a power adjustment has been made for that CM. The
exclamation point (!) indicates that the CM has reached its maximum power transmit level and cannot
increase its power level further.
The following example shows the display of flap-list tables sorted by MAC address:
router# show cable flap-list sort-flap
Mac Addr CableIF Ins Hit Miss CRC P-Adj Flap Time
0010.1eab.2c0b C6/0 U0 108 318 27 0 0 108 Sep 10 15:26:56
0010.1eb2.bb07 C6/0 U0 0 293 31 1 1 1 Sep 10 15:15:49
The following example shows the display of flap-list tables sorted by time:
Router# show cable flap-list sort-time
Mac Addr CableIF Ins Hit Miss CRC P-Adj Flap Time
00e0.2222.2202 C4/0 U0 464 2069 242 0 421 885 Oct 16 22:47:23
0010.7b6b.57e1 C4/0 U0 0 2475 43 0 1041 1041 Oct 16 22:47:04
The following sample output of the show cable flap-list command provides the aggregated data across
all upstream channels for CMs in the MTC mode on a uBR10012 router in Cisco IOS Release
12.2(33)SCC:
router# show cable flap-list
MAC Address Upstream Ins Hit Miss CRC P-Adj Flap Time
001e.6bfb.0f9e C5/0/0/UB 0 62539 0 0 2 2 Apr 18 03:53:00
0050.f110.b277 C5/0/0/UB 0 10965 211 0 0 9 Apr 18 03:53:00
Field Description
Mac Addr MAC address for the CM.
CableIF Cable interface line card, including upstream, for this CM.
Ins Number of times the CM comes up and inserts itself into the
network. It can indicate intermittent downstream sync loss or
DHCP or modem registration problems.
Hit Number of times the CM responds to MAC layer keepalive
messages. (The minimum hit rate is once per 30 seconds. It can
indicate intermittent upstream, laser clipping, or common-path
distortion.
Miss Number of times the CM misses the MAC layer keepalive message.
An 8 percent miss rate is normal for the Cisco cable interface line
cards. It can indicate intermittent upstream, laser clipping, or
common-path distortion.
CRC Number of cyclic redundancy check (CRC) errors from this CM. It
can indicate intermittent upstream, laser clipping, or common-path
distortion.
P-Adj Number of times the headend instructed the CM to adjust transmit
(TX) power more than 3 dB. It can indicate amplifier degradation,
poor connections, or thermal sensitivity.
Flap Sum of P-Adj and Ins values. CMs with high flap counts have high
SIDs and might not register.
Time Most recent time that the CM dropped the connection.
Related Commands
Command Description
cable flap-list aging Specifies the number of days to keep a CM in the flap-list table before aging
it out of the table.
cable flap-list Sets the insertion time interval that determines whether a CM is placed in the
insertion-time flap list.
cable flap-list Specifies the miss threshold for recording a flap-list event.
miss-threshold
cable flap-list Specifies the power-adjust threshold for recording a CM flap-list event.
power-adjust
threshold
cable flap-list size Specifies the maximum number of CMs that can be listed in the flap-list
table.
clear cable flap-list Clears all the entries in the flap-list table.
debug cable flap Displays information about the operation of the CM flap list that is
maintained for the cable interfaces.
ping docsis Sends a DOCSIS ping to a CM and increments the flap-list counters as
appropriate.
show cable modem Displays information about all CMs on an interface or about a particular CM.
show cable modem Displays flap list statistics for one or more cable modems.
flap
Syntax Description cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable
interface on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
modular-cable slot/bay/port (Optional) Displays information for all CMs on the specified modular
cable interface on a Cisco uBR10012 router, where
• slot—The slot where a SIP resides. On the Cisco uBR10012
router, slots 1 and 3 can be used for SIPs.
• bay—The bay in a SIP where a SPA is located. Valid values are 0
(upper bay) and 1 (lower bay).
• port—Specifies the interface number on the SPA.
WB RF channel number (Optional) Specifies the wideband RF channel number.
QAM (Optional) Specifies the number of QAM flaps.
MDD (Optional) Specifies the number of MDD flaps.
Examples The following is a sample output of the show cable flap-list wb-rf command:
router# show cable flap-list wb-rf
Syntax Description cable slot/port (Optional) Specifies a cable interface on the Cisco uBR7100 series
and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On
the Cisco uBR7200 series router, slot can range from 3 to 6, and port
can be 0 or 1, depending on the cable interface.
cable slot/subslot/port (Optional) Specifies a cable interface on the Cisco uBR10012 router.
The following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
upstream uport (Optional) Specifies an upstream port for which to display the
frequency hop status.
history (Optional) Displays changes from one state to another, at any time
and for any reason, for frequency, modulation, and channel width.
threshold (Optional) Displays the user defined thresholds and current
carrier-to-noise ratio (CNR), signal-to-noise ratio (SNR), correctable
forward error correction (FEC) percentage, uncorrectable FEC
percentage, and missed station maintenances percentage values of the
upstreams.
Examples The following example shows typical output from the show cable hop command:
Router# show cable hop
Upstream Port Poll Missed Min Missed Hop Hop Corr Uncorr
Port Status Rate Poll Poll Poll Thres Period FEC FEC
(ms) Count Sample Pcnt Pcnt (sec) Errors Errors
Cable4/0/U0 down 1000 * * * frequency not set * * * 0 0
Cable4/0/U1 down 1000 * * * frequency not set * * * 0 0
Cable4/0/U2 down 1000 * * * frequency not set * * * 0 0
Cable4/0/U3 down 1000 * * * frequency not set * * * 0 0
Cable4/0/U4 down 1000 * * * frequency not set * * * 0 0
Cable4/0/U5 down 1000 * * * frequency not set * * * 0 0
Cable5/0/U0 down 1000 * * * interface is down * * * 0 0
Cable5/0/U1 down 1000 * * * frequency not set * * * 0 0
Cable5/0/U2 down 1000 * * * interface is down * * * 0 0
Cable5/0/U3 down 1000 * * * interface is down * * * 0 0
Cable5/0/U4 down 1000 * * * interface is down * * * 0 0
Cable5/0/U5 down 1000 * * * interface is down * * * 0 0
Cable6/0/U0 down 1000 * * * interface is down * * * 0 0
Cable6/0/U1 22.000 Mhz 1000 * * *set to fixed frequency * * * 31375 1912
Cable6/0/U2 26.000 Mhz 1000 * * *set to fixed frequency * * * 0 0
Cable6/0/U3 admindown 1000 * * * frequency not set * * * 0 0
The following example shows typical output from the show cable hop upstream command:
Upstream Port Poll Missed Min Missed Hop Hop Corr Uncorr
Port Status Rate Poll Poll Poll Thres Period FEC FEC
(ms) Count Sample Pcnt Pcnt (sec) Errors Errors
Cable2/0/U2 admindown 1000 * * * frequency not set * * * 0 0
Router#
Table 52 describes the fields displayed by the show cable hop and show cable hop upstream
commands.
Field Description
Upstream Port The upstream port for this information line.
Port Status Lists the status of the port. Valid states are down if frequency is
unassigned or admindown if the port is shut down. If the port is up,
this column shows the center frequency of the channel.
Poll Rate The rate that station maintenance polls are generated (in
milliseconds).
Missed Poll Count The number of missing polls, per codeword/FEC block.
Min Poll Sample The number of polls in the sample, per codeword/FEC block.
Missed PollPcnt The ratio of missing polls to the number of polls, expressed as a
percentage.
Hop Thres Pcnt The level that the missed poll percentage must exceed to trigger a
frequency hop, expressed as a percentage.
Hop Period The maximum rate that frequency hopping will occur (in seconds).
Field Description
Corr FEC Errors The number of correctable forward error corrections (FEC) errors
on this upstream port, per codeword/FEC block.
Uncorr FEC Errors The number of uncorrectable FEC errors on this upstream port, per
codeword/FEC block.
Note The show cable hop and show controllers cable commands display FEC errors per
codewords, while the show interface cable upstream command displays FEC errors per
packets, where a packet could contain multiple codewords.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
The following example shows typical output from the show cable hop threshold command:
Router# show cable hop c6/0/0 threshold
Upstream SNR(dB) CNR(dB) CorrFEC% UncorrFEC% MissedSM%
Port Val Thre1 Thre2 Val Thre1 Thre2 Pcnt Thre Pcnt Thre Pcnt Thre
Ca6/0/0/U0 27 25 15 39 35 25 0 3 0 1 75 75
Ca6/0/0/U1 31 25 15 51 35 25 0 3 0 1 90 75
Ca6/0/0/U2 -- 35 25 -- 35 25 0 3 0 1 0 75
Ca6/0/0/U3 -- 35 25 -- 35 25 0 3 0 1 0 75
Table 53 describes the fields displayed by the show cable hop threeshold command.
Field Description
Upstream Port The upstream port for this information line.
SNR (dB) The signal-to-noise ratio (SNR) for a particular cable modem
(CM), in decibels (dB).
CNR (dB) The current upstream carrier-to-noise ratio (CNR) for a particular
cable modem (CM), in decibels (dB).
Corr FEC Errors The number of correctable forward error corrections (FEC) errors
on this upstream port, per codeword/FEC block.
Uncorr FEC Errors The number of uncorrectable FEC errors on this upstream port, per
codeword/FEC block.
Missed SM The number of missing station maintenance polls, per
codeword/FEC block.
The following example shows typical output from the show cable hop history command:
Router# show cable hop c8/1/1 upstream 0 history
F = Frequency Hop, M = Modulation Change, C = Channel Width Change
Table 54 describes the fields displayed by the show cable hop history command.
Field Description
Upstream Port The upstream port for this information line.
Action Time The time of the spectrum management action.
Code The code associated with the type of hop.
Chg From The previous state of the spectrum management action.
Chg To The current state of the spectrum management action.
Action Reason The reason for changing the frequency.
Note The show cable host command is not supported on the Cisco uBR10012 universal broadband router.
Syntax Description mac-addr (Optional) Specifies the 48-bit hardware address for a particular CM or host.
ip-addr (Optional) Specifies the IP address for a particular CM or host.
Usage Guidelines This command displays information only for hosts and other CPE devices. To display information for
CMs and their associated CPE devices, use the show cable device access-group command. To display
information only for CMs, use the show cable device access-group command.
If an SNMP manager is requesting information about CM or CPE devices at the same time that this
command is given, the command displays the following error message:
No information is available, please try later.
Wait until the SNMP retrieval is done and retry the CLI command.
Examples The following example shows how to display all the hosts behind the CMs in the network:
router# show cable host access-group
Router#
Table 0-55 describes the fields that are shown in the show cable host access-group display:
Field Description
MAC Address The MAC address for the CPE device.
IP Address The IP address that the DHCP server has assigned to the CPE device.
Type Identifies the type of device. With this command, this field should always be
host to indicate a CPE device. Use the show cable device access-group or
show cable modem access-group command to display information for CMs.
Access-group Displays the access group name or number in use (if any) for this CPE device.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following is sample output from the show cable ib-ipc command. The command show cable ib-ipc
ports displays the internal virtual channel identifiers and internal service flows for Ironbus based IPC.
Router# show cable ib-ipc ports
6/0: LCP High Priority VCCI 135, SFID 32891
LCP Normal Priority VCCI 135, SFID 135
8/0: LCP High Priority VCCI 153, SFID 32909
LCP Normal Priority VCCI 153, SFID 153
Usage Guidelines You must enable the Cable IPC Statistics Collection tool using the cable ipc-stats command before
using the show cable ipc-stats command. When you use this show command, a separate shadow
database buffer is allocated, and the contents of the active database are copied into the shadow database
to display the IPC statistics. This ensures that all the statistics are frozen at the same time for easy
comparison and analysis.
Examples The following is a sample output of the show cable ipc-stats command that shows statistics of all IPC
messages on a Cisco CMTS router:
Router# show cable ipc-stats
entity app io s/s reqid idx: pkts bytes lastEvt totalDur maxDur lastMax
(sec) (msec) (msec) (sec)
rp-lc c10k TxReq 1/0 10241 1: 1 24 17
rp-lc c10k TxReq 1/0 10 14: 11 704 0
rp-lc c10k TxReq 2/1 10 14: 10 640 4
rp-lc c10k TxReq 3/0 10 14: 10 640 4
rp-lc c10k TxReq 3/1 10 14: 11 704 0
rp-lc c10k TxReq 4/0 10 14: 10 640 3
rp-lc c10k TxReq 6/0 10252 2: 10 9376 13
rp-lc c10k TxReq 6/0 10 14: 11 704 0
rp-lc c10k TxReq 6/1 10252 2: 1 88 53
rp-lc c10k TxReq 6/1 10 14: 11 704 0
TXQ_6_1
enQ: 1 pkts max Q size 1 at 53 sec ago
deQ: 1 pkts max delay 0 msec at 53 sec ago
delay between ( 0, 10) msec: 1 pkts
delay between ( 0, 1) sec : 1 pkts
flush: 0 ptks 0 times
TXQ_7_0
enQ: 7 pkts max Q size 1 at 5 sec ago
deQ: 7 pkts max delay 48 msec at 13 sec ago
delay between ( 0, 10) msec: 1 pkts
delay between ( 10, 20) msec: 5 pkts
delay between ( 40, 50) msec: 1 pkts
delay between ( 0, 1) sec : 7 pkts
flush: 0 ptks 0 times
cr10k LP rxq
enQ: 25 pkts max Q size 1 at 0 sec ago
deQ: 25 pkts max delay 0 msec at 0 sec ago
delay between ( 0, 10) msec: 25 pkts
delay between ( 0, 1) sec : 25 pkts
flush: 0 ptks 0 times
Table 1 describes the fields displayed by the show cable ipc-stats command.
Field Description
entity Route processor-to-line card connection or a line
card-to-line card connection.
app Message group.
io Send request or a send response, or a receiver
request or a receiver response.
s/s Slot/subslot
reqid Nonsequential message ID for the original
request.
idx Sequential message index for the original request.
pkts Number of messages.
bytes Number of bytes.
lastEvt (sec) Seconds since the last send or receive event.
totalDur (msec) Total time in milliseconds for the blocked send
wait or received request process.
Field Description
maxDur (msec) Maximum time in milliseconds for the blocked
send wait or received request process.
lastMax (sec) Seconds since the last maxDur is recorded.
Syntax Description mac-address (Optional) Displays the mapping for the cable modem with the specified
hardware MAC address.
vpn vpnid (Optional) Displays Layer 2 VPN information on a cable modem with the
specified MAC address, or for the specified VPN ID across all cable
modems.
verbose (Optional) Displays additional information about the Layer 2 mapping,
including the number of packets and bytes received on the upstream and
downstream.
customer cust-name (Optional) Displays the VLAN mappings for this particular customer name.
Defaults Displays information for all cable modems that have a defined IEEE 802.1Q VLAN mapping.
Usage Guidelines This command displays the cable modem to VLAN mappings that have been defined using the cable
dot1q-vc-map command. It displays the MAC address, service ID (SID), and cable interface being used
by the cable modem, and the interface and VLAN ID to which it has been mapped.
Tip The customer option displays only those VLAN mappings that have been configured with a particular
customer name, using the cable dot1q-vc-map command.
The command also displays L2VPN information for cable modem traffic and service flows on CMTS
router Ethernet interfaces that have been defined using the cable l2-vpn-service default-nsi command.
MAC Address Ethernet Interface VLAN ID Cable Intf SID Priv Bits
0010.7bed.9c95 FE0/0.2 3 Cable4/0 3 0
0007.0e03.69f9 FE0/0.1 4 Cable4/0 1 0
Router#
The following example shows typical output for a particular cable modem with the MAC address of
0001.0203.0405:
Router# show cable l2-vpn dot1q-vc-map 0001.0203.0405
MAC Address Ethernet Interface VLAN ID Cable Intf SID Priv Bits
0010.7bed.9c91 GE2/0 5 Cable5/0 7 0
Router#
The following example shows a typical example for the verbose option:
Router# show cable l2-vpn dot1q-vc-map 0001.0203.0405 verbose
Field Description
MAC Address Hardware (MAC) address for the CM being mapped.
Ethernet Interface Destination interface (Ethernet, Fast Ethernet, or Gigabit Ethernet) for the
VLAN being used for the mapping.
VLAN ID Destination VLAN on the Ethernet, Fast Ethernet, or Gigabit Ethernet interface
for the traffic coming from the CM.
Cable Intf Cable interface to which the CM is connected.
SID Primary service ID (SID) for this cable modem.
Field Description
Priv Bits Identifies the current settings of the two privacy bits in the extended header (EH)
that is used for BPI-encrypted packets.
• First bit = Enable bit. Set to 1 when BPI or BPI+ is enabled.
• Second bit = Toggle bit. Matches the least-significant bit (LSB) of the key
sequence number (KSN) in the EH.
For example, a value of “0” indicates that BPI is not enabled. A value of “10”
indicates that BPI is enabled and that the KSN is an even number. A value of “11”
indicates that BPI is enabled and that the KSN is an odd number.
Note For more information on these bits, see the DOCSIS Baseline Privacy
Interface Plus Interface Specification (SP-BPI+-I08-020301 or later).
Total US pkts/bytes Total number of packets and bytes sent on the upstream to the Layer 2 tunnel by
this cable modem.
Total DS pkts/bytes Total number of packets and bytes received on the downstream from the Layer 2
tunnel by this cable modem.
The following example shows sample output of VLAN information for a VPN with ID 0234560001:
Router# show cable l2 dot1q-vc-map vpn 0234560001
MAC Address Ethernet Interface VLAN ID Cable Intf SID Customer Name/VPNID
0014.f8c1.fd66 GigabitEthernet4/0/0 68 Cable6/0/0 3 0234560001
The following example shows sample output of VLAN information for a VPN with ID 0234560001 on
the cable modem with MAC address 0014.f8c1.fd66:
Router# show cable l2-vpn dot1q-vc-map 0014.f8c1.fd66 vpn 0234560001
MAC Address Ethernet Interface VLAN ID Cable Intf SID Customer Name/VPNID
0014.f8c1.fd66 GigabitEthernet4/0/0 68 Cable6/0/0 3 0234560001
The following example shows sample output of detailed VLAN information for a VPN with ID
0234560001 on the cable modem with MAC address 0014.f8c1.fd66:
Router# show cable l2-vpn dot1q-vc-map 0014.f8c1.fd66 vpn 0234560001 verbose
MAC Address : 0014.f8c1.fd66
Prim Sid : 3
Cable Interface : Cable6/0/0
VPN ID : 0234560001
L2VPN SAID : 12294
Upstream SFID : 23
Downstream CFRID[SFID] : 2[24]
CMIM : 0x60
Ethernet Interface : GigabitEthernet4/0/0
DOT1Q VLAN ID : 68
Total US pkts : 1372
Total US bytes : 500226
Total US pkt Discards : 0
The following example shows sample output of detailed VLAN information for a cable modem with
MAC address 0014.f8c1.fd66:
Router# show cable l2-vpn dot1q-vc-map 0014.f8c1.fd66 verbose
VPN ID : 0234560001
L2VPN SAID : 12294
Upstream SFID : 23
Downstream CFRID[SFID] : 2[24]
CMIM : 0x60
Ethernet Interface : GigabitEthernet4/0/0
DOT1Q VLAN ID : 68
Total US pkts : 1374
Total US bytes : 501012
Total US pkt Discards : 0
Total US byte Discards : 0
Total DS pkts : 1250
Total DS bytes : 416250
Total DS pkt Discards : 0
Total DS byte Discards : 0
Field Description
MAC Address Hardware (MAC) address for the CM being mapped.
Prim Sid Primary service ID for the CM.
Cable Interface Cable interface to which the CM is connected.
L2VPNs provisioned Number of L2VPNs supported by the CM.
DUT Control/CMIM State of Downstream Unencrypted Traffic (DUT) filtering and Cable
Modem Interface Mask (CMIM).
VPN ID Identification number of the Layer 2 VPN tunnel.
L2VPN SAID Layer 2 VPN Security Association Identifier (SAID).
Upstream SFID Upstream Service Flow Identifier (SFID).
Downstream CFRID Downstream classifiers (classifier identifiers) and corresponding
[SFID] downstream service flows identifiers for this L2VPN.
CMIM Cable Modem Interface Mask.
Ethernet Interface Ethernet Network System Interface (NSI).
DOT1Q VLAN ID Destination VLAN on the Ethernet, Fast Ethernet, or Gigabit Ethernet
interface for the traffic coming from the CM.
Table 58 show cable l2-vpn dot1q-vc-map with L2VPN Field Descriptions (continued)
Field Description
Total US pkts/bytes Total number of packets and bytes sent on the upstream to the Layer 2 tunnel
by this CM.
Total US pkt/byte Total number of packets and bytes dropped on the upstream to the Layer 2
Discards tunnel by this CM.
Total DS pkts/bytes Total number of packets and bytes received on the downstream from the
Layer 2 tunnel by this CM.
Total DS pkt/byte Total number of packets and bytes dropped on the downstream from the
Discards Layer 2 tunnel by this CM.
Syntax Description dot1q-vc-map Specifies the mapping of one or all cable modems to IEEE 802.1Q Virtual
Local Area Networks (VLANs) on the Ethernet interfaces of a router.
mpls-vc-map Specifies the mapping between an MPLS pseudowire and its virtual circuits.
mac-address (Optional) Specifies the MAC address for a cable modem.
customer (Optional) Specifies the customer name.
customer-name
state (Optional) Specifies the state of all virtual circuits.
Examples Example of the show cable l2-vpn xconnect Command for the Mapping Between an MPLS Pseudowire and All
Virtual Circuits
The following is a sample output of the show cable l2-vpn xconnect command that shows the mapping
between an MPLS pseudowire and all virtual circuits on a Cisco uBR10012 router:
Router# show cable l2-vpn xconnect mpls-vc-map
MAC Address Peer IP Address VCID CktID Cable Intf SID Customer
Name/VPNID
0000.396e.6a68 101.1.0.2 221 Bu254:221 Cable7/0/0 1 customer1
0014.f8c1.fd66 10.76.1.1 2004 Bu254:5121 Cable7/0/0 8
0019.474a.d566 10.76.1.1 2001 Bu254:5122 Cable7/0/0 4 0234560002
0019.474a.d42e 10.76.1.1 2002 Bu254:2003 Cable7/0/0 5 0234560003
Example of the show cable l2-vpn xconnect Command for a Particular MAC Address
The following sample output displays the mapping between an MPLS pseudowire and the virtual circuit
for a particular MAC address of a cable modem on a Cisco uBR10012 router:
Router# show cable l2-vpn xconnect mpls-vc-map 0000.396e.6a68
MAC Address Peer IP Address VCID CktID Cable Intf SID Customer
Name/VPNID
0000.396e.6a68 101.1.0.2 221 Bu254:221 Cable7/0/0 1 customer1
Example of the show cable l2-vpn xconnect Command for a Particular Customer
The following sample output displays the mapping between an MPLS pseudowire and all virtual circuits
configured for a particular customer on a Cisco uBR10012 router:
Router# show cable l2-vpn xconnect mpls-vc-map customer1
MAC Address Peer IP Address VCID CktID Cable Intf SID Customer
Name/VPNID
0000.396e.6a68 101.1.0.2 221 Bu254:221 Cable7/0/0 1 customer1
Example of the show cable l2-vpn xconnect Command that Shows Information About the State of All Virtual
Circuits
The following sample output displays the state of all virtual circuits associated with an MPLS
pseudowire on a Cisco uBR10012 router:
Router# show cable l2-vpn xconnect mpls-vc-map state
Table 59 describes the fields shown in the show cable l2-vpn xconnect command display.
Field Description
MAC Address MAC address of a cable modem.
Peer IP Address IP address of the remote provider edge router.
VCID Virtual circuit ID.
CktID Circuit ID.
Cable Intf Cable interface for the MPLS pseudowire.
SID Service ID.
STATE State of all virtual circuits.
Syntax Description cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port on the Cisco uBR7246VXR router.
On the Cisco uBR7246VXR router, slot can range from 3 to 6, and port can
be 0 or 1, depending on the cable interface.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on the Cisco uBR10012 router. The following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
requests-filtered (Optional) Displays the number of DHCP LEASEQUERY requests that have
[minimum-requests] been filtered for each particular cable modem on a cable interface.
• minimum-requests—(Optional) Displays only those cable modems for
which the router has filtered at least this minimum number of lease
queries. The valid range for minimum-requests is 1 to 65535, with a
default of 1.
Usage Guidelines The show cable leasequery-filter command displays the total number of DHCP LEASEQUERY
requests that have been filtered on a Cisco Cable Modem Termination System (CMTS) router and on a
particular cable interface. This command can also optionally display details for each particular cable
modem on an interface that has had DHCP lease queries filtered.
Examples The following example shows how to display the total number of DHCP LEASEQUERY requests that
have been filtered on the router and on a particular cable interface:
Router# show cable leasequery-filter
The following example shows how to display a list of cable modems on a cable interface and the number
of DHCP LEASEQUERY messages that have been filtered for each:
Router# show cable leasequery-filter cable 8/1/0 requests-filtered
Router#
The following example shows how to display a list of cable modems on a cable interface that have had
10 or more DHCP LEASEQUERY messages that have been filtered:
Router# show cable leasequery-filter cable 8/1/0 requests-filtered 10
Router#
Syntax Description group n (Optional) Specifies the number of the load balancing group to be
displayed. The valid range is from 1 to 336. The range from 1 to 80 is
reserved for legacy load balancing group (LBG). The range from 81 to 336
is reserved for DOCSIS LBGs. The default is to display information for all
load balancing groups.
all (Optional) Displays all information about the LBG.
load (Optional) Displays the current interface load and load balancing group
assignments.
pending (Optional) Displays the list of cable modems that are moved from one
downstream or upstream to another.
statistics (Optional) Displays cumulative statistics for load balancing operations.
target (Optional) Displays the current and target interfaces (upstreams and
downstreams) used for load balancing.
fiber-node-validation (Optional) Displays DOCSIS LBG and channel information after checking
if the channel configuration in load balancing fits in the fiber node
configuration
Defaults Displays information for all load balancing groups for each cable interface and its current load and load
balancing status.
Usage Guidelines Use the show cable load-balance command to display the current, real-time statistics for load balancing
operations.
Examples The following is a sample output of the show cable load-balance command:
Router# show cable load-balance
DOCSIS LB Enabled: No
The following is a sample output of the all option of the show cable load-balance command. The all
option displays information of all options available for this command except the fiber-node-validation
option.
Router# show cable load-balance all
DOCSIS LB Enabled: No
Current load:
Target assignments:
Statistics:
Cable5/0/3/U1 up 0 0 0 0
Cable5/0/3/U2 up 0 0 0 0
Cable5/0/3/U3 up 0 0 0 0
Cable5/0/4 (465 MHz) up 0 0 0 0
Cable5/0/4/U0 up 0 0 0 0
Cable5/0/4/U1 up 0 1 0 0
Cable5/0/4/U2 up 0 0 0 0
Cable5/0/4/U3 up 0 0 0 0
Mo1/0/0:0 (555 MHz) down 0 0 0 0
Pending:
Router#
The following is a sample output of the fiber-node-validation option of the show cable load-balance
command.
Router# show cable load-balance fiber-node-validation
DOCSIS LBG ID Match Channel Fiber-node list
1 match Ca5/0/0/U0 {1}
Ca5/0/0/U1 {1}
Ca5/0/0/U2 {1}
Ca5/0/0/U3 {1}
Mo1/0/0:0 {1}
2 match Ca5/0/0/U0 {1}
Ca5/0/0/U1 {1}
Ca5/0/0/U2 {1}
Mo1/0/0:0 {1}
Table 60 describes the fields shown in the show cable load-balance command displays.
Field Description
Fields for the Default Displays and load Option
Interface Cable interface (downstream or upstream) that belongs to a load balancing group.
Group Number of the load balancing group to which the cable interface has been assigned.
Field Description
Utilization This field is a long-term average of the upstream utilization and displays current load usage of
the cable interface expressed as a percentage of the total bandwidth. For upstreams, this field
shows a single percentage value, which is the average percentage of bandwidth being used on
the upstream.
For downstreams, this field shows a set of three percentage values:
• The percentage shows the load usage for the entire interface.
• The first percentage, within the parentheses, shows the load for the downstream.
• The second percentage, within the parentheses, shows the average load for all upstreams
on the downstream.
For example, if this field shows “ 18%(18%/12%)”, it indicates that downstream and upstream
channels on the interface are running on an average load of 18 percent. The downstream is
running on an average load of 18 percent and all upstreams for this downstream are running on
an average load of 12 percent.
Note To view the short-term average of the utilization, use the show interface cable
mac-scheduler command.
State Current state of the cable interface.
The following states indicate normal operational states, depending on the configuration:
• down—Interface is shut down. The CMTS cannot use the interface for load balancing in
this state.
• initial—Interface is currently in the initialization phase. The CMTS uses the interface for
load balancing after the initialization completes.
• up—Interface is up and passing traffic. The CMTS actively uses the interface for load
balancing.
• testing—Interface is currently under a load balancing test. The CMTS is unable to use the
interface for normal load balancing operations until the test completes.
The following states indicate abnormal states. The CMTS does not use interfaces in these states
for load balancing operations, but continues to monitor and update the status every time the
CMTS polls the interfaces for their current load usage:
• suspicious—Interface is in an unknown state. The interface might be up and passing
traffic, but is not consistent enough to support load balancing operations. The CMTS
attempts to reinitialize the interface after a timeout period. If the interface has failed
initialization more than 10 times, the CMTS moves the interface to the disabled state.
• disabled—Interface has been disabled because a load balancing test is in-progress or
because the interface reinitialization failed after 10 attempts.
• unstable—Interface has failed repeated initialization attempts. The CMTS will attempt to
reinitialize the interface after a timeout period. If a load balance test is not in-progress and
if reinitialization fails, the CMTS moves it to the unstable state.
Reserved Percentage of bandwidth that is currently reserved by unsolicited grant service (UGS) service
flows.
Modems Number of cable modems currently online on this cable interface.
Flows Number of service flows currently active on the cable interface.
Field Description
Weight Interface bandwidth, in megabits per second (mbps), for the downstream or upstream. The
system uses this value in calculating whether the loads on the interfaces are balanced.
Changing a channel parameter, such as modulation profile or channel width, affects the channel
bandwidth and weight value.
Additional Fields When Displaying Load Balancing Groups
Interval Indicates in seconds, the current load on each cable interface in the load balancing group as
configured using the cable load-balance group interval command.
Method Load balancing method used for the load balancing group as configured using the cable
load-balance group (global configuration) command.
Threshold Thresholds configured for this load balancing group:
• M = Minimum
Minimum difference in the number of cable modems or service flows that can exist on two
interfaces in the group before cable modems are moved between the interfaces. If the
imbalance between interfaces is below this value, cable modems are not moved. This field
contains a value only when the group is configured for the modems or service flows
method of load balancing. (This value is configured using the load minimum option of the
cable load-balance group threshold command.)
• S = Static
Minimum difference in the percentage of total load that must exist between interfaces in a
load balancing group before the Cisco CMTS performs static load balancing. When the
load between interfaces is greater than this value, cable modems that are in the process of
registering with the CMTS are moved between interfaces until the load difference is again
below this value. (This value is configured using the load option of the cable load-balance
group threshold command.)
• E = Enforce
Minimum difference in the percentage of total load that must exist between interfaces in a
load balancing group before the Cisco CMTS performs dynamic load balancing and begins
moving cable modems that are currently online. When the difference in load between two
interfaces falls below this value, the CMTS stops dynamic load balancing and performs
static load balancing. (This value is configured using the enforce option of the cable
load-balance group threshold command.)
• U = Ugs
Percentage of the bandwidth that is allocated for Unsolicited Grant Services (UGS) traffic,
such as Voice-over-IP (VoIP), that is in use on an interface because the CMTS moves cable
modems that are online with active UGS service flows. (This value is configured using the
ugs option of the cable load-balance group threshold command.)
• P = PacketCable MultiMedia (PCMM)
• Percentage of the reserved bandwidth threshold. Above this level, cable modems with
active PCMM service flows participate in load balancing. The default threshold is 70%.
Field Description
Additional Fields for the target Option
Interface Source downstream or upstream interface that is part of a cable load balancing group. If the
Target field contains a value, it indicates that the source interface is currently oversubscribed.
To reduce the cable load, the CMTS moves cable modems from the source interface to the
target interface.
Target Downstream or upstream interface to which cable modems on the source interface are being
moved as part of load balancing operations. This field indicates the following:
• If it is a downstream interface, the display shows the center frequency of the downstream
within parentheses.
• If only a frequency is shown, it indicates that the CMTS is moving cable modems to a
different center frequency on the same downstream interface.
• When the display includes the words “enforce”, it indicates that the CMTS is performing
dynamic load balancing on the interfaces.
• If this field is blank, it indicates that the source interface is not oversubscribed.
Additional Fields for the statistics Option
Target interface Downstream or upstream interface. If this is a downstream interface, the display shows the
center frequency of the downstream within parentheses.
Transfers The following information is tracked for the indicated target interface:
• complete—Number of cable modems successfully moved to the target interface.
• pending—Number of cable modems in the process of being moved to the target interface.
• retries—Number of times that the CMTS unsuccessfully tried to move the same cable
modem to the target interface. This occurs when one or more MAC layer messages to the
cable modem are dropped due to radio frequency (RF) noise or because the modem is not
DOCSIS-compliant. If the number of retries exceeds five for a particular cable modem, the
CMTS counts this as a failure.
• failures—Number of times that the CMTS exceeded the maximum number of allowable
retries (5) when trying to move a particular cable modem to the target interface. A large
number of failures could indicate one or more possible problems:
– The specific cable modems are not DOCSIS-compliant.
– One or both interfaces are having problems passing traffic.
– One or both interfaces are having persistent RF noise problems.
– The source and target interfaces are not combined in the same node and do not share
the same physical connectivity (which is required when interfaces are part the same
load balancing group).
Additional Fields for the pending Option
Modem Hardware (MAC) address of the cable modem that is moved as part of load balancing
operations.
Source interface Downstream or upstream cable interface on which the cable modem is currently online.
Field Description
Target interface Downstream or upstream cable interface to which the CMTS is trying to move the cable modem
to load balance the interfaces in this load balancing group. If the CMTS is moving the cable
modem to a different frequency on the same downstream interface, this field shows only the
new center frequency.
Retries Number of times that the CMTS has attempted to move this cable modem to the target
interface. The CMTS attempts to move the cable modem 5 times before counting this load
balancing move as a failure.
Additional Fields for the fiber-node-validation Option
DOCSIS LBG ID The DOCSIS LBG ID.
Channel The upstream or downstream channel that is associated with the DOCSIS LBG.
Fiber-node list The list of all fiber nodes that include the channel.
show cable load-balance docsis-group {docsis-group-id | {FN fn-id MD cable slot/port }} [all |
load | pending | statistics | target | modem-list]
Syntax Description docsis-group-id DOCSIS load balancing group ID. The group ID is in the range of 1 to
2147483647.
FN fn-id Specifies the fiber node (FN) where certain DOCSIS 3.0 GLBG parameters,
such as disable, docsis-policy, init-tech-list, interval, method, policy, and
threshold, can be configured.
MD cable Specifies the MAC domain interface of the fiber node.
slot/subslot/port
• slot—Slot where the line card resides. The permitted range is from 5 to
8.
• subslot—Subslot where the line card resides. The available slots are 0
or 1.
• port—The downstream controller number on the line card. The
permitted port range is from 0 to 4.
MD cable slot/port Specifies the MAC domain interface of the fiber node on the
Cisco uBR7246VXR or Cisco uBR7225VXR routers.
• slot—Slot where the line card resides.
– Cisco uBR7225VXR router—The valid range is from 1 to 2.
– Cisco uBR7246VXR router—The valid range is from 3 to 6.
• port—The downstream controller number on the line card. The
permitted port values are 0 or 1.
all (Optional) Displays all load balancing group information.
load (Optional) Displays current interface load and load balancing group (LBG)
assignments.
pending (Optional) Displays a list of cable modems that are pending movement from
one downstream/upstream to another.
statistics (Optional) Displays cumulative statistics of load balancing operations for
one group.
target (Optional) Displays current and target interfaces (upstream and
downstream) used for load balancing.
modem-list (Optional) Displays cable modems assigned to the specified DOCSIS LBG.
Defaults Displays information of all load balancing groups for each cable interface with its current load and load
balancing status.
Usage Guidelines Use the show cable load-balance docsis-group command to display the current, real-time statistics for
load balancing operations.
Examples The following is a sample output of a show cable load-balance docsis-group command.
The following is a sample output of the show cable load-balance docsis-group all command. This
command displays information of all options in this command.
Current load:
Interface State Group Utilization Reserved Modems Flows Weight
Index
Cable1/0 (453 MHz) up 82 0%(0%/0%) 0% 13 26 26
Cable1/0/U2 down 82 0% 0% 0 0 0.0
Cable1/1 (459 MHz) initial 82 0%(0%/0%) 0% 0 0 26
Cable1/1/U0 initial 82 0% 0% 0 0 2.5
Cable1/1/U1 initial 82 0% 0% 0 0 2.5
Cable1/1/U2 initial 82 0% 0% 0 0 2.5
Cable1/1/U3 initial 82 0% 0% 0 0 2.5
Target assignments:
Statistics:
Pending:
The following is a sample output of the show cable load-balance docsis-group load command.
The following is a sample output of the show cable load-balance docsis-group pending command.
The following is a sample output of the show cable load-balance docsis-group statistics command.
The following is a sample output of the show cable load-balance docsis-group target command.
The following is a sample output of the show cable load-balance docsis-group FN fn-id MD cable
slot/subslot/port command:
The following is a sample output of the show cable load-balance docsis-group modem-list
command:
Table 61 describes the fields shown in the show cable load-balance docsis-group display.
Field Description
Fields for the Default Display and all Option
DOCSIS Group Displays the current number of DOCSIS groups created on
the CMTS.
Group Index Number of the load balancing group to which the cable
interface has been assigned.
Status Displays the following information about the DOCSIS LBG:
• R—Restricted load balancing group (RLBG).
• G—General load balancing group (GLBG).
• E—The DOCSIS LBG is enabled.
• D—The DOCSIS LBG is disabled.
Interval Minimum time period configured when cable modems can be
moved to load balance the interfaces.
DCC mask/UCC Downstream and upstream channel change masks associated
with the DOCSIS group.
For example, in the output ‘0x40(1)/Y’, ‘0x40’ indicates that
the user configured the dynamic channel change (DCC)
technique 1 for the DOCSIS LBG. Similarly, '0x80' indicates
configured DCC technique 0 and '0x20' indicates configured
DCC technique 2. '(1)' indicates the DCC technique 1 is used
to move the cable modem (CM). '/Y' indicates that load
balancing sends upstream channel change (UCC) for
movement of US channel only.
Policy DOCSIS policy associated with the load balancing group.
Field Description
Method Load balancing method used for the load balancing group.
The following indicates what method is used for DS and US
modems:
• m = modem
Uses the number of active cable modems on an interface.
• s = service flow
Uses the number of active Service Flow IDs (SFIDs) on
an interface.
• u = utilization
Uses the current percent of utilization of an interface.
Field Description
Threshold Thresholds configured for this load balancing group:
• M = Minimum
Minimum difference in the number of cable modems or
service flows that can exist on two interfaces in the group
before cable modems are moved between the interfaces.
If the imbalance between interfaces is below this value,
cable modems are not moved. This field contains a value
only when the group is configured for the modems or
service flows method of load balancing. (This value is
configured using the load minimum option of the cable
load-balance group threshold command.)
• S = Stability.
Minimum allowable percentage of good periodic ranging
requests that is acceptable. When the channel has a lower
percent of modems responding to the ranging requests in
a one minute period, the Cisco CMTS begins moving
modems. The valid range is 0 to 100 percent, with a
default of 50 percent.
• E = Enforce
Minimum difference in the percentage of total load that
must exist between interfaces in a load balancing group
before the Cisco CMTS performs dynamic load
balancing and begins moving cable modems that are
currently online. When the difference in load between
two interfaces falls below this value, the CMTS stops
dynamic load balancing and performs static load
balancing. (This value is configured using the enforce
option of the cable load-balance group threshold
command.)
• U = Ugs
Percentage of the bandwidth that is allocated for
Unsolicited Grant Services (UGS) traffic, such as
Voice-over-IP (VoIP), that is in use on an interface
because the CMTS moves cable modems that are online
with active UGS service flows. (This value is configured
using the ugs option of the cable load-balance group
threshold command.)
• P = PacketCable MultiMedia (PCMM)
Percentage of the reserved bandwidth threshold. Above
this level, cable modems with active PCMM service
flows participate in load balancing. The default threshold
is 70%.
Interface Cable interface (downstream or upstream) that belongs to a
load balancing group.
Field Description
Utilization This field is a long-term average of the upstream utilization
and displays current load usage of the cable interface
expressed as a percentage of the total bandwidth. For
upstreams, this field shows a single percentage value, which
is the average percentage of bandwidth being used on the
upstream.
For downstreams, this field shows a set of three percentage
values:
• The percentage shows the load usage for the entire
interface.
• The first percentage, within the parentheses, shows the
load for the downstream.
• The second percentage, within the parentheses, shows
the average load for all upstreams on the downstream.
For example, if this field shows “18%(18%/12%)”, it indicates
that downstream and upstream channels on the interface are
running on an average load of 18 percent. The downstream is
running on an average load of 18 percent and all upstreams
for this downstream are running on an average load of 12
percent.
Note To view the short-term average of the utilization, use
the show interface cable mac-scheduler command.
Field Description
State Current state of the cable interface.
The following states indicate normal operational states,
depending on the configuration:
• down—Interface is shut down. The CMTS cannot use the
interface for load balancing in this state.
• initial—Interface is currently in the initialization phase.
The CMTS uses the interface for load balancing after the
initialization completes.
• up—Interface is up and passing traffic. The CMTS
actively uses the interface for load balancing.
• testing—Interface is currently under a load balancing
test. The CMTS is unable to use the interface for normal
load balancing operations until the test completes.
The following states indicate abnormal states. The CMTS
does not use interfaces in these states for load balancing
operations, but continues to monitor and update the status
every time the CMTS polls the interfaces for their current
load usage:
• suspicious—Interface is in an unknown state. The
interface might be up and passing traffic, but is not
consistent enough to support load balancing operations.
The CMTS attempts to reinitialize the interface after a
timeout period. If the interface has failed initialization
more than 10 times, the CMTS moves the interface to the
disabled state.
• disabled—Interface has been disabled because a load
balancing test is in-progress or because the interface
reinitialization failed after 10 attempts.
• unstable—Interface has failed repeated initialization
attempts. The CMTS will attempt to reinitialize the
interface after a timeout period. If a load balance test is
not in-progress and if reinitialization fails, the CMTS
moves it to the unstable state.
Reserved Percentage of bandwidth that is currently reserved by
unsolicited grant service (UGS) service flows.
Modems Number of cable modems currently online on this cable
interface.
Flows Number of service flows currently active on the cable
interface.
Field Description
Weight Interface bandwidth, in megabits per second (mbps), for the
downstream or upstream. The system uses this value in
calculating whether the loads on the interfaces are balanced.
Changing a channel parameter, such as modulation profile or
channel width, affects the channel bandwidth and weight
value.
Field Description
Transfers The following information is tracked for the indicated target
interface:
• complete—Number of cable modems successfully
moved to the target interface.
• pending—Number of cable modems in the process of
being moved to the target interface.
• retries—Number of times that the CMTS unsuccessfully
tried to move the same cable modem to the target
interface. This occurs when one or more MAC layer
messages to the cable modem are dropped due to radio
frequency (RF) noise or because the modem is not
DOCSIS-compliant. If the number of retries exceeds five
for a particular cable modem, the CMTS counts this as a
failure.
• failures—Number of times that the CMTS exceeded the
maximum number of allowable retries (5) when trying to
move a particular cable modem to the target interface. A
large number of failures could indicate one or more
possible problems:
– The specific cable modems are not
DOCSIS-compliant.
– One or both interfaces are having problems passing
traffic.
– One or both interfaces are having persistent RF noise
problems.
– The source and target interfaces are not combined in
the same node and do not share the same physical
connectivity (which is required when interfaces are
part the same load balancing group).
Additional Fields for the pending Option
Modem Hardware (MAC) address of the cable modem that is moved
as part of load balancing operations.
Source interface Downstream or upstream cable interface on which the cable
modem is currently online.
Target interface Downstream or upstream cable interface to which the CMTS
is trying to move the cable modem to load balance the
interfaces in this load balancing group. If the CMTS is
moving the cable modem to a different frequency on the same
downstream interface, this field shows only the new center
frequency.
Retries Number of times that the CMTS has attempted to move this
cable modem to the target interface. The CMTS attempts to
move the cable modem 5 times before counting this load
balancing move as a failure.
Field Description
Additional Fields for the modem-list option
US Displays the upstream channels in the DOCSIS LBG.
MAC Address Displays the total number (in parentheses) and MAC
addresses of the modems connected to the upstream channels.
Syntax Description badipsource Displays the contents of the error log buffer containing the error messages
for bad IP source addresses.
summary Displays the status of the logging feature and its buffer.
slot (Optional) Displays the log for a particular cable interface on the
Cisco uBR7200 series router. The slot parameter can range from 3 to 6,
depending on the cable interface.
Note This option is supported only on the Cisco uBR-MC16U/X,
Cisco uBR10-MC5X20U, Cisco uBR10-MC5X20H and
Cisco uBR-MC28U/X cable interface line card.
Usage Guidelines For additional information about the Cable Duplicate MAC Address Reject feature on the Cisco CMTS,
or enforced DOCSIS 1.1 security, refer to the following document on Cisco.com:
Examples The following example shows a typical display of the show cable logging badipsource command. The
oldest messages are displayed first.
Router# show cable logging badipsource
The following example shows the display of the show cable logging badipsource command when
logging has not been enabled with the cable logging badipsource command:
Router# show cable logging badipsource
The following example shows a typical display for the summary option, showing whether logging is
enabled, the total size of the buffer, how many bytes are currently used, and how many error messages
have been logged since the buffer was last cleared.
Router# show cable logging summary
The following example shows a typical display for the summary option, indicating the line card’s CPU
revision number. The display given below is specific to the uBR7200 series routers.
Router# show cable logging summary slot 6
Current LC State Info for slot 6
CLC CPU: BCM1250(Rev A8/A10)
- Status - NO NPE/CLC OIR Timeout detected
Related Commands cable logging badipsource Logs error messages about bad IP source addresses on the cable
interfaces.
cable source-verify Enables verification of IP addresses for CMs and CPE devices on the
upstream.
clear cable logging Removes all error messages about bad IP source addresses on the
cable interfaces from the error log buffer.
New Commands
Modified Commands
Syntax Description slot Specifies the chassis slot number of the cable interface line card. Valid
values are 5 to 8.
subslot Specifies the secondary slot number of the cable interface line card. Valid
subslots are 0 or 1.
port Specifies the port number. Valid values are 0 to 4 (depending on the cable
interface).
Examples
Note The show cable mac-domain cable forwarding command does not support wideband and modular
interfaces. However, if wideband and modular interfaces belong to the Mac domain, the interfaces are
listed in the output with the interface state.
The following is sample output of the show cable mac-domain cable forwarding command on the
cable interface at 8/0/0:
Router# show cable mac-domain cable 8/0/0 forwarding
Field Description
Interface Name The name of the interface belonging to Mac
domain.
Output Packets/Rate The cumulative packets output and output rate.
Interface Bandwidth The total interface bandwidth allocated.
Reserved/Reservable Bandwidth The total reserved and available bandwidth.
Interface State Indicates whether the interface is up or down.
Syntax Description cable Identifies the cable interface on the Cisco uBR10012 router.
slot/subslot/port
• slot—Slot where the line card resides. The valid range is from 5 to 8.
• subslot—Subslot where the line card resides. Available slots are 0 or 1.
• port—Downstream controller number on the line card. Valid port values are
from 0 to 4.
cable slot/port Identifies the cable interface on the Cisco uBR7246VXR or Cisco uBR7225VXR
router.
• slot—Slot where the line card resides.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
• port—Downstream port number on the line card. The valid port value is 0 or 1.
Usage Guidelines The show cable mac-domain cgd-associations command displays the following information for each
cable MAC domain:
• Shared port adapter (SPA) downstream channels that have been added to each MAC domain.
• Upstream channels associated with each SPA downstream channel and the downstream channels of
the integrated cable interface line card.
If the All column in the command output indicates Y, then this indicates that all upstream channels
associated with the line card downtream channels or SPA downstream channels are configured using
the upstream cable connector command. If all upstream channels are not configured, then this
column will not display.
• The SPA downsteam channels that are currently active.
A SPA downstream channel is active when the corresponding modular cable interface, which
represents the SPA downstream channel, and its line protocol are up. A SPA downstream channel
that is considered active is an operational primary downstream channel in the cable MAC domain.
Note For more information on Channel Grouping Domains, refer to the Cisco DOCSIS 3.0 Downstream
Solution Design and Implementation Guide, Release 2.0.
Usage Guidelines Use the show cable mac-domain downstream-service-group command to display MAC Domain
Downstream Service Group (MD-DS-SG) information for the specified primary downstream channel.
For each fiber node, a traditional DOCSIS downstream channel on a Cisco uBR10-MC5X20 cable
interface line card is used to carry MAC management and signaling messages, and the associated
traditional DOCSIS upstream channel is used for return data traffic and signaling. The traditional
DOCSIS downstream channel used in this way for a MAC domain is called the primary downstream
channel.
Note Beginning in Cisco IOS Release 12.3(23)BC, either an RF channel from the SPA or a
Cisc uBR10-MC5X20 downstream channel can serve as a primary channel in a fiber node. Changes in
Cisco IOS Release 12.3(23)BC apply to Cisco IOS Release 12.2(33)SCB and do not apply to
Cisco IOS Release 12.2(33)SCA.
Examples The following two examples display show cable mac-domain downstream-service-group output for
the primary downstream channel on the cable interface at slot/subslot/port 5/0/0:
Primary MD-DS-SG RF
IF Id SPA Chan
C5/0/0 1 1/0/0 0 - 1
In the preceding examples, the MD-DS-SG with ID 1 is used for RF channels 0 and 1 on the Wideband
SPA located in slot/subslot/bay 1/0/0.
Examples The following is a sample output of the show cable mac-domain rcc command on the cable interface at
slot/subslot/port 8/0/0:
Router# show cable mac-domain cable 8/0/0 rcc
The following is a sample output of the show cable mac-domain rcc command on the cable interface at
slot/port 5/0:
Router# show cable mac-domain cable 5/0 rcc
Field Description
RCC-ID RCC index per MAC domain. The RCC ID refers
to the RCC ID output from the show cable modem
wideband command.
RCP The receive channel profile associated with the
RCC object.
RCs Total number of DS channels.
MD-DS-SG Indicates the MAC domain DS service group for
which the RCC is generated.
CM Total number of CMs associated with the RCC
object.
WB/RCC-TMPL Indicates the wideband interface or the RCC
template.
Note A zero value in the RCP or MD-DS-SG field indicates that the RCC is generated directly through a
wideband interface configuration and not through any RCC templates.
Syntax Description slot Chassis slot number of the cable interface line card. The valid range is from
0 to 8.
subslot Secondary slot number of the cable interface line card. Valid values are 0 or
1.
port Port number. The valid range is from 0 to 4 (depending on the cable
interface).
upstream-service-grou Specifies the upstream service group number.
p
Usage Guidelines This command displays privacy information of a particular CM, identified by its IP address or MAC
address.
Examples The following is a sample output of the show cable mac-domain upstream-service-group command
on the cable interface line card at slot/subslot/port 7/1/0:
Router# show cable mac-domain cable 7/1/0 upstream-service-group
Cable MD 7/1/0
US-SG-ID : 1 US-Chan : U0,1,2,3,4
Primary-DS: 5/1/0:0 US-SG-ID: 1
MDD US-List : U0,1,2,3
MDD Ambiguity : U0,1,2,3
Primary-DS: 3/0/0:0 US-SG-ID: 1
MDD US-List : U0,1,2,3,4
MDD Ambiguity : U0,1,2,3,4
Primary-DS: 3/0/0:1 US-SG-ID: 1
MDD US-List : U0,1,2,3,4
MDD Ambiguity : U0,1,2,3,4
Primary-DS: 3/0/0:2 US-SG-ID: 1
MDD US-List : U0,1,2,3,4
MDD Ambiguity : U0,1,2,3,4
Primary-DS: 3/0/0:3 US-SG-ID: 1
MDD US-List : U0,1,2,3,4
MDD Ambiguity : U0,1,2,3,4
Field Description
US-SG-ID Upstream service group ID.
US-chan Total number of upstream channels on the cable interface line
card.
Primary-DS The primary downstream interface.
MDD US-List MAC management message: MDD TLV type 7 content,
upstream active channel list.
MDD Ambiguity MAC management message: MDD TLV type 8 content,
upstream ambiguity resolution channel list.
Syntax Description verbose (Optional) Displays the information in a more readable format.
Usage Guidelines The show cable metering-status command displays information about the most recent successful
usage-based billing operation. If usage-based billing is configured for File mode, this command displays
the device and file name for the record that was last written. If usage-based billing is configured for
Streaming mode, this command displays the IP address and port number for the external server to which
the billing record was sent.
Note This command displays the status of the last successful billing record operation. If a failure occurred,
the CMTS sends an SNMP trap to the SNMP manager with that information.
Examples The following example shows a typical output for the show cable metering-status command when
usage-based billing is configured to write the billing records to a local file system:
Router# show cable metering-status
destination complete-time
flow cpe status
aggr supp
disk0:R7519-UBR7246-200308-004428 Jun 12 09:33:05 No No success
The following example shows a typical output for the show cable metering-status command when
usage-based billing is configured to stream the billing records to an external server:
Router# show cable metering-status
The following example shows a typical output for the verbose form of the show cable metering-status
command:
Router# show cable metering-status verbose
Destination : disk0:R7519-UBR7246-20000308-004428
Complete Time : Jun 12 09:33:05
Flow Aggregate : Yes
Cpe list suppression : Yes
Status of last export : success
The following example shows a typical output for the show cable metering-status command when
usage-based billing is configured to use the Internet Protocol Detail Record (IPDR) Exporter to stream
the billing records to an external server:
Router# show cable metering-status
destination complete-time flow cpe status
aggr supp
IPDR_Session1 Jun 12 09:33:05 N/A N/A success
The following example shows a typical output for for the verbose form of the show cable
metering-status command when usage-based billing is configured to use the IPDR Exporter to stream
the billing records to an external server:
Router# show cable metering-status verbose
Last export status
Destination : IPDR_Session1
Complete Time : Jun 12 09:36:05
Status of last export : success
The following example shows the error message that is displayed when you enter the show cable
metering-status command but not have enabled usage-based billing:
Router# show cable metering-status
Table 65 describes the fields displayed by the show cable metering-status command.
Field Description
destination, Destination Destination for the billing records. This is a file system device name
and file name, if records are being written to a local file system, or
an IP address and TCP port number, if records are being streamed
to an external server.
complete_time, Complete Time Date and time when the last billing record was written to a local file
or streamed to an external server.
flow aggr, Flow Aggregate Indicates whether traffic counters are aggregated in the billing
records, so that one total is recorded for the upstream service flows
and downstream service flows for each CM.
Field Description
cpe suppress, CPE list Indicates whether CPE IP addresses are included or suppressed in
suppression the billing records:
• Yes = CPE addresses are suppressed and are not included in the
billing records.
• No = CPE addresses are included in the billing records.
status, Status of last export Indicates the status of the last billing operation:
• success—The billing records were successfully written to the
filesystem (file mode) or transferred to the billing collection
server (streaming mode).
• connect-failed—The CMTS was able to open the proper socket
connection to the server but could not connect to the server.
• data-incomplete—A failure occurred during the file write or the
streaming to the collection server, and the records that were
written might be incomplete.
• disk-full—The billing records could not be written because the
filesystem does not have sufficient free space.
• no-memory—The processor had insufficient memory to collect
the billing records.
• open-failure—The transfer failed because the CMTS could not
open a new file on the filesystem (file mode) or open a socket
to the destination IP address and port (streaming mode).
• unknown—An unknown error occurred.
• write-error—The operating system reported an error when
attempting to write the billing records (file mode), or the send
to the destination socket failed (streaming mode).
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] queue
[verbose] [cm-status]
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] [verbose] [cm-status]
Syntax Description ip-address (Optional) IPv4 or IPv6 address of a specific CM to be displayed. If you
specify the IP address for a CPE device behind a CM, information for that
CM is displayed.
mac-address (Optional) MAC address of a specific CM to be displayed. You can also
specify the MAC address for a CPE device behind a CM, and information for
that CM will be displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port:
• slot—Slot where the line card resides:
– Cisco uBR7100 series router: The valid value is 1.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
• port—Downstream port number:
– Cisco uBR7100 series router: The valid value is 0.
– Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid
value is 0 or 1.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Chassis slot number of the cable interface line card. Valid slots are
5 to 8.
• subslot—Secondary slot number of the cable interface line card. Valid
subslots are 0 or 1.
• port—Downstream port number. Valid ports are 0 to 4, depending on the
cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
verbose Displays detailed information for the CMs.
cm-status Displays CM status events.
queue Displays the downstream hierarchical queueing framework (HQF) queue
information for a cable modem.
Command History This table includes the following release-specific history entries:
• BC Release
• C Release
• E Release
• N Release
• SC Release
• T Release
• X Release
BC Release Modification
12.2(15)BC1 Additional lines were added to the show cable modem verbose displays,
for one or all cable modems, to show information about the dynamic
shared-secret feature. Cable modems that fail the dynamic secret
authentication checks and then come online are marked with an exclamation
point (!), so that this situation can be investigated.
12.2(4)BC1 Support was added for the Cisco uBR10012 router.
12.2(8)BC2 The output for the Online State field was updated for the cable tftp-enforce
command. A pound sign (#) appears next to the state value when a CM was
allowed to come online without attempting to download a DOCSIS
configuration file through the cable interface with the Cisco CMTS.
12.2(15)BC1c The verbose option displays whether dynamic service change requests
(DSX) are allowed from cable modems.
12.2(15)BC2 Two new states—cc(r1) and cc(r2)—have been added to the CM MAC state
field (see Table 67) to indicate the CM status when it has been instructed to
change channels and is ranging to obtain a new downstream or upstream
channel.
Also, three new states—online(pkd), online(ptd), and expire(pkd)—were
added to clarify the BPI state when network access has been disabled in the
CM’s DOCSIS configuration file.
In addition, the show cable modem verbose command now displays the
total amount of time that a CM has been online since last registering.
12.3(13a)BC New initialization states were added for the MAC State Field:
• init(d)—The Cisco CMTS has seen DHCPDISCOVER
• init(io)—The Cisco CMTS has seen DHCPOFFER
• init(dr)—The Cisco CMTS has seen DHCPREQUEST
• init(i)—The Cisco CMTS has seen DHCPACK
• init(o)—The Cisco CMTS has seen first TFTP packet for TFTP request
for cable modem configuration file
• init(t)—The Cisco CMTS has seen the TOD request
See Table 67 for additional information.
12.3(21)BC All cable bundles are now automatically converted and configured to be in
a virtual bundle, and standalone cable interfaces must be manually
configured to be in a virtual bundle to operate properly. Previously, new
virtual interface bundles and bundle members required reconfiguration, and
there could also be standalone interfaces not part of a bundle at all.
12.3(23)BC The verbose option displays additional information about the cable modem.
The following fields have been added to the output of this option:
• Host Interface
• Primary Downstream
• Wideband Capable
• Voice Enabled
• DS Change Times
C Release Modification
12.1(4)CX Support was added for the Cisco uBR10012 router.
12.2(15)CX The verbose option displays the sysDescr field for each cable modem, when
the cable modem remote-query command has been configured. Other
fields have also been added to support DOCSIS 2.0 (ATDMA) operation.
E Release Modification
12.1(10)EC1 Adds an exclamation point to CMs that have exceeded the maximum
delay/timing offset specified by the cable map-advance command.
12.1(11b)EC1 The output for the Online State field was updated for the cable tftp-enforce
command. A pound sign (#) appears next to the state value when a CM was
allowed to come online without attempting to download a DOCSIS
configuration file through the cable interface with the Cisco CMTS.
12.1(20)EC1 The three new states—online(pkd), online(ptd), and expire(pkd)—were
added to the Cisco IOS Release 12.1 EC train.
N Release Modification
11.3(5)NA The output was reorganized and the Receive Power field was added.
SC Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA, with
the following changes:
• Support for the Cisco uBR7225VXR router was added.
• Support for specifying the IPv6 address of a CM or CPE device was
added.
• The name keyword option was added for specifying the fully-qualified
domain name of a CM.
• The output column spacing and headings were changed, including
some of the following changes:
– “BPI Enb” has been changed to “BPI”
– “DIP” output field was added to indicate support of dual IP for both
IPv4 and IPv6 addressing.
• The following new initialization states were added to show
initialization of CMs and CPEs supporting IPv6:
– init6(s)—CMTS router has seen SOLICIT message.
– init6(a)—CMTS router has seen ADVERTISE message.
– init6(r)—CMTS router has seen REQUEST message.
– init6(i)—CMTS router has seen REPLY message.
– init6(o)—CMTS router has seen version 6 TFTP request.
– init6(t)—CMTS router has seen version 6 TOD request.
12.2(33)SCB A new keyword, cm-status, was added to display CM status events.
12.2(33)SCC This command was modified with the following changes:
• The command output displays the CM attribute bitmasks.
• The command output provides basic receive-statistics for all event code
types of the specified CM.
12.2(33)SCD This command was modified. The cm-status keyword was added to display
the CM status events and the queue keyword was added to display
downstream HQF queue information on the Cisco uBR7225VXR and
Cisco uBR7246VXR routers.
12.2(33)SCD2 This command was modified. The command output was modified to display
the cable modems that are in upstream and downstream partial service
mode.
T Release Modification
2.1(1a)T1 The output of this command was enhanced to show that the Cisco CMTS
has detected an unstable return path for a particular CM and has
compensated with a power adjustment. An asterisk (*) appears in the power
adjustment field for a modem when a power adjustment has been made; an
exclamation point (!) appears when the CM has reached its maximum power
transmit level and cannot increase its power level further.
12.0(7)T The detail option was replaced with the verbose option.
X Release Modification
11.3XA This command was introduced.
12.0(4)XI The output was expanded to show the primary service identifier (SID) and
the customer premises equipment (CPE) count.
12.0(7)XR The output of this command was enhanced to show that the Cisco CMTS
has detected an unstable return path for a particular CM and has
compensated with a power adjustment. An asterisk (*) appears in the power
adjustment field for a modem when a power adjustment has been made; an
exclamation point (!) appears when the CM has reached its maximum power
transmit level and cannot increase its power level further.
This command displays information for all CMs, for all CMs attached to a specific CMTS cable
interface, or for a particular CM, identified by its IP address, MAC address, or its domain name. The
output is sorted by the cable interface and the CM MAC address.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip Several options in the show cable modem command do not pause the screen to display the information
page by page, even if the terminal length command has been used to set the page size of your terminal.
Paging and pausing the display could result in outdated or stale information for CMs, and thus produce
an incorrect snapshot of the current CM state of the system. To capture or review this information, use
your terminal program’s capture buffer to save the information to a file, and then review it offline.
Tip You can also specify the MAC address or IP address for a CPE device, and the Cisco CMTS will display
the information for the CM that is associated with that CPE device in its internal database.
Note If the CPE IP address is no longer associated with a cable modem, the show cable modem command
might not display information about the cable modem. To display the IP address of the CPE device for
the cable modem, use the clear cable host ip-address command to clear the IP address of the modem
from the router database, and then enter the ping docsis mac-address command, which resolves the
MAC address by sending the DOCSIS ping to the CM.
Refer to the following document on Cisco.com for additional information about cable interface bundling
and virtual interface bundling on the Cisco CMTS:
• Cable Interface Bundling and Virtual Interface Bundling on the Cisco CMTS
In addition, when HCCP redundancy has been configured, the Cisco IOS software automatically
synchronizes the secondary, backup cards whenever the configuration is changed. The cards can also be
synchronized manually, using the hccp resync command. When a SYNC event command is occurring,
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Operation of the show cable modem Commands with Different Cable Interface Line Cards
The show cable modem commands display the most current information for standard cable interface
line cards. If the card itself is down, the show cable modem commands still show whatever information
is appropriate (such as offline cable modems and flap list information).
The show cable modem commands function slightly different when used on routers that are using
Broadband Processing Engine (BPE) cable interface line cards (such as the Cisco uBR-MC16U/X,
Cisco uBR-MC28U/X, or Cisco uBR10-MC5X20S/U/H). When BPE cards are the only cable interface
cards installed, the show cable modem commands do not display any output until at least one BPE card
is up and communicating with the router processor. If the BPE cards are not yet up, the show cable
modem command does not display any output.
Examples Example of the show cable modem Command Output for all CMs
The following sample output from the show cable modem command shows the default CM displays for
individual CMs.
Router# show cable modem
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPEs Enbld
0010.7b6b.58c1 0.0.0.0 C4/0/U5 offline 5 -0.25 2285 0 yes
0010.7bed.9dc9 0.0.0.0 C4/0/U5 offline 6 -0.75 2290 0 yes
0010.7bed.9dbb 0.0.0.0 C4/0/U5 offline 7 0.50 2289 0 yes
0010.7b6b.58bb 0.0.0.0 C4/0/U5 offline 8 0.00 2290 0 yes
0010.7bb3.fcd1 10.20.113.2 C5/0/U5 online 1 0.00 1624 0 yes
0010.7bb3.fcdd 0.0.0.0 C5/0/U5 init(r1) 2 -20.00 1624 0 no
0010.7b43.aa7f 0.0.0.0 C5/0/U5 init(r2) 3 7.25 1623 0 no
Example of the show cable modem Command for a Specified MAC Address
Router# show cable modem 0010.7bb3.fcd1
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPEs Enbld
0010.7bb3.fcd1 10.20.113.2 C5/0/U5 online 1 0.00 1624 0 Y
Example of the show cable modem Command for all CMs on a Cisco uBR10012 Router
The following shows a typical display for a Cisco uBR10012 router:
Note The asterisk(*) in the Primary SID (Prim Sid) field indicates that the modem has service flows
with zero blaze index in Cisco IOS Release 12.3(23)BC.
In Cisco IOS Release 12.2(33)SCB and later, the asterisk that may appear in the Primary SID
field does not signify anything.
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
0010.9507.01db 144.205.151.130 C5/1/0/U5 online(pt) 1 0.25 938 1 N
0080.37b8.e99b 144.205.151.131 C5/1/0/U5 online 2 -0.25 1268 0 N
0002.fdfa.12ef 144.205.151.232 C6/1/0/U0 online(pt) 13 -0.25 1920 1 N
0002.fdfa.137d 144.205.151.160 C6/1/0/U0 online *16 -0.50 1920 1 N
0003.e38f.e9ab 144.205.151.237 C6/1/0/U0 online 3 -0.50 1926 1 N
0003.e3a6.8173 144.205.151.179 C6/1/1/U2 offline *4 0.50 1929 0 N
0003.e3a6.8195 144.205.151.219 C6/1/1/U2 online(pt) 22 -0.50 1929 1 N
0006.28dc.37fd 144.205.151.244 C6/1/1/U2 online(pt) 61 0.00 1925 2 N
0006.28e9.81c9 144.205.151.138 C6/1/1/U2 online(pt) 2 !0.75 1925 1 N
0006.28f9.8bbd 144.205.151.134 C6/1/1/U2 #online 25 -0.25 1924 1 N
0006.28f9.9d19 144.205.151.144 C6/1/1/U2 online(pt) 28 0.25 1924 1 N
0010.7bed.9b6d 144.205.151.228 C6/1/1/U2 online(pt) 59 0.25 1554 1 N
0002.fdfa.12db 144.205.151.234 C7/0/0/U0 online 15 -0.75 1914 1 N
0002.fdfa.138d 144.205.151.140 C7/0/0/U5 online 4 0.00 1917 1 N
0003.e38f.e85b 144.205.151.214 C7/0/0/U5 online 17 *0.25 1919 1 N
0003.e38f.f4cb 144.205.151.238 C7/0/0/U5 online(pt) 16 0.00 !2750 1 N
0003.e3a6.7fd9 144.205.151.151 C7/0/0/U5 online 1 0.25 1922 0 N
0020.4005.3f06 144.205.151.145 C7/0/0/U0 online(pt) 2 0.00 1901 1 N
0020.4006.b010 144.205.151.164 C7/0/0/U5 online(pt) 3 0.00 1901 1 N
0050.7302.3d83 144.205.151.240 C7/0/0/U0 online(pt) 18 -0.25 1543 1 N
00b0.6478.ae8d 144.205.151.254 C7/0/0/U5 online(pt) 44 0.25 1920 21 N
00d0.bad3.c0cd 144.205.151.149 C7/0/0/U5 online 19 0.25 1543 1 N
00d0.bad3.c0cf 144.205.151.194 C7/0/0/U0 online 13 0.00 1546 1 N
00d0.bad3.c0d5 144.205.151.133 C7/0/0/U0 online 12 *0.50 1546 1 N
Example of show cable modem Command Output When no CMs are Online
The following example shows sample output when the cable interface line cards are up, but no cable
modems are yet online:
Router# show cable modem
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
Example of show cable modem Command Output When no Cable Interface Line Cards are Up
The following example shows sample output when the Cisco CMTS router contains only Broadband
Processing Engine (BPE) cable interface line cards and none of the cable interface line cards are up:
Router# show cable modem
Example of show cable modem verbose Command Output for a Specified MAC Address
The following example shows sample output for the verbose option for a particular CM:
Router# show cable modem 0010.7bb3.fcd1 verbose
Prim Sid : 1
QoS Profile Index : 6
Interface : C5/0/U5
sysDescr : Vendor ABC DOCSIS 2.0 Cable Modem
Upstream Power : 0 dBmV (SNR = 33.25 dBmV)
Downstream Power : 0 dBmV (SNR = ----- dBmV)
Timing Offset : 1624
Initial Timing Offset : 2812
Received Power : 0.25
MAC Version : DOC1.0
Qos Provisioned Mode : DOC1.0
Enable DOCSIS2.0 Mode : Y
Phy Operating Mode : atdma
Capabilities : {Frag=N, Concat=N, PHS=N, Priv=BPI}
Sid/Said Limit : {Max Us Sids=0, Max Ds Saids=0}
Optional Filtering Support : {802.1P=N, 802.1Q=N}
Transmit Equalizer Support : {Taps/Symbol= 0, Num of Taps= 0}
Number of CPE IPs : 0(Max CPEs = 1)
CFG Max-CPE : 1
Flaps : 373(Jun 1 13:11:01)
Errors : 0 CRCs, 0 HCSes
Stn Mtn Failures : 0 aborts, 3 exhausted
Total US Flows : 1(1 active)
Total DS Flows : 1(1 active)
Total US Data : 1452082 packets, 171344434 bytes
Total US Throughput : 0 bits/sec, 0 packets/sec
Total DS Data : 1452073 packets, 171343858 bytes
Total DS Throughput : 0 bits/sec, 0 packets/sec
Active Classifiers : 0 (Max = NO LIMIT)
DSA/DSX messages : reject all
Dynamic Secret : A3D1028F36EBD54FDCC2F74719664D3F
Spoof attempt : Dynamic secret check failed
Total Time Online : 16:16
Note The “Number of CPES” field shows the value set for the CM, not the value for the CMTS that is set by
the cable modem max-cpe command. In Cisco IOS Release 12.2(15)BC1 and later releases, the verbose
display also includes information about the dynamic shared-secret feature (see the cable
dynamic-secret command).
Note An asterisk (*) in the Receive Power column indicates that a power adjustment has been made for that
CM. An exclamation point (!) in the Receive Power column indicates that the CM has reached its
maximum power transmit level and cannot increase its power level further. An exclamation point (!) in
the Timing Offset column indicates that the CM has exceeded the maximum delay and timing offset
specified by the cable map-advance command.
A pound sign (#) in the MAC State column indicates that the cable tftp-enforce mark-only command
has been used for the CM to attempt a TFTP download of the DOCSIS configuration file before
registering, but the CM did not do so (Cisco IOS Release 12.1(11b)EC1 and Cisco IOS
Release 12.2(8)BC2 or later releases).
Tip The show cable modem command displays the CM timing offset in DOCSIS ticks, while other
commands, such as cable map-advance, display the offset in microseconds. Use the following method
to convert microseconds to DOCSIS ticks: ticks = microseconds*64/6.25.
Example of the Updated show cable modem verbose Command Output for a Specified MAC Address in Cisco IOS
Release 12.3(23)BC
The following example shows sample output for the verbose option for a particular CM for the Cisco
IOS Release 12.3(23)BC with new output fields:
Router# show cable modem 0000.39b9.ac51 verbose
Note In Cisco IOS Release 12.3(23)BC, the output for this command does not display information
about dynamic shared secret.
Example of show cable modem Command Output for a CM or CPE With a Specified IPv6 Address
The following example shows sample output for the show cable modem command for a CM with the
IPv6 address of 2001:ODBA:4321:600:980D:E743:174F:1E48.
Note The IP Address field shows “---” because the IPv6 address is too long for the size of the output field. To
view a complete IPv6 address for a device, use the verbose form of the command.
Example of the show cable modem verbose Command Output That Shows CM Attribute Masks in Cisco IOS
Release 12.2(33)SCC
The following example shows the sample output for the verbose option for a particular CM in Cisco IOS
Release 12.2(33)SCC:
Router# show cable modem 001a.c3ff.ce9e verbose
Example of the show cable modem Command Output for a Cable Modem Operating in the MTC Mode
The following example shows the sample output for the verbose option for a particular CM operating in
the MTC mode in Cisco IOS Release 12.2(33)SCC:
Router# show cable modem 0014.f831.d596 verbose
RCP ID : 00 10 00 00 04
Multi-Transmit Channel Mode : Y
Upstream Channel : US1 US2 US3 US4
Ranging Status : sta sta sta sta
Upstream Power (dBmV) : 0.00 0.00 0.00 0.00
Upstream SNR (dB) : 36.12 36.12 36.12 33.1
Received Power (dBmV) : 0.00 1.00 0.00 -0.75
Reported Transmit Power (dBmV) : 45.00 45.00 45.00 54.75
Peak Transmit Power (dBmV) : 51.00 51.00 56.00 56.00
Minimum Transmit Power (dBmV) : 24.00 24.00 21.00 18.00
Timing Offset (97.6 ns): 2312 2281 2282 2282
Initial Timing Offset : 2314 2058 2058 2058
Rng Timing Adj Moving Avg(0.381 ns): 7 4 0 -94
Rng Timing Adj Lt Moving Avg : 63 30 11 -144
Rng Timing Adj Minimum : -512 -256 -256 -512
Rng Timing Adj Maximum : 256 57088 57344 57344
Pre-EQ Good : 0 0 0 0
Pre-EQ Scaled : 0 0 0 0
Pre-EQ Impulse : 0 0 0 0
Pre-EQ Direct Loads : 0 0 0 0
Good Codewords rx : 5012 4996 4992 4990
Corrected Codewords rx : 0 0 0 0
Uncorrectable Codewords rx : 0 0 0 0
Phy Operating Mode : atdma* atdma* tdma* tdma*
sysDescr :
Downstream Power : 0.00 dBmV (SNR = ----- dB)
MAC Version : DOC3.0
QoS Provisioned Mode : DOC1.1
Enable DOCSIS2.0 Mode : Y
Modem Status : {Modem= w-online, Security=disabled}
Capabilities : {Frag=N, Concat=N, PHS=Y}
Security Capabilities : {Priv=, EAE=Y, Key_len=}
L2VPN Capabilities : {L2VPN=N, eSAFE=N}
Sid/Said Limit : {Max US Sids=8, Max DS Saids=24}
Optional Filtering Support : {802.1P=N, 802.1Q=N, DUT=N}
Transmit Equalizer Support : {Taps/Symbol= 1, Num of Taps= 24}
Number of CPE IPs : 0(Max CPE IPs = 16)
CFG Max-CPE : 4
Flaps : 0()
Errors : 0 CRCs, 0 HCSes
Stn Mtn Failures : 0 aborts, 0 exhausted
Total US Flows : 2(2 active)
Total DS Flows : 1(1 active)
Total US Data : 6 packets, 1557 bytes
Total US Throughput : 0 bits/sec, 0 packets/sec
Total DS Data : 0 packets, 0 bytes
Total DS Throughput : 0 bits/sec, 0 packets/sec
LB group ID assigned (index) : N/A (N/A)
LB group ID in config file (index) : N/A (N/A)
LB policy ID : 0
LB policy ID in config file : 0
LB priority : 0
Tag :
Required DS Attribute Mask : 0x0
Forbidden DS Attribute Mask : 0x0
Required US Attribute Mask : 0x0
Forbidden US Attribute Mask : 0x0
Service Type ID :
Service Type ID in config file :
Active Classifiers : 0 (Max = NO LIMIT)
CM Upstream Filter Group : 0
CM Downstream Filter Group : 0
CPE Upstream Filter Group : 0
CPE Downstream Filter Group : 0
Note An asterisk (*) in the Phy Operating Mode row indicates the type of PHY-layer modulation that the CM
(operating in the MTC mode) is using: tdma or atdma.
Example of the show cable modem Command Output on the Cisco uBR7225VXR and Cisco uBR7246VXR Routers
The following example shows the sample output for the cm-status option in
Cisco IOS Release 12.2(33)SCD on a Cisco uBR7246VXR router:
Router# show cable modem cm-status
I/F MAC Address Event TID Count Error Dups Time
C5/0 001e.6bfb.29a6 Seq out-of-range 1 1 0 1 Jan 18 09:00:19
C7/0 001c.ea2b.79b2 MDD timeout 0 0 1 0 Jan 11 11:29:22
QAM failure 0 0 1 0 Jan 11 11:29:02
MDD recovery 0 0 1 0 Jan 11 11:30:20
QAM recovery 0 0 1 0 Jan 11 11:30:13
C7/0 001c.ea2b.78b0 MDD timeout 0 0 1 0 Jan 11 11:29:16
QAM failure 0 0 1 0 Jan 11 11:28:53
MDD recovery 0 0 1 0 Jan 11 11:29:59
QAM recovery 0 0 1 0 Jan 11 11:29:46
The following example shows the sample output of the queue option for a particular CM in
Cisco IOS Release 12.2(33)SCD:
Router# show cable modem 40.3.192.2 queue
CIR Queues:
Example of the show cable modem Command Output for Partial Service Mode
The following example shows the sample output of the show cable modem command that displays the
cable modems that are in upstream (indicated by “p” under I/F) and downstream partial service mode
(indicated by “p-online” under MAC State):
Router# show cable modem
D
MAC Address IP Address I/F MAC Prim RxPwr Timing Num I
State Sid (dBmv) Offset CPE P
0016.9252.9ac0 2.99.81.4 C7/0/0/U0 online(pt) 1 0.00 1332 0 N
000f.2172.229d 2.99.81.36 C7/0/0/U3 online(pt) 2 0.50 1778 0 N
001e.6bfb.33a0 2.99.81.14 C7/0/0/p p-online(pt) 3 -0.50 1424 0 N
Field Description
MAC Address MAC address for the CM.
IP Address IP address that the DHCP server has assigned to the CM.
IPv6 Address IPv6 address that the DHCP server has assigned to the CM.
Dual IP Support of dual IP for both IPv4 and IPv6 addressing.
I/F, Interface Cable interface line card providing the upstream for this CM.
sysDescr Vendor and model of the cable modem, as reported by the cable modem. This
field displays a value only when the cable modem remote-query command
is configured.
Upstream Power Upstream and Downstream Power fields are displayed only if the
CM remote-query feature has been enabled using the cable modem
Downstream Power
remote-query command. Upstream Power displays the CM transmit level in
dBmV, and Downstream Power displays the dBmV level received at the CM,
as measured by the CMTS.
MAC State Current state of the MAC layer.
Prim SID Primary SID assigned to this CM.
Host Interface Host interface name.
Primary Wideband Bonding group ID of the wideband interface assigned to the CM.
Channel ID
MD-DS-SG MAC Domain Downstream Service Group, the downstream channels of a
single MAC domain that reach the cable modem.
DSID Downstream Service Identifier.
Primary Downstream Primary downstream channel assigned to the CM.
Wideband Capable Cable modem is wideband-capable or not.
Multi-Transmit Cable modem is in MTC mode or not.
Channel Mode
Field Description
Upstream SNR Upstream signal-to-noise ratio (SNR) for a particular cable modem (CM), in
decibels (dB).
RxPwr, Received Average power in dBmV for the upstream channel symbol rate for the CM.
Power With default settings, 0 dBmV is considered optimal, but a range of -1 to 1
dBmV is allowable. When CMs exceed this range, older Cisco IOS releases
supported a drop to as low as -2 dBmV. Recent Cisco IOS releases support a
drop to as low as -4 dBmV.
This field supports a resolution of 0.25 dBmV, but the dB resolution level for
CMs and for the Cisco CMTS are slightly higher—approximately 1.0 and 1.4 dB.
Note An asterisk (*) in the RxPwr column indicates that a power
adjustment has been made for that CM. An exclamation point (!)
indicates that the CM has reached its maximum power transmit level
and cannot increase its power level further.
Timing Offset and Timing offset for the CM, in ticks, as recognized on the CMTS. (A tick, as
Initial Timing Offset used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it.
Note An exclamation point (!) in the Timing Offset column indicates that
the CM has exceeded the maximum delay and timing offset specified
by the cable map-advance command.
Note The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query
command, because the latter value is the offset as recognized on the
CM (which will include any internal delay between when the CM
software begins the transmission and when the bits actually appear on
the local cable interface).
Reported Transmit Reported Transmit Power level by the cable modem for each upstream
Power (dBmV) channel. This applies only to the cable modems operating in the MTC mode.
Peak Transmit Power This is the maximum transmit power level that the cable modem in the MTC
(dBmV) mode could transmit at for the upstream channel.
Minimum Transmit This is the minimum transmit power level that the cable modem in the MTC
Power (dBmV) mode could transmit at for the upstream channel.
Rng Timing Adj A Cisco CMTS router tracking variables to see relative timing offset
Moving Avg(0.381 adjustments.
ns):
Rng Timing Adj Lt
Moving Avg:
Rng Timing Adj
Minimum:
Rng Timing Adj
Maximum:
Pre-EQ Good : Equalizer statistics counter.
Pre-EQ Scaled :
Pre-EQ Impulse:
Pre-EQ Direct Loads
Field Description
Good Codewords rx Good code words for a particular upstream channel.
Corrected Codewords Correctable code words for a particular upstream channel.
rx
Uncorrectable Uncorrectable code words for a particular upstream channel.
Codewords rx
sysDescr Identifies the vendor and model of the cable modem, as reported by the cable
modem. This field displays a value only when the cable modem remote-query.
Num CPEs, CFG Indicates the number of CPE devices for which the CM is providing services.
Max-CPE
Number of CPE IPs Indicates the maximum number of IP addresses assigned to CPE devices
behind this CM, as configured by the cable max-hosts command.
Ver, MAC Version Displays the maximum supported version of DOCSIS that the CM supports
(DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).
QoS Prov, QoS Displays the version of DOCSIS that the CM currently is provisioned for
Provisioned Mode (DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).
Enable DOCSIS 2.0 Indicates whether the CM is capable of DOCSIS 2.0 (ATDMA) operation, as
Mode determined by the presence and value of the Enable 2.0 Mode (TLV39) field
in the CM’s Registration Request message or in the DOCSIS configuration
file. The valid values are:
• Y = TLV 39 was set to 1, indicating that the CM has enabled DOCSIS 2.0
mode. The CM could still be registered for DOCSIS 1.1 operations,
however, on DOCSIS 1.X interfaces.
• N = Either the TLV 39 field was not present in the CM’s Registration
Request message, indicating that the CM is not capable of DOCSIS 2.0
operations, or the TLV 39 field was set to 0 in the DOCSIS configuration
file, preventing the CM from using the DOCSIS 2.0 mode.
Phy Operating Mode Indicates the type of PHY-layer modulation that the CM is using: tdma or
atdma. Also indicates the TDMA/ATDMA/SCDA mode that the cable
modem is operating on a specific channel.
Modem Status Indicates the overall modem state and the security state of the primary SID.
BPI Enbld, BPI Indicates whether or not Baseline Privacy Interface (BPI) or BPI Plus (BPI+)
encryption is enabled for the CM.
DIP Dual IP flag. Identifies whether or not (“Y” or “N”) the CM or CPE supports
both IPv4 and IPv6 addressing.
Capabilities Indicates what the CM reported as its capabilities in its Registration Request
message: DOCSIS fragmentation, concatenation, packet header suppression
(PHS), and BPI encryption.
Security Capabilities Indicates the privacy mode used by the CM (BPI or BPI+), early
authentication and encryption (EAE) support, and the Key Length.
Optional Filtering Indicates whether 802.1P or 802.1Q packet filtering is enabled for this CM.
Support
Transmit Equalizer Number of taps being used for transmit equalization.
Support
Field Description
Flaps Number of flaps reported by this CM, with the date and time of the last flap
within the parentheses.
Errors Number of frame CRC and HCS errors reported for this CM.
Stn Mtn Failures Number of station maintenance (cable keepalive) messages that the CMTS
sent to this CM but did not receive any reply.
Total US Flows Total number of upstream service flows, with the number of active service
flows within the parentheses.
Total DS Flows Total number of downstream service flows, with the number of active service
flows within the parentheses.
Total US Data Total data this CM has transmitted on the upstream, in packets and bytes.
Total US Throughput Calculated throughput for this CM on the upstream, if available.
Total DS Data Total data this CM has received on the downstream, in packets and bytes.
Total DS Throughput Calculated throughput for this CM on the downstream, if available.
Active Classifiers Current number of active classifiers for this CM, with the maximum number
of allowable classifiers for this CM within the parentheses.
CM Required Attribute Indicates the current required attribute-mask value.
CM Forbidden Indicates the current forbidden attribute-mask value.
Attribute
DSA/DSX messages Indicates whether dynamic service changes (DSX) from the cable modem are
permitted (permit all) or disallowed (reject all).
Voice Enabled Indicates whether the CM is voice-enabled.
Number of Multicast Indicates the total number of supported multicast DSIDs.
DSIDs Support
FCType10 Forwarding Indicates FCType10 Forwarding Support.
Support
Dynamic Secret Dynamically-generated shared secret (a 16-byte hexadecimal value) that was
used in the cable modem’s previous registration cycle. If the cable modem is
currently offline, this field shows all zeroes.
Note This field displays a value only when the cable dynamic-secret
command has been used on the CMTS interface.
Spoof attempt Displays the status of the dynamic shared secret checks for this CM. If the
• Dynamic secret check failed = The DOCSIS configuration file did not
contain the proper shared secret, indicating a possible theft-of-service
attempt.
• Did not TFTP config file = The CM failed to download a DOCSIS
configuration file from the TFTP server.
Note This field displays a value only when the cable dynamic-secret
command has been used on the CMTS interface.
Field Description
Total Time Online Amount of time in days, hours, and minutes that this CM has been
continuously online since it last registered with the CMTS. This field begins
incrementing whenever the CM enters one of the online(x) MAC states, and
is reset to 0 whenever the CM enters any other MAC state.
Event Event type.
TID Transaction identifier.
Count Number of valid messages received.
Dups Number of duplicate messages received.
Time Time when last valid event was received.
Len/Limit Pkts Queue length and limit in packets.
Deqs Pkts Dequeue packets.
Drops Pkts Dropped packets.
CIR Kbps Committed information rate.
MIR/PR Kbps Maximum information and peak rate.
Forwint Forwarding interface.
SFID Service flow identifier.
BE Queues Best effort queues.
CIR Queues Committed information rate queues.
Low Latency Queues Low latency queues.
Table 67 shows the possible values for the MAC state field:
The following symbols appended to the modem state indicate a special condition:
An exclamation mark (!) indicates that the cable dynamic-secret command is used with either the mark
or reject keyword and the cable modem has failed the dynamic secret authentication check.
An ampersand (&) indicates that the cable modem has registered using a self-signed certificate. This is
inherently not secure and can be avoided by negating the cable privacy
accept-self-signed-certificate command.
A hash sign (#) indicates that the cable modem is using an unknown configuration file. To solve this
problem, use the cable dynamic-secret command with the reject keyword. This will reject
registration for CMs with DOCSIS configuration files.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Command Description
show cable modem cpe Displays the CPE devices accessing the cable interface through a
particular CM.
show cable modem Updates the cable-specific DNS cache and display the domain
domain-name name for specified CMs and CPE behind a CM on a Cisco CMTS
router.
show cable modem errors Displays error statistics for one or more CMs.
show cable modem flap Displays flap list statistics for one or more CMs.
show cable modem ipv6 Displays IPv6 information for specified CMs and CPE behind a
CM on a Cisco CMTS router.
show cable modem mac Displays MAC layer information for one or more CMs.
show cable modem maintenance Displays station maintenance (SM) error statistics for one or more
CMs.
show cable modem offline Displays a list of the CMs that are marked as offline with the
Cisco CMTS.
show cable modem partial-mode Displays information about the cable modems that are in upstream
and downstream partial service mode.
show cable modem phy Displays the DOCSIS PHY layer information for one or more
CMs.
show cable modem qos Displays quality of service (QoS) and service flow information for
a particular CM.
show cable modem registered Displays a list of the CMs that are marked as registered with the
Cisco CMTS.
show cable modem Displays information collected by the remote-query feature.
remote-query
show cable modem summary Displays a summary of CMs on one or more cable interfaces.
show cable modem unregistered Displays a list of the CMs that are marked as unregistered with the
Cisco CMTS.
show cable modem vendor Displays the vendor name or Organizational Unique Identifier
(OUI) for the CMs on each cable interface.
show cable modulation-profile Displays modulation profile group information.
show interface cable modem Displays information about the CMs connected to a particular
cable interface.
show interface cable sid Displays cable interface information.
show cable modem [ip-address | cable slot/port [upstream port] | mac-address] access-group
Syntax Description ip-address (Optional) Displays access-group information for the CM with the
specified IP address. (Cisco uBR7100 series and Cisco uBR7200
series routers only.)
mac-address (Optional) Displays access-group information for the CM with the
specified MAC address. (Cisco uBR7100 series and Cisco uBR7200
series routers only.)
cable slot/port (Optional) Identifies the cable interface and downstream port on the
Cisco uBR7100 series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On
the Cisco uBR7200 series router, slot can range from 3 to 6, and port
can be 0 or 1, depending on the cable interface.
cable slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
upstream port (Optional) Displays information for all CMs using this specific
upstream. You can specify this option only when displaying
information for a cable interface. The valid range for port begins with
0 and ends with a value that depends on the number of upstream ports
on the cable interface line card.
Usage Guidelines This command displays information only for CMs. To display information for both CMs and their
associated hosts and other customer premises equipment (CPE) devices, use the show cable device
access-group command. To display information only for hosts, use the show cable host access-group
command.
If an SNMP manager is requesting information about CM or CPE devices at the same time that this
command is given, the command displays the following error message:
No information is available, please try later.
Wait until the SNMP retrieval is done and retry the CLI command.
Note Also see the information about this command’s behavior in a Hot Standby Connection-to-Connection
Protocol (HCCP) configuration, see the “Operation with Hot Standby Connection-to-Connection
Protocol (HCCP) Configuration” section on page 1194.
Examples The following example shows sample output for the show cable modem access-group command on a
Cisco uBR7200 series router for a particular CM:
Router# show cable modem 0010.7bb3.fcd1 access-group
Router#
Note The upstream and downstream power fields will be displayed only if the CM remote-query feature has
been enabled using the cable modem remote-query command.
The following example shows sample output for the show cable modem access-group command for a
particular cable interface on a Cisco uBR10012 router:
Router# show cable modem c8/1/0 access-group
Router#
Table 0-68 describes the fields that are shown in the show cable modem access-group display:
Table 0-68 Descriptions for the show cable modem access-group Fields
Field Description
MAC Address The MAC address for the CM.
IP Address The IP address that the DHCP server has assigned to the CM.
Access-group Displays the access group name or number in use (if any) for this CM.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description ip-address (Optional) IPv4 or IPv6 address of a CM that is displayed. If you specify the
IP address for a CPE device behind a CM, information for that CM is
displayed.
mac-address (Optional) MAC address of a CM that is displayed. You can also specify the
MAC address for a CPE device behind a CM, and information for that CM
will be displayed.
auth-profile (Optional) Displays the multicast authorization profile, and profile group
information.
Usage Guidelines Use this command to display the multicast authorization profile, and the profile group information.
Examples The following sample output of the show cable modem auth-profile command shows the multicast
authorization profile and profile group display for a particular ip-address or mac-address.
Router# show cable modem 30.17.2.23 auth-profile
Router#
Command Description
show cable multicast Displays the entire multicast downstream service identifier (DSID) database
dsid content.
show cable multicast Displays the configuration information for MQoS (Group-Config,
qos Group-QoS-Config, Group-Encryption-Config).
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] calls
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] calls
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a
CM, information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be
displayed. If you specify the MAC address for a CPE device behind
a CM, information for that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable
interface and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation
for your router chassis and cable interface line card for supported slot
and port numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable
interface on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified
upstream port. You can specify this option only when displaying
information for a cable interface. The valid range for port begins with
0 and ends with a value that depends on the number of upstream ports
supported by the cable interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the
cable device to be displayed. This option is only available if the show
cable modem domain-name command has been run for the first time
to update the cable DNS cache on the CMTS router.
Usage Guidelines Using the keyword options, you can display IPv6 information by IP address (IPv4 or IPv6) of a particular
CM, for all CMs associated with a specified cable interface, by MAC address of a CM, or by domain
name of a CM.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
This command supports PacketCable and PacketCable MultiMedia (PCMM) information. Additional
information for voice call support with PacketCable and PacketCable MultiMedia (PCMM) is available
in the feature document PacketCable and PacketCable Multimedia for the Cisco CMTS available on
Cisco.com:
Examples The following example shows sample output for the default calls option for a particular CM:
Router# show cable modem calls
Command Description
show cable modem Displays information about the classifiers for a particular CM.
classifiers
show cable modem Displays information about the upstream carrier-to-noise ratio (CNR) for a
cnr particular cable modem.
show cable modem Displays connectivity statistics for one or more CMs.
connectivity
show cable modem Displays error statistics for one or more CMs.
errors
show cable modem Displays flap list statistics for one or more cable modems.
flap
show cable modem Displays station maintenance (SM) error statistics for one or more cable
maintenance modems.
show cable modem Displays information collected by the remote-query feature.
remote-query
show cable Displays modulation profile group information.
modulation-profile
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
Syntax Description ip-address Specifies the IPv4 or IPv6 address of a specific CM to be displayed. If you
specify the IP address for a CPE device behind a CM, classifier information
for that CM is displayed.
mac-address Displays classifier information for the CM with the specified MAC address.
If you specify the MAC address for a CPE device behind a CM, information
for that CM is displayed.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
cache (Optional) Displays the classifiers in the cache maintained for each CM.
(This cache is based on IP header field values and speeds up classifier
lookups and reduces per-packet processing overhead.)
verbose (Optional) Displays detailed information for the CM classifiers.
Usage Guidelines This command displays classifier information for a particular CM, identified either by its IP address,
MAC address, or domain name.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Note For information about this command’s behavior in a Hot Standby Connection-to-Connection Protocol
(HCCP) configuration, see the “Operation with Hot Standby Connection-to-Connection Protocol
(HCCP) Configuration” section of the show cable modem command.
Examples The following example shows sample output for the default classifiers option for a particular CM:
Router# show cable modem 10.4.0.81 classifiers
Router#
Table 69 describes the fields that are shown in the show cable modem classifiers display:
Field Description
CfrID Classifier ID for the classifier that is being displayed.
SFID Service flow ID (SFID) for this classifier.
CM MAC Address MAC address for the CM.
Direction Identifies whether this classifier applies to the downstream or the upstream
direction.
State Classifier activation state: active or inactive.
Priority Classifier rule priority value for this classifier.
Matches Number of packets that have been matched to this service flow.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Command Description
show cable modem Displays error statistics for one or more CMs.
errors
show cable modem Displays flap list statistics for one or more cable modems.
flap
show cable modem Displays station maintenance (SM) error statistics for one or more cable
maintenance modems.
show cable modem Displays information collected by the remote-query feature.
remote-query
show cable Displays modulation profile group information.
modulation-profile
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
Syntax Description ip-address IPv4 or IPv6 address of a specific CM to be displayed. If you specify the IP
address for a CPE device behind a CM, classifier information for that CM
is displayed.
mac-address Classifier information for the CM with the specified MAC address. If you
specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
Command History This table includes the following release-specific history entries:
• BC Release
• CX Release
• SC Release
BC Release Modification
12.2(4)BC2 The command was changed to its current form of show cable modem cnr.
12.2(8)BC2 Support was added for the Cisco uBR-LCP2-MC16S cable interface line
card on the Cisco uBR10012 router.
12.2(11)BC3 Support was added for the Cisco uBR10-MC5X20S cable interface line
cards on the Cisco uBR10012 router.
12.2(15)BC1 If a cable modem is offline, its CNR value is now shown as “-----”.
12.2(15)BC2 Support was added for the Cisco uBR-MC16U/X and
Cisco uBR-MC5X20U cable interface line cards.
12.3(17a)BC2 Support was added for the Cisco uBR-MC5X20H cable interface line card.
CX Release Modification
12.1(7)CX1 This command was introduced (in the form of show cable modem snr) for
Cisco uBR7200 series routers using the Cisco uBR-MC16S cable interface
line card.
12.2(15)CX Support was added for the Cisco uBR-MC28U/X cable interface line cards
on the Cisco uBR7246VXR router.
SC Release Modification
12.2(33)SCA This command was integrated into Cisco IOS Release 12.2(33)SCA, with
the following changes:
• Support for the Cisco uBR7225VXR router was added.
• Support for specifying the IPv6 address of a CM or CPE device was
added.
• The name keyword option was added for specifying the fully-qualified
domain name of a CM.
• The following new initialization states were added to show
initialization of CMs and CPEs supporting IPv6:
– init6(s)—CMTS router has seen SOLICIT message.
– init6(a)—CMTS router has seen ADVERTISE message.
– init6(r)—CMTS router has seen REQUEST message.
– init6(i)—CMTS router has seen REPLY message.
– init6(o)—CMTS router has seen version 6 TFTP request.
– init6(t)—CMTS router has seen version 6 TOD request.
12.2(33)SCC The output of this command was modified to show the CNR and SNR
information for multiple upstream connections providing service to a single
CM.
Usage Guidelines This command displays information on the current CNR value for cable modems that are using interfaces
on the following cable line cards:
• Cisco uBR-MC16S
• Cisco uBR-MC16U/X
• Cisco uBR-MC28U/X
• Cisco uBR10-MC5X20S/U/H
• Cisco uBR-E-28U
• Cisco uBR-E-16U
For cable modems on all other interfaces, this command displays information about the current SNR
value of the modem.
In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
the ping ip-address command, and then the show cable modem ip-address cnr command will show the
cable modem. You can also display any particular cable modem by using the show cable modem |
include ip-address command.
In addition, when HCCP redundancy has been configured, the Cisco IOS software automatically
synchronizes the secondary, backup cards whenever the configuration is changed. The cards can also be
synchronized manually, using the hccp resync command. When a SYNC event command is occurring,
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modem cnr command for a CM:
Router# show cable modem 10.20.114.34 cnr
Router#
The following example shows the output of the show cable modem cnr command after an HCCP
switchover. The CNR value is missing until traffic is sent to the cable modem (in this case using the ping
command).
Router# show cable modem 10.10.10.46 cnr
The following example shows the output of the show cable modem cnr command for all upstream ports
providing service to a specified cable modem in Cisco IOS Release 12.2(33)SCC:
Router# show cable modem 0014.f8c1.fd1a cnr
MAC Address IP Address I/F MAC SID snr/cnr
State (dB)
0014.f8c1.fd1a 10.10.4.1 C5/0/1/U0 online 1 33
001e.6bfb.119a 9.9.9.2 C5/0/1/U1 online 2 33
001e.6bfb.0f9e 9.9.9.3 C5/0/1/U2 online 3 33
0019.474a.d4c4 9.9.9.4 C5/0/1/U3 online 4 33
Field Description
MAC Address The MAC address for the CM.
IP Address The IP address that the DHCP server has assigned to the CM.
I/F The cable interface line card providing the upstream for this CM.
MAC State The current state of the MAC layer (see Table 67).
Prim SID The primary SID assigned to this CM.
In Cisco IOS Release 12.2(33)SCC, this field is renamed to SID and
represents multiple upstream connections with unique SIDs providing service
to a single CM.
snr/cnr The current upstream carrier-to-noise ratio (CNR) or signal-to-noise ratio
(SNR) for this particular CM, in decibels (dB). In Cisco IOS Release
12.2(15)BC1 and later releases, this field shows “-----” for offline cable
modems.
Note You can also use the show controllers cable command to display the
signal-to-noise ration (SNR) or CNR for a cable interface line card,
but this value is only an estimate because it uses a random sampling
of modems to determine the average for the card at any particular
time. The CNR value shown by the show controllers cable command
can therefore appear to fluctuate compared to the individual values
shown by the show cable modem cnr command.
Table 67 shows the possible values for the MAC state field:
1
Table 71 MAC State Field Descriptions
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
connectivity
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] connectivity
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information
for that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using this specific upstream.
You can specify this option only when displaying information for a cable
interface. The valid range for port begins with 0 and ends with a value that
depends on the number of upstream ports on the cable interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
Usage Guidelines This command displays connectivity information for all CMs, for all CMs attached to a specific CMTS
cable interface, or for a particular CM, as identified by its IP address or MAC address.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Note The show cable modem connectivity command replaces the connectivity option for the show interface
cable sid command, because the connectivity statistics are better managed on a per-modem basis than
on a per-SID basis.
Examples The following example shows sample output for the show cable modem connectivity command for all
online CMs:
Router# show cable modem connectivity
The following example shows sample output for the show cable modem connectivity command for all
online CMs for a particular cable interface:
Router# show cable modem c8/1/0 connectivity
The following example shows sample output for the show cable modem connectivity command for a
particular CM:
Router# show cable modem 0010.7bb3.fcd1 connectivity
Table 72 describes the information shown in the show cable modem connectivity displays:
Field Description
Prim SID The primary SID assigned to this CM.
1st time online First time at which the modem with this SID connected.
Times online Number of times the modem with this SID connected.
% online Percentage of time the modem with this SID has been connected.
Online time The minimum, average, and maximum number of days, hours, and minutes
the modem with this SID has been connected.
Note A CM is considered online when it has completed the registration
process and has communicated with the DHCP, TFTP, and TOD
servers.
Offline time The minimum, average, and maximum number of days, hours, and minutes
the modem with this SID has been disconnected.
Note A CM is considered offline after it has missed 16 consecutive station
maintenance messages.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
counters
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] counters
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modems counters command for all
CMs:
Router# show cable modem counters
Router#
The following example shows sample output for the show cable modems counters command for all
CMs on a particular cable interface:
Router# show cable modem c8/1/0 counters
Router#
The following example shows sample output for the show cable modems counters command for a
particular CM, as identified by its MAC address:
Router# show cable modem 0010.7bb3.fcd1 counters
Router#
The following example shows sample output for the show cable modems counters command for a
particular CM, as identified by its IP address:
Router# show cable modem 23.1.1.10 counters
Router#
Table 73 describes the fields shown in the show cable modem counters displays:
Field Description
MAC Address MAC address for the CM.
US Packets Number of packets this CM has transmitted on the upstream.
US Bytes Number of bytes this CM has transmitted on the upstream.
DS Packets Number of packets this CM has received on the downstream.
DS Bytes Number of byte this CM has received on the downstream.
Syntax Description ip-address Displays the CPE devices for the CM with the specified IPv4 or IPv6
address.
mac-address Displays the CPE devices for the CM with the specified MAC address.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
Usage Guidelines This command lists the CPE devices that are accessing the cable network through a particular CM. You
can identify the CM either by its IP address or by its MAC address.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
ping ip-address command, and then the show cable modem ip-address command will show the cable
modem. You can also display any particular cable modem by using the show cable modem | include
ip-address command.
In addition, when HCCP redundancy has been configured, the Cisco IOS software automatically
synchronizes the secondary, backup cards whenever the configuration is changed. The cards can also be
synchronized manually, using the hccp resync command. When a SYNC event command is occurring,
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modem cpe command, listing the CPE
devices by their MAC and IP addresses:
Router# show cable modem 10.14.1.20 cpe
10.14.30.100 00b0.4a9b.bc8c
10.14.30.101 00b0.4a9b.bc8d
Command Description
show cable Displays modulation profile group information.
modulation-profile
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
show cable modem docsis device-class [summary [cable slot/subslot [cable slot/subslot]
[upstream port1 port2]]] [total]
Syntax Description summary (Optional) Displays a summary of DOCSIS device class information for
CMs on all or specified cable interfaces on the CMTS router.
cable slot/subslot (Optional) Specifies a single cable interface, or a range of cable interfaces
[cable slot/subslot] on a Cisco uBR7100 or Cisco uBR7200 series router, whose CMs you want
to display information about, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• subslot—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Specifies a single cable interface, or a range of cable interfaces
[cable slot/subslot/port] on a Cisco uBR10012 router, whose CMs you want to display information
about, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port1 port2 (Optional) Specifies a specific upstream port, or a range of upstream ports
on the specified cable interface(s), whose CMs you want to display
information about, where:
• port1—Specify only port1 if you want to display information about a
single upstream. When used with the port2 argument, specifies the
beginning of a range of upstream ports, and port1 must be a
lower-numbered port than port2.
• port2—Specifies the end of a range of upstream ports, and port2 must
be a higher-numbered port than port1.
total (Optional) Displays a total of DOCSIS device-class information for the CMs
connected to all interfaces, or to the specified cable interfaces.
Command Default The default form of the command (show cable modem docsis device-class without any options)
provides DOCSIS device class information for all CMs on the CMTS router.
Usage Guidelines This command displays a summary of DOCSIS device-class information for all CMs for a single cable
interface, or for a range of cable interfaces, and optionally specified upstreams on those cable interfaces.
Examples The following example shows typical output for the default form of the show cable modem docsis
device-class command on a Cisco uBR100012 router:
Router# show cable modem docsis device-class
MAC Address I/F MAC Prim Reg Device Class Reg
State Sid Ver -------------------- Priv
0030.80bc.22b9 C3/0/U0 online(pt) 1 1.0 CM BPI
0000.cadb.04b2 C3/0/U0 online(pt) 2 1.1 eCM eMTA BPI+
0000.cadb.0512 C3/0/U0 online(pt) 3 1.1 eCM eMTA eSTB BPI+
0003.e38f.f5c7 C3/0/U1 online(pt) 4 1.0 CM BPI
0000.cadb.0bae C3/0/U1 online(pt) 5 1.1 eCM ePS BPI+
0010.7b6b.77ed C3/0/U2 online 6 1.0 CM
0000.cadb.0356 C4/0/U0 online(pt) 1 1.1 eCM eMTA BPI+
0000.cadb.02a6 C4/0/U0 init(d) 2 n/a <unavailable>
0000.cadb.2f7a C4/0/U1 online(pt) 3 2.0 eCM eSTB BPI+
0000.cadb.2952 C4/0/U2 online(pt) 4 1.1 eCM eSTB ePS BPI+
0000.cadb.0236 C4/0/U2 init(d) 6 n/a <unavailable>
0003.e3a6.850d C4/0/U3 online(pt) 7 1.1 eCM eMTA ePS BPI+
0003.e3a6.85ad C4/0/U3 online(pt) 8 1.0 CM BPI
The following example shows sample output for the show cable modem docsis device-class command
for a particular cable interface, in chassis slot 3 and subslot 0:
Router# show cable modem cable3/0 docsis device-class
MAC Address I/F MAC Prim Reg Device Class Reg
State Sid Ver -------------------- Priv
0030.80bc.22b9 C3/0/U0 online(pt) 1 1.0 CM BPI
0000.cadb.04b2 C3/0/U0 online(pt) 2 1.1 eCM eMTA BPI+
0000.cadb.0512 C3/0/U0 online(pt) 3 1.1 eCM eMTA eSTB BPI+
0003.e38f.f5c7 C3/0/U1 online(pt) 4 1.0 CM BPI
0000.cadb.0bae C3/0/U1 online(pt) 5 1.1 eCM ePS BPI+
0010.7b6b.77ed C3/0/U2 online 6 1.0 CM
Field Description
MAC Address The MAC address of the CM.
I/F The cable interface line card providing the upstream for this CM.
MAC State The current state of the MAC layer.
Prim Sid The primary SID assigned to this CM.
Reg Ver Displays the maximum supported version of DOCSIS that the CM supports. The
possible values are: DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0, and DOCSIS 3.0.
Shows “n/a” if the modem is not online.
Device Class Displays the device-class information for the PacketCable device. The modem
can report its device-class type during registration. The possible values are:
• CM or eCM—A standalone cable modem or embedded CM.
• ePS—Embedded Portal Services
• eMTA—Embedded Multimedia Terminal Adapter
• eSTB—Embedded Set Top Box
• unavailable—The CM has not reported its device class.
Reg Priv Indicates whether Baseline Privacy Interface (BPI) or BPI Plus (BPI+)
encryption is enabled for the CM.
The following example shows sample output for the show cable modem docsis device-class summary
form of the command on a Cisco CMTS router:
Router# show cable modem docsis device-class summary
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Cable4/0/U0 2 1 0 1 1 0 0
Cable4/0/U1 1 0 0 1 0 1 0
Cable4/0/U2 2 1 0 1 0 1 1
Cable4/0/U3 2 0 1 1 1 0 1
The following example shows sample output for the show cable modem docsis device-class summary
command with the total option on a Cisco CMTS router:
Router# show cable modem docsis device-class summary total
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Cable4/0/U0 2 1 0 1 1 0 0
Cable4/0/U1 1 0 0 1 0 1 0
Cable4/0/U2 2 1 0 1 0 1 1
Cable4/0/U3 2 0 1 1 1 0 1
Total: 13 2 4 7 4 3 3
The following example shows sample output for the show cable modem docsis device-class summary
total command for all enabled upstreams on a specific cable interface line card on a Cisco CMTS router:
Router# show cable modem docsis device-class summary cable 3/0 total
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Total: 6 0 3 3 2 1 1
The following example shows sample output for the show cable modem docsis device-class summary
total command for a range of interfaces on a Cisco CMTS router:
Router# show cable modem docsis device-class summary cable 3/0 cable 4/0 total
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Cable4/0/U0 2 1 0 1 1 0 0
Cable4/0/U1 1 0 0 1 0 1 0
Cable4/0/U2 2 1 0 1 0 1 1
Cable4/0/U3 2 0 1 1 1 0 1
Total: 13 2 4 7 4 3 3
The following example shows sample output for the show cable modem docsis device-class summary
total command for a range of interfaces and upstreams on a CMTS router:
Router# show cable modem docsis device-class summary cable 3/0 cable 4/0 upstream 0 2
total
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Cable4/0/U0 2 1 0 1 1 0 0
Cable4/0/U1 1 0 0 1 0 1 0
Cable4/0/U2 2 1 0 1 0 1 1
Total: 11 2 3 6 3 3 2
The following example shows sample output for the show cable modem docsis device-class summary
total command for a range of upstreams on an interface:
Router# show cable modem docsis device-class summary cable3/0 upstream 0 1 total
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Total: 5 0 2 3 2 1 1
The following example shows sample output for the show cable modem docsis device-class summary
command for all enabled upstreams on a specific cable interface line card:
Router# show cable modem cable3/0 docsis device-class summary
DOCSIS Device Class
----------------------------
Interface Online unrep CM eCM eMTA eSTB ePS
Cable3/0/U0 3 0 1 2 2 1 0
Cable3/0/U1 2 0 1 1 0 0 1
Cable3/0/U2 1 0 1 0 0 0 0
Total: 6 0 3 3 2 1 1
Field Description
Interface Name of the cable interface and associated upstreams on the Cisco CMTS router.
Online Total number of CMs currently online on this cable interface.
unrep Total number of CMs on this interface for which the device-class information is
unreported or unavailable.
CM Total number of CMs on this interface that have a reported device class as a
standalone cable modem.
eCM Total number of CMs on this interface that have reported the device class as an
embedded cable modem.
eMTA Total number of CMs on this interface that have reported the device class as an
embedded multimedia terminal adapter.
eSTB Total number of CMs on this interface that have reported the device class as an
embedded set-top box.
ePS Total number of CMs on this interface that have reported the device class as
embedded portal services.
Total The total number of all CMs reported online and for a given DOCSIS device class
across all cable interfaces on the Cisco CMTS router.
show cable modem docsis version [summary [cable slot/subslot [cable slot/subslot] [upstream
port1 port2]]] [total]
show cable modem docsis version [summary [cable slot/subslot/port [cable slot/subslot/port]
[upstream port1 port2]]] [total]
Syntax Description summary (Optional) Displays a summary of DOCSIS device class information for
CMs on all or specified cable interfaces on the CMTS router.
cable slot/subslot (Optional) Specifies a single cable interface, or a range of cable interfaces
[cable slot/subslot] on a Cisco uBR7100 or Cisco uBR7200 series router, where:
• slot—Slot where the line card resides:
– Cisco uBR7100 series router: The valid value is 1.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
• port—Downstream port number:
– Cisco uBR7100 series router: The valid value is 0.
– Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid
value is 0 or 1.
cable slot/subslot/port (Optional) Specifies a single cable interface or a range of cable interfaces on
[cable slot/subslot/port] a Cisco uBR10012 router, where:
• slot—Chassis slot number of the cable interface line card. Valid slots are
5 to 8.
• subslot—Secondary slot number of the cable interface line card. Valid
subslots are 0 or 1.
• port—Downstream port number. Valid ports are 0 to 4, depending on the
cable interface line card.
upstream port1 port2 (Optional) Specifies a specific upstream port, or a range of upstream ports
on the specified cable interface(s), whose cable modems you want to display
information about, where:
• port1—Specify only port1 if you want to display information about a
single upstream. When used with the port2 argument, specifies the
beginning of a range of upstream ports, and port1 must be a
lower-numbered port than port2.
• port2—Specifies the end of a range of upstream ports, and port2 must
be a higher-numbered port than port1.
total (Optional) Displays a total of DOCSIS device-class information for the CMs
connected to all interfaces, or to the specified cable interfaces.
Command Default The default form of the command (show cable modem docsis version without any options) provides
DOCSIS version information for all CMs on the CMTS router.
Usage Guidelines This command displays a summary of DOCSIS version information for all CMs for a single cable
interface or upstream, or for a range of cable interfaces or upstreams.
The following example shows sample output for the show cable modem docsis version command for a
particular cable interface on a Cisco uBR10012 router:
Router# show cable modem cable 5/1/0 docsis version
MAC Address I/F MAC Prim Reg QoS US Phy DS Chl
State Sid Ver Prov Mode Mode
0018.6852.800a C5/1/0/U3 w-online(pt) 166 2.0 1.1 tdma WB
0018.6852.7f92 C5/1/0/U1 w-online(pt) 167 2.0 1.1 tdma WB
0014.bfbe.3ea6 C5/1/0/U0 w-online(pt) 168 2.0 1.1 tdma WB
0018.6852.8022 C5/1/0/U2 w-online(pt) 169 2.0 1.1 tdma WB
0018.6852.7fa0 C5/1/0/U0 w-online(pt) 170 2.0 1.1 tdma WB
0018.6852.8016 C5/1/0/U3 w-online(pt) 171 2.0 1.1 tdma WB
0018.6852.8008 C5/1/0/U2 w-online(pt) 172 2.0 1.1 tdma WB
0018.6852.800e C5/1/0/U1 w-online(pt) 173 2.0 1.1 tdma WB
0018.6852.8000 C5/1/0/U1 w-online(pt) 174 2.0 1.1 tdma WB
Field Description
MAC Address The MAC address of the CM.
I/F The cable interface line card providing the upstream for this CM.
MAC State The current state of the MAC layer.
Prim Sid The primary SID assigned to this CM.
Reg Ver Displays the maximum supported version of DOCSIS that the CM supports. The
possible values are: 1.0, 1.1, 2.0, and 3.0. Shows “n/a” if the modem is not online.
QoS Prov Displays the version of DOCSIS that the CM currently is provisioned and
registered for. The possible values are: 1.0, 1.1, 2.0, and 3.0. Shows “n/a” if the
modem is not online.
US Phy Mode Displays the DOCSIS operating mode for the CM, with the following possible
values:
• tdma—DOCSIS 1.X, Time Division Multiple Access (TDMA)-only mode
• atdma—DOCSIS 2.0 Advanced Time Division Multiple Access (A-TDMA)
mode
• scdma—DOCSIS 2.0 Synchronous Code Division Multiple Access
(SCDMA) mode
Note This field is the same as that returned by the
docsIfCmtsCmStatusModulationType object in the DOCS-IF-MIB.
DS Chl Mode Displays the downstream channel mode for the CM, with the following possible
values:
• NB—Narrowband
• WB—Wideband
Beginning in Cisco IOS Release 12.2(33)SCD2, the output of the show cable modem docsis
version total command was modified to display the cable modems that are in partial service mode as
shown in the following example:
Router# show cable modem docsis version total
Table 77 describes the fields shown in the show cable modem docsis version total command display.
Field Description
Total Registered CMs Total number of cable modems currently online in a CMTS router.
Total Unregistered CMs Total number of cable modems that are either offline and not currently
communicating with the CMTS router, or that are attempting to come
online but are not yet registered.
Total DOCSIS x.y Total number of cable modems (in a/b/c format) for the specified
Operating/Capable/Registered DOCSIS version (x.y) that have the following status:
CMs: a/b/c
• Operating—Total number (a) of CMs currently operating in the
specified DOCSIS version.
• Capable—Total number (b) of CMs that can operate in the
specified DOCSIS version, but might not be operating in that
version.
• Registered—Total number (c) of CMs that are currently
registered in the specified DOCSIS version.
Total Vx.y US QoS operating Total number of cable modems whose upstreams are currently
CMs operating in a specified DOCSIS version (x.y) quality of service
(QoS).
Total Wide Band US operating Total number of cable modems with upstreams currently operating in
CMs wideband channel mode.
Total Wide Band US Total number of cable modems with upstreams currently operating in
partial-mode CMs partial wideband channel mode.
Total mode US Phy operating Total number of cable modems with upstreams currently operating in
CMs a particular wideband channel mode, where mode is:
• scdma—DOCSIS 2.0 Synchronous Code Division Multiple
Access (SCDMA) mode
• atdma—DOCSIS 2.0 Advanced Time Division Multiple Access
(A-TDMA) mode
• tdma—DOCSIS 1.X, Time Division Multiple Access (TDMA)
mode
Total Wide Band DS operating Total number of cable modems with downstreams operating in
CMs wideband channel mode.
Total Wide Band DS Total number of cable modems with downstreams operating in partial
partial-mode CMs wideband channel mode.
Total Narrow Band DS Total number of cable modems with downstreams operating in
operating CMs narrowband channel mode.
Beginning in Cisco IOS Release 12.2(33)SCD2, the output of the show cable modem docsis version
summary command was modified to display the cable modems that are in full or partial service mode
as shown in the following example:
The following example shows typical output for the show cable modem docsis version summary
command with the total option on a Cisco uBR10012 router:
Total: 15 0 14 1 0 15 0 0 0 0 15 11 4
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem docsis version
summary total command was modified as shown in the following example:
Router# show cable modem docsis version summary total
-----------------------------------------------------------------------------
Total: 15 v3.0: 0 v1.1: 15 WB : 0 WB: 11
v2.0: 14 v1.0: 0 scdm: 0 NB: 4
v1.1: 1 atdm: 0
v1.0: 0 tdma: 15
-----------------------------------------------------------------------------
Beginning in Cisco IOS Release 12.2(33)SCD2, the output of the show cable modem docsis version
summary total command was modified to display the cable modems that are in full or partial service
mode as shown in the following example:
-----------------------------------------------------------------------------
Total: 35 v3.0: 22 v1.1: 35 UB : 21 WB: 22
UP : 9 WP: 12
v2.0: 12 v1.0: 0 scdm: 0 NB: 13
v1.1: 1 atdm: 0
v1.0: 0 tdma: 14
-----------------------------------------------------------------------------
Examples: show cable modem docsis version summary cable total Command
The following example shows sample output for the show cable modem docsis version summary cable
total command for all enabled upstreams on a specific cable interface line card on a Cisco uBR10012
router:
Router# show cable modem docsis version summary cable 5/1/0 total
Total: 9 0 9 0 0 9 0 0 0 0 9 9 0
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem docsis version
summary cable total command was modified as shown in the following example:
Router# show cable modem docsis version summary cable 5/1/0 total
Cable Modem DOCSIS Version Summary
-----------------------------------------------------------------------------
Total: 9 v3.0: 0 v1.1: 9 WB : 0 WB: 9
v2.0: 9 v1.0: 0 scdm: 0 NB: 0
v1.1: 0 atdm: 0
v1.0: 0 tdma: 9
-----------------------------------------------------------------------------
The following example shows sample output for the show cable modem docsis version summary cable
total command for a range of interfaces on the Cisco uBR10012 router:
Router# show cable modem docsis version summary cable 5/1/0 cable 5/1/3 total
Cable Modem DOCSIS Version Summary
C5/1/0/U3 2 0 2 0 0 2 0 0 0 0 2 2 0
C5/1/1/U0 4 0 3 1 0 4 0 0 0 0 4 2 2
C5/1/3/U0 2 0 2 0 0 2 0 0 0 0 2 0 2
Total: 15 0 14 1 0 15 0 0 0 0 15 11 4
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem docsis version
summary cable total command for a range of interfaces was modified as shown in the following
example:
Router# show cable modem docsis version summary cable 5/1/0 cable 5/1/3 total
Cable Modem DOCSIS Version Summary
-----------------------------------------------------------------------------
Total: 15 v3.0: 0 v1.1: 15 WB : 0 WB: 11
v2.0: 14 v1.0: 0 scdm: 0 NB: 4
v1.1: 1 atdm: 0
v1.0: 0 tdma: 15
-----------------------------------------------------------------------------
The following example shows sample output for the show cable modem docsis version summary cable
upstream total command for a range of interfaces and upstreams on the Cisco uBR10012 router:
Router# show cable modem docsis version summary cable 5/1/0 cable 5/1/3 upstream 0 3 total
Cable Modem DOCSIS Version Summary
Total: 15 0 14 1 0 15 0 0 0 0 15 11 4
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem docsis version
summary cable upstream total command for a range of interfaces and upstreams was modified as
shown in the following example:
Router# show cable modem docsis version summary cable 5/1/0 cable 5/1/3 upstream 0 3 total
Cable Modem DOCSIS Version Summary
-----------------------------------------------------------------------------
Total: 15 v3.0: 0 v1.1: 15 WB : 0 WB: 11
v2.0: 14 v1.0: 0 scdm: 0 NB: 4
v1.1: 1 atdm: 0
v1.0: 0 tdma: 15
-----------------------------------------------------------------------------
The following example shows sample output for the show cable modem docsis version summary cable
upstream total command for a range of upstreams in an interface on the Cisco uBR10012 router:
Router# show cable modem docsis version summary cable 5/1/0 upstream 0 3 total
Cable Modem DOCSIS Version Summary
Total: 9 0 9 0 0 9 0 0 0 0 9 9 0
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem docsis version
summary cable upstream total command for a range of upstreams was modified as shown in the
following example:
Router# show cable modem docsis version summary cable 5/1/0 upstream 0 3 total
-----------------------------------------------------------------------------
Total: 9 v3.0: 0 v1.1: 9 WB : 0 WB: 9
v2.0: 9 v1.0: 0 scdm: 0 NB: 0
v1.1: 0 atdm: 0
v1.0: 0 tdma: 9
-----------------------------------------------------------------------------
The following example shows sample output for the show cable modem cable docsis version summary
command for all enabled upstreams on a specific cable interface line card on a Cisco uBR10012 router:
Router# show cable modem cable 8/0/1 docsis version summary
Cable Modem DOCSIS Version Summary
Beginning in Cisco IOS Release 12.3(23)BC7, the output for the show cable modem cable docsis
version summary command for a range of upstreams was modified as shown in the following example:
Router# show cable modem cable 8/0/1 docsis version summary
Cable Modem DOCSIS Version Summary
Field Description
Interface The cable interface line card providing the upstream for this cable
modem.
Online Total number of cable modems currently online on this cable
interface.
DOCSIS Registered Total number of cable modems registered on this cable interface with
the specified DOCSIS version (x.y) capabilities.
US QoS Total number of cable modems whose upstreams are currently
operating in a specified DOCSIS version (x.y) quality of service
(QoS).
US Phy Mode Total number of cable modems on this cable interface with upstreams
currently operating in a particular wideband channel mode, where:
• WB—Total number of upstreams on this cable interface operating
in any wideband channel mode.
• scdma—Total number of upstreams on this cable interface
operating in DOCSIS 2.0 Synchronous Code Division Multiple
Access (SCDMA) mode.
• atdma—Total number of upstreams on this cable interface
operating in DOCSIS 2.0 Advanced Time Division Multiple
Access (A-TDMA) mode.
• tdma—Total number of upstreams on this cable interface
operating in DOCSIS 1.X, Time Division Multiple Access
(TDMA) mode.
DS Mode Total number of cable modems on this cable interface whose
downstreams are operating in the following modes:
• WB—Total number of downstreams on this cable interface
operating in wideband channel mode.
• NB—Total number of downstreams on this cable interface
operating in narrowband channel mode.
DOCSIS Mode • UP—Total number of cable modems in upstream bonding partial
service mode (p).
• WB—Total number of cable modems in downstream bonding
fully-operational mode (w-online).
• WP—Total number of cable modems in downstream bonding
partial service mode (p-online).
• NB—Total number of cable modems in narrowband online mode
(online).
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
domain-name
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] domain-name
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines Use the show cable modem domain-name command without any options to initiate an update to the
cable-specific DNS cache on the CMTS router and to enable use of domain names in other CMTS router
cable modem commands that support a name option.
Note In Cisco IOS Release 12.2(33)SCA, although the show cable modem domain-name command accepts
an IPv4 address format for a CM, DNS for IPv4-managed cable devices is not supported.
Examples The following example shows sample output for all CMs and CPE behind a CM for the show cable
modem domain-name command, listing the devices by their MAC and IP addresses and displaying the
associated domain name:
Router# show cable modem domain-name
MAC Address IP Address Domain Name
0018.6835.27b3 10.3.37.76
0019.474a.c14a 2001:0DB8:3800:809:A896:1431:75EA:5EA1 cisco-test-cm1.cisco.com
0007.0e03.6851 10.3.37.36
0007.0e01.b085 10.3.37.34
0018.6835.27aa 2001:0DB8:3800:809:E97D:2986:9F37:FFE cisco-test-cm2.cisco.com
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] errors
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] errors
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information
for that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using this specific upstream.
You can specify this option only when displaying information for a cable
interface. The valid range for port begins with 0 and ends with a value that
depends on the number of upstream ports on the cable interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
Usage Guidelines This command displays packet header error information for all CMs, for all CMs attached to a specific
CMTS cable interface, or for a particular CM, as identified by its IP address or MAC address.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.2(15)BC1 and later releases, use the clear cable modem flap-counters
command to clear these counters.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modem errors command for all CMs
on a particular cable interface.
Router# show cable modem c8/1/0 errors
Router#
Table 79 describes the fields shown in the show cable modem errors displays:
Field Description
MAC Address The MAC address for the CM.
I/F The cable interface line card, including the upstream, for this CM.
CRC Number of times the CMTS upstream receiver flagged a packet with a cyclic
redundancy check (CRC) error from this CM. CRC errors usually indicate
downstream signal interruption or interference noise on a plant. Occasional
CRC errors can always be expected, but a high number of CRC errors could
indicate plant problems such as intermittent upstream problems, laster
clipping, common-path distortion, or impulsive noise or interference.
HCS Number of times the CMTS upstream receiver flagged a packet with a header
checksum (HCS) error from this CM. HCS errors could indicate the same sort
of plant problems as CRC errors.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] flap
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] flap
Syntax Description ip-address (Optional) IPv4 or IPv6 address of a specific CM to be displayed. If you
specify the IP address for a CPE device behind a CM, information for that
CM is displayed.
mac-address (Optional) MAC address of a specific CM to be displayed. If you specify the
MAC address for a CPE device behind a CM, information for that CM is
displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
flap mtc Displays aggregate data across all upstream channels for each flap detector
for CMs in MTC mode. Displays per channel flap information for a single
CM in MTC mode.
Usage Guidelines This command displays information about the flap-list activity for one or more cable modems. Unlike
the show cable flap-list command, the show cable modem flap command displays flap counters of a
cable modem irrespective of the plant condition.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
In addition, when HCCP redundancy has been configured, the Cisco IOS software automatically
synchronizes the secondary, backup cards whenever the configuration is changed. The cards can also be
synchronized manually, using the hccp resync command. When a SYNC event command is occurring,
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
For CMs in MTC mode, the show cable modem flap command will display aggregate data across all
upstream channels for each flap detector. However, for a single MTC CM, the show cable modem flap
command will display per channel flap information.
Note The output of the show cable modem flap command will remain unchanged for non-MTC mode CMs.
Examples The following example shows sample output for the show cable modem flap command for all cable
modems on a specific cable interface:
Router# show cable modem c8/1/0 flap
MAC Address I/F Ins Hit Miss CRC P-Adj Flap Time
0050.7366.1243 C8/1/0/U1 6 29770 79 0 0 11 Apr 28 13:08:06
0002.b970.0027 C8/1/0/U4 6 29737 109 0 1 14 Apr 28 13:08:44
0006.5314.858d C8/1/0/U4 2 29635 41 0 0 4 Apr 28 13:09:21
Router#
The following example shows sample output for the show cable modem flap command for a particular
CM:
Router# show cable modem 0010.7bb3.fcd1 flap
MAC Address I/F Ins Hit Miss CRC P-Adj Flap Time
0010.7bb3.fcd1 C5/0/U5 0 36278 92 0 369 372 Jun 1 13:05:23
The following example shows sample output of the show cable modem flap command for all cable
modems in the MTC mode on a specific cable interface:
Router# show cable modem c8/1/0 flap
MAC Address I/F Ins Hit Miss CRC P-Adj Flap Time
000e.5c44.d2f0 C5/0/0/U0 0 3040 0 0 0 0
0019.474a.d542 C5/0/0/U3 0 2930 214 0 0 1 May 27 05:21:26
001a.c3ff.d578 C5/0/0/UB 0 12195 60 0 0 4 May 25 10:01:03
The following example shows sample output of the show cable modem flap command for a particular
CM in the MTC mode:
Router# show cable modem 0010.7bb3.fcd1 flap
MAC Address I/F Ins Hit Miss CRC P-Adj Flap Time
001a.c3ff.d578 C5/0/0/U0 0 3048 15 0 0 1 May 25 10:01:03
0019.474a.d4c4 C5/0/0/U1 0 3049 15 0 0 1 May 25 10:01:03
0019.474a.d4be C5/0/0/U2 0 3049 15 0 0 1 May 25 10:01:03
001a.c3ff.d58a C5/0/0/U3 0 3049 15 0 0 1 May 25 10:01:03
Field Description
MAC Address The MAC address for the CM.
I/F The cable interface line card, including upstream, for this CM.
Ins The number of times the CM comes up and inserts itself into the network. It
can indicate intermittent downstream sync loss or DHCP or modem
registration problems.
Hit The number of times the CM responds to MAC layer keepalive messages.
(The minimum hit rate is once per 30 seconds. It can indicate intermittent
upstream, laser clipping, or common-path distortion.
Miss The number of times the CM misses the MAC layer keepalive message. An 8
percent miss rate is normal for the Cisco cable interface line cards. It can
indicate intermittent upstream, laser clipping, or common-path distortion.
CRC The number of cyclic redundancy check (CRC) errors from this CM. It can
indicate intermittent upstream, laser clipping, or common-path distortion.
P-Adj The number of times the headend instructed the CM to adjust transmit (TX)
power more than 3 dB. It can indicate amplifier degradation, poor
connections, or thermal sensitivity.
Flap The sum of P-Adj and Ins values. CMs with high flap counts have high SIDs
and might not register.
Time The most recent time that the CM dropped the connection.
Command Description
show cable flap-list Displays the current contents of the flap list.
show cable modem Displays information for the registered and unregistered CMs.
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] ipv6
[cpe | prefix | registered | unregistered]
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] ipv6 [cpe | prefix | registered | unregistered]
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines Use the show cable modem ipv6 command without any options to display IPv6 information for all CMs
on the CMTS router.
Using the keyword options, you can display IPv6 information by IP address (IPv4 or IPv6) of a particular
CM, for all CMs associated with a specified cable interface, by MAC address of a CM, or by domain
name of a CM.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Field Description
MAC Address MAC address of this CM.
Type Type of device that this CM is functioning as, with the
following possible values:
• B/D—CM as bridge using DHCP address assignment.
• G/D—CPE router using DHCP address assignment.
• C/A—CPE using Stateless Address Auto-Configuration
(SLAAC) address assignment.
Note In Cisco IOS Release 12.2(33)SCA, the Cisco CMTS
router does not support SLAAC.
Interface Cable line card interface and upstream associated with this
CM.
Mac State The current state of the MAC layer for this CM (See Table 67
for descriptions of the possible states).
D/IP Dual IP flag. Identifies whether or not (“Y” or “N”) the CM
or CPE supports both IPv4 and IPv6 addressing.
IP Address IP address acquired by the CM. Prior to acquisition of the IP
address, or if the CM fails registration, the following output
is shown:
• IPv4 address not yet acquired—”0.0.0.0”
• IPv6 address not yet acquired—“::”
• CM fails IPv6 registration, but online with IPv4 address
or CM fails IPv4 registration, but online with IPv6
address: “---”
• IPv6 address of IPv4-only CM, or IPv4 address of an
IPv6-only CM: “---”
Table 67 shows the possible values for the MAC state field:
Example of the show cable modem ipv6 prefix Command for all CMs
The following example shows sample output for the show cable modem ipv6 prefix command for all
CMs on the CMTS routers:
Router# show cable modem ipv6 prefix
Device Type: B - CM Bridge, R - CM Router
IP Assignment Method: D - DHCP
MAC Address Type D/IP IPv6 prefix
0006.2854.7275 R/D Y 2001:ODB8:3800:80C::/64
Example of the show cable modem ipv6 Command for all Registered CMs
The following example shows sample output for the show cable modem ipv6 registered command for
all registered CMs on the CMTS routers:
Router# show cable modem ipv6 registered
Interface Prim Online CPE IP Address MAC Address
Sid State
C4/0/U2 1 online 0 --- 0018.6835.27b3
C4/0/U2 2 online 0 2001:0DB8:3800:809:A896:1431:75EA:5EA1 0019.474a.c14a
C4/1/U1 2 online 0 --- 0007.0e03.6851
C4/1/U1 3 online 0 --- 0007.0e01.b085
C4/1/U1 4 online 0 2001:0DB8:3800:809:E97D:2986:9F37:FFE 0018.6835.27aa
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
mac[summary [total]]
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] mac[summary [total]]
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information
for that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
summary [total] (Optional) Displays a summary of MAC layer information for each cable
interface. If you add the optional total keyword, the display includes a total
of CMs that are included in each of the displayed fields.
Usage Guidelines
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Cisco IOS Release 12.3(17a)BC introduces changes for two versions of the show cable modem mac
command.
• show cable modem mac summary
The information displayed with this command is revised. The DOCSIS 2.0 column in the Quality of
Service (QoS) Provision Mode field has been removed, as this field is not applicable to QoS
provisioning in DOCSIS 2.0.
Examples This section contains examples for the different forms of the show cable modem mac command.
Default Displays
The following example shows typical output for the default form of the show cable modem mac
command:
Router# show cable modem mac
MAC Address MAC Prim Ver QoS Frag Concat PHS Priv DS US
State Sid Prov Saids Sids
0050.7366.1243 online 1 DOC1.0 DOC1.0 no no no BPI 0 0
0002.b970.0027 online 2 DOC1.1 DOC1.0 no yes yes BPI+ 0 4
0006.5314.858d online 3 DOC1.1 DOC1.1 yes yes yes BPI+ 0 4
0010.64ff.e4ad online 1 DOC1.1 DOC1.0 yes yes yes BPI+ 0 4
0010.f025.1bd9 init(rc) 2 DOC1.0 DOC1.0 no no no BPI 0 0
0010.9659.4447 online(pt) 3 DOC1.0 DOC1.0 no yes no BPI 0 0
0010.9659.4461 online(pt) 4 DOC1.0 DOC1.0 no yes no BPI 0 0
0010.64ff.e459 online 5 DOC1.0 DOC1.0 no yes no BPI 0 0
0020.4089.7ed6 online 6 DOC1.0 DOC1.0 no no no BPI 0 0
0090.9607.3831 online(pt) 7 DOC1.0 DOC1.0 no no no BPI 0 0
0090.9607.3830 online(pt) 1 DOC1.0 DOC1.0 no no no BPI 0 0
0050.7366.12fb init(i) 2 DOC1.0 DOC1.0 no no no BPI 0 0
0010.fdfa.0a35 online(pt) 3 DOC1.1 DOC1.1 yes yes yes BPI+ 0 4
The following example shows sample output for the show cable modem mac command for a particular
cable interface:
Router# show cable modem c3/0 mac
MAC Address MAC Prim Ver QoS Frag Concat PHS Priv DS US
State Sid Prov Saids Sids
0050.7366.1243 online 1 DOC1.0 DOC1.0 no no no BPI 0 0
0002.b970.0027 online 2 DOC1.1 DOC1.0 no yes yes BPI+ 0 4
0006.5314.858d online 3 DOC1.1 DOC1.1 yes yes yes BPI+ 0 4
The following example shows sample output for the show cable modem mac command for a particular
CM, as identified by its MAC address:
Router# show cable modem 0010.7bb3.fcd1 mac
MAC Address MAC Prim Ver QoS Frag Concat PHS Priv DS US
State Sid Prov Saids Sids
0010.7bb3.fcd1 online 91 DOC1.1 DOC1.1 yes yes yes BPI+ 1 4
The following example shows sample output for the show cable modem mac command for a particular
CM, as identified by its IP address:
Router# show cable modem 10.1.1.10 mac
MAC Address MAC Prim Ver QoS Frag Concat PHS Priv DS US
State Sid Prov Saids Sids
0002.b970.0027 online 2 DOC1.1 DOC1.0 no yes yes BPI+ 0 4
Table 83 describes the fields shown in the default forms of the show cable modem mac displays:
Table 83 Descriptions for the Default show cable modem mac Fields
Field Description
MAC Address The MAC address for the CM.
MAC State The current state of the MAC layer (see Table 67).
Prim SID The primary SID assigned to this CM.
Table 83 Descriptions for the Default show cable modem mac Fields
Field Description
Ver Displays the maximum supported version of DOCSIS that the CM supports
(DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).
QoS Prov Displays the version of DOCSIS that the CM currently is provisioned and
registered for (DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).
Frag Indicates whether DOCSIS 1.1 or 2.0 MAC-layer fragmentation is enabled
for this CM.
Concat Indicates whether DOCSIS 1.1 or 2.0 MAC-layer concatenation is enabled
for this CM.
PHS Indicates whether DOCSIS 1.1 or 2.0 packet header suppression (PHS) is
enabled for this CM.
Priv Indicates whether Baseline Privacy Interface (BPI) or BPI Plus (BPI+)
encryption is enabled for the CM.
DS Saids Number of downstream security association IDs (Saids) used by this CM.
US Sids Number of upstream service IDs (SIDs) used by this CM.
Table 67 shows the possible values for the MAC state field:
Router#
The following example shows the summary display when the total option is added:
Router# show cable modem mac summary total
Total: 32 0 1 31 25 0 0 25
Router#
Table 85 describes the fields shown in the show cable modem mac summary displays:
Table 85 Descriptions for the show cable modem mac summary Fields
Field Description
I/F The cable interface line card providing the upstream for this CM.
Total Total number of CMs currently active on this cable interface.
MAC Version Total number of CMs on this interface that reported in their registration
DOC 2.0 request as having DOCSIS 2.0 capabilities.
MAC Version Total number of CMs on this interface that reported in their registration
DOC 1.1 request as having DOCSIS 1.1 capabilities.
MAC Version Total number of CMs on this interface that reported in their registration
DOC 1.0 request as having DOCSIS 1.0 capabilities.
Reg/Online Total number of CMs on this interface that have completed registration and
are currently online.
QoS Provisioned Mode Total number of CMs on this interface that have been provisioned and
DOC 2.0 registered for DOCSIS 2.0 operations.
QoS Provisioned Mode Total number of CMs on this interface that have been provisioned and
DOC 1.1 registered for DOCSIS 1.1 operations.
QoS Provisioned Mode Total number of CMs on this interface that have been provisioned and
DOC 1.0 registered for DOCSIS 1.0 operations.
Related Commands
Command Description
cable modem vendor Associates the name of a vendor with its Organizational Unique
Identifier (OUI).
show cable modem Displays information for the registered and unregistered CMs.
show cable modem cnr Displays information about the upstream carrier-to-noise ratio (CNR)
for a particular cable modem.
show cable modem Displays connectivity statistics for one or more CMs.
connectivity
show cable modem errors Displays error statistics for one or more CMs.
show cable modem flap Displays flap list statistics for one or more CMs.
show cable modem Displays station maintenance (SM) error statistics for one or more
maintenance CMs.
show cable modem phy Displays the DOCSIS PHY layer information for one or more CMs.
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable sid Displays cable interface information.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
maintenance
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] maintenance
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines This command displays information about the number of times that a CM has exhausted its maximum
retry attempts to respond to a Station Maintenance (SM) request, as well as the number of times that the
CMTS has aborted ranging with a CM during a Station Maintenance interval. This information can be
used to determine whether a particular cable modem or interface is experiencing plant or network
difficulties.
You can display this information for all online cable modems, all online cable modems for a specific
cable interface, or for one particular cable modem.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modem maintenance command for all
online cable modems:
Router# show cable modem maintenance
The following example shows sample output for the show cable modem maintenance command for all
cable modems on a specific cable interface:
Router# show cable modem c8/1/0 maintenance
Router#
The following example shows sample output for the show cable modem maintenance command for a
particular CM:
Router# show cable modem 0010.7bb3.fcd1 maintenance
Router#
Table 86 describes the fields shown in the show cable modem maintenance displays:
Field Description
MAC Address The MAC address for the CM.
I/F The cable interface line card, including upstream, for this CM.
Field Description
Prim SID The primary SID assigned to this CM.
SM Exhausted Number of times this CM has repeatedly timed out and exhausted the
Count maximum allowable retry attempts when it was sent a Station Maintenance
request. The CMTS responds by taking the CM offline, forcing the CM to
reinitialize and reregister.
SM Exhausted The last time that this CM repeatedly timed out and exhausted the maximum
Time allowable retry attempts when it was sent a Station Maintenance request.
SM Aborted Number of times the CMTS has aborted ranging for a CM during a Station
Count Maintenance period, typically because the CM has been reset.
SM Aborted The last time the CMTS aborted ranging for a CM during a Station
Time Maintenance period, typically because the CM has been reset.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
offline
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] offline
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Defaults Displays a list of all offline CMs known by the Cisco CMTS router.
Usage Guidelines This command displays a list of CMs that had either been online previously or had attempted to register
with the CMTS, but that are now considered offline. Offline cable modems remain in the CMTS
databases for 24 hours and then are deleted.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
In addition, when HCCP redundancy has been configured, the Cisco IOS software automatically
synchronizes the secondary, backup cards whenever the configuration is changed. The cards can also be
synchronized manually, using the hccp resync command. When a SYNC event command is occurring,
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the default form of the show cable modem offline
command.
Router# show cable modem offline
The following example shows sample output for the show cable modem offline command for a
particular upstream on a cable interface:
Router# show cable modem c3/0 upstream 0 offline
The following example shows sample output for the show cable modem offline command for a single
CM, as identified by its IP address:
Router# show cable modem 22.1.1.10 offline
The following example shows sample output for the show cable modem offline command for a single
CM, as identified by its MAC address:
Router# show cable modem 0030.946a.5d61 offline
Table 87 describes the major fields shown in the show cable modem offline displays:
Field Description
Interface The cable interface line card that this CM last used when it was online.
MAC address Hardware MAC address for this CM.
Prim SID The primary SID that had been last assigned to this CM before it went offline.
Previous State The last known state of the MAC layer for this CM before it went offline (see
Table 67).
Note A pound sign (#) in the Previous State column indicates that the cable
tftp-enforce mark-only command has been used to require that a CM
attempt a TFTP download of the DOCSIS configuration file before
registering, but the CM did not do so (Cisco IOS Release
12.1(11b)EC1 and Cisco IOS Release 12.2(8)BC2 or later releases).
Offline Time The time and date that this CM last went offline.
Rx Power The last known received power level (in dB) for the CM before it went offline.
Note An asterisk (*) in the Rx Power column indicates that a power
adjustment was made for that CM. An exclamation point (!) indicates
that the CM had reached its maximum power transmit level and could
not increase its power level further.
Rx SNR The last known signal-to-noise ratio (SNR) value for this CM before it went
offline.
SM Exhaust Count Number of times that this CM has exhausted the maximum allowable retries
for not responding to the regular Station Maintenance (SM) messages sent to
it by the CMTS.
Note Using the clear counters command to reset a cable interface’s counters also resets the SM
Exhaust Count field for all offline CMs to zero and resets the Offline Time field for all offline
CMs to the current time.
Table 67 shows the possible values for the Previous State field:
Usage Guidelines If all cable modems are in full service mode (all downstream and upstream channels of the cable modems
are online and operational), then the show cable modem partial-mode command does not provide any
output. This command provides output only when the cable modems register in partial service mode (one
or more downstream or upstream channels of the downstream or upstream bonded cable modems are not
operational).
Examples The following is a sample output of the show cable modem partial-mode command that displays all the
cable modems in partial service mode:
Router# show cable modem partial-mode
Field Description
MAC Address MAC address of the cable modem.
IP Address IP address that the DHCP server has assigned to the cable modem.
Field Description
I/F Cable interface line card providing the upstream for the cable
modem.
MAC State Current state of the MAC layer.
Prim Sid Primary Service ID (SID) assigned to the cable modem.
RCC ID Receive channel configuration (RCC) ID of the cable modem.
UP-reason/Failed-tcs • UP-reason—Upstream partial service reason. This is a bitmap
defined in upstream resiliency.
• Failed-tcs—Transmit channel set (TCS) bitmap of the cable
modem, which is not available.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] phy
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] phy
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Command History This table includes the following release-specific history entries:
• CX and BC Releases
• SC Release
Usage Guidelines This command displays information about the DOCSIS PHY layer for one or more CMs. You can display
information for all CMs, for all CMs on a particular cable interface, or for a particular CM, as identified
by its IP or MAC address.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples Example from Cisco IOS Release 12.3(17a)BC and Later Releases
Cisco IOS Release 12.3(17a)BC introduces revised output for the show cable modem phy command.
The MicroReflec column (MicroReflections) has been removed, and the DOCSIS Prov (DOCSIS
Provider) column has been added in its place. This new column contains DOCSIS version information.
Router# show cable modem phy
MAC Address I/F Sid USPwr USSNR Timing DSPwr DSSNR Mode DOCSIS
(dBmV) (dB) Offset (dBmV) (dB) Prov
0003.e350.9a3f C5/1/0/U0 1 0.00 30.23 2811 0.00 ----- tdma 1.0
0050.734e.c1a1 C5/1/0/U0 2 0.00 30.47 2811 0.00 ----- tdma 1.0
0007.0e01.1749 C5/1/0/U0 3 0.00 30.65 2808 0.00 ----- tdma 1.0
0007.0e00.90dd C5/1/0/U0 4 0.00 30.66 2806 0.00 ----- tdma 1.0
0003.e350.9ad3 C5/1/0/U0 5 0.00 30.47 2810 0.00 ----- tdma 1.0
0003.e38f.f4e5 C5/1/0/U0 6 0.00 30.36 2813 0.00 ----- tdma 1.0
0003.e350.9b97 C5/1/0/U0 7 0.00 30.44 2812 0.00 ----- tdma 1.0
0003.e350.9bed C5/1/0/U0 8 0.00 30.16 2814 0.00 ----- tdma 1.0
0003.e308.455d C5/1/0/U0 9 0.00 30.79 2811 0.00 ----- tdma 1.0
0003.6bd6.bfaf C5/1/0/U0 10 0.00 30.40 2813 0.00 ----- tdma 1.0
The following example shows sample output for the show cable modem phy command for all CMs on
the Cisco CMTS router:
Router# show cable modem phy
MAC Address I/F Sid USPwr USSNR Timing MicroReflec DSPwr DSSNR Mode
(dBmV) (dBmV) Offset (dBc) (dBmV) (dBmV)
The following example shows sample output for the show cable modem phy command for all CMs on
a particular cable interface:
Router# show cable modem cable 3/0 phy
MAC Address I/F Sid USPwr USSNR Timing MicroReflec DSPwr DSSNR Mode
(dBmV) (dBmV) Offset (dBc) (dBmV) (dBmV)
0008.0e09.81f8 C3/0 1 50.00 28.40 1705 26 -3.4 36.02 tdma
0003.6b3c.1aa7 C3/0 2 0.00 28.27 3643 0 0.00 ----- tdma
The following example shows sample output for the show cable modem phy command for a particular
CM:
Router# show cable modem 0050.7366.1243 phy
MAC Address I/F Sid USPwr USSNR Timing MicroReflec DSPwr DSSNR Mode
(dBmV) (dBmV) Offset (dBc) (dBmV) (dBmV)
0050.6736.4124 C3/0 14 38.00 24.58 1651 0 8.00 35.41 tdma
MAC Address I/F Sid USPwr USMER Timing DSPwr DSMER Mode DOCSIS
(dBmV) (SNR) Offset (dBmV) (SNR) Prov
(dB) (dB)
0019.474a.d396 C5/0/0/U2 1 0.00 36.12 1022 0.00 ----- tdma 1.1
0019.474a.d440 C5/0/0/U1 2 0.00 36.12 1022 0.00 ----- tdma 1.1
001a.c3ff.d6a8 C5/0/1/U0 2 0.00 36.12 3570 0.00 ----- tdma* 1.1
001a.c3ff.d6a8 C5/0/1/U1 2 0.00 36.12 1976 0.00 ----- tdma* 1.1
001a.c3ff.d6a8 C5/0/1/U2 2 0.00 36.12 3570 0.00 ----- tdma* 1.1
001a.c3ff.d6a8 C5/0/1/U3 2 0.00 36.12 3570 0.00 ----- tdma* 1.1
001e.6bfa.f714 C5/0/1/U0 8 0.00 36.12 3570 0.00 ----- tdma* 1.1
001e.6bfa.f714 C5/0/1/U1 8 0.00 36.12 1977 0.00 ----- tdma* 1.1
001e.6bfa.f714 C5/0/1/U2 8 0.00 36.12 3571 0.00 ----- tdma* 1.1
001e.6bfa.f714 C5/0/1/U3 8 0.00 36.12 3571 0.00 ----- tdma* 1.1
001a.c3ff.d59e C5/0/1/U0 1 0.00 36.12 3569 0.00 ----- tdma* 1.1
001a.c3ff.d59e C5/0/1/U1 1 0.00 36.12 1976 0.00 ----- tdma* 1.1
001a.c3ff.d59e C5/0/1/U2 1 0.00 36.12 3570 0.00 ----- tdma* 1.1
001a.c3ff.d59e C5/0/1/U3 1 0.00 36.12 3570 0.00 ----- tdma* 1.1
0019.474a.d592 C5/0/1/U0 3 0.00 27.99 1574 0.00 ----- tdma 1.1
0022.cea4.f04a C5/0/1/U0 11 0.00 36.12 1972 0.00 ----- tdma* 1.1
0022.cea4.f04a C5/0/1/U1 11 0.00 36.12 3688 0.00 ----- tdma* 1.1
0022.cea4.f04a C5/0/1/U2 11 0.00 36.12 3689 0.00 ----- tdma* 1.1
0022.cea4.f04a C5/0/1/U3 11 0.00 36.12 3696 0.00 ----- tdma* 1.1
0022.cea4.ef6a C5/0/1/U0 4 0.00 36.12 8260 0.00 ----- tdma* 1.1
0022.cea4.ef6a C5/0/1/U1 4 0.00 36.12 6827 0.00 ----- tdma* 1.1
0022.cea4.ef6a C5/0/1/U2 4 0.00 36.12 8261 0.00 ----- tdma* 1.1
0022.cea4.ef6a C5/0/1/U3 4 0.00 36.12 8261 0.00 ----- tdma* 1.1
Table 90 describes the fields shown in the show cable modem phy displays:
Field Description
MAC Address The MAC address for the CM.
I/F The cable interface on the CMTS that is providing services for this CM.
SID Service ID that this CM is using.
USPwr (dBmV) Displays the CM transmit level in dBmV, as measured by the CMTS.
USSNR (dBmV) Upstream signal-to-noise ratio (SNR) or carrier-to-noise ratio (CNR), in dB,
as measured by the CMTS. This field shows the CNR value for cable
interfaces that support onboard hardware-based spectrum management, such
as the Cisco uBR-MC16S card, and shows the SNR value for other cable
interfaces.
Note Although the field name shows the value as being given in dBmV, the
actual value should be interpreted in dB.
Timing Offset The timing offset for the CM, in ticks, as recognized on the CMTS. (A tick,
as used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it.
Note An exclamation point (!) in the Timing Offset column indicates that
the CM has exceeded the maximum delay and timing offset specified
by the cable map-advance command.
Note The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query
command, because the latter value is the offset as recognized on the
CM (which will include any internal delay between when the CM
software begins the transmission and when the bits actually appear on
the local cable interface).
Microreflec (dBc) The approximate value of microreflections on the downstream, measured in
dBc below the signal level, as seen by the CM. Microreflections are a type of
impairment that is caused by impedance mismatches between amplifiers,
couples, cables, and other equipment in the cable plant. Microreflections
create copies of a signal that arrive at the receiver with different amounts of
delay and attenuation, generating intersymbol interference (ISI) that can
cause the receiver to improperly detect the amplitude and phase of the
incoming signal.
Note This value is not exact but provides an approximate indication of the
microreflections that have been received.
DSPwr (dBmV) Downstream receive power level, in dBmV, as reported by the CM.
DSSNR (dBmV) Downstream signal-to-noise ratio (SNR), in dB, as reported by the CM.
Table 90 Descriptions for the show cable modem phy Fields (continued)
Field Description
Note This command displays values for the downstream power and SNR values only if you have
configured the cable modem remote-query command on the CMTS, and if the CM supports
providing those options.
Mode DOCSIS operating mode for the CM:
• tdma=DOCSIS 1.X, TDMA-only mode
• atdma=DOCSIS 2.0 A-TDMA mode
A hyphen (-) indicates the mode is unknown or the CM has not yet registered.
For DOCSIS 3.0-certified cable modems with multiple upstream channels,
the output may contain multiple results for the same MAC address. In
Cisco IOS Release 12.2(33)SCC, the asterix (*) that appears beside the
DOCSIS operating mode under the Mode column identifies that the CM is
operating in the MTC mode.
Note This field is the same as that returned by the
docsIfCmtsCmStatusModulationType object in the DOCS-IF-MIB.
Syntax Description slot The slot used for the cable interface line card. Valid values are 5 to 8.
subslot The subslot used for the cable interface line card. Valid values are 0 to 1.
port The downstream port used as a primary downstream port. Valid values are 0
to 4.
non-bonding-capable Displays the cable modems and primary downstreams of the cable modems
that are not capable of bonding.
legacy-initial-ranging Displays modems that access with legacy INIT-RNG-REQ.
wideband Displays wideband online modems.
registered-traditional-d Displays wideband cable modems registered in traditional pre-DOCSIS3.0
ocsis mode.
Usage Guidelines Use this command to display the primary downstream channel information of modems for different
modem categories in terms of bonding capability, such as, non-bonding-capable modems accessed with
legacy initial ranging or wideband cable modems registered via traditional DOCSIS.
Examples The following show cable modem primary-channel non-bonding-capable command shows the
individual cable modems displays and the primary downstream channel for each cable modem.
Router# show cable modem primary-channel non-bonding-capable
MAC Address IP Address Host MAC Prim Num Primary DS
Interface State Sid CPE Downstream RfId
000f.66f9.aa73 80.17.1.3 C6/0/0/U0 online(pt) 1 0 C6/0/0 255
0007.0e02.d7e9 80.17.1.7 C6/0/0/U0 online(pt) 5 0 Mo3/0/0:1 1
0013.10bb.22f9 80.17.1.2 C6/0/0/U0 online(pt) 2 0 Mo3/0/0:1 1
Related Commands show cable modem voice Displays detected voice-enabled modems.
show cable service-voice Shows the current enforced downstream type on the uBR10-MC5x20 line
downstream type card.
Syntax Description slot The slot used for the cable interface line card. Valid values are 5 to 8.
subslot The subslot used for the cable interface line card. Valid values are 0 to 1.
port The downstream port used as a MAC domain host interface port. Valid values are
0 to 4.
Usage Guidelines Use the show cable modem primary-channel summary total command to display the number of cable
modems grouped by primary downstream channels. You can also use this command to display
information for narrowband and wideband modems and group the information based on a SPA or a
uBR10-MC 5x20 primary downstream. You can also display information on modems based on a specific
cable MAC domain.
Examples The following example shows attributes of the primary channels to which the various modems are hosted
under the CGD domain c6/0/0.
Router#show cable modem primary-channel
MAC Address IP Address Host MAC Prim Num Primary DS
Interface State Sid CPE Downstream RfId
000f.66f9.aa73 80.17.1.2 C6/0/0/U0 online 13 0 C6/0/0 255
000f.66f9.b193 80.17.1.3 C6/0/0/U0 online 14 0 C6/0/0 255
0012.17ea.f3fb 80.17.1.5 C6/0/0/U0 online 15 0 C6/0/0 255
0019.474a.d4f8 80.17.1.13 C6/0/0/U0 online 16 0 C6/0/0 255
0000.cab7.7f1c 80.17.1.8 C6/0/0/U0 online 17 1 C6/0/0 255
0019.474a.d3d4 80.17.1.11 C6/0/0/U0 online 18 0 C6/0/0 255
0007.0e02.d7e9 80.17.1.10 C6/0/0/U0 online 19 0 C6/0/0 255
0019.474a.cd82 80.17.1.20 C6/0/0/U0 online 20 0 C6/0/0 255
0019.474a.d3fa 80.17.1.7 C6/0/0/U0 online 22 0 C6/0/0 255
0018.6852.82ea 80.17.1.6 C6/0/0/U0 online 24 0 C6/0/0 255
0013.10bb.23d1 80.17.1.12 C6/0/0/U0 online 23 1 Mo3/0/0:0 0
The following example shows modems grouped according to their capability, indicating whether they
are wideband or narrowband modems. The command also displays the local of the primary downstreams
of the modem, indicating whether the primary downstream is a SPA downstream (Remote) or a
uBR10-MC 5x20 downstream (Local). The Wideband column indicates if the status of the modem is
online or wideband-online.
C6/0/1 0 0 0 0 0 0 0 0 0 0 0
Subtotal: 5 5 5 0 0 0 0 0 0 0 0
C6/0/1 0 0 0 0 0 0 0 0 0 0 0
Subtotal: 5 5 5 0 0 0 0 0 0 0 0
Total: 11 11 11 0 0 0 0 0 0 0 0
The example below shows the modems grouped by primary downstream channels for the cable MAC
domain c6/0/0.
Router#show cable modem primary-channel summary c6/0/0 total
Cable Modem
Total Reg Oper Unreg Offline Wideband initRC initD initIO initO 0-Blaze
Subtotal: 1 1 1 0 0 0 0 0 0 0 0
Total: 11 11 11 0 0 0 0 0 0 0 0
Syntax Description ip-address IPv4 or IPv6 address of a specific CM to be displayed. If you specify the IP
address for a CPE device behind a CM, information for that CM is displayed.
mac-address MAC address of a specific CM to be displayed. If you specify the MAC
address for a CPE device behind a CM, information for that CM is displayed.
privacy Displays the privacy information for the CMs.
verbose Displays detailed information for the CMs.
Usage Guidelines This command displays privacy information of a particular CM, identified by its IP address or MAC
address.
Examples The following sample output from the show cable modem privacy command shows the privacy
information for a particular CM using a specified MAC address.
Router# show cable modem 0018.6835.2987 privacy
Example of show cable modem privacy verbose Command Output for a Specified MAC Address
The following example shows sample output for the verbose option for a particular CM:
Router# show cable modem 0018.6835.2987 privacy verbose
MAC Address : 0018.6835.2987
Primary SID : 10
BPI Mode : BPI+
BPI State : assign(tek)
Security Capabilities :
Encryption : DES-56
EAE : Unsupported
Latest Key Sequence : 2
Key Status : Active
Remaining Lifetime : 256 sec
Key Gracetime : 60 sec
Authorization Key : 2004065504831967119C16051FD722C5209E165F
Key Encryption Key : F14EFC15118B6B06
Upstream HMAC Key : 150E3F56451F6E033DEB79BCF819A9D8EAF6B95D
Downstream HMAC Key : 9AA3EC8869D64927560589692CCE4C21F3DA9029
Current Key Sequence : 2
Authorization Counters :
Authorization Infos : 4
Authorization Requests : 2
Authorization Replies : 2
Authorization Rejects : 0
Authorization Invalids : 0
Traffic Key Counters :
Traffic Key Requests : 4
Traffic Key Replies : 4
Traffic Key Rejects : 0
Traffic Key Invalids : 0
Certificate Counters :
Untrusted Manufacturer : 0
Untrusted CM Certificate : 0
Issuer Not Found : 0
Invalid Signature : 0
Expired Certificate : 0
Certificate Not Activated: 0
Certificate in Hotlist : 0
Public Key Mismatch : 0
Invalid MAC : 0
Invalid CM Certificate : 0
CA Certificate Details :
Certificate Serial : 57BF2DF60E9FFBECF8E69709DE34BC26
Certificate Self-Signed : False
Certificate State : Chained
CM Certificate Details :
CM Certificate Serial : 010244AF1A135202
CM Certificate State : Chained
KEK Reject Code : None
KEK Reject Reason : No Information
KEK Invalid Code : None
KEK Invalid Reason : No Information
Table 91 describes the major fields shown in the show cable modem privacy command display:
Field Description
MAC Address MAC address for the CM.
Prim SID Primary SID assigned to the CM.
BPI Mode Baseline Privacy Interface (BPI) mode used.
BPI State Displays the BPI state.
Security Capabilities Security capabilities of the modem like encryption algorithm
and Early Authentication and Encryption (EAE).
Encryption Encryption method used.
Field Description
EAE EAE support.
Latest Key Sequence Latest key sequence number.
Key Status Status of the key; whether active or not.
Remaining Lifetime Remaining lifetime of the key in seconds.
Key Gracetime Grace time available for the key in seconds.
Authorization Key Authorization key code.
Key Encryption Key Key used to encrypt the traffic key.
Upstream HMAC Key Upstream Hashed Message Authentication Code (HMAC)
key.
Downstream HMAC Key Downstream Hashed Message Authentication Code (HMAC)
key.
Current Key Sequence Current key sequence number.
Authorization Counters Authorization counter information.
Authorization Infos Authorization information.
Authorization Requests Number of authorized requests.
Authorization Replies Number of authorized replies.
Authorization Rejects Rejected authorization.
Authorization Invalids Invalid authorization.
Traffic Key Counters Traffic key counter informayion.
Traffic Key Requests Number of traffic key requests.
Traffic Key Replies Number of traffic key replies.
Traffic Key Rejects Number of traffic key rejects.
Traffic Key Invalids Number of invalid traffic keys.
Certificate Counters Certificate counter information.
Untrusted Manufacturer Count of untrusted manufacturers.
Untrusted CM Certificate Count of untrusted CM certificates.
Issuer Not Found Count of certificate issuers not found in the database.
Invalid Signature Count of invalid signatures.
Expired Certificate Number of expired certificates.
Certificate Not Activated Count of certificates not activated.
Certificate in Hotlist Number of certificates in hotlist.
Public Key Mismatch Number of public key mismatch.
Invalid MAC Number of invalid MACs.
Invalid CM Certificate Number of invalid CM certificates.
CA Certificate Details CA certificate information.
Certificate Serial CA certificate serial number.
Certificate Self-Signed Self-signed CA certificate.
Field Description
Certificate State Current state of the CA certificate.
CM Certificate Details CM certificate information.
CM Certificate Serial CM certificate serial number.
CM Certificate State Current state of the CM certificate.
KEK Reject Code Key Encryption Key (KEK) reject code.
KEK Reject Reason KEK reject reason.
KEK Invalid Code KEK invalid code.
KEK Invalid Reason Reason for the invalid KEK.
Primary SID Information Primary SID assigned to this CM.
SID SID used by the CM.
Encryption Algorithm Encryption algorithm used.
Latest Sequence Number Latest sequence number.
Current Sequence Number Current sequence number.
Hardware Keys Match Hardware key match.
DES Key Data Encryption Standard (DES) key number.
DES IV Initialization vector. This can be AES or DES.
TEK Requests Displays the number of Traffic Exchange Key (TEK)
requests.
TEK Replies Number of TEK requests.
TEK Rejects Number of TEK rejects.
TEK Invalids Number of invalid TEKs.
TEK Receive Errors Number of TEK receive errors.
TEK Reject Code TEK reject code.
TEK Reject Reason TEK reject reason.
TEK Invalid Code TEK invalid code.
TEK Invalid Reason TEK invalid reason.
Syntax Description ip-address Specifies the IPv4 or IPv6 address of a specific CM to be displayed. If you
specify the IP address for a CPE device behind a CM, information for that
CM is displayed.
mac-address Specifies the MAC address of a specific CM to be displayed. If you specify
the MAC address for a CPE device behind a CM, information for that CM
is displayed.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update
the cable DNS cache on the CMTS router.
verbose (Optional) Displays detailed information for each service flow ID (SFID)
for the CM.
Usage Guidelines This command displays the service flows currently in use by a CM. The default form of the display
shows one service flow per line, while the verbose form displays complete information for each flow.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the show cable modem qos command for a particular
CM, as identified by its MAC address:
Router# show cable modem 0010.7bb3.fcd1 qos
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput
State Type
3 US act 1 BE 7 2000000 1522 100000 0
4 DS act N/A BE 0 4000000 1522 0 0
The following example shows sample output for the show cable modem qos command for a particular
CM, as identified by its IP address:
Router# show cable modem 22.1.1.10 qos
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput
State Type
7 US act 3 BE 0 0 3044 0 0
9 US act 4 BE 0 1000000 65224 0 0
10 US act 5 BE 0 1000000 65224 0 0
8 DS act N/A BE 0 0 3044 0 0
The following example shows sample output for the verbose form of the show cable modem qos
command for a particular CM, as identified by its IP address:
Router# show cable modem 22.1.1.10 qos verbose
Sfid : 7
Current State : Active
Sid : 3
Traffic Priority : 0
Maximum Sustained rate : 0 bits/sec
Maximum Burst : 3044 bytes
Mimimum Reserved rate : 0 bits/sec
Sfid : 9
Current State : Active
Sid : 4
Traffic Priority : 0
Maximum Sustained rate : 1000000 bits/sec
Maximum Burst : 65224 bytes
Mimimum Reserved rate : 0 bits/sec
Minimum Packet Size : 64 bytes
Admitted QoS Timeout : 0 seconds
Active QoS Timeout : 0 seconds
Maximum Concatenated Burst : 1522 bytes
Scheduling Type : Best Effort
Request/Transmission policy : 0x0
IP ToS Overwrite[AND-mask, OR-mask] : 0xFF, 0x0
Current Throughput : 0 bits/sec, 0 packets/sec
Sfid : 10
Current State : Active
Sid : 5
Traffic Priority : 0
Maximum Sustained rate : 1000000 bits/sec
Maximum Burst : 65224 bytes
Mimimum Reserved rate : 0 bits/sec
Minimum Packet Size : 64 bytes
Admitted QoS Timeout : 0 seconds
Active QoS Timeout : 0 seconds
Maximum Concatenated Burst : 1522 bytes
Scheduling Type : Best Effort
Request/Transmission policy : 0x0
IP ToS Overwrite[AND-mask, OR-mask] : 0xFF, 0x0
Current Throughput : 0 bits/sec, 0 packets/sec
Sfid : 8
Current State : Active
Sid : N/A
Traffic Priority : 0
Maximum Sustained rate : 0 bits/sec
Maximum Burst : 3044 bytes
Mimimum Reserved rate : 0 bits/sec
Minimum Packet Size : 64 bytes
Admitted QoS Timeout : 200 seconds
Active QoS Timeout : 0 seconds
Maximum Latency : 0 usecs
Current Throughput : 0 bits/sec, 0 packets/sec
Router#
The following example shows sample output for the verbose form of the show cable modem qos
command indicating the traffic peak rate value for a specific service flow.
Router# show cable modem 22.1.1.10 qos verbose
Sfid : 40
Current State : Active
Sid : 35
Traffic Priority : 4
Maximum Sustained rate : 20000000 bits/sec
Maximum Burst : 20000000 bytes
Minimum Reserved rate : 0 bits/sec
Minimum Packet Size : 0 bytes
Admitted QoS Timeout : 200 seconds
Active QoS Timeout : 0 seconds
Maximum Concatenated Burst : 65535 bytes
Scheduling Type : Best Effort
Request/Transmission policy : 0x0
IP ToS Overwrite[AND-mask, OR-mask] : 0xFF, 0x0
Peak Rate : 50000000 bits/sec
Current Throughput : 0 bits/sec, 0 packets/sec
Table 92 describes the major fields shown in the show cable modem qos displays:
Field Description
Sfid Identifies the Service Flow ID (SFID) for this service flow.
Dir Identifies whether the service flow applies to the downstream (DS) or
upstream (US) direction.
Curr State Current State—Identifies the current state of the service flow: Active or
Inactive.
Sid Identifies the Service ID (SID) associated with this SFID.
Sched Type Identifies this service flow’s scheduling type:
• BE—Best-Effort
• NRTPS—Non-Real-Time Polling Service
• RTPS—Real-Time Polling Service
• RSVD—Reserved but not yet in use
• UGS_AD—Unsolicited Grant Service with Activity Detection
• UGS—Unsolicited Grant Service
• UNDEF—Not yet defined.
Prio Traffic priority (0 to 7) given to this service flow.
MaxSusRate Maximum sustained rate value, in bits per second.
MaxBrst Maximum burst value, in bytes.
MinRsvRate Minimum reserved rate, in bits per second.
Throughput Current Throughput for this service flow, in packets per second.
Minimum Packet Size Assumed minimum reserved rate packet size on this service flow, in bytes.
Admitted QoS Timeout Timeout for admitted QoS parameters, in seconds, which specifies the length
of time that the CMTS must reserve resources for a service flow’s admitted
Qos parameter set, when they exceed the resources allowed by the active QoS
parameter set.
Table 92 Descriptions for the show cable modem qos Fields (continued)
Field Description
Active QoS Timeout Timeout for active Qos parameters, in seconds, which specifies the maximum
amount of time that resources can remained unused on an active service flow.
Maximum Latency Maximum downstream latency allowed for packets using this service flow, in
microseconds.
Examples The following example shows typical output for the default version of the show cable qos enforce-rule
command:
Router# show cable qos enforce-rule
Name Dur Dir byte-cnt Auto rate penalty Reg Enf Ena Persist
(min) (kbytes) enf (min) (min) QoS QoS
residential 10 us 5 act 1 10080 5 10 Yes Yes
ef-q11d 30 ds 150 act 1 20 11 99 Yes Yes
The following example shows sample output from the show cable qos enforce-rule command for a
particular enforce-rule named “residential”:
Router# show cable qos enforce-rule residential
Name Dur Dir byte-cnt Auto rate penalty Reg Enf Ena Persist
(min) (kbytes) enf (min) (min) QoS QoS
residential 10 us 5 act 1 10080 5 10 Yes Yes
Table 113 describes the significant fields displayed by the show cable qos enforce-rule command.
.
Table 93 show cable qos enforce-rule Field Descriptions
Field Description
Name Name of the enforce-rule.
Dur (min) The monitoring duration period, in minutes.
Dir Direction in which the byte-count is applied:
• DS—Downstream direction
• US—Upstream direction
byte-cnt (kbytes) Maximum number of bytes, in kilobytes, that subscribers using this
enforce-rule can transmit during the monitoring-duration window before
being considered to be overconsuming.
Auto enf Displays whether the enforce-rule QoS profile is automatically activated
when a subscriber exceeds their allowed bandwidth.
rate (min) Size of the sample-rate interval, in minutes.
penalty (min) Size of the penalty period, in minutes.
Reg QoS Profile ID for the registered QoS profile or the name of the service class.
Enf QoS Profile ID for the enforced QoS profile or the name of the service class.
Field Description
Ena Displays whether this enforce-rule is currently enabled and active.
Persist Displays whether this enforce-rule keeps the enforced QoS profile in
force across cable modem reboots:
• Yes—Enforced QoS profiles remain in effect across cable modem
reboots.
• No—Enforced QoS profiles do not remain in effect when a cable
modem reboots. See the no-persistence option for the qos-profile
enforced command.
The following example shows the sample output from the show cable qos enforce-rule verbose form
of the command with the new output fields beginning in Cisco IOS Release 12.3(23)BC2:
Name : test
Version : docsis10
Monitoring Type : peak-offpeak
Registered : 255
Enforced : 4
Monitoring Duration : 120 (in minutes)
Sample-rate : 10 (in minutes)
Average-rate : 1 kbits/sec
Direction : upstream
Penalty Time : 10080 (in minutes)
Penalty End-time : 23 (time of day in hrs)
Rule Enabled : Yes
Persistence : Yes
Week-end : Yes
First Peak Time : 6
Duration : 180 (in minutes)
First Average-rate : 2 kbits/sec
Second Peak Time : 18
Duration : 240 (in minutes)
Second Averate-rate : 3 kbits/sec
Offpeak Duration : 120 (in minutes)
Offpeak Average-rate : 1 kbits/sec
Auto-enforce : active
Weekend First Peak Time : 8
Weekend First Duration : 120 (in minutes)
Weekend First Average-rate : 2 kbits/sec
Weekend Second Peak Time : 18
Weekend Second Duration : 180 (in minutes)
Weekend Second Average-rate : 5 kbits/sec
Weekend Offpeak Duration : 240 (in minutes)
Weekend Offpeak Average-rate : 4 kbits/sec
Weekend Auto-enforce : active
The following example shows the sample output from the show cable qos enforce-rule verbose form
of the command with the new output fields in Cisco IOS Release 12.3(33)SCD2:
Router# show cable qos enforce-rule test verbose
Name : test
Version : docsis11
Monitoring Type : peak-offpeak
Registered : REG-DS
Enforced : ENF-DS
Command Description
service-class Specifies a service class (enforced or registered) that should be used for the
(enforce-rule) cable modem monitoring in an enforce-rule. This command is applicable for
DOCSIS 1.1 or later cable modems.
show cable Displays subscribers who are violating their registered QoS profiles.
subscriber-usage
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
registered
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] registered
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Defaults Displays a list of all registered CMs on the Cisco CMTS router.
Usage Guidelines
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
Cable3/0/U0 1 online 2812 -0.25 5 1 10.18.1.5 0030.80bc.2303
Cable3/0/U0 2 online 2804 0.50 5 0 10.18.1.9 0006.2854.73f5
The following example shows sample output for the show cable modem registered command for a
particular cable interface:
Router# show cable modem c8/1/0 registered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U1 1 online 1548 0.00 5 0 10.1.1.11 0050.7366.1243
C8/1/0/U4 2 online 1925 0.00 5 0 10.1.1.10 0002.b970.0027
C8/1/0/U4 3 online 1918 -0.50 2 0 10.1.1.10 0006.5314.858d
The following example shows sample output for the show cable modem registered command for a
single CM, as identified by its IP address:
Router# show cable modem 22.1.1.10 registered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U4 3 online 1918 -0.75 2 0 10.1.1.10 0006.5314.858d
The following example shows sample output for the show cable modem registered command for a
single CM, as identified by its MAC address:
Router# show cable modem 0006.5314.858d registered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U4 3 online 1918 -0.25 2 0 10.1.1.10 0006.5314.858d
Note An asterisk (*) in the Receive Power column indicates that a power adjustment has been made for that
CM. An exclamation point (!) in the Receive Power column indicates that the CM has reached its
maximum power transmit level and cannot increase its power level further. An exclamation point (!) in
the Timing Offset column indicates that the CM has exceeded the maximum delay and timing offset
specified by the cable map-advance command.
A pound sign (#) in the MAC State column indicates that the cable tftp-enforce mark-only command
has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before
registering, but the CM did not do so (Cisco IOS Release 12.1(11b)EC1 and Cisco IOS
Release 12.2(8)BC2 or later releases).
Tip The show cable modem command displays the CM timing offset in DOCSIS ticks, while other
commands, such as cable map-advance, display the offset in microseconds. Use the following method
to convert microseconds to DOCSIS ticks: ticks = microseconds*64/6.25.
Table 94 describes the major fields shown in the show cable modem registered displays:
Field Description
Interface The cable interface line card providing the upstream for this CM.
Prim SID The primary SID assigned to this CM.
Online State The current state of the MAC layer. Should show “online” for registered CMs.
Timing Offset The timing offset for the CM, in ticks, as recognized on the CMTS. (A tick,
as used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it.
Note An exclamation point (!) in the Timing Offset column indicates that
the CM has exceeded the maximum delay and timing offset specified
by the cable map-advance command.
Note The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query
command, because the latter value is the offset as recognized on the
CM (which will include any internal delay between when the CM
software begins the transmission and when the bits actually appear on
the local cable interface).
Rec Power The received power level (in dB) for the CM.
Note An asterisk (*) in the RxPwr column indicates that a power
adjustment has been made for that CM. An exclamation point (!)
indicates that the CM has reached its maximum power transmit level
and cannot increase its power level further.
QoS Displays the QoS profile assigned to the CM (DOCSIS 1.1 and DOCSIS 2.0
CMs only).
CPE Indicates the number of CPE devices for which the CM is providing services.
IP Address The IP address that the DHCP server has assigned to the CM.
MAC Address The MAC address for the CM.
Related Commands
Command Description
cable modem vendor Associates the name of a vendor with its Organizational Unique Identifier
(OUI).
show cable modem Displays information for the registered and unregistered CMs.
show cable modem Displays the access groups for the CMs on a particular cable interface.
access-group
show cable modem Displays displays voice call information for a particular CM, identified
calls either by its IP address or MAC address.
show cable modem Displays information about the classifiers for a particular CM.
classifiers
show cable modem Displays connectivity statistics for one or more CMs.
connectivity
show cable modem Displays the CPE devices accessing the cable interface through a particular
cpe CM.
show cable modem Displays a list of the CMs that are marked as offline with the Cisco CMTS.
offline
show cable modem Displays a list of the CMs that are marked as unregistered with the
unregistered Cisco CMTS.
show cable modem Displays the vendor name or Organizational Unique Identifier (OUI) for the
vendor CMs on each cable interface.
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
Usage Guidelines This command shows the statistics collected when the remote-query feature has been enabled and
configured by the cable modem remote-query command.
Note In Cisco IOS Release 12.1 CX, Cisco IOS Release 12.2 BC, and later, use the show cable
modem phy command instead of the show cable modem remote-query command.
Tip The information shown by this command can also be displayed by querying the attributes in the
CISCO-DOCS-REMOTE-QUERY-MIB.
Note Also see the information about this command’s behavior in a Hot Standby Connection-to-Connection
Protocol (HCCP) configuration, see the “Operation with Hot Standby Connection-to-Connection
Protocol (HCCP) Configuration” section on page 1194.
Examples The following example shows typical output from the show cable modem remote-query command. In
this example, the final CM (IP address of 10.200.71.2) has not been configured with an SNMP
community string that allows access to the remote-query feature.
Router# show cable modem remote-query
Remote Query Polling State : Active
Table 0-95 shows the fields displayed by the show cable modem remote-query command.
Table 0-95 Descriptions for the show cable modem remote-query Fields
Field Description
IP Address The IP address that the DHCP server has assigned to the CM.
MAC Address The MAC address for the CM.
S/N Ratio The current signal-to-noise ratio (SNR) on the downstream, as seen by the
CM.
US Power The current operational transmit power level, in dBmV, as seen by the CM.
DS Power The received power level, in dBmV, as seen by the CM. This field is set to
zero if the CM does not support power level measurements.
TX Time Offset The timing offset for the CM, in ticks, as recognized on the CM. (A tick, as
used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it. The CM value includes any internal delay between
when the CM software begins the transmission and when the bits actually
appear on the local cable interface.
Note The timing offset shown here is typically larger than the Time Offset
value shown by the show cable modem command, because the latter
value is the offset as recognized on the CMTS (which does not
include the internal delay on the CM).
Micro (dB) Reflection The approximate number of total microreflections (including in-channel
responses) on the downstream, measured in dBc below the signal level, as
seen by the CM. Microreflections are a type of impairment that is caused by
impedance mismatches between amplifiers, couples, cables, and other
equipment in the cable plant. Microreflections create copies of a signal that
arrive at the receiver with different amounts of delay and attenuation,
generating intersymbol interference (ISI) that can cause the receiver to
improperly detect the amplitude and phase of the incoming signal.
Note This value is not exact but provides an approximate indication of the
microreflections that have been received.
Modem State The current state of the MAC layer for the CM (see Table 67 on page 1207).
The following example shows typical output from the show cable modem remote-query command.
Router# show cable modem remote-query
Router#
The following example shows typical output from the show cable modem remote-query command
when the remote-query feature has not been configured.
Router# show cable modem remote-query
Router#
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] rogue
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] rogue
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines This command displays a list of cable modems that attempted to register with a DOCSIS configuration
file that does not pass the authentication required by the cable dynamic-secret command. After a cable
modem is added to the rogue list, it remains in the rogue list until one of the following occurs:
• The cable modem remains offline, without attempting to reregister, for 24 hours. It is then removed
from all of the CMTS internal databases, including the rogue list.
• An administrator manually deletes the cable modem from the CMTS internal databases, using the
clear cable modem delete command.
• An administrator unlocks the cable modem using the clear cable modem lock command.
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following sample output from the show cable modem rogue command.
Router# show cable modem rogue
Spoof TFTP
MAC Address Vendor Interface Count Dnld Dynamic Secret
Router#
Table 0-96 describes the fields shown by the show cable modem rogue command.
Field Description
MAC Address The MAC address for the CM.
Vendor Vendor name for this cable modem, as configured using the cable modem
vendor command.
Interface The cable interface line card providing the upstream for this CM.
Spoof Count Number of times that this cable modem has attempted to register with an
invalid dynamic shared-secret value.
Note To account for possible network problems, such as loss of packets and
congestion, the Cisco CMTS will allow a cable modem to attempt to
register twice before marking it as having failed the dynamic
shared-secret authentication checks.
TFTP Dnld Whether TFT downloads are enforced, as configured by the cable
tftp-enforce command.
Dynamic Secret The dynamic shared-secret for this cable modem.
Command Description
cable Configures one or more secondary shared secret keys that CMs can use to
shared-secondary-secret successfully process the DOCSIS configuration file and register with the
CMTS.
cable shared-secret Configures an authentication shared secret key that CMs must use to
successfully process the DOCSIS configuration file and register with the
CMTS.
cable tftp-enforce Requires that all CMs on a cable interface attempt to download a DOCSIS
configuration file using the Trivial File Transfer Protocol (TFTP) through
the cable interface before being allowed to register and come online.
clear cable modem lock Resets the lock on one or more CMs, and reinitializes them, so that they
can reregister with a valid DOCSIS configuration file.
show cable modem Displays information for the registered and unregistered CMs.
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable sid Displays the SID information for a CM.
Syntax Description service-type-id Specifies the name of the service type identifier.
Command Default If no service type identifier is specified, this command will show all the CMs with their respective
service-type-id.
Examples The following example shows sample output for the show cable modem service-type-id command:
Router# show cable modem service-type-id
B D
MAC Address IP Address I/F MAC Prim Service-type-id P I
State Sid I P
0018.6812.29ae 41.42.2.212 C6/1/4/U2 offline 3838 commercial N N
0018.6811.f9f8 41.42.0.140 C6/1/4/U2 offline 3225 commercial N N
0018.6811.fba6 41.42.5.169 C6/1/4/U2 offline 3439 commercial N N
0018.6812.225a 41.42.3.210 C6/1/4/U2 offline 3355 commercial N N
0018.6811.fa8c 41.42.1.133 C6/1/4/U2 offline 3091 commercial N N
0018.6812.37e8 41.42.0.136 C6/1/4/U2 offline 7439 commercial N N
0018.6811.fbca 41.42.2.255 C6/1/4/U2 offline 6263 commercial N N
0018.6811.fb44 41.42.2.17 C6/1/4/U2 offline 2996 commercial N N
0018.6812.2f20 41.42.0.100 C6/1/4/U2 offline 3544 commercial N N
Field Description
MAC Address Hardware (MAC-layer) address of the cable
modem or CPE device.
IP Address IP address of the cable modem or CPE device.
Field Description
I/F The cable interface line card providing the
upstream for this CM.
MAC State The current state of the MAC layer.
Prim Sid Primary Service ID (SID) of the device.
Service Type Id Service Type identifier.
BPI Indicates whether or not Baseline Privacy
Interface (BPI) or BPI Plus (BPI+) encryption is
enabled for the CM.
DIP Dual IP flag. Identifies whether or not (“Y” or
“N”) the CM or CPE supports both IPv4 and IPv6
addressing.
Syntax Description ip-address Specifies the IPv4 address of a specific CM to be displayed. If you specify
the IP address for a CPE device behind a CM, information for that CM is
displayed.
mac-address Identifies the MAC address of a specific CM to be displayed. You can also
specify the MAC address for a CPE device behind a CM, and information for
that CM will be displayed.
service-flow Displays summary of relevant parameters and statistics for all service flows
associated with a particular modem.
verbose (Optional) Displays comprehensive details for all service flows associated
with a particular modem.
Usage Guidelines The show cable modem service-flow command has a verbose and a non-verbose option. The
non-verbose command supports live debugging and provides a summary of relevant parameters and
statistics for all service flows of a particular modem. The verbose option of the command provides
comprehensive details for all service flows associated with a particular modem.
Examples The following is a sample output of the show cable modem service-flow command without the verbose
option:
Router# show cable modem 40.30.0.5 service-flow
SUMMARY:
MAC Address IP Address Host MAC Prim Num Primary DS
Interface State Sid CPE Downstream RfId
001a.c30c.7eec 40.30.0.5 C7/0/0/U0 online 15 0 C7/0/0 Local
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput
State Type
31 US act 15 BE 0 0 3044 0 0
32 DS act N/A BE 0 0 3044 0 0
Flags Legend:
$: Low Latency Queue (aggregated)
~: CIR Queue
Command Description
show cable modem registered Displays a list of the CMs that are marked as registered with the
Cisco CMTS.
show cable modem Displays information collected by the remote-query feature.
remote-query
show cable modem summary interface1 [interface2] upstream port1 port2 total
Syntax Description total (Optional) Displays a footer line showing the totals for each column.
interface1 (Optional) Cable interface to be summarized. The interface1 parameter can
take the following forms:
• cable slot/port—On the Cisco uBR7100 series router, the only valid
value is 1/0. On the Cisco uBR7200 series router, slot can range from 3
to 6, and port can be 0 or 1, depending on the cable interface.
• cable slot/subslot/port—On the Cisco uBR10012 router, slot can range
from 5 to 8, subslot can be either 0 or 1, and port can range from 0 to 4
(depending on the interface).
interface2 (Optional) Second cable interface, specifying a range of cable interfaces to
be summarized. The interface2 parameter has the same form as interface1.
Note When specifying a range of cable interfaces, interface1 must be the
lower-numbered interface and interface2 must be the
higher-numbered interface.
upstream port1 port2 (Optional) Specifies a range of upstream ports on the cable interfaces to be
summarized. The port1 and port2 parameters can start at 0, and port2 must
be a higher-numbered port than port1.
upstream port (Optional) Specifies a specific upstream port to be summarized. This option
can be specified only when summarizing a single cable interface.
Release Modification
12.2(8)BC1 The total option was supported for the Cisco uBR10012 universal
broadband router.
12.2(15)BC2 The upstream Description field was added to the show cable modem
summary display in Cisco IOS Release 12.2 BC.
12.3(21)BC Support was added for wideband cable modem output.
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 This command displays a summary of CMs for a single cable interface or upstream, or for a range of
cable interfaces or upstreams. The following possible combinations are possible for this command:
• show cable modem summary total—Displays a summary and a total for all CMs on the chassis.
• show cable modem summary cable x/0 total—Displays a summary of CMs on a specified card.
• show cable modem summary cable x/0 upstream port1 port2 total—Displays a summary of CMs
on the specified card and specified range of ports. The port1 value must be less than the port2 value.
• show cable modem summary cable x/0 cable y/0 total—Displays a summary of CMs on the
specified range of cards.
• show cable modem summary cable x/0 cable y/0 upstream port1 port2 total—Displays a
summary of CMs on the specified range of ports on the specified range of cards.
Note Also see the information about this command’s behavior in a Hot Standby Connection-to-Connection
Protocol (HCCP) configuration, see the “Operation with Hot Standby Connection-to-Connection
Protocol (HCCP) Configuration” in the Cisco Broadband Cable Command Reference Guide.
Examples The following example shows typical output for the default form of the show cable modem summary
command on a Cisco uBR7200 series router:
Router# show cable modem summary
Router#
Note The Description field appears in Cisco IOS Release 12.1(11b)EC, 12.2(15)BC2, and later releases, and
shows the string configured for the upstream using the cable upstream description command.
The following example shows typical output for the show cable modem summary command with the
total option on a Cisco uBR7200 series router:
Router# show cable modem summary total
Router#
The following example shows sample output for the show cable modem summary command with the
total option for a Cisco uBR10012 router:
Router# show cable modem summary total
Interface Cable Modem Description
Total Reg Unreg Offline Wideband initRC initD initIO initO
C5/0/0/U0 84 84 0 0 84 0 0 0 0
C5/0/0/U1 84 84 0 0 84 0 0 0 0
C5/0/0/U2 83 83 0 0 83 0 0 0 0
C5/0/0/U3 83 83 0 0 83 0 0 0 0
<<output omitted>>
Router#
The following example shows sample output for the show cable modem summary total command for
a range of interfaces on the Cisco uBR10012 router:
Router# show cable modem summary c5/1/1 c5/1/2 total
Interface Cable Modem Description
Total Reg Unreg Offline Wideband initRC initD initIO initO
C5/1/1/U0 84 84 0 0 84 0 0 0 0
C5/1/1/U1 84 84 0 0 83 0 0 0 0
C5/1/1/U2 83 83 0 0 83 0 0 0 0
C5/1/1/U3 83 83 0 0 83 0 0 0 0
C5/1/2/U0 84 84 0 0 84 0 0 0 0
C5/1/2/U1 84 84 0 0 84 0 0 0 0
C5/1/2/U2 83 83 0 0 83 0 0 0 0
C5/1/2/U3 83 83 0 0 83 0 0 0 0
Router#
The following example shows sample output for the show cable modem summary total command for
a range of interfaces and upstreams on the Cisco uBR10012 router:
Router# show cable modem summary c5/1/1 c5/1/2 upstream 0 1 total
Interface Cable Modem Description
Total Reg Unreg Offline Wideband initRC initD initIO initO
C5/1/1/U0 84 84 0 0 84 0 0 0 0
C5/1/1/U1 84 84 0 0 83 0 0 0 0
C5/1/2/U0 84 84 0 0 84 0 0 0 0
C5/1/2/U1 84 84 0 0 84 0 0 0 0
Router#
Note When displaying a summary for a range of ports or cable interfaces, the first port or cable interface (for
example, u0 or c4/0) must be lower-numbered than the second port or interface (for example, u6 or c6/0).
If you specify the higher-numbered port or interface first, the display shows no CMs connected.
Table 98 describes the fields shown in the show cable modem summary displays:
Field Description
Interface The cable interface line card providing the upstream for the CMs.
Total Modems or Total Total number of CMs, registered, unregistered, and offline for this interface.
Registered Modems or Total number of CMs that have registered and are online on this interface.
Reg This number might be different from the Total Modems number if some
modems are offline or not fully registered.
Unregistered Modems Total number of CMs that are either offline and not currently communicating
with the CMTS, or attempting to come online but are not yet registered.
Offline Total number of CMs that were online or attempted to register but are no
longer communicating with the CMTS.
Wideband CM is registered as a wideband CM.
init(rc) MAC state of CM is init(rc).
init(d) MAC state of CM is init(d).
init(io) MAC state of CM is init(io).
init(o) MAC state of CM is init(o).
Description Description entered for this upstream using the cable upstream description
command.
Note For information on MAC states, see the show cable modem command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Command Description
show cable modem Displays downstream and upstream traffic counters for one or more CMs.
counters
show cable modem Displays the CPE devices accessing the cable interface through a particular
cpe CM.
show cable modem Displays a list of the CMs that are marked as offline with the Cisco CMTS.
offline
show cable modem Displays a list of the CMs that are marked as registered with the
registered Cisco CMTS.
show cable modem Displays information collected by the remote-query feature.
remote-query
show cable modem Displays a list of the CMs that are marked as unregistered with the
unregistered Cisco CMTS.
show cable modem Displays the vendor name or Organizational Unique Identifier (OUI) for the
vendor CMs on each cable interface.
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
show cable modem Displays information for a wideband CMs.
wideband
Syntax Description cable slot/subslot/port (Optional) Specifies the cable interface. The following are the
valid values:
• slot—Specifies the chassis slot number of the cable
interface line card. Valid values are 5to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the port number. Valid values are 0 to 4
(depending on the cable interface).
modular-cable (Optional) Specifies the modular cable interface. The following
slot/bay/port:nb-channel-number are the valid values:
• slot—The slot where a SIP resides. On the Cisco uBR10012
router, slots 1 and 3 can be used for SIPs.
• bay—The bay in a SIP where a SPA is located. Valid values
are 0 (upper bay) and 1 (lower bay).
• port—Specifies the interface number on the SPA.
• nb-channel-number—Specifies the narrowband channel
number.
Examples The following is a sample output of the show cable modem summary wb-rf command on the cable
interface at slot/subslot/port 8/0/0:
Router# show cable modem cable 8/0/0 summary wb-rfs
The following is a sample output of the show cable modem summary wb-rf command on the modular
cable interface at slot/bay/port and narrowband channel 1/0/0 18:
Router# show cable modem c8/0/0 summary wb-rfs modular-cable 1/0/0 18
Related Commands
Command Description
show cable modem Displays a summary of CMs on one or more cable interfaces.
summary
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn] type
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] type
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Usage Guidelines
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
Examples The following example shows sample output for the show cable modem type command :
Router# show cable modem type
Boot Mode configuration:
P - Primary Boot mode (IPv6 or IPv4)
D - Dual Stack (Yes/No)
A - Alternative Provisioning Mode (Yes/No)
Field Description
MAC Address MAC address of this CM.
Interface Cable line card interface and upstream associated with this
CM.
P/D/A String of 3 values representing the boot mode configuration
of the CM as follows:
• P—Primary Boot Mode, where “v4” or “v6” indicates
IPv4 or IPv6 as the primary addressing mode.
• D—Dual Stack, where “Y” or “N” indicates whether or
not both IPv4 and IPv6 addressing modes are supported.
• A—Alternative Provisioning Mode (APM), where “Y”
or “N” indicates whether or not APM is supported.
Note APM is not supported by the Cisco CMTS routers in
Cisco IOS Release 12.2(33)SCA.
Field Description
IPv4 address IPv4 address acquired by the CM. Prior to acquisition of the
IP address, or if the CM fails IPv4 registration, the following
output is shown:
• IPv4 address not yet acquired—“0.0.0.0”
• CM fails IPv4 registration, but online with IPv6 address:
“---”
• IPv4 address of an IPv6-only CM: “---”
IPv6 Address IPv6 address acquired by the CM. Prior to acquisition of the
IP address, or if the CM fails IPv6 registration, the following
output is shown:
• IPv6 address not yet acquired—“::”
• CM fails IPv6 registration, but online with IPv4 address
“---”
• IPv6 address of IPv4-only CM: “---”
show cable modem [ip-address | mac-address | cable slot/port [upstream port] | name fqdn]
unregistered
show cable modem [ip-address | mac-address | cable slot/subslot/port [upstream port] | name
fqdn] unregistered
Syntax Description ip-address (Optional) Specifies the IPv4 or IPv6 address of a specific CM to be
displayed. If you specify the IP address for a CPE device behind a CM,
information for that CM is displayed.
mac-address (Optional) Specifies the MAC address of a specific CM to be displayed. If
you specify the MAC address for a CPE device behind a CM, information for
that CM is displayed.
cable slot/port (Optional) Displays information for all CMs on the specified cable interface
and downstream port, where:
• slot—Specifies the chassis slot number of the cable interface line card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router and
cable interface line card. Refer to the hardware documentation for your
router chassis and cable interface line card for supported slot and port
numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable interface
on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to 4,
depending on the cable interface line card.
upstream port (Optional) Displays information for all CMs using the specified upstream
port. You can specify this option only when displaying information for a
cable interface. The valid range for port begins with 0 and ends with a value
that depends on the number of upstream ports supported by the cable
interface line card.
name fqdn (Optional) Specifies the fully qualified domain name (FQDN) of the cable
device to be displayed. This option is only available if the show cable
modem domain-name command has been run for the first time to update the
cable DNS cache on the CMTS router.
Defaults Displays a list of all unregistered CMs on the Cisco CMTS router.
Usage Guidelines
Note In Cisco IOS Release 12.2(33)SCA, the show cable modem domain-name command must be run first
on the route processor (RP) of the CMTS router before any domain name can be used as part of a cable
command.
CLI commands might be very slow to respond. In particular, if you enter the show cable modem
command at the same time a SYNC event is occurring, the command might respond produce a blank
display, or it might display an error message similar to the following:
%No response from slot 6/1. Command aborted
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows sample output for the default form of the show cable modem
unregistered command.
Router# show cable modem unregistered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
Cable3/0/U0 1 online 2812 -0.25 5 1 3.18.1.5 0030.80bc.2303
Cable3/0/U0 2 online 2804 0.50 5 0 3.18.1.9 0006.2854.73f5
C6/0/U0 6 init6(i) 1532 -0.50 2 0 0.0.0.0 0018.6835.27dd
The following example shows sample output for the show cable modem unregistered command for a
particular cable interface:
Router# show cable modem c8/1/0 unregistered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U1 1 online 1548 0.00 5 0 22.1.1.11 0050.7366.1243
C8/1/0/U4 2 online 1925 0.00 5 0 23.1.1.10 0002.b970.0027
C8/1/0/U4 3 online 1918 -0.50 2 0 22.1.1.10 0006.5314.858d
The following example shows sample output for the show cable modem unregistered command for a
single CM, as identified by its IP address:
Router# show cable modem 22.1.1.10 unregistered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U4 3 online 1918 -0.75 2 0 22.1.1.10 0006.5314.858d
The following example shows sample output for the show cable modem unregistered command for a
single CM, as identified by its MAC address:
Router# show cable modem 0006.5314.858d unregistered
Interface Prim Online Timing Rec QoS CPE IP address MAC address
Sid State Offset Power
C8/1/0/U4 3 online 1918 -0.25 2 0 22.1.1.10 0006.5314.858d
Note An asterisk (*) in the Receive Power column indicates that a power adjustment has been made for that
CM. An exclamation point (!) in the Receive Power column indicates that the CM has reached its
maximum power transmit level and cannot increase its power level further. An exclamation point (!) in
the Timing Offset column indicates that the CM has exceeded the maximum delay and timing offset
specified by the cable map-advance command.
A pound sign (#) in the MAC State column indicates that the cable tftp-enforce mark-only command
has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before
registering, but the CM did not do so (Cisco IOS Release 12.1(11b)EC1 and Cisco IOS
Release 12.2(8)BC2 or later releases).
Tip The show cable modem command displays the CM timing offset in DOCSIS ticks, while other
commands, such as cable map-advance, display the offset in microseconds. Use the following method
to convert microseconds to DOCSIS ticks: ticks = microseconds*64/6.25.
Table 100 describes the major fields shown in the show cable modem unregistered displays:
Table 100 Descriptions for the show cable modem unregistered Fields
Field Description
Interface The cable interface line card providing the upstream for this CM.
Prim SID The primary SID assigned to this CM.
Online State The current state of the MAC layer (see Table 67).
Timing Offset The timing offset for the CM, in ticks, as recognized on the CMTS. (A tick,
as used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it.
Note An exclamation point (!) in the Timing Offset column indicates that
the CM has exceeded the maximum delay and timing offset specified
by the cable map-advance command.
Note The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query
command, because the latter value is the offset as recognized on the
CM (which will include any internal delay between when the CM
software begins the transmission and when the bits actually appear on
the local cable interface).
Rec Power The received power level (in dB) for the CM.
Note An asterisk (*) in the RxPwr column indicates that a power
adjustment has been made for that CM. An exclamation point (!)
indicates that the CM has reached its maximum power transmit level
and cannot increase its power level further.
QoS Displays the QoS profile assigned to the CM (DOCSIS 1.1 and DOCSIS 2.0
CMs only).
CPE Indicates the number of CPE devices for which the CM is providing services.
IP Address The IP address that the DHCP server has assigned to the CM.
MAC Address The MAC address for the CM.
Table 67 shows the possible values for the Online State field:
Syntax Description summary (Optional) Displays the total numbers for each vendor and OUI, along with
the total numbers of those vendor’s CMs that are currently registered with
the CMTS, unregistered, or offline.
Usage Guidelines This command displays the vendor name for each CM. If the vendor name has not been defined by the
cable modem vendor command, the command displays the OUI value for the modem’s vendor.
Note The Institute of Electrical and Electronics Engineers (IEEE) is the official issuer of OUI values. The
IEEE OUI web site is at http://standards.ieee.org/regauth/oui/index.shtml.
Note Also see the information about this command’s behavior in a Hot Standby Connection-to-Connection
Protocol (HCCP) configuration, see the “Operation with Hot Standby Connection-to-Connection
Protocol (HCCP) Configuration” section on page 1194.
Examples The following example shows typical output for the show cable modem vendor command:
Router# show cable modem vendor
Vendor MAC Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
Cisco 0001.9659.519f C1/0/U0 init(rc) 16 0.75 2738 0 N
Cisco 0002.b96f.fdbb C1/0/U0 online 20 1.00 2738 1 N
Cisco 0002.b96f.fdf9 C1/0/U0 online 21 0.50 2737 1 N
Cisco 0002.b96f.fff7 C1/0/U0 online 12 0.50 2737 1 N
Cisco 0002.fdfa.1163 C1/0/U0 online 1 0.00 2734 1 N
Cisco 0002.fdfa.12d5 C1/0/U0 online 14 0.00 2737 1 N
Cisco 0002.fdfa.12db C1/0/U0 online 18 0.25 2736 1 N
Cisco 0002.fdfa.12e9 C1/0/U0 online 13 0.25 2737 1 N
Cisco 0006.28dc.37fd C1/0/U0 offline 7 0.25 2734 0 N
Cisco 0006.28e9.81c9 C1/0/U0 online 2 0.75 2735 1 N
Motorola 0020.28f9.9d19 C1/0/U0 online 28 -0.25 2733 1 N
Motorola 0020.4006.b010 C1/0/U0 online 19 0.00 2728 1 N
Router#
The following example shows typical output for the show cable modem vendor command on the
Cisco uBR10012 router:
Router# show cable modem vendor
Vendor MAC Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPE Enb
Thomson 0010.9507.01db C5/1/0/U5 online 1 0.00 938 1 N
Ericsson 0080.37b8.e99b C5/1/0/U5 online 2 -0.25 1268 0 N
Cisco 0002.fdfa.12ef C6/1/0/U0 online 13 0.00 1920 1 N
Cisco 0002.fdfa.137d C6/1/0/U0 online 16 -0.50 1920 1 N
Cisco 0003.e38f.e9ab C6/1/0/U0 online 3 -0.25 1926 1 N
Cisco 0003.e3a6.7f69 C6/1/0/U0 online 15 0.50 1927 1 N
Cisco 0003.e3a6.816d C6/1/0/U0 online 4 0.00 1929 1 N
Cisco 0006.28f9.8be5 C6/1/0/U0 online 12 0.75 1922 1 N
Cisco 0001.9659.519f C6/1/1/U2 online 26 0.25 1930 1 N
Cisco 0002.b96f.fdbb C6/1/1/U2 online 29 -0.75 1929 1 N
Cisco 0002.b96f.fdf9 C6/1/1/U2 online 39 -0.50 1931 1 N
Cisco 0002.b96f.fff7 C6/1/1/U2 online 38 0.00 1928 1 N
Cisco 0002.fdfa.1163 C6/1/1/U2 online 15 0.00 1923 1 N
Cisco 0002.fdfa.12d5 C6/1/1/U2 online 35 0.25 1923 1 N
Cisco 0002.fdfa.12e9 C6/1/1/U2 online 5 -0.25 1925 1 N
Cisco 0050.7302.3d73 C6/1/1/U2 online 58 0.25 1553 1 N
Cisco 0002.fdfa.12db C7/0/0/U0 online 15 -0.75 1914 1 N
Cisco 0002.fdfa.138d C7/0/0/U5 online 4 0.25 1917 1 N
Cisco 0003.e38f.e85b C7/0/0/U5 online 17 0.25 1919 1 N
Cisco 0003.e38f.f4cb C7/0/0/U5 online 16 0.00 1922 1 N
Cisco 0003.e3a6.7fd9 C7/0/0/U5 online 1 0.25 1922 0 N
Motorola 0020.4005.3f06 C7/0/0/U0 online 2 0.00 1901 1 N
Motorola 0020.4006.b010 C7/0/0/U5 online 3 0.25 1901 1 N
Cisco 0050.7302.3d83 C7/0/0/U0 online 18 -0.25 1543 1 N
Cisco 00b0.6478.ae8d C7/0/0/U5 online 44 0.50 1920 21 N
Cisco 00d0.bad3.c0cd C7/0/0/U5 online 19 0.00 1543 1 N
Cisco 00d0.bad3.c0cf C7/0/0/U0 online 13 0.00 1546 1 N
Cisco 00d0.bad3.c0d5 C7/0/0/U0 online 12 -0.50 1546 1 N
Router#
Tip The show cable modem vendor command displays the CM timing offset in DOCSIS ticks, while other
commands, such as cable map-advance, display the offset in microseconds. Use the following method
to convert microseconds to DOCSIS ticks: ticks = microseconds*64/6.25.
Table 0-102 describes the major fields shown in the show cable modem vendor displays:
Table 0-102 Descriptions for the show cable modem vendor Fields
Field Description
Vendor The vendor name for the indicated CM, as specified by the cable modem
vendor command. If no name for this vendor has been specified, displays the
modem’s OUI value.
MAC Address The MAC address for the CM.
Table 0-102 Descriptions for the show cable modem vendor Fields (continued)
Field Description
I/F The cable interface line card providing the upstream for this CM.
MAC State The current state of the MAC layer (see Table 67 on page 1207).
Prim SID The primary SID assigned to this CM.
RxPwr The received power level (in dB) for the CM.
Note An asterisk (*) in the RxPwr column indicates that a power
adjustment has been made for that CM. An exclamation point (!)
indicates that the CM has reached its maximum power transmit level
and cannot increase its power level further.
Timing Offset The timing offset for the CM, in ticks, as recognized on the CMTS. (A tick,
as used here, is 6.25/64 microseconds.) This is the delay between when a
particular cable modem is scheduled to make a transmission and when the
CMTS actually receives it.
Note An exclamation point (!) in the Timing Offset column indicates that
the CM has exceeded the maximum delay and timing offset specified
by the cable map-advance command.
Note The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query
command, because the latter value is the offset as recognized on the
CM (which will include any internal delay between when the CM
software begins the transmission and when the bits actually appear on
the local cable interface).
Num CPE Indicates the number of CPE devices for which the CM is providing services.
BPI Enbld Indicates whether Baseline Privacy Interface (BPI) or BPI Plus (BPI+)
encryption is enabled for the CM.
Note An asterisk (*) in the RxPwr column indicates that a power adjustment has been made for that CM. An
exclamation point (!) in the Receive Power column indicates that the CM has reached its maximum
power transmit level and cannot increase its power level further. An exclamation point (!) in the Timing
Offset column indicates that the CM has exceeded the maximum delay and timing offset specified by the
cable map-advance command.
A pound sign (#) in the MAC State column indicates that the cable tftp-enforce mark-only command
has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before
registering, but the CM did not do so (Cisco IOS Release 12.1(11b)EC1 and Cisco IOS
Release 12.2(8)BC2 or later releases).
The following example shows typical output for the show cable modem vendor summary command,
displaying the total numbers for each vendor and OUI, along with the total numbers of those vendor’s
CMs that are currently registered with the CMTS, unregistered, or offline.
Router# show cable modem vendor summary
Router#
Tip You can add a timestamp to this command using the exec prompt timestamp command in line
configuration mode.
Syntax Description pending (Optional) Displays cable modems that are being moved to the target channel via
Downstream Frequency Override (DFO).
failed (Optional) Displays cable modems that have already reached the maximum
Downstream Frequency Override retry limit without success.
Usage Guidelines Use this command to display the detected voice-enabled modems.
Related Commands show cable service-voice Displays the downstream-types that are capable of providing voice
downstream-type services.
Usage Guidelines This command displays information for a one or more wideband CMs. Optionally, the CMs for which to
display information can be identified IP address, MAC address, or cable interface.
If a wideband-capable CM is not able to register as a wideband CM (for example, if no wideband channel
is available), the CM attempts to register as a traditional DOCSIS modem. The
registered-traditional-docsis keyword limits the set of wideband CMs for which to display information
to wideband-capable CMs that are currently registered as DOCSIS 1.X or DOCSIS 2.0 modems.
Examples The following example shows typical output for the default form of the show cable modem wideband
command on a Cisco uBR10012 router running a Cisco IOS version prior to Cisco IOS Release
12.2(33)SCB:
Router# show cable modem wideband
Table 103 describes the fields that are shown in the show cable modem wideband display:
Table 103 Descriptions for the show cable modem wideband Fields
Field Description
MAC Address The MAC address for the CM.
IP Address The IP address that the DHCP server has assigned to the CM.
I/F The cable interface providing the upstream for this CM.
MAC State The current state of the MAC layer (see Table 104).
Prim SID The primary SID assigned to this CM.
Bonding group ID The identifier of the primary wideband channel.
DSID The Downstream Service Identifier.
MD-DS-SG The MAC Domain Downstream Service Group, the downstream channels of
a single MAC domain that reach the cable modem.
The following example shows typical output for the default form of the show cable modem wideband
command on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB:
Router# show cable modem wideband
Note The RCC ID refers to the output of the show cable mac-domain rcc command.
Table 104 shows the possible values for the MAC State field for a wideband CM modem that registers
as a traditional DOCSIS modem:
Table 104 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1
Table 104 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1
Table 104 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1
Table 104 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Table 105 shows the possible values for the MAC state field for a wideband-capable CM that registers
as a wideband modem:
Table 105 Additional MAC States for a Wideband Cable Modem
Command Description
show interface cable Displays information about the CMs connected to a particular cable
modem interface.
show interface cable Displays cable interface information.
sid
Syntax Description ip-address Identifies the IP address of a specific cable modem to be displayed. If you specify the
IP address for a CPE device behind a cable modem, information for that cable modem
is displayed.
mac-address Identifies the MAC address of a specific cable modem to be displayed. You can also
specify the MAC address for a CPE device behind a cable modem, and information for
that cable modem will be displayed.
Usage Guidelines This command displays primary-channel information for a wideband channel that is associated with a
specific MAC address or IP address of a cable modem or CPE device behing the cable modem.
Syntax Description mac-address (Optional) Specifies the MAC address of a wideband CM to be displayed.
ip-address (Optional) Specifies the IP address of a wideband CM to be displayed.
cable slot/subslot/port Optional) Identifies a cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot—Specifies the chassis slot number of the cable interface line card.
Valid values are 5to 8.
• subslot—Specifies the secondary slot number of the cable interface line
card. Valid subslots are 0 or 1.
• port—Specifies the port number. Valid values are 0 to 4 (depending on
the cable interface).
Examples The following is a sample output of the show cable modem wideband rcs-status command on a
wideband cable interface:
Router# show cable modem wideband rcs-status
CM : 0019.474a.c0ba
RF : 1/0/0 10
Status : UP
FEC/QAM Failure : 0
Dup FEC/QAM Failure : 0
FEC/QAM Recovery : 0
Dup FEC/QAM Recovery : 0
MDD Failure : 0
Dup MDD Failure : 0
MDD Recovery : 0
Dup MDD Recovery : 0
Flaps : 0
Flap Duration : 00:00
RF : 1/0/0 11
Status : UP
FEC/QAM Failure : 0
Dup FEC/QAM Failure : 0
FEC/QAM Recovery : 0
Dup FEC/QAM Recovery : 0
MDD Failure : 0
Dup MDD Failure : 0
MDD Recovery : 0
Dup MDD Recovery : 0
Flaps : 0
Flap Duration : 00:00
Syntax Description profile (Optional) Profile number. Valid values start with 1.
verbose (Optional) Displays detailed information for an individual profile.
iuc-code (Optional) Internal usage code (IUC). Valid options are:
a-long—Advanced Phy Long Grant Burst (IUC 10)
a-short—Advanced Phy Short Grant Burst (IUC 9)
a-ugs—Advanced Phy Unsolicited Grant Burst (IUC 11)
initial—Initial Ranging Burst (IUC 3)
long—Long Grant Burst (IUC 6)
reqdata—Request/Data Burst (IUC 2) 1
request—Request Burst (IUC 1)
short—Short Grant Burst (IUC 5)
station—Station Ranging Burst (IUC 4)
cable slot/port Identifies a cable interface and downstream port on the Cisco uBR7100
series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On the
Cisco uBR7200 series router, slot can range from 3 to 6, and port can
be 0 or 1, depending on the cable interface.
cable slot/subslot/port Identifies a cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
upstream port (Optional) Displays information for a particular upstream on the
selected cable interface. The port value starts with 0 and continues up,
depending on the type of cable interface card.
1. The Cisco CMTS recognizes the reqdata burst type but does not use it.
Release Modification
12.1(3a)EC This reqdata type was added as a placeholder for scripts that might
reference it, but the DOCSIS MAC scheduler on the Cisco CMTS does not
use this type of burst.
12.2(15)CX Support was added for the Cisco uBR-MC28U/X cable interface line card,
including support for DOCSIS 2.0 A-TDMA and mixed modulation profiles.
This includes adding additional information to the command’s display, as
well as adding the a-long, a-short, a-ugs, and verbose options.
12.2(15)CX1 Added the ability to display the modulation profiles being used by a
particular cable interface and upstream.
12.2(15)BC2 This command displays all default modulation profiles 1, 21, 41, 101, 121,
201, 221, and 241), even when the cable interface card that is associated with
those profiles is not installed. Previous releases displayed only the default
modulation profiles that were in use.
Usage Guidelines The show cable modulation-profile command displays modulation profile group information. A
modulation profile is a collection of burst profiles that are sent out in a Upstream Channel Descriptor
(UCD) message to configure a modem’s transmit parameters for an upstream message burst type.
Table 106 shows the IUC codes for each burst type:
Cable Interface DOCSIS 1.X (TDMA) Mixed DOCSIS 1.X/2.0 DOCSIS 2.0 (A-TDMA)
1
Cisco uBR7100 series 1 to 10 , default=1 N/A N/A
Cisco uBR-MC16C 1 to 10, default=1 N/A N/A
Cisco uBR-MC16S 1 to 10, default=1 N/A N/A
Cisco uBR-MC28C 1 to 10, default=1 N/A N/A
Cable Interface DOCSIS 1.X (TDMA) Mixed DOCSIS 1.X/2.0 DOCSIS 2.0 (A-TDMA)
Cisco uBR10-MC5X20S, 21 to 30, default=21 121 to 130, default=121 221 to 230, default=221
Cisco uBR10-MC5X20U,
Cisco uBR10-MC5X20H
Cisco uBR-MC16U/X, 41 to 50, default=41 141 to 150, default=141 241 to 250, default=241
Cisco uBR-MC28U/X
1. Only 8 modulation profiles are supported in Cisco IOS software releases before 12.2(15)BC1, so in these releases the valid range
is 1 to 8.
Note Default modulation profiles are created for each type of card and operation mode. You cannot delete the
default modulation profiles (1, 21, 41, 101, 121, 201, 221, and 241). In Cisco IOS Release 12.2(15)BC2
and later, all default modulation profiles are displayed, even when that particular cable interface is not
installed. In previous versions, only the default modulation profiles that were in use were displayed.
Examples The following is sample output from the show cable modulation-profile command in Cisco IOS
Release 12.2(11)BC3 and earlier releases:
CMTS01# show cable modulation-profile
Mo IUC Type Preamb Diff FEC FEC Scrambl Max Guard Last Scrambl Preamb
length enco T CW seed B time CW offset
bytes size size size short
1 request qpsk 64 no 0x0 0x10 0x152 1 8 no yes 56
1 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0
1 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0
1 short qpsk 72 no 0x5 0x4B 0x152 0 8 no yes 48
The following is sample output from the show cable modulation-profile command in Cisco IOS
Release 12.2(15)CX and later releases:
Router# show cable modulation-profile
141 short 16qam 160 no 0x6 0x4C 0x152 7 8 yes yes 0 16qam na
141 long 16qam 160 no 0x8 0xE7 0x152 0 8 yes yes 0 16qam na
141 a-short 32qam 160 no 0x9 0x4C 0x152 6 8 yes yes 0 qpsk1 no
141 a-long 64qam 196 no 0xC 0xE7 0x152 0 8 yes yes 0 qpsk1 no
241 request qpsk 68 no 0x0 0x10 0x152 0 8 no yes 0 qpsk0 no
241 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 no
241 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 no
241 a-short 32qam 160 no 0x9 0x4C 0x152 6 8 yes yes 0 qpsk1 no
241 a-long 64qam 196 no 0xC 0xE7 0x152 0 8 yes yes 0 qpsk1 no
241 a-ugs 16qam 80 no 0x3 0xE7 0x152 0 8 yes yes 0 qpsk1 no
242 request qpsk 68 no 0x0 0x10 0x152 0 8 no yes 0 qpsk0 no
242 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 no
242 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 no
242 a-short qpsk 80 no 0x4 0x4C 0x152 12 8 yes yes 0 qpsk0 no
242 a-long qpsk 68 no 0x8 0xEC 0x152 0 8 yes yes 0 qpsk0 no
242 a-ugs qpsk 80 no 0x0 0xEC 0x152 0 8 yes yes 0 qpsk0 no
243 request 64qam 132 no 0x4 0x10 0x152 0 8 no yes 0 qpsk1 no
243 initial 64qam 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk1 no
243 station 64qam 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk1 no
243 a-short 64qam 160 no 0x9 0x4C 0x152 5 8 yes yes 0 qpsk1 no
243 a-long 64qam 196 no 0xC 0xE7 0x152 0 8 yes yes 0 qpsk1 no
243 a-ugs 64qam 100 no 0x7 0xE7 0x152 0 8 yes yes 0 qpsk1 no
244 request 64qam 132 no 0x4 0x10 0x152 0 8 no yes 0 qpsk1 no
244 initial 64qam 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk1 no
244 station 64qam 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk1 no
244 a-short 64qam 160 no 0x9 0x4C 0x152 5 8 yes yes 0 qpsk1 no
244 a-long 64qam 196 no 0xC 0xE7 0x152 0 8 yes yes 0 qpsk1 no
244 a-ugs 64qam 32 no 0xA 0xC8 0x152 255 32 yes yes 0 qpsk1 yes
245 initial qpsk 32 no 0xA 0xC8 0x152 32 32 no yes 0 qpsk1 yes
245 station qpsk 32 no 0xA 0xC8 0x152 32 32 yes yes 0 qpsk1 yes
245 a-short 64qam 64 no 0xA 0xC8 0x152 32 32 yes yes 0 qpsk1 yes
245 a-long 64qam 32 no 0xA 0xC8 0x152 252 32 yes yes 0 qpsk1 yes
245 a-ugs 64qam 32 no 0xA 0xC8 0x152 32 32 yes yes 0 qpsk1 yes
Router#
The following shows sample output from the show cable modulation-profile command for a mixed
mode modulation profile (TDMA/A-TDMA) on the Cisco uBR10-MC5X20S cable interface line card:
Router# show cable modulation-profile 121
Mod IUC Type Pre Diff FEC FEC Scrmb Max Guard Last Scrmb Pre Pre RS
len enco T k seed B time CW offst Type
BYTE BYTE siz size short
121 request qpsk 32 no 0x0 0x10 0x152 0 20 no yes 0 qpsk na
121 initial qpsk 64 no 0x5 0x22 0x152 0 48 no yes 64 qpsk na
121 station qpsk 64 no 0x5 0x22 0x152 0 48 no yes 64 qpsk na
121 short qpsk 64 no 0x5 0x4B 0x152 6 20 yes yes 64 qpsk na
121 long qpsk 64 no 0x8 0xDC 0x152 0 20 yes yes 64 qpsk na
121 a-short 64qam 128 no 0x5 0x63 0x152 10 20 yes yes 192 qpsk0 no
121 a-long 64qam 128 no 0xF 0xC8 0x152 0 20 yes yes 192 qpsk0 no
Router#
The following shows sample output from the show cable modulation-profile command for two
DOCSIS 2.0 modulation profiles (A-TDMA) on the Cisco uBR10-MC5X20S cable interface line card:
Router# show cable modulation-profile 221
Mod IUC Type Pre Diff FEC FEC Scrmb Max Guard Last Scrmb Pre Pre RS
len enco T k seed B time CW offst Type
BYTE BYTE siz size short
221 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 184 qpsk0 na
221 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 na
Mod IUC Type Pre Diff FEC FEC Scrmb Max Guard Last Scrmb Pre Pre RS
len enco T k seed B time CW offst Type
BYTE BYTE siz size short
241 request qpsk 68 no 0x0 0x10 0x152 0 8 no yes 0 qpsk0 no
241 initial qpsk 2 no 0x0 0x10 0x0 0 0 no no 0 qpsk1 no
241 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk0 no
241 a-short 32qam 160 no 0x9 0x4C 0x152 6 8 yes yes 0 qpsk1 no
241 a-long 64qam 132 no 0xC 0xE7 0x152 0 8 yes yes 0 qpsk1 no
241 a-ugs 16qam 80 no 0x3 0xE7 0x152 0 8 yes yes 0 qpsk1 no
Router#
The following shows sample output for the upstream option, which displays the modulation profile
currently being used by a particular upstream:
Router# show cable modulation-profile cable 4/1 upstream 1
Mod IUC Type Pre Diff FEC FEC Scrmb Max Guard Last Scrmb Pre Pre RS
len enco T k seed B time CW offst Type
BYTE BYTE siz size short
41 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 396 qpsk na
41 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 6 qpsk na
41 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 6 qpsk na
41 short qpsk 88 no 0x5 0x4C 0x152 35 42 yes yes 396 qpsk na
41 long qpsk 76 no 0x6 0xE8 0x152 135 143 yes yes 396 qpsk na
Router#
The following example shows typical detailed output for an individual modulation profile that is
displayed when using the verbose option. Each IUC is described in detail.
Router# show cable modulation-profile 1 verbose
Router#
Table 108 describes the significant fields displayed by the show cable modulation-profile command.
.
Table 108 show cable modulation-profile Field Descriptions
Field Description
Mo Modulation profile group number. A modulation profile group is the set
of burst profiles that defines upstream transmit characteristics for the
various types of upstream transmission classes.
IUC Interval usage code. Each upstream transmit burst belongs to a class that
is given a number called the interval usage code (IUC). Bandwidth maps
messages (MAP) by IUC codes used to allocate upstream time slots. The
following types are currently defined:
• Request—Bandwidth request slot
• Request Data—Bandwidth request and short data burst slot
• Initial Maintenance—Initial link registration contention slot
• Station Maintenance—Link keepalive slot
• Short Data Grant—Short data burst slot
• Long Data Grant—Long data burst slot
Type Modulation type.
Preamb length Preamble length.
Diff enco Differential encoding enabled (yes) or not enabled (no).
FEC T bytes Number of bytes that can be corrected for each forward error correction
(FEC) code word.
FEC CW size Size, in bytes, of the FEC code word.
Scrambl seed Scrambler seed value in hex format.
Max B size Maximum burst size.
Guard time size Time between successive bursts measured in symbols.
Last CW short Handling of FEC for shortened last code word.
Scrambl Scrambler enabled (yes) or not enabled (no).
Preamb offset (DOCSIS 1.0 and DOCSIS 1.1 modulation profiles) The bits to be used
for the preamble value.
Pre offst (DOCSIS 2.0 modulation profiles) The bits to be used for the preamble
value.
Pre Type (DOCSIS 2.0 modulation profiles) The A-TDMA preamble type (qpsk0
or qpsk1).
RS (DOCSIS 2.0 modulation profiles) The A-TDMA RS encoding type.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Usage Guidelines Use this command to display all the profile groups and CMs associated with the profiles.
Examples The following command shows all the profile groups and rules associated with the command:
Router# show cable multicast authorization profile-group all
The following command shows all the profiles and the session rules for each profile.
Router# show cable multicast authorization profile-list all
CMTS Authorization Profile List
-------------------------------
The following command shows all the profile groups associated with the CM.
Router# show cable multicast authorization profile-list all
Multicast Profile Group # : 0
This CM's Session Limit : 5
Profile Id Profile
0 goldservice
1 platinumservice
2 silverservice
Field Description
ProfileId Displays the QoS profile being used.
CMs Displays the CMs belonging to the profile.
Profile Displays the profile being used for multicast.
Src Displays the source IP address.
Grp Displays the group IP address.
Priority Displays the rule priority value.
Action Displays the action taken for multicast.
Command Description
show cable multicast Displays the entire Downstream Service Identifier (DSID) database content.
dsid
show cable multicast Displays the configuration information for MQoS, (Group-Config,
qos Group-QoS-Config, Group-Encryption-Config).
Usage Guidelines Use this command to display the contents of the multicast explicit tracking database.
Examples The following example shows a sample output for the show cable multicast db command:
Router# show cable multicast db
Interface : Bundle1
Session (S,G) : (*,230.1.1.1)
Fwd Intfc Sub Intfc Host Intfc CM Mac Hosts
w1/0/0:0 aaaa.bbbb.cccc 2
w1/0/0:0 aaaa.bbbb.cccc 2
Interface : Bundle2
Session (S,G) : (*,230.1.1.1)
Fwd Intfc Sub Intfc Host Intfc CM Mac Hosts
w1/0/0:0 aaaa.bbbb.cccc 2
w1/0/0:0 aaaa.bbbb.cccc 2
The following example shows a sample output for the show cable multicast db summary command:
Router# show cable multicast db summary
The following example shows a sample output for the show cable multicast db bundle bundle-interface
command:
Router# show cable multicast db bundle1
Interface : Bundle1
Session (S,G) : (*,230.1.1.1)
Fwd Intfc Sub Intfc Host Intfc CM Mac Hosts
w1/0/0:0 aaaa.bbbb.cccc 2
w1/0/0:0 aaaa.bbbb.cccc 2
The following example shows a sample output for the show cable multicast db bundle bundle-interface
summary command:
Router# show cable multicast db bundle1 summary
The following example shows a sample output for the show cable multicast db bundle bundle-interface
ipv4-address command:
Router# show cable multicast db bundle1 225.0.0.1
The following example shows a sample output for the show cable multicast db bundle bundle-interface
ipv6-address command:
Router# show cable multicast db bundle1 ff15::1
The following example shows a sample output for the show cable multicast db cm-mac command:
Router# show cable multicast db 000f.66f9.aa73
The following example shows a sample output for the show cable multicast db cm-mac host-mac-add
command:
Router# show cable multicast db aaaa.bbbb.cccc 000f.66f9.aa73
The following example shows a sample output for the show cable multicast db cm-mac hosts command:
Router# show cable multicast db aaaa.bbbb.cccc hosts
The following example shows a sample output for the show cable multicast db cm-mac proxy
command:
Router# show cable multicast db aaaa.bbbb.cccc proxy
IGMP/MLD Ver :
TimeStamp Delta :
Table 110 describes the significant fields shown in the show cable multicast db command display.
Field Description
Bundle Interface Bundle interface number.
CM Mac MAC address of the CM.
Host Mac Host MAC address.
Fwd Intfc Forwarding interface name.
Sub Intfc Sub-interface name.
Host Intfc Host interface name.
IGMP/MLD Ver IPv4 or IPv6 multicast group signaling protocols.
IPv4: IGMPv1/v2/v3
IPv6: MLDv1/v2
TimeStamp Delta Timestamp of the session.
Hosts Hosts behind the CM.
Usage Guidelines Use this command to display the DSID database content and SIP and SPA indexes assigned for a
multicast session.
Examples The following example shows a sample output for the show cable multicast dsid command:
Router# show cable multicast dsid
Example of the show cable multicast dsid ip-address Command Output That Shows the DSID Entry With Matching
Multicast Session for the Cisco uBR7246VXR and Cisco uBR7225VXR routers in Cisco IOS Release 12.2(33)SCD
The following example shows a sample output for the show cable multicast dsid ip-address [source-ip]
command:
Router# show cable multicast dsid 225.0.0.1
Example of the show cable multicast dsid wideband-Cable Command Output That Displays the Dynamic or
Preallocated Static DSID Created on a Particular Interface for the Cisco uBR7246VXR and Cisco uBR7225VXR
routers in Cisco IOS Release 12.2(33)SCD
The following example shows a sample output for the show cable multicast dsid wideband-Cable
[dynamic | static] command:
Router# show cable multicast dsid wideband-Cable 5/0:0 dynamic
Example of the show cable multicast dsid integrated-Cable Command Output That Displays the Dynamic DSID
Created on a Particular Interface for the Cisco uBR7246VXR and Cisco uBR7225VXR routers in
Cisco IOS Release 12.2(33)SCD
The following example shows a sample output for the show cable multicast dsid integrated-Cable
static command:
Router# show cable multicast dsid integrated-Cable 5/0:0 static
Table 111 describes the significant fields shown in the show cable multicast dsid command display.
Field Description
Multicast Group Multicast group.
Source Source IP address.
IDB Interface description block number.
Interface Interface name.
Dsid Downstream service identifier.
StatIndex Blaze indexes assigned for a multicast session.
SAID Security Association Identifier.
Usage Guidelines Use this command to display the the configuration information for MQoS.
Examples The following example shows sample output for the show cable multicast qos command:
Router# show cable multicast qos ?
group-config Display Multicast Group Config information
group-encryption Display Multicast Group Encryption information
group-qos Display Multicast Group QOS information
Field Description
Group Identifies the multicast group.
QOS Identifies the QoS profile that is being enforced.
Index Index number of the QoS group.
Service Class Identifies the service class being used for the multicast.
Control Identifies the type of control.
Igmp Limit Displays the Internet Group Management Protocol (IGMP)
session limit for aggregate service flows.
Override Displays the additional IGMP session admitted and
forwarded as best effort traffic.
Syntax Description slot/port Identifies the cable interface and downstream port on the
Cisco uBR7100 series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On
the Cisco uBR7200 series router, slot can range from 3 to 6, and port
can be 0 or 1, depending on the cable interface.
slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
Usage Guidelines This command is not supported on Cisco IOS Release 12.1(3a)EC1 or later releases.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description eae-exclude Displays the early authentication and encryption details.
manufacturer-cert-list Displays the BPI manufacturer certificate verification list.
root-cert-list Displays the BPI root certificate verification list.
Usage Guidelines This command appears and is available only in images that support BPI and BPI+ encryption.
Examples The following examples show how to display BPI+ certificate information using the show cable privacy
command:
Router# show cable privacy eae-exclude
EAE Exclusion List:
MAC: 1111.1111.1111 Mask: ffff.ffff.ffff
MAC: 2222.2222.2222 Mask: ffff.ffff.ffff
<certificate dump>
<certificate dump>
Router#
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following example shows typical output for the default version of the show cable qos enforce-rule
command:
Router# show cable qos enforce-rule
Name Dur Dir byte-cnt Auto rate penalty Reg Enf Ena Persist
(min) (kbytes) enf (min) (min) QoS QoS
residential 10 us 5 act 1 10080 5 10 Yes Yes
ef-q11d 30 ds 150 act 1 20 11 99 Yes Yes
ef-q11u 30 us 60 act 1 20 11 99 Yes Yes
ef-q21 720 us 60 act 1 10 21 81 Yes Yes
ef-q21d 300 ds 150 act 1 10 21 81 Yes Yes
ef-q22 720 us 60 act 1 10 22 82 Yes Yes
ef-q22d 300 ds 150 act 1 10 22 82 Yes No
ef-q23 720 us 60 act 1 10 23 83 Yes Yes
ef-q23d 300 ds 150 act 1 10 23 83 Yes Yes
The following example shows sample output from the show cable qos enforce-rule command for a
particular enforce-rule named “residential”:
Router# show cable qos enforce-rule residential
Name Dur Dir byte-cnt Auto rate penalty Reg Enf Ena Persist
(min) (kbytes) enf (min) (min) QoS QoS
residential 10 us 5 act 1 10080 5 10 Yes Yes
Table 113 describes the significant fields displayed by the show cable qos enforce-rule command.
.
Table 113 show cable qos enforce-rule Field Descriptions
Field Description
Name Name of the enforce-rule.
Dur (min) Monitoring-duration time period, in minutes.
Dir Direction in which the byte-count is applied:
• DS—Downstream direction
• US—Upstream direction
byte-cnt (kbytes) Maximum number of bytes, in kilobytes, that subscribers using this
enforce-rule can transmit during the monitoring-duration window before
being considered to be overconsuming.
Auto enf Displays whether the enforce-rule QoS profile is automatically activated
when a subscriber exceeds their allowed bandwidth.
rate (min) Size of the sample-rate interval, in minutes.
penalty (min) Size of the penalty period, in minutes.
Reg QoS Profile ID for the registered QoS profile.
Enf QoS Profile ID for the enforced QoS profile.
Ena Displays whether this enforce-rule is currently enabled and active.
Persist Displays whether this enforce-rule keeps the enforced QoS profile in
force across cable modem reboots:
• Yes—Enforced QoS profiles remain in effect across cable modem
reboots.
• No—Enforced QoS profiles do not remain in effect when a cable
modem reboots. See the no-persistence option for the qos-profile
enforced command.
The following example shows sample output from the show cable qos enforce-rule verbose form of the
command with the new output fields beginning in Cisco IOS Release 12.3(23)BC2:
Router# show cable qos enforce-rule test verbose
Name : test
Version : docsis10
Monitoring Type : peak-offpeak
Registered : 255
Enforced : 4
Monitoring Duration : 120 (in minutes)
Sample-rate : 10 (in minutes)
Average-rate : 1 kbits/sec
Direction : upstream
Penalty Time : 10080 (in minutes)
Penalty End-time : 23 (time of day in hrs)
Rule Enabled : Yes
Persistence : Yes
Week-end : Yes
Examples The following example displays the output of the show cable qos permission command:
CMTS01# show cable qos permission
Table 0-114 describes the fields displayed by the show cable qos permission command.
Field Description
Create by SNMP Indicates permission setting for creation of QoS table entries by the
Simple Network Management Protocol (SNMP).
Update by SNMP Indicates permission setting for creation of QoS table entries by
modem registration requests.
Create by modems Indicates permission setting for dynamic updating of QoS table
entries by the SNMP.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description profile-index Displays cable QoS table. Valid range is 1 to 255.
verbose Displays detailed information about the QoS profiles.
Examples The following example shows how to display the existing QoS profiles on the CMTS:
Router# show cable qos profile
ID Prio Max Guarantee Max Max TOS TOS Create B IP prec.
upstream upstream downstream tx mask value by priv rate
bandwidth bandwidth bandwidth burst enab enab
1 0 0 0 0 0 0x0 0x0 cmts(r) no no
2 0 64000 0 1000000 0 0x0 0x0 cmts(r) no no
3 7 31200 31200 0 0 0x0 0x0 cmts yes no
4 7 87200 87200 0 0 0x0 0x0 cmts yes no
5 2 256000 0 128000 1503 0x0 0x0 cm no no
Profiles 1 and 2 are always created by the CMTS at initial startup. The CMTS dynamically creates
profiles 3 and 4, as shown above, to support Voice over IP (VoIP) codecs G.711 and G.729 when a CM
configures phone lines and uses dynamic service requests to request VoIP service. The remaining
profiles, such as profile 5 above, are typically created by a CM when it comes online.
Profile 3 creates a grant-size of 31.22 KiloBytes per second for G.729 service, and profile 4 creates a
grant-size of 87.2 KiloBytes per second for G.711 service. Both profiles use a default grant-interval of
20 milliseconds. For more information on these profiles, see the TAC technical note at the following
URL:
http://www.cisco.com/warp/public/109/uBR7200_QoSMAC.html
Profile Index 1
Name Default
Upstream Traffic Priority 0
Upstream Maximum Rate (bps) 0
Upstream Guaranteed Rate (bps) 0
Unsolicited Grant Size (bytes) 0
Unsolicited Grant Interval (usecs) 0
Upstream Maximum Transmit Burst (bytes) 0
IP Type of Service Overwrite Mask 0x0
IP Type of Service Overwrite Value 0x0
Downstream Maximum Rate (bps) 0
Created By cmts(r)
Baseline Privacy Enabled no
Table 0-115 describes the fields displayed by the show cable qos profile command.
Field Description
ID Profile number.
Prio Priority level.
Max upstream bandwidth Maximum upstream bandwidth.
Guarantee upstream bandwidth Guaranteed minimum upstream bandwidth.
Max downstream bandwidth Maximum downstream bandwidth.
Max tx burst Maximum transmit burst size in bytes.
Tos mask Hex value of the mask bits.
Tos value Value of the mask byte.
Create by Identity of who created the profile:
• cmts = Created by the CMTS with read-write properties. The
profile can be modified but not deleted.
• cmts(r) = Created by the CMTS with read-only properties. The
profile cannot be modified or deleted.
• cm = Created by the CM DOCSIS configuration file.
• mgmt = Created by an operator using CLI commands.
B priv enab Describes whether Baseline Privacy Interface (BPI) encryption is
enabled (yes) or disabled (no) for this QoS profile.
IP prec. rate enab Describes whether IP precedence rate limiting enabling is enabled
(yes) or disabled (no) for this QoS profile. When a profile is created
by a CM, this value is set by the Type Length Value (TLV) 11 fields
in the DOCSIS configuration file, unless overwritten using the
cable qos profile command.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Usage Guidelines This command displays the current global rate-adapt settings that govern all cable modem and the local
rate-adapt settings that relate to a specific cable modem upstream.
Examples The following example shows a typical display of the show cable rate-adapt command:
Router# show cable rate-adapt
Global:Enabled Local-Only:Enabled global:maps 500 priority 6, rate 12 bcs 10 fcms On
Note The output “maps 500” relates to duration. It indicates that the service flow is optimized for 500 MAPs.
Table 116 describes the fields shown in the show cable rate-adapt display.
Field Description
Global Indicates if upstream utilization optimization is enabled globally
on all cable modems.
Local Indicates if upstream utilization optimization is enabled locally on
a specific upstream flow.
priority Indicates the specified priority setting.
rate Indicates the specified minimum max-rate.
bcs Indicates the number of broadcast contention minislots (BCS).
fcms Indicates if forced broadcast contention minislot (fcms) is turned
on or off.
duration Indicates the duration of a rate-adapt flow.
Syntax Description start-index (Optional) Starting index for the log entries. The valid range is from 0 to
2000. The default value is 0.
count (Optional) Total number of log entries to be displayed. The valid range is
from 0 to 2000.
clear (Optional) Clears information about rate limiting.
Examples The following is a sample output of the show cable rate-limit-ccf command that displays information
about rate limiting criteria for upstream bonded service flows on a Cisco uBR10-MC5X20H cable
interface line card:
Router# show cable rate-limit-ccf
Table 117 describes the fields shown in the show cable rate-limit-ccf command display.
Field Description
aggr_throughput Aggregate throughput value.
aggr_burst Aggregate burst rate value.
cpu_threshold CPU threshold for Continuous Concatenation and
Fragmentation (CCF) in percentage.
cpu_burst CPU burst for CCF in percentage
cpu-throttle Total number of bandwidth requests that stopped
due to CPU throttle.
Field Description
ccf-bw-drop Total number of bandwidth requests that stopped
due to CCF resource constraint.
5X20H rate limit ccf info count Total number of log entries.
Syntax Description hashfilter Displays the hash filter(s) being used in the scheme.
class Displays the displays the number of cable modems in each DDC class of the
same scheme.
calls Displays the number of active and E911 calls currently being supported on
the relative DDC nodes.
Examples The following example of the show cable redundancy hashfilter command illustrates the same DDC
Redundancy scheme (two Cisco uBR7246VXR routers). This command displays the configured hash
filter parameters. You can either list all hash filters (as shown) or list one hash filter, if specified with the
optional hash_id value at the end of the command.
Router# show cable redundancy hashfilter
HashFilter 1
HashType MacMask
default ffff.ffff.ffff
MacAddr OUI Node
0000.39cc.b270 1
0000.39cc.ba70 2
0000.39cc.c070 2
HashFilter 2
HashType MacMask
default 0000.00ff.ffff
MacAddr OUI Node
00.00.391
00.08.0D1
00.0C.E51
The following example of the show cable redundancy class command displays the number of cable
modems in each DDC class of the same scheme (two Cisco uBR7246VXR routers).
Router# show cable redundancy class
Cable3/0 32 00 0 0
Cable3/1 3200 0 0
Cable4/0320 0 0 0
Cable4/100 0 0 0
Cable5/0310 0 0 0
Cable5/1320 0 0 0
Cable6/000 0 0 0
Cable6/100 0 0 0
The following example of the show cable redundancy calls command displays the number of active 911
(E911) calls, voice calls, and the number of cable modems with service flows for each subinterface. If
the subinterface is configured on a bundle, the number of calls is the total for all the members in the
bundle.
Router# show cable redundancy calls
Examples The following is a sample output of the show cable rf-status command used to display the logical state
of all RF channels on a modular cable interface:
Router# show cable rf-status
18 UP 0
19 UP 0
20 UP 0
21 UP 0
22 UP 0
23 UP 0
Field Description
RF Indicates the RF channel ID.
Logical Status Indicates the logical up and down state of all RF channels.
Flap Counts Indicates the number of times the RF channel has dropped and recovered.
Flap Time Indicates the duration in seconds for each flap count.
The following is a sample output of the show cable rf-status command used to display the logical up
and down state of a particular channel number on a modular cable interface:
Router# show cable rf-status modular-cable 1/0/0:1
Load for five secs: 6%/0%; one minute: 3%; five minutes: 2%
Time source is NTP, .14:47:27.751 EDT Thu Aug 7 2008
Related
Commands Command Description
show interface rf-status Displays the logical up and down state for each of the configured RF
channels for a wideband interface.
Syntax
Description mac-addr (Optional) The MAC address of the specific cable modem in hexadecimal
format.
Usage Guidelines The show cable rsvp flow-db command displays contents of the RSVP to DOCSIS service-flow
mapping database.
Examples The following example shows the sample output for the show cable rsvp flow-db command.
Router# show cable rsvp flow-db
CM Count : 1
Flow Count : 1
Mac Address Src IP Src Dest IP Dest Pr Sfid Dir Handle
Port Port ot (Hex)
0019.474a.c5f6 200.0.0.1 1000 40.1.1.62 1000 6 11 DS 7000406
Field Description
Mac Address The MAC address of the specific cable modem.
Src IP RSVP path source IP address.
Src Port RSVP path source port number.
Dest IP Destination IP address.
Dest port Destination port number.
Proto IP protocol type. Here 17 is the UDP's IP protocol number.
Field Description
SFid Service flow ID.
Dir Direction of the DOCSIS service flow. Here DS indicates
downstream flow.
Syntax Description sclass-index Identifies the index for a service class that has already been defined
(1 to 255).
verbose Displays all of the defined attributes for the service class.
Usage Guidelines You can display a summary of either one service class or all service classes. You can also display a
complete listing of each service class and of all the defined service classes.
Examples The following sample output shows the standard and verbose formats of the show cable service class
command:
Router# show cable service-class
Index: 1
Name: UP_UGS
Direction: Upstream/Downstream
Traffic Priority: 0
Maximum Sustained Rate: 0 bits/sec
Max Burst: 1522 bytes
Index: 1
Name: UP_UGS
Direction: Upstream/Downstream
Traffic Priority: 0
Maximum Sustained Rate: 0 bits/sec
Max Burst: 1522 bytes
Minimum Reserved Rate: 0 bits/sec
Minimum Packet Size 100 bytes
Peak Rate 0 bits/sec
Admitted QoS Timeout 30 seconds
Active QoS Timeout 30 seconds
Scheduling Type: Unsolicited Grant Service
Request/Transmission Policy: 0x1FF
Unsolicited Grant Size: 100 bytes
Nominal Grant Interval: 20000 usecs
Tolerated Grant Jitter: 4000 usecs
Grants per Interval: 1
IP ToS Overwrite [AND-mask,OR-mask]: 0xE0,0xA0
Max Latency: 0 usecs
Parameter Presence Bitfield: {0xE08, 0xBCC000}
Index: 2
Name: UP_UGSAD
Direction: Upstream/Downstream
Traffic Priority: 0
Maximum Sustained Rate: 0 bits/sec
Max Burst: 1522 bytes
Minimum Reserved Rate: 0 bits/sec
Minimum Packet Size 100 bytes
Peak Rate 0 bits/sec
Admitted QoS Timeout 30 seconds
Active QoS Timeout 30 seconds
Scheduling Type: Unsolicited Grant Service(AD)
Request/Transmission Policy: 0x1FF
Nominal Polling Interval: 10000 usecs
Tolerated Poll Jitter: 4000 usecs
Unsolicited Grant Size: 100 bytes
Nominal Grant Interval: 20000 usecs
Tolerated Grant Jitter: 4000 usecs
Grants per Interval: 1
IP ToS Overwrite [AND-mask,OR-mask]: 0xE0,0xA0
Max Latency: 0 usecs
Parameter Presence Bitfield: {0xE08, 0xBFC000}
Index: 3
Name: UP_RTPS
Direction: Upstream/Downstream
Traffic Priority: 0
Index: 4
Name: UP_BE
Direction: Upstream/Downstream
Traffic Priority: 5
Maximum Sustained Rate: 128000 bits/sec
Max Burst: 2000 bytes
Minimum Reserved Rate: 0 bits/sec
Minimum Packet Size 64 bytes
Peak Rate 0 bits/sec
Admitted QoS Timeout 30 seconds
Active QoS Timeout 30 seconds
Maximum Concatenated Burst: 1522 bytes
Scheduling Type: Best Effort
Request/Transmission Policy: 0x0
IP ToS Overwrite [AND-mask,OR-mask]: 0xE0,0x0
Max Latency: 0 usecs
Parameter Presence Bitfield: {0xDE8, 0x80E000}
Index: 5
Name: DOWN_BE
Direction: Upstream/Downstream
Traffic Priority: 5
Maximum Sustained Rate: 1000000 bits/sec
Max Burst: 3000 bytes
Minimum Reserved Rate: 0 bits/sec
Minimum Packet Size 64 bytes
Peak Rate 0 bits/sec
Admitted QoS Timeout 30 seconds
Active QoS Timeout 30 seconds
Maximum Concatenated Burst: 0 bytes
Scheduling Type: Best Effort
Request/Transmission Policy: 0x0
IP ToS Overwrite [AND-mask,OR-mask]: 0xFF,0x0
Max Latency: 0 usecs
Parameter Presence Bitfield: {0xDE8, 0x0}
Router#
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Related Commands
Usage Guidelines Use this command to display the downstream-types that are capable for providing voice services on each
uBR10-MC 5x20 line card.
Examples The example below shows that both HA-capable-DS and MDC-DS are enabled for downstream types on
the uBR10-MC 5x20 line card in slot 5, subslot 1 and the line card in slot 6, subslot 0.
Router# show cable service-voice downstream-type
Slot 5/1 : HA-capable-DS MDC-DS
Slot 6/0 : HA-capable-DS MDC-DS
show cable signal-quality {cable {slot/port | slot/subslot/port} upstream number | cmts | mer}
Usage Guidelines The show cable signal-quality command with the mer keyword displays the modulation error rate data
per cable interface. Note that at least one cable modem (CM) must be online on the cable interface for
this command to provide the modulation error rate data. This is identical to the modulation error rate
data displayed by the show controllers command.
The CNR data is displayed only for the upstream channels that are assigned to a spectrum group.
Upstream channels with fixed frequencies do not return any CNR data.
Examples The following example shows the CNR data received on the upstream ports on the cable interface line
card at slot/subslot/port 7/0/3 on a Cisco uBR10012 router:
Router# show cable signal-quality cable 7/0/3 cmts
The following example shows the MER data received on the cable upstream port 3 on the cable interface
line card at slot/subslot/port 5/0/0 on a Cisco uBR10012 router:
Router# show cable signal-quality cable 5/0/0 upstream 3 mer
The following example shows the signal quality information for all cable interfaces on a
Cisco uBR10012 router:
Router#show cable signal-quality mer
Table 120 describes the major fields displayed by the show cable signal-quality command.
Field Description
I/F Cable interface.
CNiR (db) CNR value.
Expected Received Signal Power Expected signal power received per upstream port.
(dBmV)
Received MER (db) Received MER signal-to-noise ratio (SNR) value.
Received MER (samples) Samples used for calculating the SNR per upstream port.
Syntax Description slot/subslot/port Displays information about all CMs on the specified cable interface line
card on a Cisco CMTS router:
• slot—Chassis slot number of the cable interface line card. Valid slots
are from 5 to 8.
• subslot—Secondary slot number of the cable interface line card. Valid
subslots are 0 or 1.
• port—Downstream port number. Valid ports are from 0 to 4, depending
on the cable interface line card.
upstream port Specifies the upstream port number.
Examples The following example shows the spectrum measurements on upstream port 1 on a Cisco uBR10012
router:
Router# show cable spectrum-analysis c5/0/0 upstream 1
Field Description
Spectrum analysis measurements Spectrum measurements.
Channel center frequency Channel center frequency value.
Frequency span Frequency span.
No of Bins Total number of bins in the spectrum analysis data.
Bin spacing Spacing between the center frequency of each bin.
Resolution Bandwidth Spacing between bins after the spectral window is applied.
Amplitude Data Spectral amplitudes for the received signal power of a bin.
Syntax Description groupnum (Optional) Displays information about the specified group number
(1–32). If no group number is specified, information for all spectrum
groups is displayed.
detail (Optional) Displays whether the groups are allocated, free, or in-use.
Examples The following is sample output from the show cable spectrum-group command for all upstream
spectrum groups:
CMTS01# show cable spectrum-group
1 5.000-42.000 0 No
1 17.328 [1.60] Cable3/0 U0 0
1 5.808 [1.60] Cable3/0 U1 0
1 5.808 [1.60] Cable3/0 U2 0
1 15.792 [1.60] Cable3/0 U3 0
1 6.096 [1.60] Cable3/0 U4 0
1 5.808 [1.60] Cable3/0 U5 0
2 5.000-42.000 0 No
2 6.608 [3.20] Cable6/0 U1 0
2 5.808 [1.60] Cable6/0 U2 0
2 5.808 [1.60] Cable6/0 U3 0
2 5.808 [1.60] Cable6/0 U4 0
2 5.808 [1.60] Cable6/0 U5 0
3 5.000-42.000 0 No
3 17.488 [1.60] Cable5/0 U1 0
3 6.160 [1.60] Cable5/0 U2 0
3 36.912 [1.60] Cable5/0 U3 0
3 36.560 [1.60] Cable5/0 U4 0
3 16.240 [1.60] Cable5/0 U5 0
4 6.000- 8.600 0 No
4 16.000-18.000 0 No
4 17.168 [1.60] Cable5/0 U0 0
5 5.000-42.000 0 No
6 5.000-42.000 0 No
7 5.000-42.000 0 No
8 5.000-42.000 0 No
9 5.000-42.000 0 No
10 5.000-42.000 0 No
11 5.000-42.000 0 No
12 10.000-13.000 0 No
CMTS#
The following is sample output from the show cable spectrum-group detail command:
CMTS# show cable spectrum-group detail
1 10.000 1 Yes
1 10.000 2 Yes
1 11.000 3 Yes
1 11.000 4 Yes
1 15.000-20.000 0 Yes
A 8.400-12.600
A 15.000-20.000
1 11.008 [0.80] Cable3/0 U2 4
1 15.808 [1.60] Cable3/0 U3 0
1 Unassigned Cable3/0 U4
1 17.408 [1.60] Cable3/0 U5 0
I 10.600-11.400 4
I 15.000-16.600 0
I 16.600-18.200 0
F 8.400-10.600
F 11.400-12.600
F 18.200-20.000
C Width [3.20]
C Width [1.60]
C Width [0.80]
O 19.000 [1.60] 0
O 10.000 [0.80] 2
O 18.600 [0.80] 0
O 19.400 [0.80] 0
O 10.000 [0.80] 1
CMTS#
Table 0-122 describes the fields shown in the show cable spectrum-group displays.
Field Description
Group No. Identifies the spectrum group. When using the detail keyword, the
following also appear:
• A = Signifies that the band is allocated.
• F = Signifies that the band is free.
• I = Signifies that the band is in-use.
• C = Identifies the channel width.
• O = Identifies the offered list bands (based on the current
channel widths).
Frequency Band (MHz) Identifies the upper and lower ranges of the frequency for this
spectrum group.
Upstream Port Identifies the upstream port number.
Weekly Scheduled Availability Identifies the day and time of day when this group is available. If
no values appear in the From and To Time fields, this group is
available at all times.
Input PowerLevel Identifies the assigned decibels per millivolt (dBmV) input level.
Shared Spectrum Indicates if upstreams are physically combined (share the same
combiner group). Y or yes values indicate that upstreams that are
members of the spectrum group are combined and cannot be
assigned overlapping frequency bands.
N or no values indicate that upstreams that are members of the
spectrum group are not combined and can be assigned overlapping
frequency bands.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description over-consume (Optional) Displays only those subscribers who have exceeded their
maximum allowed bandwidth.
cable slot/port (Optional) Displays information for all CMs on the specified cable
interface and downstream port on a Cisco 7100 series or Cisco 7200
series router, where:
• slot—Specifies the chassis slot number of the cable interface line
card.
• port—Specifies the downstream port number.
Valid values for these arguments are dependent on your CMTS router
and cable interface line card. Refer to the hardware documentation for
your router chassis and cable interface line card for supported slot and
port numbering.
cable slot/subslot/port (Optional) Displays information for all CMs on the specified cable
interface on a Cisco uBR10012 router, where:
• slot—Specifies the chassis slot number of the cable interface line
card. Valid slots are 5 to 8.
• subslot—Specifies the secondary slot number of the cable
interface line card. Valid subslots are 0 or 1.
• port—Specifies the downstream port number. Valid ports are 0 to
4, depending on the cable interface line card.
upstream port (Optional) Displays information for a particular upstream on the
selected cable interface. The port value starts with 0 and continues up,
depending on the type of cable interface card.
sort-byte-count (Optional) Sorts the list by the subscriber byte count, with the highest
byte counts listed first. The default is to sort the list by Service Flow
ID (SFID). (This option is replaced by the sort-avg-rate keyword in
later releases.)
sort-avg-rate (Optional) Sorts the list by the subscriber’s average rate. The default is
to sort the list by Service Flow ID (SFID).
Command Default All subscribers are shown, with the display sorted by SFID.
Usage Guidelines The show cable subscriber-usage command displays the current usage statistics for all subscribers on
the Cisco CMTS router, all subscribers on a particular cable interface, or for only those subscribers that
are marked as over-consuming bandwidth.
Effective with Cisco IOS Release 12.3(9a)BC, the sort-byte-count keyword option is replaced by the
sort-avg-rate keyword option.
Examples The following example shows typical output for the default version of the show cable subscriber-usage
command:
Router# show cable subscriber-usage
The following example shows typical output for subscribers on a particular cable interface:
Router# show cable subscriber-usage c6/0/0
The following example shows typical output for the show cable subscriber-usage command for one
upstream on a particular cable interface:
Router# show cable subscriber-usage c6/0/1 upstream 0
The following example shows typical output for the sort-byte-count option for the show cable
subscriber-usage command:
Router# show cable subscriber-usage sort-byte-count
Sfid Mac Address Enforce-rule Total-Kbyte Last-detect Last-penalty Pen
Name Count time time Flag
7 0007.0e03.2cad test1 65157114 Feb24 11:36:34 Mar3 11:36:34 Act
9 0007.0e03.2c45 test1 16381014 -
5 0007.0e03.2c25 test1 13440960 -
Table 123 describes the fields shown by the show cable subscriber-usage command.
Field Description
SFID Number of the Service Flow ID.
Mac Address Hardware address (MAC address) of the subscriber’s cable modem.
Enforce-rule Name Name of the enforce-rule being applied to this subscriber.
Total-Kbyte Total number of kilobytes consumed by the subscriber’s cable
modem during the last monitoring-duration window.
Note The total byte count is reset to 0 whenever an enforce-rule’s
configuration is changed.
Last-detect time Last time period, if any, at which it was determined that the cable
modem was using more bandwidth than allowed by their QoS
profile. This value also shows the time at which the enforced QoS
profile was automatically applied, if this option has been enabled.
Last-penalty time If an enforced QoS profile is currently in effect, this field shows the
time period at which the subscriber’s current penalty time expires,
at which point their original registered QoS profile is restored.
Pen Flag Identifies whether a penalty enforce-rule has been applied to this
cable modem.
Related Commands
Command Description
activate-rule Specifies the number of bytes that a subscriber can transmit during the
at-byte-count monitoring period on a Cisco CMTS router.
cable qos enforce-rule Creates an enforce-rule to enforce a particular QoS profile for subscriber
traffic management and enters enforce-rule configuration mode.
duration Specifies the time period and sample rate to be used for monitoring
subscribers.
enabled (enforce-rule) Activates an enforce-rule and begins subscriber traffic management on a
Cisco CMTS Router.
penalty-period Specifies the time period that an enforced QoS profile should be in effect for
subscribers who violate their registered QoS profiles.
qos-profile enforced Specifies a QoS profile that should be enforced when users violate their
registered QoS profiles.
qos-profile registered Specifies the registered QoS profile that should be used for this enforce-rule.
show cable qos Displays the QoS enforce-rules that are currently defined.
enforce-rule
Syntax Description slot/port (Optional) Cisco IOS Release 12.3(9a)BC allows you to display
information about one specific cable interface.
Identifies the cable interface and downstream port on the Cisco uBR7100
series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On the
Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0
or 1, depending on the cable interface.
slot/subslot/port (Optional) Cisco IOS Release 12.3(9a)BC allows you to display
information about one specific cable interface.
Identifies the cable interface on the Cisco uBR10012 router. The following
are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
Usage Guidelines The show cable tech-support command displays a large amount of configuration, run-time status, and
other information about the cable interfaces on the Cisco CMTS. The output of this command can be
provided to technical support representatives when reporting a problem.
Note The show tech-support includes most of the information shown in the show cable tech-support
command. Unless the problem is clearly cable-specific, TAC personnel will typically request the show
tech-support output to troubleshoot any problems.
The show cable tech-support command displays the output of a number of different show commands.
The exact output depends on the platform, configuration, and type of protocols being used. Typically,the
output includes the output from the following commands:
• show cable modem
• show cable flap-list
• show cable qos profile
• show cable modulation-profile
• show cable spectrum-group
• show cable hop
• show interface cable sid (for each cable interface)
• show interface cable sid connectivity (for each cable interface)
• show interface cable downstream
• show interface cable upstream
• show interface cable mac-scheduler
show interface cable modem Other commands could be included in the show cable tech-support output,
depending on the CMTS platform, the Cisco IOS software being used, and the cards that are installed in
the chassis.
On the Cisco uBR10012 router, the following commands also appear in Cisco IOS Release 12.2(15)BC2
and later releases:
• show pxf cpu statistics
• show pxf cpu subblocks
• show pxf cpu buffer
• show pxf dma
• show pxf cpu cef memory
• show pxf cpu queue
• show pxf cpu statistics drop
Tip Depending on the platform and configuration, the output from the show cable tech-support command
can easily exceed the buffers found in most communications programs. To capture this output so it can
be sent to Cisco TAC, use a Telnet program that allows you to capture the output directly to disk.
Examples The following abbreviated example illustrates the cable modem and interface information for the
Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed.
Router# show cable tech-support
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (dB) Offset CPE Enb
Sid Prim MAC Address IP Address Type Age Admin Sched Sfid
State Type
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (dB) Offset CPE Enb
Sid Prim MAC Address IP Address Type Age Admin Sched Sfid
State Type
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Examples The following is a sample output of the show cable us-sg command.
Router# show cable us-sg
Cable MD 5/0/0
US-SG-ID : 1 US-Chan : U0,1,2,3,4,5
Primary-DS: 1/0/0:0 US-SG-ID: 1
MDD US-List : U0,1,2,3,4,5
MDD Ambiguity : U0,1,2,3,4,5
Cable MD 6/0/0
US-SG-ID : 1 US-Chan : U0,1,2,3
Primary-DS: 1/0/0:4 US-SG-ID: 1
MDD US-List : U0,1,2,3
MDD Ambiguity : U0,1,2,3
Cable MD 7/0/0
US-SG-ID : 1 US-Chan : U0,1,2,3
Primary-DS: 7/0/0:0 US-SG-ID: 1
MDD US-List : U0,1,2,3
MDD Ambiguity : U0,1,2,3
Primary-DS: 7/0/0:1 US-SG-ID: 1
MDD US-List : U0,1,2,3
MDD Ambiguity : U0,1,2,3
Field Description
US-SG-ID Upstream service group ID.
US-Chan Upstream channels on the cable interface line card.
Primary-DS Primary downstream interafce.
Field Description
MDD US-List MAC management message: MDD TLV type 7 content, upstream
active channel list.
MDD Ambiguity MAC management message: MDD TLV type 8 content, upstream
ambiguity resolution channel list.
New Commands
Modified Commands
Obsolete Commands
show checkpoint
To display information about the Checkpoint Facility (CF) subsystem on a Cisco CMTS, use the show
checkpoint command in privileged EXEC mode.
Usage Guidelines The Checkpoint Facility (CF) subsystem manages the passing of messages from the Active to Standby
interfaces. It also handles sequencing and throttling, as needed during redundancy operations.
Checkpoint clients, such as line cards and other subsystems, register with the CF subsystem so that they
can update the Protect card or standby processor with state changes as necessary.
The show checkpoint command displays information about the clients (other processes on the CMTS
that are sending checkpoint messages), entities, and run-time status for checkpoint operations.
The show checkpoint clients client-id command displays information about the client with a particular
client ID.
Examples The following shows typical output for the show checkpoint clients command:
Router# show checkpoint clients
Router#
The following shows typical output for the show checkpoint clients command with the client-id
parameter:
Router# show checkpoint clients 1
--------------------------------------------------------------------------------
Client Name Client Entity Bundle
ID ID Mode
--------------------------------------------------------------------------------
CHKPT Test client 1 -- On
Router#
The following shows typical output for the show checkpoint entities command:
Router# show checkpoint entities
The following shows typical output for the show checkpoint statistics command:
Router# show checkpoint statistics
Router#
show controller integrated-cable slot/port [all | association | brief | config | counters | errors |
mapping | registers | status]
Syntax Description integrated-cable Identifies the cable interface on the Cisco uBR10012 router.
slot/subslot/port
• slot—Slot where the line card resides. The valid range is from 5 to 8.
• subslot—Subslot where the line card resides. Available slots are 0 or 1.
• port—Downstream controller number on the line card. Valid port
values are from 0 to 4.
integrated-cable Identifies the cable interface on the Cisco uBR7246VXR or
slot/port Cisco uBR7225VXR router.
• slot—Slot where the line card resides.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
• port—Downstream port number on the line card. The valid port value
is 0 or 1.
all (Optional) Displays the complete information about the line card statistics.
association (Optional) Displays the controller association information.
brief (Optional) Displays brief information about the line card statistics.
config (Optional) Displays statistics about the JIB hardware and downstream PHY
configuration.
counters (Optional) Displays information about the RF and WB channel counters.
errors (Optional) Displays information about the error counters such as DOCSIS
processor error counters, BPI error counters, and queue manager error
counters.
mapping (Optional) Displays mapping statistics of the RF and WB channels.
registers (Optional) Displays the list of JIB hardware downstream register values.
status (Optional) Displays the JIB hardware and downstream PHY status.
Usage Guidelines This command allows the user to view the following line card statistics:
• Controller association
• JIB hardware downstream configuration
• Channel counters
• Errors
• Mapping of WB and RF channels
• JIB hardware downstream registers
• JIB hardware downstream status
Examples The following example shows a typical display of the show controller integrated-cable command and
the association keyword:
Router# show controller integrated-Cable 7/1/0 association
Table 125 describes the fields shown in the show controller integrated-cable association displays.
Field Description
WB channel Wideband channel number.
BG ID Bonding group ID.
Bundle num Bundle number.
NB channel Narrowband channel number.
NB chan ID Narrowband channel ID.
Reserved CIR Reserved committed information rate (CIR) value.
Total CIR Total committed information rate (CIR) value.
The following example shows a typical display of the show controller integrated-cable command and
the brief keyword:
Router# show controller integrated-Cable 7/1/0 brief
Channel Resources:
------------------
Total Non-bonded Channels..........= 20
Per-Controller Non-bonded Channels = 4
Total Bonded Channels..............= 32
Per-Controller Bonded Channels.....= 6
Slot-Wide Resources:
--------------------
Number of PHS Rules...........= 12K (0x3000)
Number of BPI Table Entries...= 24K (0x6000)
Number of Service Flows.......= 64K (0x10000)
Device Status:
--------------
UPX Alarm Status = 0x3FF
UPX Alarm Mask = 0x19000
The following example provides information about all controllers using the show controller
integrated-cable command and the counters keyword:
Router# show controller integrated-Cable card 7/1 counters rf
Tx Tx Tx
7/1/0 0 510617849 1411052 1.411052 45424209 894786143
7/1/0 1 511430476 1415614 1.415614 45424208 894786138
7/1/0 2 510750271 1412707 1.412707 45424208 894786121
7/1/0 3 512009268 1416818 1.416818 45424207 894786108
7/1/1 0 268915155 743427 0.74347 45424206 223046013
7/1/1 1 0 0 0.0 0 0
7/1/1 2 0 0 0.0 0 0
7/1/1 3 0 0 0.0 0 0
7/1/2 0 0 0 0.0 0 0
7/1/2 1 0 0 0.0 0 0
7/1/2 2 0 0 0.0 0 0
7/1/2 3 0 0 0.0 0 0
7/1/3 0 269847377 746886 0.746886 45424206 223769698
7/1/3 1 269850587 746936 0.746936 45424205 223769696
7/1/3 2 269851105 746886 0.746886 45424204 223769690
7/1/3 3 269868256 747036 0.747036 45424199 223769663
7/1/4 0 0 0 0.0 0 0
7/1/4 1 0 0 0.0 0 0
7/1/4 2 0 0 0.0 0 0
7/1/4 3 0 0 0.0 0 0
Table 126 describes the fields shown in the show controller integrated-cable displays.
Field Description
Controller Chan Controller channel number.
RF Packets RF packets.
MPEG bps MPEG value in bps.
MPEG mbps MPEG value in Mbps.
MPEG Packets MPEG packets.
Sync Packets Synchronization packets.
MAP/UCD MAP/ UCD value.
Syntax Description slot/port Identifies the cable interface and downstream port on the
Cisco uBR7100 series and Cisco uBR7200 series routers.
• slot—Slot where the line card resides.
– Cisco uBR7246VXR router: The valid range is from 3 to 6.
– Cisco uBR7225VXR router: The valid range is from 1 to 2.
– Cisco uBR7100 series router: The valid value is 1.
• port—Downstream port number on the line card. The valid port
value is 0 or 1.
slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot—Slot where the line card resides. The valid range is from 5 to
8.
• subslot—Subslot where the line card resides. Available slots are 0
or 1.
• port—Downstream controller number on the line card. Valid port
values are from 0 to 4.
downstream (Optional) Displays the downstream interface status.
upstream (Optional) Displays the upstream interface status.
port (Optional) Specifies the desired upstream port. Valid values start with 0
for the first upstream port on the cable interface line card.
ipc (Optional) Displays the Inter-Process Communication (IPC)
information between different line cards.
mem-stat (Optional) Displays the output from the show memory statistics
command that contains a summary of memory statistics for a Broadband
Processing Engine (BPE) cable interface line card.
memory (Optional) Displays the output from the show memory command that
contains a summary of memory statistics, including the memory as it is
allocated per process, for a BPE cable interface line card.
proc-cpu (Optional) Displays the output from the show processes cpu command
that contains the processor status for a BPE cable interface line card.
Usage Guidelines The mem-stat, memory, and proc-cpu keywords are used to obtain the relevant information from the
onboard processor on BPE cable interface line cards, such as the Cisco uBR-MC16U/X,
Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U/H cards. This allows you to obtain information
that is specific to a line card, as opposed to having to run these commands on the entire router.
The logical-index is shown only when multiple logical channels are configured using the
cable upstream max-logical-chans command.
Note The mem-stat, memory, and proc-cpu options are not available for cable interface line cards that do not
contain an onboard processor (for example, the Cisco uBR-MC16C card).
Examples The following abbreviated example illustrates the initial information for the tech-support keyword for
the Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed:
Router# show controllers c8/1/0 tech-support
Table 127 describes the fields shown in the show controllers cable downstream command display.
Field Description
Cable Slot and port number indicating the location of the Cisco cable
interface line card.
Downstream is up RF downstream interface is enabled.
Frequency Transmission frequency of the RF downstream. (This information
may not match the current transmission frequency, which is external
on CMTS platforms that use an external upconverter.)
Channel Width Width of the RF downstream channel.
QAM Modulation scheme.
Symbol Rate Transmission rate (in number of symbols per second).
FEC ITU-T Motion Picture Experts Group (MPEG) framing standard.
Annex Annex for the RF downstream channel.
R/S Interleave I/J Reed Solomon framing based on ITU S.83-B.
For cable interfaces that include an integrated upconverter, the show controllers cable command
includes the frequency and power settings for the integrated upconverter. The following example shows
a typical output for the show controllers cable command that includes the information for the integrated
upconverter:
ubr7100# show controllers cable 1/0
Interface Cable1/0
Hardware is IMC11
BCM3210 revision=0x56B2
Cable1/0 Upconverter is Enabled Output is Enabled
Model: 74-2094-01 Serial Number: 0WAV04480010 CLEI Code: CLEI#
HW Rev: PC2D0107 SW Rev: 007, NVRAM Rev: 006 ECI number 123456
Downstream Frequency 525.0000 MHz
IF Power 0.3 dBmv RF Power 51.0 dBmv
...
The following is a sample output of the show controllers cable downstream command for a
downstream on the Cisco uBR-MC28U cable interface line card or a cable interface line card with
integrated upconverter:
ubr7246vxr# show controllers cable 6/0 downstream
Interface Cable6/0
Hardware is MC28U (F-connector) with Integrated Up-converter
Primary rommon version is: 11.4
Secondary rommon version is: 6553.5
Current rommon is Primary
Late input drops = 0
Output queue: 0/1000/64/0 (size/max total/threshold/drops)
JIB version 372
H/W Spectrum Management Information:
BCM3138 Chip State: 1 1 1 1, Serial Port State 1, Busy Count: 0 25 0 0
Spectrum Management IPC Statistics:
Tx Statistics
Pkts: 48413, Lock Errs: 0, MB not Empty: 0, No Buffs: 0
Rx Statistics
Pkts: 46097, Timeout: 1, Unexpected: 0, No Buffs: 0, Lock Errs: 0
Inuse band lower=0 upper=0 CNR=56
candidate band lower=0 upper=0 Mod=0
Inuse band lower=0 upper=0 CNR=52
candidate band lower=0 upper=0 Mod=0
Inuse band lower=0 upper=0 CNR=55
candidate band lower=0 upper=0 Mod=0
Inuse band lower=23000 upper=26200 CNR=55
candidate band lower=23000 upper=26200 Mod=0
Cable6/0 Upconverter is Enabled Output is Enabled
Model: 74-2094-05 Serial Number: 0WAV06530029 CLEI Code: FFFFFFFFFF
HW Rev: PC2D0108 SW Rev: 010, NVRAM Rev: 006 ECI number FFFFFF
Downstream Frequency 471.0000 MHz
RF Power 54.9 dBmv
Router#
Table 128 describes the fields related to the integrated upconverter shown in the show controllers cable
downstream command display.
Field Description
Downstream Frequency Center frequency (in MHz) for which the integrated upconverter is
configured.
IF Power Power level (in dBmV) of the signal that the integrated upconverter
is receiving from the cable interface line card in the
Cisco uBR7100 series router.
RF Power Power level (in dBmV) of the RF output signal that the integrated
upconverter is transmitting on the DS0 RF port.
The following is a sample output of the show controllers cable downstream command for the cable
interface on slot 8, subslot 0, and port 0 on a Cisco CMTS router:
ubr10012# show controllers c8/0/0 downstream
Cable8/0/0 Downstream is up
Frequency 453.0000 MHz, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
Downstream channel ID: 191
Dynamic Services Stats:
DSA: 0 REQs 0 RSPs 0 ACKs
0 Successful DSAs 0 DSA Failures
DSC: 0 REQs 0 RSPs 0 ACKs
0 Successful DSCs 0 DSC Failures
DSD: 0 REQs 0 RSPs
0 Successful DSDs 0 DSD Failures
DCC: 0 REQs 0 RSPs 0 ACKs
0 Successful DCCs 0 DCC Failures
DCC end of transaction counts:
DCC unknown cause(0) offline(0) if down(0) no cm(0)
DCC no resource(0) no retries(0) reject(0) unknown state (0)
DCC rebuild err (0) T15 timeout(0) wrong channel(0) reinit MAC (0)
DCC dcc succeeds(0)
DCC wcm(0)
Local total modems 800, modems active 800, total DS flows 801
NB DS Mo3/0/1:0, STATE: UP
Frequency 555.0000 MHz 64-QAM, ANNEX B, R/S Interleave I=32, J=4
Network Delay 550 (usec)
Bandwidth (Kbps): 4315, Load Percent: 0
Channel ID: 48, US MAP: 0x0037
Total modems: 4, modems active : 4, total DS flows: 5
NB DS Mo3/0/1:1, STATE: UP
Frequency 561.0000 MHz 64-QAM, ANNEX B, R/S Interleave I=32, J=4
Network Delay 550 (usec)
Bandwidth (Kbps): 4315, Load Percent: 0
Channel ID: 49, US MAP: 0x0037
Total modems: 2, modems active : 2, total DS flows: 3
NB DS Mo3/0/1:2, STATE: UP
Frequency 567.0000 MHz 64-QAM, ANNEX B, R/S Interleave I=32, J=4
Network Delay 550 (usec)
Bandwidth (Kbps): 4315, Load Percent: 0
Channel ID: 50, US MAP: 0x0037
Total modems: 1, modems active : 1, total DS flows: 2
NB DS Mo3/0/1:3, STATE: UP
Frequency 573.0000 MHz 64-QAM, ANNEX B, R/S Interleave I=32, J=4
Network Delay 550 (usec)
Bandwidth (Kbps): 13485, Load Percent: 0
Channel ID: 51, US MAP: 0x0037
Total modems: 3, modems active : 3, total DS flows: 4
The following is sample output from the show controllers cable upstream command for a Cisco CMTS
router with a cable interface card located in slot 4, port 0:
CMTS01# show controllers cable 4/0 upstream 2
The following example shows a typical output of the show controllers cable upstream command for a
cable interface line card that includes onboard hardware-based spectrum management capabilities:
Router# show controllers cable 3/0 upstream 3
Cable6/0 Upstream 3 is up
Frequency 24.600 MHz, Channel Width 3.200 MHz, 64-QAM Symbol Rate 2.560 Msps
This upstream is mapped to physical port 3
Spectrum Group 14, Last Frequency Hop Data Error: NO(0)
MC28U CNR measurement - better than 50 db
Nominal Input Power Level 0 dBmV, Tx Timing Offset 2815
Ranging Backoff automatic (Start 0, End 3)
Ranging Insertion Interval automatic (60 ms)
Tx Backoff Start 0, Tx Backoff End 4
Modulation Profile Group 241
Concatenation is enabled
Fragmentation is enabled
part_id=0x3138, rev_id=0x02, rev2_id=0x00
nb_agc_thr=0x0000, nb_agc_nom=0x0000
Range Load Reg Size=0x58
Request Load Reg Size=0x0E
Minislot Size in number of Timebase Ticks is = 2
Minislot Size in Symbols = 32
Bandwidth Requests = 0x23C800
Piggyback Requests = 0x489FB8
Invalid BW Requests= 0x0
Minislots Requested= 0x4499EBE
Minislots Granted = 0x6C67B7
Minislot Size in Bytes = 24
Map Advance (Dynamic) : 2454 usecs
UCD Count = 429798
ATDMA mode enabled
Multicast/Broadcast RateLimit Dropped Pkts : 0
The following example shows a typical output of the show controllers cable upstream command for
the Cisco uBR10-MC5X20H cable interface line card that is configured with multiple logical channels:
Router# show controllers cable 7/1/0 upstream 0
Cable7/1/0 Upstream 0 is up
Frequency 30.000 MHz, Channel Width 1.600 MHz, Symbol Rate 1.280 Msps
Modulations - Short QPSK, Long QPSK
This upstream is mapped to physical port 0
Spectrum Group is overridden
US phy MER(SNR)_estimate for good packets - 30.2024 dB
Nominal Input Power Level 3 dBmV, Tx Timing Offset 1419
Ranging Backoff Start 0, Ranging Backoff End 1
US timing offset adjustment type 0, value 0
Ranging Insertion Interval automatic (60 ms)
US throttling off
For Broadband Processing Engine (BPE) cards and other cable interfaces that include onboard
upconverters, the show controllers cable command also displays the upconverter status and
configuration information. The following excerpt from the command output shows the information that
is displayed for the Cisco uBR10-MC5X20S cable interface line card:
Router# show controllers cable 5/1/4
Interface Cable5/1/4
Hardware is MC520S
JIB version 66
Cable5/1/4 Upconverter is Enabled Output is Enabled
Model: 74-2094-04 Serial Number: 0WAV0649000L CLEI Code: FFFFFFFFFF
HW Rev: PC2D0108 SW Rev: 010, NVRAM Rev: 006 ECI number FFFFFF
Downstream Frequency 255.0000 MHz
RF Power 49.8 dBmv
...
Table 129 describes the fields shown in the show controllers cable upstream command display.
Field Description
Cable Slot and port number indicating the location of the Cisco cable
interface line card.
Upstream is up/administratively Administrative state of the upstream (whether it is shutdown or
down not).
Channel Width Width of the RF upstream channel.
QPSK Symbol Rate Modulation technique for upstream transmission.
Spectrum Group 4 Spectrum group associated with this slot and port.
Frequency Transmission frequency of the RF upstream channel.
Note Cisco cable interface line cards always program the
upstream center frequency in 16 KHz increments. This is
the frequency displayed in the router configuration and the
show controllers cable upstream command. For example,
if you use the cable upstream frequency command to
specify a center frequency of 27 MHz, the actual center
frequency will be 27.008 MHz, which is the next highest 16
KHz boundary.
Modulations Spectrum group associated with this slot and port.
Field Description
SNR measurement Estimate for the overall signal-to-noise ratio (SNR) for cable
interfaces that do not include onboard hardware-based spectrum
management. For most cable interface line cards, this value reflects
the modulation error rate (MER) value for the upstream (as
calculated according to the IEEE 802.14 PHY layer specifications).
The MER is sometimes incorrectly referred to as the
carrier-to-noise ratio (CNR), and the SNR value is generally lower
than the CNR value.
Note In Cisco IOS Release 12.1(10)EC1 and Cisco IOS Release
12.2(4)BC1b, the algorithm for calculating the SNR
estimate was refined for a more accurate value. Depending
on the plant characteristics, the new SNR estimate could be
up to 6 dB lower than the values shown in earlier software
releases. This value is only an estimate—for the most
accurate value, use a spectrum analyzer.
<card-name> CNR measurement Estimate for the overall carrier-to-noise ratio (CNR) for the
upstream on cable interfaces that include onboard hardware-based
spectrum management. When the CNR measurement exceeds
40 dB, this line states “better than 40 dB.” As a general rule, the
CNR is greater than the SNR value.
Note This value is only an estimate—for the most accurate
value, use a spectrum analyzer or use the show controllers
cable upstream spectrum command. For individual cable
modems, you can also use the show cable modem cnr
command.
Nominal Input Power level Desired power level coming into the receiver.
Tx Timing Offset Largest ranging offset reported by CMs on the upstream.
Ranging Backoff Start/End Ranging slots (expressed as an exponent of 2) to back off before
resending the ranging bursts after an upstream collision. These
values are configured using the cable upstream range-backoff
start end command.
Ranging Backoff Automatic Start and end ranging backoff exponents, which are set
automatically, using the cable upstream range-backoff
automatic command.
Note These counters are not accurately updated on the
Cisco uBR10-MC5X20S cable interface line card, which
should manually configure the ranging backoff instead.
US timing offset Upstream timing offset adjustment type and value.
Ranging Insertion Interval Ranging insertion interval.
US throttling Status of the upstream throttling.
Tx Backoff Start Starting exponential backoff value for data collisions.
Tx Backoff End Ending exponential backoff value for data collisions.
Modulation Profile Group Set of burst profiles defining an upstream range.
Field Description
part_id= Part number of the PHY chip. FFFF means the PHY chip is turned
off.
rev_id= PHY chip revision number.
rev2_id= PHY chip subrevision number.
nb_agc_thr= Threshold used to control gain.
nb_agc_nom= Accelerate convergence of input power level.
Range Load Reg Size= Size in symbols for range request bursts.
Request Load Reg Size= Size in symbols for request bursts.
Minislot Size in number of Size in tick units of upstream minislot. A tick is 6.25 microseconds.
Timebase Ticks is
Minislot Size in Symbols Size in symbols of the upstream minislot.
Bandwidth Requests Number of successful bandwidth requests received in the
contention minislots.
Piggyback Requests Number of successful bandwidth requests piggybacked with
regular data transmissions.
Invalid BW Requests Number of invalid bandwidth (BW) requests. An example of an
invalid bandwidth request is a modem using a nonexistent service
identifier (SID) to request bandwidth.
Minislots Requested Total number of minislots requested.
Minislots Granted Total number of minislots granted.
Minislot Size in Bytes Size of the minislot in bytes.
Map Advance (Dynamic) Dynamic map advance time.
Map Count Total number of map counts.
Remote Map Counts Total number of remote map counts.
UCD Count Number of Upstream Channel Descriptors (UCDs) sent for this
upstream.
Remote UCD Counts Number of remote UCDs sent for this upstream.
PHY Physical layer information for the following:
• us errors—Number of upstream errors.
• us recoveries—Number of upstream recoveries.
MAC PHY TSS Statistics on the integrity of sync status of timestamp snapshot
values between MAC and PHY.
MAC PHY Status MAC physical status for the following:
• bcm3140 status
• lookout status
MAP/UCD Replication MAP/UCD replication instructions.
Instructions
DES Ctrl Reg # = Interval data encryption standard (DES) controller register dump.
Field Description
Null Modem RateLimit Dropped (Cisco uBR-MC16U/X, Cisco uBR-MC28U/X only) Number of
Pkts packets that were dropped because they had a Service Flow ID
(SFID) of 0, which occurs when the packets are dropped due to
rate-limiting on their original service flow.
Additional Information for Broadband Processing Engine (BPE) Cable Interface Line Cards
JIB Version Revision of the JIB circuitry, which is the custom processor
onboard the BPE cards that handles the MAC-layer processing.
Upconverter is Enabled Status of the upconverter and the signal output. If this field shows
Output is Enabled that the output is disabled, use the no cable downstream
rf-shutdown command to reenable it.
Downstream Frequency Configured frequency, in MHz, for the integrated upconverter (if
present).
RF Power Current RF power, in dBmV, as measured on the cable interface
line card upconverter. The upconverter circuitry is accurate to a few
tenths of a dBmV, but might vary +/- 1 dBmV depending on the
transient noise that occurs when the power is measured.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in the line configuration mode.
Syntax Description slot/port Identifies the cable interface and downstream port on the
Cisco uBR7100 series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On the
Cisco uBR7200 series router, slot can range from 3 to 6, and port can
be 0 or 1, depending on the cable interface.
slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
n Port number for the desired upstream (0 to 5).
ip-address (Optional) IP address, in dotted decimal notation, for a CM on the
specified upstream.
mac-address (Optional) MAC address, in dotted hexadecimal notation, for a CM on
the specified upstream.
start-freq Starting frequency for the frequency range that is being reported
(5 to 42 MHz; can also be specified as 5000 to 42000 KHz or
5000000 to 42000000 Hz).
end-freq Ending frequency for the frequency range that is being reported
(5 to 42 MHz).
Note The ending frequency must be greater than the starting
frequency and must be specified using the same units as the
starting frequency (MHz, KHz, Hz).
res-freq Resolution frequency to determine the number of data points for the
report (12 to 37000 KHz).
Note The resolution frequency must be specified in the same units as
the starting and ending frequency (MHz, KHz, Hz). To use a
resolution value less than 1 MHz, you must specify the other
parameters in either Hz or KHz.
Usage Guidelines Cisco IOS Release 12.3(9a)BC adds the tech-support keyword to the show controllers cable command.
This change allows users with large numbers of online cable modems to collect the necessary line card
information without consuming the console session for a long period of time.
Additional and related improvements are also available for the show cable tech-support command.
For all supported releases, the show controllers cable upstream spectrum command displays the
power in dBmV for a given frequency range for the specified upstream. The frequency range can cover
any portion of the DOCSIS upstream frequency range (5 to 42 MHz), and the frequency range can be
divided into a resolution as small as 12 KHz.
If a CM is specified by its IP address or MAC address, the power information for that particular CM is
given. If no IP or MAC address is given, the command displays the background noise for the entire
upstream. All displays use historical averaging of data collected at the time the command is used;
historical information is not saved.
Note Cisco cable interface line cards always program the upstream’s center frequency in 16-KHz increments,
and this is the frequency displayed by the show controller cable upstream command. For example, if
you use the cable upstream frequency command to specify a center frequency of 27 MHz (cable
upstream x frequency 27000000), the actual center frequency will be 27.008 MHz, which is the
next-highest 16-KHz boundary.
Tip By default, the show controller cable upstream command displays its output to the router’s console
port. To display the command’s output when logged in during a Telnet session over an Ethernet port, use
the terminal monitor command before giving the show controller cable upstream command.
Examples The following example shows the show controllers cable upstream command displaying the power
information for a particular CM on upstream 5 of cable interface slot 3/0. The power information is
displayed over the entire upstream (5–42 MHz), with a resolution of 5 MHz:
Router# show cable modem
MAC Address IP Address I/F MAC Prim RxPwr Timing Num BPI
State Sid (db) Offset CPEs Enbld
...
00d0.ba77.7595 10.20.114.34 C3/0/U5 online 1 0.25 2740 1 yes
00d0.ba77.7621 10.20.114.17 C3/0/U5 online 2 0.25 2740 2 yes
00d0.ba77.7533 10.20.114.55 C3/0/U5 online 3 0.25 2740 1 yes
...
Note The output for each frequency range includes a time-stamp, the ending frequency for each range
(in KHz), the historical average power level for that range (in dBmV), and a series of asterisks that
provides a graphical representation of the noise floor level for the signal (a stronger signal is indicated
by more asterisks).
The following example shows a partial display of the background noise data for upstream 4 of cable
interface slot 6/0. The command covers the entire upstream spectrum (5–42 MHz) at the minimum
resolution of 12 KHz.
Router# show controller cable 6/0 upstream 4 spectrum 5000 42000 12
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines The show controllers cable-modem display begins with information from the first few registers of the
Broadcom BCM3300 chip. Next is buffer information for the receive, receive MAC message, buffer
descriptor, and packet descriptor rings. Then comes MIB statistics from the BCM3300 chip, DMA base
registers to indicate where the rings start, global control and status information, and finally interrupts for
the interrupt code.
When using this command, be sure to check the tx_count and the tx_head and tx_tail values for the buffer
descriptor (TX BD) and packet descriptor (TX PD) rings. The tx_count should be greater than 0, and the
tx_head and tx_tail values should not be equal. If these values do not change for several minutes, it could
indicate that there are packets stuck on the ring. This condition is often caused by the CMTS not giving
grants.
Examples The following shows typical output for the show controllers cable-modem command:
Router# show controllers cable-modem 0
BCM Cable interface 0:
BCM3300 unit 0, idb 0x200EB4, ds 0x82D4748, regaddr = 0x800000, reset_mask 0x80
station address 0010.7b43.aa01 default station address 0010.7b43.aa01
PLD VERSION: 32
Tuner: status=0x00
Rx: tuner_freq 699000000, symbol_rate 5055849, local_freq 11520000
snr_estimate 33406, ber_estimate 0, lock_threshold 26000
QAM in lock, FEC in lock, qam_mode QAM_64
Tx: tx_freq 20000000, power_level 0x3E, symbol_rate 1280000
ehdr: 01 06 02 74 34 11
07 status=0x20 bd_index=0x0007 len=0x0000 hdr_len=0x0000
ehdr: 01 06 02 74 34 11
MIB Statistics
DS fifo full = 0, Rerequests = 0
DS mac msg overruns = 0, DS data overruns = 0
Qualified maps = 348, Qualified syncs = 73
CRC fails = 0, HDR chk fails = 0
Data pdus = 0, Mac msgs = 423
Valid hdrs = 423
BCM3300 Registers:
downstream dma:
ds_data_bd_base=0x001D40, ds_mac_bd_base=0x001E80
ds_data_dma_ctrl=0x98, ds_mac_dma_ctrl=0xD8
ds_dma_data_index=0x0007, ds_dma_msg_index=0x0000
upstream dma:
us_bd_base=0x001FB8, us_pd_base=0x002038
us_dma_ctrl=0x80, us_dma_tx_start=0x00
Global control and status:
global_ctrl_status=0x00
interrupts:
irq_pend=0x0008, irq_mask=0x00F7
Router#
The following shows an excerpt from the display for the all option:
Router# show controllers cable-modem 0 all
BCM MAC/PHY: Chip id = BCM3300 Revision A (1)
...
Tuner: status=0x00
Rx: tuner_freq 645000000, symbol_rate 5056000, local_freq 11520000
snr_estimate 345(TenthdB), ber_estimate 0, lock_threshold 23000
QAM in lock, FEC in lock, qam_mode QAM_64 (Annex B)
Tx: tx_freq 27984000, symbol rate 16 (2560000 sym/sec)
power_level: 29.75 dBmV (current)
30 (gain in US AMP units)
5 (BCM3300 attenuation in .4 dB units)
IF AGC=0x2010 (8208) RF AGC=0x3753 (14163)
Combined AGC = 22371 (band = 1)
Router#
Note The show controllers cable-modem 0 all command displays extensive information about the current
state of the modem and its MAC-layer and PHY-layer registers and buffers. You need to open a capture
buffer on your terminal or Telnet software to log this information before you give this command.
Table 130 describes the significant fields shown by the show controllers cable-modem command. For
more information, see the Broadcom documentation for the BCM3300 chip.
Field Description
BCM3300 unit Unit number of this BCM3300 chip.
idb Interface description block number.
ds Downstream channel.
regaddr Indicates the start of the BCM3300 registers.
reset_mask Indicates the bit to hit when resetting the chip.
station address MAC address of this router’s cable interface.
default station address Default MAC address assigned by the factory for this router.
PLD VERSION PLD version of the BCM3300 chip.
MAC State Current MAC state of the router.
Prev States Number of states that have previously existed since initialization.
MAC mcfilter MAC control filter for MAC messages.
data mcfilter MAC control filter for data.
DS Downstream Broadcom receiver chip number and ID.
US Upstream Broadcom transmitter chip number and ID.
Tuner: status Current status of the tuner.
Rx: tuner_freq Downstream frequency (in Hz) that the router searched for and found.
symbol_rate Downstream frequency in symbols per second.
local_freq Frequency on which the transmitter and the tuner communicate.
snr_estimate Estimate of signal-to-noise ratio (SNR) in dB multiplied by 1000.
ber_estimate Estimate of bit error rate (always 0).
lock_threshold Minimum signal-to-noise ratio (SNR) that the router will accept as a valid
lock.
qam_mode The modulation scheme used in the downstream direction.
Tx: tx_freq Upstream frequency sent to the router by the CMTS in the UCD message.
power_level Transmit power level as set in the hardware, expressed as a hexadecimal
value. The units are unique to the hardware used. Use the show controllers
cable-modem mac state command to see the power level in dBmV.
symbol_rate Upstream frequency in symbols per second.
TFTP server IP address of the TFTP server at the CMTS.
TOD server IP address of the time-of-day server at the CMTS.
Security server IP address of the security server at the CMTS.
Field Description
Timezone Offset Correction received from the DHCP server to synchronize the router time
clock with the CMTS.
Config filename Name of the file stored on the cable company’s TFTP server that contains
operational parameters for the router.
buffer size Size in bytes of the BCM3300 message buffers.
RX data PDU ring: Indicates the memory location of the beginning of buffer information for the
receive data ring.
rx_head Indicates current head buffer descriptor.
rx_p Indicates current head packet descriptor.
RX MAC message ring: Indicates the memory location of the beginning of buffer information for the
receive MAC message ring.
rx_head_mac Indicates current head buffer descriptor.
rx_p_mac Indicates current head packet descriptor.
TX BD ring: Indicates the memory location of the beginning of buffer information for the
transmit buffer descriptor ring.
tx_count If tx_count is 0, or if tx_head and tx_tail are equal and there is no change for
a period of time, it means there are packets stuck on the ring. This condition
may be caused by the CMTS not giving grants.
tx_head Indicates current head transmit packet descriptor.
head_txp The next packet descriptor to get used, along with its index.When head_txp
and tail_txp are the same, the transmit queue is empty.
tx_tail Indicates current tail transmit packet descriptor.
tail_txp The next packet descriptor to get sent, along with its index. When head_txp
and tail_txp are the same, the transmit queue is empty.
TX PD ring: Indicates the memory location of the beginning of buffer information for the
transmit packet descriptor ring.
tx_head_pd Indicates current head packet descriptor.
tx_tail_pd Indicates current tail packet descriptor.
ehdr Extended MCNS header.
MIB Statistics
DS fifo full Number of times the downstream input first-in first-out (FIFO) buffer
became full on the router.
rerequests Number of times a bandwidth request generated by the router was not
responded to by the CMTS.
DS mac msg overruns Number of times the router’s DMA controller had a downstream MAC
message and there were no free MAC message buffer descriptors to accept
the message.
DS data overruns Number of times the router’s DMA controller had downstream data and there
were no free data PDU buffer descriptors to accept the data.
Qualified maps Number of times a MAP message passed all filtering requirements and was
received by the router.
Field Description
Qualified syncs Number of times a timestamp message was received by the router.
CRC fails Number of times a MAC message failed a cyclic redundancy check (CRC).
HDR chk fails Number of times a MAC header failed its 16-bit CRC check. The MAC
header CRC is a 16-bit Header Check Sequence (HCS) field that ensures the
integrity of the MAC header even in a collision environment.
Data pdus Total number of data protocol data units (PDUs) of all types received by the
router.
Mac msgs Number of MAC messages received by the router.
Valid hdrs Number of valid headers received by the router, including PDU headers,
MAC headers, and headers only.
Global control and Used to reset the BCM3300 chip.
status:
interrupts: Hexadecimal values of the pending IRQ interrupt and IRQ mask.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR904, Cisco uBR905, Cisco uBR924, and Cisco uBR925 cable access routers, and Cisco CVA122 Cable
Voice Adapter
Usage Guidelines Baseline privacy key management exchanges take place only when both the router and the CMTS are
running code images that support Baseline Privacy Interface (BPI) or BPI Plus (BPI+) encryption, and
the privacy class of service is enabled via the configuration file that is downloaded to the router. Baseline
privacy code images for the router contain k1, k8, or k9 in the code image name.
Examples The following shows typical output for the show controllers cable-modem bpkm command for
DOCSIS 1.0 BPI operation when the CMTS does not have baseline privacy enabled:
Router# show controllers cable-modem 0 bpkm
Field Description
authorization wait time The number of seconds the router waits for a reply after sending the
Authorization Request message to the CMTS.
reauthorization wait The number of seconds the router waits for a reply after it has sent an
time Authorization Request message to the CMTS in response to a
reauthorization request or an Authorization Invalid message from the CMTS.
authorization grace time The number of seconds before the current authorization is set to expire that
the grace timer begins, signaling the router to begin the reauthorization
process.
operational wait time The number of seconds the Traffic Exchange Key (TEK) state machine waits
for a reply from the CMTS after sending its initial Key Request for its SID’s
keying material.
rekey wait time The number of seconds the TEK state machine waits for a replacement key
for this Service ID (SID) after the TEK grace timer has expired and the
request for a replacement key has been made.
tek grace time The number of seconds before the current TEK is set to expire that the TEK
grace timer begins, signaling the TEK state machine to request a replacement
key.
authorization rej wait Number of seconds the router waits before sending another Authorization
time Request message to the CMTS after it has received an Authorization Reject
message.
kek state The current state of the key encryption key that the CMTS uses to encrypt
the traffic encryption keys it sends to the router. See Table 133 for the
possible values.
tek state The current state of the traffic encryption key state machine for the specified
SID. See Table 133 for the possible values.
The following shows typical output for the show controllers cable-modem bpkm command for
DOCSIS 1.1 BPI+ operation when baseline privacy is enabled:
Router# show controllers cable-modem 0 bpkm
Router#
Table 132 describes the fields shown in the display for BPI+ operation.
Field Description
Privacy Version Whether BPI or BPI+ is being run.
public key The Diffie-Hellman public key that the router uses to establish a BPI+
session with the CMTS.
keks The odd and even values for the key encryption key (KEK).
hmac upstream keys The odd and even values for the hash message authentication code (HMAC)
key used in upstream key requests.
hmac downstream keys The odd and even values for the HMAC message authentication key used in
downstream key replies, key rejects, and invalid TEK messages.
authorization wait time The number of seconds the router waits for a reply after sending the
Authorization Request message to the CMTS.
reauthorization wait The number of seconds the router waits for a reply after it has sent an
time Authorization Request message to the CMTS in response to a
reauthorization request or an Authorization Invalid message from the CMTS.
authorization grace time The number of seconds before the current authorization is set to expire that
the grace timer begins, signaling the router to begin the reauthorization
process.
operational wait time The number of seconds the TEK state machine waits for a reply from the
CMTS after sending its initial Key Request for its SID’s keying material.
rekey wait time The number of seconds the TEK state machine waits for a replacement key
for this SID after the TEK grace timer has expired and the request for a
replacement key has been made.
Table 132 show controllers cable-modem bpkm Field Descriptions (BPI+) (continued)
Field Description
tek grace time The number of seconds before the current TEK is set to expire that the TEK
grace timer begins, signaling the TEK state machine to request a replacement
key.
authorization rej wait Number of seconds the router waits before sending another Authorization
time Request message to the CMTS after it has received an Authorization Reject
message.
sa map wait time Number of seconds the router waits for a response after sending a Security
Association (SA) map request before timing out and resending the request.
sa map retries Number of times the router attempts an SA map request before it rejects the
attempt to create a new downstream service flow.
kek state The current state of the key encryption key that the CMTS uses to encrypt
the traffic encryption keys it sends to the router. See Table 133 for the
possible values.
tek state The current state of the traffic encryption key state machine for the specified
SID. See Table 133 for the possible values.
Table 133 describes the valid values for the kek state and tek state fields:
Table 133 State Values for KEK and TEK State Fields
State Description
Key Encryption Key (KEK) States
STATE_A_START The router is still completing the DOCSIS provisioning
process. If this state persists, it indicates that BPI/BPI+
encryption was not enabled for the router in its DOCSIS
configuration file.
STATE_B_AUTH_WAIT DOCSIS provisioning has been completed, and the router has
sent an authorization request to the CMTS and is waiting for a
reply. If this state persists, it indicates that the CMTS has not
enabled BPI/BPI+ operations.
STATE_C_AUTHORIZED The router has received a valid authorized reply from the
CMTS, completing the KEK exchange, and allowing the TEK
exchange to begin.
STATE_D_REAUTH_WAIT The router sent a reauthorization request and is waiting for the
reply from the CMTS. A reauthorization request can be sent if
the initial request is rejected, or when existing keys have
expired and must be reacquired.
STATE_E_AUTH_REJ_WAIT The router has received a nonpermanent authorization reject
response from the CMTS and is waiting for the timeout period
before sending another request.
STATE_F_SILENT The router has received a permanent authorization reject
response from the CMTS and has been placed in silent mode,
in which it does not pass traffic but does accept SNMP
management requests. (Valid only for BPI+ operations.)
Table 133 State Values for KEK and TEK State Fields (continued)
State Description
Traffic Encryption Key (TEK) States
STATE_A_START The router is still completing the DOCSIS provisioning
process, or is still performing the KEK key exchange. If this
state persists, it indicates that KEK authorization failed, or that
BPI/BPI+ encryption was not enabled for the router in its
DOCSIS configuration file.
STATE_B_OP_WAIT The router has successfully completed the KEK key exchange,
has sent a key request to the CMTS, and is waiting for a reply.
STATE_C_OP_REAUTH_WAIT The router has sent a reauthorization request and is waiting for
a reply, or the TEK key has been declared invalid. BPI/BPI+
encryption has not yet begun. If this state persists, it indicates
that the TEK key exchange has failed.
STATE_D_OPERATIONAL The router has completed the TEK key exchange, and BPI or
BPI+ encryption is operational between the router and the
CMTS.
STATE_E_REKEY_WAIT The existing TEK keys have expired, and the router has
requested a key update from the CMTS.
STATE_F_REKEY_REAUTH_WAIT The router has requested a key update from the CMTS and is
waiting for a reply. BPI/BPI+ encryption can continue using
the existing keys until they expire.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR905 and uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the classifiers that are currently defined for both the upstream and downstream.
The information shown corresponds to the Quality of Service classifier parameters that are listed in
Appendix C of the DOCSIS 1.1 specification.
Examples The following example shows typical output for both upstream and downstream classifiers on the show
controllers cable-modem classifiers command:
Router# show controllers cable-modem 0 classifiers
IP classifiers
Tos: 0x1 0x3 0xFF
Protocol: 258
Source Address: 0.0.0.0
Source Mask: 255.255.255.255
Destination Address: 0.0.0.0
Destination Mask: 255.255.255.255
Source Port Start: 0
Source Port End: 65535
Destination Port Start: 0
Destination Port End: 65535
LLC Classifiers
Source MAC address: 0:0:0:0:0:0
Ether Type: 0x0 0x0 0x0
IP classifiers
Tos: 0x5 0x5 0xD
Protocol: 258
Source Address: 0.0.0.0
Source Mask: 255.255.255.255
Destination Address: 0.0.0.0
Destination Mask: 255.255.255.255
Source Port Start: 0
Source Port End: 65535
LLC Classifiers
Destination MAC address: 0:0:0:0:0:0:0:0:0:0:0:0
Source MAC address: 0:0:0:0:0:0
Ether Type: 0x0 0x0 0x0
IP classifiers
Tos: 0x8 0xFF 0xF8
Protocol: 258
Source Address: 0.0.0.0
Source Mask: 255.255.255.255
Destination Address: 0.0.0.0
Destination Mask: 255.255.255.255
Source Port Start: 0
Source Port End: 65535
Destination Port Start: 0
Destination Port End: 65535
LLC Classifiers
Destination MAC address: 0:0:0:0:0:0:0:0:0:0:0:0
Source MAC address: 0:0:0:0:0:0
Ether Type: 0x0 0x0 0x0
Router#
The following shows the typical display for the summary option:
Router# show controllers cable-modem 0 classifiers summary
Router#
The following shows the detailed information that is displayed for a specific classifier:
Router# show controllers cable-modem 0 classifiers 4
Field Description
Classifier Reference, The reference ID to uniquely identify the classifier in the DOCSIS
Classifier Ref configuration file and MAC management messages.
Classfier ID The ID used to uniquely identify the classifier in each service flow.
Service Flow Reference, The reference ID that uniquely identifies the service flow.
SF Ref
Service Flow ID, SFID The ID that uniquely identifies the service flow.
Rule Priority The priority assigned to the classifier, 0 to 255, with a higher value
indicating a higher priority.
Activation State, State Whether the classifier is activate (1) or inactive (0).
Dynsrv Change Action The action taken for this classifier in dynamic service change messages:
• 0 = Add the classifier.
• 1 = Replace the classifier.
• 2 = Delete the classifier.
SID The service ID (SID) associated with this classifier.
IP Classifiers
ToS The matching Type of Service (Tos) low byte, high byte, and masking
value.
Protocol The matching IP protocol type, as given in RFC 1700. A value of 256
matches any IP protocol, and a value of 257 matches TCP and UDP traffic.
Source Address and The matching IP source address, where the source address is ANDed with
Source Mask the source mask to specify the valid range of source addresses.
Destination Address and The matching IP destination address, where the destination address is
Destination Mask ANDed with the destination mask to specify the valid range of destination
addresses.
Source Port Start and The low end and high end matching source TCP/UDP port values.
Source Port End
Destination Port Start The low end and high end matching destination TCP/UDP port values.
and Destination Port End
LLC Classifiers
Destination MAC The six-byte matching MAC destination address and six-byte mask. The
address first six bytes (address) are ANDed with the last six bytes (mask) to
specify the valid range of MAC destination addresses.
Field Description
Source MAC address The six-byte matching MAC source address.
Ether Type The one-byte Ethernet protocol type and two-byte matching layer 3
protocol ID in the Ether frame. The first byte can have the following
values, which control the meaning of the following two bytes:
• 0x00 = no matching Ethernet protocol is required.
• 0x01 = Ethertype DIX or SNAP frames that match the two-byte packet
type.
• 0x02 = non-SNAP IEEE 802.2 encapsulation frames that match the
eight-bit packet type.
• 0x03 = MAC Management Messages with a type field between the two
bytes, except that RNG_RSP, REG_REQ, REG_RSP, and REG_ACK
frames are always matched.
• 0x04 = matches all data PDU packets, regardless of the two-byte
protocol ID.
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the router’s X.509 DOCSIS cable-modem certificate, which uniquely identifies
the router during the BPI+ negotiation process. This command shows the individual X.509 components
of the certificate, starting with the DOCSIS restricted X.501 Distinguished Name and ending with the
1024-bit public key.
Tip This command displays the certificate that is burned into the router at the factory and is not normally
changed. The show controllers cable-modem manuf-cert command displays the manufacturer’s
certificate that is incorporated into the Cisco IOS image that the router is currently running. Upgrading
the Cisco IOS image could also update the manufacturer’s certificate.
Examples The following example shows the starting lines and ending lines of typical output for the show
controllers cable-modem cmcert command:
Router# show controllers cable-modem 0 cmcert
OID(3):Country 2.5.4.6
1w3d: PRT(2):US
END
END
SET(22)
SEQ(20)
OID(3):Organization 2.5.4.10
1w3d: PRT(13):Cisco Systems
END
END
SET(15)
SEQ(13)
OID(3):Organization Unit 2.5.4.11
1w3d: PRT(6):DOCSIS
END
END
SET(58)
SEQ(56)
OID(3):Common Name 2.5.4.3
1w3d: PRT(49):Cisco Cable Modem Root Certificate Authority R
END
END
...
1w3d: C7 9A A8 5C BD F3 30 5A E5 B6 66 1F 1E 3A C9 2E
1w3d: 04 5D B5 57 3E 75 ED A3 0A AB B6 5D 73 87 E9 BE
1w3d: ED 1A 68 7B B3 08 DA 0F E9 AA 05 28 E2 61 1B 3D
1w3d: END
Router#
Note You must manually enter a return to redisplay the router prompt after the certificate has been displayed.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Examples The following shows typical output for the show controllers cable-modem crypto des command.
Router# show controllers cable-modem 0 crypto des
downstream des:
ds_des_key_table:
key 0: even 0, odd 0
key 1: even 0, odd 0
key 2: even 0, odd 0
key 3: even 0, odd 0
ds_des_cbc_iv_table:
iv 0: even 0, odd 0
iv 1: even 0, odd 0
iv 2: even 0, odd 0
iv 3: even 0, odd 0
ds_des_sid_table:
sid_1=0x0000, sid_2=0x0000, sid_3=0x0000, sid_4=0x0000
ds_des_sid_enable=0x80, ds_des_ctrl=0x2E
ds_des_sv=0x0F00
ds_unencrypted_length=0x0C
upstream des:
us_des_key_table:
key 0: even 0, odd 0
key 1: even 0, odd 0
key 2: even 0, odd 0
key 3: even 0, odd 0
us_des_cbc_iv_table:
iv 0: even 0, odd 0
iv 1: even 0, odd 0
iv 2: even 0, odd 0
iv 3: even 0, odd 0
pb_req_bytes_to_minislots=0x10
us_des_ctrl=0x00, us_des_sid_1= 0x1234
ds_unencrypted_length=0x0C
Router#
Table 135 describes the significant fields shown in the display. For more information, see the Broadcom
documentation for the BCM3300 chip.
Field Description
ds_des_key_table Displays a table showing the downstream DES keys.
ds_des_cbc_iv_table Displays a table showing the downstream DES Cipher Block Chaining
(CBC) mode information.
ds_des_sid_table Displays a table showing the SID values to be enabled for DES encryption.
ds_des_sid_enable Identifies which SID entries in the SID table are enabled for encryption. In
the above example, none of the entries are enabled for encryption.
ds_des_ctrl Control register that identifies the operating mode of the downstream DES
engine.
ds_des_sv Displays the DES security version register; the range of the version field in
the Baseline Privacy Interface (BPI) extended headers that will be accepted
by the hardware. High byte is upper limit, low byte is lower limit. The router
will accept versions 0 to 15.
ds_unencrypted_length Specifies the number of bytes that will be unencrypted at the beginning of
the MAC frame. 0x0C means the first 12 bytes are not encrypted, which is
what the DOCSIS Baseline Privacy specification calls for.
us_des_key_table Displays a table showing upstream DES keys.
us_des_cbc_iv_table Displays a table of upstream DES CBC mode information.
us_des_ctrl Control register that controls the operating mode of the upstream DES
engine. The value 0x24 means that the upstream is configured to enable
decryption and to use CBC mode.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
show controllers cable-modem Displays the mini-slot lookup table for the cable interface.
lookup-table
show controllers cable-modem Displays detailed MAC-layer information for the cable interface.
mac
show controllers cable-modem Displays the contents of the registers used in the downstream
phy physical hardware for the cable interface.
show controllers cable-modem Displays the settings for the upstream and downstream tuners used
tuner by the cable interface.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines Some of the filtering parameters are MAC hardware addresses, Service IDs (SIDs), and upstream
channel IDs.
Examples The following shows typical MAC and SID filter information displayed by the show controllers
cable-modem filters command:
Router# show controllers cable-modem 0 filters
burst_maps:
map[0]=0 map[1]=0 map[2]=0 map[3]=0
bytes_per_minislot_exp=0x04
us_map_parser_minislot_adv=0x03, ticks_per_minislot=0x08, maint_xmit=0x0001
us_sid_table:
sid_1=0x0000, sid_2=0x0000, sid_3=0x0000, sid_4=0x0000
max_re_req=0x0010, rang_fifo=0x00
Router#
Table 136 describes the fields shown in the display. For more information, see the Broadcom
documentation for the BCM3300 chip.
Field Description
ds_mac_da_filters MAC address of the cable interface and the MAC address of any Ethernet
MAC it is bridging.
ds_mac_da_filter_ctrl Downstream MAC filter control for data.
ds_mac_msg_sof Downstream MAC message start of frame.
ds_mac_da_mc Downstream MAC control filter for data.
map_parser_sids Service IDs used for upstream bandwidth allocation.
ds_mac_filter_ctrl Downstream MAC filter control for MAC messages.
us_channel_id Upstream channel ID.
ds_pid Downstream packet ID.
mac_msg_proto_ver Version of the MAC management protocol in use.
reg_rang_req_sid Service ID (SID) field of the ranging request message.
ds_data_da_filter_table Downstream data processing filter table.
ds_data_da_filter_ctrl Downstream data processing filter control.
ds_pdu_sof Downstream PDU start of frame.
ds_data_da_mc Downstream data processing MAC control.
us_ctrl_status Upstream control status.
Minislots per request Length of each registration request in mini-slots.
burst_maps Maps the burst profiles saved in the BCM3037 registers to interval usage
codes (IUCs).
bytes_per_minislot_exp Number of bytes per expansion mini-slot.
ticks_per_minislot Number of time ticks (6.25-microsecond intervals) in each upstream
mini-slot.
maint_xmit Number of initial maintenance transmit opportunities.
us_sid_table Upstream service ID table.
max_re_req Maximum number of registration re-requests allowed.
rang_fifo Number of ranging requests that can be held in the first-in-first-out (FIFO)
buffer.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the details of the lookup table. The driver uses this table to convert the size of
the packets that the router wants to transmit into a bandwidth request to the CMTS in mini-slots. The
contents of this table are affected by the upstream symbol rate that is negotiated between the CMTS and
the cable access router.
Use this table to look up the packet size and determine how many mini-slots will be needed.
Examples The following shows a typical mini-slot lookup table as displayed by the show controllers
cable-modem lookup-table command:
Router# show controllers cable-modem 0 lookup-table
000: 01 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
010: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
020: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
030: 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06 06
040: 06 06 06 06 06 06 06 06 06 06 06 06 10 10 10 10
050: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
060: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
070: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
080: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
090: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0A0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0B0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0C0: 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10 10
0D0: 10 10 10 10 10 10 10 10 10 10 10 10 10 1F 1F 1F
0E0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
0F0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
100: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
110: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
120: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
130: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
140: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
150: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
160: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
170: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
180: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
190: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
1A0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F 1F
1B0: 1F 1F 1F 1F 1F 1F 1F 1F 1F 2D 2D 2D 2D 2D 2D 2D
1C0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1D0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1E0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
1F0: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
200: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
210: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
220: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
230: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
240: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
250: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
260: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
270: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
280: 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D 2D
290: 2D 2D 2D 2D 2D 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2A0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2B0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2C0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2D0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2E0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
2F0: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
300: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
310: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
320: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
330: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
340: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
350: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
360: 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C 3C
370: 3C 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
380: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
390: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3A0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3B0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3C0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3D0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3E0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
3F0: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
400: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
410: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
420: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
430: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B
440: 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 4B 5A 5A 5A
450: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
460: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
470: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
480: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
490: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4A0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4B0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4C0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4D0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4E0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
4F0: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
500: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
510: 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A 5A
520: 5A 5A 5A 5A 5A 5A 5A 5A 5A 68 68 68 68 68 68 68
530: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
540: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
550: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
560: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
570: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
580: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
590: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5A0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5B0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5C0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5D0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5E0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
5F0: 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68 68
600: 68 68 68 68 68 77 77 77 77 77 77 77 77 77 77 77
610: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
620: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
630: 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77 77
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
show controllers cable-modem number mac {errors | hardware | log | resets | state}
Usage Guidelines MAC log messages are written to a circular log file even when debugging is not turned on. These
messages include timestamps, events, and information pertinent to these events. Use the show
controllers cable-modem mac log command to view MAC log messages.
If the router interface fails to come up or resets periodically, the MAC log will capture what happened.
For example, if an address is not obtained from the DHCP server, an error is logged, initialization starts
over, and the router scans for a downstream frequency.
The most useful keywords for troubleshooting a router are log, errors, and resets. See the following
examples for typical outputs for these options.
Examples The following shows a typical display of the MAC log file for a cable interface that has successfully
registered with the CMTS:
Router# show controllers cable-modem 0 mac log
The following example gives the typical error messages that appear in the MAC log when the DHCP
server cannot not be reached:
Router# show controllers cable-modem 0 mac log
Router#
In this situation, use the MAC error display also contains information indicating that the DHCP server
could not be reached:
Router# show controllers cable-modem 0 mac errors
The following is a typical display of the MAC error log information, which is the same information that
is also available using SNMP:
Router# show controllers cable-modem 0 mac errors
This output indicates that the router acquired a downstream lock, successfully read a UCD, and
successfully read a MAP. However, it was unable to communicate with the CMTS after ranging through
all upstream transmit power levels. The router will try to communicate with the CMTS 16 times, and if
cannot receive a response from the CMTS, it will reset the cable interface to try to find a better
downstream frequency.
The show controllers cable-modem 0 mac resets command shows only the entries in the MAC log that
begin with the field CMAC_LOG_RESET. These fields provide you with a summary of the most recent reasons
why the cable interface was reset.
Reset messages and brief explanations are included in the following examples. However, the reset
messages do not commonly occur.
The following example shows the errors that are logged when the configuration file downloaded from
the TFTP server could not be read, typically because the file might not exist, or because the file might
have incorrect permissions.
Router# show controllers cable-modem 0 mac resets
62526.114 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62564.368 CMAC_LOG_RESET_T4_EXPIRED
62677.178 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62717.462 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62757.746 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62796.000 CMAC_LOG_RESET_T4_EXPIRED
62908.808 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62949.092 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
62989.380 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63029.662 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63069.944 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63110.228 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
63148.484 CMAC_LOG_RESET_T4_EXPIRED
63261.296 CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED
Router#
The following example shows that the DHCP server could not be reached, or that it took too long to
respond.
Router# show controllers cable-modem 0 mac resets
497989.804 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
498024.046 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
498058.284 CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED
Router#
The following example indicates that an event in the cable interface driver caused the interface to reset.
This often occurs because a shutdown command was just issued on the interface.
Router# show controllers cable-modem 0 mac resets
527986.444 CMAC_LOG_RESET_FROM_DRIVER
528302.042 CMAC_LOG_RESET_FROM_DRIVER
528346.600 CMAC_LOG_RESET_FROM_DRIVER
528444.494 CMAC_LOG_RESET_FROM_DRIVER
Router#
Table 137 describes the status messages that can appear in the show controllers cable-modem mac
resets command.
Message Description
CMAC_LOG_RESET_CONFIG_FILE_PARSE_FAILED The format of the DOCSIS configuration file acquired from the
TFTP server is not acceptable.
CMAC_LOG_RESET_LOSS_OF_SYNC Synchronization with the CMTS has been lost (SYNC messages are
not being received).
CMAC_LOG_RESET_T4_EXPIRED The maintenance ranging opportunities for this router are not being
received from the CMTS.
CMAC_LOG_RESET_DHCP_WATCHDOG_EXPIRED The DHCP server took too long to respond.
CMAC_LOG_RESET_TOD_WATCHDOG_EXPIRED The Time-of-Day (ToD) server took too long to respond.
CMAC_LOG_RESET_PRIVACY_WATCHDOG_EXPIRED The baseline privacy exchange with the CMTS took too long.
CMAC_LOG_RESET_CHANGE_US_WATCHDOG_EXPIRED The router was unable to transmit a response to a UCC-REQ
message.
CMAC_LOG_RESET_SECURITY_WATCHDOG_EXPIRED A “full security” exchange with the CMTS took too long.
CMAC_LOG_RESET_CONFIG_FILE_WATCHDOG_EXPIRED The TFTP server took too long to respond.
CMAC_LOG_RESET_ALL_FREQUENCIES_SEARCHED All downstream frequencies to be searched have been searched.
Note This message indicates that downstream frequencies were
found, but the router failed to acquire a downstream lock.
CMAC_LOG_RESET_T2_EXPIRED Initial ranging opportunities are not being received.
Table 137 show controllers cable-modem mac resets Field Descriptions (continued)
Message Description
CMAC_LOG_RESET_T3_RETRIES_EXHAUSTED The CMTS failed too many times to respond to a RNG-REQ
message.
Note After 16 T3 timeouts, the router will reset the cable
interface.
CMAC_LOG_RESET_RANGING_ABORTED The CMTS commanded the router to abort the ranging process.
CMAC_LOG_RESET_NO_MEMORY The router has run out of memory.
CMAC_LOG_RESET_CANT_START_PROCESS The router was unable to start an internal process necessary to
complete ranging and registration.
CMAC_LOG_RESET_CONFIG_FILE_READ_FAILED The reading of the configuration file from the TFTP server failed.
Note The file might not exist, or it might have incorrect
permissions.
CMAC_LOG_RESET_AUTHENTICATION_FAILURE The router failed authentication as indicated in a REG-RSP message
from the CMTS.
CMAC_LOG_RESET_SERVICE_NOT_AVAILABLE The CMTS has failed the router’s registration because a required or
requested class of service is not available.
CMAC_LOG_RESET_T6_RETRIES_EXHAUSTED The CMTS failed too many times to respond to a REG-REQ
message.
CMAC_LOG_RESET_MAINTENANCE_WATCHDOG_DRIVER The router MAC layer failed to detect a change in the interface
driver.
CMAC_LOG_RESET_NET_ACCESS_MISSING The Network Access parameter is missing from the DOCSIS
configuration file.
CMAC_LOG_RESET_FAILED_WRITE_ACCESS_CONTROL The router was unable to set the Write Access Control for an SNMP
parameter as specified by the DOCSIS configuration file.
CMAC_LOG_RESET_DHCP_FAILED The DHCP server did not respond with all the required values. The
required values are: IP address, network mask, TFTP server IP
address, TOD server IP address, DOCSIS configuration file name,
and time zone offset.
CMAC_LOG_RESET_CANT_START_DS_TUNER_PRCESS The router was unable to start the internal process used to manage
the downstream tuner.
CMAC_LOG_RESET_TOO_MANY_DS_LOCKS_LOST Downstream QAM/FEC lock has been lost too many times.
CMAC_LOG_RESET_NO_SEND_TO_DS_TUNER_PROCESS The router MAC-layer process was unable to communicate with the
downstream tuner management process.
CMAC_LOG_RESET_DS_TUNER_WATCHDOG The downstream tuner process failed to report its continuing
operation for a long period of time.
CMAC_LOG_RESET_UNABLE_TO_SET_MIB_OBJECT The router was unable to set an SNMP parameter as specified by the
DOCSIS configuration file.
CMAC_LOG_RESET_MIB_OBJECT_PROCESS_WATCHDOG The internal MIB object took too long to process the entries in the
DOCSIS configuration file.
The following example is a typical display for the show controllers cable-modem 0 mac hardware
command. The most interesting bit is the station address (hardware address). The MIB statistics reflect
the MAC hardware counters for various events, but these counters are typically reset every few seconds,
so their contents are not accurate in this display.
Router# show controllers cable-modem 0 mac hardware
PLD VERSION: 32
MIB Statistics
DS fifo full = 0, Rerequests = 0
DS mac msg overruns = 0, DS data overruns = 0
Qualified maps = 0, Qualified syncs = 0
CRC fails = 0, HDR chk fails = 0
Data pdus = 0, Mac msgs = 0
Valid hdrs = 0
BCM3300 Registers:
downstream dma:
ds_data_bd_base=0x001D40, ds_mac_bd_base=0x001E80
ds_data_dma_ctrl=0x98, ds_mac_dma_ctrl=0x98
ds_dma_data_index=0x0000, ds_dma_msg_index=0x0000
upstream dma:
us_bd_base=0x001FB8, us_pd_base=0x002038
us_dma_ctrl=0x00, us_dma_tx_start=0x00
global control and status:
global_ctrl_status=0x00
interrupts:
irq_pend=0x0018, irq_mask=0x00E7
timing recovery circuit:
loop_enable=0x00, minislot_divisor=0x00
K0_ctrl=0x06, K1_ctrl=0x07, acq_threshhold=0x01
err_threshhold=0x04, timeout_threshold=0xFF
nco_bias=0x4F7004F7, ranging_offset=0x00000000
ts_err=0x00, sync_valid=0x00, delta_F=0x00
timeout_err=0x00
spi:
dynamic_ctrl=0x09, static_ctr=0x9F, autonomous=0x01
irq_ack=0x00, spi_cmd=0x51, spi_addr=0x11
spi_data= FF/00/00/00/00/00/00
burst profiles:
profile 0:
01 19 1D 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 1:
01 19 1D 03 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 2:
01 19 1D 04 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
profile 3:
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Router#
Table 138 describes the MIB statistics shown in the display for this command.
Field Description
DS fifo full Number of times the downstream receive buffer on the router has become
full.
Rerequests Number of registration requests sent by the router to the CMTS.
DS mac msg overruns Number of times the DMA controller has had a downstream MAC message
and there were no free MAC message buffer descriptors to accept the
message.
DS data overruns Number of times the DMA controller has had downstream data and there
were no free data PDU buffer descriptors to accept the data.
Qualified maps Number of valid MAP messages received by the router.
Qualified syncs Number of times the router has received synchronization with the
downstream channel.
CRC fails Number of cyclic redundancy checks (CRCs) generated by the far-end
device that did not match the checksums calculated from the message
portions of the packets received.
HDR check fails Number of cyclic redundancy checks (CRCs) generated by the far-end
device that did not match the checksums calculated from the MAC headers
of the packets received. The MAC header CRC is a 16-bit Header Check
Sequence (HCS) field that ensures the integrity of the MAC header even in
a collision environment.
Data pdus Total number of data PDUs (protocol data units) of all types received by the
cable interface.
Mac msgs Number of MAC messages received by the cable interface.
Valid hdrs Number of valid MAC headers received by the cable interface.
Below the MIB statistics in the show controllers cable-modem 0 mac hardware display, the BCM3300
registers section shows the DMA locations of the indicated processing routines of the Broadcom 3220
MAC chip within the router.
The following is typical output from the show controllers cable-modem mac state command that
summarizes the state of the cable MAC layer and provides a list of downstream search frequency bands
and the order in which they are searched. The normal operational state of the interface is the
maintenance_state. If the cable MAC layer is in the wait_for_link_up_state, the information shown
in the display corresponds to the last time the interface was up.
Router# show controller cable-modem 0 mac state
MIB Values:
Mac Resets: 0
Sync lost: 0
Invalid Maps: 0
Invalid UCDs: 0
Invalid Rng Rsp: 0
Invalid Reg Rsp: 0
T1 Timeouts: 0
T2 Timeouts: 0
T3 Timeouts: 4
T4 Timeouts: 0
Range Aborts: 0
DS ID: 1
DS Frequency: 663000000
DS Symbol Rate: 5056941
DS QAM Mode 64QAM
DS Search:
88 453000000 855000000 6000000
89 93000000 105000000 6000000
90 111250000 117250000 6000000
91 231012500 327012500 6000000
92 333015000 333015000 6000000
93 339012500 399012500 6000000
94 405000000 447000000 6000000
95 123015000 129015000 6000000
96 135012500 135012500 6000000
97 141000000 171000000 6000000
98 219000000 225000000 6000000
99 177000000 213000000 6000000
US ID: 1
US Frequency: 20000000
US Power Level: 34.0 (dBmV)
US Symbol Rate: 1280000
Ranging Offset: 12460
Mini-Slot Size: 8
Change Count: 4
Preamble Pattern: CC CC CC CC CC CC CC CC CC CC CC CC CC CC 0D 0D
A9 17 D9 C3 52 2F B3 86 A4 5F 67 0D 48 BE CE 1A
91 7D 9C 35 22 FB 38 6A 45 F6 70 D4 8B EC E1 A9
17 D9 C3 52 2F B3 86 A4 5F 67 0D 48 BE CE 1A 91
F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3
F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 F3 33 F7 33 F7
88 84 04 4C C4 84 C0 0C 44 08 08 CC 8C 0C 80 48
88 40 44 CC 48 4C 00 C4 40 80 8C C8 C0 C8 04 88
Burst Descriptor 0:
5 2 2 2 F4 7 811C24B0
Router#
Field Description
MAC State Current operational state of the MAC layer of the router.
Ranging SID Service ID used for ranging requests.
Registered Indicates whether or not the router is currently registered with the CMTS.
Privacy Established Indicates whether or not keys for baseline privacy have been exchanged
between the router and the CMTS, establishing privacy.
Privacy Version Indicates whether the router is using BPI or BPI+ baseline privacy.
DOCSIS Operating Mode Indicates the DOCSIS revision that the router has been provisioned for
(DOCSIS 1.0 or DOCSIS 1.1).
Snmp Operating Mode Indicates the current SNMP operating mode:
• Co-existence Mode—SNMPv3 co-existence model
• NmAccess Mode—SNMPv2 model
Mac Resets Number of times the router reset or initialized this interface.
Sync lost Number of times the router lost synchronization with the downstream
channel.
Invalid Maps Number of times the router received invalid MAP messages.
Table 139 show controller cable-modem mac state Field Descriptions (continued)
Field Description
Invalid UCDs Number of times the router received invalid upstream channel descriptor
(UCD) messages.
Invalid Rng Rsp Number of times the router received invalid ranging response messages.
Invalid Reg Rsp Number of times the router received invalid registration response
messages.
T1 Timeouts Number of timeouts caused by the router not receiving a valid UCD from
the CMTS within the specified time.
T2 Timeouts Number of timeouts caused by the router not receiving a maintenance
broadcast for ranging opportunities from the CMTS within a specified
time.
T3 Timeouts Number of timeouts caused by the router not receiving a response within
a specified time from the CMTS to a RNG-REQ message during initial
maintenance.
T4 Timeouts Number of timeouts caused by the router not receiving a response within
a specified time from the CMTS to a periodic maintenance request.
Range Aborts Number of times the ranging process was aborted by the CMTS.
DS ID Identifier of the downstream channel on which this MAC management
message has been transmitted. This identifier is arbitrarily chosen by the
CMTS and is only unique within the MAC-sublayer domain.
DS Frequency Downstream frequency acquired by the router during its last initialization
sequence.
DS Symbol Rate Downstream frequency in symbols per second.
DS QAM Mode Downstream modulation scheme being used by the router.
DS Search Frequency bands scanned by the router when searching for a downstream
channel. The router’s default frequency bands correspond to the North
American EIA CATV channel plan for 6 MHz channel slots between
90 MHz and 858 MHz.
US ID Identifier of the upstream channel to which this MAC management
message refers. This identifier is arbitrarily chosen by the CMTS and is
only unique within the MAC-sublayer domain.
US Frequency Transmission frequency used by the router in the upstream direction.
US Power Level Transmit power level of the router in the upstream direction.
US Symbol Rate Upstream frequency in symbols per second.
Ranging Offset Delay correction (in increments of 6.25 microseconds/64) applied by the
router to the CMTS upstream frame time derived at the router. Used to
synchronize the upstream transmissions in the time division multiple
access (TDMA) scheme, this value is roughly equal to the round-trip delay
of the router from the CMTS.
Mini-Slot Size Size T of the mini-slot for this upstream channel in units of the timebase
tick of 6.25 microseconds. Allowable values are 2, 4, 8, 16, 32, 64, or 128.
Table 139 show controller cable-modem mac state Field Descriptions (continued)
Field Description
Change Count Incremented by 1 by the CMTS whenever any of the values of this channel
descriptor change. If the value of this count in a subsequent upstream
channel descriptor (UCD) remains the same, the router can quickly decide
that the remaining fields have not changed, and may be able to disregard
the remainder of the message.
Preamble Pattern Byte pattern used for the preamble.
Burst Descriptor: A compound type/length/value (TLV) encoding that defines, for each type
of upstream usage interval, the physical-layer characteristics that are to be
used during that interval. Each burst descriptor is given an identifying
number.
Interval Usage Code Each upstream transmit burst belongs to a class which is given a number
called the interval usage code (IUC). Bandwidth MAP messages are used
by IUC codes to allocate upstream time slots. The following types are
currently defined:
1. Request: bandwidth request slot
2. Request/Data: bandwidth request or data slot
3. Initial Maintenance: initial link registration contention slot
4. Station Maintenance: link keep-alive slot
5. Short Data Grant: short data burst slot
6. Long Data Grant: long data burst slot
Modulation Type Upstream modulation format. (1 = QPSK; 2 = 16-QAM)
Differential Encoding Indicates whether or not differential encoding is used. (1 = yes; 2 = no)
Preamble Length Length of the preamble in bits. This value must be an integral number of
symbols—a multiple of 2 for QPSK; a multiple of 4 for 16-QAM.
FEC Error Correction Length of the forward error correction in bytes. The range is 0 to 10 bytes;
a value of 0 implies no forward error correction.
FEC Codeword Info Number of information bytes in the FEC codeword.
Bytes
Scrambler Seed 15-bit seed value loaded at the beginning of each burst after the register
has been cleared. Not used if scrambler is off.
Maximum Burst Size Maximum number of mini-slots that can be transmitted during this burst
type. When the interval type is Short Data Grant, this value must be
greater than 0. If this value is 0, the burst size is limited elsewhere.
Guard Time Size Amount of time in symbols between the center of the last symbol of a
burst and the center of the first symbol of the preamble of an immediately
following burst in an upstream transmission from the router to the CMTS.
Last Codeword Length Indicates whether or not the length of the last codeword is fixed or
shortened. (1 = fixed; 2 = shortened)
Scrambler on/off Indicates whether or not a scrambler is enabled in the upstream modulator.
(1 = on; 2 = off)
Network Access Indicates whether or not the router has access to the HFC network.
Table 139 show controller cable-modem mac state Field Descriptions (continued)
Field Description
Concatenation Indicates whether DOCSIS 1.1 concatenation is enabled or disabled.
Maximum CPEs Maximum number of CPEs supported for this cable modem.
Vendor ID Unique identifier specifying the CM manufacturer.
Auth. Wait Timeout Number of seconds the router waits for a reply after sending the
Authorization Request message to the CMTS.
Reauth. Wait Timeout Number of seconds the router waits for a reply after it has sent an
Authorization Request message to the CMTS in response to a
reauthorization request or an Authorization Invalid message from the
CMTS.
Auth. Grace Time Number of seconds before the current authorization is set to expire that the
grace timer begins, signaling the router to begin the reauthorization
process.
Op. Wait Timeout Number of seconds the TEK state machine waits for a reply from the
CMTS after sending its initial Key Request for its SID’s keying material.
Retry Wait Timeout Number of seconds the TEK state machine waits for a replacement key for
this SID after the TEK grace timer has expired and the request for a
replacement key has been made.
TEK Grace Time Number of seconds before the current TEK is set to expire that the TEK
grace timer begins, signaling the TEK state machine to request a
replacement key.
Auth. Reject Wait Time Number of seconds the router waits before sending another Authorization
Request message to the CMTS after it has received an Authorization
Reject message.
Assigned SID Service ID assigned by the CMTS for the corresponding service class.
Max Downstream Rate Maximum downstream rate in bits per second that the CMTS is permitted
to forward to CPE unicast MAC addresses learned or configured as
mapping to this router. This rate does not include MAC packets addressed
to broadcast or multicast MAC addresses.
Max Upstream Rate Maximum upstream rate in bits per second that the router is permitted to
forward to the RF network. This rate includes packet PDU data packets
addressed to broadcast or multicast addresses.
Upstream Priority Relative priority assigned to this service class for data transmission in the
upstream channel. Higher numbers indicate higher priority.
Min Upstream Rate Date rate in bits per second that will be guaranteed to this service class on
the upstream channel.
Max Upstream Burst Maximum transmit burst in bytes allowed for this service class on the
upstream channel.
Privacy Enable Indicates whether or not Baseline Privacy is enabled for this service class.
Ranging Backoff Start Initial back-off window for initial ranging contention, expressed as a
power of 2. Valid values are from 0 to 15.
Ranging Backoff End Final back-off window for initial ranging contention, expressed as a power
of 2. Valid values are from 0 to 15.
Table 139 show controller cable-modem mac state Field Descriptions (continued)
Field Description
Data Backoff Start Initial back-off window for contention data and requests, expressed as a
power of 2. Valid values are from 0 to 15.
Data Backoff End Final back-off window for contention data and requests, expressed as a
power of 2. Valid values are from 0 to 15.
IP Address IP address of the cable interface.
Net Mask Subnet mask of the cable interface.
TFTP Server IP Address IP address of the CMTS TFTP server.
Time Server IP Address IP address of the CMTS Time-of-Day (TOD) server.
Config File Name Name of the configuration file that is downloaded from the TFTP server
to provide the router with operational parameters.
Time Zone Offset Correction received from the DHCP server to synchronize the router time
clock with the CMTS.
Log Server IP Address Displays the IP address for a syslog server, if any has been defined.
Drop Ack Enabled Indicates whether the TCP drop acknowledge feature is enabled or
disabled.
Piggyback when Ccat On Indicates whether the piggybacking of data onto request packets is
enabled when concatenation is also enabled.
Mac Sid Status Displays the service IDs currently in use.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR905 and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the manufacturing certificate for Cisco Systems, which the Secure Software
Download procedure uses to authenticate the software that the router downloads. This command shows
the individual X.509 components of the certificate, starting with the DOCSIS restricted X.501
Distinguished Name and ending with the 1024-bit public key.
Tip This command displays the certificate that is incorporated into the Cisco IOS image that the router is
currently running. Upgrading the Cisco IOS image could also update the manufacturer’s certificate. The
show controllers cable-modem cmcert command displays the cable-modem certificate that is that is
burned into the router at the factory and is not normally changed.
Examples The following example shows the starting lines and ending lines of typical output for the show
controllers cable-modem manuf-cert command:
Router# show controllers cable-modem 0 manuf-cert
OID(3):Country 2.5.4.6
1w3d: PRT(2):US
END
END
SET(57)
SEQ(55)
OID(3):Organization 2.5.4.10
1w3d: PRT(48):Data Over Cable Service Interface Specification
END
END
SET(21)
SEQ(19)
OID(3):Organization Unit 2.5.4.11
1w3d: PRT(12):Cable Modems
END
END
...
1w3d: E1 13 05 10 3C F1 F1 A0 CE 43 74 30 9C 59 F5 70
1w3d: 4B C2 71 8E 79 AC 19 3D AB 94 1E B0 BE BC 15 D8
1w3d: AD A4 79 F5 58 CA 04 25 62 A9 F8 3F E7 40 64 E2
1w3d: 65 B0 D0 53 65 FF F1 12 FF 1B CD DE 1D 47 A2 6E
1w3d: END
Router#
Note You must manually enter a return to redisplay the router prompt after the certificate has been displayed.
Cisco uBR905, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the PHS parameters that are currently in use for both the upstream and
downstream. The information shown corresponds to the PHS parameters that are listed in Appendix C
of the DOCSIS 1.1 specification.
Examples The following shows an excerpt from typical output from the show controllers cable-modem phs
command:
Router# show controllers cable-modem 0 phs
PHS Parameters
PHS Classifier Refer: 2
PHS Classifier ID: 1
PHS Service Flow Reference: 1
PHS Service Flow ID: 3
PHS Dynsrv Change Action: 0
PHS Fields:
PHS Index: 1
PHS Mask: 0x00 0x00 0x00 0x03 0xC0
PHS Size: 0
PHS Verification: 0
PHS Parameters
PHS Classifier Refer: 2
PHS Classifier ID: 1
PHS Service Flow Reference: 1
PHS Parameters
PHS Classifier Refer: 2
PHS Classifier ID: 1
PHS Service Flow Reference: 1
PHS Service Flow ID: 3
PHS Dynsrv Change Action: 0
PHS Fields:
PHS Index: 1
PHS Mask: 0x00 0x00 0x00 0x03 0xC0
PHS Size: 0
PHS Verification: 0
...
PHS Parameters
PHS Classifier Refer: 1
PHS Classifier ID: 2
PHS Service Flow Reference: 2
PHS Service Flow ID: 4
PHS Dynsrv Change Action: 0
PHS Fields: 0x08 0x00 0x45 0x00 0x00 0x56 0x00 0x00 0x00 0x00 0x3B
0x00 0x6D 0xA7 0x01 0x0A 0x28 0x03 0x00 0x00 0x00 0x00
PHS Index: 1
PHS Mask: 0x00 0x03 0xC0
PHS Size: 22
PHS Verification: 0
PHS Parameters
PHS Classifier Refer: 3
PHS Classifier ID: 3
PHS Service Flow Reference: 4
PHS Service Flow ID: 10
PHS Dynsrv Change Action: 0
PHS Fields: 0x08 0x00 0x45 0x00 0x00 0x56 0x00 0x00 0x00 0x00 0x3B
0x00 0x6D 0xA7 0x00 0x00 0x00 0x00 0x01 0x0A 0x28 0x42
PHS Index: 2
PHS Mask: 0x00 0x00 0x3C
PHS Size: 0
PHS Verification: 0
Router#
PHS Parameters
PHS Classifier Refer: 15
Router#
Field Description
PHS Classifier The reference ID for the classifier using this PHS rule.
Refer
PHS Classifier ID The ID for the classifier using this PHS rule.
PHS Service Flow The reference ID for the service flow using this PHS rule.
Reference
PHS Service Flow The ID for the service flow using this PHS rule.
ID
PHS Dynsrv The action taken in a dynamic service change request for this PHS rule:
Change Action
• 0 = Add the PHS rule.
• 1 = Set the PHS rule.
• 2 = Delete the PHS rule.
• 3 = Delete all PHS rules.
PHS Fields The bytes of the headers that must be suppressed and restored during PHS
operation. For the upstream, this includes the PDU bytes starting with the first
byte after the MAC header checksum. For the downstream, this includes the PDU
bytes starting with the 13th byte after the MAC header checksum.
PHS Index The index that references the suppressed byte string in the PHS Fields. The index
is unique per service flow in the upstream direction and unique per the cable
modem in the downstream direction.
PHS Mask The mask used to interpret the bytes in the PHS Fields, where each bit indicates
whether the corresponding byte in the PHS Fields should be suppressed (0 = do
not suppress, 1 = suppress).
PHS Classifier Size The total number of bytes in the header to be suppressed.
PHS Classifier Indicates whether the header bytes are to be verified before suppression (0 =
Verification verify, 1 = do not verify).
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines To understand the output from this command, consult the Broadcom specifications for the BCM3116 and
BCM3037 chips.
Examples The following is typical output from the show controllers cable-modem phy command:
Router# show controllers cable-modem 0 phy receive
The following example shows typical output for the physical transmit registers:
Router# show controllers cable-modem 0 phy transmit
Preamble values:
CC CC CC CC CC 0D 0D CC CC CC CC CC CC CC CC 0D
04 25 01 01 01 01 02 01 02 03 02 00 40 04 02 00
40 05 01 00 06 01 10 07 02 01 52 08 01 01 09 01
08 0A 01 01 0B 01 02 04 25 03 01 01 01 02 01 02
03 02 00 50 04 02 00 30 05 01 00 06 01 22 07 02
01 52 08 01 00 09 01 30 0A 01 01 0B 01 02 04 25
04 01 01 01 02 01 02 03 02 00 40 04 02 00 40 05
01 00 06 01 22 07 02 01 52 08 01 00 09 01 30 0A
Router#
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR905, Cisco uBR924, and Cisco uBR925 cable access routers, and Cisco CVA122 Cable Voice Adapter
Usage Guidelines When the cable modem is operating in DOCSIS 1.0 or DOCSIS 1.0+ mode, this command displays the
four possible stream queues, the Service ID (SID) associated with each queue (if the queue is currently
in use), and whether the SID is the primary SID, a secondary (static) SID, or a dynamic (on demand)
SID. The display also shows the packets and bytes that have been transmitted and received on each
stream.
When the cable modem is operating in DOCSIS 1.1 mode, this command also displays the modem’s
capabilities and packet classifiers.
Examples The following example shows typical output for a DOCSIS 1.0 or DOCSIS 1.0+ cable modem for the
QoS statistics for each of the router’s four queues:
Router# show controllers cable-modem 0 qos
Router#
In Cisco IOS Release 12.2(15)CZ and later releases, the QoS statistics include information about the
DOCSIS 1.1 operations, including the type of service flow and packet classifiers being used for each
queue. The following is a typical default display:
Router# show controllers cable-modem 0 qos
0 2 F T T F
1 0 T T T T
2 0 T T T T
3 0 F T T T
Router#
0 2 F T T F
1 0 T T T T
2 0 T T T T
3 0 F T T T
Packet Classifiers
Router#
Table 141 describes the significant fields shown in the display for a DOCSIS 1.0 or DOCSIS 1.0+ cable
modem:
Field Description
Queue One of the four possible service flow queues that exist in the router.
SID Service identifier, a 14-bit integer assigned by the CMTS to each active
upstream service flow.
SID Type The type of SID:
• Primary—The service flow used for best-effort data traffic and MAC
maintenance messages.
• Secondary—Secondary static service flows that are created at
power-on provisioning for voice calls when dynamic SIDs are not
active.
• Dynamic—Secondary service flows that are created for on-demand
voice calls when using dynamic SIDs.
SFID Service flow identifier, a 32-bit integer assigned by the CMTS to each
service flow on the router.
TX Pkts Number of packets the router has transmitted on this service flow.
TX Bytes Number of bytes the router has transmitted on this service flow.
RX Pkts Number of packets the router has received on this service flow.
RX Bytes Number of bytes the router has received on this service flow.
Queue/SF Type Identifies the type of service flow being used for each queue.
In Cisco IOS Release 12.2(15)CZ and later releases, the QoS statistics include information about the
DOCSIS 1.1 operations, including the type of service flow and packet classifiers being used for each
queue:
Router# show controllers cable-modem 0 qos
Queue SF Type
0 BE
1 BE
2 UGS_AD
3 NA
Packet Classifiers
Classifier id = 1 SFID = 91
IP source: 10.188.1.88
IP dest: 10.188.1.66
UDP/TCP source range: 18416 to 18416
UDP/TCP dest range: 16740 to 16740
IP Protocol: 17
PHS: Inactive
Classifier id = 2 SFID = 93
IP source: 10.188.1.88
IP dest: 10.188.1.66
UDP/TCP source range: 16796 to 16796
UDP/TCP dest range: 19138 to 19138
IP Protocol: 17
PHS: Inactive
Table 142 describes the fields shown in the display for a DOCSIS 1.1 cable modem.
Table 142 show controllers cable-modem qos Field Descriptions (DOCSIS 1.1)
Field Description
Queue One of the four possible service flow queues that exist in the router.
SID Service Identifier, a 14-bit integer assigned by the CMTS to each active
upstream service flow.
SID Type The type of SID:
• Primary—The service flow used for best-effort data traffic and MAC
maintenance messages.
• Secondary—Secondary static service flows that are created at
power-on provisioning for voice calls when dynamic SIDs are not
active.
• Dynamic—Secondary service flows that are created for on-demand
voice calls when using dynamic SIDs.
SFID Service Flow Identifier, a 32-bit integer assigned by the CMTS to each
service flow on the router.
Table 142 show controllers cable-modem qos Field Descriptions (DOCSIS 1.1) (continued)
Field Description
TX Pkts Number of packets the router has transmitted on this service flow.
TX Bytes Number of bytes the router has transmitted on this service flow.
RX Pkts Number of packets the router has received on this service flow.
RX Bytes Number of bytes the router has received on this service flow.
Capabilities These four fields describe whether the following features are enabled.
cbr Indicates whether committed bit rate traffic (CBR) is supported (T) or not
(F). This could indicate either UGS or UGS-AD service flows.
cc Indicates whether concatenation is supported (T) or not (F).
fr Indicates whether DOCSIS fragmentation is supported (T) or not (F).
nbr Indicates the Not Broadcast status, depending on whether the classifier
supports broadcasts (F) or not (T).
Queue/SF Type Identifies the type of service flow being used for each queue.
Packet Classifiers Describes the classifiers defined on the router.
Class id ID used to uniquely identify the classifier in each service flow.
SFID ID that uniquely identifies the service flow.
Pri Traffic Priority parameter that was assigned to this classifier. If no value
was set, the priority defaults to 0 (lowest priority).
Table 142 show controllers cable-modem qos Field Descriptions (DOCSIS 1.1) (continued)
Field Description
valid A 13-bit bitmask showing which Type/Length/Value (TLV) fields were set
on the classifier. The following shows the meaning of each bit, with the
least significant bit on the far right. The bit is set to 1 if the corresponding
TLV was set for the classifier:
• 0x0001—IP Type of Service Range and Mask
• 0x0002—IP Protocol
• 0x0004—IP Source Address
• 0x0008—IP Source Mask
• 0x0010—IP Destination Address
• 0x0020—IP Destination Mask
• 0x0040—TCP/UDP Source Port Start and TCP/UDP Source Port End
• 0x0080—TCP/UDP Destination Port Start and TCP/UDP Destination
Port End
• 0x0100—Destination MAC Address
• 0x0200—Source MAC Address
• 0x0400—Ethertype/DSAP/MacType
• 0x0800—IEEE 802.1P User_Priority
• 0x1000—IEEE 802.1Q VLAN_ID
For example, a value of D6 translates to the bit-mask “1101 0110”, which
indicates that the following fields were set for the classifier: IP Protocol,
IP Source Address, IP Destination Address, and the TCP/UDP Source and
Destination Port values.
Match Number of packets matching the classifier.
SIDT Address for the classifier in the internal SID table (SIDT).
Packet Classifier Details Describes each packet classifier in detail.
Classifier ID ID used to uniquely identify the classifier in each service flow.
SFID ID that uniquely identifies the service flow.
IP source The matching IP source address.
IP dest The matching IP destination address.
UDP/TCP source range The low-end and high-end matching source TCP/UDP port values.
UDP/TCP dest range The low-end and high-end matching destination TCP/UDP port values.
IP Protocol The matching IP protocol type, as given in RFC 1700. A value of 256
matches any IP protocol, and a value of 257 matches TCP and UDP traffic.
PHS Indicates whether Payload Header Suppression (PHS) is active or inactive.
Downstream Payload Indicates that PHS is being used on the downstream.
Header Suppression
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR905, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines This command displays the Quality of Service (QoS) parameters that make up each of the service flows
that are defined on the router for the upstream and downstream. The information shown corresponds to
the QoS parameters that are listed in Appendix C of the DOCSIS 1.1 specification.
Examples The following example shows typical output for the default form of the show controllers cable-modem
service-flows command.
Router# show controllers cable-modem 0 service-flows
Router#
The following example shows typical output for the summary option of the show controllers
cable-modem service-flows command.
Router# show controllers cable-modem 0 service-flows summary
Router#
The following example shows typical output for the show controllers cable-modem service-flows
command, when displaying information for individual service flows:
Router# show controllers cable-modem 0 service-flows 3
Router#
Table 143 describes the significant fields shown by this command. The information shown corresponds
to the QoS parameters that are listed in Appendix C of the DOCSIS 1.1 specification.
Field Description
Flow Type, Sf type Identifies whether the type of service-flow:
• Primary—The primary service-flow for the upstream or downstream.
• Static—A permanent secondary service-flow.
• Dynamic—A dynamically created secondary service-flow.
Flow Reference, Sf Ref The service flow reference ID that is used to establish the Service Flow ID.
Field Description
Service Flow ID, Sfid The ID that unique identifies this service flow on the upstream or
downstream.
Service ID, Sid The service identifier (SID) that the CMTS assigns to the service flow.
QoS Set Type The QoS parameter set type for the service flow. This is a three-bit value,
where bit 0 is set for the Provisioned Set, bit 1 is set for the Admitted Set,
and bit 2 is set for the Active Set. Multiple bits can be set to produce the
following possible values:
• 0 = Set Active and Admitted Sets to null.
• 1 = Apply to Provisioned Set only.
• 2 = Perform admission control and apply to Admitted Set only.
• 3 = Perform admission control and apply to Provisioned and Admitted
Sets.
• 4 = Check against Admitted set in separate Service Flow encoding,
perform admission control if needed, activate this service flow, and
apply to Active Set.
• 5 = Perform admission control, apply to Provisioned and Active Sets,
and activate this service flow.
• 6 = Perform admission control, activate this service flow, and apply to
Admitted and Active Sets.
• 7 = Perform admission control, activate this service flow, and apply to
Provisioned, Admitted, and Active Sets.
QoS Traffic Priority The priority assigned to the service flow (0 to 7, where 7 is the highest
priority).
QoS Max Sustained The maximum traffic rate, in bits, for a token-bucket rate limit for packets.
Traffic Rate
QoS Max Traffic Burst The maximum size of a single packet on this service flow.
QoS Min Reserved The minimum rate, in bits per second, for traffic on this service flow.
Traffic Rate
QoS Min Reserved Rate The minimum packet size, in bytes, for which the minimum rate can be
Pkt Size sustained on this service flow.
QoS Timeout For Active The maximum time, in seconds, that resources on a service flow can
Param remain unused before the CMTS sets the flow’s Admitted and Active Sets
to null. A value of 0 indicates no timeout period.
Qos Timeout For The maximum time, in seconds, that Admitted resources on a service flow
Admitted Param can remain without being activated. After this timeout period, the CMTS
will release Admitted resources on a service flow and retain only the
activated ones.
Max Concatenated Burst The maximum burst size, in bytes, for concatenated traffic on the service
flow. A value of 0 indicates no limit.
Field Description
Scheduling Type The type of service used on the upstream for grant requests:
• 1 = Undefined
• 2 = Best effort
• 3 = Non-real-time polling service (NRTPS)
• 4 = Real-time polling service (RTPS)
• 5 = Unsolicited grant service with activity detection (UGS-AD)
• 6 = Unsolicited grant service (UGS)
Request/Transmission The allowable means of grant request and transmission on the upstream.
Policy This value is a 9-bit mask where the bits have the following meanings
when set to 1:
• Bit 0 = Do not use broadcast request opportunities.
• Bit 1 = Do not use priority request multicast request opportunities.
• Bit 2 = Do not use Request/Data grants for requests.
• Bit 3 = Do not use Request/Data grants for data.
• Bit 4 = Do not piggyback data on grant requests.
• Bit 5 = Do not use concatenation.
• Bit 6 = Do not use DOCSIS fragmentation.
• Bit 7 = Do not use payload header suppression (PHS).
• Bit 8 = UGS service flows must drop packets that do not fit.
See Table 144 for the possible values of each bit for each of the supported
flow types.
Nominal Polling Interval The interval, in microseconds, between successive unicast grant requests
for the service flow on the upstream.
Tolerated Poll Jitter The maximum amount of time, in microseconds, that a unicast request
interval may be delayed from the typical polling schedule.
Unsolicited Grant Size The size of unsolicited grants, in bytes.
Nominal Grant Interval The interval, in microseconds, between successive data grant opportunities
for the service flow on the upstream.
Tolerated Grant Jitter The maximum amount of time, in microseconds, that transmission
opportunities may be delayed from the typical polling schedule.
Grants Per Interval The actual number of grants per Nominal Grant Interval for UGS service
flows, and the maximum number of active grants per Nominal Grant
Interval for UGS-AD service flows.
Max DS Latency The maximum latency, in microseconds, between the reception of a packet
by the CMTS on its network interface and the transmission of the packet
on its downstream cable interface.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Examples The following example shows typical tuner settings. Table 145 describes the output field possibilities
and descriptions.
Router# show controllers cable-modem 0 tuner
Tuner: status=0x00
Rx: tuner_freq 507000000, symbol_rate 5360736, local_freq 11520000
snr_estimate 17488, ber_estimate 0, lock_threshold 26000
QAM not in lock, FEC not in lock, qam_mode QAM_64
Tx: tx_freq 20000000, power_level 0x3E, symbol_rate 1280000
Router#
Field Description
tuner_freq Indicates the current downstream frequency.
symbol_rate Indicates the downstream symbol rate in symbols per second.
local_freq Frequency on which the transmitter and tuner communicate.
snr_estimate Signal-to-noise ratio (SNR) estimate in dB multiplied by 1000.
ber_estimate Bit error rate estimate (always 0).
lock_threshold Minimum SNR that the router will accept as a valid lock.
QAM status Indicates if QAM/FEC lock has been acquired and the modulation mode in use.
tx_freq Upstream frequency sent to the router by the CMTS in the UCD message.
Field Description
power_level Transmit power level as set in the hardware, given as a hexadecimal value. The
units are unique to the hardware used. Use the show controllers cable-modem
mac state command to see the power level in dBmV.
symbol_rate Indicates the upstream symbol rate in symbols per second that is negotiated
between the CMTS and the cable access router.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Usage Guidelines To reset the counters that are displayed with the show controllers clock-reference command, use the
cable clock clear-counters command.
This command supports the Cisco CMTS clock feature set, which provides a synchronized clock for
improved Voice-over-IP (VoIP) operations. The clock feature set requires one of the following
configurations:
• A Cisco uBR10012 router with one or two TCC+ cards that are connected to an external national
clock source.
• A Cisco uBR7246 VXR router using a Cisco uBR-MC16S, Cisco uBR-MC16E,
Cisco uBR-MC28C, or Cisco uBR-MC28C-BNC cable interface line card. The router must also be
equipped with a Cisco cable clock card and be running Cisco IOS 12.1(1a)T1, 12.1(2)EC1, or a later
release. The Cisco cable clock card should be connected to an external national clock source.
Only these cable interface cards support the external clock card reference from a clock card to distribute
that signal to CMs or set-top boxes (STBs) attached to the specific network segments. You can use other
cable interface cards, such as the Cisco uBR-MC16C, with the clock card, but these other cable
interfaces will not synchronize their downstream SYNC messages with the external clock source.
Each CM or STB must also support VoIP applications and the clock feature set. For example, the
Cisco uBR924, running Cisco IOS Release 12.0(7)T or later, supports clock card feature automatically.
Examples The following is sample output from the show controllers clock-reference command for a
Cisco uBR7246 VXR router with a national clock card:
The following is sample output from the show controllers clock-reference command for a
Cisco uBR10012 router with two TCC+ cards.
Note Each TCC+ card—Active and Backup—has its own separate set of registers.
Router#
Note The show controllers clock-reference command might display compare errors on the Cisco uBR10012
router because there could be a slight delay at system startup before the TCC+ cards synchronize with
each other. These initial compare errors can be ignored and cleared with the cable clock clear-counters
command.
Most of the information shown by the show controllers clock-reference command is in the form of a
hexadecimal bitfield that is not meaningful for normal operations, but the following fields can be useful
in troubleshooting problems with the TCC+ and cable interface line cards:
• UCPC Bus Control Status Reg—Displays the status of both TCC+ cards and whether the LCD
Display Panel is present.
• Line Card Presence Status Reg—Provides a software view of whether a cable interface line card is
physically present in the Cisco uBR10012 chassis.
• LC Presence Input Reg—Provides a hardware view of whether a cable interface line card is
physically present in the Cisco uBR10012 chassis.
• LC Power off Status Reg—Indicates whether a cable interface line card slot has been powered off
using the cable power command.
Table 0-146 shows how to interpret these fields.
Field Description
UCPC Bus Control Status Reg Displays the status of both TCC+ cards and of the LCD
Display Panel. Each TCC+ card displays this field from its
own point of view, where “this card” refers to itself and “the
other card” refers to the other TCC+ card slot.
• Bits 2–0 display the status of the other TCC+ card:
– 0x00=No card.
– 0x03=The other card is the backup card.
– 0x05=The other card is the active card.
• Bit 3 is set to 1 upon a state change for the other TCC+
card.
• Bits 6–4 display the status of this TCC+ card:
– 0x00=No card.
– 0x03=This card is the backup card.
– 0x05=This card is the active card.
– 0x06=This card has assumed the active card role,
because the other card had been active but is now
unresponsive.
• Bit 7 is set to 1 upon a state change for this TCC+ card.
• Bits 13–8 are unused.
• Bit 14 is set to 1 if the LCD Display Panel is present.
• Bit 15 is set to 1 if the presence of the LCD Display Panel
has changed since the counters were last cleared.
The most common bit patterns for the UCPC Bus Control Status Reg field are:
• 0x4003—This TCC+ card is not present, the other card is the active card, and an LCD Display is
present.
• 0x4030—This TCC+ card is the active card, the other card is not present, and an LCD Display is
present.
• 0x4035—This TCC+ card is the backup card, the other card is the active card, and an LCD
Display is present.
• 0x4053—This TCC+ card is the active card, the other card is the backup card, and an LCD
Display is present.
• 0x4065—This TCC+ card has assumed the active card role, because the other card had been active
but is now unresponsive. The LCD Display is present.
Field Description
Line Card Presence Status Reg The first eight bits indicate whether the line card is physically
present, and the high eight bits indicate whether the card’s
physical state has changed since the counters were last cleared
using the cable clock clear-counters command.
0x0001=slot 5/0 contains a cable interface card
0x0002=slot 5/1 contains a cable interface card
0x0004=slot 6/0 contains a cable interface card
0x0008=slot 6/1 contains a cable interface card
0x0010=slot 7/0 contains a cable interface card
0x0020=slot 7/1 contains a cable interface card
0x0040=slot 8/0 contains a cable interface card
0x0080=slot 8/1 contains a cable interface card
0x0100=slot 5/0 has changed physical state
0x0200=slot 5/1 has changed physical state
0x0400=slot 6/0 has changed physical state
0x0800=slot 6/1 has changed physical state
0x1000=slot 7/0 has changed physical state
0x2000=slot 7/1 has changed physical state
0x4000=slot 8/0 has changed physical state
0x8000=slot 8/1 has changed physical state
LC Presence Input Reg The lower eight bits of this register indicate whether a cable
interface line card is physically present in the chassis slot. The
bit meanings are the same as the lower eight bits the Line Card
Presence Status Reg.
The upper eight bits of this register are unused.
Note The Line Card Presence Status Reg displays the line card state as determined by the Cisco IOS
software, while the LC Presence Input Reg displays the state as determined by the chassis
hardware.
LC Power off Status Reg 0x01=slot 5/0 is powered off
0x02=slot 5/1 is powered off
0x04=slot 6/0 is powered off
0x08=slot 6/1 is powered off
0x10=slot 7/0 is powered off
0x20=slot 7/1 is powered off
0x40=slot 8/0 is powered off
0x80=slot 8/1 is powered off
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Syntax Description slot The slot where the Wideband SIP resides. On the Cisco uBR10012 router,
slots 1 and 3 can be used for the Wideband SIP.
subslot The subslot where the Wideband SIP resides. On the Cisco uBR10012
router, subslot 0 is always specified.
all (Optional) Displays values for all registers.
cpld (Optional) Displays values for the CPLD registers.
processor (Optional) Displays values for the processor registers.
vanadium (Optional) Displays values for the Vanadium registers.
spi_fpga (Optional) Displays values for the SPI FPGA registers.
Command Default If you do not specify all or the keyword for a specific register, show controllers jacket displays values
for all registers.
Usage Guidelines Use the show controllers jacket command to display Wideband SIP register values. Values for the
following Wideband SIP components can be displayed:
• CPLD—A Complex Programmable Logic Device (CPLD) that contains logic to control resets, the
I/O bus, and SPA OIR.
• Processor—The Wideband SIP on-board processor that is responsible for configuring the chips on
the SIP, communication to the PRE module, and communication with the SPA.
• Vanadium—A Cisco-designed ASIC that provides a link between the Wideband SIP and the PRE
module.
• SPI FPGA—A bus converter that supports up to eight channels on a POS-PHY Level 3 (PL3)
interface and up to eight channels shared between the two System Packet Interface Level 4 Phase 2
(SPI 4.2) interfaces. The SPI FPGA also interfaces the on-board processor complex to the Wideband
SIP bus.
Examples The following examples display show controllers jacket command output for the cpld and processor
keywords:
Router# show controllers jacket 1/0 cpld
CPLD registers
[A4000000] Version:4
[A4000004] Clock frequency:32
[A4000008] Reset status and control:1
[A400000C] Software reset reason:0
[A4000010] Datapath reset: 19
[A4000014] SPA 0 OIR register: FF
[A4000018] SPA 1 OIR register: FF
[A400001C] SPA OIR interrupt status: (would clear on read)
[A4000020] SPA OIR interrupt mask: FF
Processor Registers
Port A:
Pin Assignment C00000
Data Direction FF437C3A
Open-Drain 1800F
Data A88005
Special Options 0000
Port B:
Pin Assignment 0008
Data Direction FFFFBEF
Open-Drain 0000
Data BF0FEFC
Special Options 0008
Port C:
Pin Assignment 3580C
Data Direction FF7CA7F3
Open-Drain 0000
Data 84D004
Special Options 0000
Port D:
Pin Assignment 30005
Data Direction FFCFFFE
Open-Drain 30000
Data 30000
Special Options 30000
Syntax Description slot The slot where the Wideband SIP resides. On the Cisco uBR10012 router,
slots 1 and 3 can be used for the Wideband SIP.
subslot The subslot where the Wideband SIP resides. On the Cisco uBR10012
router, subslot 0 is always specified.
bay The bay in the Wideband SIP where the Wideband SPA is located. Valid
values are 0 (upper bay) and 1 (lower bay).
port Specifies the interface number on the SPA.
brief (Optional) Displays a brief summary of Wideband SPA controller
information.
fpga_registers (Optional) Displays information on the Wideband SPA FPGA (Blaze)
registers.
all (Optional) Displays both SFP module and PHY information for the
Wideband SPA.
sfp (Optional) Displays information on the Wideband SPA small form-factor
pluggable (SFP) modules.
ge_phy (Optional) Displays physical layer (PHY) information on the Wideband
SPA Gigabit Ethernet ports.
port port_num (Optional) When used with sfp or ge_phy, the information displayed is for
the specified Wideband SPA Gigabit Ethernet port. If the port port_num
argument is not used, the information displayed is for both Gigabit
Ethernet ports.
Command Default If you specify no keyword or argument, all categories of information for both Gigabit Ethernet ports are
displayed.
Usage Guidelines Use the show controllers modular-cable command to display internal state information for the
Wideband SPA controller.
• The fpga_registers keyword displays FPGA register information for the Wideband SPA FPGA.
• The sfp keyword displays SFP module information and hardware details on the SFP modular in the
specified Wideband SPA port.
• The ge_phy keyword displays physical layer (PHY) and register values for the specified Wideband
SPA port.
If you specify all instead of sfp or ge_phy, both SFP module and PHY information is displayed.
Note This command will not provide crash dump information for the Cisco 10000 series SIP-600. Use the
show diag 1/0 crashdump command to obtain this information for the Cisco 10000 Series SIP-600.
Examples The following examples display show controllers modular-cable output for the fpga_registers, sfp,
and ge_phy keywords. In some cases, only part of the output is shown.
Router# show controllers modular-cable 1/0/0 fpga_registers
SFP in port 1
SFP is present
ID: SFP
Extended ID: 4
Connector: LC
SONET compliance: not specified
Gigabit Ethernet compliance: 1000BASE-SX
Fibre Channel link length: not specified
Fibre Channel transmitter technology: not specified
Fibre Channel transmission media: not specified
Fibre Channel speed: not specified
Encoding: 8B10B
Bit Rate: 1300 Mbps
50 micron-multimode fiber supported length: 550 m
62.5 micron-multimode fiber supported length: 270 m
Upper bit rate limit: not specified
Lower bit rate limit: not specified
Date code (yy/mm/dd): 05/02/23
Vendor name: CISCO-AGILENT
Vendor OUI: 12499
Vendor Part Number (PN): QFBR-5766LP Vendor Rev:
Vendor SN (SN): AGS090855CE
Options implemented:
LOS Signal
TX Fault Signal
TX Disable Signal
Enhanced options implemented: none
Diagnostic monitoring implemented: none
Idprom contents (hex):
0x00: 03 04 07 00 00 00 01 00 00 00 00 01 0D 00 00 00
0x10: 37 1B 00 00 43 49 53 43 4F 2D 41 47 49 4C 45 4E
0x20: 54 20 20 20 00 00 30 D3 51 46 42 52 2D 35 37 36
0x30: 36 4C 50 20 20 20 20 20 20 20 20 20 03 52 00 B5
0x40: 00 1A 00 00 41 47 53 30 39 30 38 35 35 43 45 20
0x50: 20 20 20 20 30 35 30 32 32 33 20 20 00 00 00 C4
0x60: 00 00 06 C9 F0 FA 7C 01 B3 C8 41 6B 39 04 FC 85
0x70: BB 20 9E 00 00 00 00 00 00 00 00 00 B4 94 52 CC
0x80: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x90: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
State: Initalized
Phased Initialization
Phase Reached: 4
Phase Exit Code: 0
Phase Read Offset: 0
Socket Verification
The command output was modified to capture the SPA sensor temperature readings and error packet
information.
The error information contains details about the:
• Timestamp of the capturing.
• Interrupt state when packet is captured, which indicates the error type.
• Packet length.
• Blaze header part of the packet.
Sample output for show controllers modular-cable command with NO error packets.
Router# show controllers modular-Cable 1/0/1 | b reading
WBCMTS DOCSIS SPA temperature sensor 0, reading: 25C/77F
WBCMTS DOCSIS SPA temperature sensor 1, reading: 25C/77F
Sample output of show controllers modular-cable command with error packets already been captured.
Router# show controllers modular-Cable 1/0/0
SPA 0 is present
status LED: [green]
Host 12V is enabled and is okay.
Power has been enabled to the SPA.
SPA reports power enabled and okay.
SPA reports it is okay and is NOT held in reset.
Note The temperature sensor readings in the command output shown above is specific to the Cisco IOS
Release 12.3(23)BC and will not appear in the Cisco IOS Release 12.2(33)SCB and later releases.
Beginning in Cisco IOS Release 12.3(23)BC6, the command output was modified to capture the SPA
environment monitoring information. The environment monitoring information includes the temperature
sensor information and the voltage sensor information.
The temperature sensor information contains details about the:
• Sensor number
• Current sensor reading
• Low threshold
• Warning threshold
• Critical threshold
• Shutdown threshold
The voltage sensor information contains details about the:
• Nominal value of the rail
• Current voltage reading
• Low shutdown threshold
• Low warning threshold
• High warning threshold
• High shutdown threshold
Sample output for the show controllers modular-cable command that displays the SPA environment
monitoring information.
Router# show controllers modular-cable 1/0/0 | b SPA Env
SPA Environment Monitoring Information:
Temperature sensors for SPA-24XDS-SFP[1/0]:
Sensor Reading Low Warning Critical Shutdown
0 26C 0C 58C 68C 85C
1 27C 0C 58C 68C 85C
Voltage sensors for SPA-24XDS-SFP[1/0]:
Nominal Reading LowShut LowWarn HighWarn HighShut
3.300V 3.276V 3.069V 3.135V 3.465V 3.531V
2.500V 2.485V 2.325V 2.375V 2.625V 2.675V
1.200V 1.186V 1.116V 1.140V 1.260V 1.284V
1.800V 1.801V 1.674V 1.710V 1.890V 1.926V
Note The SPAs are shut down automatically when the sensor readings go beyond the threshold shutdown
value.
In Cisco IOS Release 12.2(33)SCC, when the primary link on the SPA toggles more than five times
within 30 seconds, and the backup link is UP, the backup link is selected for traffic. The link switches
back to the primary link during the next primary link transition after 30 seconds or when the backup link
fails. The show controllers modular-cable command output was modified to capture the toggle
information.
Sample output for the show controllers modular-cable command that displays the toggle information.
Router# show controllers modular-cable 1/1/0
SPA 1 is present
status LED: [green]
Host 12V is enabled and is okay.
Power has been enabled to the SPA.
SPA reports power enabled and okay.
SPA reports it is okay and is NOT held in reset.
0 0x7 0 0 ms
1 0xC 0 0 ms
2 0x0 0 0 ms
3 0x0 0 0 ms
4 0x0 0 0 ms
5 0x0 0 0 ms
6 0x0 0 0 ms
7 0x0 0 0 ms
8 0x0 0 0 ms
9 0x0 0 0 ms
10 0x0 0 0 ms
11 0x0 0 0 ms
Cisco uBR925 cable access router, Cisco CVA122 Cable Voice Adapter
Examples The following example shows sample output from the show controllers usb command:
Router# show controllers usb 0
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Usage Guidelines For additional information about this feature and related commands, refer to the following document on
Cisco.com:
• COPS Engine Operation on the Cisco CMTS
Examples The following example illustrates the use of the show cops server command.
Router# show cops servers
COPS SERVER: Address: 161.44.135.172. Port: 3288. State: 0. Keepalive: 120 sec
Number of clients: 1. Number of sessions: 1.
COPS CLIENT: Client type: 1. State: 0.
The following example displays the policy server address, state, keepalives, and policy client
information:
Router# show cops servers
COPS SERVER: Address: 161.44.135.172. Port: 3288. State: 0. Keepalive: 120 sec
Number of clients: 1. Number of sessions: 1.
COPS CLIENT: Client type: 1. State: 0.
Command Description
debug packetcable cops Enables debugging processes for PacketCable with the COPS
engine.
debug packetcable gate Enables and displays debugging processes for PacketCable gate
control control.
debug packetcable subscriber Enables and displays debugging processes for PacketCable
subscribers.
show debug Displays current debugging information that includes PacketCable
COPS messages on the Cisco CMTS.
show ip rsvp policy Displays policy server addresses, ACL IDs, and client/server
connection status.
show cpd
To display the CPD functionality state, use the show cpd command in privileged EXEC mode.
show cpd
Examples The following example shows the output of the show cpd command:
Router# show cpd
CPD enabled
CR ID :12345
To display packet processing information for a particular service ID (SID) on a cable interface, use the
show cr10k-rp cable command in user EXEC or privileged EXEC mode.
show cr10k-rp cable slot/subslot/port sid {classifier | mac-rw-index | queue | service-flow {ds |
us}}
Syntax Description cable slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router for which
information should be displayed, where:
• slot—0 to 8
• subslot—0 or 1
• port—0 to 4 (depending on the cable interface)
sid (Optional) Identifies the service ID (SID) for which information should be
displayed.
classifier Displays classifier information for the SID.
mac-rw-index Displays the MAC rewrite index for the SID.
queue Displays information about the output packet queues for the modem
identified by the SID.
service-flow ds Displays the information of the downstream service-flows for the modem
identified by the SID.
service-flow us Displays the information of the upstream service-flows for the modem
identified by the SID.
Usage Guidelines The show cr10k-rp cable command displays information that the PRE routing processor (RP) module
has about a particular SID. This information includes configuration information about the SID, as well
as internal status information that is useful only to Cisco engineers in troubleshooting problems.
Examples The following example shows typical output for the show cr10k-rp cable command for a SID that
identifies a cable modem:
Router# show cr10k-rp c6/1/0 2 classifier
Mac Rw Index: 5CCB Index: 7
CM Classifiers:
id=4, sfid=14 CFR Index 16396 RP sfindex 16396,
prio=10, sip=0.0.0.0, sip mask=0.0.0.0
dip=0.0.0.0, dip mask=0.0.0.0, prot=17, tos=A0,E0
sport = 0,750, dport = 1024,10000 matches = 0
The following example shows typical output for the show cr10k-rp classifier command for a SID that
identifies a customer premises equipment (CPE) device:
Router# show cr10k-rp c6/0/0 70 classifier
CPE Classifiers:
Mac Rw Index: 390 CCB Index: 97
id=7, sfid=205 CFR Index 16484 RP sfindex 16484,
prio=255, sip=0.0.0.0, sip mask=0.0.0.0
dip=15.0.0.1, dip mask=255.255.255.255, prot=257, tos=0,FF
sport = 0,65535, dport = 1001,1001 matches = 0
CPE Classifiers:
Mac Rw Index: 387 CCB Index: 93
id=4, sfid=202 CFR Index 16481 RP sfindex 16481,
prio=255, sip=0.0.0.0, sip mask=0.0.0.0
dip=14.0.0.1, dip mask=255.255.255.255, prot=17, tos=0,FF
sport = 0,65535, dport = 0,65535 matches = 0
The following example shows typical output for the mac-rw-index option:
Router# show cr10k-rp c8/0/0 1 mac-rw-index
Router#
Tip To display more information about the max-rw-index, use the show pxf cpu cef command to display
information for a specific IP address. The output of this command shows the max-rw-index value in the
“rw_index” field.
The following example shows typical output for the show cr10k-rp queue command:
Router# show cr10k-rp c6/1/0 1 queue
BE Queues:
Queue Index: 131241, GlobalQID 71, CBLT ID 131241
MinRate(Kbps) 0, ExcessRatio 4, ShapeRate(bps) 0, QLimit 255
Service Flow(s): rp_sf_index 32881, lc_sfid 29, min_rate(bps) 0, max_rate(bps) 0
CIR Queues:
Queue Index: 2049, GlobalQID 70, CBLT ID 2049
MinRate(Kbps) 100, ExcessRatio 32, ShapeRate(bps) 0, QLimit 255
Service Flow(s): rp_sf_index 32880, lc_sfid 8, min_rate(bps) 100000, max_rate(bps) 0
LL Queues:
The following example shows typical output for the show cr10k-rp service-flow command for both the
downstream and upstream directions:
Router# show cr10k-rp c8/0/0 1 service-flow ds
16385 4 0 0 261
SFID SID
3 1
To display packet processing information for a particular service ID (SID) on a cable interface, use the
show cr10k-rp controller command in user EXEC or privileged EXEC mode.
Syntax Description modular-cable Identifies the cable interface on the Cisco uBR10012 router for which
slot/bay/port information should be displayed, where:
• slot—0 to 8
• bay—0 or 1
• port—0
Note Support for modular-cable keyword was introduced in Cisco IOS
Release 12.3(23)BC.
lblt Identifies the Logical Bandwidth Limiting Traffic (LBLT) associated with
the RF Physical Logical Bandwidth Limiting Traffic (PBLT).
pblt Identifies the PBLTs associated with the RF Channels.
Usage Guidelines The show cr10k-rp controller command displays information that the PRE remote processor (RP)
module has about a particular SID. This information includes configuration information about the SID,
as well as internal status information that is useful only to Cisco engineers in troubleshooting problems.
Examples The following examples show typical output for the show cr10k-rp controller command for a SID that
identifies a cable modem:
Router# show cr10k-rp controller modular-cable 1/1/0 lblt
LBLTs on each RF Channel's PBLT
To display information about the packet queues for a cable interface, use the show cr10k-rp queue
command in user EXEC or privileged EXEC mode.
Syntax Description cable slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router for which
information should be displayed, where:
• slot—0 to 8
• subslot—0 or 1
• port—0 to 4
modular-cable Identifies the cable interface on the Cisco uBR10012 router for which
slot/bay/port:channel information should be displayed, where:
• slot—0 to 8
• bay—0 or 1
• port—0
• channel—0
Note Support for modular-cable keyword was introduced in Cisco IOS
Release 12.3(23)BC.
wideband-cable Identifies the wideband-cable interface on the Cisco uBR10012 router for
slot/bay/port:channel which information should be displayed, where:
• slot—0 to 8
• bay—0 or 1
• port—0
• channel—0
Note Support for wideband-cable keyword was introduced in Cisco IOS
Release 12.3(21)BC.
queue Displays information about the packet queues for the SID.
Note Options for the keyword queue were removed from Cisco IOS
Release 12.3(21)BC.
Usage Guidelines The show cr10k-rp queue command displays information about the queues on the Cisco uBR10012
router.
Examples The following examples show typical displays for each form of the show cr10k-rp queue command:
Router# show cr10k-rp cable 7/0/0 queue
BE Queues:
Queue Index: 131345, GlobalQID 125, CBLT ID 131345
MinRate(Kbps) 0, ExcessRatio 4, ShapeRate(bps) 10000000, QLimit 255
Service Flow(s): rp_sf_index 32925, lc_sfid 7, min_rate(bps) 0, max_rate(bps) 10
CIR Queues:
LL Queues:
BE Queues:
Queue Index: 131346, GlobalQID 126, CBLT ID 131346
MinRate(Kbps) 0, ExcessRatio 4, ShapeRate(bps) 10000000, QLimit 255
Service Flow(s): rp_sf_index 32927, lc_sfid 8, min_rate(bps) 0, max_rate(bps) 10
CIR Queues:
LL Queues:
BE Queues:
Queue Index: 131347, GlobalQID 123, CBLT ID 131347
MinRate(Kbps) 0, ExcessRatio 4, ShapeRate(bps) 10000000, QLimit 255
Service Flow(s): rp_sf_index 32928, lc_sfid 8, min_rate(bps) 0, max_rate(bps) 10
CIR Queues:
LL Queues:
To display slot information for a particular service ID (SID) on a cable interface, use the show cr10k-rp
slots command in user EXEC or privileged EXEC mode.
Usage Guidelines The show cr10k-rp slots command displays information that the PRE remote processor (RP) module
has about a particular SID. This information includes configuration information about the SID, as well
as internal status information that is useful only to Cisco engineers in troubleshooting problems.
Examples The following example shows typical output for the show cr10k-rp slots command for a SID that
identifies a cable modem:
Router# show cr10k-rp slots
-----------------------------------------------------------
Slot/Sub Flags (Address)
-----------------------------------------------------------
1/0 0x0804 (0x6494E168)
1/1 0x0804 (0x6494E250)
2/0 0x0002 (0x6494E338)
2/1 0x0002 (0x6494E420)
3/0 0x0002 (0x6494E508)
3/1 0x0002 (0x6494E5F0)
4/0 0x0804 (0x6494E6D8)
4/1 0x0804 (0x6494E7C0)
5/0 0x0804 (0x6494E8A8)
5/1 0x0002 (0x6494E990)
6/0 0x0002 (0x6494EA78)
6/1 0x0002 (0x6494EB60)
OIR TABLE:
slot: 0 type: 00000001 bays: 0 analyzed: 1
slot: 1 type: 00000001 bays: 0 analyzed: 1
slot: 2 type: 00000415 bays: 4 analyzed: 1
bay: 0 type: 000004AE
bay: 1 type: 000004AE
bay: 2 type: 00000000
bay: 3 type: 00000000
slot: 3 type: 000005B0 bays: 0 analyzed: 1
slot: 4 type: 00000000 bays: 0 analyzed: 0
slot: 5 type: 000002AF bays: 0 analyzed: 1
slot: 6 type: 00000000 bays: 0 analyzed: 0
slot: 7 type: 00000000 bays: 0 analyzed: 0
slot: 8 type: 00000390 bays: 0 analyzed: 1
slot: 9 type: 00000390 bays: 0 analyzed: 1
slot: 10 type: 00000487 bays: 0 analyzed: 1
slot: 11 type: 00000000 bays: 0 analyzed: 0
slot: 12 type: 00000000 bays: 0 analyzed: 0
slot: 13 type: 00000000 bays: 0 analyzed: 0
slot: 14 type: 000003D5 bays: 0 analyzed: 1
slot: 15 type: 00000000 bays: 0 analyzed: 0
slot: 16 type: 00000000 bays: 0 analyzed: 0
slot: 17 type: 00000000 bays: 0 analyzed: 0
SLOT INFO:
slot: 0 subslot: 0 index: 0 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 7178D9A0 ironbus i0
slot: 0 subslot: 1 index: 1 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F000 ironbus i0
slot: 1 subslot: 0 index: 2 num_bays: 4
double wide: 1 type: 00000415 util type: FFFFFFFF plugin: 72CB529C ironbus i1
slot: 1 subslot: 0 index: 2 type: 000004AE
slot: 1 subslot: 256 index: 2 type: 000004AE
slot: 1 subslot: 512 index: 2 type: 00000000
slot: 1 subslot: 768 index: 2 type: 00000000
slot: 1 subslot: 1 index: 3 num_bays: 0
double wide: 0 type: 000005B0 util type: FFFFFFFF plugin: 22900974 ironbus i1
slot: 2 subslot: 0 index: 4 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F120 ironbus i0
slot: 2 subslot: 1 index: 5 num_bays: 0
double wide: 0 type: 000002AF util type: FFFFFFFF plugin: 26362104 ironbus i0
slot: 3 subslot: 0 index: 6 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F1E0 ironbus i0
slot: 3 subslot: 1 index: 7 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F240 ironbus i0
slot: 4 subslot: 0 index: 8 num_bays: 0
double wide: 0 type: 00000390 util type: FFFFFFFF plugin: 263621A4 ironbus i0
slot: 4 subslot: 1 index: 9 num_bays: 0
double wide: 0 type: 00000390 util type: FFFFFFFF plugin: 761EF050 ironbus i1
slot: 5 subslot: 0 index: 10 num_bays: 0
double wide: 0 type: 00000487 util type: FFFFFFFF plugin: 76200EFC ironbus i0
slot: 5 subslot: 1 index: 11 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F3C0 ironbus i0
slot: 6 subslot: 0 index: 12 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F420 ironbus i0
slot: 6 subslot: 1 index: 13 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F480 ironbus i0
slot: 7 subslot: 0 index: 14 num_bays: 0
double wide: 0 type: 000003D5 util type: FFFFFFFF plugin: 22900FA0 ironbus i0
slot: 7 subslot: 1 index: 15 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F540 ironbus i0
slot: 8 subslot: 0 index: 16 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F5A0 ironbus i0
slot: 8 subslot: 1 index: 17 num_bays: 0
double wide: 0 type: FFFFFFFF util type: FFFFFFFF plugin: 6494F600 ironbus i0
Usage Guidelines
Note You can use the unsupported command test cable generate in privileged EXEC mode to force the Cisco
CMTS to register the root certificate.
For additional information about using the show crypto commands on the Cisco CMTS, refer to the
“Configuring DOCSIS 1.1 on the Cisco CMTS” chapter of the Cisco CMTS Feature Guide:
Examples The following example illustrates the use of the show crypto ca certificates command:
Router# show crypto ca certificates
Usage Guidelines
Note The show crypto ca trustpoints command does not display the root certificate until after at least one
cable modem has registered with the Cisco CMTS using BPI+ encryption. Alternatively, you can use the
unsupported command test cable generate in privileged EXEC mode to force the Cisco CMTS to
register the root certificate.
Tip To display all certificates (Root, Manufacturers, CM) that the CMTS has learned, use the show crypto
ca certificates command.
For additional information about using the show crypto commands on the Cisco CMTS, refer to the
“Configuring DOCSIS 1.1 on the Cisco CMTS” chapter of the Cisco CMTS Feature Guide:
Examples The following example illustrates the show crypto ca trustpoints command with
Cisco IOS Release 12.3(9a)BC:
Router# show crypto ca trustpoints
Root certificate
Status: Available
Certificate Serial Number: D54BB68FE934324F6B8FD0E41A65D867
Key Usage: General Purpose
Issuer:
CN = DOCSIS Cable Modem Root Certificate Authority
OU = Cable Modems
O = Data Over Cable Service Interface Specifications
C = US
Subject Name:
CN = "BPI Cable Modem Root Certificate Authority "
OU = DOCSIS
O = BPI
C = US
Validity Date:
start date: 07:00:00 UTC Mar 27 2001
end date: 06:59:59 UTC Jan 1 2007
Syntax Description control (Optional) Displays out the number of control commands that are queued
for execution by the hardware accelerator crypto engine.
packet (Optional) Displays out the contents and status information for the transmit
packet rings that are used by the hardware accelerator crypto engine.
pool (Optional) Displays out the contents and status information for the receive
packet rings that are used by the hardware accelerator crypto engine.
Examples The following example shows a typical display of the number of control commands that are waiting to
be executed by the router’s hardware accelerator.
Router# show crypto engine accelerator ring control
Router#
The following truncated example displays typical output from the show crypto engine accelerator ring
command about the transmit packet rings that are used by the router’s hardware accelerator.
Router# show crypto engine accelerator ring packet
.
.
.
123: 0x00A0 0x007B 0x0012 0x05B2 0x870C
124: 0x00A0 0x007C 0x0011 0x05DC 0x0000
125: 0x00A0 0x007D 0x0012 0x05B3 0x870E
126: 0x00A0 0x007E 0x0011 0x05DC 0x0000
127: 0x00A0 0x007F 0x0012 0x05B4 0x8710
Head = 59 Tail = 59 Taken = 59
Router#
The following example shows typical output from the show crypto engine accelerator ring pool
command about the contents of the receive rings that are used by the router’s hardware accelerator.
Router# show crypto engine accelerator ring pool
Router#
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Command Description
crypto engine accelerator Enables the use of the Cisco uBR905 and Cisco uBR925 router’s
onboard hardware accelerator for IPSec encryption.
crypto ipsec Defines the IPSec security associations and transformation sets.
crypto isakmp Enables and defines the IKE protocol and its parameters.
crypto key Generates and exchanges keys for a cryptographic session.
crypto map Creates and modifies a crypto map for a session.
debug crypto engine Displays each control command as it is given to the crypto engine.
accelerator control
debug crypto engine Displays information about each packet sent for encryption and
accelerator packet decryption.
show crypto engine accelerator Displays the active (in-use) entries in the crypto engine security
sa-database association (SA) database.
show crypto engine accelerator Displays the current run-time statistics and error counters for the
statistic crypto engine.
show crypto engine brief Displays a summary of the configuration information for the crypto
engine.
show crypto engine Displays the version and configuration information for the crypto
configuration engine.
show crypto engine Displays a list of the current connections maintained by the crypto
connections engine.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Examples The following example displays the security associations database for the router’s hardware accelerator.
Router# show crypto engine accelerator sa-database
Flow Summary
Index Algorithms
001 transport inbound esp-des
002 transport outbound esp-des
003 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
004 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
005 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
006 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
007 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
008 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
009 transport inbound esp-md5-hmac esp-3des ah-md5-hmac
010 transport outbound esp-md5-hmac esp-3des ah-md5-hmac
011 tunnel inbound esp-3des
012 tunnel outbound esp-3des
013 tunnel inbound esp-3des ah-sha-hmac
014 tunnel outbound esp-3des ah-sha-hmac
015 tunnel inbound esp-des
016 tunnel outbound esp-des
017 tunnel inbound esp-des ah-md5-hmac
018 tunnel outbound esp-des ah-md5-hmac
019 tunnel inbound esp-des ah-md5-hmac
020 tunnel outbound esp-des ah-md5-hmac
036 tunnel inbound esp-des ah-sha-hmac
037 tunnel outbound esp-des ah-sha-hmac
038 tunnel inbound esp-md5-hmac esp-3des ah-md5-hmac
039 tunnel outbound esp-md5-hmac esp-3des ah-md5-hmac
SA Summary:
Index DH-Index Algorithms
001 007 DES SHA
002 001(deleted) DES SHA
003 001(deleted) DES SHA
Table 0-147 describes the fields shown in the display for this command.
Field Description
Flow Summary
Index Unique identifier for the flow.
Algorithms The Flow Algorithm field displays the transformation set for each SA:
Mode
• tunnel—Original IP packet is encrypted and encapsulated.
• transport—Only the data portion of the IP packet is encrypted and
encapsulated.
Direction
• inbound—Encryption is performed on incoming packets.
• outbound—Encryption is performed on outgoing packets.
Table 0-147 show crypto engine accelerator sa-database Field Descriptions (continued)
Field Description
Algorithms The transformation algorithm set for this SA:
• Encryption: DES or 3DES.
• Authentication: MD5 or SHA.
DH Summary
Index Unique DH index.
Group Identifies the DH group.
Config The type of keys:
• Shared Secret—Keys were pre-shared.
• Valid Pub/Priv—Keys were negotiated.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Command Description
show crypto engine Displays the version and configuration information for the crypto
configuration engine.
show crypto engine Displays a list of the current connections maintained by the crypto
connections engine.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Examples The following example shows typical output of the current statistics and error counters for the router’s
hardware accelerator.
Router# show crypto engine accelerator statistics
HIFN79xx:
ds: 0x80D92A64 idb:0x80D6F39C
Statistics for Virtual Private Network (VPN) Module:
1292 packets in 1292 packets out
2 paks/sec in 2 paks/sec out
6 Kbits/sec in 6 Kbits/sec out
rx_no_endp: 0 rx_hi_discards: 0 fw_failure: 0
invalid_sa: 0 invalid_flow: 0
fw_qs_filled: 0 fw_resource_lock:0 lotx_full_err: 0
null_ip_error: 0 pad_size_error: 0 out_bound_dh_acc: 0
esp_auth_fail: 0 ah_auth_failure: 0 crypto_pad_error: 0
ah_prot_absent: 0 ah_seq_failure: 0 ah_spi_failure: 0
esp_prot_absent:0 esp_seq_fail: 0 esp_spi_failure: 0
obound_sa_acc: 0 invalid_sa: 0 out_bound_sa_flow: 0
invalid_dh: 0 bad_keygroup: 0 out_of_memory: 0
no_sh_secret: 0 no_skeys: 0 invalid_cmd: 0
dsp_coproc_err: 0 comp_unsupported:0 pak_too_big: 0
pak_mp_length_spec_fault: 0
tx_lo_queue_size_max 2 cmd_unimplemented: 0
tx_lo_count 60
15124 seconds since last clear of counters
Interrupts: Notify = 0, Reflected = 1292, Spurious = 0
packet_loop_max: 2 packet_loop_limit: 512
Router#
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Examples The following example shows typical output for the show crypto engine brief command:
Router# show crypto engine brief
Compression: No
3 DES: Yes
Privileged Mode: 0x0000
Maximum buffer length: 4096
Maximum DH index: 0010
Maximum SA index: 0020
Maximum Flow index: 0040
Maximum RSA key size: 0256
Router#
Field Description
crypto engine name Name of the crypto engine as assigned with the key-name
argument in the crypto key generate dss command. If no name
has been assigned, this field shows “unknown.”
crypto engine type The type of encryption engine running, always “ISA/ISM” and
“software” for the Cisco uBR905 and Cisco uBR925 cable
access routers.
hifn chip id, rev, and api rev Identifies the hardware accelerator, the revision of its onboard
firmware, and the revision of the software application layer.
Compression Identifies whether packets are compressed as well as encrypted.
3DES Identifies whether Triple DES (3DES) 168-bit encryption is
supported.
crypto engine state The current run-time state of the crypto engine:
• installed—Indicates that the crypto engine is present but is
not configured for encryption.
• dss key generated—Indicates that the crypto engine has
DSS keys already generated.
crypto engine in slot The chassis slot number containing the crypto engine. This
field is always N/A for the Cisco uBR905 and Cisco uBR925
cable access routers because the engine is not in a slot but is
permanently onboard the routers.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Command Description
debug crypto engine Displays each control command as it is given to the crypto engine.
accelerator control
debug crypto engine Displays information about each packet sent for encryption and
accelerator packet decryption.
show crypto engine accelerator Displays the contents of command and transmit rings for the crypto
ring engine.
show crypto engine accelerator Displays the active (in-use) entries in the crypto engine security
sa-database association (SA) database.
show crypto engine accelerator Displays the current run-time statistics and error counters for the
statistic crypto engine.
show crypto engine Displays the version and configuration information for the crypto
configuration engine.
show crypto engine Displays a list of the current connections maintained by the crypto
connections engine.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Usage Guidelines This command displays the version, capabilities, and other information for the hardware accelerator
engine that performs IPSec encryption/decryption for the router.
Examples The following example shows typical output from the show crypto engine configuration command:
Router# show crypto engine configuration
Compression: No
3 DES: Yes
Privileged Mode: 0x0000
Maximum buffer length: 4096
Maximum DH index: 0010
Maximum SA index: 0020
Maximum Flow index: 0040
Maximum RSA key size: 0256
Field Description
crypto engine name Name of the crypto engine as assigned with the key-name
argument in the crypto key generate dss command. If no name
has been assigned, this field shows “unknown.”
crypto engine type Type of encryption engine running, always “ISA/ISM” and
“software” for the Cisco uBR905 and Cisco uBR925 cable
access routers.
hifn chip id, rev, and api rev Identifies the hardware accelerator, the revision of its onboard
firmware, and the revision of the software application layer.
Compression Identifies whether packets are compressed as well as encrypted.
3 DES Identifies whether Triple DES (3DES) 168-bit encryption is
supported.
Maximum buffer length Maximum size of the data buffer for each connection.
Maximum DH index, SA index, and Maximum size of each index that is supported per connection.
Flow index
Maximum RSA key size Maximum size of the RSA encryption key that is supported.
Lock Count Number of connections that have requested access to the crypto
engine and are waiting for processing time.
Unlock Count Number of connections that have finished encryption
processing and are waiting to release the crypto engine.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Command Description
debug crypto engine Displays information about each packet sent for encryption and
accelerator packet decryption.
show crypto engine accelerator Displays the contents of command and transmit rings for the crypto
ring engine.
show crypto engine accelerator Displays the active (in-use) entries in the crypto engine security
sa-database association (SA) database.
show crypto engine accelerator Displays the current run-time statistics and error counters for the
statistic crypto engine.
show crypto engine brief Displays a summary of the configuration information for the crypto
engine.
show crypto engine Displays a list of the current connections maintained by the crypto
connections engine.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Syntax Description active (Optional) Displays the configuration information for each active session.
dh (Optional) Displays the Diffie-Hellman connection status.
dropped-packet (Optional) Displays the number of packets that the crypto engine has
dropped.
flow (Optional) Displays the definition for each flow that has been defined.
Usage Guidelines This command displays the version, capabilities, and other information for the hardware accelerator
engine that performs IPSec encryption/decryption for the router.
Examples The following example shows typical output from the show crypto engine connections active
command:
Router# show crypto engine connections active
Field Description
ID Identifies the connection by its number. Each active encrypted
session connection is identified by a positive number from 1 to
299. These connection numbers correspond to the table entry
numbers.
Interface Interface involved in the encrypted session connection.
IP-Address IP address of the interface.
State Current state of the connection:
• alloc—the connection is requesting resources.
• set—an active connection (normal state).
Algorithm The encryption algorithms used for this connection. If this field
reads “NONE,” this connection is still being allocated and has
not yet requested an algorithm.
Encrypt Total number of encrypted outbound IP packets.
Decrypt Total number of encrypted outbound IP packets.
The following example shows typical output from the show crypto engine connections dh command:
Router# show crypto engine connections dh
Conn ID Status
0 0 1
0 14 1
0 0 1
0 0 1
0 18 1
Router#
Field Description
Conn Identifies the connection by its number. Each active encrypted
session connection is identified by a positive number from 1 to
299. These connection numbers correspond to the table entry
numbers.
ID Identifies the Diffie-Hellman group.
Status Identifies the Diffie-Hellman status:
1—768-bit Diffie-Hellman prime modulus group.
2—1024-bit Diffie-Hellman prime modulus group.
The following example shows typical output from the show crypto engine connections
dropped-packet command:
Router# show crypto engine connections dropped-packet
Router#
Field Description
Interface Interface involved in the encrypted session connection.
IP-Address IP address of the interface.
Drop Count Total number of dropped packets since the last reset of the
router.
The following example shows typical output for the show crypto engine connections flow command:
Router# show crypto engine connections flow
Router#
Field Description
flow_id Unique identifier for this flow.
ah_conn_id Unique identifier for the flow’s Authentication Header.
esp_conn_id Unique Identifier for the flow’s Encapsulating Security
Protocol (ESP).
comp_spi Security Parameter Index (SPI)—An arbitrary number that
unique identifies the flow’s security association.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Note For information about these additional commands, see the IP Security and Encryption section in the
Cisco IOS Security Command Reference.
Examples The following example shows a typical display from the show crypto ipsec client ezvpn command for
an active virtual private network (VPN) connection when the router is in client mode:
Router# show crypto ipsec client ezvpn
The following example shows a typical display from the show crypto ipsec client ezvpn command for
an active VPN connection when the router is in network-extension mode:
Router# show crypto ipsec client ezvpn
Mask : 255.255.255.128
Protocol : 0x0
Source Port: 0
Dest Port : 0
Router#
The following example shows a typical display from the show crypto ipsec client ezvpn command for
an inactive VPN connection:
Router# show crypto ipsec client ezvpn
Table 0-154 describes the fields shown by the show crypto ipsec client ezvpn command:
Field Description
Current State Displays whether the VPN tunnel connection is active or idle. Typically, when
the tunnel is up, the current state is IPSEC ACTIVE.
Last Event Displays the last event performed on the VPN tunnel. Typically, the last event
before a tunnel is created is SOCKET UP.
Address Displays the IP address used on the outside interface.
Mask Displays the subnet mask used for the outside interface.
DNS Primary Displays the primary domain name system (DNS) server provided by the
dynamic host configuration protocol (DHCP) server.
DNS Secondary Displays the secondary DNS server provided by the DHCP server.
Domain Name Displays the domain name provided by the DHCP server.
NBMS/WINS Displays the primary NetBIOS Microsoft Windows Name Server provided by the
Primary DHCP server.
NBMS/WINS Displays the secondary NetBIOS Microsoft Windows Name Server provided by
Secondary the DHCP server.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Command Description
crypto ipsec client (Interface configuration mode) Assigns a Cisco Easy VPN Remote
ezvpn (interface configuration to an interface.
configuration)
crypto ipsec client Manually connects to a specified IPSec VPN tunnel.
ezvpn connect
ip http ezvpn Enables the Cisco Easy VPN Remote web server interface.
show crypto ipsec Displays the specific configuration for one or all transformation sets.
transform
New Commands
Modified Commands
Replaced Commands
show debug
To display current debugging information that includes PacketCable COPS messages on the Cisco
CMTS, use the show debug command in privileged EXEC mode.
show debug
Usage Guidelines For additional information about this feature and related commands, refer to the following document on
Cisco.com:
• COPS Engine Operation on the Cisco CMTS
Examples The following example illustrates the use of the show debug command in relation to the COPS Engine
Operation feature on the Cisco CMTS.
Router# show debug
PacketCable Client:
Pktcbl COPS msgs debugging is on
PacketCable specific:
Debugging is on for Subscriber 68.1.2.4, Mask 255.255.255.255
SLOT 6/0: Nov 19 04:57:09.219: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered
Cable Modem 0002.8a8c.8c1a
SLOT 6/0: Nov 19 04:57:12.279: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered
Cable Modem 0002.8a8c.92ae
*Nov 19 04:57:19.751: PktCbl(cops): Received callback [code 2, handle: 0x63982B08] from
COPS engine
*Nov 19 04:57:19.751: PktCbl(cops): Received a COPS DEC message, flags is 0x1
*Nov 19 04:57:19.755: PktCbl(cops): Received callback [code 2, handle: 0x63982B08] from
COPS engine
*Nov 19 04:57:19.755: PktCbl(cops): Received a COPS DEC message, flags is 0x1
*Nov 19 04:57:19.755: PktCbl(cops): Received callback [code 2, handle: 0x63982B08] from
COPS engine
*Nov 19 04:57:19.755: PktCbl(cops): Received a COPS DEC message, flags is 0x1
*Nov 19 04:57:19.755: PktCbl(cops): Received callback [code 2, handle: 0x63982B08] from
COPS engine
*Nov 19 04:57:19.755: PktCbl(ndle: 0x63982B08] from COPS engine
show depi
To display Downstream External PHY Interface (DEPI) information, use the show depi command in
privileged EXEC mode.
Examples The following example shows sample output of the show depi tunnel command for all the active control
connections:
Router# show depi tunnel
LocTunID RemTunID Remote Name State Remote Address Sessn L2TP Class/
Count VPDN Group
1834727012 3849925733 RFGW-10 est 1.3.4.155 1 rf6
The following example shows sample output of the show depi tunnel [depi-tunnel-name] [verbose]
command for a specific active control connection identified by the depi-tunnel-name:
Router# show depi tunnel 1834727012 verbose
The following example shows sample output of the show depi session command for all the established
DEPI data sessions:
Router# show depi session
The following example shows sample output of the show depi session [session-id] [verbose] command
for a specific established DEPI data session identified by the session-id:
Router# show depi session 1252018468 verbose
The following example shows sample output of the show depi session command for all the configured
DEPI data sessions:
Router# show depi session configured
Table 155 describes the major fields shown in the show depi command display:
Field Description
LocTunID Identifier of the local tunnel.
RemTunID Identifier of the remote tunnel.
Remote Name Name of the remote tunnel.
State State of the tunnel.
Remote Address IP address of the remote tunnel.
Session Count Number of sessions.
L2TP Class/VPDN L2TP class name for the tunnel.
Group
LocID Identifier of the session.
RemID Identifier of the remote session.
TunID Identifier of the tunnel.
Username, Intf/Vcid, Username or the identifier of the interface.
Circuit
State State of the session.
Last Chg Last state change timestamp.
Uniq ID Unique identifier of the QAM channel.
Session Name Name of the session.
State State of the session.
Reason Reason for the current state of the session.
Time Timestamp of the session.
Related Commands
Command Description
depi-tunnel Creates a template of DEPI tunnel configuration
settings that can be inherited by different pseudowire
classes.
rf-channel depi-tunnel Binds the depi-tunnel to an rf-channel on a shared port
adapter (SPA).
controller modular-cable Enters controller configuration mode to configure the
SPA controller.
show dhcp
To display the current Dynamic Host Configuration Protocol (DHCP) settings on point-to-point
interfaces, use the show dhcp command in privileged EXEC mode.
Cisco uBR904, uBR905, uBR924, uBR925 cable access routers, Cisco CVA122 Cable Voice Adapter
Usage Guidelines You can use this command on any point-to-point type of interface that uses DHCP for temporary IP
address allocation.
Examples The following is typical output from the show dhcp lease command:
Router# show dhcp lease
Field Description
Temp IP addr IP address leased from the DHCP server for the cable interface.
Temp subnet mask Temporary subnet mask assigned to the cable interface.
Field Description
DHCP Lease server IP address of the DHCP server that assigned an IP address to this client.
state Current state of this client (the cable interface). Possible states are Bound,
Renew, or Rebinding. For descriptions of these states, see RFC 2131.
DHCP transaction id Unique number established by the router before the first request message is
sent to the DHCP server. The same transaction ID is used as long as the
lease keeps getting renewed and is valid. If a new “discover” message is
sent, a new transaction ID is used.
Lease Time (in seconds) for which the leased IP address is valid; the duration of
the lease.
Renewal Time interval (in seconds) from address assignment until the client
transitions to the renewing state. When the renewal (T1) time expires, the
client sends a unicast dhcprequest message to the server to extends its lease.
The default value of this timer is 0.5 times the duration of the lease.
Rebind Time interval (in seconds) from address assignment until the client
transitions to the rebinding state and sends a broadcast dhcprequest message
to any DHCP server to extends its lease. The default value of this timer (T2)
is 0.875 times the duration of the lease.
Temp default-gateway IP address of the router closest to this client on the network.
addr
Next timer fires after Time in hours, minutes, and seconds until the next timer expires.
Retry count Number of times the client has sent any message to the DHCP server—most
likely a request message to extend its lease. When the lease is renewed, the
Retry count is reset to 0.
Client-ID MAC address (with optional media type code) that uniquely identifies the
client on the subnet for binding lookups.
The following example shows typical output for the show dhcp server command:
Router# show dhcp server
Field Description
DHCP server MAC address used by the DHCP server.
Leases Number of current leased IP addresses.
Offers Number of offers for an IP address sent to a proxy client from the server.
Field Description
Requests Number of requests for an IP address to the server.
Acks Number of acknowledge messages sent by the server to the proxy client.
Naks Number of not acknowledge messages sent by the server to the proxy client.
Declines Number of offers from the server that have been declined by the proxy
client.
Releases Number of times IP addresses have been relinquished gracefully by the
client.
Bad Number of bad packets received due to wrong length, wrong field type, or
other causes.
TFTP Server Name Name (if any) configured for the server providing TFTP downloads to the
CM.
TIME0 IP address of the primary Time-of-Day (ToD) server.
TIME1 IP address of the secondary ToD server.
Subnet Subnet containing the DHCP server.
Tip In Cisco IOS Release 12.2(8)T and later releases, you can add a timestamp to show commands using the
exec prompt timestamp command in line configuration mode.
Usage Guidelines The level of diagnostic tests which run at bootup can be either configured as complete or minimal. To
configure the bootup level, use the diagnostic bootup level command in global configuration mode. The
show diagnostic bootup level command is used to display the currently configured bootup diagnostic
level.
Examples The following example shows a sample output of the show diagnostic bootup level command on the
Cisco uBR10012 Router:
Router# show diagnostic bootup level
Current bootup diagnostic level: complete
show diagnostic content [all | bay slot/bay | slot slot-no | subslot slot/subslot]
Syntax Description all Displays information about available tests for all modules.
bay slot/bay Indicates the card slot and bay number of the SPA for which the
available test content details is displayed. The bay keyword is used to
refer a SPA on the router. The valid range for the slot number is from 1
to 8 and 0 to 3 for the bay number.
slot slot-no Indicates the slot number of the full-height line card for which the
available test content details is displayed. The slot keyword is used to
refer a full-height line card on the router. The valid range for slot is 1 to
8.
subslot slot/subslot Indicates the slot and subslot number of half-height line card for which
the available test content details has to be displayed. The subslot
keyword is used to refer a half-height line card on Cisco uBR10012
Router. The valid range for the slot number is from 1 to 8 and 0 to 1 for
the subslot number.
Usage Guidelines For each available diagnostic test, a set of attributes is displayed as a series of characters in the Attributes
field of the command output. An asterisk (*) in the character location indicates that the attribute is not
applicable to the test. The following set of attributes is displayed:
Attribute Description
M Test runs when the bootup diagnostic level is set to either Minimal or
Complete.
C Test runs when the bootup diagnostic level is set to Complete.
B Test runs when the diagnostic ondemand command is executed. Indicates
that the test is a basic ondemand test.
P Test runs on a port, not the entire device (per-port test).
Attribute Description
V Test runs on the entire device (per-device test).
D Test disrupts the network traffic (disruptive test).
N Test runs when the system is online without disrupting the network traffic
(non disruptive test).
S If the card under test is a standby card, only the standby card runs the test.
The test does not run from the active card. If the card under test is an active
card, the active card runs the test on itself.
X Test is not a health-monitoring test.
F Monitoring interval of the test cannot be modified by the user (fixed
monitoring test).
E User cannot disable the test (always enabled test).
A Monitoring is active for this test.
I Monitoring is inactive for this test.
If a test is configured to run periodically, the interval will be displayed in the Test Interval field of the
command output in the format dd hh:mm:ss.ms, indicating days, hours, minutes, seconds, and
milliseconds. For example, the test interval of a test that runs every 15 minutes will be displayed as
000 00:15:00.00. The test interval of a test that runs every 14 days will be displayed as 014 00:00:00.00.
Examples This example shows a sample output of the show diagnostic content bay 1/0 command that displays the
test suite, monitoring interval, and test attributes for bay 1/0 on the Cisco uBR10012 Universal
Broadband Router.
Router# show diagnostic content bay 1/0
Table 158 describes the fields shown in the show diagnostic content bay displays.
Field Description
ID The identification number.
Test Name The name of the test that is run on the specific bay.
Attributes The test attribute for the specific bay.
Test Interval The test interval in the dd hh:mm:ss.ms format, indicating days, hours,
minutes, seconds, and milliseconds.
This example shows a sample output of the show diagnostic content subslot 8/0 command that displays
the test suite, monitoring interval, and test attributes for subslot 8/0 on the Cisco uBR10012 Universal
Broadband Router.
Router# show diagnostic content subslot 8/0
Command Description
show diagnostic status Displays the running diagnostics tests.
diagnostic ondemand Configures the on-demand diagnostics.
diagnostic event-log size Modifies the diagnostic event-log size dynamically.
diagnostic start Runs the specified diagnostic test.
diagnostic stop Stops the testing process.
Syntax Description slot Specifies that the status information will be viewed for a line card in
a full slot.
subslot Specifies that the status information will be viewed for a line card in
a subslot.
slot-number Specifies the slot number of the line card whose status information
will appear in the command output.
subslot-number Specifies the subslot number of the line card whose status
information will appear in the command output.
detail Displays the status information and the detailed test results of the
specified line card in the command output.
Usage Guidelines The show diagnostic ood-status output discloses if a line card supports Field Diagnostic testing and if
the line card has already downloaded a Field Diagnostic image. Therefore, the show diagnostic
ood-status command is useful as a reference before loading the Field Diagnostic image onto the line
card.
It is important to note that the show diag and show diagnostic commands produce completely different
outputs. Therefore, the show diagnostic output cannot be gathered using show diag because the
autocomplete function will generate the show diag, not the show diagnostic, output. If you want to
abbreviate the show diagnostic command, the shortest possible abbreviation is show diagn.
Examples In the following example, the show diagnostic ood-status command is used to view status information
of all the line card in the uBR10012 router.
Router# show diagnostic ood-status
Load for five secs: 0%/0%; one minute: 1%; five minutes: 1%
Time source is hardware calendar, *05:56:50.835 EDT Thu Nov 5 2009
Field Description
Slot Identifies the slot on the router.
Card Description A text explanation of the line card in the specified slot.
FDiag Support Indicates whether the line card in the specific slot supports
Field Diagnostic testing.
• Yes—the line card in the slot supports Field Diagnostic
testing.
• No—the card in the slot does not support Field
Diagnostic testing.
Loaded Image Type Specifies the run-time image for each line card.
• Field Diag—Indicates that the Field Diagnostic image is
loaded on the line card. A line card will either have the
Field Diagnostic or LCDOS image.
• IOS—Specifies that the processor is running Cisco IOS.
• LCDOS—Line card DOS. The LCDOS image is the
image the line card is running during normal router
operation. It is removed temporarily when a Field
Diagnostic image is loaded onto the line card and loaded
back onto a line card when a Field Diagnostic image is
unloaded.
Note The LCDOS image is not loaded on cable line cards.
Field Description
Overall Diag Result Displays the result of the last performed Field Diagnostic
test, assuming the Field Diagnostic image has not been
removed since the last test.
• Pass—This line card passed the last diagnostic test.
• Fail—At least one Field Diagnostic test failed during the
last diagnostic test.
• N/A—This line card has not been tested.
Current Card State The current card state:
• Diag Ready—A diagnostic image is loaded onto the line
card and Field Diagnostic tests can be run.
• Running Diag—A diagnostic image is loaded on to the
line card and is currently being run.
• Offline—The line card is not currently passing traffic
and no Field Diagnostic image has been downloaded
onto the line card.
• Online—The line card is active and can pass traffic.
In the following sample output, the test results per line card is displayed when the show diagnostic
ood-status command is used along with subslot and detail keywords. The output displays diagnostic
status of the line card along with details of the tests being run and their status.
Router# show diagnostic ood-status subslot 6/0 detail
Router#
Table 160 show diagnostic ood-status subslot x/y detail Field Descriptions
Field Description
Current card state Specifies the card state.
ID The test identification number.
Test Name The name of the test.
Selected to Run Specifies whether the test was specified to run. Y indicates
the test will be run and N indicates the test will not be run.
Test Status Provides the current test status.
show diagnostic result [[bay slot/bay | slot slot-no | subslot slot/subslot] {detail | test {test-id |
test-id-range | all}} | all]
Syntax Description bay slot/bay (Optional) Indicates the card slot and bay number for which the
diagnostic test results are displayed. The bay keyword is used to refer a
SPA on Cisco uBR10012 Universal Broadband Router. The valid range
to specify slot is 1 to 8 and the valid range for bay is 0 to 3.
slot slot-no (Optional) Indicates the slot number of the full-height line card for
which the diagnostic test results have to be displayed. The slot keyword
is used to refer a full-height line card on Cisco uBR10012 Universal
Broadband Router. The valid range for the slot number is from 1 to 8.
subslot slot/sub-slot (Optional) Indicates the slot and subslot number of the half-height line
card for which the diagnostic test results have to be displayed. The
subslot keyword is used to refer a half-height line card on Cisco
uBR10012 Router. The valid range to specify slot is 1 to 8 and the valid
range for sub-slot is 0 to 1.
all (Optional) Displays diagnostic test results for all the SPAs, full-height
line cards, and half-height line cards.
list List of modules in the following format:
• Entries separated by a comma, for example, 1,4,6-10.
• Ranges specified with a hyphen, for example, 1-4,6-10.
slot Single module by slot number.
slot/subslot Single sub module by slot number and subslot or bay within the module.
detail (Optional) Displays the detailed test results. The detail keyword is used
along with the bay, slot, or subslot keywords to provide detailed test
result information for a SPA, full-height line card, or half-height line
card.
test test-id (Optional) Displays test results only for the specified test-ids.
test test-id-range (Optional) Displays test results for the specified range of test ids.
test all (Optional) Displays the test results for all the tests running on the SPA,
full-height line card, or half-height line card.
Usage Guidelines In the command output, the possible testing results are as follows:
• Passed (.)
• Failed (F)
• Untested (U)
To display the results of a specific diagnostic test, specify the test-id number using the test test-id
keyword and argument. The test-id numbers for available diagnostic tests are displayed in the output of
the show diagnostic content command.
You can use the show diagnostic description command to see a detailed description of a diagnostic test.
The command syntax to refer a line card or SPAs is different on Cisco uBR10012 Router. The keyword
is slot x for a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.
Note To view the diagnostic test results for a SPA, full-height line card, or half-height line card use the show
diagnostic result command along with the bay, slot, or subslot keywords respectively.
The GOLD test cases used to poll for system errors in Cisco IOS Software Release 12.2(33)SCC are
Low Latency Queueing (LLQ) drop, Cable Line Card (CLC) memory leak, and Guardian index leak
tests.
Examples The following example shows a sample output of the show diagnostic result all command. The output
displays a summary of test results on all the SPAs, full-height line cards, and half-height line cards on
the Cisco uBR10012 Router:
Router# show diagnostic result all
1) TestJacketSample --------------------------> U
1) TestModenaSample --------------------------> U
2) TestModenaLLQDrops ------------------------> .
1) TestSampleProxy ---------------------------> U
2) Test520LLQDrops:
Port 0 1 2 3 4
-------------------
. . . . .
3) TestBlazeIndexLeak ------------------------> U
4) TestMemLeaks ------------------------------> .
1) TestSampleProxy ---------------------------> U
2) Test520LLQDrops:
Port 0 1 2 3 4
-------------------
. . . . .
3) TestBlazeIndexLeak ------------------------> .
4) TestMemLeaks ------------------------------> .
1) TestSampleProxy ---------------------------> U
2) Test520LLQDrops:
Port 0 1 2 3 4
-------------------
. . . . .
3) TestBlazeIndexLeak ------------------------> U
4) TestMemLeaks ------------------------------> .
The following example shows a sample output of the show diagnostic result subslot 5/0 detail
command. The command output provides useful details such as overall diagnostic results and the
time-related values of various important parameters, which help in identifying and resolving the issue:
Router# show diagnostic result subslot 5/0 detail
1) TestSampleProxy ---------------------------> U
Error code ----------------------------> 0 (DIAG_SUCCESS)
2) Test520LLQDrops:
Port 0 1 2 3 4
-------------------
. . . . .
Error code ----------------------------> 0 (DIAG_SUCCESS)
Total run count -----------------------> 17
Last test execution time --------------> Aug 11 2009 09:42:22
First test failure time ---------------> n/a
Last test failure time ----------------> n/a
Last test pass time -------------------> Aug 11 2009 09:42:22
Total failure count -------------------> 0
Consecutive failure count -------------> 0
___________________________________________________________________________
3) TestBlazeIndexLeak ------------------------> U
Error code ----------------------------> 0 (DIAG_SUCCESS)
Total run count -----------------------> 1
Last test execution time --------------> Aug 11 2009 00:42:19
First test failure time ---------------> n/a
Last test failure time ----------------> n/a
Last test pass time -------------------> Aug 11 2009 00:42:19
Total failure count -------------------> 0
Consecutive failure count -------------> 0
___________________________________________________________________________
4) TestMemLeaks ------------------------------> .
Error code ----------------------------> 0 (DIAG_SUCCESS)
Total run count -----------------------> 7
Last test execution time --------------> Aug 11 2009 06:42:19
First test failure time ---------------> n/a
Last test failure time ----------------> n/a
Last test pass time -------------------> Aug 11 2009 06:42:19
Total failure count -------------------> 0
Consecutive failure count -------------> 0
___________________________________________________________________________
Command Description
diagnostic start Runs the specified diagnostic test.
diagnostic stop Stops the testing process.
show diagnostic content Displays the available diagnostic tests.
module
diagnostic bootup level Configures the diagnostic bootup level.
diagnostic event-log size Modifies the diagnostic event-log size dynamically.
diagnostic monitor Configures the health-monitoring diagnostic testing.
diagnostic ondemand Configures the on-demand diagnostics.
diagnostic schedule Sets the scheduling of diagnostic testing for a specific bay, slot, or
subslot.
show diagnostic schedule [all | bay slot/bay | slot slot-no | subslot slot/subslot]
Syntax Description all Displays the scheduled diagnostic tasks for all the installed SPAs,
full-height line cards, and half-height line cards on the Cisco uBR10012
Universal Broadband Router.
bay slot/bay (Optional) Indicates the card slot and bay number for which the
scheduled diagnostic tasks is displayed. The bay keyword is used to
refer a SPA on the router. The valid range for the slot number is from 1
to 8 and 0 to 3 for the bay number.
slot slot-no (Optional) Indicates the slot number of the full-height line card for
which the scheduled diagnostic tasks is displayed. The slot keyword is
used to refer a full-height line card on the router. The valid range for slot
is 1 to 8.
subslot slot/sub-slot (Optional) Indicates the slot and subslot number of the half-height line
card for which the scheduled diagnostic tasks have to be displayed. The
subslot keyword is used to refer a half-height line card on the router. The
valid range for the slot number is from 1 to 8 and 0 to 1 for the subslot.
Usage Guidelines Diagnostic tests for a specific bay, slot, or subslot can be scheduled daily, weekly, or on specific dates
and time using the diagnostic schedule command from global configuration mode. The show diagnostic
schedule command output displays the diagnostic tests that have been scheduled for the bay, slot, or
subslot using the command diagnostic schedule.
Examples This example shows a sample output of the show diagnostic schedule slot 1 command that displays
diagnostic tasks scheduled for slot 1 on the Cisco uBR10012 Universal Broadband Router:
Router# show diagnostic schedule slot 1
This example shows a sample output of how to display the diagnostic tasks scheduled for all the bays,
full-height line cards, and half-height line cards installed on the Cisco uBR10012 Universal Broadband
Router:
Router# show diagnostic schedule all
Syntax Description severity (Optional) String that identifies the severity of an alarm. The default severity
level is info, which shows all alarms. Severity levels are defined as the
following:
• critical—Only critical alarms are shown.
• major—All major and critical facility alarms are shown.
• minor—All minor, major, and critical facility alarms are shown.
• info—All facility alarms are shown.
Usage Guidelines When a severity level is identified, statuses of alarms at that level and higher are shown. For example,
when you set a severity of major, all major and critical alarms are shown.
The show facility-alarm status command does not show the real status of the upstream channel
connector when frequency stacking is configured on the upstream channel.
Note The show facility-alarm status command does not show the critical alarm temperature thresholds. You
can display these values using the show running-config | include facility command. If this does not
display any commands for critical alarms, then the temperature thresholds are set at their default values.
For additional information on Frequency Stacking feature, refer to the Virtual Interfaces and Frequency
Stacking Configuration on MC5x20S and MC28U Linecards document on Cisco.com.
Examples The following example shows a typical display of the show facility-alarm status command:
Router# show facility-alarm status
Thresholds:
Intake minor 40 major 49 critical 72
Core minor 45 major 53 critical 85
Router#
Field Description
System Totals Total number of alarms generated, identified by severity.
Source Interface from which the alarm was generated.
Severity Severity level of the alarm generated.
ACO Alarm cutoff. It could be “NORMAL” or “CLEARED”.
Description [Index] Type of the alarm and the index of the alarm type. The index
can be any number based on the number of alarm types that
the device supports.
show frame-clocks
To display information about the midplane time-division multiplexing (TDM) clock reference, use the
show frame-clocks command in privileged EXEC mode.
show frame-clocks
Examples The following sample output from the show frame-clocks command shows that there are no clock
sources configured and the clock card is the default clock source:
Router# show frame-clocks
Table 0-162 describes the fields displayed by the show frame-clocks command:
Table 0-162 show frame-clocks Field Descriptions
Field Description
Priority 1-4 clock source The configuration of the four network clock sources.
Current clock source The current clock source, its input, and priority. In this
example, the clock card is providing the clock source.
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
show hccp
To display information about groups associated with cable interfaces, use the show hccp command in
user EXEC or privileged EXEC mode.
show hccp group member [mac-address classifier | channel-switch | host | modem | qosparam |
service-flow sfid [classifier] | sid]
Syntax Description brief (Optional) Displays a brief summary of the groups, configuration types,
member numbers, and status for cable interfaces. You can also use this
option when displaying information for a specific group.
channel-switch (Optional) Displays information about the channel-switch configuration.
detail (Optional) Displays a detailed summary of the groups, configuration types,
member numbers, and status for cable interfaces, as well as the CLI
commands that are being synchronized across interfaces.
group (Optional) Specifies a group number to be displayed. The valid range is 1
to 255.
member (Optional, when displaying information for a particular group) Specifies the
member number of the Inter-database for the specified group. The valid
range is 1 to 255.
mac-address classifier (Optional) Displays classifier information for the specified MAC address.
channel-switch (Optional) Displays channel-switch information for this particular group
and member.
host (Optional) Displays host information for this particular group and member.
modem (Optional) Displays cable modem information for this particular group and
member.
qosparam (Optional) Displays quality of service (QoS) parameter information for this
particular group and member.
service-flow sfid (Optional) Displays service flow and classifier information for the specified
classifier service flow ID (SFID) for this particular group and member.
sid (Optional) Displays service ID (SID) information for this particular group
and member.
Release Modification
12.2(11)BC1 Support was added for the Cisco uBR-RFSW N+1 (1:n) RF Switch with the
Cisco uBR7246VXR router and Cisco uBR-MC16C, Cisco uBR-MC16S,
and Cisco uBR-MC28C cards.
12.2(15)BC2 The output of the show hccp detail command was changed to show separate
lists of the critical and non-critical CLI commands that are being
synchronized for each Working and Protect interface and subinterface.
12.2(33)SCB This command was integrated into Cisco IOS Release 12.2(33)SCB and the
output of the show hccp detail command was changed to show CMTS
interface pre-critical config information.
12.2(33)SCC This command was integrated into Cisco IOS Release 12.2(33)SCC.
Examples The following examples are from the show hccp and show hccp brief commands for the entire chassis:
Router# show hccp
In Cisco IOS Release 12.2(8)BC2 and later 12.2 BC releases, the brief option also shows the amount of
time left before the next resynchronization and the time left before a restore:
Router# show hccp brief
Router#
The following example shows a sample output for the show hccp channel-switch command, displaying
the groups and module numbers for each configured member:
Router# show hccp channel-switch
module 9, normal
module 13, normal
Grp 1 Mbr 7 Protect channel-switch:
"uc" - disabled, frequency 555000000 Hz
"rfswitch" - module 1, normal
module 3, normal
module 5, normal
module 7, normal
module 11, normal
Grp 1 Mbr 5 Protect channel-switch:
"uc" - disabled, frequency 555000000 Hz
"rfswitch" - module 1, normal
module 3, normal
module 5, normal
module 7, normal
module 11, normal
Router#
The following example shows the first part of the display for the detail option of this command, which
first displays chassis-wide configuration information. The command then displays the CLI configuration
commands that are being synchronized for each subinterface.
Router# show hccp detail
corr-fec 1, uncorr-fec 1
upstream 2 -
hop-priority frequency modulation channel-width
upstream 3 -
frequency 16000000, power level 0
upstream 3 -
modulation-profile 1, channel-width 3200000
upstream 3 -
cnr-profile1 25, cnr-profile2 15
corr-fec 1, uncorr-fec 1
upstream 3 - hop-priority frequency modulation channel-width
sub-interface 200 config:
ip address 10.23.240.1 255.255.255.0
ip address 213.57.42.254 255.255.255.128 secondary
ip helper-address 213.57.75.70
ip helper-address 213.57.75.66, ip access-group 87 in, ip access-group 87 out
cable helper-address 213.57.75.70
cable helper-address 213.57.75.66
cable arp, proxy-arp,
cable ip-multicast-echo,
cable dhcp-giaddr policy,
sub-interface 8 config:
ip address 10.23.128.1 255.255.240.0
ip address 62.90.198.254 255.255.255.0 secondary
ip helper-address 213.57.75.70
ip helper-address 213.57.75.66, ip access-group BARAK in, ip access-group
ANTI_TRACE out
cable helper-address 213.57.75.70
cable helper-address 213.57.75.66
cable arp, proxy-arp,
cable ip-multicast-echo,
cable dhcp-giaddr policy,
sub-interface 1 config:
ip address 3.0.1.1 255.255.0.0
ip address 99.99.1.1 255.255.255.0 secondary
ip address 99.99.2.1 255.255.255.0 secondary
ip address 99.99.3.1 255.255.255.0 secondary
ip address 99.99.4.1 255.255.255.0 secondary
ip helper-address 1.9.62.10
ip helper-address 1.9.62.11, ip access-group no_netbios2 in, ip access-group
no_netbios2 out
ip pim sparse-dense-mode
cable arp,
cable ip-multicast-echo
. . .
Router#
In Cisco IOS Release 12.2(15)BC2 and later releases, the show hccp detail command shows the critical
and non-critical synchronized CLI commands in separate lists for each cable interface and subinterface:
Router# show hccp detail
Member 5 standby
target ip address: protect 222.1.1.9, working 222.1.1.9
channel-switch "uc" (wavecom-hd, 1.10.45.11/7, 1.10.45.11/4) enabled
channel-switch "rfsw" (rfswitch-group, 1.10.52.33/0x40100000/8) enabled
tran #: SYNC 0, last SYNC_ACK 9
hold timer expires in 00:00:13.756
Interface Generic Critical Config
========================
int Cable6/0/0
mac-address 00e0.6666.1270
end
end
Router#
In Cisco IOS Release 12.2(33)SCB and later releases, the show hccp detail command shows CMTS
interface pre-critical configuration information as part of the critical and non-critical synchronized CLI
commands:
Router# show hccp detail
=================================
int Cable6/0/0
end
Member 5 standby
target ip address: protect 222.1.1.9, working 222.1.1.9
channel-switch "uc" (wavecom-hd, 1.10.45.11/7, 1.10.45.11/4) enabled
channel-switch "rfsw" (rfswitch-group, 1.10.52.33/0x40100000/8) enabled
tran #: SYNC 0, last SYNC_ACK 9
hold timer expires in 00:00:13.756
Interface Generic Critical Config
========================
int Cable6/0/0
mac-address 00e0.6666.1270
end
Router#
The following shows an example of the show hccp command to display QoS parameters for a particular
member of a particular group:
Router# show hccp 1 1 qosparam
Cable5/0/0:
Index Name Dir Sched Prio MaxSusRate MaxBurst MinRsvRate
1 US BE 0 64000 0 0
2 DS BE 0 1000000 0 0
3 US BE 7 1024000 1522 0
4 DS BE 0 10000000 1522 0
Router#
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
The following example shows a detailed display for the Cisco uBR10-MC5X20S cable interface line
card:
Router# show hccp detail
mac-address 0005.00e4.1236
cmts config:
resolve sid, dci-response success,
downstream - frequency 441000000, channel id 0
downstream - insertion_invl auto min = 60, max = 480
downstream - rf-shutdown, rf-power 48
upstream 0 - frequency 11408000, power level 0
upstream 0 - modulation-profile 1, channel-width 3200000
upstream 0 - cnr-profile1 25, cnr-profile2 15
corr-fec 1, uncorr-fec 1
Note For cable interfaces with an integrated upconverter, the line showing the RF power will show
rf-shutdown when the upconverter has been powered off.
The following example shows the service flow information for a cable interface line card on group 2
member 50:
Router# show hccp 2 50 service-flow
The following example shows the cable modem information for a cable interface line card on group 2
member 50:
Router# show hccp 2 50 modem
Syntax Description interface The cable interface for which you want to display HCCP group information.
The information presented includes HCCP groups, configuration types,
member numbers, status, authentication algorithms, authentication key
chains, HCCP timers, Ip address assignments, and downstream switch
designations for the specified cable interface.
brief (Option) Displays a brief summary of the HCCP groups, configuration
types, member numbers, and status for a specified cable interface.
detail (Option) Displays a detailed summary of the HCCP groups, configuration
types, member numbers, and status for a specified cable interface.
Examples The following examples are from the show hccp interface cable 4/0 and show hccp interface cable 4/0
brief commands:
Router# show hccp interface cable 4/0
Router#
In Cisco IOS Release 12.2(8)BC2 and later 12.2 BC releases, the brief option also shows the amount of
time left before the next resynchronization and the time left before a restore:
Router# show hccp interface cable 4/0 brief
Router#
Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to
show commands using the exec prompt timestamp command in line configuration mode.
Usage Guidelines Other than the FPD version information, the output for this command can also contain useful
FPD-related notes.
For more information about FPD upgrades on SPA interface processors (SIPs) and shared port adapters
(SPAs), see the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide.
In Cisco IOS Release 12.2(33)SCB, the FPD image upgrade is supported only for the SPAs inserted in
the SIP-600 jacket card on a Cisco uBR10012 router.
The following example shows that all FPDs for the port adapter have the minimum required version. For
the NPE-400, the “###” characters in the ID-Name, Current Version, and Min, Required Version fields
indicate that FPD does not apply to the NPE-400.
Router# show hw-module all fpd
The following example shows FPD image file versions that require an upgrade (indicated by the asterisk)
for two SIPs in the Cisco 7600 series router. The SIPs are disabled due to the version mismatch.
Router# show hw-module all fpd
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and
3 can be used for SIPs.
subslot The subslot where a SIP resides. On the Cisco uBR10012 router, subslot 0
is always specified.
bay The bay in a SIP where a SPA is located. Valid values are 0 (upper bay)
and 1 (lower bay).
port Specifies the interface number on the SPA.
all Specifies that the displayed information will be for both bay 1 and bay 0
if Wideband SPAs are installed in both bays.
show-type The type of information to display. Valid values are association, config,
counters, and mapping. See the Usage Guidelines for more information
on show types.
wideband-channel Displays information for the wideband channel indicated by device-index.
rf-channel Displays information for the RF channel indicated by device-index.
modular-channel Displays information for the narrowband channel indicated by
device-index.
device-index (Optional) The wideband channel number or RF channel number or
Baseline Privacy Interface (BPI) index number.
• When the wideband-channel keyword is specified, valid values for
device-index are 0 to 11.
• When the rf-channel keyword is specified, valid values for
device-index are 0 to 23 depending on how the Wideband SPA is
configured with the annex modulation command.
verbose (Optional) Used with the config keyword. Shows more configuration
information on the wideband channel or RF channel.
Usage Guidelines The type of information that show hw-module bay displays is determined by the value of the show-type
argument. Table 0-1 describes the information shown for each show-type. In the table, the Allowed with
Keyword column indicates whether the show-type can be used with the keyword wideband-channel,
rf-channel or modular-channel.
If device-index is omitted from show hw-module bay, the command displays information for all
wideband channels, RF channels, or BPI+ indexes depending on the keywords used.
The association show-type displays wideband-to-narrowband (traditional DOCSIS) channel association
information only when the cable interface line card and Wideband SPA are physically present in the
CMTS.
Note • If you do not specify the verbose keyword, less detailed configuration information is displayed.
• Changes in Cisco IOS release 12.3(23)BC are not supported in Cisco IOS release 12.2(33)SCA.
Allowed with
show-type Keyword Description
association wideband-channel Displays wideband-to-narrowband (traditional DOCSIS)
channel association information. The association of a
wideband channel to a traditional DOCSIS downstream
channel is made when a primary downstream channel for
the fiber node is configured with the downstream
command.
config wideband-channel or Displays wideband channel or RF channel configuration
rf-channel information depending on the keyword specified.
counters wideband-channel or Displays wideband channel or RF channel statistics
rf-channel depending on the keyword specified.
mapping wideband-channel, Displays mapping of wideband channels to RF channels
rf-channel, or depending on the keyword specified.
modular-channel
Examples The following examples display sample output for the show hw-module bay command for wideband
channel 0 on the Wideband SPA located in slot 1, subslot 0, bay 0:
Router# show hw-module bay 1/0/0 counters wideband-channel 0
SPA WB RF BW %
channel channel
1/0/0 0 0 100
1 100
2 100
3 100
4 100
5 100
6 100
The following example shows sample output for the show hw-module bay command in Cisco IOS
Release 12.3(21)BC:
Router# show hw-module bay 1/0/0 association wideband-channel 0
WB BG Bundle NB NB chan Reserved Avail
channel ID num channel ID CIR CIR
Wideband-Cable1/0/0:0 1 1 Cable6/0/0 251 0 0
The following example shows sample output for the show hw-module bay command inCisco IOS
Release 12.3(23)BC:
Router# show hw-module bay 1/0/0 association wideband-channel 0
WB BG Bundle NB NB chan Reserved Total
channel ID num channel ID CIR CIR
Wideband-Cable1/0/0:0 1 140 Cable6/0/0 30 0 42064200
In the preceding example, the following information is displayed for each wideband channel when the
association keyword is specified.
• WB channel—Wideband-cable interface (wideband channel).
• BG ID—Bonding Group ID for the wideband channel.
• MC BW %—Percentage of rf-channel bandwidth assigned to the corresponding modular-cable
interface.
• Bundle num—The number of the virtual bundle interface in which the wideband channel is a
member.
• NB channel—The slot/subslot/port of the primary downstream channel (narrowband channel or
traditional DOCSIS channel) for the wideband channel.
• NB channel ID—Channel ID for the primary downstream channel.
• Reserved CIR—The reserved committed information rate (CIR).
• Total CIR—The total CIR that is available.
Note For Cisco IOS Release 12.3(21)BC, the descriptions for the Reserved CIR and Available CIR fields are
as follows:
Reserved CIR—The reserved committed information rate (CIR). Because QoS is currently best effort
for wideband traffic, reserved CIR is always 0.
Avail CIR—The part of the CIR that is available. Because QoS is currently best effort for wideband
traffic, available CIR is always 0.
The following examples display show hw-module bay command output for wideband channels (0 to 11)
on the Wideband SPA located in slot 1, subslot 0, bay 0:
Router# show hw-module bay 1/0/0 counters wideband-channel
In the preceding example, the following information is displayed for each wideband channel when the
config keyword is specified.
• WB Channel—Specifies the wideband channel slot, sub-slot, bay and wideband channel number.
• BG ID—Bonding Group ID.
• Bundle num—The number of the virtual bundle interface to which the wideband channel is a
member.
• WB Host Slot/Subslot—The cable interface line card that has been configured for Wideband
protocol operations. See the command modular-host.
• Primary BG—Yes indicates that the wideband channel is a primary bonding group (primary
wideband channel).
The following examples display show hw-module bay command output for RF channel 0 on the
Wideband SPA located in slot 1, subslot 0, bay 0:
Router# show hw-module bay 1/0/0 config rf-channel 0
In the preceding output, these fields provide information on the edge QAM device that is associated with
the RF channel:
• IP Address—The IP address of the edge QAM device.
• MAC address—The MAC address of the next-hop device or edge QAM device.
• UDP port—The UDP port number for the edge QAM device that will be used for this RF channel.
Router# show hw-module bay 1/0/0 config rf-channel 0 verbose
The following example displays the show hw-module bay counters rf-channel command output for the
RF channels of a Cisco Wideband SPA. Activity is seen on channels 1,2, and 3 as the MPEG Mbps field
shows they are each transmitting at about 29 Mbps. Channel 1 is primary-capable as it is transmitting
SYNC packets.
3/3/0 9 0 0 0.000 0 0
3/3/0 10 0 0 0.000 0 0
3/3/0 11 0 0 0.000 0 0
3/3/0 12 0 0 0.000 0 0
3/3/0 13 0 0 0.000 0 0
3/3/0 14 0 0 0.000 0 0
3/3/0 15 0 0 0.000 0 0
3/3/0 16 0 0 0.000 0 0
3/3/0 17 0 0 0.000 0 0
3/3/0 18 0 0 0.000 0 0
3/3/0 19 0 0 0.000 0 0
3/3/0 20 0 0 0.000 0 0
3/3/0 21 0 0 0.000 0 0
3/3/0 22 0 0 0.000 0 0
3/3/0 23 0 0 0.000 0 0
SPA RF WB BW %
channel channel
1/0/0 0 0 100
The following example displays show hw-module bay command output for RF channels on the
Wideband SPA located at slot 1, subslot 0, bay 0. In the example, the output is for only RF channels 0
to 8 because only those RF channels have been associated with a wideband channel. The BW % column
is the percent of the RF channel bandwidth that is assigned to the wideband channel with the cable
rf-channel command.
Router# show hw-module bay 1/0/0 mapping rf-channel
SPA RF WB BW %
channel channel
1/0/0 0 0 100
1/0/0 1 0 100
1/0/0 2 0 100
1/0/0 3 0 100
1/0/0 4 0 100
1/0/0 5 0 100
1/0/0 6 0 100
1/0/0 7 2 100
1/0/0 8 1 100
Syntax Description slot The slot where a SIP resides. On the Cisco uBR10012 router, slots 1 and
3 can be used for a SIP.
subslot The subslot where the Wideband SIP resides. On the Cisco uBR10012
router, subslot 0 is always specified.
bay The bay in the SIP where a SPA is located. Valid values are 0 (upper bay)
and 1 (lower bay).
port Specifies the interface number on the SPA.
all Displays OIR status for all Wideband SPAs in the system.
internal (Optional) Displays detailed diagnostic information. This option is
intended for internal diagnostic use with Cisco technical support
personnel.
Command Default If you do not specify the internal keyword, detailed diagnostic information is not displayed.
Usage Guidelines Use the show hw-module bay oir command to obtain operational status information about a Wideband
SPA. To display information for a specific SPA, specify slot/subslot/bay for the SPA. To display
information for all SPAs in the router, use the all keyword.
The optional internal keyword displays detailed diagnostic information that is recommended only for
use with Cisco technical support personnel.
Table 164 describes the possible values for the Operational Status field in the output.
Examples The following example shows the operational status of a Wideband SPA:
Router# show hw-module bay 1/0/0 oir
The following example shows the operational status of a Wideband SPA when the internal keyword is
specified:
Router# show hw-module bay 1/0/0 oir internal
Cisco 7600 Series Routers, Catalyst 6500 Series Switches, Cisco 12000 Series Routers, and Cisco uBR10012
Universal Broadband Router
Defaults For the Cisco 7304 router, if no location is specified, the output for this command will show information
for all supported card types on the router.
For the Cisco 7600 series routers, Catalyst 6500 series switches, and Cisco 12000 series routers, there
is no default behavior or values.
For more information about FPD upgrades on shared port adapters (SPAs), refer to the Cisco 7600 Series
Router SIP, SSC, and SPA Software Configuration Guide.
Release Modification
12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.
12.2(33)SCB This command was integrated into Cisco IOS Release 12.2(33)SCB.
Usage Guidelines Other than the FPD version information, the output for this command may also contain useful
FPD-related notes.
Cisco 7600 Series Routers, Catalyst 6500 Series Switches, 12000 Series Routers, and Cisco uBR10012 Universal
Broadband Router
If you do not use the all keyword, then you must specify the slot/subslot arguments to select the location
of a particular card. There is no default behavior for this command on the Cisco 7600 series routers.
Displaying Information for all SPAs in the System Example (Cisco 7304 only)
The all keyword is not supported on the Cisco 7304 router.
To display all FPD image file versions for all SPAs on a Cisco 7304 router, enter the show hw-module
subslot fpd command without specifying a slot and subslot. The following example shows all FPD
image file versions on a Cisco 7304 router:
Router# show hw-module subslot fpd
Usage Guidelines From Cisco IOS Release 12.2(33)SCB onwards, the multicast-sessions keyword will not display any
output, though it is available as part of the show interface bundle command.
Examples The following example shows a typical display of the show interface bundle multicast-sessions
command for bundle 1:
Router# show interface bundle 1 multicast-sessions
Syntax Description slot/port Identifies the cable interface and downstream port on the
Cisco uBR7100 series and Cisco uBR7200 series routers.
On the Cisco uBR7100 series router, the only valid value is 1/0. On
the Cisco uBR7200 series router, slot can range from 3 to 6, and port
can be 0 or 1, depending on the cable interface.
slot/subslot/port Identifies the cable interface on the Cisco uBR10012 router. The
following are the valid values:
• slot = 5 to 8
• subslot = 0 or 1
• port = 0 to 4 (depending on the cable interface)
options Cable-specific options are documented in their own command
reference pages:
• show interface cable downstream
• show interface cable intercept
• show interface cable mac-scheduler
• show interface cable monitor
• show interface cable qos paramset
• show interface cable service-flow
• show interface cable sid
• show interface cable signal-quality
• show interface cable upstream
A number of non-cable-specific options are also supported (but not all
are meaningful for cable interfaces):
accounting—Displays the number of packets of each protocol
type that was sent through the interface.
crb—Displays routing and bridging information.
description—Displays the description entered for the interface.
fair-queue—Displays distributed weighted fair queuing (DWFQ)
statistics.
irb—Displays integrated routing bridge information.
mac-accounting—Displays Ethernet MAC accounting
information.
random-detect—Displays weighted random early detection
(WRED) information.
rate-limit—Displays rate-limit information.
shape—Displays Traffic Shape information.
stats—Displays numbers of packets that were switched.
Note For information on the non-cable specific options, see the Cisco IOS Release 12.2 documentation on
Cisco.com and the Customer Documentation CD-ROM.
Examples The following is sample output from the show interface cable command:
CMTS01# show interface cable 6/0
Table 0-165 describes the fields shown in the show interface cable display.
Field Description
Cable slot/port is Indicates whether the interface hardware is currently active or
up/...administratively down taken down by the administrator.
line protocol is Indicates whether the software processes that handle the line
up/...administratively down protocol believe the interface is usable or if it has been taken down
by the administrator.
hardware Hardware type and address.
Internet address Internet address followed by subnet mask.
MTU Maximum transmission unit (MTU) of the interface.
BW Bandwidth of the interface in kilobits per second.
DLY Delay of the interface in microseconds.
Field Description
rely Reliability of the interface as a fraction of 255, calculated as an
exponential average over 5 minutes. (For example, 255/255 is 100
percent reliability.)
load Load on the interface as a fraction of 255, calculated as an
exponential average over 5 minutes. (For example, 255/255 is
complete saturation.)
Encapsulation Encapsulation method assigned to this interface.
ARP type Type of Address Resolution Protocol (ARP) and timeout value
assigned.
Last input Number of hours, minutes, and seconds since the last packet was
successfully received by an interface.
output Number of hours, minutes, and seconds since the last packet was
successfully sent by an interface.
Last clearing of “show interface” Time at which the counters that measure cumulative statistics (such
counters as number of bytes sent and received) were last reset to zero.
Queueing strategy Displays the type of queueing configured for this interface. In the
following example output, the type of queueing configured is