Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration Guide - For Cisco IOS Releases 12.3(21)BC, 12.3(21a)BC3 and later 12.3(21a)BCx releases - Configuring the Wideband SPA [Cisco uBR10000 Series Universal Broadband Routers]

Table Of Contents

Configuring the Wideband SPA

Configuration Tasks

Wideband SPA Overview and Terminology

Fiber Node Configuration

Wideband Cable Modems

Specifying the Location for a Wideband SPA

Specifying Wideband Channels

Hardware Status and Line Protocol Status for a Wideband-Channel Cable Interface

Preprovisioning of the Wideband SIP and Wideband SPA

Entering Controller Configuration Mode for the Wideband SPA

Completing Required and Optional Wideband-Related Configuration Tasks

Setting General Configuration Values for the Wideband SPA

Configuring RF Channels

Configuring Fiber Nodes

Configuring Wideband Channels and Primary Downstream Channels as Virtual Bundle Members

Setting Optional Configuration Values

Verifying the Configuration

Verifying the Wideband SPA Configuration

Verifying RF Channel Configuration

Configuration Examples

Wideband SPA Controller Configuration Example

Wideband Channel Configuration Example

Virtual Bundle Configuration Example

Cable Fiber Node Configuration Example

Primary Downstream Channel Configuration Example

Configuring the Wideband SPA

This chapter provides information about configuring the Wideband SPA on the Cisco uBR10012 router. It includes the following sections:

•Configuration Tasks

•Verifying the Wideband SPA Configuration

•Configuration Examples

For more information about the commands used in this chapter, refer to this documentation in the order shown:

1. Chapter 11, "SIP and SPA Commands" in this guide

2. Cisco Broadband Cable Command Reference Guide

If the command is not located in those publications, refer to the Cisco IOS Release 12.3 command reference and master index publications. For more information about accessing these publications, see the "Related Documentation" section on page 9.

Configuration Tasks

This section describes how to configure the Wideband SPA and includes the following topics:

•Wideband SPA Overview and Terminology

•Specifying the Location for a Wideband SPA

•Specifying Wideband Channels

•Preprovisioning of the Wideband SIP and Wideband SPA

•Entering Controller Configuration Mode for the Wideband SPA

•Completing Required and Optional Wideband-Related Configuration Tasks

Wideband SPA Overview and Terminology

The Wideband SPA is a single-wide, half-height shared port adapter that provides DOCSIS 3.0 formatting to downstream data packets. The Wideband SPA is used for downstream data traffic only. The Cisco Wideband SPA is a key component for the Cisco IOS feature DOCSIS 3.0 Downstream Channel Bonding.

Each Wideband SPA is installed into a bay (subslot) of a Wideband SIP (SPA interface processor) on a Cisco uBR10012 universal broadband router. See the "Identifying the Location of Wideband SIPs and SPAs" section on page 4-2 for information on slot restrictions. Each Wideband SPA has one active and one redundant Gigabit Ethernet port that is used to send traffic to one or more external edge QAM devices.

The Cisco uBR10012 router can support up to two Wideband SPAs. Depending on how it is configured, each Wideband SPA allows up to 24 RF channels. A Cisco uBR10012 router with two Wideband SPAs supports a total of up to 48 RF channels.

A wideband channel is a logical grouping of one or more physical radio frequency (RF) channels over which wideband MPEG-TS packets are carried. By aggregating or "channel bonding" multiple RF channels, the wideband channel is capable of greater bandwidth capacity for downstream data traffic than a single RF channel. During Wideband SPA configuration, each wideband channel is associated with one or more RF channels. Each Wideband SPA supports 12 wideband channels.

A traditional DOCSIS channel (also called a narrowband channel) is a standard DOCSIS-protocol downstream channel that contains one RF channel. The traditional DOCSIS channels are located on a cable interface line card (for example, Cisco uBR10-MC5X20S-D). The DOCSIS 3.0 Downstream Channel Bonding feature uses an existing traditional DOCSIS downstream channel for carrying the MAC management and signaling messages, and uses the associated traditional DOCSIS upstream channel for return data traffic and signaling. During Wideband SPA configuration, each wideband channel is associated with one or more traditional DOCSIS channels, one of which is used as described above. The traditional DOCSIS downstream channel used in this way is called the primary downstream channel.

The DOCSIS 3.0 Downstream Channel Bonding feature can be deployed in parallel with DOCSIS 1.X/2.0 technology. The CMTS supports DOCSIS 1.X/ 2.0 modems on non-wideband ports while wideband cable modems deliver higher-speed throughput on the wideband ports.

Fiber Node Configuration

In a cable network, a fiber node is a point of interface between a fiber trunk and the coaxial distribution. A cable modem is physically connected to only one fiber node. Fiber node software configuration mirrors the physical topology of the cable network. When configuring fiber nodes with Cisco IOS CLI commands, a fiber node is a software mechanism to define the following:

•The set of downstream RF channels that will flow into the fiber node

•At least one primary downstream channel (traditional DOCSIS downstream channel) for the fiber node

•The set of upstream channel ports on the cable interface line card that are connected to the fiber node and available as upstream channels

The DOCSIS 3.0 Downstream Channel Bonding feature requires that a fiber node be associated with at least one primary downstream channel. A fiber node can be associated with more than one primary downstream channel though only one primary downstream channel is used at any given point in time. On the uBR10-MC5X20 cable interface card, each primary downstream channel has an upstream port that is statically associated with the downstream port.

Wideband Cable Modems

