|
|
Cisco uBR7246 universal broadband features enable the Cisco uBR7246 universal broadband router to communicate with a hybrid fiber coaxial (HFC) cable network via a Cisco MC11 cable modem card. Cisco MC11 cable modem cards allow you to connect cable modems on the HFC network to a Cisco uBR7246 in a Community Antenna Television (CATV) headend facility. The modem card provides the interface between the Cisco uBR7246 protocol control information (PCI) bus and the radio frequency (RF) signal on the HFC network.
The MC11 cable modem cards consist of the following components:
You must install at least one Cisco MC11 cable modem card in the Cisco uBR7246 chassis to establish communication between the Cisco uBR7246 and the HFC network.
Figure 1 shows the network topology for the modem card and illustrates network connections using the Cisco uBR7246.
As shown in Figure 1, the Cisco uBR7246 serves as an interface between a WAN backbone and an HFC cable plant. Typically installed at a CATV headend, the Cisco uBR7246 is often colocated with the following internet service provider-related components.
The Ethernet switch is used to reduce traffic on the WAN backbone.
The proxy server usually functions as a Web cache for host computers, and the DHCP/TFTP server for cable modems. DHCP for host computers in the HFC plant is often handled over the WAN. The WAN router provides a gateway to the data network.
On the RF side, the downstream port is assigned a 6-8 MHz channel slot at a standard broadcast CATV frequency. An upconverter device is used to convert the 44 MHz intermediate frequency (IF) output to the assigned slot. In North America, carrier frequencies in the forward plant are assigned between 54-860 MHz. After upconversion, the signal is combined with other analog TV or digital TV signals and sent to the transmit input of a fiber transceiver.
The receive input of the fiber transceiver is connected to an upstream port of the Cisco uBR7246. The upstream port is assigned a 0.2-3.2 MHz frequency band in the reverse plant. In North America, carrier frequencies in the reverse plant are between 5-42 MHz.
The fiber transceiver is connected to up to 80 kilometers of optical fiber. Signals are carried in analog form to a neighborhood where they terminate in a fiber node. The fiber node, located on a telephone pole or in an underground box, converts the optical signal back to an electrical signal which is passed on to a two-way, distribution amplifier system. The distribution amplifier system passes through the neighborhood where it is tapped off to individual CATV subscribers. Typically, there are 500-1500 homes passed per fiber node.
A coaxial cable delivers the signal from the tap to a subscriber's drop box. From the drop box, the signal is split and cabled to consumer CATV appliances. In addition to analog or digital television, the subscriber obtains data services using a cable modem appliance, like the Cisco uBR904 cable modem.
The Cisco uBR7246 features bring value to the digital broadband network by:
The Cisco uBR7246 cable modem cards are fully compatible with the Data Over Cable System Interface Specification (DOCSIS) established by major North American cable operators through the Multimedia Cable Network System (MCNS) consortium.
The Cisco uBR7246 supports both two-way and telephone return modems on a single downstream channel. The Cisco uBR7246 therefore allows both one-way and two-cable plants to provide cable modem service, and gives cable operators the flexibility to roll out service in systems that are only partially upgraded to two-way.
Community Antenna Television (CATV)---Broadband transmission facility.
Downstream---Frequency multiplexed band in a CATV channel that distributes signals from headend to users. In this instance, downstream refers to the data flow from the Cisco MC11 modem card in a Cisco uBR7246 to the user's cable modem.
Headend---Originating point of a signal in a Cable TV system.
Intermediate Frequency (IF)---Intermediate electromagnetic frequencies generated by a superheterodyne radio receiver.
Hybrid Fiber Coaxial Cable (HFC)---Distribution cabling concept using both fiber optic and coaxial cable. Fiber is used for the backbone distribution medium, terminating in a remote unit where optoelectrical conversion takes place. The signal is then passed as data to coaxial cables that carry it to its destination.
Quadrature Amplitude Modulation (QAM)---Modulation technique that allows data-encoded symbols to be represented in 16 or 32 different states.
Quaternary Phase Shift Keying (QPSK)---Compression technique used in modems and wireless networks, allowing the transmission of 2 bits per symbol. QPSK provides a 2:1 compression ratio, resulting in double efficiency for the circuit being used.
Radio Frequency (RF)---Group of electromagnetic energy whose wavelengths are between the audio and light range, usually between 500 KHz and 300 GHz.
Symbol---Phase range of a sine wave.
Upstream---Frequency multiplexed band in a CATV channel that distributes signals from transmitting stations to headend. In this instance, upstream refers to the data flow from a cable modem to the Cisco MC11 modem card in a Cisco uBR7246.
This feature is supported only on the Cisco uBR7246. The access unit installed in the subscriber's location is the Cisco uBR904 Cable Modem. Other compatible cable modems may also be used.
Before you can configure Cisco uBR7246 universal broadband router features, you must first:
The Cisco uBR7246 universal broadband features support the RF Interface Management Information Base (MIB). For descriptions of supported MIBs and how to use MIBs, see Cisco's MIB website on CCO at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml. No RFCs are supported by this feature.
The Cisco IOS software command-line interface (CLI) is used to configure the Cisco MC11 cable modem card for correct operation on the HFC network. Perform the following tasks to configure the MC11 cable modem card. For some tasks, the default values are adequate to configure the device; these configuration tasks are optional.
The first step in configuring the MC11 cable modem interface is to configure the downstream cable interface. In this case, downstream refers to the data flow from the Cisco MC11 modem card in a Cisco uBR7246 to the user's cable modem. Data passing through the MC11 cable modem card is converted to IF and then run through an upconverter to transform the signal to RF. This RF signal is then sent down the line to the user's cable modem. Downstream cable interface commands configure the frequency, symbol rate, compression, and modulation of the downstream signal.
Perform the following tasks to configure the downstream cable interface:
Downstream frequency is an information-only command that should reflect the digital carrier frequency, which is the center frequency of the downstream RF carrier (the channel) for that downstream port. The configuration controlling the digital carrier frequency is done in the IF-to-RF upconverter that must be installed in the downstream path from the Cisco uBR7246. Refer to the upconverter's manufacturer's instructions for information about configuring the upconverter.
The digital carrier frequency is specified to be the center of a 6.0 MHz channel. For example, EIA channel 95 spans 90.000 to 96.000 MHz. The center frequency is 93.000 MHz, which is the digital carrier frequency that should be configured as the downstream frequency.
To set the downstream center frequency, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable downstream frequency down-freq-hz | Enter the fixed center frequency for your downstream RF carrier in Hz. |
To verify the current value of the center frequency, enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency is not set. Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
If you are having trouble:
 | Caution The default downstream symbol rate is set to comply with MCNS specifications for Annex B cable modem support at 5.056941 Msps with 64-QAM modulation and 5.36037 Msps with 256-QAM modulation. This command should only be used to change the symbol rate to support Annex A cable modems that are used outside North America. |
To set the downstream symbol rate, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable downstream symbol-rate number | Set the downstream symbol rate for Annex A (5.056944 Msps). Do not enter the decimal point in the symbol rate. |
To verify the downstream symbol rate, enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
If you are having trouble:
Annex B is the North America standard and Annex A is the European standard. You should review your local standards and specifications for downstream MPEG framing to determine which format you should use.
To set the downstream MPEG framing format, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable downstream annex {A | B} | Set the downstream MPEG framing format. |
To verify the downstream MPEG framing format (Annex A or Annex B) setting, enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
If you are having trouble:
To set the downstream modulation, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable downstream modulation 64qam | Set the standard MCNS rate. |
To verify the downstream modulation setting, enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
If you are having trouble:
To set the downstream interleave depth, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable downstream interleave-depth {8 | 16 | 32 | 64 | 128} | Set the downstream interleave depth. |
To verify the downstream interleave depth setting, enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=
If you are having trouble:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface cable port/slot | Specify a cable interface and enter the cable interface configuration mode. | ||
| cable downstream if-output | Activate downstream digital data from the Cisco uBR7246. (This is the default setting.) |
To verify that the downstream carrier is active (up), enter the show controllers cable command for the downstream port that you have just configured:
router# show controllers cable 6/0 downstream
Cable6/0 Downstream is up
Frequency=96000000, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
If you are having trouble with this configuration:
The next step is to configure the upstream cable interface. In this case, upstream refers to the data flow from a cable modem to the Cisco MC11 modem card in a Cisco uBR7246. The user's cable modem sends an RF signal back to the MC11 cable modem card, which translates the RF signal back to data format. Upstream cable interface commands configure the frequency and input power level of the upstream signal, in addition to error detection and correction of the upstream signal.
The configuration of the upstream cable interface depends on each cable operator's physical plant.
Perform the following tasks to configure the upstream cable interface:
To set the upstream frequency, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable upstream port frequency up-freq-hz | Enter the fixed center frequency for your upstream RF carrier in Hz. |
To verify the current value of the upstream frequency, enter the show controllers cable command for the upstream port that you have just configured:
router#show controllers cable 6/0 u0 Cable6/0 Upstream 0 is upFrequency 7.008 MHz, Channel Width 1.6 MHz, QPSK Symbol Rate 1.280 Msps Nominal Input Power Level 0 dBmV, Tx Timing Offset 0 Ranging Backoff Start 0, Ranging Backoff End 4, Tx Backoff Start 0 Tx Backoff End 4, Modulation Profile Group 1 part_id=0x3136, rev_id=0x02, rev2_id=0x61 nb_agc_thr=0x0100, nb_agc_nom=0x3000 Range Load Reg Size=0x58 Request Load Reg Size=0x0C Minislot Size in number of Timebase Ticks is = 8 Minislot Size in Symbols =64 Minislot Size in Bytes = 16 UCD Count = 361894 DES Reg #580 = E204301, #584 = 3E030303, #588 = 0. #590 = C0C0C0C.
If you are having trouble:
The uBR7246 controls the output power levels of the cable modems to meet the desired upstream input power level. The default setting of 0 dBmV is the optimal setting for the upstream power level.
| Caution If you increase the input power level, the cable modems on your HFC network will increase their transmit power level. This might cause an increase in the carrier-to-noise ratio (CNR) on the network. Be careful if you adjust this parameter. You might violate the upstream return laser design parameters. |
To set the upstream input power level, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable upstream port power-level dbmv | Enter the upstream power level in dBmV. |
To verify the current value of the upstream input power level, enter the show controllers cable command for the upstream port that you have just configured:
router# show controllers cable 6/0 u0
Cable6/0 Upstream 0 is up
Frequency 7.008 MHz, Channel Width 1.6 MHz, QPSK Symbol Rate 1.280 Msps
Nominal Input Power Level 0 dBmV, Tx Timing Offset 0
Ranging Backoff Start 0, Ranging Backoff End 4, Tx Backoff Start 0
Tx Backoff End 4, Modulation Profile Group 1
part_id=0x3136, rev_id=0x02, rev2_id=0x61
nb_agc_thr=0x0100, nb_agc_nom=0x3000
Range Load Reg Size=0x58
Request Load Reg Size=0x0C
Minislot Size in number of Timebase Ticks is = 8
Minislot Size in Symbols = 64
Minislot Size in Bytes = 16
UCD Count = 361894
DES Reg #580 = E204301, #584 = 3E030303, #588 = 0.
#590 = C0C0C0C.
If you are having trouble:
To activate the upstream forward error correction, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable upstream port/slot fec | Enable FEC. |
To verify if FEC is activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information. The following is an excerpt from the more system:running-config command output.
router#more system:running-config
Building configuration...
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble:
 | Caution Scrambler must be activated for normal operation. Deactivate only for prototype modems that do not support scrambler. |
