Cmts 12 2sc SCG Cisco
Cmts 12 2sc SCG Cisco
Configuration Guide
Cisco IOS Release 12.2SC
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.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at
www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
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.
Book Title
© 2009-2013 Cisco Systems, Inc. All rights reserved.
CONTENTS
Configuring the Cisco uBR10012 Universal Broadband Router for the First Time 1
Configuring the Cisco uBR7200 Series Universal Broadband Routers for the First Time 23
Configuring the Cisco uBR7200 Series Router Using the Setup Facility 40
Configuring the Cisco uBR7200 Series Router Manually Using Configuration Mode 52
Performing OIR of Cable Interface Line Cards on the Cisco CMTS Routers 57
OIR of Cable Interface Line Cards on the Cisco uBR7200 Series Universal Broadband Routers 57
OIR of Cable Interface Line Cards on the Cisco uBR10012 Universal Broadband Router 58
Contents 61
Additional References 69
Command Reference 70
This chapter describes how to start up and configure the Cisco uBR10012 Universal Broadband Router
as a Cable Modem Termination System (CMTS) for the first time. This chapter contains the following
sections:
Section Purpose
“Preparing for Configuration” Identifies tasks and analysis that you must complete prior to
section on page 2 powering on and configuring the Cisco uBR10012 router.
“Understanding Describes the basic principles of using passwords and
Cisco uBR10012 Router summarizes the initial router configuration utilities that are
Configuration Fundamentals” available to you. The remainder of this chapter provides
section on page 3 instructions for each utility.
“Configuring the Describes how to use the AutoInstall process, which is designed
Cisco uBR10012 Router Using to configure the Cisco uBR10012 router automatically after
AutoInstall” section on page 7 connection to your WAN.
“Configuring the Describes how to use the Setup facility (also called the System
Cisco uBR10012 Router Using the Configuration dialog) for configuring your CMTS, an
Setup Facility” section on page 8 alternative to AutoInstall. The Setup facility supports several
functions so that cable interfaces and cable interface line cards
are fully operational (after initial setup). Use the Setup facility
prior to completing a WAN or LAN connection to your router.
“Configuring the Describes how to configure the Cisco uBR10012 router
Cisco uBR10012 Router Manually manually if you prefer not to use the Setup or AutoInstall
Using Configuration Mode” section facilities.
on page 13
“Removing the Cable Interfaces” Describes how to reset and remove the interfaces on the Cisco
section on page 14 uBR10012 router.
Section Purpose
“Configuring the Cable Interface Provides instructions for using the Setup facility to create an
with the Extended Setup Facility” initial configuration. The extended setup prompts you to
section on page 16 configure each interface on the system.
“Reviewing Your Settings and Provides commands to check your settings and review any
Configurations” section on page 19 changes to your configuration.
• Configuring the CMTS to support IP over the cable plant and network backbone
Caution If you plan to use service-class-based provisioning, the service classes must be configured at the CMTS
before CMs attempt to make a connection.
Note These sections provide minimal configuration instructions. For additional configuration information,
refer to subsequent chapters in this guide. For examples of Cisco uBR10000 series CMTS configuration
files, refer to the “Viewing Sample Configuration Files” section on page 19.
Tip Be sure that you have appropriate addresses and values based on your network before you attempt to
configure the router. Enter the show version command to display the release of Cisco IOS software on
your router.
Step 1 Connect a terminal to the I/O controller console port of the Cisco uBR10012 router and establish a
terminal session. You can open a Terminal application (Hyper Terminal) on a PC as follows:
a. Connect using: Direct to Com 1
b. Set bits per second: 9600
c. Set data bits: 8
d. Set parity: none
e. Set stop bit: 1
f. Set flow control: none
Step 2 Power on the Cisco uBR10000 series. Enter no to choose the normal operating mode of the router. The
user EXEC prompt appears:
Would you like to enter the initial dialog?[yes]: no
Router>
Note For security purposes, the EXEC has two levels of access to commands: user EXEC mode and privileged
EXEC mode. The commands available at the user level are a subset of those available at the privileged
level.
Tip Because many privileged-level EXEC commands are used to set operating parameters, password-protect
these commands to prevent unauthorized use.
At the EXEC prompt, enter one of the following two commands to set password protection:
• enable secret password (which is a very secure, encrypted password)
• enable password (which is a less secure, nonencrypted password)
To gain access to privileged-level commands, enter the desired password.
Note An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters.
An enable password can contain any number of uppercase and lowercase alphanumeric characters. A
number cannot be the first character. Spaces are valid password characters; for example, “two words” is
a valid password. Leading spaces are ignored. Trailing spaces are recognized. Alphanumeric characters
are recognized as uppercase or lowercase.
Passwords should be different for maximum security. If you enter the same password for both during the
setup script, the system accepts it, but you receive a warning message indicating that you should enter a
different password.
Note It is possible to recover the enable or console login password. The enable secret password is encrypted,
however, and must be replaced with a new enable secret password.
Step 1 If you can log in to the router, enter the show version command to determine the existing configuration
register value.
Step 2 Press the Break key to get to the bootstrap program prompt (ROM monitor). You might need to reload
the system image by power cycling the router.
Step 3 Change the configuration register so that the following functions are enabled:
• Break
• Ignore startup configuration
Note The key to recovering a lost password is to set the configuration register bit 6 (0x0040) so that
the startup configuration (usually in NVRAM) is ignored. This allows you to log in without
using a password and to display the startup configuration passwords. Cisco recommends setting
the configuration register to 0x142.
Step 4 Power cycle the router by turning power off and then back on.
Step 5 Log in to the router and enter the privileged EXEC mode.
Step 6 Enter the show startup-config command to display the passwords.
Step 7 Recover or replace the displayed passwords.
Step 8 Change the configuration register back to its original setting.
Note To recover a lost password if Break is disabled on the router, you must have physical access to the router.
Complete the following steps to recover or replace a lost enable, enable secret, or console login
password:
Step 1 Attach an ASCII terminal to the console port on your Cisco uBR10012 router.
Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 2 stop bits.
Step 3 If you can log in to the router as a nonprivileged user, enter the show version command to display the
existing configuration register value. Note the value for later use. If you cannot log in to the router at all,
continue with the next step.
Step 4 Press the Break key or send a Break from the console terminal.
• If Break is enabled, the router enters the ROM monitor, indicated by the ROM monitor prompt
(rommon n>), where n is the number of the command line. Proceed to Step 6.
• If Break is disabled, power cycle the router (turn the router off or unplug the power cord, and then
restore power). Proceed to Step 5.
Step 5 Within 60 seconds of restoring the power to the router, press the Break key or send a Break. This action
causes the router to enter the ROM monitor and display the ROM monitor prompt (rommon 1>).
Step 6 To set the configuration register on a Cisco uBR10012 router, use the configuration register utility by
entering the confreg command at the ROM monitor prompt as follows:
rommon 1> confreg
Answer yes to the enable ignore system config info? prompt and note the current configuration
register settings.
Step 7 Initialize the router by entering the reset command as follows:
rommon 2> reset
The router initializes, the configuration register is set to 0x142, the router boots the system image from
Flash memory and enters the System Configuration dialog (setup), as follows:
Step 12 Scan the configuration file display looking for the passwords; the enable passwords are usually near the
beginning of the file, and the console login or user EXEC password is near the end. The passwords
displayed will look something like this:
enable secret 5 $1$ORPP$s9syZt4uKn3SnpuLDrhuei
enable password 23skiddoo
.
.
line con 0
password onramp
Note The enable secret password is encrypted and cannot be recovered; it must be replaced. The enable and
console passwords can be encrypted text or clear text.
Proceed to the next step to replace an enable secret, console login, or enable password. If there is no
enable secret password, note the enable and console login passwords if they are not encrypted and
proceed to Step 17.
Caution Do not perform the next step unless you have determined that you must change or replace the enable,
enable secret, or console login passwords. Failure to follow the steps as presented here could cause your
router configuration to be erased.
Step 13 Enter the configure memory command to load the startup configuration file into running memory. This
action allows you to modify or replace passwords in the configuration.
Router# configure memory
Change only the passwords necessary for your configuration. You can remove individual passwords by
using the no form of the previous commands. For example, entering the no enable secret command
removes the enable secret password.
Step 16 You must configure all interfaces to not be administratively shut down as follows:
Enter the equivalent commands for all interfaces that were originally configured. If you omit this step,
all interfaces are administratively shut down and unavailable when the router is restarted.
Step 17 Use the config-register command to set the configuration register to the original value noted in Step 3
or Step 7.
Step 18 Press Ctrl-Z or type end to exit configuration mode:
Router(config)# end
Caution Do not perform the next step unless you have changed or replaced a password. If you have skipped
Step 13 through Step 16 previously, then proceed now to Step 20. Failure to observe this sequence
causes the system to erase your router configuration file.
Step 19 Enter the copy running-config startup-config command to save the new configuration to nonvolatile
memory:
Router# copy running-config startup-config
Step 1 Attach the appropriate synchronous serial cable to the synchronous serial interface 0 on the router.
Step 2 Turn the power switch on each power supply to the ON (|) position. This action turns on power to the
router.
The router loads the operating system image from Flash memory; this process can take several minutes.
If the remote end of the WAN connection is connected and properly configured, the AutoInstall process
begins.
Step 3 When the AutoInstall process is completed, use the copy running-config startup-config command to
write the configuration data to the router’s nonvolatile random-access memory (NVRAM):
Router# copy running-config startup-config
Completing this step saves the configuration settings that the AutoInstall process created to NVRAM. If
you fail to do this, your configuration will be lost the next time you reload the router.
Tip The router might take several minutes to determine that AutoInstall is not set up to a remote TCP/IP host.
When the router determines that AutoInstall is not configured, it defaults to the Setup facility. If the LAN
or WAN cable is not connected, the router boots from Flash memory and automatically runs the Setup
facility.
Note You can run the Setup facility when the enable prompt (#) is displayed, by entering the setup command
in privileged EXEC mode.
Step 1 Connect a console terminal to the console port on the I/O controller, and then boot the router.
Step 2 After booting from Flash memory, the following information appears after about 30 seconds. When you
see this information, you have successfully booted your router:
Restricted Rights Legend
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
32768K bytes of Flash internal SIMM (Sector size 256KB).
Note The first two sections of the configuration script, the banner and the installed hardware, appear only at
initial system startup. On subsequent uses of the Setup facility, the script begins with the following
prompt.
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Step 3 When asked if you want to continue with the System Configuration dialog and enter basic management
setup (displays the current interface summary), enter yes or press Return:
Continue with configuration dialog? [yes/no]: yes
.
.
.
Would you like to enter basic management setup? [yes/no]: yes
The interface summary appears, showing the state of configured and unconfigured interfaces.
Step 4 Choose which protocols to support on your interfaces. For IP-only installations, you can accept the
default values for most of the questions. A typical configuration using IP follows and continues through
Step 7:
Configuring global parameters:
Step 5 Enter the enable secret password, the enable password, and the virtual terminal password:
The enable secret password is a one-way cryptographic secret
password used instead of the enable password when it exists.
Step 6 The Simple Network Management Protocol (SNMP) is the most widely supported open standard for
network management. SNMP provides a means to access and set configuration and run-time parameters
of routers and communication servers. SNMP also defines a set of functions that can be used to monitor
and control network elements.
Enter yes to accept SNMP management; enter no to refuse it:
Configure SNMP Network Management? [no]:
Community string [public]:
Step 7 In all cases, you will use IP routing. When you are using IP routing, select an interior routing protocol.
You can specify one of only two interior routing protocols to operate on your system using the Setup
facility, either Interior Gateway Routing Protocol (IGRP) or Routing Information Protocol (RIP).
To configure IP routing, enter yes (the default) or press Return, and then select an interior routing
protocol:
Configure IP? [yes]:
Configure IGRP routing? [yes]:
Your IGRP autonomous system number [1]: 15
Step 8 Configure your line card interface parameters. The following example shows how an 8-port Ethernet line
card is installed in line card slot 3. The Setup facility determines the status of all interfaces.
To configure each active interface port for IP, enter yes (the default) or press Return. For all inactive
ports, the default is no. You can press Return to accept the default.
Configuring interface Ethernet 1/0:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface [19.2.22.4]:
Number of bits in subnet field [8]:
Class A network is 19.0.0.0, 8 subnet bits; mask is /16
Step 9 Configure your cable interface. The following example shows a Cisco uBR10012 router with cable
interface. The Setup facility, for the most part, determines the status of all interfaces.
To configure each active interface port, enter yes (the default) or press Return. For all inactive ports, the
default is no. You can press Return to accept the default.
Configuring interface cable 5/0/0:
Is this interface in use? [yes]:
Configure this interface? [yes]:
IP address for this interface [19.2.22.5]:
Number of bits in subnet field [8]:
Class A network is 19.0.0.0, 8 subnet bits; mask is /16
The configuration program displays the newly created command interface script:
The following command script was created:
hostname router
enable secret 5 $1$f0fc$A38P/KN/9yD3sEKSt6hKQ/
enable password betty
line vty 0 4
password wilma
snmp-server community public
!
ip routing
!
router igrp 15
network 19.0.0.0
!
end
Step 10 When asked if you want to use this configuration, enter yes or press Return.
Use this configuration? [yes/no]: yes
Step 11 Save your settings to NVRAM. (Refer to the “Configuring the Cable Interface with the Extended Setup
Facility” section on page 16.)
Note You must always manually save the configuration settings to NVRAM whenever they are modified.
Step 1 After the Setup facility has initially configured noncable interfaces on the Cisco uBR10012 router, enter
the enable command and your password (privileged EXEC).
Step 2 Enter the configure terminal command to get into global configuration mode.
Step 3 In global configuration mode, configure modulation profiles and spectrum groups for your
Cisco uBR10012 router using the cable modulation-profile and cable spectrum-group commands.
Step 4 In cable interface configuration mode, configure various characteristics for the interface in question,
using the cable upstream commands.
Step 1 Connect a console terminal to the console port on the I/O controller.
Step 2 When asked if you want to enter the initial dialog, answer no to go into the normal operating mode of
the router:
Would you like to enter the initial dialog? [yes]: no
Step 3 After a few seconds, the user EXEC prompt (Router>) appears. Type enable to enter enable mode
(configuration changes can be made only in enable mode):
Router> enable
The prompt changes to the enable mode (also called privileged EXEC) prompt:
Router#
Step 4 Enter the configure terminal command at the enable prompt to enter configuration mode from the
terminal:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Tip To see a list of the configuration commands available to you, enter ? at the prompt or type help while in
configuration mode.
Step 5 At the Router(config)# prompt, enter the interface type slot/port command to enter the interface
configuration mode:
Router(config)# interface cable slot/port
Router(config-if)#
Step 6 Set the downstream center frequency to reflect the digital carrier frequency of the downstream RF carrier
(the channel) for the downstream port:
Router(config-int)# cable downstream frequency down-freq-hz
Note This command has no effect on the external upconverter. It is informational only.
Step 7 Activate the downstream port on the cable interface line card to support digital data transmission over
the hybrid fiber-coaxial network:
Router(config-int)# no shutdown
Step 8 Enter the fixed center frequency in Hz for your downstream RF carrier and the port number:
Note Be sure not to select an upstream frequency that interferes with that used for any other upstream
application in your cable plant.
Step 9 Repeat Step 8 for each upstream port on the cable interface line card.
Step 10 Activate the upstream port:
Router(config-int)# no cable upstream port shutdown
Step 11 Repeat Step 10 to activate each port used on your cable interface line card.
Step 12 Exit to return to the configuration mode:
Router(config-if)# exit
Router(config)#
Step 13 Enter the next interface to configure, following Step 6 through Step 12, or type exit to return to enable
mode.
Router(config)# exit
Router#
%SYS-5-CONFIG_I: Configured from console by console#
Step 1 Reset the configuration of the interface back to its default values using the default command in global
configuration mode.
Router(config)# default interface wideband-Cable slot/{subslot |
bay}/port:wideband-channel
Step 1 Reset the configuration of the interface back to its default values using the default command in global
configuration mode.
Router(config)# default interface Integrated-Cable slot/subslot/port:rf-channel
Step 1 Reset the configuration of the interface back to its default values using the default command in global
configuration mode.
Router(config)# default interface Modular-Cable slot/{subslot | bay}/port:interface-number
MAC-Layer Addressing
The MAC-layer or hardware address is a standardized data link layer address required for certain
network interface types. These addresses are not used by other devices in the network; they are unique
to each port. The Cisco uBR10012 router uses a specific method to assign and control the MAC-layer
addresses for line cards.
All LAN interfaces (ports) require unique MAC-layer addresses, also known as hardware addresses.
Typically, the MAC address of an interface is stored on a memory component that resides directly on the
interface circuitry; however, the online insertion and removal (OIR) feature requires a different method.
The OIR feature lets you remove a line card and replace it with another identically configured one. If the
new line card matches the line card you removed, the system immediately brings it online.
To support OIR, an address allocator with a unique MAC address is stored in an EEPROM on the
Cisco uBR10012 router midplane. Each address is reserved for a specific port and slot in the router
regardless of whether a line card resides in that slot.
Caution When hot swapping a line card with a different type of interface, you might have to reconfigure the
interfaces. Refer to the hardware installation guide that ships with your CMTS or to the appropriate
field-replaceable unit (FRU) document for more specific information regarding OIR.
The MAC addresses are assigned to the slots in sequence. This address scheme allows you to remove
line cards and insert them into other Cisco uBR10012 router without causing the MAC addresses to
move around the network or be assigned to multiple devices.
Storing the MAC addresses for every slot in one central location means that the addresses stay with the
memory device on which they are stored.
– The card supports upstream channel widths of 200 kHz, 400 kHz, 800 kHz, 1.6 MHz, and
3.2 MHz.
– The card outputs +42 dBmV and +/- 2 dBmV.
– The downstream modulator has both an RF output, using the integrated upconverter, and an
intermediate frequency (IF) output, which must be connected to an external upconverter.
Use the slot number and downstream port number to display information about a downstream interface.
You can abbreviate the command to sh int c. The following example shows the display for upstream
channel port 0 on a Cisco uBR10012 router:
Router# sh int c 5/0/0
To display information about a specific cable interface slot’s upstream channel, use the
show interfaces cable command. Include these CM card parameters:
• Slot number
• Downstream port number
• Upstream port number
Use this format:
show interfaces cable slot/downstream-port [upstream] upstream-port
Use the slot number, downstream port number, and upstream port number to display information about
an upstream interface. You can abbreviate the command to sh int c.
The following example shows the display for upstream channel port 0 in cable interface slot 3 of a
Cisco uBR10012 router that is turned up:
Router# sh int c3/0/0 upstream
Next, the enable password is used when you do not specify an enable secret password, with some older
software versions, and some boot images.
Step 3 Respond to this prompt: Enter enable password [rHoz]: bb
Next, use the virtual terminal password to protect access to the router over a network interface.
Step 4 Respond to this prompt: Enter virtual terminal password [cc]: cc
Note For modems to acquire an IP address, they must have direct access to DHCP, TFTP, or ToD servers, or
have a static route set.
This command saves the configuration settings you set using configuration mode, the Setup facility, or
AutoInstall.
Tip If you do not save your settings, your configuration will be lost the next time you reload the router.
– Use this command to verify the current value of an upstream port frequency:
Router# show controllers cable slot/port upstream
– Use this command to check the value of the settings you entered:
Router# show running-config
• To review changes you make to the configuration, use the EXEC show startup-config command to
display the information stored in NVRAM.
Note The cable interface must also support encryption and decryption.
When Baseline Privacy is enabled, the Cisco uBR10012 router routes encrypted and decrypted packets
from a host or peer to another host or peer. BPI is configured with key encryption keys (KEKs) and traffic
encryption keys (TEKs). A KEK is assigned to a CM, based on the CM’s service identifier (SID), and
permits the CM to connect to the Cisco uBR10012 router when Baseline Privacy is activated. 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 uBR10012 router.
KEKS and TEKs can be set for Baseline Privacy on the HFC network to expire based on a grace-time
or a life-time value, defined in seconds. A grace-time value assigns a temporary key to a CM to access
the network. A life-time value assigns a more permanent key to a CM. Each CM that has a life-time
value assigned requests a new lifetime key from the Cisco uBR10012 router before the current one
expires.
To set the duration in seconds for KEK or TEK grace-time or life-time, use the following commands
in global configuration mode. To restore the default values, use the no form of each command.
cable privacy kek {grace-time [seconds] | life-time [seconds]}
no cable privacy kek {grace-time | life-time}
Syntax Description grace-time seconds (Optional) Length of key encryption grace-time in seconds. Valid range is
300 to 1800 seconds. The default grace-time value is 600 seconds.
life-time seconds (Optional) Length of the key encryption life-time in seconds.Valid range is
86,400 to 604,8000. The default life-time value is 604800 seconds.
Tip Use the show cable modem command to identify a CM with encryption and decryption enabled. The
online(pk) output of this command reveals a CM that is registered with BPI enabled and a KEK assigned.
The online(pt) output reveals a CM that is registered with BPI enabled and a TEK assigned.
Should you want to change the Cisco uBR10000 series default of 56-bit encryption and decryption to
40-bit, use the “40 bit DES” option:
Router(config-if)# cable privacy ?
40-bit-des select 40 bit DES
^^^^^^^^^^
authenticate-modem turn on BPI modem authentication
authorize-multicast turn on BPI multicast authorization
kek KEK Key Parms
mandatory force privacy be mandatory
tek TEK Key Parms
Software then generates a 40-bit DES key, where the DES key that is generated and returned masks the
first 16 bits of the 56-bit key to zero in software. To return to 56-bit encryption and decryption after
changing to 40-bit, enter the no command in front of the “40 bit des” option.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
This chapter describes how to start up and configure a Cisco uBR7200 series universal broadband router
as a Cable Modem Termination System (CMTS) for the first time. This chapter contains the following
sections:
Section Purpose
“Configuration Fundamentals Identifies tasks and analysis that you must complete prior to
for the Cisco uBR7200 Series powering on and configuring the Cisco uBR7200 series router. This
Routers” section on page 24 includes instructions for completing preconfiguration tasks and for
using password procedures.
“Configuring the Cisco Describes how to use the AutoInstall process, which is designed to
uBR7200 Series Router Using configure the Cisco uBR7200 series router automatically after
AutoInstall” section on page 31 connection to your WAN.
“Configuring the Cisco Describes how to use the Setup facility (also called the System
uBR7200 Series Router Using Configuration dialog) for configuring your CMTS, an alternative to
the Setup Facility” section on AutoInstall. Use the Setup facility prior to completing a WAN or
page 40 LAN connection to your router. The Setup facility supports several
functions so that cable interfaces and cable interface line cards are
fully operational (after initial setup).
“Removing the Cable Interfaces” Describes how to reset and remove the existing cable interfaces on
section on page 45 the Cisco uBR7200 series routers.
“Configuring the Cable Interface Provides instructions for using the Setup facility to create an initial
with the Extended Setup configuration. The extended setup prompts you to configure each
Facility” section on page 49 interface on the system.
“Configuring the Cisco Describes how to configure the Cisco uBR7200 series router
uBR7200 Series Router manually if you prefer not to use the Setup or AutoInstall facilities.
Manually Using Configuration
Mode” section on page 52
Section Purpose
“Saving Your Configuration Describes how to store the configuration or changes to your startup
Settings” section on page 53 configuration in NVRAM using the copy running-config
startup-config command.
“Reviewing Your Settings and Provides commands to check your settings and review any changes
Configurations” section on to your configuration.
page 53
“Overview of the Cisco Network Provides additional cable-specific instructions about the Cisco
Registrar for the Cisco uBR7200 Network Registrar (CNR) that are pertinent to the
Series” section on page 1 Cisco uBR7200 series and CMTS management.
Note These sections provide minimal configuration instructions. For additional configuration information,
refer to subsequent chapters in this guide. For examples of Cisco uBR7200 series CMTS configuration
files, refer to the “Viewing Sample Configuration Files” section on page 54.
Tip Be sure that you have appropriate addresses and values based on your network before you attempt to
configure the router. Enter the show version command to display the release of Cisco IOS software on
your router.
SUMMARY STEPS
DETAILED STEPS
After these prerequisites are met, you are ready to configure the Cisco uBR7200 series CMTS. This
includes, at a minimum:
• Configuring a host name and password for the Cisco uBR7200 series router
• Configuring the router to support IP over the cable plant and network backbone
Caution If you plan to use service-class-based provisioning, the service classes must be configured at the CMTS
before CMs attempt to make a connection.
SUMMARY STEPS
1. Connect a terminal to the I/O controller console port of the Cisco uBR7200 series router and
establish a terminal session.
2. Power on the Cisco uBR7200 series router. Enter no to choose the normal operating mode of the
router.
3. Continue to password definition or recovery and additional configuration.
DETAILED STEPS
Example:
Would you like to enter the initial dialog?[yes]:
no
Router>
Step 3 Continue to password definition or recovery and additional Refer to the remaining procedures in this chapter.
configuration.
Note For security purposes, the EXEC has two levels of access to commands: user EXEC mode and privileged
EXEC mode. The commands available at the user level are a subset of those available at the privileged
level.
Tip Because many privileged-level EXEC commands are used to set operating parameters, password-protect
these commands to prevent unauthorized use.
SUMMARY STEPS
DETAILED STEPS
Example:
Router> enable secret cisco
Note • An enable secret password can contain from 1 to 25 alphanumeric characters in uppercase and
lowercase.
• An enable password can contain any number of alphanumeric characters in uppercase and
lowercase.
• A number cannot be the first character.
• Spaces are valid password characters; for example, “two words” is a valid password.
• Leading spaces are ignored. Trailing spaces are recognized.
• Alphanumeric characters are recognized as uppercase or lowercase.
Passwords should be different for maximum security. If you enter the same password for both during the
setup script, the system accepts it, but you receive a warning message indicating that you should enter a
different password.
Note It is possible to recover the enable or console login password. The enable secret password is encrypted,
however, and must be replaced with a new enable secret password.
Step 1 If you can log in to the router, enter the show version command to determine the existing configuration
register value.
Step 2 Press the Break key to get to the bootstrap program prompt (ROM monitor). You might need to reload
the system image by power cycling the router.
Step 3 Change the configuration register so that the following functions are enabled:
• Break
• Ignore startup configuration
• Boot from Flash memory
Note The key to recovering a lost password is to set the configuration register bit 6 (0x0040) so that
the startup configuration (usually in NVRAM) is ignored. This allows you to log in without
using a password and to display the startup configuration passwords. Cisco recommends setting
the configuration register to 0x142.
Step 4 Power cycle the router by turning power off and then back on.
Step 5 Log in to the router and enter the privileged EXEC mode.
Step 6 Enter the show startup-config command to display the passwords.
Step 7 Recover or replace the displayed passwords.
Step 8 Change the configuration register back to its original setting.
Note To recover a lost password if Break is disabled on the router, you must have physical access to the router.
Step 1 Attach an ASCII terminal to the console port on your Cisco uBR7200 series router.
Step 2 Configure the terminal to operate at 9600 baud, 8 data bits, no parity, and 2 stop bits.
Step 3 If you can log in to the router as a nonprivileged user, enter the show version command to display the
existing configuration register value. Note the value for later use. If you cannot log in to the router at all,
continue with the next step.
Step 4 Press the Break key or send a Break from the console terminal.
• If Break is enabled, the router enters the ROM monitor, indicated by the ROM monitor prompt
(rommon n>), where n is the number of the command line. Proceed to Step 6.
• If Break is disabled, power cycle the router (turn the router off or unplug the power cord, and then
restore power). Proceed to Step 5.
Step 5 Within 60 seconds of restoring the power to the router, press the Break key or send a Break. This action
causes the router to enter the ROM monitor and display the ROM monitor prompt (rommon 1>).
Step 6 To set the configuration register on a Cisco uBR7200 series router, use the configuration register utility
by entering the confreg command at the ROM monitor prompt as follows:
rommon 1> confreg
Answer yes to the enable ignore system config info? prompt and note the current configuration
register settings.
Step 7 Initialize the router by entering the reset command as follows:
rommon 2> reset
The router initializes, the configuration register is set to 0x142, the router boots the system image from
Flash memory and enters the System Configuration dialog (setup), as follows:
--- System Configuration Dialog --
Step 8 Enter no in response to the System Configuration dialog prompts until the following message appears:
Press RETURN to get started!
Step 12 Scan the configuration file display looking for the passwords; the enable passwords are usually near the
beginning of the file, and the console login or user EXEC password is near the end. The passwords
displayed will appear similar to the following:
enable secret 5 $1$ORPP$s9syZt4uKn3SnpuLDrhuei
enable password 23skiddoo
.
.
line con 0
password onramp
Note The enable secret password is encrypted and cannot be recovered; it must be replaced. The enable and
console passwords can be encrypted text or clear text.
Proceed to the next step to replace an enable secret, console login, or enable password. If there is no
enable secret password, note the enable and console login passwords if they are not encrypted and
proceed to Step 17.
Caution Do not perform the next step unless you have determined that you must change or replace the enable,
enable secret, or console login passwords. Failure to follow the steps as presented here could cause your
router configuration to be erased.
Step 13 Enter the configure memory command to load the startup configuration file into running memory. This
action allows you to modify or replace passwords in the configuration.
Router# configure memory
Change only the passwords necessary for your configuration. You can remove individual passwords by
using the no form of the previous commands. For example, entering the no enable secret command
removes the enable secret password.
Step 16 You must configure all interfaces to not be administratively shut down as follows:
Router(config)# interface fast ethernet 0/0
Router(config)# no shutdown
Enter the equivalent commands for all interfaces that were originally configured. If you omit this step,
all interfaces are administratively shut down and unavailable when the router is restarted.
Step 17 Use the config-register command to set the configuration register to the original value noted in Step 3
or Step 7.
Step 18 Press Ctrl-Z or type end to exit configuration mode:
Router(config)# end
Caution Do not perform the next step unless you have changed or replaced a password. If you have skipped
Step 13 through Step 16 previously, then proceed now to Step 20. Failure to observe this sequence
causes the system to erase your router configuration file.
Step 19 Enter the copy running-config startup-config command to save the new configuration to nonvolatile
memory:
Router# copy running-config startup-config
Note If you wish to configure the device manually, you should connect directly to the console port and ensure
that the router is not connected to the network via any of the interface ports before you turn on the router.
Note that it may take several minutes for the device to determine that AutoInstall is not connected to the
network.
Autoinstall Requirements
For AutoInstall to work properly, the following conditions must be met:
• Routers must be attached physically to the network using one or more of the following interface
types:
– Ethernet
– Token Ring
– FDDI
– Serial with High-Level Data Link Control (HDLC) encapsulation
– Serial with Frame Relay encapsulation
Note HDLC is the default serial encapsulation. If the AutoInstall process fails over HDLC, the Cisco IOS
software automatically configures Frame Relay encapsulation.
Note Of Token Ring interfaces, only those that set ring speed with physical jumpers support AutoInstall.
AutoInstall does not work with Token Ring interfaces for which the ring speed must be set with software
configuration commands. If the ring speed is not set, the interface is set to shutdown mode.
• A TCP/IP host on your network must be preconfigured to provide the required configuration files.
• The TCP/IP host can exist anywhere on the network as long as the following conditions are
maintained:
– The host must be on the LAN or WAN side of the router’s line card connection to the WAN.
– The User Datagram Protocol (UDP) broadcasts to and from the router.
– The TCP/IP host is enabled.
This functionality is coordinated by your system administrator at the site where the TCP/IP host is
located. You should not use AutoInstall unless the required files are available on the TCP/IP host.
Understanding AutoInstall
Once the requirements for using AutoInstall are met, the dynamic configuration of the new router occurs
as follows:
1. The new router acquires its IP address. Depending on the interface connection between the two
routers and/or access servers, the new router's IP address is dynamically resolved by either SLARP
requests or BOOTP or RARP requests.
2. The new router resolves its name through network-confg, cisconet.cfg, or DNS.
3. The new router automatically requests and downloads its configuration file from a TFTP server.
4. If a host name is not resolved, the new router attempts to load router-confg or ciscortr.cfg.
Step 1 Attach the appropriate synchronous serial cable to the synchronous serial interface 0 on the router.
Step 2 Turn the power switch on each power supply to the ON (|) position. This action turns on power to the
router.
The router loads the operating system image from Flash memory; this process can take several minutes.
If the remote end of the WAN connection is connected and properly configured, the AutoInstall process
begins.
Step 3 When the AutoInstall process is completed, use the copy running-config startup-config command to
write the configuration data to the router’s nonvolatile random-access memory (NVRAM):
Router# copy running-config startup-config
Completing this step saves the configuration settings that the AutoInstall process created to NVRAM. If
you fail to do this, your configuration will be lost the next time you reload the router.
Step 4 Choose your preferred method to verify the required file configurations for the AutoInstall Facility:
Task Description
a. Verify that the configuration file is Complete this task first (required). Verify that a configuration file
on the TFTP server. for the new router resides on a TFTP server. This file can contain
the full or minimum-required configuration for the administrator
to Telnet into the new router (for configuration using Autoinstall).
Note In addition, complete one of the following two tasks.
b. Verify that a file named Complete this task, or task c. In this task, verify that the
network-confg also resides on the network-confg file on the TFTP server has an Internet Protocol
TFTP server. (IP) host name entry for the new router. The TFTP server must be
reachable from the new router.
c. Add IP-address-to-host name Complete this task, or task b. In this task, add an IP address-to-host
mapping to a DNS database file. name mapping for the new router to a Domain Name System
(DNS) database file on the TFTP server.
Step 5 If the existing router is to help install the new router automatically via an HDLC-encapsulated serial
interface using Serial Line Address Resolution Protocol (SLARP), that interface must be configured
with an IP address whose host portion has the value 1 or 2. (AutoInstall over Frame Relay does not have
this address constraint.) Subnet masks of any size are supported.
Step 6 If the existing router is to help install the new router automatically using a Frame Relay-encapsulated
serial interface, that interface must be configured with the following:
• An IP helper address pointing to the TFTP server. In the following example, 171.69.2.75 is the
address of the TFTP server:
ip helper 171.69.2.75
• A Frame Relay map pointing back to the new router. In the following example, 172.21.177.100 is
the IP address of the new router's serial interface, and 100 is the PVC identifier:
frame-relay map ip 172.21.177.100 100 dlci
Step 7 If the existing router is to help install the new router automatically via an Ethernet, Token Ring, or FDDI
interface using BOOTP or Reverse Address Resolution Protocol (RARP), then a BOOTP or RARP server
also must be set up to map the new router's Media Access Control (MAC) address to its IP address.
Step 8 IP helper addresses might need to be configured to forward the TFTP and DNS broadcast requests from
the new router to the host that is providing those services.
Note For a detailed description of the processes involved with AutoInstall, refer to the “Using AutoInstall and
Setup” chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 book
on Cisco.com.
To dynamically configure a new router using AutoInstall, complete the following steps. Steps 1, 2, and 3
are completed by the central administrator. Step 4 is completed by the person at the remote site.
Step 1 Modify the existing router's configuration to support the AutoInstall procedure.
Step 2 Set up the TFTP server to support the AutoInstall procedure.
Step 3 Set up the BOOTP or RARP server if needed. A BOOTP or RARP server is required for AutoInstall
using an Ethernet, Token Ring, FDDI, or Frame Relay-encapsulated serial interface. With a Frame
Relay-encapsulated serial interface, the existing router acts as the BOOTP server. A BOOTP or RARP
server is not required for AutoInstall using an HDLC-encapsulated serial interface.
Step 4 Connect the new router to the network.
To set up AutoInstall via a serial line with HDLC encapsulation (the default), you must configure the
existing router. Use the following commands, beginning in global configuration mode:
Command Purpose
Step 1 interface serial Configures the serial interface that connects to the new router with
interface-number HDLC encapsulation (the default), and enters interface configuration
mode for the specified interface number.
Step 2 ip address address mask Enters an IP address for the interface. The host portion of the address
must have a value of 1 or 2. (AutoInstall over Frame Relay does not have
this address constraint.)
Step 3 ip helper-address address Configures a helper address for the serial interface to forward broadcasts
associated with the TFTP, BOOTP, and DNS requests.
Step 4 clock rate bps (Optional) Configures a DCE clock rate for the serial line, unless an
external clock is being used. This step is needed only for DCE appliques.
Step 5 Ctrl-Z Exits configuration mode.
Step 6 copy running-config Saves the configuration file to your startup configuration. On most
startup-config platforms, this step saves the configuration to NVRAM. On the
Cisco7000 family, this step saves the configuration to the location
specified by the CONFIG_FILE environment variable.
In the following example, the existing router's configuration file contains the commands needed to
configure the router for AutoInstall on a serial line using HDLC encapsulation:
Router# more system:startup-config
. . .
interface serial 0
ip address 172.31.10.1 255.255.255.0
ip helper-address 172.31.20.5
. . .
To set up AutoInstall using an Ethernet, Token Ring, or FDDI interface, you must modify the
configuration of the existing router. Use the following commands, beginning in global configuration
mode:
Command Purpose
Step 1 interface {ethernet | tokenring | Enters interface configuration mode for the specified LAN
fddi} interface-number interface.
Step 2 ip address address mask Specifies an IP address for the interface.
Step 3 ip helper-address address (Optional) Configures a helper address to forward broadcasts
associated with the TFTP, BOOTP, and DNS requests.
Command Purpose
Step 4 Ctrl-Z Exits configuration mode.
Step 5 copy running-config startup-config Saves the configuration file to your startup configuration. On
most platforms, this step saves the configuration to NVRAM.
On the Cisco7000 family, this step saves the configuration to
the location specified by the CONFIG_FILE environment
variable.
Typically, the LAN interface and IP address are already configured on the existing router. You might
need to configure an IP helper address if the TFTP server is not on the same network as the new router.
In the following example, the existing router's configuration file contains the commands needed to
configure the router for AutoInstall on an Ethernet interface:
Router# more system:startup-config
. . .
interface Ethernet 0
ip address 172.31.10.1 255.255.255.0
ip helper-address 172.31.20.5
. . .
To set up AutoInstall via a serial line with Frame Relay encapsulation, you must configure the existing
router. Use the following commands beginning in global configuration mode:
Command Purpose
Step 1 interface serial 0 Configures the serial interface that connects to the new router,
and enters interface configuration mode.
Step 2 encapsulation frame-relay Configures Frame Relay encapsulation on the interface that
connects to the new router.
Step 3 frame-relay map ip ip-address dlci Creates a Frame Relay map pointing back to the new router.
or or
frame-relay interface-dlci dlci For point-to-point subinterfaces, assigns a data link connection
option [protocol ip ip-address] identifier (DLCI) to the interface that connects to the new
router, and provides the IP address of the serial port on the new
router.
Step 4 ip address address mask Specifies an IP address for the interface. This step sets the IP
address of the existing router.
Step 5 ip helper-address address Configures a helper address for the TFTP server.
Step 6 _(_IREFOBJ:1006127_) (Optional) Configures a DCE clock rate for the serial line,
_clock rate bps unless an external clock is being used. This step is needed only
for DCE appliques.
Step 7 Ctrl-Z Exits configuration mode.
Step 8 copy running-config startup-config Saves the configuration file to your startup configuration.
Note On most platforms, this step saves the configuration to
NVRAM. On the Cisco 7000 family, this step saves the
configuration to the location specified by the
CONFIG_FILE environment variable.
You must use a DTE interface on the new router because the network always provides the clock signal.
In the following example, the existing router's configuration file contains the commands needed to
configure the router for Frame Relay AutoInstall on a serial line:
Router# more system:startup-config
. . .
interface serial 0
ip address 172.31.20.20 255.255.255.0
encapsulation frame-relay
frame-relay map ip 172.31.10.1 255.255.255.0 48
ip helper-address 172.31.20.5
. . .
Step 1 Enable TFTP on a server. For information on this process, consult your host vendor's TFTP server
documentation and RFCs 906 and 783.
Step 2 If you want to use a network-confg or cisconet.cfg file to resolve the new router's name, create the
network-confg or cisconet.cfg file containing an IP address-to-host name mapping for the new router.
Enter the ip host command into the TFTP config file, not into the router. The IP address must match the
IP address that is to be dynamically obtained by the new router.
If you want to use DNS to resolve the new router's name, create an address-to-name mapping entry for
the new router in the DNS database. The IP address must match the IP address that is to be dynamically
obtained by the new router. For more information on this step, contact your DNS administrator or refer
to RFCs 1101 and 1183.
Step 3 Create the name-confg or name.cfg file, which should reside in the tftpboot directory on the TFTP server.
The name part of name-confg or name.cfg filename must match the host name you assigned for the new
router in the previous step. Enter configuration commands for the new router into this file.
The name-confg or the name.cfg file can contain either the new router's full configuration or a minimal
configuration.
The minimal configuration file is a virtual terminal password and an enable password. It allows an
administrator to Telnet into the new router to configure it. If you are using BOOTP or RARP to resolve
the address of the new router, the minimal configuration file must also include the IP address to be
obtained dynamically using BOOTP or RARP.
You can use the copy running-config tftp command to help you generate the configuration file that you
later download during the AutoInstall process.
Note The existing router might need to forward TFTP requests and response packets if the TFTP server is not
on the same network segment as the new router. When you modified the existing router's configuration,
you specified an IP helper address for this purpose.
You can save a minimal configuration under a generic newrouter-confg file. Use the ip host command
in the network-confg or cisconet.cfg file to specify newrouter as the host name with the address you will
be dynamically resolving. The new router should then resolve its IP address, host name, and minimal
configuration automatically.
Use Telnet to connect to the new router from the existing router and use the setup command facility to
configure the rest of the interfaces. For example, the line in the network-confg or cisconet.cfg file could
be similar to the following:
ip host newrouter 131.108.170.1
The following host configuration file contains the minimal set of commands needed for AutoInstall using
SLARP or BOOTP:
enable-password letmein
!
line vty 0
password letmein
!
end
The preceding example shows a minimal configuration for connecting from a router one hop away. From
this configuration, use the setup facility to configure the rest of the interfaces. If the router is more than
one hop away, you also must include routing information in the minimal configuration.
The following minimal network configuration file maps the new router's IP address, 131.108.10.2, to the
host name newrouter. The new router's address was learned via SLARP and is based on the existing
router's IP address of 131.108.10.1.
ip host newrouter 131.108.10.2
Note If the RARP server is not on the same subnet as the new router, use the ip rarp-server command to
configure the existing router to act as a RARP server. For more information, see the "Configuring a
Router as a RARP Server" section.
The following host configuration file contains the minimum set of commands needed for AutoInstall
using RARP. It includes the IP address that will be obtained dynamically via BOOTP or RARP during
the AutoInstall process. When RARP is used, this extra information is needed to specify the proper
netmask for the interface.
interface ethernet 0
Command Purpose
Step 1 enable password Enters privileged mode on the new router.
Step 2 copy running-config Saves the information from the name-config file into your startup
startup-config configuration. On most platforms, this step saves the configuration to
NVRAM. On the Cisco 7000 family, this step saves the configuration to the
location specified by the CONFIG_FILE environment variable.
Caution Verify that the existing and new routers (or access servers) are connected before entering the
copy running-config startup-config EXEC command to save configuration changes. Use the ping
EXEC command to verify connectivity. If an incorrect configuration file is downloaded, the new router
will load NVRAM configuration information before it can enter AutoInstall mode.
If the configuration file is a minimal configuration file, the new router comes up, but with only one
interface operational. Use the following commands to connect to the new router and configure it:
Command Purpose
Step 1 telnet existing Establishes a Telnet connection to the existing router.
Step 2 telnet newrouter From the existing router, establishes a Telnet connection to the new router.
Step 3 enable password Enters privileged EXEC mode.
Step 4 setup Enters setup mode to configure the new router.
Tip The router might take several minutes to determine that AutoInstall is not set up to a remote TCP/IP host.
When the router determines that AutoInstall is not configured, it defaults to the Setup facility. If the LAN
or WAN cable is not connected, the router boots from Flash memory and automatically runs the Setup
facility.
Note You can run the Setup facility when the enable prompt (#) is displayed, by entering the setup command
in privileged EXEC mode.
Step 1 Connect a console terminal to the console port on the I/O controller, and then boot the router.
Step 2 After booting from Flash memory, the following information appears after about 30 seconds. When you
see this information, you have successfully booted your router:
Restricted Rights Legend
This product may not be exported outside the U.S. and Canada
either by physical or electronic means without PRIOR approval
of Cisco Systems, Inc. or the U.S. Government.
Persons outside the U.S. and Canada may not re-export, resell,
or transfer this product by either physical or electronic means
without prior approval of Cisco Systems, Inc. or the U.S.
Government.
125440K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
4096K bytes of Flash internal SIMM (Sector size 256K).
cable submgmt default active
Note The first two sections of the configuration script, the banner and the installed hardware, appear only at
initial system startup. On subsequent uses of the Setup facility, the script begins with the following
prompt.
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Step 3 When asked if you want to continue with the System Configuration dialog and enter basic management
setup (displays the current interface summary), enter yes or press Return:
Continue with configuration dialog? [yes/no]: yes
.
.
.
Would you like to enter basic management setup? [yes/no]: yes
The interface summary appears, showing the state of configured and unconfigured interfaces.
Step 4 Choose which protocols to support on your interfaces. For IP-only installations, you can accept the
default values for most of the questions. A typical configuration using IP follows and continues through
Step 7:
Configuring global parameters:
Step 5 Enter the enable secret password, the enable password, and the virtual terminal password:
The enable secret password is a one-way cryptographic secret
password used instead of the enable password when it exists.
Step 6 The Simple Network Management Protocol (SNMP) is the most widely supported open standard for
network management. SNMP provides a means to access and set configuration and run-time parameters
of routers and communication servers. SNMP also defines a set of functions that can be used to monitor
and control network elements.
Enter yes to accept SNMP management; enter no to refuse it:
Configure SNMP Network Management? [no]:
Community string [public]:
Step 7 In all cases, you will use IP routing. When you are using IP routing, select an interior routing protocol.
You can specify one of only two interior routing protocols to operate on your system using the Setup
facility, either Interior Gateway Routing Protocol (IGRP) or Routing Information Protocol (RIP).
To configure IP routing, enter yes (the default) or press Return, and then select an interior routing
protocol:
Configure IP? [yes]:
Configure IGRP routing? [yes]:
Your IGRP autonomous system number [1]: 15
Step 8 Configure your line card interface parameters. The following example shows how an 8-port Ethernet line
card is installed in line card slot 3. The Setup facility determines the status of all interfaces.
To configure each active interface port for IP, enter yes (the default) or press Return. For all inactive
ports, the default is no. You can press Return to accept the default.
Configuring interface Ethernet 1/0:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface [19.2.22.4]:
Number of bits in subnet field [8]:
Class A network is 19.0.0.0, 8 subnet bits; mask is /16
Step 9 Configure your cable interface. The following example shows a Cisco uBR7200 series router with cable
interface. The Setup facility, for the most part, determines the status of all interfaces.
To configure each active interface port, enter yes (the default) or press Return. For all inactive ports, the
default is no. You can press Return to accept the default.
The configuration program displays the newly created command interface script:
hostname router
enable secret 5 $1$f0fc$A38P/KN/9yD3sEKSt6hKQ/
enable password betty
line vty 0 4
password wilma
snmp-server community public
!
ip routing
!
interface cable 5/0
ip address 19.2.22.5 255.255.0.0
router igrp 15
network 19.0.0.0
!
end
Step 10 When asked if you want to use this configuration, enter yes or press Return.
Use this configuration? [yes/no]: yes
Note You must always manually save the configuration settings to NVRAM whenever they are modified.
Step 1 After the Setup facility has initially configured noncable interfaces on the Cisco uBR7200 series router,
enter the enable command and your password (privileged EXEC).
Step 2 Enter the configure terminal command to get into global configuration mode.
Step 3 In global configuration mode, configure modulation profiles and spectrum groups for your
Cisco uBR7200 series router using the cable modulation-profile and cable spectrum-group
commands.
Step 4 In cable interface configuration mode, configure various characteristics for the interface in question,
using the cable upstream commands.
Step 1 Reset the configuration of the interface back to its default values using the default command in global
configuration mode.
Router(config)# default interface wideband-Cable slot/port:wideband-channel
Step 1 Reset the configuration of the interface back to its default values using the default command in global
configuration mode.
Router(config)# default interface Integrated-Cable slot/port:rf-channel
Step 1 In the following example, the system is being configured for an Ethernet LAN using IP. Respond to the
prompts as follows, using your own addresses and mask at the setup prompts:
Configuring interface parameters:
Configuring interface Ethernet0/0:
Is this interface in use? [no]: yes
Configure IP on this interface? [no]: yes
IP address for this interface: 1.1.1.10
Number of bits in subnet field [0]:
Class A network is 1.0.0.0, 0 subnet bits; mask is 255.0.0.0
Step 2 Do not enable Internetwork Package Exchange (IPX) on this interface; IPX is not supported on the Cisco
uBR7200 series universal broadband router:
Configure IPX on this interface? [no]: no
Step 3 If additional Ethernet interfaces are available in your system, enter their configurations when you are
prompted.
Step 4 Save the configuration to NVRAM:
Router# copy running-config startup-config
Note You must always manually save the configuration settings to NVRAM whenever they are modified.
Step 2 Determine which protocols you want on the synchronous serial interface and enter the appropriate
responses:
Configure IP unnumbered on this interface? [no]:
IP address for this interface: 10.1.1.20
Number of bits in subnet field [0]:
Class A network is 10.0.0.0, 0 subnet bits; mask is 255.0.0.0
Step 3 If additional synchronous serial interfaces are available in your system, enter their configurations when
you are prompted.
Step 4 Save the configuration to NVRAM:
Router# copy running-config startup-config
Note You must always manually save the configuration settings to NVRAM whenever they are modified.
The following sample display includes a continuous listing of all interface configuration parameters
selected for Ethernet and synchronous serial interfaces. These parameters are shown in the order in
which they appear on your console terminal.
Tip Only one Ethernet and one synchronous serial interface are configured for this example.
hostname Router
[OK]
Use the enabled mode `configure' command to modify this configuration.
Your Cisco uBR7200 series router is now minimally configured and is ready to use. Use the setup
command in provileged EXEC mode if you want to modify the parameters after the initial configuration.
To perform more complex configurations, use the configure privileged EXEC command in global
configuration mode.
Frequency: 33808000
Would you like to configure the DHCP server? [yes/no]: yes
IP address for the DHCP server [X.X.X.X]: 10.0.0.2
Configure IP on this interface? [yes]:
IP address for this interface [10.20.133.65]:
Subnet mask for this interface [255.0.0.0]: 255.255.255.248
Class A network is 10.0.0.0, 29 subnet bits; mask is /29
In this example, the input above generates the following command interface script:
interface Cable 5/0
no shutdown
cable downstream frequency 531000000
no shutdown
cable downstream modulation 64qam
cable downstream annex B
cable downstream interleave-depth 32
no cable upstream 0 shutdown
cable upstream 0 frequency 33808000
cable helper-address 10.0.0.2
ip address 10.20.133.65 255.255.255.248
Note Cable modems or set-top boxes with integrated cable modems are brought online when the utility is run.
Note For Dynamic Host Configuration Protocol (DHCP)/time of day (TOD)/Trivial File Transfer Protocol
(TFTP), a static route must exist to the host.
– The card supports upstream channel widths of 200 kHz, 400 kHz, 800 kHz, 1.6 MHz, and
3.2 MHz.
– The card outputs +42 dBmV and +/- 2 dBmV.
– The downstream modulator has both an RF output, using the integrated upconverter, and an
intermediate frequency (IF) output, which must be connected to an external upconverter.
Use the slot number and downstream port number to display information about a downstream interface.
You can abbreviate the command to sh int c. The following example shows the display for upstream
channel port 0 on a Cisco uBR7200 series router:
Router# sh int c 5/0
To display information about a specific cable interface slot’s upstream channel, use the
show interfaces cable command. Include these CM card parameters:
• Slot number
• Downstream port number
• Upstream port number
Use this format:
show interfaces cable slot/downstream-port [upstream] upstream-port
Use the slot number, downstream port number, and upstream port number to display information about
an upstream interface. You can abbreviate the command to sh int c.
The following example shows the display for upstream channel port 0 in cable interface slot 3 of a
Cisco uBR7200 series router that is turned up:
Router# sh int c3/0 upstream
The enable secret password is used to protect access to privileged EXEC and configuration modes. This
password, after entered, becomes encrypted in the configuration.
Step 2 Respond to this prompt:
Enter enable secret [Use current secret]: aa
Next, the enable password is used when you do not specify an enable secret password, with some older
software versions, and some boot images.
Step 3 Respond to this prompt:
Next, use the virtual terminal password to protect access to the router over a network interface.
Step 4 Respond to this prompt:
Enter virtual terminal password [cc]: cc
Note For modems to acquire an IP address, they must have direct access to DHCP, TFTP, or ToD servers, or
have a static route set.
Step 1 Connect a console terminal to the console port on the I/O controller.
Step 2 When asked if you want to enter the initial dialog, respond no to go into the normal operating mode of
the router:
Would you like to enter the initial dialog? [yes]: no
Step 3 After a few seconds, the user EXEC prompt (Router>) appears. Type enable to enter enable mode
(configuration changes can be made only in enable mode):
Router> enable
The prompt changes to the enable mode (also called privileged EXEC) prompt:
Router#
Step 4 Enter the configure terminal command (conf t)at the enable prompt to enter configuration mode from
the terminal:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#
Tip To see a list of the configuration commands available to you, enter ? at the prompt or type help while in
configuration mode.
Step 5 At the Router(config)# prompt, enter the interface type slot/port command to enter the interface
configuration mode:
Router(config)# interface cable slot/port
Router(config-if)#
Step 6 Set the downstream center frequency to reflect the digital carrier frequency of the downstream RF carrier
(the channel) for the downstream port:
Router(config-int)# cable downstream frequency down-freq-hz
Note This command has no effect on the external upconverter. It is informational only.
Step 7 Activate the downstream port on the cable interface line card to support digital data transmission over
the hybrid fiber-coaxial network:
Router(config-int)# no shutdown
Step 8 Enter the fixed center frequency in Hz for your downstream RF carrier and the port number:
Router(config-int)# cable upstream port frequency up-freq-hz
Note Be sure not to select an upstream frequency that interferes with that used for any other upstream
application in your cable plant.
Step 9 Repeat Step 8 for each upstream port on the cable interface line card.
Step 10 Activate the upstream port:
Router(config-int)# no cable upstream port shutdown
Step 11 Repeat Step 10 to activate each port used on your cable interface line card.
Step 12 Exit to return to the configuration mode:
Router(config-if)# exit
Router(config)#
Step 13 Enter the next interface to configure, following Step 6 through Step 12, or type exit to return to enable
mode.
Router(config)# exit
Router#
%SYS-5-CONFIG_I: Configured from console by console#
This command saves the configuration settings you set using configuration mode, the Setup facility, or
AutoInstall.
Tip If you do not save your settings, your configuration will be lost the next time you reload the router.
– Use the following command to verify the current value of an upstream port frequency:
Router# show controllers cable slot/port upstream
– Use the following command to check the value of the settings you entered:
Router# show running-config
• To review changes you make to the configuration, use the EXEC show startup-config command to
display the information stored in NVRAM.
Note The cable interface must also support encryption and decryption.
When Baseline Privacy is enabled, the Cisco uBR7200 series router routes encrypted and decrypted
packets from a host or peer to another host or peer. BPI is configured with key encryption keys (KEKs)
and traffic encryption keys (TEKs). A KEK is assigned to a CM, based on the CM’s service identifier
(SID), and permits the CM to connect to the Cisco uBR7200 series router when Baseline Privacy is
activated. 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 uBR7200 series router.
KEKS and TEKs can be set for Baseline Privacy on the HFC network to expire based on a grace-time
or a life-time value, defined in seconds. A grace-time value assigns a temporary key to a CM to access
the network. A life-time value assigns a more permanent key to a CM. Each CM that has a life-time
value assigned requests a new lifetime key from the Cisco uBR7200 series router before the current one
expires.
To set the duration in seconds for KEK or TEK grace-time or life-time, use the following commands
in global configuration mode. To restore the default values, use the no form of each command.
cable privacy kek {grace-time [seconds] | life-time [seconds]}
no cable privacy kek {grace-time | life-time}
Syntax Description grace-time seconds (Optional) Length of key encryption grace-time in seconds. Valid range is
300 to 1800 seconds. The default grace-time value is 600 seconds.
life-time seconds (Optional) Length of the key encryption life-time in seconds.Valid range is
86,400 to 604,8000. The default life-time value is 604800 seconds.
Tip Use the show cable modem command to identify a CM with encryption and decryption enabled. The
online(pk) output of this command reveals a CM that is registered with BPI enabled and a KEK assigned.
The online(pt) output reveals a CM that is registered with BPI enabled and a TEK assigned.
Should you want to change the Cisco uBR7200 series default of 56-bit encryption and decryption to
40-bit, use the “40 bit DES” option:
Router(config-if)# cable privacy ?
40-bit-des select 40 bit DES
^^^^^^^^^^
authenticate-modem turn on BPI modem authentication
authorize-multicast turn on BPI multicast authorization
kek KEK Key Parms
mandatory force privacy be mandatory
tek TEK Key Parms
Software then generates a 40-bit DES key, where the DES key that is generated and returned masks the
first 16 bits of the 56-bit key to zero in software. To return to 56-bit encryption and decryption after
changing to 40-bit, enter the no command in front of the “40 bit des” option.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
The Cisco uBR7200 series and Cisco uBR10012 universal broadband routers support online insertion
and removal (OIR) of cable interface line cards, but have different requirements. The following sections
describe this support for each of the platforms.
Caution When you OIR different types of cable interface line cards (for example, a Cisco uBR-MC16U card
replaced by a Cisco uBR-MC16X card, or Cisco uBR-MC16U card replaced by a Cisco uBR-MC28U
card), you not only might have to reconfigure the interfaces, we recommend that you reload the router.
Step 1 From global configuration mode, enter the cr10k card oir-compatibility command for the cable
interface line card that you want to OIR, as shown in the following example:
Router(config)# cr10k card 8/0 oir-compatibility
This command helps preserve the configuration and performs some internal synchronization to make
sure that the OIR runs successfully.
Note The console log displays a new message appears whenever a line card type has been replaced. For
example, if the MC520U-D in subslot 8/1 is replaced by an MC520S-D, the following message is
displayed:
%UBR10K-6-COMPAT_NEW_CARD: The 5cable-mc520u-d in slot 8/1 has been replaced by a
5cable-mc520s-d
This message appears when an OIR operation involves two different types of MC520 line cards.
Caution The console log message does not appear for cards other than the MC520S/U/H. It also does not appear
if the OIR operation involves identical MC520 card types. For instance, it will not appear if an MC520U
is replaced by another MC520U. In such cases, you not only might have to reconfigure the interfaces,
we recommend that you reload the router.
Step 2 Save the configuration to ensure the transition, as shown in the following example:
Router# copy running-config startup-config
Step 3 Turn the power off to the line card using the cable power off command for the slot that is being replaced
as shown in the following example:
Router# cable power off 8/0
Line Card 8/0 is POWERED OFF
Step 4 Before removing the card, verify that the proper grounding instructions have been followed for the card.
For more information about preventing electrostatic discharge (ESD) damage, refer to the document at:
http://www.cisco.com/warp/public/109/cable-linecard-handling.pdf
Step 5 Remove the line card.
Step 6 Replace it with the new line card in the slot.
Step 7 Enter the cable power on command to power up the line card, as shown in the following example:
Router# cable power on 8/0
Step 8 Enter the show interface cable command and verify that the card and line protocol is “up” as shown in
the following example:
Router# show interface cable 8/0/0
Cable8/0/0 is up, line protocol is up
Hardware is BCM3210 ASIC, address is 000a.13e8.1ca8 (bia 000a.13e8.1a60)
Step 9 Enter the show controllers cable command and verify the hardware status as shown in the following
example:
Router# show controllers cable 8/0/0
Cable8/0/0 JIB hardware status:
JIB Downstream port Enabled
JIB Upstream port 0 Enabled
JIB Upstream port 1 Enabled
JIB Upstream port 2 Enabled
JIB Upstream port 3 Enabled
Cable8/0/0 Upconverter is Enabled Output is Enabled
Model: 74-3153-02 Serial Number: 0WAV090200A1 CLEI Code: FFFFFFFFFF
HW Rev: PC2D0109 SW Rev: 203, NVRAM Rev: 021 ECI numb
Step 10 Verify the configuration with the show running-configuration command as shown in the following
example:
Router# show running-configuration
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
The Unique Device Identifier Retrieval (UDI retrieval) feature provides the ability to retrieve and display
the Unique Device Identifier (UDI) information from any Cisco product that has electronically stored
such identity information.
Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This
feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that
references many legacy documents related to Cisco IOS 12.3BC. In general, any references to Cisco IOS
Release 12.3BC also apply to Cisco IOS Release 12.2SC.
Finding Support Information for Platforms and Cisco IOS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image
support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on
Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at
the login dialog box and follow the instructions that appear.
Contents
• Prerequisites for Unique Device Identifier Retrieval, page 62
• Information About Unique Device Identifier Retrieval, page 62
• How to Retrieve the Unique Device Identifier, page 63
• Configuration Examples for Unique Device Identifier Retrieval, page 69
• Additional References, page 69
• Command Reference, page 70
SUMMARY STEPS
1. enable
2. show inventory [raw]
DETAILED STEPS
Step 1 enable
Enters privileged EXEC mode. Enter your password if prompted.
Router> enable
For diagnostic purposes, the show inventory command can be used with the raw keyword to display
every RFC 2737 entity including those without a PID, UDI, or other physical identification.
Note The raw keyword option is primarily intended for troubleshooting problems with the show inventory
command itself.
Troubleshooting Tips
If any of the Cisco products do not have an assigned PID, the output may display incorrect PIDs and the
VID and SN elements may be missing, as in the following example.
NAME: "POS3/0/0", DESCR: "Skystone 4302 Sonet Framer"
PID: FastEthernet, VID: , SN:
In the sample output, the PID is exactly the same as the product description. The UDI is designed for use
with new Cisco products that have a PID assigned. UDI information on older Cisco products is not
always reliable.
Additional References
This section provides references related to the UDI Retrieval feature.
Related Documents
Standards
Standards Title
No new or modified standards are supported by this —
feature, and support for existing standards has not been
modified by this feature.
MIBs
RFCs
RFCs Title
RFC 2737 Entity MIB (Version 2)
Technical Assistance
Description Link
Technical Assistance Center (TAC) home page, http://www.cisco.com/cisco/web/support/index.html
containing 30,000 pages of searchable technical
content, including links to products, technologies,
solutions, technical tips, and tools. Registered
Cisco.com users can log in from this page to access
even more content.
Command Reference
The following commands are introduced or modified in the feature or features documented in this
module. For information about these commands, see the Cisco IOS Cable Command Reference at
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html. For information about
all Cisco IOS commands, go to the Command Lookup Tool at
http://tools.cisco.com/Support/CLILookup or to the Cisco IOS Master Commands List.
• show inventory
CCVP, the Cisco logo, and Welcome to the Human Network are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is
a service mark of Cisco Systems, Inc.; and Access Registrar, Aironet, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity,
Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS,
iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys, MeetingPlace, MGX, Networkers,
Networking Academy, Network Registrar, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet Quotient,
and TransPath are registered trademarks of Cisco Systems, Inc. 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. (0711R)
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.
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 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.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this
URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS Routers 1
Finding Feature Information 1
Contents 2
Prerequisites for Advanced-Mode DSG Issue 1.2 2
Restrictions for Advanced-Mode DSG Issue 1.2 3
Information About Advanced-Mode DSG Issue 1.2 4
How to Configure Advanced-Mode DSG Issue 1.2 7
How to Monitor and Debug the Advanced-mode DOCSIS Set-Top Gateway Feature 29
Configuration Examples for Advanced-Mode DSG 41
Additional References 45
Feature Information for Advanced-Mode DSG 1.2 for the Cisco CMTS Routers 46
Note Cisco IOS Release 12.2(33)SCA integrates support for this feature on the Cisco CMTS routers. This
feature is also supported in Cisco IOS Release 12.3BC, and this document contains information that
references many legacy documents related to Cisco IOS 12.3BC. In general, any references to
Cisco IOS Release 12.3BC also apply to Cisco IOS Release 12.2SC.
The Advanced-Mode DOCSIS Set-Top Gateway (A-DSG) Issue 1.2 introduces support for the latest
DOCSIS Set-Top specification from CableLabs™, to include the following enhancements:
• DOCSIS Set-top Gateway (DSG) Interface Specification
• A-DSG 1.2 introduces support for the DOCS-DSG-IF MIB.
Cisco A-DSG 1.2 is certified by CableLabs™, and is a powerful tool in support of latest industry
innovations. A-DSG 1.2 offers substantial support for enhanced DOCSIS implementation in the
broadband cable environment. The set-top box (STB) dynamically learns the overall environment from
the Cisco CMTS router, to include MAC address, traffic management rules, and classifiers.
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS Routers
Contents
Contents
• Prerequisites for Advanced-Mode DSG Issue 1.2, page 2
• Restrictions for Advanced-Mode DSG Issue 1.2, page 3
• Information About Advanced-Mode DSG Issue 1.2, page 4
• How to Configure Advanced-Mode DSG Issue 1.2, page 7
• How to Monitor and Debug the Advanced-mode DOCSIS Set-Top Gateway Feature, page 29
• Configuration Examples for Advanced-Mode DSG, page 41
• Additional References, page 45
• Feature Information for Advanced-Mode DSG 1.2 for the Cisco CMTS Routers, page 46
Note The hardware components introduced in a given Cisco IOS Release are supported in all subsequent
releases unless otherwise specified.
Table 1 A-DSG for the Cisco CMTS Routers Hardware Compatibility Matrix
Table 1 A-DSG for the Cisco CMTS Routers Hardware Compatibility Matrix
Subinterfaces
A-DSG 1.2 supports subinterfaces on the Cisco CMTS router starting from Cisco IOS Release
12.2(33)SCB4.
FQDN Support
Starting with Cisco IOS Release 12.2(33)SCG, you can specify either a fully-qualified domain name
(FQDN) or IP address for A-DSG classifier multicast group and source addresses using the cable dsg cfr
command in global configuration mode. We recommend that you use an FQDN to avoid modification of
multicast group and source addresses when network changes are implemented.
This feature allows you to use a hostname (FQDN) in place of the source IP address using the
cable dsg cfr command. For example, you have two A-DSG tunnel servers, in two locations, sending
multicast traffic to the same multicast address. In this scenario, you can specify a hostname for the source
IP address and let the DNS server determine which source is sending the multicast traffic.
If you configure an A-DSG classifier with a hostname, the Cisco CMTS router immediately verifies if
the hostname can be resolved against an IP address using the local host cache. If not, the router does not
enable the classifier until the hostname is resolved. If the hostname cannot be resolved locally, the router
performs a DNS query to verify the DSG classifiers.
The FQDN format does not support static Internet Group Management Protocol (IGMP) join requests
initiated on the Cisco CMTS router. The IGMP static group IP address created automatically under a
bundle interface at the time of A-DSG configuration is not displayed in the
show running-config interface command output in Cisco IOS Release 12.2(33)SCG and later. To
display the A-DSG static groups configured under a bundle interface, use the
show cable dsg static-group bundle command in privileged EXEC mode in
Cisco IOS Release 12.2(33)SCG and later.
Starting with Cisco IOS Release 12.2(33)SCG, you can disable A-DSG forwarding per primary capable
interface using the cable downstream dsg disable command in interface configuration mode. Primary
capable interfaces include modular, integrated cable interfaces, and Cisco uBR10-MC5X20 and
Cisco uBR-MC28U cable interfaces.
For example, assume the cable interface 7/1/1 has A-DSG enabled and has four modular channels
attached to it. However, you want A-DSG forwarding enabled only on two of these four modular
channels. You can exclude the channels of your choice using the cable downstream dsg disable
command. For details on how to disable modular channels, see the “Disabling A-DSG Forwarding on
the Primary Channel” section on page 28.
Note If A-DSG downstream forwarding is disabled on a primary capable interface, the router does not create
multicast service flows on the primary capable interface and stops sending Downstream Channel
Descriptor (DCD) messages.
SUMMARY STEPS
1. enable
2. configure terminal
3. cable multicast group-qos default scn service-class-name aggregate
4. end
DETAILED STEPS
Example:
Router# configure terminal
Router(config)#
Step 3 cable multicast group-qos default scn Configures a service class name for the QoS profile.
service-class-name aggregate
• scn service-class-name—Service class name
for the QoS profile.
Example:
Router(config)# cable multicast group-qos default
• aggregate—Specifies that service flows are
scn name1 aggregate grouped for sessions in the same MQoS group
Step 4 end Returns to privileged EXEC mode.
Example:
Router(config)# end
Note If you configure or remove the default MQoS while the CMTS is sending multicast traffic, duplicate
traffic is generated for approximately 3 minutes (or 3 times the query interval).
Prerequisites
Starting with the Cisco IOS Release 12.2(33)SCC1, when DOCSIS Set-top Gateway (DSG) is
configured to have quality of service (QoS) for tunnel, ensure that the default multicast QoS (MQoS) is
also configured. For more information, see Configuring the Default Multicast Quality of Service, page 7.
Restrictions
The DSG tunnel service class configuration is rejected, if default MQoS is not configured.
SUMMARY STEPS
1. enable
2. configure terminal
3. cable dsg tg group-id [channel channel-id | priority DSG-rule-priority] [enable | disable]
4. cable dsg tg group-id [channel channel-id [ucid ID1 | ID2 ID3 ID4]]
5. cable dsg tg group-id [channel channel-id [vendor-param vendor-group-id]]
6. cable dsg vendor-param group-id vendor vendor-id oui oui value value-in-TLV
7. cable dsg chan-list list-index index entry-index freq freq
8. cable dsg timer index [Tdsg1 Tdsg1] | [Tdsg2 Tdsg2] | [Tdsg3 Tdsg3] | [Tdsg4 Tdsg4]
9. end
DETAILED STEPS
Example:
Router# configure terminal
Router(config)#
Step 3 cable dsg tg group-id [channel channel-id|priority Command allows the association of a group of
DSG-rule-priority] [enable|disable] tunnels to one or more downstream interfaces on the
Cisco CMTS.
Example: • tg—DSG tunnel group id
Router(config)# cable dsg tg 1 channel 1 priority 1
enable • channel—downstream channel index
• priority—DSG Rule priority
• enable—Enable tunnel group
• disable—Disable tunnel group
Step 4 cable dsg tg group-id [channel channel-id [ucid Sets the upstream channel or channels to which the
ID1]] DSG 1.2 tunnel applies.
• ucid—List of Upstream channel ID for which
Example: the rule applies
Router(config)# cable dsg tg 1 channel 1 ucid 1
Example:
Router(config)# end
Examples
The following example illustrates global upstream configurations implemented with the above
commands:
Router> enable
Router# configure terminal
Router(config)# cable dsg tg 1 channel 1 priority 1 enable
Router(config)# cable dsg tg 1 channel 1 ucid 1
Router(config)# cable dsg tg 1 channel 1 vendor-param 1
Router(config)# end
Router#
Troubleshooting Tips
Refer to debug and show commands in the “How to Monitor and Debug the Advanced-mode DOCSIS
Set-Top Gateway Feature” section on page 29.
Prerequisites
Cisco IOS Release 12.2(33)SCB4 or Cisco IOS Release 12.2(33)SCC1 or future release versions must
be installed previously on the Cisco CMTS.
The downstream DSG should exist to create IGMP static joins.
Restrictions
You can associate a DSG tunnel group to only one subinterface within the same bundle interface.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface bundle bundle-subif-number
4. cable dsg tg group-id
5. end
DETAILED STEPS
Example:
Router# configure terminal
Router(config)#
Step 3 interface bundle bundle-subif-number Specifies the interface bundle and enters the
subinterface configuration mode.
Example: • bundle-subif-number—Interface bundle
Router(config)# interface bundle 11.2 number.
Router(config-subif)#
Step 4 cable dsg tg group-id Adds a DSG tunnel group to a subinterface.
• group-id—DSG tunnel group identifier.
Example:
Router(config-subif)# cable dsg tg 1
Step 5 end Returns to privileged EXEC mode.
Example:
Router(config-subif)# end
Examples
The following example shows how to add a DSG tunnel group to a subinterface:
Router> enable
Router# configure terminal
Router(config)# interface bundle 11.2
Router(config-subif)# cable dsg tg 1
Router(config-subif)# end
Router#
Restrictions
The in-dcd ignore option is not supported by DSG-IF-MIBS specification.
SUMMARY STEPS
1. enable
2. configure terminal
3. cable dsg client-list client-list-id id-index id {application-id app-id | ca-system-id sys-id |
mac-addr mac-addr | broadcast [broadcast-id]}
4. cable dsg client-list client-list-id id-index id [vendor-param vendor-group-id]
5. cable dsg tunnel tunnel id mac_addr mac addr tg tunnel-group clients client-list-id [enable |
disable]
6. cable dsg cfr cfr index [dest-ip {ipaddr | hostname}] [tunnel tunnel index] [dest-port start end]
[priority priority] [src-ip {ipaddr | hostname} [src-prefix-len length]] [enable | disable] [in-dcd
{yes | no | ignore}]
7. end
DETAILED STEPS
Example:
Router# configure terminal
Example:
Router(config)# end
Router#
Examples
The following example illustrates global configuration of DSG 1.2 on the Cisco CMTS, supporting the
specified settings shown. Global configuration may vary, but this example is representative of a typical
configuration:
Router(config)# cable dsg vendor-param 1 vendor 1 oui 000001 value 010101
Router(config)# cable dsg client-list 1 id-index 1 mac-addr abcd.abcd.abcd
Router(config)# cable dsg tg 1 channel 1
Router(config)# cable dsg tunnel 1 mac-addr 0abc.0abc.0abc tg 1 clients 1
Router(config)# cable dsg cfr 1 dest-ip 224.225.225.225 tunnel 1 dest-port 40 50 priority
2 src-ip 1.11.37.0 src-prefix-len 24 in-dcd ignore
Router(config)# cable dsg timer 1 Tdsg1 4 Tdsg2 600 Tdsg3 300 Tdsg4 1800
Router(config)# cable dsg chan-list 1 index 1 freq 471000000
Troubleshooting Tips
Refer to debug and show commands in the “How to Monitor and Debug the Advanced-mode DOCSIS
Set-Top Gateway Feature” section on page 29.
SUMMARY STEPS
1. enable
2. configure terminal
3. interface cable {slot/port | slot/subslot/port}
4. cable downstream dsg tg group-id [channel channel-id]
5. cable downstream dsg chan-list list-index
6. cable downstream dsg timer timer-index
7. cable downstream dsg vendor-param vsif-grp-id
8. cable downstream dsg [ dcd-enable | dcd-disable ]
9. end
DETAILED STEPS
Example:
Router# configure terminal
Step 3 interface cable {slot/port | slot/subslot/port} Enters interface configuration mode.
• On the Cisco uBR7200 series router, slot can range
Example: from 3 to 6, and port can be 0 or 1, depending on the
Router(config)# interface cable 8/1/1 cable interface.
• On the Cisco uBR10012 router, the valid values are:
– slot—5 to 8
– subslot—0 or 1
– port—0 to 4 (depending on the cable interface)
Example:
Router(config-if)# end
Examples
The following example illustrates downstream settings configured for DSG 1.2 on the Cisco CMTS:
Downstream 1
Router# configure terminal
Router(config)# interface cable 7/1/1
Router(config-if)# cable downstream dsg chan-list 1
Router(config-if)# cable downstream dsg timer 1
Router(config-if)# cable downstream dsg tg 1 channel 1
Router(config-if)# end
Downstream 2
The setting given below uses the same DSG tunnel-group as that of downstream 1.
Router# configure terminal
Router(config)# interface cable 8/1/1
Router(config-if)# cable downstream dsg chan-list 1
Router(config-if)# cable downstream dsg timer 1
Router(config-if)# cable downstream dsg tg 1 channel 2
Router(config-if)# cable downstream dsg vendor-param 1
Router(config-if)# Ctrl^Z
SUMMARY STEPS
1. configure terminal
2. ip multicast-routing
3. ip pim ssm {default | range {access-list | word}}
4. ip cef distributed
5. interface bundle bundle-number
6. ip pim {dense-mode | spasrse-mode | sparse-dense-mode}
7. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 ip multicast-routing Enables multicast routing on the router.
Example:
Router(config)# ip multicast-routing
Step 3 ip pim ssm {default | range {access-list | Defines the Source Specific Multicast (SSM) range of IP
word}} multicast addresses. To disable the SSM range, use the no
form of this command.
Example: • vrf— (Optional) Supports the multicast Virtual Private
Router(config)# ip pim ssm range 4 Network (VPN) routing and forwarding (VRF)
instance.
• vrf-name—(Optional) Name assigned to the VRF.
• default—Defines the SSM range access list to 232/8.
• range access-list—Specifies the standard IP access list
number. The valid range is from 1 to 99.
• word—Standard IP access list name defining the SSM
range.
Note When an SSM range of IP multicast addresses is
defined by the ip pim ssm command, no Multicast
Source Discovery Protocol (MSDP) Source-Active
(SA) messages will be accepted or originated in the
SSM range.
Step 4 ip cef distributed Enables Cisco Express Forwarding (CEF) on the route
processor card. To disable CEF, use the no form of this
command.
Example:
Router(config)# ip cef distributed For additional information about the ip cef command, refer
to the following document on Cisco.com:
• Cisco IOS Switching Services Command Reference,
Release 12.3
http://www.cisco.com/en/US/docs/ios/12_3/switch/co
mmand/reference/swtch_r.html
Step 5 interface bundle bundle-number Enters interface configuration mode for each interface
bundle being used for DSG traffic.
Example:
Router(config)# interface bundle 10
Prerequisites
Ensure that the IP DNS-based hostname-to-address translation is configured on the Cisco CMTS router
using the ip domain-lookup command in global configuration mode. This is configured by default, and
the status is not displayed in the running configuration.
SUMMARY STEPS
1. configure terminal
2. ip domain-name name
3. ip name-server server-address [multiple-server-addresses]
4. cable dsg name-update-interval minutes
5. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 ip domain-name name Sets the IP domain name that the Cisco IOS software uses
to complete unqualified host names.
Example: • name—Default domain name.
Router(config)# ip domain-name cisco.com
Step 3 ip name-server server-address Sets the server IP address.
[multiple-server-addresses]
• server-address— IP address of the server.
• multiple-server-addresses—(Optional) IP address of
Example:
Router(config)# ip name-server 131.108.1.111
multiple servers. You can specify a maximum of six
server addresses.
Step 4 cable dsg name-update-interval minutes Sets the interval to check the DNS server for any FQDN
classifier changes.
Example: • minutes—Interval in minutes. The valid range is from
Router(config)# cable dsg name-update-interval 1 to 60. The default value is 5.
10
Step 5 end Returns to privileged EXEC mode.
Example:
Router(config)# end
Tip This procedure should be performed after the cable interface has already been configured for DSG
operations, as described in the “Configuration Examples for Advanced-Mode DSG” section on page 41.
Note The Cisco CMTS router supports NAT only when it is running an “IP Plus” (-i-) Cisco IOS software
image. Refer to the release notes for your Cisco IOS release for complete image availability and
requirements.
SUMMARY STEPS
1. configure terminal
2. interface wan-interface
3. ip nat outside
4. interface bundle bundle-number
5. ip address ip-address mask secondary
6. ip nat inside
7. exit
8. ip nat inside source static ip-multicast-address cable-ip-address
9. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 interface wan-interface Enters interface configuration mode for the specified WAN
interface.
Example:
Router(config)# interface FastEthernet0/0
Step 3 ip nat outside Configures the WAN interface as the “outside” (public)
NAT interface.
Example:
Router(config-if)# ip nat outside
Step 4 interface bundle bundle-number Enters interface configuration mode for the specified
interface bundle.
Example: Note This interface bundle should have previously been
Router(config-if)# interface bundle 10 configured for DSG operations.
Step 5 ip address ip-address mask secondary Configures the cable interface with an IP address and subnet
that should match the unicast address being used for DSG
traffic. This IP address and its subnet must not be used by
Example:
Router(config-if)# ip address 192.168.18.1
any other cable interfaces, cable modems, or any other types
255.255.255.0 secondary of traffic in the cable network.
Step 6 ip nat inside Configures the cable interface as the “inside” (private) NAT
interface.
Example:
Router(config-if)# ip nat inside
Step 7 exit Exits interface configuration mode and returns to global
configuration mode.
Example:
Router(config-if)# exit
Tip This procedure assumes a basic knowledge of how access lists use an IP address and bitmask to
determine the range of IP addresses that are allowed access. For full details on configuring access lists,
see the documents listed in the “Additional References” section on page 45.
SUMMARY STEPS
1. configure terminal
2. access-list access-list permit group-ip-address [mask]
3. access-list access-list deny group-ip-address [mask]
4. access-list access-list deny any
5. interface bundle bundle-number
6. ip access-group access-list
7. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 access-list access-list permit group-ip-address Creates an access list specifying that permits access to the
[mask] specific multicast address that matches the specified
group-ip-address and mask.
Example: • access-list—Number or name of a standard IP access
Router(config)# access-list 90 permit 228.1.1.1 list. The number can range from 1 to 99 with no default.
• group-ip-address—IP address to be used as a base for
this access list. It should be based on the group IP
address used for DSG tunnels of the interface.
• mask—(Optional) Bitmask that determines which
addresses in the group-ip-address will be allowed
access. The default is 255.255.255.255.
Tip This procedure assumes a basic knowledge of how access lists use an IP address and bitmask to
determine the range of IP addresses that are allowed access. For full details on configuring access lists,
see the documents listed in the “Additional References” section on page 45.
SUMMARY STEPS
1. configure terminal
2. access-list access-list permit group-ip-address [mask]
3. access-list access-list deny group-ip-address [mask]
4. access-list access-list deny any
5. interface cable interface
6. ip igmp access-group access-list [version]
7. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 access-list access-list permit group-ip-address Creates an access list specifying that permits access to the
[mask] specific multicast address that matches the specified
group-ip-address and mask.
Example: • access-list —Number or name of a standard IP access
Router(config)# access-list 90 permit 228.1.1.1 list. The number can range from 1 to 99 with no default.
• group-ip-address—IP address to be used as a base for
this access list. It should be based on the group IP
address used for the interface’s DSG tunnels.
• mask—(Optional) Bitmask that determines which
addresses in the group-ip-address will be allowed
access. The default is 255.255.255.255.
SUMMARY STEPS
1. configure terminal
2. interface modular-cable slot/subslot/port: interface-number
3. cable downstream dsg disable
4. end
DETAILED STEPS
Example:
Router# configure terminal
Step 2 interface modular-cable slot/subslot/port: Specifies the modular cable interface and enters cable
interface-number interface configuration mode. Variables for this command
may vary depending on the Cisco CMTS router and the
Example: Cisco IOS software release. For details, see the Cisco IOS
Router(config)# interface modular-cable 1/0/0:0 CMTS Cable Command Reference.
• slot—Slot where a SPA interface processor (SIP) or a
line card resides.
• subslot—Secondary slot for a shared port adapter
(SPA) or a line card.
• port—Downstream port or the MAC domain index.
• interface-number—Modular cable interface number.
Step 3 cable downstream dsg disable Disables A-DSG forwarding and DCD messages on the
primary capable interface.
Example:
Router(config-if)# cable downstream dsg disable
Step 4 end Returns to privileged EXEC mode.
Example:
Router(config-if)# end
To verify details of a particular DSG classifier, use the show cable dsg cfr command as shown in the
following example:
Router# show cable dsg cfr 1010
To verify the detailed output for all DSG classifiers, use the show cable dsg cfr command as shown in
the following example:
Router# show cable dsg cfr verbose
Cfr Id : 1000
State : enable
Resolved : yes
Applied : yes
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 1000
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 232.10.10.0
Src Hostname : dsg-server-a
Src Hostname IP : 40.0.0.30
Src IP : 40.0.0.30
Src Prefix Length : 32
Dest Port Start : 2000
Dest Port End : 13821
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
Cfr Id : 1010
State : enable
Resolved : yes
Applied : yes
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 1010
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 232.10.10.10
Src Hostname : dsg-server-b
Src Hostname IP : 40.0.0.40
Src IP : 40.0.0.40
Src Prefix Length : 32
Dest Port Start : 2000
Dest Port End : 13821
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
Cfr Id : 2000
State : enable
Resolved : yes
Applied : yes
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 2000
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 232.10.11.0
Src Hostname : dsg-server-c
Src Hostname IP : 40.0.0.50
Src IP : 40.0.0.50
Src Prefix Length : 32
Dest Port Start : 13822
Dest Port End : 13822
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
Cfr Id : 2010
State : enable
Resolved : no
Applied : no
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 2010
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 232.10.11.10
Src Hostname : non-exist-hostname
Src Hostname IP : ----
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 2000
Dest Port End : 13821
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
Cfr Id : 3000
State : enable
Resolved : yes
Applied : yes
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 3000
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 239.10.11.11
Src Hostname : ----
Src Hostname IP : ----
Src IP : 0.0.0.0
Src Prefix Length : 32
Dest Port Start : 2000
Dest Port End : 13821
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
To verify the detailed output for a single DSG classifier, use the show cable dsg cfr command as shown
in the following example:
Router# show cable dsg cfr 1010 verbose
Cfr Id : 1010
State : enable
Resolved : yes
Applied : yes
Conflict : no
Conflict Cfr Id : --
Error Code : 0(DSG_CFR_ERR_NONE)
Tunnel Id : 1010
Dest Hostname : ----
Dest Hostname IP : ----
Dest IP : 232.10.10.10
Src Hostname : dsg-server-b
Src Hostname IP : 40.0.0.40
Src IP : 40.0.0.40
Src Prefix Length : 32
Dest Port Start : 2000
Dest Port End : 13821
Priority : 1
In DCD : yes
Forwarded : 0
Received : 0
To verify the verbose output of the mapping of the DSG hostnames and IP addresses on a Cisco CMTS
router, use the show cable dsg host command as shown in the following example:
Router# show cable dsg host verbose
The below example shows detailed information of all the classifiers associated to the specified tunnel.
Router# show cable dsg tunnel 1 cfr
tunnel cfr cfr cfr destination ip source ip srcPre d_port d_port
id id state pri address address length start end
1 1 en 0 230.1.0.1 0.0.0.0 32 0 65535
6 en 0 231.1.1.6 0.0.0.0 32 0 65535
7 en 0 231.1.1.7 0.0.0.0 32 0 65535
8 en 0 231.1.1.8 0.0.0.0 32 0 65535
The below example illustrates detailed information about all the clients associated to the specified
tunnel.
Router# show cable dsg tunnel 1 clients
The below example illustrates all DSG interfaces and rules associated to the specified tunnel.
Router# show cable dsg tunnel 1 interfaces
The below example illustrates all detailed information about the specified tunnel.
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
Note Beginning with Cisco IOS Release 12.2(33)SCG, the “TG state” field in the show cable dsg tg
command output was replaced by “Chan state” to indicate that a channel belonging to a tunnel group is
either enabled or diabled. It is possible that a tunnel group is enabled but a particular channel in that
tunnel group is disabled.
The below example displays the same information as above for the specified tunnel group.
Router# show cable dsg tg 1 channel 1
The below example illustrates detailed information for the specified tunnel group.
Router# show cable dsg tg 1 channel 1 verbose
The following is a sample output for the show cable dsg tg command that displays the ignore option,
introduced in Cisco IOS Release 12.2(33)SCD5, under the ‘In DCD’ column.
Router# show cable dsg tg 1 channel 1 verbose
Note The IGMP static group IP address created automatically at the time of DSG configuration is not
displayed in the show running-config interface command output in Cisco IOS Release 12.2(33)SCG
and later.
chan chFreq chan timer init oper twoWay oneWay num num num num num
list index freq index timeout timeout timer timer rule tunnel cfr client vsp
1 1 471 1 4 600 300 1800 6 6 3 4 2
2 477
3 483
4 583
Router#
02:08:42: DCD TLV last sent:
32360101 01020110 03040102 03040412 02060100 5E000001 04020951 01000102
00040506 01005E01 00010602 00012B08 08030000 01010101 170F0202 00010501
00090605 04E60100 01322801 01020201 10030401 02030404 0403020A BC050601
005E0100 02060200 022B0808 03000001 01010117 0F020200 02050100 09060504
E6010002 32280101 03020110 03040102 03040404 04020123 05060100 5E010003
06020003 2B080803 00000101 0101170F 02020003 05010009 060504E6 01000332
38010104 02010B04 12020601 005E0000 01040209 51010001 02000405 06000200
0200012B 09080300 00010102 01022B09 08030000 02010201 02322A01 01050201
0B040403 020ABC05 06000200 0200022B 09080300 00010102 01022B09 08030000
02010201 02324601 01060201 0B042002 06002100 21000102 06002100 21000202
06002100 21000302 06002100 21000405 06000200 0200032B 09080300 00010102
01022B09 08030000 02010201 02332801 041C12E3 C001041C 6E714001 041CC9FE
C0010422 BFDFC002 02000403 02025804 02012C05 020708
The following example illustrates typical information displayed with this command in DSG 1.2:
Router# show interfaces c5/0 dsg downstream tg
The following examples displays the same type of information as above for the given tunnel group.
Router# show interfaces c5/0 dsg downstream tg 1 channel 1
The following is a sample output for the show interfaces cable dsg downstream tg command that
displays the ignore option, introduced in Cisco IOS Release 12.2(33)SCD5, under the ‘In DCD’ column.
Router# show interfaces cable 7/0/0 dsg downstream tg
The following is a sample output for the show interfaces cable dsg downstream tunnel command that
displays the interface information for the DSG downstream tunnel in DSG 1.2:
Router# show interfaces c5/0 dsg downstream tunnel
The following is a sample output for the show interfaces cable dsg downstream tunnel command that
displays information for the specified interface and tunnel:
Router# show interfaces c5/0 dsg downstream tunnel 1
Each Cisco CMTS is configured as follows, and the remainder of this topic describes example
configurations that apply to this architecture.
CMTS Headend #1
• DSG Server #1—Connected to Cisco CMTS via IP Multicast, with DSG Server having IP Address
12.8.8.1
• Destination IP Address for the Cisco CMTS—228.9.9.1
• DSG Tunnel Address—0105.0005.0005
• Downstream #1 Supporting two DSG Clients:
– DSG Client #1—ID 101.1.1
– DSG Client #2—ID 102.2.2
CMTS Headend #2
• DSG Server #2—Connected to Cisco CMTS via IP Multicast, with DSG Server having IP Address
12.8.8.2
• Destination IP Address for the Cisco CMTS—228.9.9.2
• DSG Tunnel Address—0106.0006.0006
• Downstream #2 Supporting two DSG Clients:
– DSG Client #1—ID 101.1.1
– DSG Client #2—ID 102.2.2
• Downstream Rule #2
– DSG Rule ID #2
– DSG Client ID—102.2.2
– DSG Tunnel Address—106.6.6
Example of Two DSG Tunnels with Full Classifiers and MAC DA Substitution
In this configuration, and given the two Cisco CMTS Headends cited above, below are the two sets of
DSG rules, with each set applying to each Cisco CMTS, in respective fashion.
These settings apply to DSG #1:
• DSG Rule ID 1
• Downstreams 1 and 2
• DSG Client ID 101.1.1
• DSG Tunnel Address 105.5.5
• DSG Classifier ID—10
• IP SA—12.8.8.1
• IP DA—228.9.9.1
• UDP DP—8000
Example of One DSG Tunnel Supporting IP Multicast from Multiple DSG Servers
In this configuration, and given the two Cisco CMTS Headends cited earlier in this topic, below is an
example of one DSG Tunnel with multiple DSG servers supporting IP Multicast:
• DSG Rule ID 1
• Downstreams 1 and 2
• DSG Client ID 101.1.1 and 102.2.2
• DSG Tunnel Address 105.5.5
• DSG Classifier ID—10
– IP SA—12.8.8.1
– IP DA—228.9.9.1
– UDP DP—8000
• DSG Classifier ID—20
– IP SA—12.8.8.2
– IP DA—228.9.9.2
– UDP DP—8000
Additional References
The following sections provide references related to A-DSG 1.2.
Related Documents
Related Topic Document Title
Cisco CMTS Commands Cisco IOS CMTS Cable Command Reference
http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_bo
ok.html
DOCSIS 3.0 Multicast Support on the CMTS DOCSIS 3.0 Multicast Support on the CMTS Routers
Routers
http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/ubr_d3
0_mcast_support.html
Standards
Standard Title
CM-SP-DSG-I18-110623 DOCSIS Set-top Gateway (DSG) Interface Specification
MIBs
MIB MIBs Link
DOCS-DSG-IF-MIB To locate and download MIBs for selected platforms, Cisco IOS
releases, and feature sets, use Cisco MIB Locator found at the
following URL:
http://www.cisco.com/go/mibs
RFCs
RFCs Title
No new or modified RFCs are supported by this —
feature, and support for existing RFCs has not been
modified.
Technical Assistance
Description Link
The Cisco Support and Documentation website http://www.cisco.com/cisco/web/support/index.html
provides online resources to download documentation,
software, and tools. Use these resources to install and
configure the software and to troubleshoot and resolve
technical issues with Cisco products and technologies.
Access to most tools on the Cisco Support and
Documentation website requires a Cisco.com user ID
and password.
Note Table 2 lists only the software release that introduced support for a given feature in a given software
release train. Unless noted otherwise, subsequent releases of that software release train also support that
feature.
Table 2 Feature Information for DOCSIS Set-Top Gateway and A-DSG for the Cisco CMTS Routers
Table 2 Feature Information for DOCSIS Set-Top Gateway and A-DSG for the Cisco CMTS Routers
Table 2 Feature Information for DOCSIS Set-Top Gateway and A-DSG for the Cisco CMTS Routers
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned 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. (1110R)
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.
Note Use this document in conjunction with the Configuring Call Home for Cisco 7200 Series Routers feature
guide.
For Cisco IOS Release 12.2(33)SCE, the Call Home feature provides a mechanism to automatically
create cases and update Cisco, customer, or a partner about events and changes on a Cisco device in a
customer network. This feature provides e-mail and web-based notification of critical system events.
Multiple message formats are available for optimum compatibility with pager services, e-mail, or
XML-based automated parsing applications. Common uses of this feature include paging a network
support engineer, sending an e-mail notification to a Network Operations Center, XML-based message
delivery to a support website, and generating a direct case with the Cisco Systems Technical Assistance
Center (TAC).
For more information, see the Configuring Call Home for Cisco 7200 Series Routers feature guide.
Contents
• Prerequisites for the Call Home Feature for the Cisco CMTS Routers, page 50
• Information About the Call Home Feature for the Cisco CMTS Routers, page 50
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
Call Home Feature for the Cisco CMTS Routers
Prerequisites for the Call Home Feature for the Cisco CMTS Routers
Prerequisites for the Call Home Feature for the Cisco CMTS
Routers
Table 1 shows the hardware compatibility matrix for this feature.
Note The hardware components introduced in a given Cisco IOS Release are supported in all subsequent
releases unless otherwise specified.
Table 1 Call Home Feature for the Cisco CMTS Routers - Hardware Compatibility Matrix
Note For support of this feature on the Cisco uBR 7200 series universal broadband routers, see the
Configuring Call Home for Cisco 7200 Series Routers feature guide.
Information About the Call Home Feature for the Cisco CMTS
Routers
The Call Home feature provides a reactive support mode of operation triggered by various system events
on a Cisco uBR10012 universal broadband router. This feature also supports a proactive support mode
where configuration and inventory change messages are automatically reported to a destination target
specified in the system profile.
You can specify a Call Home Server on the Cisco network as a destination target.
The Call Home functionality in a Cisco device is provided by one or more network devices or through
an appliance, such as the Smart Call Home server. Each system event provides a set of call home triggers
required for reactive mode situations, for example, hardware failures.
The Call Home function can leverage Cisco, customer, or a partner support. Flexible message delivery
and format options allow for easy integration of specific support requirements into the Call Home and
Call Home Server.
For more information on setting up and configuring this feature, see the Configuring Call Home for
Cisco 7200 Series Routers feature guide.
<ch:CustomerId></ch:CustomerId>
<ch:SiteId></ch:SiteId>
<ch:ContractId></ch:ContractId>
<ch:DeviceId>UBR10012@C@SPE100202ZH</ch:DeviceId>
</ch:ContractData>
<ch:SystemInfo>
<ch:Name>router</ch:Name>
<ch:Contact></ch:Contact>
<ch:ContactEmail>[email protected]</ch:ContactEmail>
<ch:ContactPhoneNumber></ch:ContactPhoneNumber>
<ch:StreetAddress></ch:StreetAddress>
</ch:SystemInfo>
</aml-block:Builder>
<aml-block:BlockGroup>
<aml-block:GroupId>GC3:SPE100202ZH:D060082A</aml-block:GroupId>
<aml-block:Number>0</aml-block:Number>
<aml-block:IsLast>true</aml-block:IsLast>
<aml-block:IsPrimary>true</aml-block:IsPrimary>
<aml-block:WaitForPrimary>false</aml-block:WaitForPrimary>
</aml-block:BlockGroup>
<aml-block:Severity>1</aml-block:Severity>
</aml-block:Header>
<aml-block:Content>
<ch:CallHome xmlns:ch="http://www.cisco.com/2005/05/callhome" version="1.0">
<ch:EventTime>2010-10-13 10:27:39 GMT+00:00</ch:EventTime>
<ch:MessageDescription>Configuration Change</ch:MessageDescription>
<ch:Event>
<ch:Type>configuration</ch:Type>
<ch:SubType>delta</ch:SubType>
<ch:Brand>Cisco Systems</ch:Brand>
<ch:Series>Cisco uBR10K Series Routers</ch:Series>
</ch:Event>
<ch:CustomerData>
<ch:UserData>
<ch:Email>[email protected]</ch:Email>
</ch:UserData>
<ch:ContractData>
<ch:CustomerId></ch:CustomerId>
<ch:SiteId></ch:SiteId>
<ch:ContractId></ch:ContractId>
<ch:DeviceId>UBR10012@C@SPE100202ZH</ch:DeviceId>
</ch:ContractData>
<ch:SystemInfo>
<ch:Name>router</ch:Name>
<ch:Contact></ch:Contact>
<ch:ContactEmail>[email protected]</ch:ContactEmail>
<ch:ContactPhoneNumber></ch:ContactPhoneNumber>
<ch:StreetAddress></ch:StreetAddress>
</ch:SystemInfo>
<ch:CCOID></ch:CCOID>
</ch:CustomerData>
<ch:Device>
<rme:Chassis xmlns:rme="http://www.cisco.com/rme/4.0">
<rme:Model>UBR10012</rme:Model>
<rme:HardwareVersion>257</rme:HardwareVersion>
<rme:SerialNumber>SPE100202ZH</rme:SerialNumber>
<rme:AdditionalInformation>
<rme:AD name="PartNumber" value="800-09026-03" />
<rme:AD name="SoftwareVersion" value="12.2(20100929:171810)" />
<rme:AD name="SystemObjectId" value="1.3.6.1.4.1.9.1.317" />
<rme:AD name="SystemDescription" value="Cisco IOS Software, 10000 Software
(UBR10K4-K9P6U2-M), Experimental Version 12.2(20100929:171810) [username-card 111]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Wed 29-Sep-10 10:18 by username" />
</rme:AdditionalInformation>
</rme:Chassis>
</ch:Device>
</ch:CallHome>
</aml-block:Content>
<aml-block:Attachments>
<aml-block:Attachment type="inline">
<aml-block:Name>show diag</aml-block:Name>
<aml-block:Data encoding="plain">
<![CDATA[
Slot A:
Active PRE card
RP EEPROM contents:
Controller Type : 1443
Hardware Revision : 1.0
PCB Part Number : 73-10867-03
Board Revision : B0
Deviation Number : 0-0
Fab Version : 05
PCB Serial Number : CAT1336F051
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Top Assy. Part Number : 800-28163-03
CLEI Code : IPUCAM3BAC
Product Identifier (PID) : ESR-PRE4
Version Identifier (VID) : V03
FP EEPROM contents:
Controller Type : 1442
Hardware Revision : 1.0
PCB Part Number : 73-10866-03
Board Revision : B0
Deviation Number : 0-0
Fab Version : 04
PCB Serial Number : CAT1403F1JT
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Operational Image Version, Slot A
Cisco IOS Software, 10000 Software (UBR10K4-K9P6U2-M), Experimental Version
12.2(20100929:171810) [uname-card 111]
Copyright (c) 1986-2010 by Cisco Systems, Inc.
Compiled Wed 29-Sep-10 10:18 by uname
Reset reason 0x00000002 (software reset)
Slot B:
Standby PRE card
RP EEPROM Contents:
Slot 1:
2jacket-1 card, 0 ports
Card is full slot size
Card is analyzed
Card detected 2d06