The number of RF channels that can be aggregated into a wideband channel is determined by the capability of the wideband cable modem. The Cisco Cable Wideband Solution, Release 1.0, supports the following modems:

•Linksys WCM300-NA, WCM300-EURO, and WCM300-JP Modems

•Scientific Atlanta DPC2505 and EPC2505 Modems

Linksys WCM300-NA, WCM300-EURO, and WCM300-JP Modems

For wideband channels, the Linksys WCM300-NA, WCM300-EURO, and WCM300-JP wideband cable modems support the receiving of a 50 MHz capture window of up to eight different downstream RF channels at 6 MHz per channel, or six different downstream RF channels at 8 MHz per channel. In addition to these eight RF channels, the Linksys WCM300 modem supports reception of one primary downstream channel (traditional DOCSIS channel).

The Linksys WCM300 wideband cable modem software supports the acquisition of up to three wideband (bonded) downstream channels:

•One primary bonded channel is the wideband channel on which the wideband cable modem receives all of its unicast data and some multicast data.

•Up to two secondary bonded channels are the wideband channels on which the wideband cable modem receives common multicast data streams. Secondary bonded channels are intended to receive multicast data such as broadcast video that is not available on the primary bonded channel.

The DOCSIS configuration file and the cable bonding-group-id command are used to define the primary and secondary bonded channels for the modem to select and acquire. The cable modem may identify the primary bonded channel and any secondary bonded channels to the CMTS at cable modem registration time. The DOCSIS configuration file can define the primary and secondary bonded channels for the modem to pass to the CMTS.

Note When a wideband channel is specified as a primary or secondary bonded channel in the DOCSIS configuration file, the channel must be identically specified as a primary or secondary bonded channel in the CMTS active, running configuration file. The cable bonding-group-id command specifies whether a bonding group is a primary or secondary bonding group (bonded channel). For information on the cable bonding-group-id command, see Chapter 11, "SIP and SPA Commands."

For information on the TLV encodings that can be used in the DOCSIS configuration file to identify primary and secondary bonded channels, see the Cisco Cable Wideband Solution Design and Implementation Guide, Release 1.0.

Scientific Atlanta DPC2505 and EPC2505 Modems

For wideband channels, the Scientific Atlanta DPC2505 and EPC2505 wideband cable modems support the receiving of two different downstream RF channels at either 6 MHz per channel or at 8 MHz per channel. In addition to these two RF channels, the Scientific Atlanta DPC2505 and EPC2505 modems support reception of one primary downstream channel (traditional DOCSIS channel). With the Scientific Atlanta cable modem, the two RF channels that are used for the wideband channel are called non-primary downstream channels.

•Unicast data can be received on any downstream channel.

•DOCSIS 2.0 multicast data can be received only on the primary downstream channel.

Specifying the Location for a Wideband SPA

For information on specifying the location of a Wideband SPA, see the "Identifying the Location of Wideband SIPs and SPAs" section on page 4-2.

Specifying Wideband Channels

At the Cisco IOS command line, the following interface command syntax is used to specify a wideband channel:

interface wideband-cable slot/subslot/bay:wb-channel-number

Wideband channels are similar to cable interfaces and are displayed in the output of commands such as show ip interface, show interfaces, and show interface wideband-cable command. For example:
Router# show interfaces 
...
Wideband-Cable1/0/0:0 is up, line protocol is up 
  Hardware is Wideband CMTS Cable interface, address is 0012.001a.8896 (bia 
0012.001a.8896)
  MTU 1500 bytes, BW 74730 Kbit, def 74730 Kbit DLY 1000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation MCNS, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:09, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  30 second input rate 0 bits/sec, 0 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     17033 packets output, 1765690 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
...
Router#
Hardware Status and Line Protocol Status for a Wideband-Channel Cable Interface

When a wideband-channel cable interface is specified in show interface wideband-cable or another Cisco IOS command that displays hardware status and line protocol status for a cable interface, the following applies:

•The hardware status for a wideband-channel cable interface will be up if the Wideband SPA is installed in the Wideband SIP and both the SIP and SPA are powered on.

•The line protocol for a wideband-channel cable interface will be up if the wideband channel is associated with at least one RF channel and the following parameters have been set for the RF channel:

–RF channel frequency

–MAC address of the next-hop interface or edge QAM device

–IP address of the edge QAM device

–UDP port number for the QAM that is used for the RF channel

If the line protocol for a wideband-channel cable interface is up, all wideband-channel configuration information needed to successfully send data is present. However, additional configuration information may be needed to complete the Wideband SPA configuration process. See the "Completing Required and Optional Wideband-Related Configuration Tasks" section for configuration procedures.

Preprovisioning of the Wideband SIP and Wideband SPA

Preprovisioning is an optional configuration task for the Wideband SIP and Wideband SPA. Preprovisioning on the Cisco uBR10012 router allows you to configure the Wideband SIP and Wideband SPA without their being physically present.

For information on preprovisioning the Wideband SIP and Wideband SPA, see the "Optional Configuration Tasks" section on page 4-4.

Entering Controller Configuration Mode for the Wideband SPA

The Wideband SPA is represented in the Cisco IOS software as a controller. You enable controller configuration by preprovisioning the Wideband SPA using the card command or by physically inserting the Wideband SPA in the Wideband SIP.

To enter controller configuration mode for the Wideband SPA, use the controller modular-cable command with the slot/subslot/bay identifying the location of the Wideband SPA:

controller modular-cable slot/subslot/bay

Most Wideband SPA configuration tasks are performed in controller configuration mode.

Completing Required and Optional Wideband-Related Configuration Tasks