To activate the upstream scrambler, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable upstream port scrambler | Enable the scrambler. |
To verify if the upstream scrambler is activated, enter the command more system:running-config and look for the cable interface configuration information. The following is an excerpt from the more system:running-config command output.
router# more system:running-config
Building configuration...
Current configuration:
!
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
end
If you are having trouble:
Make sure that you have entered the correct upstream port number. Currently this is always u0.
Activate the RF carrier on the upstream ports. Each upstream port must be activated to enable upstream data from the cable modems on the HFC network to the Cisco uBR7246.
To activate the upstream ports, use the following commands in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| interface cable port/slot | Specify a cable interface, and enter the cable interface configuration mode. | ||
| no cable upstream 0 shutdown | Enable upstream data traffic. |
To verify if the upstream ports are activated or deactivated, enter the show interface cable command for the upstream port that you have just configured:
router# show interface cable 6/0
Cable6/0 is up, line protocol is up
Hardware is BCM3210 FPGA, address is 00e0.1e5f.7a60 (bia 00e0.1e5f.7a60)
Internet address is 1.1.1.3/24
MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation, loopback not set, keepalive not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:25, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sea, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
10878 packets input, 853740 bytes, 0 no buffer
Received 3679 broadcasts, 0 runts, 0 giants, 0 throttles
3 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5401 packets output, 645885 bytes, 0 underruns
0 output errors, 0 collisions, 9 interface resets
0 output buffer failures, 0 output buffers swapped out
If you are having trouble:
To encrypt upstream and downstream data, you need to configure and activate baseline privacy. Baseline privacy on an HFC network is configured with key encryption keys (keks) and traffic encryption keys (teks). The encryption is based on 40-bit or 56-bit data encryption standard (DES) encryption algorithms.
A kek is assigned to a cable modem based on the cable modem's service identifier (SID) and permits the cable modem to connect to the Cisco uBR7246 when baseline privacy is activated. The tek is assigned to a cable modem when its kek has been established. The tek is used to encrypt data traffic between the cable modem and the Cisco uBR7246.
Keks and teks can be set to expire based on a grace-time or a life-time value. A grace-time key is used to assign a temporary key to a cable modem to access the network. A life-time key is used to assign a more permanent key to a cable modem. Each cable modem that has a life-time key assigned will request a new life-time key from the Cisco uBR7246 before the current one expires.
The configuration and activation of baseline privacy depend on each cable operator's physical plant.
To configure and activate baseline privacy, perform the following tasks:
To configure kek data privacy on the HFC network, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
cable privacy kek grace-time seconds | Set the cable privacy kek grace-time. |
A grace-time kek can be set from 300 to 1,800 seconds. A life-time kek can be set from 86,400 to 6,048,000 seconds.
To verify the kek life-time or grace-time values that have been set, enter the show cable privacy kek command:
router# show cable privacy kek
Configured KEK life-time value = 750000
If you are having trouble, make sure you have entered a valid value for grace-time or life-time.
| Command | Purpose |
|---|---|
cable privacy tek grace-time seconds | Set the cable privacy tek grace-time. |
A grace-time tek can be set from 300 to 1,800 seconds. A life-time tek can be set from 1,800 to 604,800 seconds.
To verify the tek life-time or grace-time values that have been set, enter the show cable privacy tek command:
router# show cable privacy tek
Configured TEK life-time value = 56000
If you are having trouble, make sure you have entered a valid value for grace-time or life-time.
After the kek and tek vales have been set, you can activate encryption on the HFC network.
To activate baseline data privacy on the HFC network, use the following commands in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| cable privacy enable | Activate cable privacy. This is the default. | ||
| cable privacy mandatory | Activate cable privacy and do not allow access for any unencrypted cable modem connections. |
To verify if baseline privacy is activated, enter the cable privacy enable or cable privacy mandatory command. By default, cable privacy is enabled and can only be disabled with the no cable privacy command.
If you are having trouble, make sure you have entered a valid value for grace-time or life-time for kek and tek privacy.
Frequency agility is a way to improve performance on upstream signal traffic and to compensate for noise and interference. The spectrum manager monitors the upstream frequencies; if too much noise or interference is detected in an upstream channel, the spectrum manager reassigns the upstream channel to a different upstream frequency.
Frequency agility is configured and activated using spectrum groups. A spectrum group is a table of frequencies that can be used by upstream ports to implement a frequency-hopping policy. There are two types of policies, blind and scheduled, with two corresponding types of spectrum groups.
The configuration and activation of frequency agility depends on each cable operator's physical plant.
To configure and activate frequency agility, perform the following tasks:
To create spectrum groups, use the following commands in global configuration mode:
| Step | Command | Purpose | ||
|---|---|---|---|---|
| cable spectrum-group group-number type blind | Create a blind spectrum group. | ||
| cable spectrum-group group-number type scheduled daily | Create a scheduled spectrum group that can change its frequency and power level at the same time every day. | ||
| cable spectrum-group group-number type scheduled periodic-sec seconds | Create a scheduled spectrum group that can change its frequency and power level at a specified interval in seconds. |
To verify that a spectrum group has been created, enter the show cable spectrum-group command:
router# show cable spectrum-group spectrum-group 1 spectrum-group 2 spectrum-group 3
If you are having trouble, make sure you have entered a valid spectrum group number and type.
To configure and activate a spectrum group, use the following command in global configuration mode:
| Command | Purpose |
|---|---|
cable spectrum-group group-number [time hh:mm:ss] frequency number [power-level-dbmv] | Add the upstream frequency to the list of valid frequencies with a default power level for a spectrum group. |
To verify if spectrum groups have been configured and activated, enter the show cable spectrum-group command:
router# show cable spectrum-group spectrum-group 1 6 .500 MHz 0 dBmV input level 7 .000 MHz 0 dBmV input level spectrum-group 2 7 .500 MHz -5 dBmV input level spectrum-group 3 9 .000 MHz -0 dBmV input level 9 .500 MHz -5 dBmV input level
If you are having trouble, make sure you entered a valid spectrum group number, time, frequency, and input power level.
To activate ARP requests, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable arp | Enable ARP. |
To verify if ARP has been activated, enter the command more system:running-config and look for the cable interface configuration information. If ARP has been activated, it does not appear in this output. If ARP has been deactivated, it will appear in the output as no cable arp as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
no cable arp
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure you entered the correct port and modem card slot number when you activated ARP and when you entered the show interface cable command.
To activate proxy ARP for host-to-host communications, use the following command in cable interface configuration mode:
| Command | Purpose |
|---|---|
cable proxy-arp | Enable proxy ARP on the cable interface. |
To verify if proxy ARP has been activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information. If proxy ARP has been activated, it does not appear in this output. If proxy ARP has been deactivated, it will appear in the output as no cable proxy-arp as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
no cable proxy-arp
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure you entered the correct port and modem card slot number when you activated proxy ARP.
To configure optional IP parameters, perform the following tasks:
| Command | Purpose |
|---|---|
cable ip-multicast-echo | Enable IP multicast echo. |
To verify if IP multicast echo has been activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information. If IP multicast echo has been activated, it does not appear in this output. If IP multicast echo has been deactivated, it appears in this output as no cable ip-multicast-echo as shown in the command output excerpt below:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
no cable ip-multicast-echo
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure that you have entered the correct slot and port numbers when you entered cable interface configuration mode.
| Command | Purpose |
|---|---|
cable ip-broadcast-echo | Enable IP broadcast echo. |
To verify if IP broadcast echo has been activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
cable ip-broadcast-echo
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure that you entered the correct slot and port numbers when you entered cable interface configuration mode.
To manage cable modems, perform the following tasks:
To activate cable modem authentication, use the following command from the cable interface configuration mode:
| Command | Purpose |
|---|---|
cable shared-secret secret-key | Enable cable modem authentication. |
To verify if cable modem authentication has been activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information. If cable modem authentication has been activated, it does not appear in this output. If cable modem authentication has been deactivated, it appears in this output as no cable secret-shared as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
no cable secret-shared
cable insertion-interval 150000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure you entered the correct slot and port numbers when you entered cable interface configuration mode.
To activate or deactivate cable modem upstream verification, use the following command:
| Command | Purpose |
|---|---|
cable source-verify | Activate cable modem upstream verification. |
To verify that cable modem upstream verification has been activated or deactivated, enter the command more system:running-config and look for the cable interface configuration information. If cable modem upstream verification has been deactivated, it does not appear in this output. If cable modem upstream verification has been activated, it appears in this output as cable source-verify as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
cable source-verify
cable insertion-interval 2000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure that you entered the correct slot and port numbers when you entered cable interface configuration mode.
To activate cable modem insertion interval, use the following command in cable interface configuration mode:
| Command | Task |
|---|---|
cable insertion-interval milliseconds | Set the insertion interval in milliseconds. |
To verify that a cable modem insertion interval has been set, enter the command more system:running-config and look for the cable interface configuration information as shown in this command output excerpt:
router# more system:running-config
Building configuration...
Current configuration:
!
interface Cable6/0
ip address 1.1.1.1 255.255.255.0
no keepalive
cable insertion-interval 2000
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream symbol-rate 5056941
cable upstream 0 frequency 15008000
cable upstream 0 fec
cable upstream 0 scrambler
no cable upstream 0 shutdown
!
If you are having trouble, make sure that you entered the correct slot and port numbers when you typed the command.
! Enter the global configuration mode. configure terminal ! !Enter the cable interface configuration mode. This example shows that the !Cisco MC11 card is in the 6th slot or bottom slot of the Cisco uBR7246 chassis. interface cable 6/0 ! !Configure the upstream data frequency. In this example, for channel 0, the frequency is 15, 800 MhZ, or 15,800,000 Hz. cable u0 1580000 !Enable cable interface. no cable upstream 0 shutdown ! Enable router interface. no shutdown !Set interface's IP address ip address <ipaddr> <subnet mask> end
This section documents new or modified commands on the Cisco uBR7246. All other commands used with this feature are documented in the Cisco IOS Release 11.3 command references.
The following commands are new or have been modified to support the Cisco uBR7246:
This command has no arguments or keywords.
ARP enabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
ARP is an Internet protocol used to map IP addresses to MAC addresses on computers and other equipment installed in a network. You need to activate ARP requests so the Cisco uBR7246 can perform IP address resolution on the downstream path.
This following example activates cable ARP requests for port 0 on the cable modem installed in slot 6:
configure terminal interface cable 6/0 cable arp
sid | Service identifier (SID) of the cable modem. Valid entries are from 1 to 8191. |
channel | User-defined or user-selected; in the current release, there is only one upstream channel available. Therefore, this value is always 0. |
0
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Moving a cable modem to a new channel can improve performance, increase bandwidth availability, or troubleshoot a cable modem. You use the SID to identify a particular cable modem.
The following example changes a cable modem channel allocation from SID 50 to 0:
interface cable 6/0 cable channel-change 50 0
A | Annex A. The downstream is compatible with the European MPEG framing format specified in ITU-TJ.83 Annex A. |
B | Default. The downstream is compatible with the North American MPEG framing format specified in ITU-TJ.83 Annex B. |
Annex B
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The MPEG framing format must be compatible with the downstream symbol rate you set. Annex B is the North America standard and Annex A is the European standard. You should review your local standards and specifications for downstream MPEG framing to determine which format you should use.
The following example sets the MPEG framing format to Annex A:
interface cable 6/0 cable downstream annex A
down-freq-hz | The known center frequency of the downstream carrier in Hz. The valid range is 54,000,000 to 1,020,000,000 Hz. |
Disabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
You need to set the downstream frequency of your RF output to comply with the expected input frequency of your upconverter. To do this, you enter the fixed center frequency of the downstream RF carrier for a downstream port. (You can also select a default which does not set a specific fixed value.) The valid range for a fixed center frequency is 54,000,000 to 1,020,000,000 Hz. The center frequency is also used to configure an IF-to-RF upconverter that must be installed in your downstream path.
To calculate the center frequency, add the frequencies in Hz of the lowest channel and the highest channel available at your headend. Divide that number by 2. The typical range for current CATV headends is 88,000,000 to 860,000,000 Hz; the MCNS specification is 94,000,000 to 860,000,000 Hz.
The following example sets the downstream center frequency:
interface cable 6/0 cable downstream frequency 96000000
This command has no arguments or keywords.
Downstream carrier enabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The following example enables the downstream port 0 on the cable modem installed in slot 6:
interface cable 6/0 cable downstream if-output
8 | 16 | 32 | 64 | 128 | Indicates the amount of time (in milliseconds) that defines the downstream interleave depth. The default is 32. |
32
Interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
This command sets the minimum latency of the system. Higher interleave depth provides more protection from bursts of noise on the HFC network; however, higher depth also increases downstream latency. Table 1 shows interleave characteristics.
| I (Number of Taps) | J (Increment) | Burst Protection 64 QAM/256QAM | Latency 64QAM/256QAM |
|---|---|---|---|
8 | 16 | 5.9 µsec/4.1 µsec | 0.22 msec/0.15 msec |
16 | 8 | 12 µsec/8.2 µsec | 0.48 msec/0.33 msec |
32 | 4 | 24 µsec/16 µsec | 0.98 msec/0.68 msec |
64 | 2 | 47 µsec/33 µsec | 2.0 msec/1.4 msec |
128 | 1 | 95 µsec/66 µsec | 4.0 msec/2.8 msec |
The following example configures the downstream interleave depth to 128:
interface cable 6/0 cable downstream interleave-depth 128
64qam | Modulation is 6 bits per symbol. |
64qam
Cable interface configuration
This command was added in Cisco IOS Release 11.3 XA.
Downstream modulation is the speed at which downstream data travels to the user; by setting the downstream modulation, you define the speed, which is 64qam (6 bits per downstream symbol rate, which is the standard Multimedia Cable Network Systems (MCNS) rate).
The following example sets the downstream modulation:
interface cable 6/0 cable downstream modulation 64
number | Number of megasymbols per second (Msps) rate for a downstream port. The valid range is 0 to 6000000 Msps. |
5056941 symbols per second (sps) with 64-QAM and 5360537 sps for 256-QAM.
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
A symbol is the basic unit of modulation. QPSK encodes 2 bits per symbol, 16-QAM encodes 4 bits per symbol, 64-QAM encodes 6 bits per symbol, and 256-QAM encodes 8 bits per symbol. The valid range for the downstream symbol rate is 0 to 6,000,000 Msps.
| Caution The default downstream symbol rate is set to comply with MCNS specifications for Annex B cable modem support at 5.056941 Msps with 64-QAM modulation and 5.36037 Msps with 256-QAM modulation. This command should only be used to change the symbol rate to support Annex A cable modems that are used outside of North America. |
The following example sets the downstream symbol rate to 5056941 symbols per second (sps) to comply with MCNS specifications for Annex B:
interface cable 6/0 cable downstream symbol-rate 5056941
milliseconds | Amount of time in milliseconds the cable modem can request a channel. Valid entries are from 100 to 2000 milliseconds. |
2000 milliseconds
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
When a cable modem connects to the HFC network, it requests a channel from the Cisco uBR7246. Use the cable insertion-interval command to limit the amount of time that a cable modem requests a channel for the first time from the Cisco uBR7246. A cable modem's initial channel request is known as insertion.
The following example limits the amount of time that a cable modem can request a channel for the first time from the Cisco uBR7246 (insertion-interval) to 1500 milliseconds:
interface cable 6/0 cable insertion-interval 1500
This command has no arguments or keywords.
IP multicast echo is enabled.
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The following example activates IP multicast echo:
interface cable 6/0 cable ip-multicast-echo
This command has no arguments or keywords.
IP broadcast echo is disabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The following example activates IP broadcast echo:
interface cable 6/0 cable ip-broadcast-echo
seconds | Number of seconds defining the length of key encryption grace-time. Valid range is 300 to 1800 seconds. Default is 600 seconds. |
600 seconds for kek grace-time
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Baseline privacy on an HFC network is configured with key encryption keys (keks) and traffic encryption keys (teks). The encryption is based on 40-bit or 56-bit data encryption standard (DES) encryption algorithms.
A kek is assigned to a cable modem based on the cable modem's service identifier (SID) and permits the cable modem to connect to the Cisco uBR7246 when baseline privacy is activated. Keks can be set to expire based on a grace-time or a life-time value. A grace-time key is used to assign a temporary key to a cable modem to access the network.
A cable modem must renew its kek (grace-seconds) before it expires.
The following example sets kek privacy grace-time to 800 seconds:
configure terminal cable privacy kek grace-time 800
seconds | Number of seconds defining the length of the key encryption life-time.Valid range is 86400 to 6048000. Default is 604800 seconds. |
604800 seconds for kek life-time
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Baseline privacy on an HFC network is configured with key encryption keys (keks) and traffic encryption keys (teks). The encryption is based on 40-bit or 56-bit data encryption standard (DES) encryption algorithms.
A kek is assigned to a cable modem based on the cable modem's service identifier (SID) and permits the cable modem to connect to the Cisco uBR7246 when baseline privacy is activated. Keks can be set to expire based on a grace-time or a life-time value. A life-time key is used to assign a more permanent key to a cable modem. Each cable modem that has a life-time key assigned will request a new life-time key from the Cisco uBR7246 before the current one expires.
A cable modem must renew its kek (lifetime-seconds) before it expires.
The following example sets kek privacy life-time to 750,000 seconds:
configure terminal cable privacy kek life-time 750000
seconds | Number of seconds defining the length of traffic encryption grace-time. Valid range is 300 to 1800 seconds. Default is 600 seconds. |
600 seconds for tek grace-time
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Baseline privacy on an HFC network is configured with key encryption keys (keks) and traffic encryption keys (teks). The encryption is based on 40-bit or 56-bit data encryption standard (DES) encryption algorithms.
The tek is assigned to a cable modem when its kek has been established. The tek is used to encrypt data traffic between the cable modem and the Cisco uBR7246. Teks can be set to expire based on a grace-time or a life-time value. A grace-time key is used to assign a temporary key to a cable modem to access the network.
A cable modem must renew its tek (grace-seconds) before it expires.
The following example sets traffic encryption key grace-time to 800 seconds:
configure terminal cable privacy tek grace-time 800
seconds | Number of seconds defining the length of the traffic encryption lifetime.Valid range is 1800 to 6048000. Default is 43200 seconds. |
43,200 seconds for tek life-time
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Baseline privacy on an HFC network is configured with key encryption keys (keks) and traffic encryption keys (teks). The encryption is based on 40-bit or 56-bit data encryption standard (DES) encryption algorithms.
The tek is assigned to a cable modem when its kek has been established. The tek is used to encrypt data traffic between the cable modem and the Cisco uBR7246. Teks can be set to expire based on a grace-time or a life-time value. A life-time key is used to assign a more permanent key to a cable modem. Each cable modem that has a life-time key assigned will request a new life-time key from the Cisco uBR7246 before the current one expires.
A cable modem must renew its tek (life-time second) before it expires.
The following example sets traffic encryption key life-time to 43,200 seconds:
configure terminal cable privacy tek life-time 43200
This command has no arguments or keywords.
Disabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Because the downstream and upstream are separate interfaces, modems can not directly perform address resolution with other modems on the cable plant. This command allows modems to perform address resolution through a proxy.
The following example activates proxy ARP for host-to-host communications:
interface cable 6/0 cable proxy-arp
secret-key | Text string used as secret key. Text string can be from 1 to 80 characters in length. |
Null string
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Use this command to activate authentication so that all cable modems must return a known text string to register with the Cisco uBR7246 for access to the network.
The following example activates cable modem authentication, using "scoobee" as the shared secret key:
interface cable 6/0 cable shared-secret scoobee
group-number | Spectrum group number. Valid range is from 1 to 32. |
blind | Allows the upstream frequency and input power level to change whenever noise impairs upstream data traffic. |
scheduled | Allows the upstream frequency and power level to change at set times in a day. |
daily periodic-sec | Allows the upstream frequency level at a specified interval in seconds. |
seconds | Rate in seconds when upstream frequency and power level change. |
No spectrum group is defined.
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
Upstream traffic may be affected by noise or other cable plant impairment. The spectrum manager monitors the upstream traffic. If station maintenance messages from cable modems are not received for approximately 2.5 minutes, then the spectrum manager reassigns a different upstream frequency to the upstream channel.
Frequency agility is configured and activated using spectrum groups. A spectrum group is a table of frequencies that can be used by upstream ports to implement a frequency-hopping policy. There are two types of policies, blind and scheduled, with two corresponding types of spectrum groups.
A maximum of 32 spectrum groups can be configured in the system.
The following example creates spectrum groups and sets the periodic rate to 48000 seconds:
configure terminal cable spectrum-group 1 type blind cable spectrum-group 2 type scheduled daily cable spectrum-group 3 type scheduled periodic-sec 48000
group-number | Spectrum group number. Valid range is 1 to 32. Configuring a spectrum group with multiple entries of this type, defines a list of frequencies which are available for use as upstream frequencies. |
time hh:mm:ss | (Optional) For scheduled spectrum groups, specifies the time of day that the frequency and input power level should change. |
up-freq-hz | Upstream frequency. Valid range is 5,000,000 to 42,000,000 Hz. |
power-level-dbmv | (Optional) Nominal input power level. Valid range is -10 to +10 decibels per millivolt (dBmV). Some cable plants might want to change only the input power level and not frequency on a daily time schedule. |
Operator must determine a value based on his spectrum allocation plan.
Global configuration
This command first appeared in Cisco IOS Release 11.3 XA.
After you create a spectrum group, you need to configure a list of upstream frequencies and nominal power levels that each spectrum group can use when an upstream frequency change is necessary. Each spectrum group should have its own list of upstream frequencies. Valid frequencies are 5,000,000 to 42,000,000 Hz, and valid power levels are -10 dBmV to 10 dBmV. The power level value should only be changed if you want to change only the power level as part of spectrum management. The standard power level is 0 dBmV.
The following example creates spectrum group frequencies:
configure terminal cable spectrum-group 1 frequency 6500000 cable spectrum-group 1 frequency 7000000d cable spectrum-group 2 frequency 750000 -5 cable spectrum-group 3 time 02:00:00 frequency 9000000 cable spectrum-group 3 time 02:00:00 frequency 9500000 -5 end
This command has no arguments or keywords.
Disabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The following example activates cable upstream verification:
configure terminal interface cable 6/0 cable source-verify
port | The port number identifying the location of the installed Cisco MC11cable modem card. |
FEC is disabled.
Interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The Cisco uBR7246 uses forward error correction (FEC) to attempt to correct any upstream data that might have been corrupted. To use this feature, you need to activate FEC on the upstream RF carrier. When FEC is activated, the Cisco uBR7246 commands all cable modems on the network to activate FEC.
The following example activates upstream forward error correction:
configure terminal interface cable 6/0 cable upstream 0 fec
You can use the master indexes or search online to find documentation of related commands.
cable upstream frequency
cable upstream power level
cable upstream scrambler
cable upstream shutdown
port | The port number identifying the location of the installed Cisco MC11 cable modem card. |
up-freq-hz | The upstream center frequency is configured to a fixed value. The valid range is 5,000,000 to 42,000,000 Hz. |
Upstream center frequency is not configured to a fixed value.
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
You need to set the upstream frequency of your RF output to comply with the expected input frequency of your Cisco MC11 cable modem. You do this by entering a fixed frequency of the upstream RF carrier for an upstream port. The valid range for a fixed upstream frequency is 5,000,000 Hz to 42,000,000 Hz.
The following example configures the upstream center frequency for port 0 (located in slot 6) to 5,700,000 Hz.
interface cable 6/0 cable upstream 0 frequency 5700000
port | The port number identifying the location of the installed Cisco MC11. |
dbmv | Decibels per millivolt designating the upstream signal input power level. Valid range of -10 decibels per millivolt (dBmV to 10 dBmV). |
Upstream nominal input power level is configured to 0 dBmV
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The power level of the upstream signal has to match MC11 cable modems expected input power levels. Because of this, you need to set the nominal input power level for the upstream RF carrier in decibels per millivolt (dBmV). You can also select the default of 0 dBmV, which is the optimal setting for the upstream power level.
The valid range for the input power level is -10 dBmV to 10 dBmV. Higher values cause the modems to increase their transmit power, achieving a greater carrier-to-noise ratio (CNR). If your power levels operate at greater than 10 dBmV, you must use an in-line attenuator to bring the power level to within the valid range.
| Caution If you increase the input power level, the cable modems on your HFC network will increase their transmit power level. This might cause an increase in the carrier-to-noise ratio (CNR) on the network. Be careful if you adjust this parameter. You might violate the upstream return laser design parameters. |
The following example sets the upstream input power level:
interface cable 6/0 cable upstream 0 power-level -5
You can use the master indexes or search online to find documentation of related commands.
cable upstream fec
cable upstream frequency
cable upstream scrambler
cable upstream shutdown
port | The port number identifying the location of the installed Cisco MC11. |
Upstream scrambler disabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
You need to activate the scrambler on the upstream RF carrier so that the cable modems on the HFC network will use built-in scrambler circuitry for upstream data transmissions. The scrambler circuitry improves reliability of the upstream receiver on the cable modem card. This command causes modems to enable their pseudo-random scrambler circuitry to improve the robustness of the upstream receiver on the line card.
| Caution Scrambler must be activated for normal operation. Deactivate only for prototype modems that do not support scrambler. |
The following example activates the upstream scrambler:
interface cable 6/0 cable upstream 0 scrambler
You can use the master indexes or search online to find documentation of related commands.
cable upstream fec
cable upstream frequency
cable upstream power level
cable upstream shutdown
port | The port number identifying the location of the installed Cisco MC11. |
Upstream port enabled
Cable interface configuration
This command first appeared in Cisco IOS Release 11.3 XA.
The following example disables the upstream ports:
interface cable 6/0 cable upstream 0 shutdown
This command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show cable burst-profile command:
router# show cable burst-profile Burst Type Preamb Diff FEC err FEC Scrambl Max Guard Last Scrambl profile length encode correct codeword seed burst time codeword number length size size shortened 1 1 48 no 0x0 0x6 0x152 1 16 1 yes 2 1 48 no 0x0 0x6 0x152 1 12 1 no 3 1 48 no 0x5 0x2C 0x152 0 48 1 yes 4 1 48 no 0x5 0x2C 0x152 0 48 1 yes 5 1 48 no 0x5 0x32 0x152 0 20 1 yes 6 1 48 no 0x0 0x32 0x152 0 20 1 no
Table 2 describes the fields shown in the show cable burst-profile display.
| Field | Description |
Burst profile number | The number of the burst profile. |
Type | Type of burst profile. |
Preamb length | Length of the preamble. |
Diff encode | Shows if there is a diff encode. |
FEC err correct | Shows the forward error correction. |
FEC codeword length | Shows the length of the forward error correction codeword. |
Scrambl seed | Shows the seed of the scrambler. |
Max burst size | Designates the maximum burst size. |
Guard time size | Indicates the guard time size. |
Last codeword shortened | Shows last codeword shortened. |
Scrambl | Indicates whether scramble is enabled (yes) or not (no). |
You can use the master indexes or search online to find documentation of related commands.
show cable modem
show cable modulation profile
show cable privacy
show cable qos
show cable spectrum-group
To view configuration settings on the Cisco uBR7246, use the show cable EXEC command.
show cable modem [ip-address]
ip-address | (Optional) Specify the IP address of the modem. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
This command displays information on all cable modems or a particular cable modem on the network.
The following are sample outputs from the show cable modem command specifying two different IP addresses:
router# show cable modem 172.16.0.0 Interface Upstream Timing offset SID QoS IP address MAC address Cable6/0 U0 2851 1 2 1.1.1.5 00e0.1eab.2c0b Cable6/0 U0 2850 2 2 1.1.1.7 00e0.1eb2.bb07 Cable6/0 U0 2852 3 2 1.1.1.2 00e0.1eab.2c29 Cable6/0 U0 2851 4 2 1.1.1.6 00e0.1eb2.bb8f Cable6/0 U0 2851 5 2 1.1.1.3 00e0.1eb2.bb53 Cable6/0 U0 2852 6 2 1.1.1.4 00e0.1eb2.bbb1 router# show cable modem 1.1.1.5 Interface Upstream Timing offset SID QoS IP address MAC address Cable6/0 U0 2851 1 2 1.1.1.5 00e0.1eab.2c0b
Table 3 describes the fields shown in the show cable modem display.
| Field | Description |
|---|---|
Interface | The interface on which the cable modem has an active connection. |
Upstream | The upstream port on the interface that is being used by the cable modem. |
Timing offset | The cable modem's current timing adjustment in units of the 10.24 MHz time base tick. |
SID | The service identifier assigned to the modem. |
QoS | The service class assigned to the modem. |
IP address | IP address of the modem. |
MAC address | Media access layer address. |
You can use the master indexes or search online to find documentation of related commands.
show cable burst-profile
show cable modulation-profile
show cable privacy
show cable qos
show cable spectrum-group
This command has no arguments or keywords.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
This command displays modulation profile group information. A modulation profile is a collection of six burst profiles that are sent out in a UCD message to configure a modem's transmit parameters for the following upstream message types: request, request/data, initial maintenance, station maintenance, short grant, and long grant.
The following is sample output from the show cable modulation-profile command:
router# show cable modulation-profile Modulation profile group Interval usage code Burst profile number 1 1 1 1 3 3 1 4 4 1 5 5 1 6 6
Table 4 describes the fields shown in the show cable modulation-profile display.
.
| Field | Description |
|---|---|
Modulation profile group | A modulation profile group is the set of burst profiles that define upstream transmit characteristics for the various types of upstream transmission classes. |
Interval usage code | Each upstream transmit burst belongs to a class which is given a number called the IUC (interval usage code). Bandwidth maps messages (MAP) by used IUC codes to allocate upstream time slots. The following types are currently defined: 1. Request: bandwidth request slot 2. Request/Data: bandwidth request or data slot 3. Initial Maintenance: initial link registration contention slot 4. Station Maintenance: link keep-alive slot 5. Short Data Grant: short data burst slot 6. Long Data Grant: long data burst slot |
Burst profile number | Burst profile number as displayed by the show cable burst-profile command. |
You can use the master indexes or search online to find documentation of related commands.
show cable burst-profile
show cable modem
show cable privacy
show cable qos
show cable spectrum-group
To display baseline privacy information, use the show cable privacy Privileged EXEC command.
show cable privacy {tek | kek}
tek | Traffic encryption key. |
kek | Key encryption key. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following are sample outputs for the show cable privacy command:
router#show cable privacy tek Configured TEK life-time value = 56000 Configured TEK grace-time value = 900router#show cable privacy kek Configured KEK life-time value = 750000 Configured KEK grace-time value = 800
Table 5 describes the fields shown in the show cable privacy displays.
| Field | Description |
|---|---|
Configured TEK life-time value = | Number of seconds defining the length of the traffic encryption life-time. Valid range is 1,800 to 6,048,000 seconds. Default is 43,200 seconds. |
Configured TEK grace-time value = | Number of seconds defining the length of traffic encryption grace-time. Valid range is 300 to 1,800 seconds. Default is 600 seconds. |
Configured KEK life-time value = | Number of seconds defining the length of the key encryption life-time. Valid range is 86,400 to 6,048,000. Default is 604,800 seconds. |
Configured KEK grace-time value = | Number of seconds defining the length of key encryption grace-time. Valid range is 300 to 1,800 seconds. Default is 600 seconds. |
You can use the master indexes or search online to find documentation of related commands.
show cable burst-profile
show cable modem
show modulation-profile
show cable qos
show cable spectrum-group
This command has no arguments or keywords.
EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show cable qos command:
router# show cable qos Service Priority Max upstream Guarantee upstream Max downstream Max tx class bandwidth bandwidth bandwidth burst 1 7 0 0 0 0 2 7 2000000 100000 4000000 0
Table 6 describes the fields shown in the show cable qos display.
| Field | Description |
|---|---|
Service class | Service class number, arbitrarily assigned. |
Priority | Upstream bandwidth request priority. |
Max upstream bandwidth | Upper rate limit for granted upstream bandwidth. |
Guarantee upstream bandwidth | Lower rate limit for granted upstream bandwidth. |
Max downstream bandwidth | Upper rate limit for granted downstream bandwidth. |
Max tx burst | Maximum size of an upstream burst in minislots. |
You can use the master indexes or search online to find documentation of related commands.
show cable burst-profile
show cable modem
show modulation-profile
show cable spectrum-group
To display spectrum group information, use the show cable spectrum-group Privileged EXEC command.
show cable spectrum group [group-number]
group-number | The assigned group number of the spectrum group. |
EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
Use this command to display spectrum group information. Spectrum groups are used to manage frequency agility; the automatic reassignment of upstream channels when a channel shows loss of signal quality.
The following are sample outputs from two uses of the show cable spectrum-group command:
router# show cable spectrum-group spectrum-group 16 .500 MHz 0 dBmV input level 7 .000 MHz 0 dBmV input level 7 .500 MHz 0 dBmV input level
spectrum-group 27 .000 MHz -10 dBmV input level 7 .000 MHz -5 dBmV input level 7 .000 MHz 0 dBmV input level 7 .000 MHz 5 dBmV input level 7 .000 MHz 10 dBmV input level
router# show cable spectrum-group 1 spectrum-group 16 .500 MHz 0 dBmV input level 7 .000 MHz 0 dBmV input level 7 .500 MHz 0 dBmV input level
Table 7 describes the fields shown in the show cable spectrum-group displays.
| Field | Description |
|---|---|
Spectrum-Group | Identifies the spectrum group. |
dBmV input level | Identifies the assigned decibels per millivolt (dBmV) input level. |
You can use the master indexes or search online to find documentation of related commands.
show cable burst-profile
show cable modem
show cable modulation-profile
show cable privacy
show cable qos
slot/port | Slot number/port number indicating the location of the Cisco MC11 cable modem card. |
downstream | (Optional) Displays downstream interface status. |
upstream | (Optional) Displays upstream interface status. |
channel | (Optional) Selects specific upstream channel. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show controllers cable command for the cable modem located in slot 3/port 0:
router# show controllers cable 3/0 Cable3/0: Downstream is up 2422977 packets output, 126650143 bytes, 0 discarded 0 output errors Hardware is CMTS Line Card idb 0x6099DFD8 MAC regs 0x3CC80000 PLX regs 0x3CC00000 rx ring entries 64 tx ring entries 128 MAP tx ring entries 128 Rx ring 0x4B0607C0 shadow 0x60A64BF8 head 5 Tx ring 0x4B060A00 shadow 0x60A64D68 head 47 tail 47 count 0 MAP Tx ring 0x4B060E40 shadow 0x60A655D8 head 80 tail 80 count 0 MAP timer sourced from slot 6 throttled 0 enabled 0 disabled 0 Rx: spurious 0 framing_err 0 hcs_err 0 no_buffer 0 no_enqueue 0 no_enp 0 miss_count 2 latency 2 Tx: full 0 drop 0 stuck 0 latency 0 MTx: full 0 drop 0 stuck 0 latency 0 Slots 2134 NoUW 1 Uncorr 0 Corr 0 Req 96524429 ReqColl 0 ReqNoise 0 Rng 494 RngColl 0 RngNoise 1 MAP FIFO overflow 0, Rx FIFO overflow 0 Bandwidth Requests= 0x47B Piggyback Requests= 0x2 Ranging Requests= 0x1EC Timing Offset = 0x1
Table 8 describes the fields shown in the show controllers cable display.
| Field | Description |
|---|---|
Cable | Slot number/port number indicating the location of the Cisco MC11 cable modem card |
Downstream is up | Indicates the RF downstream interface is enabled. |
packets output | Total number of packets carried on the RF downstream. |
bytes | Total number of bytes carried on the RF downstream. |
discarded | Total number of packets discarded. |
output error | Total number of output errors. |
hardware is | Indicates the hardware being used. |
idb | Interface description block. |
MAC regs |
|
PLX regs |
|
rx ring entries |
|
tx ring entries |
|
MAP tx ring entries |
|
Rx ring/shadow/head/tail/count |
|
Tx ring/ shadow/head/tail/count |
|
Map timer sourced |
|
throttled |
|
enabled |
|
disabled |
|
Rx: spurious |
|
framing err |
|
hcs err | Header checksum errors. |
no buffer |
|
no_enqueue |
|
no_encap |
|
miss_count |
|
latency |
|
Tx: full/drop/stuck/latency |
|
MTx: full/drop/stuck/latency |
|
Slots |
|
NoUW | Number of allocated slots with power but no detection of unique word. |
Uncorr |
|
Corr |
|
Req | Number of request bursts. |
ReqColl | Number of collisions in a request burst region. |
ReqNoise | Number of noise events in a request burst region. |
Rng | Number of ranging bursts. |
RngColl | Number of collisions detected on ranging bursts. |
RngNoise | Number of noise events detected on ranging bursts. |
MAP FIFO overflow | Hardware MAC MAP first-in first-out (FIFO) overflowed. |
Rx FIFO overflow | Received MAC hardware FIFO overflowed. |
Bandwidth Requests= | Number of requests for bandwidth MAC messages. |
Piggyback Requests= | Number of piggyback request MAC messages. |
Ranging Requests= | Number of ranging messages received. |
Timing Offset= | Relative number of time units to which the cable modem needs to be adjusted. |
The following is sample output for the downstream connection for slot 3 on port 0 from the show controllers cable downstream command:
router# show controllers cable 3/0 downstream Cable 3/0 Downstream is up Frequency not set, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps FEC ITU-T J.83 Annex A, R/S Interleave I=12, J=17
Table 9 describes the fields shown in the show controllers cable downstream display.
| Field | Description |
|---|---|
Cable | Slot number/port number indicating the location of the Cisco MC11 cable modem card. |
Downstream is up | Indicates the RF downstream interface is enabled. |
Frequency | Transmission frequency of the RF downstream. (This information may not match the current transmission frequency, which is external to uBR.) |
Channel Width | Indicates the width of the RF downstream channel. |
QAM | Indicates the modulation scheme. |
Symbol Rate | Indicates the transmission rate (in number of symbols per second). |
FEC ITU-T | Indicates the MPEG framing standard. |
R/S Interleave I/J | Indicates Reed Solomon framing based on ITU S.83-B. |
The following is sample output for the upstream connection for slot 3 on port 0 from the show controllers cable upstream command:
router# show controllers cable 3/0 upstream 0 Cable3/0 Upstream 0 is up Frequency 7.008 MHz, Channel Width 1.6 MHz, QPSK Symbol Rate 1.280 Msps Nominal Input Power Level 0 dBmV, Tx Timing Offset 0 Ranging Backoff Start 0, Ranging Backoff End 3, Tx Backoff Start 2 Tx Backoff End 8, Modulation Profile Group 1 part_id=0x3136, rev_id=0x02, rev2_id=0x61 nb_agc_thr=0x0100, nb_agc_nom=0x3000 Range Load Reg Size=0x44 Request Load Reg Size=0x0C DES Reg #580 = E204301, #584 = 3E030303, #588 = 0 #590 = C0C0C0C
Table 10 describes the fields shown in the show controllers cable upstream display.
| Field | Description |
|---|---|
Cable | Slot number/port number indicating the location of the Cisco MC11 cable modem card |
Upstream is up | Indicates the RF upstream interface is enabled. |
Frequency | Transmission frequency of the RF upstream. |
Channel Width | Indicates the width of the RF upstream channel. |
QPSK Symbol Rate | Indicates the QPSK symbol rate in symbols per second. |
Nominal Input Power level | Indicates the desired power level coming into the receiver. |
Tx Timing Offset | Indicates the current ranging offset on the channel. |
Tx Backoff End | Indicates the end exponential backoff value for data collisions. |
Modulation Profile Group | A set of burst profiles defining an upstream range. |
part_id= | Identification number for burst demodulation hardware. |
rev_id= | Identification number for burst demodulation hardware. |
rev2_id= | Identification number for burst demodulation hardware. |
nb_agc_thr= | Threshold used to control gain into hardware. |
nb_agc_nom= | Used to accelerate convergence of input power level. |
Range Load Reg Size= | Size, indicated by number of symbols, for range request bursts. |
Request Load Reg Size= | Size, indicated by number of symbols, for request bursts. |
DES Reg # = |
|
To display cable interface information, use the show interface cable Privileged EXEC command:
show interface cable port/slot [downstream | upstream]
port/slot | The port number/slot number indicating the location of the installed Cisco MC11 cable modem. |
downstream | (Optional) Displays cable downstream port information for a cable modem. |
upstream | (Optional) Displays cable upstream port information for a cable modem. |
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output for the cable modem located in slot 6/port 0 from the show interface cable command:
router# show interface cable 6/0
Cable6/0 is up, line protocol is up
Hardware is BCM3210 FPGA, address is 00e0.1e5f.7a60 (bia 00e0.1e5f.7a60)
Internet address is 1.1.1.3/24
MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, rely 255/255, load 1/255
Encapsulation, loopback not set, keepalive not set
ARP type: ARPA, ARP Timeout 04:00:00
Last input 4d07h, output 00:00:00, output hang never
Last clearing of "show interface" counters never
Queueing strategy: fifo
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
10908 packets input, 855000 bytes, 0 no buffer
Received 3699 broadcasts, 0 runts, 0 giants, 0 throttles
3 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
5412 packets output, 646488 bytes, 0 underruns
0 output errors, 0 collisions, 13082 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 11 describes the fields shown in the show interface cable display.
| Field | Description |
|---|---|
Cable slot/port is up/ ...administratively down | Indicates whether the interface hardware is currently active or taken down by the administrator. |
line protocol is up/ ...administratively down | Indicates whether the software processes that handle the line protocol believe the interface is usable or if it has been taken down by the administrator. |
hardware | Hardware type and address. |
Internet address | Internet address followed by subnet mask. |
MTU | Maximum Transmission Unit (MTU) of the interface. |
BW | Bandwidth of the interface in kilobits per second. |
DLY | Delay of the interface in microseconds. |
rely | Reliability of the interface as a fraction of 255, calculated as an exponential average over 5 minutes. (For example, 255/255 is 100% reliability.) |
load | Load on the interface as a fraction of 255, calculated as an exponential average over 5 minutes. (For example, 255/255 is complete saturation.) |
Encapsulation | Encapsulation method assigned to this interface. |
ARP type | Type of Address Resolution Protocol (ARP) and timeout value assigned. |
Last input | Number of hours, minutes, and seconds since the last packet was successfully received by an interface. |
output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. |
Last clearing of "show interface" counters | Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) were last reset to zero. |
Queueing strategy | Displays the type of queueing configured for this interface. In The following example output, the type of queueing configured is First In First Out (FIFO). |
Output queue | Number of packets in the output queue. The format of this number is A/B, where A indicates the number of packets in the queue and B indicates the maximum number of packets allowed in the queue. |
drops | Indicates the number of packets dropped due to a full queue. |
input queue/drops | Number of packets in the input queue. The format of this number is A/B, where A indicates the number of packets in the queue and B indicates the maximum number of packets allowed in the queue. |
drops | Indicates the number of packets dropped due to a full queue. |
Five minute input rate | Average number of bits and packets transmitted per second in the last five minutes. |
packets input | Total number of error-free packets received by the system. |
bytes input | Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system. |
no buffer | Number of received packets discarded because there was no buffer space in the main system. |
Received broadcast | Total number of broadcast or multicast packets received by the interface. |
runts | Number of packets that are discarded because they are smaller than the medium's minimum packet size. |
giants | Number of packets that are discarded because they exceed the medium's maximum packet size. |
input errors | Includes runts, giants, no buffers, CRC, frame, overrun, and ignored counts. |
CRC | Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. |
frame | Number of packets received incorrectly having a CRC error and a non-integer number of octets. |
overrun | Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. |
ignored | Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. |
packets output | Total number of messages transmitted by the system. |
bytes | Total number of bytes, including data and MAC encapsulation, transmitted by the system. |
underruns | Number of times the transmitter has been running faster than the receiving device can handle. |
output errors | Sum of all errors that prevented the final transmission of packets out of the interface being examined. |
collisions | Not applicable for the Cisco uBR7246. |
interface resets | Number of times an interface has been completely reset. |
output buffer failures | Number of times the output buffer has failed. |
output buffer swapped out | Number of times the output buffer has been swapped out. |
The following is sample output for the downstream cable interface of slot 6 on port 0 from the show interface cable downstream command:
router# show interface cable 6/0 downstream
Cable6/0: Downstream is up
111947771 packets output, 1579682655 bytes, 0 discarded
0 output errors
Table 12 describes the fields shown in the show controllers cable downstream display.
| Field | Description |
|---|---|
Cable | Indicates the location of the downstream interface. |
Downstream is up/...administratively down | Indicates the administrative state of the interface.
|
packets output | Total number of packets transmitted out of this interface. |
bytes | Total number of bytes transmitted out of this interface. |
discarded | Total number of packets discarded. |
output errors | Sum of all errors that prevented downstream transmission of packets out of this interface. |
The following is sample output for the upstream cable interface located in slot 6/port 0 from the show interface cable upstream command:
router# show interface cable 6/0 upstream Cable6/0: Upstream 0 is upReceived 3699 broadcasts, 0 multicasts, 28586 unicasts 0 discards, 0 errors, 0 unknown protocol 21817 packets error-free, 2371 corrected, 8097 uncorrectable 0 noise, 0 microreflections CBR_queue_depth: [not implemented], ABR_queue_depth: [not implemented], UBR[1]_queue_depth: 0, UBR[2]_queue_depth: 0, UBR[3]_queue_depth: 0, POLLS_queue_depth: [not implemented] ADMIN_queue_depth: [not implemented] Last Minislot Stamp (current_time_base):190026 FLAG:1 Last Minislot Stamp (scheduler_time_base):200706 FLAG:1
Table 13 describes the fields shown in the show interface cable upstream display.
| Field | Description |
|---|---|
Cable | Identifying the cable interface. |
Upstream is up/...administratively down | Indicates the administrative state of the upstream interface. |
Received broadcasts | Number of broadcast packets received through this upstream interface. |
multicasts | Number of multicast packets received through this upstream interface. |
unicasts | Number of unicast packets received through this interface. |
discards | Number of packets discarded by this interface. |
errors |
|
unknown protocols |
|
packets error-free |
|
corrected |
|
uncorrectable |
|
noise |
|
microreflections |
|
CBR_queue_depth |
|
ABR_queue_depth |
|
UBR[1]_queue_depth |
|
UBR[2]_queue_depth |
|
UBR[3}_queue_depth |
|
POLLS_queu_depth |
|
ADMIN_queue_depth |
|
Last Minislot Stamp (current_time_base) |
|
FLAG |
|
Last Minislot Stamp (scheduler_time_base) |
|
FLAG |
|
You can use the master indexes or search online to find documentation of related commands.
show interface cable signal-quality
show interface cable sid
slot/port | Slot number/port number indicating the location of the Cisco MC11 cable modem card |
EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show interface signal quality command:
router# show interface cable 6/0 signal-quality Cable6/0: Upstream 0 is up includes contention intervals: TRUE
Table 14 describes the fields shown in the show controllers cable upstream display.
| Field | Description |
|---|---|
Cable | Interface name. |
Upstream is up includes contention intervals | States whether this statement is true. |
You can use the master indexes or search online to find documentation of related commands.
show interface
show interface cable downstream
show interface cable sid
show interface cable upstream
slot/port | Identifies the slot number and downstream port number. |
sid-number | (Optional) Identifies the service identification number. |
EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following are sample outputs from two uses of the show interface cable sid command:
router# show interface cable 6/0 sid SID Status QoS Creattime Inoctets Inpackets IP address MAC address 1 enable 2 57 80139964 101336 1.1.1.5 00e0.1eab.2c0b 2 enable 2 57 49132 649 1.1.1.7 00e0.1eb2.bb07 3 enable 2 58 80042891 100555 1.1.1.2 00e0.1eab.2c29 router#show interface cable 6/0 sid 1 SID Status QoS Creattime Inoctets Inpackets IP address MAC address 1 enable 2 57 80140204 101340 1.1.1.5 00e0.1eab.2c0b
If the value for the QoS group in the display appears as 0, it indicates that a temporary SID has been assigned to a cable modem that is in the process of connecting to the network:
router# show interface cable 6/0 sid SID Status QoS Creattime Inoctets Inpackets IP address MAC address 1 enable 0 57 80140204 101340 1.1.1.5 00e0.1eab.2c0b
If there are no cable modems connected to the cable interface you have selected, the display will appear as follows:
router# show interface cable 6/0 sid SID Status QoS Creattime Inoctets Inpackets IP address MAC address 1 Not in use
Table 15 describes the fields shown in the output for the show interface cable sid displays.
| Field | Description |
|---|---|
SID | Service identification number. |
Status | "Disable" means that the SID has been administratively disabled. "Enable" is the normal state. |
QoS | Quality of service. |
Creattime | When the SID was created, number of seconds since system booted. |
Inoctets | Number of octets received using this SID. |
Inpackets | Number of packets received using this SID. |
IP address | IP address of the modem owning this SID. |
MAC address | MAC address of the modem owning this SID. |
You can use the master indexes or search online to find documentation of related commands.
show interface cable signal-quality
There are no arguments or keywords for this command.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show diag command displaying revision level information for the cable line card (Slot 6):
router#show diag
Slot 6:
MC11 port adapter, 1 port
Port adapter is analyzed
Port adapter insertion time 02:37:10 ago
Hardware Revision : 1.2
Part Number : 800-02455-02
Board Revision : 03
Deviation Number : 0-3
Fab Version : 03
PCB Serial Number : 00004500239
RMA Test History : 00
RMA Number : 0-0-0-0
RMA History : 00
Calibration Data : Minimum: -8 dBmV, Maximum: 8 dBmV
Calibration values : 0x5D43 0x3F05 0x1794
Unknown Field (type 0083): 83 FF FF FF
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 F1 41 01 02 C0 46 03 20 00 09 97 02
0x10: 42 30 33 80 00 00 00 03 02 03 C1 8B 30 30 30 30
0x20: 34 35 30 30 32 33 39 03 00 81 00 00 00 00 04 00
0x30: C8 09 F8 08 03 5D 43 3F 05 17 94 83 83 FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Table 16 describes the fields shown in the show diag display.
| Field | Description |
|---|---|
MC11 port adapter | Line card type. |
Port adapter is analyzed | The system has identified the Cisco uBR7246 port adapter. |
Port adapter insertion time | Elapsed time since insertion. |
Hardware Revision | Version number of the Cisco uBR7246 port adapter. |
Part Number | In the Cisco uBR 7246, the part number of the port adapter. |
Board Revision | Revision number (signifying a minor revision) of the Cisco uBR 7246 port adapter. |
Deviation Number | Revision number (signifying a minor deviation) of the Cisco uBR7246 port adapter. |
Fab Version | Manufacturing fabrication version number. |
PCB Serial Number | Serial number of the printed circuit board. |
RMA Test History | Counter indicating how many times diagnostics have been performed on this port adapter. |
RMA Number | Return material authorization number, which is an administrative number assigned if port adapter needs to be returned for repair. |
RMA History | Counter indicating how many times the port adapter has been returned and repaired. |
Calibration Data | Input power calibration range. |
Calibration values | Upstream port gain calibration constant. |
Unknown Field (type) | Unrecognized EEPROM fields. |
EEPROM format version | Version number of the EEPROM format. |
EEPROM contents (hex) | Dumps of EEPROM programmed data. |
There are no arguments or keywords for this command.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.3 XA.
The following is sample output from the show c7200 command. The midplane EEPROM data describes the characteristics of the device's midplane chassis; the CPU EEPROM data describes the characteristics of the device's CPU. The fault history buffer data provides diagnostic information used only by Cisco Customer Support Engineers.
router#show c7200
Network IO Interrupt Throttling:
throttle count=0, timer count=0
active=0, configured=0
netint usec=3999, netint mask usec=200
UBR7200 Midplane EEPROM:
Number of Slots : 6
Hardware Revision : 1.1
Chassis MAC Address : 0008.cefb.fc00
MAC Address block size : 256
Unknown Field (type 01B9): 2C 1F E0 00
Unknown Field (type 01B8): 85 FF FF FF
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 F0 01 06 41 01 01 C3 06 00 08 CE FB
0x10: FC 00 43 01 00 C7 20 45 53 00 29 00 2E 00 3D 00
0x20: 4C 00 34 00 36 00 87 00 81 00 83 00 86 00 84 00
0x30: B6 00 E0 00 00 B8 DB 00 B9 2C 1F E0 00 00 B8 85
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
C7200 CPU EEPROM:
Hardware revision 2.1 Board revision A0
Serial number 4371856 Part number 73-1536-03
Test history 0x0 RMA number 00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x20: 01 15 02 01 00 42 B5 90 49 06 00 03 00 00 00 00
0x30: 50 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
Fault History Buffer:
7200 Software (UBR7200-P-M), Experimental Version 11.3(19980514:205205)
[johnchen-spydrman_2 232]
Compiled Fri 12-Jun-98 19:20 by johnchen
Signal = 23, Code = 0x24, Uptime 00:02:09
$0 : 00000000, AT : 00000000, v0 : 00000000, v1 : 00000004
a0 : 00000000, a1 : 0000FF00, a2 : 00000006, a3 : 00000002
t0 : 00000020, t1 : 3401FF01, t2 : 3401C100, t3 : FFFF00FF
t4 : 6027E180, t5 : 30443044, t6 : 30384330, t7 : 30783630
s0 : 00000000, s1 : 608BFD88, s2 : 606D9E4C, s3 : 60B43E0C
s4 : 608BFD88, s5 : 0000004A, s6 : 00000000, s7 : 608BFF9C
t8 : 00009BCB, t9 : 00000000, k0 : 3041D001, k1 : BF800000
gp : 6083B400, sp : 60BC4CA0, s8 : 608BFDF8, ra : 602797EC
EP6027AE58, SREG : 3401FF03, Cause : 00000424
The following debug cable commands are available to troubleshoot the cable interfaces on the Cisco uBR7246:
Use the debug cable env EXEC command to display information about the Cisco uBR7246 physical environment, including internal temperature, midplane voltages, fan performance, and power supply voltages. The no form of this command disables debugging output.
[no] debug cable env
This command is used to debug the sensor circuitry used to measure internal temperature, midplane voltages, fan performance, and power supply voltages on the Cisco uBR7246 console.
Figure shows the sample debug cable env output.
ENVM: ps id=0xFF0, v=0x2050, r=0xC0AB, pstype=1 > ENVM: ps id=0x2FD0, v=0x2050, r=0x24201, pstype=27 > ENVM: Sensor 0: a2dref=131, a2dact=31, vref=12219, vact=1552 > Alpha=8990, temp=27 >
| Field | Description |
|---|---|
ps id | Power supply raw voltage reading |
v |
|
r |
|
pstype | Power supply type determined from ps id, v, and r. The Cisco uBR7246 contains dual power supplies so i d information for two types is usually printed. |
Sensor | Sensor number. |
a2dref | Analog to digital converter reference reading. |
a2dact | Analog to digital converter actual (measured reading. |
vref | Reference voltage. |
vact | Actual voltage. |
Alpha | Raw temperature reading. |
temp | Temperature corresponding to Alpha. |
You can use the master indexes or search online to find documentation of related commands.
show environment all
show environment last
show environment table
Use the debug cable err EXEC command to display errors that occur in the cable MAC protocols. The no form of this command disables debugging output.
[no] debug cable err
This command is used to display unexpected DOCSIS MAC protocol messages. When the
Cisco uBR7246 does not to expect to receive a specific MAC message, an error message and hex dump are printed. Other miscellaneous error conditions may result in output.
Following is sample debug cable err output.
This is a UCD Message > This is a MAP Message > This is a RNG_RSP Message > This is a REG_RSP Message > This is a UCC_REQ Message > This is a BPKM_RSP Message > This is a TRI_TCD Message > This is a TRI_TSI Message > This is a unrecognized MCNS message > > ERROR:######TICKS PER MSLOT NOT POWER OF 2####
Use the debug cable keyman EXEC command to activate debugging of tek and kek baseline privacy key activity. The no form of this command disables debugging output.
[no] debug cable keyman
This command activates debugging of the tek and kek baseline privacy key activity. When this command is activated, all activity related to kek and tek keys will be displayed on the Cisco uBR7246 console. This command is used to display encryption key management debugging output.
Following is sample debug cable keyman output.
Read Verify DES failed with SID %2x
> Verify key failed with SID %2x : setvalue = %llx, readback = %llx
> Verify iv failed with SID %2x : setvalue = %llx, readback = %llx
> Next TEK lifetime check is set to %u seconds.
> Next Multicast TEK lifetime check is set to 1 seconds
>
> [UCAST_TEK] :", idbp->hw_namestring);
> show_sid_key_chain(ds, &ds->mcast_sid_key_list_hdr);
>
> [MCAST_TEK] :", idbp->hw_namestring);
> buginf("\nSID : %4x\t", sidkey->sid);
> buginf("seq : %2x\t current : %2x\n", sidkey->key_seq_num,
> sidkey->current_key_num);
> buginf(" Status[0] : %x\tDES IV[0] : %llx\tKey Life[0]: %u sec\n",
> sidkey->key_status[0], sidkey->des_key[0].iv,
> compute_remain_lifetime(&sidkey->des_key[0]));
>
> buginf(" Status[1] : %x\tDES IV[1] : %llx\tKey Life[1]: %u sec\n",
> sidkey->key_status[1], sidkey->des_key[1].iv,
> compute_remain_lifetime(&sidkey->des_key[1]));
>
Use the debug cable phy EXEC command to activate debugging of messages generated in the cable physical layer. The no form of this command disables debugging output.
[no] debug cable phy
This command activates debugging of messages generated in the cable phy, which is the physical layer where upstream and downstream activity between the Cisco uBR7246 and the HFC network is controlled. When this command is activated, any messages generated in the cable phy will be displayed on the Cisco uBR7246 console.
Following is sample debug cable phy output.
cmts_phy_init: mac_version == BCM3210_FPGA >bcm3033_set_tx_sym_rate(5056941) >stintctl = 0x54484800 >bcm3033_set_tx_if_freq(44000000) >stfreqctl = 0x5BAAAAAA >cmts_phy_init_us: U0 part_id = 0x3136, revid = 0x05, rev_id2 = 0x64 >cmts_phy_init: mac_version == BCM3210_FPGA Media access controller chip version. >bcm3033_set_tx_sym_rate(5056941) > stintctl = 0x54484800 Physical layer symbol rate register value. >00:51:49: bcm3033_set_tx_if_freq(44000000) >00:51:49: stfreqctl = 0x5BAAAAAA Physical layer intermediate frequency (IF) register value. >00:51:49: cmts_phy_init_us: U0 part_id = 0x3136, revid = 0x05, rev_id2 = 0x64 Physical layer receiver chip part version.
Use the debug cable privacy EXEC command to activate debugging of baseline privacy. The no form of this command disables debugging output.
[no] debug cable privacy
This command activates debugging of baseline privacy. When this command is activated, any messages generated by the spectrum manager will be displayed on the Cisco uBR7246 console.
Following is sample debug cable privacy output.
Removing both odd and even keys for sid %x. > > Invalid Len for TLV_SERIAL_NUM_TYPE : %d. > > Invalid Len for TLV_MANUF_ID_TYPE : %d. > > Invalid Len for TLV_MANUF_ID_TYPE : %d. >
Use the debug cable qos EXEC command to activate quality of service debugging. The no form of this command disables debugging output.
[no] debug cable qos
This command activates debugging of QoS. When this command is activated, any messages related to QoS parameters will be displayed on the Cisco uBR7246 console.
Following is sample debug cable qos output.
>CMTS_QOS_LOG_NO_MORE_QOS_INDEX Modems cannot add more entries to the class of service table. >CMTS_QOS_LOG_NOMORE_QOSPRF_MEM Memory allocation error when creating class of service table entry. >CMTS_QOS_LOG_NO_CREATION_ALLOWED Class of service entry cannot be created by modem. Use CLI or SNMP interface instead of the modem's TFTP configuration file. >CMTS_QOS_LOG_CANNOT_REGISTER_COS_SID A service identifier (SID) could not be assigned to the registering modem. >CMTS_QOS_LOG_CANNOT_DEREGISTER_COS_SID The modem's service identifier (SID) was already removed. >CMTS_QOS_LOG_MSLOT_TIMEBASE_WRAPPED The 160 KHz timebase clock drives a 26-bit counter which wraps around approximately every 7 minutes. This message is generated every time it wraps around.
Use the debug cable range EXEC command to display ranging messages from cable modems on the HFC network. The no form of this command disables debugging output.
[no] debug cable range
This command activates debugging of ranging messages from cable modems on the HFC network. When this command is activated, any ranging messages generated when cable modems request or change their upstream frequencies will be displayed on the Cisco uBR7246 console. Use this command to display the details of the initial and station maintenance procedures. The initial maintenance procedure is used for link establishment. The station maintenance procedure is used for link keep-alive monitoring.
Following are samples of debug cable range output.
>Got a ranging request >SID value is 0 on Interface Cable3/0/U0 >CM mac address 00:10:7B:43:AA:21 Timing offset is 3312 >3E 1E 3F FF 00 00 59 BF 01 15 F8 01 A7 00 0C F0
Output when a modem first seeks to establish a link to the Cisco uBR7246. The SID value of 0 indicates that the modem has no assigned service identifier. The "CM mac address" is"the MAC address of the modem's radio frequency (RF) interface, not its Ethernet interface. The "Timing offset" is a measure of the distance between the modem and the Cisco uBR7246 expressed in 10.24 MHz clocks. This value is adjusted down to zero by the maintenance procedures. The first 16 bytes of the prepended header of the message are dumped in hexadecimal.
CM mac address 0010.7b43.aa21 >found..Assigned SID #2 on Interface Cable3/0/U0 >Timing offset is CF0 >Power value is 15F8, or -1 dB >Freq Error = 423, Freq offset is 1692 >Ranging Modem with Sid 2 on i/f : Cable3/0/U0
Output when the modem is first assigned a SID during initial maintenance.
>Initial Range Message Received on Interface Cable3/0/U0 >CMTS reusing old sid : 2 for modem : 0010.7b43.aa21 >Timing offset is CF0 >Power value is 15F8, or -1 dB >Freq Error = 423, Freq offset is 1692 >Ranging Modem with Sid 2 on i/f : Cable3/0/U0
Output when the modem is reassigned the same SID during initial maintenance.
>Ranging Modem with Sid 2 on i/f : Cable3/0/U0 > >Got a ranging request >SID value is 2 on Interface Cable3/0/U0 >CM mac address 00:10:7B:43:AA:21 >Timing offset is 0 >Power value is 1823, or -1 dB >Freq Error = 13, Freq offset is 0 >Ranging has been successful for SID 2 on Interface Cable3/0/U0
Output when the modem is polled by the uBR7246 during station maintenance. Polling happens at a minimum rate of once every 10 seconds.
Use the debug cable reset EXEC command to display reset messages from cable interfaces. The no form of this command disables debugging output.
[no] debug cable reset
This command activates display of reset messages from cable interfaces.
Following is sample debug cable reset output.
>Resetting CMTS interface.
Output when the interface is reset due to complete loss of receive packets.
Use the debug cable specmgmt EXEC command to debug spectrum management (frequency agility) on the HFC network. The no form of this command disables debugging output.
[no] debug cable specmgmt
This command activates debugging of spectrum management (frequency agility) on the HFC network. When this command is activated, any messages generated due to spectrum group activity will be displayed on the Cisco uBR7246 console. Spectrum group activity can be additions or changes to spectrum groups, or frequency and power lever changes controlled by spectrum groups.
Following is sample debug cable specmgmt output.
>cmts_next_frequency(0x60A979AC, 1, 1)
Frequency hop was commanded.
>add_interface_to_freq(0x60BD3734, 0x60C44F68)
Interface was added to a frequency's interface list.
>set_upstream(0x60A979AC,1,21000000,-5)
Spectrum management has set an upstream port's frequency and power level.
>cmts_frequency_hop_decision(0x60B57FEC)
An interface was checked for a frequency hop decision.
Use the debug cable startalloc EXEC command to debug channel allocations on the HFC network. The no form of this command disables debugging output.
[no] debug cable startalloc
This command activates debugging of any channel allocations on the HFC network. When this command is activated, any messages generated when channels are allocated to cable modems on the HFC network will be displayed on the Cisco uBR7246 console.
Following is sample debug cable startalloc output.
>MAP startalloc adjusted by <n> mslots
Indicates time-slot MAP processing is active.
Use the debug cable ucc EXEC command to debug upstream channel change (UCC) messages generated when cable modems request or are assigned a new channel. The no form of this command disables debugging output.
[no] debug cable ucc
This command activates debugging of any upstream channel change (UCC) messages generated when cable modems request or are assigned a new channel. When this command is activated, any messages related to upstream channel changes will be displayed on the Cisco uBR7246 console.
Following is sample debug cable ucc output.
>SID 2 has been registered > >Mac Address of CM for UCC > 00:0E:1D:D8:52:16 > >UCC Message Sent to CM > >Changing SID 2 from upstream channel 1 to upstream channel 2
Output when moving modem from one upstream channel to another.
Use the debug cable ucd EXEC command to debug upstream channel descriptor (UCD) messages. The no form of this command disables debugging output.
[no] debug cable ucd
This command activates debugging of any upstream channel descriptor (UCD) messages. UCD messages contain information about upstream channel characteristics and are sent to the cable modems on the HFC network. Cable modems that are configured to use enhanced upstream channels use these UCD messages to identify and select an enhanced upstream channel to use. When this command is activated, any messages related to upstream channel descriptors will be displayed on the Cisco uBR7246 console.
Following is sample debug cable ucd output.
UCD MESSAGE
-----------
FRAME HEADER
FC - 0xC2 ==
MAC_PARM - 0x00
LEN - 0xD3
MAC MANAGEMENT MESSAGE HEADER
DA - 01E0.2F00.0001
SA - 0009.0CEF.3730
msg LEN - C1
DSAP - 0
SSAP t - 0
control - 03
version - 01
type - 02 ==
US Channel ID - 1
Configuration Change Count - 5
Mini-Slot Size - 4
DS Channel ID - 1
Symbol Rate - 8
Frequency - 10000000
Preamble Pattern - CC CC CC CC CC CC CC CC CC CC CC CC CC
CC 0D 0D
Burst Descriptor 0
Interval Usage Code - 1
Modulation Type - 1 == QPSK
Differential Encoding - 2 == OFF
Preamble Length - 64
Preamble Value Offset - 56
FEC Error Correction - 0
FEC Codeword Length - 16
Scrambler Seed - 0x0152
Maximum Burst Size - 2
Guard Time Size - 8
Last Codeword Length - 1 == FIXED
Scrambler on/off - 1 == ON
Burst Descriptor 1
Interval Usage Code - 3
Modulation Type - 1 == QPSK
Differential Encoding - 2 == OFF
Preamble Length - 128
Preamble Value Offset - 0
FEC Error Correction - 5
FEC Codeword Length - 34
Scrambler Seed - 0x0152
Maximum Burst Size - 0
Guard Time Size - 48
Last Codeword Length - 1 == FIXED
Scrambler on/off - 1 == ON
Burst Descriptor 2
Interval Usage Code - 4
Modulation Type - 1 == QPSK
Differential Encoding - 2 == OFF
Preamble Length - 128
Preamble Value Offset - 0
FEC Error Correction - 5
FEC Codeword Length - 34
Scrambler Seed - 0x0152
Maximum Burst Size - 0
Guard Time Size - 48
Last Codeword Length - 1 == FIXED
Scrambler on/off - 1 == ON
Burst Descriptor 3
Interval Usage Code - 5
Modulation Type - 1 == QPSK
Differential Encoding - 2 == OFF
Preamble Length - 72
Preamble Value Offset - 48
FEC Error Correction - 5
FEC Codeword Length - 75
Scrambler Seed - 0x0152
Maximum Burst Size - 0
Guard Time Size - 8
Last Codeword Length - 1 == FIXED
Scrambler on/off - 1 == ON
The UCD MESSAGE is :
0xC2 0x00 0x00 0xD3 0x00 0x00 0x01 0xE0
0x2F 0x00 0x00 0x01 0x00 0x09 0x0C 0xEF
0x37 0x30 0x00 0xC1 0x00 0x00 0x03 0x01
0x02 0x00 0x01 0x05 0x04 0x01 0x01 0x01
0x08 0x02 0x04 0x00 0x98 0x96 0x80 0x03
0x10 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC
0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0xCC 0x0D
0x0D 0x04 0x25 0x01 0x01 0x01 0x01 0x02
0x01 0x02 0x03 0x02 0x00 0x40 0x04 0x02
0x00 0x38 0x05 0x01 0x00 0x06 0x01 0x10
0x07 0x02 0x01 0x52 0x08 0x01 0x02 0x09
0x01 0x08 0x0A 0x01 0x01 0x0B 0x01 0x01
0x04 0x25 0x03 0x01 0x01 0x01 0x02 0x01
0x02 0x03 0x02 0x00 0x80 0x04 0x02 0x00
0x00 0x05 0x01 0x05 0x06 0x01 0x22 0x07
0x02 0x01 0x52 0x08 0x01 0x00 0x09 0x01
0x30 0x0A 0x01 0x01 0x0B 0x01 0x01 0x04
0x25 0x04 0x01 0x01 0x01 0x02 0x01 0x02
0x03 0x02 0x00 0x80 0x04 0x02 0x00 0x00
0x05 0x01 0x05 0x06 0x01 0x22 0x07 0x02
0x01 0x52 0x08 0x01 0x00 0x09 0x01 0x30
0x0A 0x01 0x01 0x0B 0x01 0x01 0x04 0x25
0x05 0x01 0x01 0x01 0x02 0x01 0x02 0x03
0x02 0x00 0x48 0x04 0x02 0x00 0x30 0x05
0x01 0x05 0x06 0x01 0x4B 0x07 0x02 0x01
0x52 0x08 0x01 0x00 0x09 0x01 0x08 0x0A
0x01 0x01 0x0B 0x01 0x01
|
|