-
Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration Guide
-
Preface
-
Using Cisco IOS Software
-
SIP and SPA Product Overview
-
Overview of Cisco uBR10012 Router SIPs
-
Configuring a SIP
-
Troubleshooting the SIPs
-
Command Summary for the SIPs
-
Overview of the Cisco Wideband SPA
-
Configuring the Cisco Wideband SPA
-
Troubleshooting the Cisco Wideband SPA
-
Command Summary for the Cisco Wideband SPA
-
Overview of Gigabit Ethernet SPAs
-
Configuring Gigabit Ethernet SPAs
-
Troubleshooting Gigabit Ethernet SPAs
-
Command Summary for Gigabit Ethernet SPAs
-
Upgrading Field-Programmable Devices
-
Command Summary for Field-Programmable Devices
-
Table Of Contents
Configuring the Cisco Wideband SPA
Cisco Wideband SPA Overview and Terminology
Wideband Channel or Bonding Group
Primary-Capable Downstream Channel
Extensible MAC Domain Support via Channel Grouping Domain
Linksys WCM300-NA, WCM300-EURO, and WCM300-JP Modems
Scientific Atlanta DPC2505 and EPC2505 Modems
Specifying the Location for the Cisco Wideband SPA
Specifying Narrowband Channels
Hardware Status and Line Protocol Status for a Wideband-Channel and Modular-Cable Interface
Preprovisioning of the Cisco Wideband SPA and a SIP
Entering Controller Configuration Mode for the Cisco Wideband SPA
Completing Required and Optional Wideband-Related Configuration Tasks
Setting General Configuration Values for the Cisco Wideband SPA
Configuring Narrowband Channels
Configuring Channel Grouping Domains
Setting Optional Configuration Values
Enabling Auto-Reset Mode on the CMTS
Configuring Primary and Secondary Bonded Channels with the cable bonding-group-id Command
Selecting Primary Downstream Channels by Narrowband and Wideband Cable Modems
Verifying the Cisco Wideband SPA Configuration
Verifying RF Channel Configuration
Verifying Fiber Node Configuration
Cisco Wideband SPA Controller Configuration Example
Wideband Channel Configuration Example
Virtual Bundle Configuration Example
Cable Fiber Node Configuration Example
Channel Grouping Domain Configuration Example
Modular Cable Interface Configuration Example
Wideband Cable Interface Configuration Examples
Wideband Cable Interface Configuration
Modular-Cable Interface Configuration
Configuring the Cisco Wideband SPA
This chapter provides information about configuring the Cisco Wideband SPA on the Cisco uBR10012 router. It includes the following sections:
•
Setting Optional Configuration Values
Configuration Tasks
This section describes how to configure the Cisco Wideband SPA and includes the following topics:
•
•
•
•
•
•
Cisco Wideband SPA Overview and Terminology
The Cisco Wideband SPA is a single-wide, half-height shared port adapter that provides DOCSIS Network formatting to downstream data packets. The Cisco Wideband SPA is used for downstream data traffic only. The Cisco Cisco Wideband SPA is a key component for the Cisco IOS features, DOCSIS 3.0 Downstream Channel Bonding and DOCSIS M-CMTS network architecture.
Each Cisco Wideband SPA is installed into a bay of the Cisco Wideband SIP or Cisco SIP-600 on a Cisco uBR10012 universal broadband router. See the "Identifying the Location of the Cisco Wideband SIP and Cisco Wideband SPA" section on page 4-2 for information on slot restrictions. Each Cisco 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 Cisco Wideband SPAs. Depending on how it is configured, each Cisco Wideband SPA allows up to 24 RF channels. A Cisco uBR10012 router with two Cisco Wideband SPAs supports a total of up to 48 RF channels.
Note
This section describes the following terms used for configuring the Cisco Wideband SPA:
•
•
•
Wideband Channel or Bonding Group
A wideband channel or bonding group 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 narrowband channel. During Cisco Wideband SPA configuration, each wideband channel is associated with one or more RF channels. Each Cisco Wideband SPA supports 32 wideband channels.
Narrowband Channel
A narrowband channel is a logical representation of a non-bonded channel that is a standard DOCSIS 1.x/2.0 protocol downstream channel that contains one RF channel.
Wideband-Cable Interface
A wideband-cable interface is a logical representation of the channels in the bonding group and is configured using the interface wideband-cable command.
Modular-Cable Interface
A modular-cable interface is a logical representation of the downstream channel's capability to carry non-bonded data traffic on the SPA downstream channels and is configured using the interface modular-cable command.
The Cisco 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 interfaces while wideband cable modems deliver higher-speed throughput on the wideband ports.
Primary-Capable Downstream Channel
A SPA downstream channel is made primary-capable via Channel Grouping Domain (CGD) configuration. A primary-capable downstream channel can carry narrowband traffic as well as wideband traffic. An RF channel is considered primary-capable when it has been associated with one or more upstream channels from a Cisco uBR10-MC5X20 cable interface and this RF channel can carry DOCSIS MAC management messages (MMM) including SYNC messages, Mini-slot Allocation Packet (MAP) messages, and Upstream Channel Descriptors (UCDs). Such an RF channel downstream is referred to as a primary-capable downstream channel. A DOCSIS Timing Interface (DTI) server that interfaces with the EQAM device and the Cisco DTCC card is used to synchronize DOCSIS MAC-layer messages. The interface represented by a single primary-capable downstream represents the narrowband portion of the RF channel.
A SPA downstream channel, whether primary-capable or not, can always be part of a bonded channel that carries bonded data traffic.
An RF channel can be shared by the associated modular-cable interface and by the wideband interfaces. The bandwidth of each RF channel can be configured to be statically divided between the modular-cable and wideband interfaces. Each RF channel's bandwidth can be used for wideband channels or narrowband channels or for a combination of the two.
A primary downstream channel is a primary-capable channel that is being used as a narrowband channel or as part of a wideband channel. A SPA DS channel may only be a primary-capable downstream channel for a single MAC domain. However, the same SPA DS channel may be part of one or more bonded channels (wideband interface) that serve multiple MAC domains. A primary downstream channel of one MAC domain can serve as non-primary downstream channel of another MAC domain. The total available bandwidth of a primary downstream channel, which is 96 percent, is split between the primary-capable downstream and non-primary-capable downstream channels. The remaining 4 percent is reserved for DOCSIS MAP and SYNC bandwidth.
Extensible MAC Domain Support via Channel Grouping Domain
A Channel Grouping Domain (CGD) is a collection of primary-capable downstream channels that are associated with a common set of upstream channels. A CGD is always specified within the context of a MAC domain to which all the downstream and upstream channels belong. The downstream channel local to the MAC domain on the Cisco uBR10-MC5X20 line card is always primary-capable, but a SPA DS channel has to be made primary-capable by explicit CGD configuration. A CGD provides the additional flexibilty of associating a subset of the upstream channels within a MAC domain to any of the primary-capable downstream channels, including the local downstream channels. When an upstream channel is associated with a downstream channel, its information is included in the MAP and UCD messages sent through that downstream channel.
Multiple CGD configurations may be included in the same MAC domain, allowing the flexibility of the MAC domain to include various primary-capable downstream channels associated with common or different sets of upstream channels.
Fiber Node Configuration
In a cable network, a fiber node is a point of interface between a fiber trunk and the coaxial portion of the cable plant. A cable modem is physically connected to only one fiber node. Fiber node software configuration mirrors the physical topology of the cable network and is needed to optimize the DOCSIS MAC-layer messages for channel bonding. When configuring fiber nodes with Cisco IOS CLI commands, a fiber node is a software mechanism to define the following:
•
•
•
A fiber node will 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. Each primary-capable downstream channel can be associated with up to 8 fiber nodes. All channels that belong to a fiber node are configured with different non-overlaying frequencies.
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 2.0 supports DOCSIS 3.0-compliant multichannel modems, including the following Linksys and Scientific Atlanta modems:
•
•
Linksys WCM300-NA, WCM300-EURO, and WCM300-JP Modems
For wideband channels, the Linksys WCM300-NA (WCM300-EURO for EuroDOCSIS and WCM300-JP for Japanese DOCSIS) wideband cable modem supports 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 eight wideband (bonded) downstream channels:
•
•
The DOCSIS configuration file and the cable bonding-group-id command define the primary and secondary bonded channels for the modem to select and acquire. The cable modem identifies the primary bonded channel and any secondary bonded channels to the CMTS at cable modem registration time.
For information on how the Linksys WCM300 modem selects primary and secondary bonded channels, see the Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide, Release 2.0.
Scientific Atlanta DPC2505 and EPC2505 Modems
When used with the Cisco uBR10012 CMTS, the Scientific Atlanta DPC2505 and EPC2505 (for EuroDOCSIS) wideband cable modems support the receiving of one wideband channel, which consists of up to three bonded downstream RF channels from the SPA at 6 MHz per channel or at 8 MHz per channel. One of the RF channels from the Cisco Wideband SPA serves as the primary downstream channel.
The Scientific Atlanta DPC2505 is DOCSIS 3.0-compliant and can be used in this mode (for example, if the modem is connected to a non-wideband Cisco CMTS or to a non-Cisco CMTS). The modem is also backward compatible with existing DOCSIS 1.x networks.
Specifying the Location for the Cisco Wideband SPA
For information on specifying the location of a Cisco Wideband SPA, see the "Identifying the Location of the Cisco Wideband SIP and Cisco Wideband SPA" section on page 4-2.
Specifying Narrowband Channels
A modular-cable interface is a narrowband interface associated with one downstream RF channel of the SPA. The same RF channel may be associated with an entirely independent bonding group, and the RF channel could be sharing RF bandwidth with this bonding group.
At the Cisco IOS command line, the interface modular-cable command is used to specify a narrowband channel.
Modular cable interfaces are similar to the downstream portion of cable interfaces and are displayed in the output of commands such as show ip interface, show interfaces, show interface modular-cable, and show running-config.
The following is sample output for the show interface command for a modular-cable interface:
Router# show interfaces
Modular-Cable 1/0/0:1 is up, line protocol is upHardware is CMTS MC interface, address is 0011.9221.84be (bia 0011.9221.84be)MTU 1500 bytes, BW 539 Kbit, DLY 1000 usec,reliability 255/255, txload 1/255, rxload 1/255Encapsulation MCNS, loopback not setKeepalive set (10 sec)ARP type: ARPA, ARP Timeout 04:00:00Last input never, output 1w3d, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort40 packets output, 9968 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out...
Note
Specifying Wideband Channels
At the Cisco IOS command line, the interface wideband-cable command is used to specify a wideband channel.
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. For example:
Router# show interfaces...Wideband-Cable1/0/0:0 is up, line protocol is upHardware 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/255Encapsulation MCNS, loopback not setKeepalive set (10 sec)ARP type: ARPA, ARP Timeout 04:00:00Last input never, output 00:00:09, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Queueing strategy: fifoOutput queue: 0/40 (size/max)30 second input rate 0 bits/sec, 0 packets/sec30 second output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort17033 packets output, 1765690 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out...Hardware Status and Line Protocol Status for a Wideband-Channel and Modular-Cable Interface
When Cisco IOS commands that display the hardware status and line protocol status for a cable interface such as the show interface wideband-cable command displays a wideband-channel cable interface or the show interface modular-cable command displays a modular cable interface, the following applies:
•
•
–
–
–
–
–
–
–
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 Cisco Wideband SPA configuration process. See the "Completing Required and Optional Wideband-Related Configuration Tasks" section for configuration procedures.
The line protocol for modular-cable interfaces will be up under the following conditions:
•
•
•
•
•
Note
•
–
–
–
–
–
Preprovisioning of the Cisco Wideband SPA and a SIP
Preprovisioning is an optional configuration task for the Cisco Wideband SPA on a SIP. Preprovisioning on the Cisco uBR10012 router allows you to configure the SIP and Cisco Wideband SPA without their physical presence.
For information on preprovisioning the Cisco Wideband SPA and a SIP, see the "Optional Configuration Tasks" section on page 4-6.
Entering Controller Configuration Mode for the Cisco Wideband SPA
The Cisco Wideband SPA is represented in the Cisco IOS software as a controller. You enable controller configuration by preprovisioning the Cisco Wideband SPA using the card command or by physically inserting the Cisco Wideband SPA in the SIP.
Following is an example of the card command:
card 1/0 2jacket-1card 1/0/0 24rfchannel-spa-1
Note
To enter controller configuration mode for the Cisco Wideband SPA, use the controller modular-cable command. Most Cisco 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 Cisco Wideband SPA
Some Cisco Wideband SPA configuration items affect all RF channels on the SPA. These general Cisco Wideband SPA configuration values are set in controller configuration mode as follows:
Note
•
•
To set these general Cisco Wideband SPA configuration values, complete the following steps:
Configuring Narrowband Channels
This section describes how to configure narrowband channels on the Cisco Wideband SPA.
Configuring RF Channels for Narrowband
This section describes how to configure the RF channels for narrowband capability. Use the RF channel commands to configure the RF channel characteristics . For each RF channel, you must specify these configuration items:
•
•
•
•
•
•
•
•
In addition to these required configuration items, each RF channel can have a description, though it is optional.
Note
By default, Cisco IOS software assigns a unique downstream channel ID to the RF channel. Use the rf-channel cable downstream channel-id command if you need to change the assigned RF channel ID.
Note
To configure an RF channel for narrowband, complete the following steps:
RF Channel Bandwidth Allocation for Modular-Cable and Wideband-Cable Interfaces
During RF channel configuration, the bandwidth from each RF channel is statically partitioned between the modular-cable and wideband-cable interfaces.
Bandwidth Allocation for Modular-Cable Interfaces
Use the cable rf-bandwidth-percent percent_value command to allocate RF channel bandwidth to a modular-cable interface. If the RF channel is primary-capable, the total allocated percentage of the RF channel, including both, modular-cable interface and the wideband interfaces must not exceed 96 percent. The extra 4 percent of RF channel bandwidth is reserved for MAP and other MAC management messages traffic using this RF channel as its primary-capable downstream channel.
The default bandwidth percentage for a modular cable interface is set to zero. If the bandwidth is not allocated, then the RF channel cannot be used as a primary-capable channel and 100 percent of this RF channel bandwidth can be used for wideband interfaces.
Bandwidth Allocation for Wideband-Cable Interfaces
The total bandwidth allocation can be 100 percent if the RF channel is configured only for wideband interfaces.
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-2, as an example, shows that a primary-capable RF channel can be associated with multiple narrowband and multiple wideband channels as long as the total allocated bandwidth for the RF channel does not exceed 96 percent. The extra 4 percent is used for MAP and MAC management traffic.
Configuring Modular-Cable Interfaces
•
From this mode, you can allocate bandwidth percentage to the narrowband interface.
•
To configure a modular-cable interface, complete the following steps:
Configuring Fiber Nodes for Narrowband
Fiber node configuration is used mainly to configure a wideband channel. Configuring fiber nodes for narrowband is optional. Use the cable fiber-node command to configure the fiber nodes.
Configuring Wideband Channels
This section provides information on how to configure the RF channels for wideband capability.
Configuring RF Channels for Wideband
A wideband channel is a logical grouping of one or more physical RF channels. 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.
•
•
1.
2.
To configure an RF channel for wideband, complete the following steps:
Configuring Wideband-Channel Cable Interfaces
•
From this mode, you can specify bandwidth percent for each cable RF channel that is added to the wideband interface. Each wideband-cable interface is a representation of a bonding group and allows you to create up to 32 bonding group IDs for each SPA. The Cisco IOS software automatically assigns a bonding group ID to each wideband-channel cable interface by default.
•
•
•
To configure a wideband-cable interface, complete the following steps:
Configuring a Virtual Bundle
For a fiber node to be in valid state, all wideband and modular cable interfaces that use the RF channels in the fiber node must belong to the same virtual bundle interface. You must assign virtual bundle numbers for wideband interfaces using CLI configuration. The bundle membership of the MAC domain, namely the Cisco uBR10-MC5X20 line card host interface, is inherited by the modular-cable interface via the CGD configuration.
Wideband-Cable Interfaces Belonging to the Same Virtual Bundle
This section provides an example of wideband-cable interfaces that belong to the same virtual bundle.
In the following example, fiber node 1 includes RF channels 0 to 3 of Cisco Wideband SPA1/0/0 and these RF channels are used by two wideband interfaces.
Note
interface Wideband-Cable1/0/0:12no ip addresscable bundle 1cable bonding-group-id 36cable rf-channel 0 bandwidth-percent 90cable rf-channel 1 bandwidth-percent 50cable rf-channel 2endinterface Wideband-Cable1/0/0:13no ip addresscable bundle 1cable bonding-group-id 37cable rf-channel 1 bandwidth-percent 50cable rf-channel 2cable rf-channel 3endIn this case, the fiber node is in valid state because the two wideband channels share the same RF channel and the wideband interfaces are in the same virtual bundle.
Modular-Cable Interfaces Belonging to the Same Virtual Bundle
In the example shown above, if RF channel 0 of the Cisco Wideband SPA 1/0/0 is configured as a primary-capable channel and is associated with the Cisco uBR10-MC5X20 line card host interface 6/0/1, then the modular-cable interface 1/0/0:0 inherits the bundle membership of this host interface. This bundle number must be the same as the two wideband interfaces, interface Wideband-Cable 1/0/0:12 and interface Wideband-Cable 1/0/0:13. Otherwise, fiber node 1 that includes the RF channels 0 to 3 will be in invalid state.
The virtual bundle number of the wideband or modular-cable interfaces cannot be changed after the RF channels that belong to these interfaces are added to the fiber node. To change the virtual bundle number, you must remove the RF channel from the fiber node before making the change.
All wideband channels on a fiber node and all associated primary downstream channels must belong to the same virtual bundle interface. The tasks involved in configuring wideband channels and primary downstream channels as members of the same virtual bundle are as follows:
1.
2.
Note
To configure two wideband cable interfaces and a CGD host interface as members of a the same virtual bundle, complete the following steps:
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 at the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/cmtsfg.htmlConfiguring Fiber Nodes for Wideband
Configuring cable fiber nodes with the cable fiber-node command is required for fiber nodes that are used for wideband channels. Cable fiber node configuration does not allow downstream interfaces to be combined into the same fiber node unless they are members of the same virtual bundle interface.
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.
2.
Cisco uBR10-MC5X20 line card downstream channels. Each fiber node should have at least one primary downstream. This command is optional if the primary downstream channel for this fiber node is assigned from a SPA downstream.3.
4.
5.
For each fiber node, a primary downstream channel is used to carry SYNCs, MAPs, and other MAC-layer management messages, and the associated upstream channel is used to carry MAC management messages. A DTI server that interfaces with the EQAM device and the Cisco DTCC card is used to synchronize DOCSIS MAC-layer messages.
In Cisco IOS Release 12.3(21)BC, the primary downstream channel, which is a traditional DOCSIS downstream channel on the Cisco uBR10-MC5X20 cable interface line card, is used to carry MAC management and signaling messages, and the associated traditional DOCSIS upstream channel is used for return data traffic and signaling.
Beginning in Cisco IOS Releases 12.3(23)BC and 12.2(33)SCB, either an RF channel from the SPA or a Cisco uBR10-MC5X20 downstream channel can serve as a primary channel in a fiber node. If the fiber node does not have a Cisco uBR10-MC5X20 downstream channel, then make sure that at least one of the RF channels specified in the downstream modular-cable rf-channel command is a primary-capable downstream channel.
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:
Note
Configuring Channel Grouping Domains
A Channel Grouping Domain (CGD) is a set of primary-capable downstreams associated with the set of upstreams under a cable interface, where the downstream channels can be shared by one or more upstreams. A Channel Grouping Domain is represented by a cable interface and can have only a single downstream from the Cisco uBR10-MC5X20 cable interface line card and one or more downstreams from the SPA that are associated with one or more upstreams. Each CGD is part of a MAC domain and each MAC domain can be enabled or disabled and can be identified by an automatically assigned unique MAC address.
A Channel Grouping Domain is created using the following:
•
•
•
Figure 8-1 shows a representation of a Channel Grouping Domain.
Figure 8-1 MAC Domain Support via Channel Grouping Domain Configurations
In this example:
•
•
•
•
Note
The CGD allows load balancing groups to be created across one or more CGDs and enables the load balancing groups by default within the CGDs.
The sample CGD shown above is configured as follows:
Load Balancing Groups
A Load Balancing Group (LBG) is an operator-configured managed object that controls how the CMTS assigns the service flows of registered cable modems among an identified set of upstream and downstream channels of the CMTS.
An operator configures a Load Balancing Group with the following attributes:
•
•
•
•
•
For more information on load balancing, refer to the Cisco DOCSIS 3.0 Downstream Channel Bonding Solution Design and Implementation Guide, Release 2.0.
Primary Downstream Channel Selection in a Fiber Node Configured with Downstreams from the Cisco uBR10-MC5X20 Cable Interface Line Card and SPA Downstreams
If a fiber node is configured with a primary downstream from a Cisco uBR10-MC5X20 cable interface line card as well as a primary downstream from the SPA that is part of a wideband channel, then the primary downstream channel selection depends on the downstream channel selection policies (that govern when the cable modem can be moved) implemented and enforced by the configuration. The fiber node can be configured to force a Scientific Atlanta DPC2505 (EPC2505 for EuroDOCSIS) to perform 3-channel bonding. But this will also depend on the implemented downstream channel selection policies that govern when the cable modem can be moved.
Here is an example of a fiber node configured with a primary downstream from the
Cisco uBR10-MC5X20 cable interface line card as well as a primary downstream from the SPA:
Assigning the Modem a 2-Channel Bonding Group Versus a 3-Channel Bonding Group
When a 3-channel modem is connected to a fiber node, the modem can be assigned either a 2-channel bonding group or a 3-channel bonding group. If the modem scans and acquires a Cisco uBR10-MC5X20 cable interface line card downstream channel as its primary donwstream, the CMTS can only assign a 2-channel bonding group to the modem. If the modem scans and acquires a primary-capable SPA downstream as its primary downstream and if the CMTS is configured to assign a 3-channel bonding group, which contains a primary-capable downstream to this modem, then the modem will perform 3-channel bonding. If CMTS assigns a 2-channel bonding group to the modem, then the modem will perform 2-channel bonding.
If the downstream channel selection policies have been implemented, then a 3-channel modem can be forced to perform 3-channel bonding.
For more information on primary-capable downstream channel selection, refer to the Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide, Release 2.0.
Setting Optional Configuration Values
These wideband-related configuration tasks are optional:
•
•
•
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:
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
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. The cable bonding-group-id command defines whether a wideband channel is a primary bonded channel or secondary bonded channel.
•
cable bonding-group-id 105•
cable bonding-group-id 105 secondaryThe primary bonded channel is the wideband channel that a Linksys WCM300 cable modem first successfully registers on and is the channel on which it receives its unicast 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 multicast data streams. The wideband cable modem selects secondary bonded channels to acquire using type, length, value (TLV) encodings from the DOCSIS configuration file.
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.
•
•
For detailed information on how the Linksys WCM300 wideband cable modem selects primary and secondary bonded channels, see the Cisco DOCSIS 3.0 Downstream Channel Bonding Solution Design and Implementation Guide, Release 2.0.
To specify that a wideband channel is a primary or secondary bonded channel, complete the following steps:
Tip
Selecting Primary Downstream Channels by Narrowband and Wideband Cable Modems
Each primary downstream channel from the SPA can be configured to carry narrowband as well as wideband traffic. Each SPA RF channel can be shared by the associated modular-cable interface as well as the wideband interfaces. Depending on the type of wideband-capable modems used, this allows support for bonding of two to eight RF channels from the same SPA to deliver higher-speed throughput data. This section describes how a modem selects the primary downstream channel that is used for MAC management traffic.
Primary Downstream Channel Selection for Wideband Cable Modems
The wideband-capable cable modems or modems that have bonded services are forced to register on the primary-capable channel that is part of a wideband channel's set of RF channels (downstream bonding group) using the following command:
cable service attribute ds-bonded downstream-type bonding-enabled [enforce]
Use this command to force a downstream bonding-capable modem to initialize on a bonded primary-capable downstream channel.
Note
Primary Downstream Channel Selection for Narrowband Modems
Primary downstream channel seletion for narrowband modems provides the flexibility to restrict narrowband modems on specific types of downstream channels.
The primary downstream channel selection for narrowband modems can be done in one of two ways:
•
cable service attribute non-ds-bonded legacy-ranging downstream-type frequency
•
cable service attribute non-ds-bonded downstream-type bonding-disabled
Both these options can be configured simultaneously. If the cable modem is a narrowband modem and accesses the CMTS with legacy initial ranging, then the option of registering the modem based on a specific downstream channel frequency will override the option where the modem is allowed to register only on narrowband channels.
Note
Note
Primary Downstream Channel Selection for Voice-Enabled Services
By default, all primary-capable narrowband downstream channels on the SPA and on the
Cisco uBR10-MC5X20 cable interface line card are voice-enabled.To restrict voice services only to downstream channels on the Cisco uBR10-MC5X20 cable interface line card, use the following command:
cable service attribute voice-enabled downstream-type HA-capable
To provide higher system availability for voice services, the voice-enabled services can be restricted only to downstreams from the Cisco uBR10-MC5X20 cable interface line card by configuring only the
Cisco uBR10-MC5X20 cable interface line card downstream channels as voice-capable. The CMTS attempts to register or move voice modems to the hosting Cisco uBR10-MC5X20 cable interface line card downstream channel in the same load balancing group.For more information on primary dowstream channel selection, refer to the Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide, Release 2.0.
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:
•
•
•
For more detailed information on monitoring the Cisco Wideband SPA and wideband channels, see the Cisco DOCSIS 3.0 Downstream Channel Bonding Solution Design and Implementation Guide.
Verifying the Cisco 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 Cisco Wideband SPA including:
•
•
•
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-5.
With Cisco IOS commands, the Cisco 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 Cisco 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 Cisco 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 1 is the active port on the Cisco Wideband SPA.
Note
Router# show controller modular-cable 1/0/0 briefSPA 0 is presentstatus 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 1Receive Interface : In ResetReceive Interface : DisabledTransmit Interface : Out of ResetTransmit Interface : EnabledPrimary Receive Clock : DisabledBackup Receive Clock : DisabledSFP [Port 0] : 1000BASE-SX PresentTx Enabled , LOS Detected , TxFault Not DetectedLink Status [Port 0] : DOWNSFP [Port 1] : 1000BASE-T PresentTx Enabled , LOS Not Detected , TxFault Not DetectedLink Status [Port 1] : UPWideband Channel informationChannel RF bitmap Police Info: Bytes Interval0 0x3 0 0 ms1 0xC 0 0 ms2 0x30 0 0 ms3 0xC0 0 0 ms4 0x300 0 0 ms5 0xC00 0 0 ms6 0x3000 0 0 ms7 0xC000 0 0 ms8 0x30000 0 0 ms9 0x0 0 0 ms10 0x0 0 0 ms11 0x0 0 0 ms12 0x0 0 0 ms13 0x0 0 0 ms14 0x0 0 0 ms15 0x0 0 0 ms16 0x0 0 0 ms17 0x0 0 0 ms18 0x0 0 0 ms19 0x0 0 0 ms20 0x0 0 0 ms21 0x0 0 0 ms22 0x0 0 0 ms23 0x0 0 0 ms24 0x0 0 0 ms25 0x0 0 0 ms26 0x0 0 0 ms27 0x0 0 0 ms28 0x0 0 0 ms29 0x0 0 0 ms30 0x0 0 0 ms31 0x0 0 0 msRF Channel informationModulation corresponds to : QAM 256Annex corresponds to : Annex BModulation Data :GE Interframe Gap = 12 , MPEG-TS Frames per pkt = 4SPA IP address = 0.0.0.0 SPA MAC Addr = 0012.001A.888BQAM Channel Rate Rate adjust State0 0 1 Enabled1 0 1 Enabled2 0 1 Enabled3 0 1 Enabled4 0 1 Enabled5 0 1 Enabled6 0 1 Enabled7 0 1 Enabled8 0 1 Enabled9 0 1 Enabled10 0 1 Enabled11 0 1 Enabled12 0 1 Enabled13 0 1 Enabled14 0 1 Enabled15 0 1 Enabled16 0 1 Enabled17 0 1 Enabled18 0 1 Enabled19 0 1 Enabled20 0 1 Enabled21 0 1 Enabled22 0 1 Enabled23 0 1 EnabledInterrupt CountsIdx Interrupt Register Interrupt Bit Total Count Masked:69 blz_sp_int_stat_reg_0 spi_train_vld 24 YES84 spa_brd_int_stat_reg sp_int_0 24 NO85 spa_brd_int_stat_reg scc_int 2 NO86 spa_brd_int_stat_reg phy1_int 1 NO87 spa_brd_int_stat_reg phy0_int 1 NO92 spa_brd_int_stat_reg temp1_int 2 NO93 spa_brd_int_stat_reg temp0_int 2 NO97 bm_int_stat_reg bm_spa_brd 26 NOVerifying RF Channel Configuration
The following example provides sample show hw-module bay output for RF channel 0 in the Cisco Wideband SPA located in slot 1, subslot 0, bay 0 of a Cisco uBR10012 router.
Note
Router# show hw-module bay 1/0/0 config rf-channel 0 verboseSPA : Modular-Cable 1/0/0RF channel number : 0Frequency : 699000000 HzModulation : 256qamAnnex : BIP address of next hop : 10.30.4.110MAC address of EQAM : 0090.f001.06ecUDP port number : 49192EQAM headroom : 0Verifying Fiber Node Configuration
The following example provides sample show cable fiber-node output for cable fiber node 1:
Router# show cable fiber-node 1Fiber-Node 1 (prim_rfch = 0x400, bg_rfch = 0x3, status = 0x1)MDD Status: ValidConfiguration Examples
This section includes the following configuration examples:
•
•
•
•
•
•
•
Cisco Wideband SPA Controller Configuration Example
The following example shows the configuration for the controller of the Cisco Wideband SPA located in slot 1, subslot 0, bay 0. Only RF channels 0 to 17 have been configured and associated with wideband channels.
Note
controller Modular-Cable 1/0/0annex B modulation 256qam 0 23modular-host subslot 5/0rf-channel 0 cable downstream channel-id 24rf-channel 0 frequency 699000000rf-channel 0 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49192rf-channel 1 cable downstream channel-id 25rf-channel 1 frequency 705000000rf-channel 1 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49193rf-channel 2 cable downstream channel-id 26rf-channel 2 frequency 711000000rf-channel 2 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49194rf-channel 3 cable downstream channel-id 27rf-channel 3 frequency 717000000rf-channel 3 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49195rf-channel 4 cable downstream channel-id 28rf-channel 4 frequency 723000000rf-channel 4 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49196rf-channel 5 cable downstream channel-id 29rf-channel 5 frequency 729000000rf-channel 5 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49197rf-channel 6 cable downstream channel-id 30rf-channel 6 frequency 735000000rf-channel 6 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49198rf-channel 7 cable downstream channel-id 31rf-channel 7 frequency 741000000rf-channel 7 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49199rf-channel 8 cable downstream channel-id 32rf-channel 8 frequency 747000000rf-channel 8 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49200rf-channel 9 cable downstream channel-id 33rf-channel 9 frequency 753000000rf-channel 9 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49201rf-channel 10 cable downstream channel-id 34rf-channel 10 frequency 759000000rf-channel 10 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49202rf-channel 11 cable downstream channel-id 35rf-channel 11 frequency 765000000rf-channel 11 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49203rf-channel 12 cable downstream channel-id 36rf-channel 12 frequency 771000000rf-channel 12 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49204rf-channel 13 cable downstream channel-id 37rf-channel 13 frequency 777000000rf-channel 13 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49205rf-channel 14 cable downstream channel-id 38rf-channel 14 frequency 783000000rf-channel 14 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49206rf-channel 15 cable downstream channel-id 39rf-channel 15 frequency 789000000rf-channel 15 ip-address 10.30.4.110 mac-address 0090.f001.06ec udp-port 49207rf-channel 16 cable downstream channel-id 40rf-channel 16 frequency 795000000rf-channel 16 ip-address 10.30.4.100 mac-address 0090.f00b.0037 udp-port 49172rf-channel 17 cable downstream channel-id 41rf-channel 17 frequency 801000000rf-channel 17 ip-address 10.30.4.100 mac-address 0090.f00b.0037 udp-port 49173rf-channel 18 cable downstream channel-id 42rf-channel 19 cable downstream channel-id 43rf-channel 20 cable downstream channel-id 44rf-channel 21 cable downstream channel-id 45rf-channel 22 cable downstream channel-id 46rf-channel 23 cable downstream channel-id 47Wideband 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 1.
Note
Note
interface Wideband-Cable1/0/0:0no ip addressload-interval 30cable bundle 1cable bonding-group-id 24cable rf-channel 0cable rf-channel 1Virtual 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 1 is configured.
interface Bundle1ip address 10.11.68.200 255.255.0.0ip pim sparse-modecable match address 102 downstream Wideband-Cable1/0/0:1 bpi-enablecable arp filter request-send 3 2cable arp filter reply-accept 3 2Cable Fiber Node Configuration Example
The following example shows how cable fiber node 1 is configured.
cable fiber-node 1downstream Cable5/0/1downstream Modular-Cable 1/0/0 rf-channel 0 - 3upstream cable 5/0 connector 4upstream cable 5/0 connector 5Channel Grouping Domain 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) 1 (as are the wideband channels on the fiber node, such as the wideband channel Wideband-Cable1/0/0:0).
Note
interface Cable5/0/1no ip addressload-interval 30downstream Modular-Cable 1/0/0 rf-channel 0 - 3 upstream 0-2no cable packet-cachecable bundle 1cable downstream channel-id 120cable downstream annex Bcable downstream modulation 256qamcable downstream interleave-depth 32cable downstream frequency 561000000no cable downstream rf-shutdowncable downstream rf-power 50cable upstream max-ports 4cable upstream 0 connector 4cable upstream 0 frequency 11400000cable upstream 0 docsis-mode tdmacable upstream 0 channel-width 1600000 1600000cable upstream 0 minislot-size 4cable upstream 0 power-level 0cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21no cable upstream 0 shutdowncable upstream 1 connector 5cable upstream 1 frequency 13000000cable upstream 1 docsis-mode tdmacable upstream 1 channel-width 1600000 1600000cable upstream 1 minislot-size 4cable upstream 1 power-level 0cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21no cable upstream 1 shutdowncable upstream 2 connector 6cable upstream 2 frequency 14600000cable upstream 2 docsis-mode tdmacable upstream 2 channel-width 1600000 1600000cable upstream 2 minislot-size 4cable upstream 2 power-level 0cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21no cable upstream 2 shutdowncable upstream 3 connector 7cable upstream 3 frequency 16200000cable upstream 3 docsis-mode tdmacable upstream 3 channel-width 1600000 1600000cable upstream 3 minislot-size 4cable upstream 3 power-level 0cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21no cable upstream 3 shutdownModular Cable Interface Configuration Example
The following example shows how a modular cable interface is configured. In this example, the modular cable interface slot/subslot/bay:narrowband channel 1/0/0:2 is configured. The cable rf-bandwidth-percent command specifies that 40 percent of the bandwidth is reserved for this interface.
Note
interface Modular-Cable 1/0/0:2no ip addresscable bundle 1cable rf-bandwidth-percent 40
Wideband Cable Interface Configuration Examples
The example below shows a three-channel wideband cable interface using Cisco uBR10-MC5X20 local downstream as the primary downstream. In this example, cable rf-channel 2, cable rf-channel 3, and cable rf-channel 4 are added to the wideband cable interface slot/subslot/bay: wideband channel 1/0/0:0. This wideband interface is capable of 3-channel bonding as well a 2-channel bonding.
Note
interface Wideband-Cable 1/0/0:0no ip addressload-interval 30cable bundle 1cable bonding-group-id 25cable rf-channel 2 bandwidth-percent 20cable rf-channel 3 bandwidth-percent 30cable rf-channel 4The example below shows the downstream cable command used in the fiber node configuration assigning the Cisco uBR10-MC5X20 downstream as the primary-capable downstream channel.
Router# configure terminalRouter(config)# cable fiber-node 5Router(config-fiber-node)# downstream cable 6/0/0downstream modular-cable 1/0/0 rf-channel 2upstream cable 5/0 connector 0The example below shows a wideband interface with a SPA RF channel 0 as a primary-capable channel. This interface is capable of 3-channel bonding.
Router# configure terminalRouter (config)# interface cable 5/1/0Router(config-if)# downstream modular-cable 1/0/0 rf-channel 0 upstream 0-1 4-5interface Wideband-Cable 1/0/0:1no ip addressload-interval 30cable bundle 1cable bonding-group-id 25cable rf-channel 0cable rf-channel 1cable rf-channel 2The example below shows a modular-cable interface capable of registering narrowband modems on a SPA RF channel.
Router# configure terminalRouter (config)# interface cable 5/1/0Router(config-if)# downstream modular-cable 1/0/0 rf-channel 2 upstream 0-1 4-5interface Modular-Cable 1/0/0:2no ip addresscable bundle 1cable rf-bandwidth-percent 40Sample Configuration
The configuration shown in Figure 8-2 represents a sample implementation of a wideband and a modular-cable interface.
Figure 8-2
Sample Cable Interface Configuration
Wideband Cable Interface Configuration
Channel Bonding: Three RF channels, RF0, RF1 and RF2 from the SPA residing in slot 1, subslot 0, and bay 0 are bonded to form the wideband cable interface 1/0/0:0.
•
•
•
Primary Downstream Channel: RF channel 0, which is associated with upstream 0, connector 0 from the Cisco uBR10-MC5X20 line card, serves as the primary downstream channel that is used for SYNCs, MAPs, and MAC management traffic.
Note
The wideband interface is configured as follows:
Router(config)# interface wideband-cable 1/0/0:0Router(config-if)# cable bundle 1Router(config-if)# cable rf-channel 0 bandwidth-percent 50Router(config-if)# cable rf-channel 1 bandwidth-percent 75Router(config-if)# cable rf-channel 2Router(config-if)# cable bonding-group-id 1Router(config-if)# exitModular-Cable Interface Configuration
RF channel 0, which is the narrowband channel, is associated with upstream 0, connector 0 from the Cisco uBR10-MC5X20 line card.
Note
The modular-cable interface is configured as follows:
Router(config)# interface modular-cable 1/0/0:0Router(config-if)# cable rf-bandwidth-percent 50Router(config-if)# exit