The required and optional wideband-related configuration tasks can be broken down into these categories:

•Setting General Configuration Values for the Wideband SPA

•Configuring RF Channels

•Configuring Fiber Nodes

•Configuring Wideband Channels and Primary Downstream Channels as Virtual Bundle Members

•Setting Optional Configuration Values

Setting General Configuration Values for the Wideband SPA

Some Wideband SPA configuration items affect all RF channels on the SPA. These general Wideband SPA configuration values are set in controller configuration mode as follows:

•Use the annex modulation command to set the annex and modulation rate for the Wideband SPA.

•Use the ip-address (controller) command to set the IP address of the Wideband SPA FPGA. The IP address that is assigned to the Wideband SPA controller with the ip-address (controller) command is used as the source IP address for packets that are transmitted by the SPA.

•Use the modular-host subslot command to specify the modular-host line card that will be used for DOCSIS 3.0 Downstream Channel Bonding operations. The Wideband SPA itself does not provide these operations.

To set these general Wideband SPA configuration values, complete the following steps:

Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# controller modular-cable slot/subslot/bay

Example:
Router(config)# controller modular-cable 1/0/1

Enters controller configuration mode to configure the Wideband SPA controller.

Step 3

Router(config-controller)# annex {A | B} modulation {64qam | 256qam}

Example:
Router(config-controller)# annex B
modulation 64qam

Sets the annex and modulation rate for the Wideband SPA.

Step 4

Router(config-controller)# ip-address ip-address

Example:

Router(config-controller)# ip-address 192.168.200.31

Sets the IP address of the Wideband SPA FPGA.

Step 5

Router(config-controller)# modular-host subslot slot/subslot

Example:
Router(config-controller)# modular-host subslot 7/0

Specifies the modular-host line card (for example, uBR10-MC5X20S-D line card) that will be used for DOCSIS 3.0 Downstream Channel Bonding operations.

For detailed information on each of the wideband-related commands shown in the preceding procedure, see Chapter 11, "SIP and SPA Commands."

Configuring RF Channels

Each Wideband SPA supports up to 24 RF channels depending on how it is configured. For annex A and 256 QAM, each Wideband SPA supports 18 RF channels. For all other cases, the SPA supports 24 RF channels.

A wideband channel is a logical grouping of one or more physical RF channels. The cable rf-channel command is used to associate one or more RF channels with a wideband channel. By aggregating or "channel bonding" multiple RF channels, the wideband channel is capable of greater bandwidth capacity for downstream traffic than a single RF channel.

The number of RF channels that can be aggregated into a wideband channel is determined by the capability of the wideband cable modem.

•The Linksys WCM300-NA, WCM300-EURO, and WCM300-JP wideband cable modems can receive a wideband channel consisting of up to eight downstream RF channels at 6 MHz per channel, or up to six downstream RF channels at 8 MHz per channel. The modem requires that the channels be received in a 50 MHz capture window.

•The Scientific Atlanta DPC2505 and EPC2505 wideband cable modems can receive a wideband channel consisting of up to two downstream RF channels at either 6 MHz per channel or 8 MHz per channel.

Use the commands rf-channel and cable rf-channel to configure RF-channel characteristics. For each RF channel, these configuration items must be specified:

•Frequency

•IP address

•MAC address

•UDP port

•Wideband channel that is associated with the RF channel

In addition to these required configuration items, each RF channel can optionally have a description.

Note Be certain to verify that the RF-channel values set with rf-channel match the values configured on the the edge QAM device. Frequency, IP address, MAC address, and UDP port must match what is configured on the edge QAM device. If any of these values are incorrect, the Wideband SPA will not successfully communicate with the edge QAM device.

The rf-channel command configures all RF-channel characteristics except downstream channel ID and wideband channel association. For ease of use, configuration characteristics for an RF channel can be specified in one or multiple invocations of the rf-channel command. The rf-channel command syntax is as follows:

rf-channel rf-port [description description] [frequency freq]
[ip-address ip-address mac-address mac-address udp-port portnum]
The cable rf-channel command associates an RF channel with a wideband channel. The command can optionally be used to assign a percent of the RF channel's bandwidth to the wideband channel. The cable rf-channel command syntax is as follows:

cable rf-channel rf-port [bandwidth-percent bw-percent]
The cable rf-channel command allows you to allocate some or all of an RF channel's bandwidth to a wideband channel. An RF channel can be associated with multiple wideband channels on the same Wideband SPA as long the wideband channels belong to the same virtual bundle interface (cable bundle) and the RF channel's total allocated bandwidth does not exceed 100 percent. As an example, Table 8-1 shows that a single RF channel can be associated with multiple wideband channels as long as the total allocated bandwidth for the RF channel does not exceed 100 percent.

Table 8-1 RF Channel Bandwidth Allocation

RF Channel

Wideband

Channel

Bandwidth

Allocated

10

0

30 percent

10

1

30 percent

10

2

40 percent

Total Bandwidth Percent: 100 percent

Note Each RF channel on the Wideband SPA can be mapped to a specific QAM port on an edge QAM device. Traffic from different Wideband SPAs cannot be mixed on the same QAM port.

Optionally the rf-channel cable downstream channel-id command can be used to assign a downstream channel ID to an RF channel. The rf-channel cable downstream channel-id command syntax is as follows:

rf-channel rf-port cable downstream channel-id channel-id
By default, IOS software assigns a unique downstream channel ID to the RF channel so rf-channel cable downstream channel-id is used in cases where the assigned channel ID for the RF channel needs to be changed.

To configure an RF channel, complete the following steps. The procedure and the command syntax shown in the procedure break down the RF channel configuration into multiple invocations of the rf-channel command.

Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# controller modular-cable slot/subslot/bay

Example:
Router(config)# controller modular-cable 1/0/1

Enters controller configuration mode to configure the Wideband SPA controller.

Step 3

Router(config-controller)# rf-channel rf-port frequency freq

Example:
Router(config-controller)# rf-channel 1 frequency 699000000

Sets the center frequency for the RF channel. The rf-port number is the RF channel number.

Step 4

Router(config-controller)# rf-channel rf-port ip-address ip-address
mac-address mac-address
udp-port portnum

Example:
Router(config-controller)# rf-channel 1 ip-address 192.168.200.30
mac-address 0011-920e-a9ff
udp-port 49152

Specifies the following:

•IP address of the edge QAM device for this RF channel

•MAC address of the edge QAM or next-hop interface for this RF channel

•UDP port number for the edge QAM that will be used for this RF channel

Step 5

Router(config-controller)# rf-channel rf-port description description

Example:
Router(config-controller)# rf-channel 1 description Used for WB channel 0

(Optional) Specifies a description for the RF channel.

Step 6

Router(config-controller)# rf-channel rf-port cable downstream channel-id channel-id

Example:
Router(config-controller)# rf-channel 1 cable downstream channel-id 121

(Optional) Assigns a downstream channel ID to the RF channel. If the rf-channel cable downstream channel-id command is not issued, Cisco IOS software assigns a unique downstream channel ID to the RF channel. Use the rf-channel cable downstream channel-id to change the default channel ID.

Step 7

Router(config-controller)# exit

Example:

Router(config-controller)# exit
Router(config)#

Exits controller configuration mode.

Step 8

Router(config)# interface wideband-cable slot/subslot/bay:wb-channel

Example:
Router(config)# interface wideband-cable 1/0/1:5

Enters interface configuration mode for a wideband channel on a Wideband SPA.

Step 9

Router(config-if)# cable rf-channel rf-port [bandwidth-percent bw-percent]

Example:
Router(config-if)# cable rf-channel 1
bandwidth-percent 50

Associates an RF channel with the wideband channel and specifies the percent of bandwidth from this RF channel that will be used for the wideband channel.

Step 10

Router(config-if)# exit

Example:

Router(config-if)# exit
Router(config)#

Exits interface configuration mode.

For detailed information on each of the wideband-related commands shown in the preceding procedure, see Chapter 11, "SIP and SPA Commands."

Configuring Fiber Nodes

In a cable network, a fiber node is a point of interface between a fiber trunk and the coaxial distribution. A cable modem is physically connected to only one fiber node. Fiber node software configuration mirrors the physical topology of the cable network. When configuring wideband channels, a fiber node is a software mechanism to define a set of downstream and upstream channels that will flow into the physical fiber node.

For a wideband channel to work correctly, each fiber node must be configured as follows:

1. Use the cable fiber-node command to create the fiber node and to enter cable fiber-node configuration mode.

2. Use the downstream cable command to associate the fiber node with one or more primary downstream channels (traditional DOCSIS downstream channels).

3. Use the upstream cable connector command to specify the upstream channel ports that are connected to a fiber node.

4. Use the downstream modular-cable rf-channel command to make one or more RF channels available for the fiber node.

5. Optionally, use the description command to specify a description for the fiber node.

For each fiber node, a traditional DOCSIS downstream channel on a Cisco uBR10-MC5X20 cable interface line card is used to carry MAC management and signaling messages, and the associated traditional DOCSIS upstream channel is used for return data traffic and signaling. The traditional DOCSIS downstream channel used in this way is called the primary downstream channel. On the uBR10-MC5X20 cable interface card, each primary downstream channel has an upstream port that is statically associated with the downstream port.

The maximum number of cable fiber nodes that can be configured is limited to 256 for each CMTS.

To configure a fiber node, complete the following steps:
Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# cable fiber-node fiber-node-id

Example:
Router(config)# cable fiber-node 1

Enters cable fiber-node configuration mode for the specified fiber node.

Step 3

Router(config-fiber-node)# downstream cable slot/subslot/port

Example:
Router(config-fiber-node)# downstream cable 6/0/0

Assigns a primary downstream channel for the fiber node.
Step 4
Router(config-fiber-node)# upstream cable slot/subslot connector list-of-ports
Example: 
Router(config-fiber-node)# upstream cable 6/0 
connector 0-3 
Specifies the upstream ports that are connected to the fiber node.
Step 5
Router(config-fiber-node)# downstream modular-cable slot/subslot/bay rf-channel {rf-port | low-high}

Example:
Router(config-fiber-node)# downstream 
modular-cable 1/0/0 rf-channel 0-1 
For the specified Wideband SPA, indicates the RF channels that are available for wideband channels on the fiber node.
Step 6

Router(config-fiber-node)# description description

Example:

Router(config-fiber-node)# description Branch Office 105

(Optional) Specifies a comment providing information about the fiber node.

Step 7

Router(config-fiber-node)# exit

Example:

Router(config-fiber-node)# exit
Router(config)#

Exits cable fiber-node configuration mode.
Note The preceding example shows how to configure one fiber node so that it has all 24 RF channels from a Wideband SPA available for a wideband channel. In a real deployment, the number of RF channels that are used for a fiber node will vary depending on how many wideband channels are provisioned for the fiber node and how much bandwidth (number of RF channels) is required for the wideband channels.

For detailed information on each of the wideband-related commands shown in the preceding procedure, see Chapter 11, "SIP and SPA Commands."

Configuring Wideband Channels and Primary Downstream Channels as Virtual Bundle Members

For each fiber node, a traditional DOCSIS downstream channel is used to carry MAC management and signaling messages, and the associated traditional DOCSIS upstream channel is used for return data traffic and signaling. The traditional DOCSIS downstream channel used in this way is referred to as the primary downstream channel. The downstream cable command is used to associate the fiber node with one or more primary downstream channels. For information on the downstream cable command, see the "Configuring Fiber Nodes" section.

All wideband channels on a fiber node and all associated primary downstream channels must belong to the same virtual bundle interface and that virtual bundle interface must have one IP subnet. The tasks involved in configuring wideband channels and primary downstream channels as members of the same virtual bundle are as follows:

1. Define a virtual bundle interface.

2. Use the cable bundle command to add wideband channels as virtual bundle members.

3. Use the cable bundle command to add primary downstream channels as virtual bundle members.

Note For recent releases of Cisco IOS, a virtual bundle interface with virtual bundle members has replaced the master-slave model that was previously used for cable bundles. The virtual bundle model is used in Cisco IOS Release 12.3(21)BC and later releases.

To configure wideband channels and primary downstream channels as members of the same virtual bundle, complete the following steps:
Command

Purpose

Step 1

Router# configure terminal

Enters global configuration mode.

Step 2

Router(config)# interface bundle n

Example:
Router(config)# interface bundle 1

Enters interface configuration mode so that a virtual bundle can be defined.

Step 3

Router(config-if)# ip address address mask

Example:
Router(config-if)# ip address 172.25.1.1 255.255.255.0

Configures an IP address and subnet mask for the virtual bundle.

Step 4

Router(config-if)# ip pim sparse-mode

Example:
Router(config-if)# ip pim sparse-mode

(Optional) For multicast, enables sparse mode protocol-independent multicast (PIM) for the virtual bundle.
Step 5
Router(config-if)# cable helper-address address

Example:
Router(config-if)# cable helper-address 
10.0.0.0
(Optional) For the virtual bundle, specifies an IP address for an external Dynamic Host Configuration Protocol (DHCP) server.
Step 6

Router(config-if)# exit

Example:

Router(config-if)# exit

Exits interface configuration mode.

Step 7

Router(config)# interface wideband-cable slot/subslot/bay: wb-channel-number

Example:
Router(config)# interface wideband-cable 1/0/0:0

Enters interface configuration mode for a wideband channel.

Step 8

Router(config-if)# cable bundle n

Example:
Router(config-if)# cable bundle 1

Adds the wideband channel as a member of the virtual bundle.

Step 9

Router(config-if)# interface Cableslot/subslot/port

Example:
Router(config-if)# interface Cable5/0/0

Enters interface configuration mode for a primary (traditional DOCSIS) downstream channel.

Step 10

Router(config-if)# cable bundle n

Example:
Router(config-if)# cable bundle 1

Adds the primary downstream channel as a member of the virtual bundle. The wideband channel and primary downstream channel must be members of the same virtual bundle.

Step 11

Router(config-if)# exit

Example:

Router(config-if)# exit
Router(config)#

Exits interface configuration mode.
The preceding example shows how to add one wideband channel and one primary downstream channel to the virtual bundle interface. In a real deployment, all wideband channels on the Wideband SPA and one or more primary downstream channels would be added to the virtual bundle interface.

The preceding example shows the basic commands that are used for configuring wideband channels on a fiber node and all associated primary downstream channels as virtual bundle members. In a real deployment, additional commands may be used for virtual interface bundling. For detailed information on virtual interface bundling, see the Cisco CMTS Feature Guide.

Setting Optional Configuration Values

These wideband-related configuration tasks are optional:

•Enabling Auto-Reset Mode on the CMTS

•Configuring Primary and Secondary Bonded Channels with the cable bonding-group-id Command

Enabling Auto-Reset Mode on the CMTS

Use the cable wideband auto-reset command to enable wideband auto-reset mode on the CMTS. If wideband auto-reset mode is enabled, wideband cable modems registered on a cable interface as traditional DOCSIS modems are auto-reset when the cable interface becomes wideband-capable. When a wideband cable modem auto-resets, it deregisters on the CMTS as a traditional DOCSIS cable modem and immediately attempts to re-register as a wideband cable modem.

For a fully configured wideband CMTS, wideband cable modems can register as traditional DOCSIS modems for a variety of reasons, such as cable interface line card boot order or line card online insertion and removal (OIR). Rather than defer wideband cable modem registration, wideband cable modems are permitted to register as traditional DOCSIS modems. When and if a cable interface becomes wideband-capable, wideband cable modems that have registered as traditional DOCSIS modems are reset for CMTS routers with auto-reset mode enabled. These modems are only reset when the interface first becomes wideband capable and are not reset again if they subsequently fail to register as wideband cable modems.

A wideband deployment typically enables wideband auto-reset mode. To enable wideband auto-reset mode, complete the following steps:
Command

Purpose
Step 1
Router# configure terminal
Example: 
Router# configure terminal 
Enters global configuration mode.
Step 2

Router(config)# cable wideband auto-reset

Example:
Router(config)# cable wideband auto-reset

Enables wideband auto-reset mode on the CMTS.
For detailed information on the cable wideband auto-reset command, see Chapter 11, "SIP and SPA Commands."

Configuring Primary and Secondary Bonded Channels with the cable bonding-group-id Command

Configuration of primary and secondary bonded (wideband) channels with the cable bonding-group-id command applies only to channels that will be received by the Linksys WCM300-NA, WCM300-EURO, and WCM300-JP cable modems.

Note The cable bonding-group-id command is not used for wideband channels that will be received by the Scientific Atlanta DPC2505 and EPC2505 wideband cable modems.

For wideband channels that will be used by the Linksys WCM300 wideband cable modem, a wideband channel is configured either as a primary bonded channel or a secondary bonded channel. On the CMTS, the cable bonding-group-id command defines whether a wideband channel is a primary bonded channel or secondary bonded channel.

•A primary bonding group is a primary bonded channel. When the cable bonding-group-id command is issued, the absence of the secondary keyword indicates a primary bonding group. For example:
cable bonding-group-id 105 
•A secondary bonding group is a secondary bonded channel. When the cable bonding-group-id command is issued, the use of the secondary keyword indicates a secondary bonding group. For example:
cable bonding-group-id 105 secondary 
The primary bonded channel is the wideband channel on which the Linksys WCM300 cable modem receives all of its unicast data and some of its multicast data.

In addition to joining a primary bonded channel, a Linksys WCM300 cable modem may join up to two secondary bonded channels simultaneously in order to receive additional multicast data streams. The cable modem may identify the primary bonded channel and any secondary bonded channels to the CMTS at cable modem registration time. The wideband cable modem uses TLV encodings from the DOCSIS configuration file to identify primary and secondary bonded channels.

If a wideband channel is specified as a primary or secondary bonded channel in the DOCSIS configuration file, the channel must be identically specified as a primary or secondary bonded channel in the CMTS active, running configuration file.

•If a wideband channel is configured with cable bonding-group-id to be a primary bonded channel or by default is a primary bonded channel, the wideband cable modem will not register using it as one of its secondary bonded channels.

•If a wideband channel is configured with cable bonding-group-id to be a secondary bonded channel, the wideband cable modem will not register using it as its primary bonded channel.

For detailed information on TLV encodings used in the DOCSIS configuration file to identify primary and secondary bonded channels for the Linksys WCM300 wideband cable modem, see the Cisco Cable Wideband Solution Design and Implementation Guide, Release 1.0.

On the CMTS, to specify that a wideband channel is a primary or secondary bonded channel, complete the following steps:
Command

Purpose
Step 1
Router#configure terminal
Example:
Router#configure terminal 
Enters global configuration mode.
Step 2

Router(config)#interface wideband-cable slot/subslot/bay:wb-channel-number

Example:
Router(config)#interface wideband-cable 1/0/0:5

Enters interface configuration mode for the wideband-channel cable interface.

Step 3

Router(config-if)#cable bonding-group-id id-num [secondary]

Example:
Router(config-if)#cable bonding-group-id 105 secondary

Specifies a bonding-group ID and whether the wideband channel is a primary bonding group or secondary bonding group. If you omit the secondary keyword, the group is a primary bonding group.
Note When a wideband channel is defined on the Wideband SPA, IOS software configures the wideband channel as a primary bonding group (primary bonded channel) and assigns a default ID to the bonding group. If a wideband channel is to be used as a secondary bonded channel, use the cable bonding-group-id command with the secondary keyword to specify that the channel is a secondary bonded channel.

For detailed information on the cable bonding-group id command, see Chapter 11, "SIP and SPA Commands."

Verifying the Configuration

This section describes some of the Cisco IOS commands you can use to verify that the configuration tasks have been performed correctly:

•Verifying the Wideband SPA Configuration

•Verifying RF Channel Configuration

For more detailed information on monitoring the Wideband SPA and wideband channels, see the Cisco Cable Wideband Solution Design and Implementation Guide.

Verifying the Wideband SPA Configuration

In addition to using the show running-configuration command to display your router configuration settings, you can use a variety of commands to display information about the Wideband SPA including:

•Wideband SPA's configuration

•Wideband channels and RF channels

•Wideband-channel cable interfaces

For an example of the show interface wideband-cable output for a wideband-channel cable interface, see the "Examples of the show diag and show interface wideband-cable Commands" section on page 7-3. For other show commands that you can use for the Wideband SIP and SPA, see Chapter 11, "SIP and SPA Commands."

With Cisco IOS commands, the Wideband SPA and its Gigabit Ethernet ports are not considered standard user-configurable interfaces and do not appear in the output of the show interfaces command. The Wideband SPA is a controller and the show controller modular-cable command displays information about the SPA, its Gigabit Ethernet ports, installed SFP modules, and so on.

The following example provides sample show controller modular-cable output for the Wideband SPA located in slot 1, subslot 0, bay 0 of a Cisco uBR10012 router. In the output, the Gigabit Ethernet Port Selected field indicates that Port 0 is the active port on the Wideband SPA.
Router# show controller modular-cable 1/0/0 brief 
SPA 0 is present
status LED: [green]
Host 12V is enabled and is okay.
Power has been enabled to the SPA.
SPA reports power enabled and okay.
SPA reports it is okay and is NOT held in reset.
Gigabit Ethernet Port Selected : Port 1
Receive Interface              : In Reset
Receive Interface              : Disabled
Transmit Interface             : Out of Reset
Transmit Interface             : Enabled
Primary Receive Clock          : Disabled
Backup Receive Clock           : Disabled
SFP [Port 0] : 1000BASE-SX Present 
 Tx Enabled , LOS Detected , TxFault Not Detected
 Link Status [Port 0] : DOWN 
SFP [Port 1] : 1000BASE-T Present 
 Tx Enabled , LOS Not Detected , TxFault Not Detected
 Link Status [Port 1] : UP 
Wideband Channel information
Channel    RF bitmap   Police Info: Bytes      Interval
0          0x3                      0            0 ms
1          0xC                      0            0 ms
2          0x30                     0            0 ms
3          0xC0                     0            0 ms
4          0x300                    0            0 ms
5          0xC00                    0            0 ms
6          0x3000                   0            0 ms
7          0xC000                   0            0 ms
8          0x30000                  0            0 ms
9          0x0                      0            0 ms
10         0x0                      0            0 ms
11         0x0                      0            0 ms
RF Channel information
Modulation corresponds to : QAM 256 
Annex corresponds to : Annex B 
Modulation Data :GE Interframe Gap = 12 , MPEG-TS Frames per pkt = 4
SPA IP address = 0.0.0.0           SPA MAC Addr = 0012.001A.888B
QAM       Channel Rate     Rate adjust   State
0         0                1            Enabled   
1         0                1            Enabled   
2         0                1            Enabled   
3         0                1            Enabled   
4         0                1            Enabled   
5         0                1            Enabled   
6         0                1            Enabled   
7         0                1            Enabled   
8         0                1            Enabled   
9         0                1            Enabled   
10        0                1            Enabled   
11        0                1            Enabled   
12        0                1            Enabled   
13        0                1            Enabled   
14        0                1            Enabled   
15        0                1            Enabled   
16        0                1            Enabled   
17        0                1            Enabled   
18        0                1            Enabled   
19        0                1            Enabled   
20        0                1            Enabled   
21        0                1            Enabled   
22        0                1            Enabled   
23        0                1            Enabled   
Interrupt Counts
Idx  Interrupt Register       Interrupt Bit            Total Count  Masked:
69   blz_sp_int_stat_reg_0    spi_train_vld            24           YES
84   spa_brd_int_stat_reg     sp_int_0                 24           NO
85   spa_brd_int_stat_reg     scc_int                  2            NO
86   spa_brd_int_stat_reg     phy1_int                 1            NO
87   spa_brd_int_stat_reg     phy0_int                 1            NO
92   spa_brd_int_stat_reg     temp1_int                2            NO
93   spa_brd_int_stat_reg     temp0_int                2            NO
97   bm_int_stat_reg          bm_spa_brd               26           NO
Router#
Verifying RF Channel Configuration

The following example provides sample show hw-module bay output for RF channel 0 in the Wideband SPA located in slot 1, subslot 0, bay 0 of a Cisco uBR10012 router.
Router# show hw-module bay 1/0/0 config rf-channel 0 verbose 
SPA                                 : Modular-Cable 1/0/0
RF channel number                   : 0
Frequency                           : 699000000 Hz
Modulation                          : 256qam
Annex                               : B
IP address of next hop              : 10.30.4.110
MAC address of EQAM                 : 0090.f001.06ec
UDP port number                     : 49192
EQAM headroom                       : 0
Router#
Configuration Examples

This section includes the following configuration examples:

•Wideband SPA Controller Configuration Example

•Wideband Channel Configuration Example

•Virtual Bundle Configuration Example

•Cable Fiber Node Configuration Example

•Primary Downstream Channel Configuration Example

Wideband SPA Controller Configuration Example

The following example shows the configuration for the controller of the Wideband SPA located at slot 1, subslot 0, bay 0. Only RF channels 0 to 7 have been configured and associated with wideband channels.
controller Modular-Cable 1/0/0                                                  
 annex B modulation 256qam 0 23                                                 
 modular-host subslot 5/0                                                       
 rf-channel 0 cable downstream channel-id 24                                    
 rf-channel 0 frequency 699000000                                               
 rf-channel 0 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49192  
 rf-channel 1 cable downstream channel-id 25                                    
 rf-channel 1 frequency 705000000                                               
 rf-channel 1 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49193  
 rf-channel 2 cable downstream channel-id 26                                    
 rf-channel 2 frequency 711000000                                               
 rf-channel 2 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49194  
 rf-channel 3 cable downstream channel-id 27                                    
 rf-channel 3 frequency 717000000                                               
 rf-channel 3 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49195  
 rf-channel 4 cable downstream channel-id 28                                    
 rf-channel 4 frequency 723000000                                               
 rf-channel 4 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49196  
 rf-channel 5 cable downstream channel-id 29                                    
 rf-channel 5 frequency 729000000                                               
 rf-channel 5 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49197  
 rf-channel 6 cable downstream channel-id 30                                    
 rf-channel 6 frequency 735000000                                               
 rf-channel 6 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49198  
 rf-channel 7 cable downstream channel-id 31                                    
 rf-channel 7 frequency 741000000                                               
 rf-channel 7 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49199  
 rf-channel 8 cable downstream channel-id 32                                    
 rf-channel 8 frequency 747000000                                               
 rf-channel 8 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49200  
 rf-channel 9 cable downstream channel-id 33                                    
 rf-channel 9 frequency 753000000                                               
 rf-channel 9 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49201  
 rf-channel 10 cable downstream channel-id 34                                   
 rf-channel 10 frequency 759000000                                              
 rf-channel 10 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49202 
 rf-channel 11 cable downstream channel-id 35                                   
 rf-channel 11 frequency 765000000                                              
 rf-channel 11 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49203 
 rf-channel 12 cable downstream channel-id 36                                   
 rf-channel 12 frequency 771000000                                              
 rf-channel 12 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49204 
 rf-channel 13 cable downstream channel-id 37                                   
 rf-channel 13 frequency 777000000                                              
 rf-channel 13 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49205 
 rf-channel 14 cable downstream channel-id 38                                   
 rf-channel 14 frequency 783000000                                              
 rf-channel 14 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49206 
 rf-channel 15 cable downstream channel-id 39                                   
 rf-channel 15 frequency 789000000                                              
 rf-channel 15 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49207 
 rf-channel 16 cable downstream channel-id 40                                   
 rf-channel 16 frequency 795000000                                              
 rf-channel 16 ip-address 10.30.4.100 mac-address 0090.f00b.0037 udp-port 49172 
 rf-channel 17 cable downstream channel-id 41                                   
 rf-channel 17 frequency 801000000                                              
 rf-channel 17 ip-address 10.30.4.100 mac-address 0090.f00b.0037 udp-port 49173 
 rf-channel 18 cable downstream channel-id 42                                   
 rf-channel 19 cable downstream channel-id 43                                   
 rf-channel 20 cable downstream channel-id 44                                   
 rf-channel 21 cable downstream channel-id 45                                   
 rf-channel 22 cable downstream channel-id 46                                   
 rf-channel 23 cable downstream channel-id 47 
Wideband Channel Configuration Example

The following example shows how a wideband channel is configured. In this example, wideband channel Wideband-Cable1/0/0:0 is a member of virtual bundle interface 123.
interface Wideband-Cable1/0/0:0                                                 
 no ip address                                                                  
 load-interval 30                                                               
 cable bundle 123                                                               
 cable bonding-group-id 24                                                      
 cable rf-channel 0                                                             
 cable rf-channel 1 
The use of primary and secondary bonding groups (bonded channels) is relevant only to a CMTS that provides services to Linksys WCM300 modems.

•If the following example were present in the CMTS configuration file, Wideband-Cable1/0/0:0 would a primary bonded channel because the cable bonding-group-id command does not include the secondary keyword.
interface Wideband-Cable1/0/0:0                                                 
 no ip address                                                                  
 load-interval 30                                                               
 cable bundle 123                                                               
 cable bonding-group-id 24                                                      
 cable rf-channel 0                                                             
 cable rf-channel 1 
•If the next example were present in the CMTS configuration file, Wideband-Cable1/0/0:0 would a secondary bonded channel because the cable bonding-group-id command does include the secondary keyword.
interface Wideband-Cable1/0/0:0                                                 
 no ip address                                                                  
 load-interval 30                                                               
 cable bundle 123                                                               
 cable bonding-group-id 24 secondary
 cable rf-channel 0                                                             
 cable rf-channel 1 
Virtual Bundle Configuration Example

The wideband channel and its associated primary channels on the fiber node must belong to the same virtual bundle interface. The following example shows how virtual bundle interface 2 is configured.
interface Bundle123
 ip address 10.11.68.200 255.255.0.0
 ip pim sparse-mode
 cable match address 102 downstream Wideband-Cable1/0/0:1 bpi-enable
 cable arp filter request-send 3 2
 cable arp filter reply-accept 3 2
Cable Fiber Node Configuration Example

The following example shows how cable fiber node 1 is configured.
cable fiber-node 1
  downstream Cable5/0/1
  downstream Modular-Cable 1/0/0 rf-channel 0 - 3 
  upstream cable 5/0 connector 4 
  upstream cable 5/0 connector 5 
Primary Downstream Channel Configuration Example

The following example shows how the primary downstream channel located at slot/subslot/port 5/0/1 is configured. In this example, the primary downstream channel is a member of virtual bundle interface (cable bundle) 123 (as are the wideband channels on the fiber node, such as wideband channel Wideband-Cable1/0/0:0).
interface Cable5/0/1
 no ip address
 load-interval 30
 no cable packet-cache
 cable bundle 123
 cable downstream channel-id 120
 cable downstream annex B
 cable downstream modulation 256qam
 cable downstream interleave-depth 32
 cable downstream frequency 561000000
 no cable downstream rf-shutdown
 cable downstream rf-power 50
 cable upstream max-ports 4
 cable upstream 0 connector 4
 cable upstream 0 frequency 11400000
 cable upstream 0 docsis-mode tdma
 cable upstream 0 channel-width 1600000 1600000
 cable upstream 0 minislot-size 4
 cable upstream 0 power-level 0
 cable upstream 0 range-backoff 3 6
 cable upstream 0 modulation-profile 21
 no cable upstream 0 shutdown
 cable upstream 1 connector 5
 cable upstream 1 frequency 13000000
 cable upstream 1 docsis-mode tdma
 cable upstream 1 channel-width 1600000 1600000
 cable upstream 1 minislot-size 4
 cable upstream 1 power-level 0
 cable upstream 1 range-backoff 3 6
 cable upstream 1 modulation-profile 21
 no cable upstream 1 shutdown
 cable upstream 2 connector 6
 cable upstream 2 frequency 14600000
 cable upstream 2 docsis-mode tdma
 cable upstream 2 channel-width 1600000 1600000
 cable upstream 2 minislot-size 4
 cable upstream 2 power-level 0
 cable upstream 2 range-backoff 3 6
 cable upstream 2 modulation-profile 21
 no cable upstream 2 shutdown
 cable upstream 3 connector 7
 cable upstream 3 frequency 16200000
 cable upstream 3 docsis-mode tdma
 cable upstream 3 channel-width 1600000 1600000
 cable upstream 3 minislot-size 4
 cable upstream 3 power-level 0
 cable upstream 3 range-backoff 3 6
 cable upstream 3 modulation-profile 21
 no cable upstream 3 shutdown