Feedback
|
Table Of Contents
Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
Prerequisites for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
Restrictions for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
Information About the Cisco uBR-MC3GX60V Cable Interface Line Card
Downstream Sharing Between the Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA
How to Configure the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the Modular Cable Controller on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring a Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the Modular Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the Wideband Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the RF Plant Topology on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring Redundancy on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring Global HCCP N+1 Line Card Redundancy on the Cisco uBR10012 Router
Configuring the DEPI Control Plane on the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring Manual DEPI on the Cisco uBR-MC3GX60V Cable Interface Line Card
Monitoring and Maintaining the Cisco uBR-MC3GX60V Cable Interface Line Card
Viewing the Cisco uBR-MC3GX60V Cable Interface Line Card Statistics
Viewing Information About the Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA Downstream Sharing
Viewing Information About the Interface Controllers
Viewing Information About the Cable Modems
Troubleshooting the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuration Examples for the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuration Examples for the Cisco uBR-MC3GX60V Cable Interface Line Card along with Wideband SPA
Feature Information for the Cisco uBR-MC3GX60V Cable Interface Line Card
Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
First Published: November 29, 2010Last Updated: October 15, 2012
The Cisco uBR-MC3GX60V cable interface line card is a Cisco modular cable modem termination system (M-CMTS) DOCSIS 3.0-compliant line card designed for the Cisco uBR10012 universal broadband router. It supports 60 upstream and 72 downstream channels.
The Cisco uBR-MC3GX60V cable interface line card offers increased configuration flexibility and provides up to 14 times the downstream data density when compared to earlier generations of cable line cards.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for the Cisco uBR-MC3GX60V Cable Interface Line Card" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Restrictions for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Information About the Cisco uBR-MC3GX60V Cable Interface Line Card
•
How to Configure the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Monitoring and Maintaining the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Configuration Examples for the Cisco uBR-MC3GX60V Cable Interface Line Card
Prerequisites for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
The Cisco uBR10012 universal broadband router must have two DOCSIS Timing, Communication and Control (DTCC) cards configured in the DOCSIS Timing Interface (DTI) mode to make the Cisco uBR-MC3GX60V cable interface line card work with an Edge QAM (EQAM) device.
Table 1 lists the general compatibility prerequisites for the Cisco uBR-MC3GX60V cable interface line card.
Restrictions for Configuring the Cisco uBR-MC3GX60V Cable Interface Line Card
•
The MAC domains on the Cisco uBR-MC3GX60V line card cannot include downstream channels from other cable interface line cards.
•
Downstream bonding groups can include only channels from a single modular-cable controller.
•
The Downstream External PHY Interface (DEPI) control plane and Manual DEPI features cannot be configured on the same Cisco uBR-MC3GX60V line card.
•
High Availability for Cisco Wideband SPA with Cisco uBR-MC3GX60V line card is not supported.
•
If Cisco uBR10-MC5X20 line card is used as working line card and Cisco uBR-MC3GX60V line card used as protect line card, the HCCP feature is not supported when the working line card is replaced (using Online Insertion and Removal (OIR)) with a Cisco uBR-MC3GX60V line card.
Information About the Cisco uBR-MC3GX60V Cable Interface Line Card
With 72 downstream and 60 upstream channels, the Cisco uBR-MC3GX60V line card supports 9 service groups (SGs) for 8-channel downstream bonding, and 18 SGs for 4-channel downstream bonding. This line card can provide up to 72 SGs of 8 downstreams for a Cisco uBR10012 router. A larger number of SGs may be supported when downstream channels are shared between MAC domains.
The Cisco uBR-MC3GX60V cable line card has 4 connector inputs and 12 PHY receivers. The upstream channel-to-physical connector assignment is flexible enough to provide any combination of 1 to 12 channels per connector from the 4-connector bundle. This means four separate connectors could provide three US channels each, or two of the four connectors could provide six US channels each, and so on.
Note
The Cisco uBR-MC3GX60V line card supports the same number of cable modems and other devices as those supported on other M-CMTS and I-CMTS line cards, on Cisco uBR10012 routers.
The Cisco uBR10012 chassis with the Cisco uBR-MC3GX60V line card offers high density downstream solutions for IP Video over DOCSIS (VDOC) and cable high speed data (HSD) applications.
The Cisco uBR10012 router can include:
•
Up to eight Cisco uBR-MC3GX60V line cards and up to six Cisco Wideband SPAs, or both
•
A mix of older line cards and up to six Cisco Wideband SPAs, or both
•
Cisco uBR-MC3GX60V line card must use PRE4 with SIP-600
•
Dual DTCCs are required even when connected to a single DTI server
The Cisco uBR-MC3GX60V line card offers high availability through:
•
N+1 redundancy for the Cisco uBR-MC3GX60V line card. A Cisco uBR-MC3GX60V can serve as a protect line card for up to seven Cisco uBR-MC3GX60V line cards.
Note
Starting with Cisco IOS Release 12.2(33)SCE1, N+1 redundancy feature including DEPI redundancy is supported on the Cisco uBR-MC3GX60V cable interface line card.
•
External RF switch for upstream connectivity.
•
DEPI Path Redundancy (DPR) for M-CMTS interfaces:
–
A protocol solution that allows for redundant DEPI connections in N+1 redundancy.
–
Minimal packet loss during failovers.
•
PRE redundancy.
•
Six Gigabit Ethernet (GigE) small form-factor pluggable (SFP) ports, organized in three pairs for 1+1 network connectivity redundancy.
Note
The GigE ports on the Cisco uBR-MC3GX60V line card support only Layer 2 CIN routing protocols.
Effective with Cisco IOS Release 12.2(33)SCG, you can configure the MAC domain to include the SPA cards and the Cisco uBR-MC3GX60V line card.
In a scenario, where 6 SPA cards and a single Cisco uBR-MC3GX60V line card are present in a chassis, 6 SPA rf-channels and 3 controller rf-channel can be configured as primary channels in a single MAC domain. However, we recommend that not more than 3 primary rf-channel controllers are configured in one MAC domain on the Cisco uBR-MC3GX60V line card.
Effective with Cisco IOS Release 12.2(33)SCG1, the Cisco uBR-MC3GX60V line card and up to five shared port adapters (SPAs) can be configured to the same LBG. You can:
•
Include all the downstreams and upstreams of the SPA cards and the Cisco uBR-MC3GX60V line card in the LBG.
•
Configure the fiber-node to include all the downstreams and upstreams of the SPA cards and the Cisco uBR-MC3GX60V line card.
Figure 1 shows the Cisco uBR-MC3GX60V cable interface line card faceplate.
Figure 1 Cisco uBR-MC3GX60V Cable Interface Line Card Faceplate
Downstream Sharing Between the Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA
Starting with Cisco IOS Release 12.2(33)SCG, MAC domains hosted on the Cisco uBR-MC3GX60V cable interface line card can include downstream channels from the Cisco Wideband SPAs. Each Cisco uBR-MC3GX60V line card, together with the Cisco Wideband SPA, can now support up to 96 downstream channels. With this increased downstream capacity, Cisco uBR10012 router supports more number of CMs.
The Cisco uBR-MC3GX60V line card and the Cisco Wideband SPA downstream sharing is supported on the Cisco CMTS through:
•
The Cisco Wideband SPA downstreams that are included on the same fiber node as the Cisco uBR-MC3GX60V downstreams and upstreams.
•
Any upstream channel of the Cisco uBR-MC3GX60V line card that is bonded with any wideband SPA downstream channel.
•
A maximum of eight Cisco uBR-MC3GX60V line cards and six Cisco Wideband SPAs that are supported on a single chassis.
•
The Cisco uBR-MC3GX60V line card that serves as the modular host for the Cisco Wideband SPA.
•
The Hot-Standby Connection-to-Connection Protocol (HCCP) N+1 Redundancy that is supported for Cisco uBR-MC3GX60V line card with the Cisco Wideband SPA.
For more information on how to configure the Cisco uBR-MC3GX60V line card with the Cisco Wideband SPA, see "Configuring a Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card" section.
For more information on configuring the Cisco Wideband SPA, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration guide.
Onboard Failure Logging
The On-Board Failure Logging (OBFL) feature enables storage and collection of critical failure information in the non-volatile memory of a Field Replaceable Unit (FRU), like a route processor (RP) or line card. The Cisco uBR-MC3GX60V cable interface line card has 2 MB of non-volatile storage dedicated for OBFL use.
The OBFL stored data assists in understanding and debugging field failures on Return Material Authorization (RMA) of a RP or line card at repair and failure analysis sites.
OBFL records operating temperatures, voltages, hardware uptime, and any other important events that assist onboard diagnosis in case of hardware failures.
For more information about the feature, see the Onboard Failure Logging feature guide located at the following URL:
http://www.cisco.com/en/US/docs/ios/12_2sx/12_2sxh/feature/guide/sxhobfl.html#wp1053048.
Note
The sample output documented in the Onboard Failure Logging feature guide might slightly vary for Cisco CMTS routers.
How to Configure the Cisco uBR-MC3GX60V Cable Interface Line Card
This section describes the steps for configuring the Cisco uBR-MC3GX60V line card at startup. These procedures provide only the initial, basic configuration for the line card.
The Cisco uBR10012 universal broadband router should be operational before beginning the following procedures to configure the Cisco uBR-MC3GX60V cable interface line card:
•
Configuring the Modular Cable Controller on the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Configuring the Modular Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Configuring the Wideband Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
•
Configuring the RF Plant Topology on the Cisco uBR-MC3GX60V Cable Interface Line Card
Note
For Annex A and 256 QAM, each Cisco uBR-MC3GX60V supports up to 54 RF channels (18 channels on every controller) at full rate and up to 72 RF channels (24 channels on every controller) at less than full rate. For all other cases, the Cisco uBR-MC3GX60V supports up to 72 RF channels.
Configuring the Modular Cable Controller on the Cisco uBR-MC3GX60V Cable Interface Line Card
The downstream modular cable controller configuration defines Layer 1 and Layer 2 parameters for specific downstream RF channels, and certain configuration parameters for the GigE port.
Note
Modular cable controllers can be configured in one of the two mutually exclusive modes—Manual DEPI or DEPI Control Plane. For information on configuring these modes, see Configuring the DEPI Control Plane on the Cisco uBR-MC3GX60V Cable Interface Line Card and Configuring Manual DEPI on the Cisco uBR-MC3GX60V Cable Interface Line Card.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
controller modular-cable slot/subslot/controller
4.
(Optional step) rf-channel rf-port cable downstream channel-id channel-id
5.
rf-channel rf-port frequency [freq | none] [annex {A | B} modulation {64 | 256} [interleave-depth {8 | 12 | 16 | 32 | 64 | 128}]]
6.
rf-channel rf-port ip-address ip-address mac-address mac-address depi-remote-id session-id
7.
no rf-channel rf-port rf-shutdown
8.
end
DETAILED STEPS
Examples
The following example shows how to configure the RF channel on a modular cable controller:
Router# enableRouter# configure terminalRouter(config)# controller Modular-Cable 6/1/0Router(config-controller)# rf-channel 0 cable downstream channel-id 1Router(config-controller)# rf-channel 0 frequency 567000000 annex B modulation 256qam interleave 32Router(config-controller)# rf-channel 0 ip-address 17.30.4.100 mac-address 0022.9084.4cbf depi-remote-id 3000Router(config-controller)# rf-channel 1 cable downstream channel-id 2Router(config-controller)# rf-channel 1 frequency 573000000 annex B modulation 256qam interleave 32Router(config-controller)# rf-channel 1 ip-address 17.30.4.100 mac-address 0022.9084.4cbf depi-remote-id 3001Router(config-controller)# no rf-channel 0 rf-shutdownTroubleshooting Tips
•
Run the show controllers modular-cable slot/subslot/controller command to view the modular cable controller configuration details.
Note
The show controllers modular-cable command for the Cisco uBR- MC3GX60V line card has a number of subcommands. Run the following command to view all the subcommands:
Router# show controllers modular-Cable slot/subslot/controller ?•
The following error may be displayed when you run the no rf-channel 0 rf-shutdown command:
%ERROR: Cannot unshut channel 0, please upgrade linecard license and retryThis error is displayed to indicate that there are insufficient licenses for the line card to unshut additional channels. You must either upgrade the license or shut down an unshut channel.
Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card
For complete information on this section, see Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card.
Configuring a Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
The cable interface is the MAC domain interface that hosts modular cable interfaces and associates upstream channels with the modular cable interfaces.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface cable slot/subslot/cable-interface-index
4.
cable bundle bundle-number
5.
downstream modular-cable slot/subslot/controller rf-channel grouplist upstream grouplist
6.
cable upstream n frequency up-freq-hz
7.
cable upstream max-ports n
8.
cable upstream upstream-channel connector physical-port
9.
cable upstream n docsis-mode {atdma | scdma | tdma | tdma-atdma}
10.
cable upstream n channel-width first-choice-width [last-choice-width]
11.
cable upstream n minislot-size size
12.
cable upstream n range-backoff {automatic | start end}
13.
cable upstream n modulation-profile primary-profile-number [secondary-profile-number] [tertiary-profile-number]
14.
no cable upstream n shutdown
15.
end
DETAILED STEPS
Examples
The following example shows how to configure a cable interface:
Router> enableRouter# configure terminalRouter(config)# interface cable 7/0/0Router(config-if)# cable bundle 2Router(config-if)# downstream modular-cable 7/0/0 rf-channel 0Router(config-if)# cable upstream 2 frequency 25000000Router(config-if)# cable upstream max-ports 4Router(config-if)# cable upstream 2 connector 0Router(config-if)# cable upstream 2 docsis-mode tdmaRouter(config-if)# cable upstream 2 channel-width 1600000 1600000eRouter(config-if)# cable upstream 2 minislot-size 4Router(config-if)# cable upstream 2 range-backoff 3 6Router(config-if)# cable upstream 2 modulation-profile 21Router(config-if)# no cable upstream 0 shutdownTroubleshooting Tips
Run the show cable mac-domain cable slot/subslot/port cgd-associations command to view a summary of the Channel Grouping Domain (CGD) associations for all cable MAC domains.
The following error may be displayed when you run the no cable upstream n shutdown:
Router(config-if)# no cable upstream 3 shutdown%ERROR: Cannot unshut channel 3 on Cable7/0/0, please upgrade linecard license and retryThis error is displayed to indicate that there are insufficient licenses for the line card to unshut additional channels. You must either upgrade the license or shut down an unshut channel.
Note
For information on logical channels, see S-CDMA and Logical Channel Support on the Cisco CMTS Routers feature guide on Cisco.com.
Configuring the Modular Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
A modular cable interface forwards non-bonded traffic in the downstream direction. By default, this interface is allocated the bandwidth from the RF channel where it is configured.
The modular cable interfaces on slots 1 and 3 are only for SPAs. The modular cable interface for the Cisco uBR-MC3GX60V line card is restricted to slots 5 through 8.
Note
The SPA and Cisco uBR-MC3GX60V line card modular cable interfaces are created independently of each other.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface modular-cable slot/subslot/controller:rf-channel
4.
cable rf-bandwidth-percent percent-value [remaining ratio excess-value]
5.
end
DETAILED STEPS
Examples
The following example shows how to configure a modular cable interface on the Cisco uBR-MC3GX60V line card:
Router> enableRouter# configure terminalRouter(config)# interface modular-cable 7/0/0:0Router(config-if)# cable rf-bandwidth-percent 96Router(config-if)# cable bundle 1Troubleshooting Tips
Run the show interfaces modular-cable slot/subslot/controller:rf-channel command to view the modular cable configuration details.
Configuring the Wideband Cable Interface on the Cisco uBR-MC3GX60V Cable Interface Line Card
A wideband (WB) cable interface forwards bonded traffic in the downstream direction. A set of RF channels is configured under the wideband cable interface. The Cisco uBR-MC3GX60V has 3 downstream controllers and 32 bonded channels per controller with a maximum of 24 RF channels in a bonding group. The 24 RF channels must be on the same controller.
Restrictions
Wideband channels can be formed only from the downstream RF channels belonging to a single controller.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface wideband-cable slot/subslot/controller:bonded-channel
4.
cable bundle bundle-id
5.
cable rf-channel rf-channel bandwidth-percent bw-percent
6.
cable bonding-group-secondary
7.
end
DETAILED STEPS
Examples
The following example shows how to configure the wideband cable interface on the Cisco uBR-MC3GX60V line card:
Router> enableRouter# configure terminalRouter(config)# interface wideband-cable 7/1/0:0Router(config-if)# cable bundle 1Router(config-if)# cable rf-channel 0 bandwidth-percent 25Router(config-if)# cable rf-channel 1 bandwidth-percent 25Router(config-if)# cable rf-channel 2 bandwidth-percent 25Router(config-if)# cable rf-channel 3 bandwidth-percent 25Troubleshooting Tips
•
Run the show interfaces wideband-cable slot/subslot/controller:bonded-channel command to view the entire configuration of the bandwidth allocation between WB channels and RF channels.
•
Run the show controllers modular-cable [association | config | mapping] command to verify whether a wideband channel is configured correctly.
Configuring the RF Plant Topology on the Cisco uBR-MC3GX60V Cable Interface Line Card
You must configure the Hybrid Fiber-Coaxial (HFC) plant topology on the Cisco uBR-MC3GX60V cable interface line card to enable DOCSIS 3.0 operation and effective upstream spectrum management. The HCF plant topology configuration is achieved by associating upstream connectors and downstream channels with HFC service group units called fiber nodes.
Prerequisites
To ensure validity of the fiber-node configuration:
•
All downstream channels in a fiber node should have a unique frequency and a downstream channel ID.
•
All downstream channels in a fiber node should belong to the same bundle.
•
All upstream channels in a fiber node must have a distinct frequency.
For details about the fiber-node configuration, see the Cable Best Practices for the uBR10012 document at Cisco.com.
Restrictions
•
The Cisco uBR-MC3GX60V line card supports 60 upstream channels mapped to 20 upstream connectors. Therefore, any connector has multiple upstream channels mapped to it.
•
The Cisco uBR-MC3GX60V line card does not create a corresponding DOCSIS 3.0 general load balancing group (GLBG) on a fiber-node configuration that includes any channel from any other line card.
In a fiber-node configuration, you can either add a restricted load balancing group (RLBG) or a DOCSIS 2.0 GLBG to contain the channels of the Cisco uBR-MC3GX60V line card for load balancing features.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
cable fiber-node fiber-node-id
4.
downstream modular-cable downstream slot/downstream subslot/controller rf-channel grouplist
5.
upstream cable slot/subslot connector physical-port
6.
end
DETAILED STEPS
Examples
The following example shows how to configure the fiber node on the Cisco uBR-MC3GX60V line card:
Router> enableRouter# configure terminalRouter(config-if)# cable fiber-node 1Router(config-if)# downstream modular-cable 6/1/0 rf-channel 3Router(config-if)# upstream Cable 6/1 connector 3Troubleshooting Tips
Run the show cable fiber-node command to list all channels associated with the fiber node and to indicate if the fiber node is valid.
Configuring Redundancy on the Cisco uBR-MC3GX60V Cable Interface Line Card
There are two levels of redundancy for the Cisco uBR-MC3GX60V line card:
•
Port-level redundancy—This redundancy is provided by the Gigabit Ethernet (GigE) ports on the Cisco uBR-MC3GX60V line card. For more information, see Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card.
•
Line-card redundancy—The line-card redundancy provides the following kinds of redundancy:
–
The upstream traffic redundancy is provided by the Global HCCP N+1 Redundancy. For more information, see Configuring Global HCCP N+1 Line Card Redundancy on the Cisco uBR10012 Router.
–
The downstream traffic redundancy is provided by manual DEPI and control plane DEPI. For more information, see Configuring the DEPI Control Plane on the Cisco uBR-MC3GX60V Cable Interface Line Card and Configuring Manual DEPI on the Cisco uBR-MC3GX60V Cable Interface Line Card.
Configuring the GigE Interface for Downstream on the Cisco uBR-MC3GX60V Cable Interface Line Card
The Cisco uBR-MC3GX60V line card supports six (3 + 3) GigE links that connect to the Cisco RF Gateway. The links are arranged in three sets of redundant pairs.
The links in the pair are modeled as an active-passive GigE pair and traffic can be quickly switched from the working GigE link to the standby GigE link in the pair.
The three active GigE links are numbered as slot/subslot/0, 2, 4 and are mapped to the modular controllers slot/subslot/0, 1, 2 respectively. You are not required to configure the passive GigE links.
During the initialization of the Cisco uBR-MC3GX60V line card, the following are created:
•
Three GigE interfaces
•
Three modular cable controllers
•
24 x 3 modular cable interfaces
Each GigE pair is assigned as:
•
Gige {0, 1} - GigE interface 0 = Modular cable controller {0}; 0 to 23 channels; 0 to 31 bonding groups
•
Gige {2, 3} - GigE interface 2 = Modular cable controller {1}; 24 to 47 channels; 32 to 63 bonding groups
•
Gige {4, 5} - GigE interface 4 = Modular cable controller {2}; 48 to 71 channels; 64 to 95 bonding groups
Prerequisites
The Cisco uBR-MC3GX60V cable interface line card supports the following types of SFPs transceivers:
Restrictions
Due to slow link loss detection, we do not recommend using the SFP-GE-T transceivers for primary interfaces.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
interface gigabitEthernet slot/subslot/port
4.
ip address [ip | dhcp | pool] IP subnet mask
5.
negotiation auto
6.
output-rate output-rate
7.
end
DETAILED STEPS
Examples
The following example shows how to configure the GigE interface on the Cisco uBR-MC3GX60V line card:
Router> enableRouter(config)# interface gigabitEthernet 8/1/0Router(config-if)# ip address 10.30.4.1 255.255.0.0Router(config-if)# negotiation autoRouter(config-if)# output-rate 100Router(config-if)# endTroubleshooting Tips
•
Run the show interfaces gigabitEthernet slot/subslot/port command to view the GigE interface configuration details.
•
Run the show controller command to display link status of the primary and secondary ports and other information.
Configuring Global HCCP N+1 Line Card Redundancy on the Cisco uBR10012 Router
Note
Starting with Cisco IOS Release 12.2(33)SCE1, N+1 redundancy feature including DEPI redundancy is supported on the Cisco uBR-MC3GX60V cable interface line card.
N+1 redundancy refers to (N) cable interface line cards, referred to as working line cards that are protected by an additional line card (+1), referred to as the protect line card.
Note
In the Cisco uBR10012 routers, the value of N can be between one and seven Cisco uBR-MC3GX60V line cards. An additional Cisco uBR-MC3GX60V protect line card can provide the redundant backup for the other Cisco uBR-MC3GX60V working cards in the HCCP group.
N+1 redundancy provides synchronization between the HCCP working interface configurations and those configurations that are inherited during the switchover to the HCCP protect interfaces. This makes the configuration of the HCCP working and protect interfaces easier and the switchover times faster.
For more information, see the N+1 Redundancy for the Cisco Cable Modem Termination System feature guide.
Prerequisites
•
Configure the RF switch name, using the rf-switch name line card redundancy configuration command, and the RF switch IP addresses before configuring the line card redundancy.
•
Configure the downstream physical connectivity using the Ethernet switch with VLANs to ensure that the Cisco RF Gateway receives downstream traffic through the protect line card Ethernet ports.
•
Ensure that the HCCP group configuration specifies the working and protect line cards, preconfiguration source line card, and the RF switch slot numbers.
•
When using the DEPI control plane, ensure that the DEPI backup sessions (secondary sessions) are established. When using the manual DEPI, ensure that the GigE link is functioning on the protect line card.
Restrictions
•
HCCP N+1 redundancy is not supported between different generations of line cards. That is, an HCCP group can consist of either M-CMTS based line cards (Cisco uBR-MC3GX60V line cards) or I-CMTS based line cards (Cisco uBR10-MC5X20 line cards or Cisco UBR-MC20X20V) to work in a redundant mode. The Cisco uBR10-MC5X20, Cisco UBR-MC20X20V, and Cisco uBR-MC3GX60V cards can coexist in the same chassis but only one group of line cards is allowed to have the redundancy configuration; that is, either integrated line cards or modular line cards.
•
For a DEPI control plane connecting to a Cisco RF Gateway that does not support DEPI path redundancy (DPR), the modems go offline during the line card switchover. Because no valid backup sessions are available, new sessions are not re-established.
Note
If your Cisco RF Gateway does not support DEPI control plane DPR, use the manual DEPI N+1 redundancy.
•
The license on the protect line card should be a superset of the license on all working line cards.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip host rf-sw1 ip_addr
4.
ip host rf-sw2 ip_addr
5.
redundancy
6.
linecard-group linecard-group identifier y-cable
7.
member subslot slot/subslot working [rfsw-slot]
8.
member subslot slot/subslot protect [slot/subslot | rf-power]
9.
end
10.
write memory
DETAILED STEPS
Examples
The following is the sample output from the show running configuration command that displays the N+1 redundancy scheme configured on the Cisco uBR10012 universal broadband router with two Cisco RF switches:
Router# show running-config...ip host rfsw-1 10.4.4.1ip host rfsw-2 10.4.4.2redundancymain-cpuauto-sync standardlinecard-group 1 cablerf-switch name 1 rf-switch-1rf-switch name 2 rf-switch-2rf-switch snmp-community private123member subslot 6/1 workingmember subslot 5/1 protectmember subslot 8/0 working...Configuring the DEPI Control Plane on the Cisco uBR-MC3GX60V Cable Interface Line Card
The Cisco CMTS supports an N+1 DEPI redundancy to protect against the Cisco uBR-MC3GX60V cable line card failures and switchovers. In the redundancy mode, the protect line card establishes a backup DEPI session. The primary DEPI control connection and session is established on the GigE ports of the working line card. The two DEPI sessions are paired through the common transport stream identifier (TSID).
Note
The network connectivity must be set up to reach the Cisco RF Gateway through the protect Cisco uBR-MC3GX60V line card.
In an N+1 line card redundancy, the protect line card initiates a DEPI control session to the RF Gateway channels during bootup. When the protect line card detects a line card failure, it enables all sessions of the failed line card. If there are multiple line cards with sessions to the same RF Gateway, the protect line card has a control connection and multiple corresponding secondary data sessions within it. The Cisco CMTS associates the primary and secondary sessions using the TSID, which has matching values for the corresponding primary and secondary sessions.
For more information, see the M-CMTS DEPI Control Plane feature guide at Cisco.com.
Prerequisites
•
The GigE interfaces corresponding to modular controllers should have their source IP addresses configured.
•
The PHY parameters (frequency, annex, modulation, and interleave) for the RF channel should be configured through the rf-channel x frequency yyy000000 annex B modulation xxx interleave xx command.
Restrictions
•
Only six DEPI-tunnel classes are allowed per controller.
•
Common Layer 2 Transmission Protocol (L2TP) class configuration for all working controllers are associated with one protect controller.
•
Modems will fall offline during the cable line card switchover, if the Cisco RF Gateway does not support DPR.
•
UDP port option is not supported on the Cisco uBR-MC3GX60V cable line card.
•
Failure detection time through the control plane is limited by the HELLO interval in L2TP class. To achieve fast failure detection, set the L2TP hello timeout to 1. The default L2TP hello timeout is 60 seconds. The recommended L2TP hello timeout is 30 seconds.
Note
If the standby line card DEPI sessions are the superset of the active line card, Control Plane DEPI can detect downstream failure through the hello timeout and trigger a line card switchover.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
l2tp-class l2tp-class-name
4.
hello seconds
5.
retransmit retries max retransmissions
6.
retransmit timeout [max | min] retransmit timeout
7.
depi-class depi-classname
8.
mode mpt
9.
depi-tunnel protect-tunnel-name
10.
dest-ip ip address
11.
depi-tunnel working-tunnel-name
12.
dest-ip ip address
13.
protect-tunnel protect-tunnel-name
14.
l2tp-class l2tp-class-name
15.
depi-class depi-class-name
16.
controller Modular-Cable slot/subslot/port
17.
rf-channel rf-channel-num depi-tunnel working-tunnel-name tsid tsid
18.
no rf-channel rf-port rf-shutdown
19.
end
DETAILED STEPS
Examples
The following example shows how to configure the GigE interface DEPI control plane on the Cisco uBR-MC3GX60V line card:
Note
Before you begin the GigE interface configuration, ensure that the GigE interfaces are configured with an IP address by running these commands:
Router(config)# interface GigabitEthernet 8/0/0Router(config-if)# ip address 1.30.3.1 255.255.255.0Router(config)# interface GigabitEthernet 5/1/0Router(config-if)# ip address 1.30.9.1 255.255.255.0Router> enableRouter# configure terminalRouter(config)# l2tp-class depi_l2tp_classRouter(config-l2tp-class)# hello 1Router(config-l2tp-class)# retransmit retries 5Router(config-l2tp-class)# retransmit timeout max 1Router(config-l2tp-class)# exitRouter(config)# depi-class depi_mpt_class
Router(config-depi-class)# mode mpt
Router(config-depi-class)# depi-tunnel depi_protect_tunnel_5_1_0
Router(config-depi-class)# dest-ip 1.30.9.100Router(config-depi-class)# depi-tunnel depi_working_tunnel_8_0_0Router(config-depi-tunnel)# dest-ip 1.30.3.100Router(config-depi-tunnel)# protect-tunnel depi_protect_tunnel_5_1_0Router(config-depi-tunnel)# l2tp-class depi_l2tp_classRouter(config-depi-tunnel)# depi-class depi_mpt_classRouter(config-depi-tunnel)# controller modular-cable 8/0/0Router(config-controller)# rf-channel 0 depi-tunnel depi_working_tunnel_8_0_0 tsid 148Router(config-controller)# no rf-channel 0 rf-shutdownRouter(config-controller)# endTroubleshooting Tips
Run the show depi, show depi session endpoints (for the DEPI session status), and show depi tunnel endpoints (for the DEPI tunnel status) commands to view the DEPI session details.
Each of the four QAMs on an RF Gateway port must have the same RF power level and a contiguous frequency range. A configuration that does not meet these conditions is rejected by the RF Gateway.
On the Cisco CMTS side, this rejection results in intermittent connectivity problems or flapping of the DEPI sessions. The mismatch in RF power level or frequency mismatch are displayed in the Reason field in the show depi session configured output
Router# show depi session configuredSession Name State Reason TimeModular-Cable8/0/0:0 IDLE QC RF Power mismatch Sep 19 18:49:42To resolve this issue, align the RF power for the QAMs to be the same value or align the frequency for the QAMs so they have a contiguous range, or do both.
You can run the following commands:
•
rf-channel rf-port rf-power power-level
•
rf-channel x frequency yyy000000 annex A | B modulation xxx qam interleave xx
Configuring Manual DEPI on the Cisco uBR-MC3GX60V Cable Interface Line Card
The manual DEPI configuration also supports N+1 DEPI redundancy and port-level redundancy on the Cisco uBR-MC3GX60V line card. In manual DEPI configuration, you do not have to configure the protect tunnel. The working card configuration is automatically applied to the protect card through IPC messages.
The DEPI connection between the M-CMTS router and the EQAM is static in manual DEPI configuration. Data sessions are not established dynamically in manual DEPI configuration.
For more information, see the M-CMTS DEPI Control Plane feature guide at Cisco.com.
Prerequisites
•
EQAM IP address and the MAC address must be specified.
•
The EQAM must support L2TPv3.
Restrictions
Manual DEPI or control plane DEPI must be used for an entire Cisco uBR-MC3GX60V cable line card. That is, you must not configure manual DEPI for one controller and control plane DEPI for another controller on the same Cisco uBR-MC3GX60V cable line card; they must all be either one or the other on the same Cisco uBR-MC3GX60V cable line card.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
redundancy
4.
linecard-group linecard-groupId y-cable
5.
member subslot slot/subslot working
6.
member subslot slot/subslot protect
7.
controller Modular-Cable slot/subslot/port
8.
rf-channel rf-port cable downstream channel-id channel-id
9.
rf-channel rf-port frequency [freq | none] [annex {A | B} modulation {64 | 256} [interleave-depth {8 | 12 | 16 | 32 | 64 | 128}]]
10.
rf-channel rf-port ip-address ip-address mac-address mac-address depi-remote-id session-id
11.
end
Note
Steps 3 to 6 are applicable only if line card redundancy is supported.
DETAILED STEPS
Example
The following example shows how to configure Manual DEPI on the Cisco uBR-MC3GX60V line card:
Router> enableRouter# configure terminalRouter(config)# redundancyRouter(config-red)# linecard-group 1 y-cableRouter(config-red-lc)# member subslot 5/0 workingRouter(config-red-lc)# member subslot 6/0 protectRouter(config-red-lc)# controller modular-cable 8/0/0Router(config-controller)# rf-channel 0 cable downstream channel-id 1Router(config-controller)# rf-channel 0 frequency 453000000 annex B modulation 256qam interleave-depth 32Router(config-controller)# rf-channel 0 ip-address 192.168.100.20 mac-address 0090.f001.930c depi-remote-id 3001Router(config-if)# endTroubleshooting Tips
Run show controllers modular-cable rf-channel to display the manual DEPI settings for the given controller.
Monitoring and Maintaining the Cisco uBR-MC3GX60V Cable Interface Line Card
The following sections describe the show commands that provide more information about the Cisco uBR-MC3GX60V cable interface line card:
•
Viewing the Cisco uBR-MC3GX60V Cable Interface Line Card Statistics
•
Viewing Information About the Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA Downstream Sharing
•
Viewing Information About the Interface Controllers
•
Viewing Information About the Cable Modems
Viewing the Cisco uBR-MC3GX60V Cable Interface Line Card Statistics
To view information about the Cisco uBR-MC3GX60V line card statistics, use the show controller modular-cable command in privileged EXEC mode.
This command allows the user to view the following line card statistics:
•
Interface association
•
JIB hardware downstream configuration
•
Channel counters
•
Errors
•
Mapping of wideband and RF channels
•
JIB hardware downstream registers
•
JIB hardware downstream status
The following example shows a typical display for the show controllers modular-cable command:
Router# show controllers modular-cable 5/1/0 all
Modular Cable Controller 5/1/0:----------------------------------Channel 1 Annex = B Modulation = 64 QAMChannel 2 Annex = B Modulation = 64 QAMSync Configuration:-------------------Jib3-DS Device Information:---------------------------Jib3-DS Version = 2.2.1.11SW Rev ID = 0x00020002 HW Rev ID = 0x0001000BDevice Type: UnknownDriver State: 3Device Object Address: 0x20112190Ironbus Base Channel: 0xC02Channel Resources:------------------Total Non-bonded Channels..........= 72Per-Controller Non-bonded Channels = 24Total Bonded Channels..............= 96Per-Controller Bonded Channels.....= 32Slot-Wide Resources:--------------------Number of PHS Rules...........= 12K (0x3000)Number of BPI Table Entries...= 24K (0x6000)Number of Service Flows.......= 64K (0x10000)Jib3-DS Status:---------------Rx SPI..............: OKTx SPI..............: OKDCM Status..........: OKERP Status..........: OKDOCSIS RLDRAM Status: OKQM RLDRAM Status....: OKBPI Error Counters:-------------------Bad Input Pkts = 0 Single-bit ECC Errors = 0Bad Output Pkts = 0PLL events: PLL 1 LD: 0000 PLL 2 LD: 0000 PLL 3 LD: 0000Low Fa/Fl/Cp/Sa 0001 0000 0000 0000Low Misc 0000The following example shows a typical display for the show controllers modular-cable command with counters keyword:router# show controllers Modular-Cable 6/0/0 counters rf-channel 2Contr RF Pkts Bytes Pkts DMPT DMPT* Sync MAP/UCD Med PriChan Tx Tx Dropped Mbps pps Pkts Pkts PktsTx Tx Tx6/0/0 2 78689590 14818993216 0 0.895732 594 13273653 65283559 135133Total: 78689590 14818993216 0 0.895732 594 13273653 65283559 135133* Does not include DEPI control plane or DLM packets.router#Viewing Information About the Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA Downstream Sharing
To view information about the Cisco uBR-MC3GX60V line card and the Cisco Wideband SPA downstream sharing, use the following commands in privileged EXEC mode:
•
show cable cgd-associations
•
show cable mac-domain cable cgd-associations
•
show cable mac-domain cable downstream-service-group
•
show controllers cable downstream
•
show controllers cable upstream
•
show pxf cpu queue WB-SPA
•
show pxf cpu statistics queue [OCQ | high Flowoff | low Flowoff]
For a complete description of the above show commands, see the Cisco IOS CMTSCable Command Reference Guide on Cisco.com.
Examples
The following example is a sample output of the show cable cgd-associations command:
Router# show cable cgd-associationsCGD Host Resource DS Channels Upstreams (AllUS) Active Remote DSCa7/1/0 7/1/0 4 0-3 Yes4
Note
In the AllUS field, Yes indicates all upstream channels are associated with downstream channels in the MAC domain. If the AllUS field is blank, all upstream channels are not associated with downstream channels.
The following example is a sample output of the show cable mac-domain cable cgd-associations command:
Router# show cable mac-domain cable 8/0/0 cgd-associationsCGD Host Resource DS Channels Upstreams (AllUS) Active Remote DSCa8/0/0 1/1/0 0 0-3 YesThe following example is a sample output of the show cable mac-domain cable downstream-service-group command:Router# show cable mac-domain cable 8/0/0 downstream-service-groupCable MD-DS-SG RFIF Id Resource Chan Primary ChanC8/0/0 1 1/1/0 00-03 01/3/0 00-037/0/0 00-038/0/2 00-03The following example is a sample output of the show controllers cable downstream command:Router# show controllers cable 8/0/0 downstreamDynamic Services Stats (All Downstreams):DSA: 0 REQs 0 RSPs 0 ACKs0 Successful DSAs 0 DSA FailuresDSC: 0 REQs 0 RSPs 0 ACKs0 Successful DSCs 0 DSC FailuresDSD: 0 REQs 29 RSPs0 Successful DSDs 0 DSD FailuresDBC: 0 REQs 96 RSPs(Rcvd) 0 ACKs0 Successful DBCs 0 DBC Failures 0 DBC Partial96 DBC Protocol Violations0 Total DBC Pending Q-SizeDCC: 0 REQs 0 RSPs 0 ACKs0 Successful DCCs 0 DCC Failures0 DCC Departs 0 DCC ArrivesDCC end of transaction counts:DCC unknown cause(0) offline(0) if down(0) no cm(0)DCC no resource(0) no retries(0) reject(0) unknown state (0)DCC rebuild err (0) T15 timeout(0) wrong channel(0) reinit MAC (0)DCC dcc succeeds(0)DCC wcm(0)CM STATUS Stats:0 invalid_event 4 tlv_error0 disabled_event 598985 invalid_state0 invalid_chid 0 prim_chidLocal total modems 0, modems active 0, total DS flows 3NB DS Mo1/1/0:0, STATE: UPFrequency 699.0000 MHz 256-QAM, ANNEX B, R/S Interleave I=32, J=4Network Delay 550 (usec)Bandwidth (Kbps): 6000, Load Percent: 0Channel ID: 5, US MAP: 0x000FTotal modems: 51, modems active : 37, total DS flows: 158DS_chan_id RFID Interface--------------------------------------5 24 Mo1/1/0:0--------------------------------------MDDs Primary Non-Primary----------------------------------------------1/1/0:0 1148012 01/1/0:1 0 11480111/1/0:2 0 11480111/1/0:3 0 11480111/3/0:0 0 11480111/3/0:1 0 11480111/3/0:2 0 11480111/3/0:3 0 11480117/0/0:0 0 11480117/0/0:1 0 11480117/0/0:2 0 11480117/0/0:3 0 11480118/0/2:0 0 11480118/0/2:1 0 11480118/0/2:2 0 11480118/0/2:3 0 1148011----------------------------------------------The following example is a sample output of the show controllers cable upstream command:
Router# show controllers cable 8/0/0 upstreamCable8/0/0 Upstream 0 is upFrequency 15.000 MHz, Channel Width 0.800 MHz, Symbol Rate 0.640 MspsModulations (16-QAM) - Short 16-QAM, Long 16-QAMMapped to shared connector 0 and receiver 0Spectrum Group is overriddenUS phy MER(SNR)_estimate for good packets - 36.1280 dBNominal Input Power Level -4 dBmV, Tx Timing Offset 5734Ranging Backoff Start 3, Ranging Backoff End 6US timing offset adjustment type 0, value 0Ranging Insertion Interval automatic (60 ms)US throttling offTx Backoff Start 3, Tx Backoff End 5Modulation Profile Group 21Concatenation is enabledFragmentation is enabledpart_id=0x3142, rev_id=0xB1, rev2_id=0x00nb_agc_thr=0x0000, nb_agc_nom=0x0000Range Load Reg Size=0x58Request Load Reg Size=0x0EMinislot Size in number of Timebase Ticks is = 8Minislot Size in Symbols = 32Bandwidth Requests = 0xC7957Piggyback Requests = 0x19899Invalid BW Requests= 0x4BFMinislots Requested= 0xF2E365Minislots Granted = 0xE240AMinislot Size in Bytes = 16Map Advance (Dynamic) : 3389 usecsMap Count Internal = 1134448325No MAP buffer= 0x0 No Remote MAP buffer= 0x0Map Counts: Controller 1/1/0 = 1134446105UCD Counts:Controller 1/1/0:0 = 1150386UCD procedures on lch 0UCD ucd-succeeds(2) ucd-shut(0) init-state-err(0)UCD init-tss-err(0) init-timeout(0) init-start-err(0)UCD ucd-ccc-time(0) ucd-timeout(0) ucd-tss-err(0)UCD ucd-state-err(0) ucd-process(0) ucd-retries(0)UCD stale-tss(0)PHY: us errors 0 us recoveries 0 (enp 0)MAC PHY TSS: tss error start 0 tss error end 0MAC PHY Status: bcm3140 status 0 lookout status 0PHY: TSS late 0 discontinuous 0PHY: TSS mis-match 0 not-aligned 0PHY: TSS missed snapshots from phy 0MAP/UCD Replication Instructions:Controller 1/1/0 index = 361, bitmap = 0x0001Cable8/0/0 Upstream 1 is upFrequency 16.000 MHz, Channel Width 0.800 MHz, Symbol Rate 0.640 MspsModulations (16-QAM) - Short 16-QAM, Long 16-QAMMapped to shared connector 0 and receiver 1Spectrum Group is overriddenUS phy MER(SNR)_estimate for good packets - 36.1280 dBNominal Input Power Level -4 dBmV, Tx Timing Offset 2330Ranging Backoff Start 3, Ranging Backoff End 6US timing offset adjustment type 0, value 0Ranging Insertion Interval automatic (60 ms)US throttling offTx Backoff Start 3, Tx Backoff End 5Modulation Profile Group 21Concatenation is enabledFragmentation is enabledpart_id=0x3142, rev_id=0xB1, rev2_id=0x00nb_agc_thr=0x0000, nb_agc_nom=0x0000Range Load Reg Size=0x58Request Load Reg Size=0x0EMinislot Size in number of Timebase Ticks is = 8Minislot Size in Symbols = 32Bandwidth Requests = 0xC0BFFPiggyback Requests = 0x18BFBInvalid BW Requests= 0x1B248Minislots Requested= 0xE50E2AMinislots Granted = 0xDA909Minislot Size in Bytes = 16Map Advance (Dynamic) : 3057 usecsMap Count Internal = 1134268243No MAP buffer= 0x0 No Remote MAP buffer= 0x0Map Counts: Controller 1/1/0 = 1134266034UCD Counts:Controller 1/1/0:0 = 1150386UCD procedures on lch 0UCD ucd-succeeds(2) ucd-shut(0) init-state-err(0)UCD init-tss-err(0) init-timeout(0) init-start-err(0)UCD ucd-ccc-time(0) ucd-timeout(0) ucd-tss-err(0)UCD ucd-state-err(0) ucd-process(0) ucd-retries(0)UCD stale-tss(0)PHY: us errors 0 us recoveries 0 (enp 0)MAC PHY TSS: tss error start 0 tss error end 0MAC PHY Status: bcm3140 status 0 lookout status 0PHY: TSS late 0 discontinuous 0PHY: TSS mis-match 0 not-aligned 0PHY: TSS missed snapshots from phy 0MAP/UCD Replication Instructions:Controller 1/1/0 index = 362, bitmap = 0x0001Cable8/0/0 Upstream 2 is upFrequency 17.000 MHz, Channel Width 0.800 MHz, Symbol Rate 0.640 MspsModulations (16-QAM) - Short 16-QAM, Long 16-QAMMapped to shared connector 0 and receiver 2Spectrum Group is overriddenUS phy MER(SNR)_estimate for good packets - 36.1280 dBNominal Input Power Level -4 dBmV, Tx Timing Offset 5733Ranging Backoff Start 3, Ranging Backoff End 6US timing offset adjustment type 0, value 0Ranging Insertion Interval automatic (60 ms)US throttling offTx Backoff Start 3, Tx Backoff End 5Modulation Profile Group 21Concatenation is enabledFragmentation is enabledpart_id=0x3142, rev_id=0xB1, rev2_id=0x00nb_agc_thr=0x0000, nb_agc_nom=0x0000Range Load Reg Size=0x58Request Load Reg Size=0x0EMinislot Size in number of Timebase Ticks is = 8Minislot Size in Symbols = 32Bandwidth Requests = 0xAB0B1Piggyback Requests = 0x163A0Invalid BW Requests= 0x696Minislots Requested= 0xE32885Minislots Granted = 0xC260CMinislot Size in Bytes = 16Map Advance (Dynamic) : 3389 usecsMap Count Internal = 1134411867No MAP buffer= 0x0 No Remote MAP buffer= 0x0Map Counts: Controller 1/1/0 = 1134409666UCD Counts:Controller 1/1/0:0 = 1150386UCD procedures on lch 0UCD ucd-succeeds(2) ucd-shut(0) init-state-err(0)UCD init-tss-err(0) init-timeout(0) init-start-err(0)UCD ucd-ccc-time(0) ucd-timeout(0) ucd-tss-err(0)UCD ucd-state-err(0) ucd-process(0) ucd-retries(0)UCD stale-tss(0)PHY: us errors 0 us recoveries 0 (enp 0)MAC PHY TSS: tss error start 0 tss error end 0MAC PHY Status: bcm3140 status 0 lookout status 0PHY: TSS late 0 discontinuous 0PHY: TSS mis-match 0 not-aligned 0PHY: TSS missed snapshots from phy 0MAP/UCD Replication Instructions:Controller 1/1/0 index = 363, bitmap = 0x0001......The following example is a sample output of the show pxf cpu queue wb-spa command:
Router# show pxf cpu queue wb-spaSPA 1/1/0MAP/UCD and LP-MMM Flow (IronBus Channel: 0xC020):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)8 0/255 251121646 0 0 1/10000 0 32771 hi-pri131100 0/255 9634685 0 0 1/10000 0 32770 lo-priSPA 1/3/0MAP/UCD and LP-MMM Flow (IronBus Channel: 0xC030):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)66 0/255 0 0 0 1/10000 0 32775 hi-pri131216 0/255 4596528 0 0 1/10000 0 32774 lo-priFauna6/0Statistics and Cable Monitor Flow (IronBus Channel: 0x1FFF):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131441 0/255 0 0 0 1/240 0 205 defCableInternal6/0Statistics and Cable Monitor Flow (IronBus Channel: 0x7000):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)178 0/255 0 0 0 1/10000 0 32789 hi-pri131440 0/255 2303963 0 0 1/10000 0 32788 lo-pri131439 0/255 0 0 0 1/240 0 20 defCableInternal6/1Statistics and Cable Monitor Flow (IronBus Channel: 0x0500):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)185 0/255 0 0 0 1/10000 0 32791 hi-pri131454 0/255 2394164 0 0 1/10000 0 32790 lo-pri131453 0/255 0 0 0 1/240 0 21 defFauna7/0Statistics and Cable Monitor Flow (IronBus Channel: 0x1FFF):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131557 0/255 0 0 0 1/240 0 266 defCableInternal7/0Statistics and Cable Monitor Flow (IronBus Channel: 0x7000):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)236 0/255 4596556 0 0 1/10000 0 32793 hi-pri131556 0/255 2377280 0 0 1/10000 0 32792 lo-pri131555 0/255 0 0 0 1/240 0 22 defFauna8/0Statistics and Cable Monitor Flow (IronBus Channel: 0x1FFF):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)131903 0/255 0 0 0 1/240 0 453 defCableInternal8/0Statistics and Cable Monitor Flow (IronBus Channel: 0x7000):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)409 0/255 0 0 0 1/10000 0 32797 hi-pri131902 0/255 3350878 0 0 1/10000 0 32796 lo-pri131901 0/255 0 0 0 1/240 0 24 defFauna8/1Statistics and Cable Monitor Flow (IronBus Channel: 0x1FFF):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)132261 0/255 0 0 0 1/240 0 697 defCableInternal8/1Statistics and Cable Monitor Flow (IronBus Channel: 0x7000):QID Len/Max Dequeues TailDrops MinRt Wt/Quantum ShapeRt FlowId(Kbps) (Kbps)582 0/255 0 0 0 1/10000 0 32799 hi-pri132260 0/255 0 0 0 1/10000 0 32798 lo-pri132259 0/255 0 0 0 1/240 0 25 defThe following example is a sample output of the show pxf cpu statistics queue ocq command:
Router# show pxf cpu statistics queue ocqOCQ counter per resourceresource flowResource slot counter00 00 0x0 (0)01 01 to RP 0x0 (0)02 09 5/0 0x0 (0)03 08 5/1 0x0 (0)04 07 6/0 0x0 (0)05 06 6/1 0x0 (0)06 05 7/0 0x0 (0)07 04 7/1 0x0 (0)08 03 8/0 0x0 (0)09 02 8/1 0x0 (0)10 17 1/0 0x0 (0)11 16 1/1 0x0 (0)12 15 2/0 0x0 (0)13 14 2/1 0x0 (0)14 13 3/0 0x0 (0)15 12 3/1 0x0 (0)16 11 4/0 0x0 (0)17 10 4/1 0x0 (0)18 18 0x0 (0)19 19 0x0 (0)20 20 0x0 (0)21 21 0x0 (0)22 22 0x0 (0)23 23 0x0 (0)24 24 0x0 (0)25 25 0x0 (0)26 26 0x0 (0)27 27 0x0 (0)28 28 0x0 (0)29 29 0x0 (0)30 30 0x0 (0)31 31 0x0 (0)* slot to resource mapping may not accurate for none PRE4Viewing Information About the Interface Controllers
To view information about the interface controllers, use the following commands in privileged EXEC mode:
•
show controller cable slot/subslot/port
•
show interface cable slot/subslot/cable-interface-index
For a complete description of the above show commands, see the Cisco Broadband Cable Command Reference Guide on Cisco.com.
Examples
The following example shows a typical display for the show controller cable command:
Router# show controller cable 5/1/0Interface Cable5/1/0Hardware is MC3GX60VUpstream MAC Processor Powered by Jib3 Upstream FPGA ComplexJib3 Upstream FPGA is InitializedJib3US Initialization Error Code: 0Jib3US Initialization Status : No error at Startup InitJib3 Upstream FPGA InformationFluorine FPGA Rev ID = 0x00000001Fluorine FPGA HW Rev ID = 0x00000006Fauna FPGA Rev ID = 0x00000008Fauna FPGA HW Rev ID = 0x00000002Jib3US Hardware Flow State Info - Segment 0Bonded HwFlows Free = 32768Bonded HwFlows Used = 0Bonded HwFlows Wait = 0NonBonded HwFlows Free = 98304NonBonded HwFlows Used = 0NonBonded HwFlows Wait = 0-------------------------------Total Jib3US HwFlows = 131072Jib3US State = Active, Active Seg = 0, Clr Rldram Done = True, CCF Done=TrueHCCP HA FLAGS:linestate: TRUE hccp_if_inited: FALSE hccphopready: TRUEhccp_keepalive: FALSE hccp_critical: FALSE ha_critical: FALSEdrop_mac_msgs: FALSE current_active_segment: 0Cable5/1/0 JIB hardware status:JIB Upstream port 1 Enabled Bound to local = 0JIB Upstream port 2 Enabled Bound to local = 0JIB Upstream port 3 Enabled Bound to local = 0JIB Upstream port 4 Enabled Bound to local = 0The following example shows a typical display for the show interface cable command.
Router# show interface cable 5/1/0Cable5/1/0 is up, line protocol is upHardware is UBR10000 CLC, address is 0013.5f05.134c (bia 0013.5f05.134c)MTU 1500 bytes, BW 26000 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 never, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0Interface Cable5/1/0 queueing strategy: fifo5 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 multicasts)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped outViewing Information About the Cable Modems
To view information about the registered and unregistered cable modems, use the show cable modem command in privileged EXEC mode. For a complete description of this command, see the Cisco Broadband Cable Command Reference Guide on Cisco.com.
Examples
The following example shows a typical display for the show cable modem command:
Router# show cable modemMAC Address IP Address I/F MAC Prim RxPwr Timing Num IState Sid (dBmV) Offset CPE P0018.f826.337e 80.14.0.2 C5/0/0/U0 online(pt) 1 0.00 1992 0 N0018.6852.82f8 80.14.0.5 C5/0/0/U0 w-online(pt) 2 0.50 1998 0 N0013.10c6.c43d 80.14.0.3 C6/1/0/U0 online(pt) 1 0.00 1997 0 N0019.474a.e162 80.14.0.4 C6/1/0/U0 w-online(pt) 2 -0.75 1999 0The following example shows a typical display for the show cable modem primary command:
Router# show cable modem primaryMAC Address IP Address Host MAC Prim Num Primary DSInterface State Sid CPE Downstream RfId0018.f826.337e 80.14.0.2 C5/0/0/U0 online(pt) 1 0 Mo5/0/0:1 240018.6852.82f8 80.14.0.5 C5/0/0/U0 w-online(pt) 2 0 Mo5/0/0:1 240013.10c6.c43d 80.14.0.3 C6/1/0/U0 online(pt) 1 0 Mo6/1/0:0 20019.474a.e162 80.14.0.4 C6/1/0/U0 w-online(pt) 2 0 Mo6/1/0:0 2Troubleshooting the Cisco uBR-MC3GX60V Cable Interface Line Card
The following MAC domain commands are useful for troubleshooting bonding operations:
•
show cable mac-domain cable cgd-associations
•
show cable mac-domain cable downstream-service-group
•
show cable mac-domain cable forwarding
•
show cable mac-domain cable rcc
•
show cable mac-domain cable upstream-service-group
To troubleshoot software license issues, use the following commands:
•
show cable license
•
show license detail
For the M-CMTS network architecture, DOCSIS Timing Interface (DTI) based timing must be enabled with the following global configuration command:
•
cable clock dti
If DTI timing does not function correctly, modems are not be seen even in an init() state.
To determine the active DOCSIS Timing and Control Card (DTCC) and its current status, run the following command:
•
show cable clock
Router# show cable clockNumber of TCC Cards in the Chassis: 1Active TCC Card is in slot: 1 subslot: 1,(DTCC Eightbells card) Clock reference used by the active card is DTIActive TCC card in slot 1/1TCC Card 1/1 DTI status:------------------------------------------- Active Client port : 2Active Client status : normal Active Client Server status : freerun Active Client frame error rate : < 2% Active Client CRC error count : 0xFC Standby Client Signal detected : noSome other commands that you can use to troubleshoot the Cisco uBR-MC3GX60 line card:
•
show diag
To verify that the Cisco uBR-MC3GX60 line card is powered on, use the show diag command. If the output of the show diag command displays any output, the Cisco uBR-MC3GX60 line card is powered on.
If the Cisco uBR-MC3GX60 line card is powered on, verify that:
–
The line card has been inserted correctly and is screwed in
–
There are no extraneous subslot shutdown commands in the configuration that are preventing the line card from booting. Run the show running | include hw-module shutdown command for more information.
If show diag command does not display any output and the card is powered on by configuration, physically examine the line card face plate and check the Fail LED status. If the LED is on, then the line card is not booting correctly.
Note
When using a Cisco uBR-MC3GX60 line card, the empty slots in the Cisco uBR10012 router must be filled with blank filler cards to maximize air flow and keep the line cards functioning within proper thermal boundaries.
•
show controllers modular-cable sfp
The Cisco uBR-MC3GX60 line card can have up to six Small Form-Factor Pluggable (SFPs) for its three controllers. To check the presence and link status of the SFP, use the show controllers modular-cable sfp command. If the SFP is not present, the output will display:
SFP in Port1 is NOT PRESENTIf the SFP is present, verify that the "Phy Port" status is "Up"
•
show ip interface brief
To verify bidirectional communication between the Cisco CMTS and the RF Gateway, run the show ip interfaces brief command.
The Cisco uBR-MC3GX60 line card has three Gigabit Ethernet interfaces. When an IP address is configured on the GigE interface in a subnet that includes the RF Gateway, the IP address of the RF Gateway becomes pingable.
For more information on troubleshooting, see the Cisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide.
For complete descriptions of the above configuration commands, see the Cisco IOS CMTS Cable Command Reference on Cisco.com.
Upgrading Cisco uBR10-MC5X20S/U/H or Cisco UBR-MC20X20V Line Cards to Cisco uBR-MC3GX60V Cable Interface Line Card
The Cisco IOS Release 12.2(33)SCE does not support online insertion and removal (OIR) compatibility for the Cisco uBR-MC3GX60V line card. To upgrade to the Cisco uBR-MC3GX60V line card from the Cisco uBR10-MC5X20S/U/H or Cisco UBR-MC20X20V line cards, you must remove the existing configuration of the line card using the no card command and create a new configuration for the Cisco uBR-MC3GX60V line card.
Configuration Examples for the Cisco uBR-MC3GX60V Cable Interface Line Card
The following example shows how to configure the Cisco uBR-MC3GX60V cable interface line card:
!! Configure DEPI tunnel to EQAM. DEPI tunnel requires L2TP class and! DEPI class configuration that be applied to multiple tunnels.!l2tp-class class1hello 1retransmit retries 5retransmit timeout max 1!depi-class rfgw10-1mode mpt!depi-tunnel rfgw10-1_81_0_wdest-ip 192.168.18.200l2tp-class class1depi-class rfgw10-1!! Configure RF channel parameters and DEPI tunnel.!controller Modular-Cable 8/1/0rf-channel 0 cable downstream channel-id 169rf-channel 0 frequency 453000000 annex B modulation 256qam interleave 32rf-channel 0 depi-tunnel rfgw10-1_81_0_w tsid 1231no rf-channel 0 rf-shutdownrf-channel 1 cable downstream channel-id 170rf-channel 1 frequency 459000000 annex B modulation 256qam interleave 32rf-channel 1 depi-tunnel rfgw10-1_81_0_w tsid 1232no rf-channel 1 rf-shutdownrf-channel 2 cable downstream channel-id 171rf-channel 2 frequency 465000000 annex B modulation 256qam interleave 32rf-channel 2 depi-tunnel rfgw10-1_81_0_w tsid 1233no rf-channel 2 rf-shutdownrf-channel 3 cable downstream channel-id 172rf-channel 3 frequency 471000000 annex B modulation 256qam interleave 32rf-channel 3 depi-tunnel rfgw10-1_81_0_w tsid 1234no rf-channel 3 rf-shutdownrf-channel 4 cable downstream channel-id 173rf-channel 4 frequency 477000000 annex B modulation 256qam interleave 32rf-channel 4 depi-tunnel rfgw10-1_81_0_w tsid 1241no rf-channel 4 rf-shutdownrf-channel 5 cable downstream channel-id 174rf-channel 5 frequency 483000000 annex B modulation 256qam interleave 32rf-channel 5 depi-tunnel rfgw10-1_81_0_w tsid 1242no rf-channel 5 rf-shutdownrf-channel 6 cable downstream channel-id 175rf-channel 6 frequency 489000000 annex B modulation 256qam interleave 32rf-channel 6 depi-tunnel rfgw10-1_81_0_w tsid 1243no rf-channel 6 rf-shutdownrf-channel 7 cable downstream channel-id 176rf-channel 7 frequency 495000000 annex B modulation 256qam interleave 32rf-channel 7 depi-tunnel rfgw10-1_81_0_w tsid 1244no rf-channel 7 rf-shutdownrf-channel 8 cable downstream channel-id 177rf-channel 9 cable downstream channel-id 178rf-channel 10 cable downstream channel-id 179rf-channel 11 cable downstream channel-id 180rf-channel 12 cable downstream channel-id 181rf-channel 13 cable downstream channel-id 182rf-channel 14 cable downstream channel-id 183rf-channel 15 cable downstream channel-id 184rf-channel 16 cable downstream channel-id 185rf-channel 17 cable downstream channel-id 186rf-channel 18 cable downstream channel-id 187rf-channel 19 cable downstream channel-id 188rf-channel 20 cable downstream channel-id 189rf-channel 21 cable downstream channel-id 190rf-channel 22 cable downstream channel-id 191rf-channel 23 cable downstream channel-id 192!! Configure MAC domain with primary capable downstream channels, and! upstream channels.!interface Cable8/1/14downstream Modular-Cable 8/1/0 rf-channel 0cable mtc-modeno cable packet-cachecable bundle 1cable upstream max-ports 4cable upstream bonding-group 81upstream 0upstream 1upstream 2upstream 3attributes 80000000cable upstream 0 connector 0cable upstream 0 frequency 15000000cable upstream 0 channel-width 1600000 1600000cable upstream 0 docsis-mode tdmacable upstream 0 minislot-size 4cable upstream 0 range-backoff 3 6cable upstream 0 modulation-profile 21no cable upstream 0 shutdowncable upstream 1 connector 0cable upstream 1 frequency 25000000cable upstream 1 channel-width 1600000 1600000cable upstream 1 docsis-mode tdmacable upstream 1 minislot-size 4cable upstream 1 range-backoff 3 6cable upstream 1 modulation-profile 21no cable upstream 1 shutdowncable upstream 2 connector 0cable upstream 2 frequency 30000000cable upstream 2 channel-width 1600000 1600000cable upstream 2 docsis-mode tdmacable upstream 2 minislot-size 4cable upstream 2 range-backoff 3 6cable upstream 2 modulation-profile 21no cable upstream 2 shutdowncable upstream 3 connector 0cable upstream 3 frequency 35000000cable upstream 3 channel-width 1600000 1600000cable upstream 3 docsis-mode tdmacable upstream 3 minislot-size 4cable upstream 3 range-backoff 3 6cable upstream 3 modulation-profile 21no cable upstream 3 shutdown!! Configure GE interface for controller 8/1/0 with DEPI tunnel source! IP address.!interface GigabitEthernet8/1/0ip address 192.168.18.100 255.255.255.0negotiation autooutput-rate 100!! Configure Modular-Cable interface for primary cable downstream channelinterface Modular-Cable8/1/0:0cable bundle 1cable rf-bandwidth-percent 46!! Configure Wideband-Cable interface with primary and non-primary! downstream channels!interface Wideband-Cable8/1/0:31cable bundle 1cable rf-channel 0 bandwidth-percent 20cable rf-channel 1 bandwidth-percent 20cable rf-channel 2 bandwidth-percent 20!! Configure Bundle interface referenced by MAC domain, Modular-Cable, and! Wideband-Cable interfaces.!interface Bundle1ip address 80.14.0.1 255.255.255.0cable arp filter request-send 3 2cable arp filter reply-accept 3 2!! Configure fiber node with downstream and upstream channels!cable fiber-node 1downstream Modular-Cable 8/1/0 rf-channel 0-7upstream Cable 8/1 connector 0!
Note
For more configuration examples, see the Cisco documentation wiki (DocWiki) at http://docwiki.cisco.com/wiki/Cisco_uBR-MC3GX60V_Cable_Line_Card_Configuration_Example.
Configuration Examples for the Cisco uBR-MC3GX60V Cable Interface Line Card along with Wideband SPA
The following example shows how to configure the Cisco uBR-MC3GX60V line card along with the Cisco Wideband SPA:
Note
The example displayed in this section contains configuration specific to the Cisco uBR-MC3GX60V and Cisco Wideband SPA downstream sharing. The steps to configure the Cisco uBR-MC3GX60V line card and Cisco Wideband SPA remain the same. For more information on how to configure the Cisco Wideband SPA, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration Guide.
!Configure the Cisco uBR-MC3GX60V line card as modular host of Cisco Wideband SPAcontroller Modular-Cable 1/1/0modular-host subslot 8/0!Configure the rf-channel for Cisco Wideband SPArf-channel 0 cable downstream channel-id 5rf-channel 0 frequency 699000000 annex B modulation 256qam interleave 32rf-channel 0 ip-address 192.168.100.60 mac-address 0090.f001.8f48 depi-remote-id 460000rf-channel 1 cable downstream channel-id 1rf-channel 1 frequency 705000000 annex B modulation 256qam interleave 32rf-channel 1 ip-address 192.168.100.60 mac-address 0090.f001.8f48 depi-remote-id 480000rf-channel 2 cable downstream channel-id 2rf-channel 2 frequency 711000000 annex B modulation 256qam interleave 32rf-channel 2 ip-address 192.168.100.60 mac-address 0090.f001.8f48 depi-remote-id 500000rf-channel 3 cable downstream channel-id 3rf-channel 3 frequency 717000000 annex B modulation 256qam interleave 32end!Configure the Cisco uBR-MC3GX60V line card to include DS from Cisco Wideband SPAinterface Cable8/0/0downstream Modular-Cable 1/1/0 rf-channel 0end!Configure the fiber node to include DSs from Cisco Wideband SPA and Cisco uBR-MC3GX60V line cardcable fiber-node 1downstream Modular-Cable 1/1/0 rf-channel 0-3downstream Modular-Cable 8/0/2 rf-channel 0-3upstream Cable 8/0 connector 0-4endConfiguration Restrictions
•
The Cisco uBR-MC3GX60V cable interface line card supports 72 downstream channels with up to 24 downstream channels per controller (GigE port). There are no restrictions when operating in Annex B framing mode.
•
The Cisco uBR-MC3GX60V cable interface line card supports up to 54 downstream channels in Annex A framing mode. The command line interface does not enforce restrictions on the number of enabled channels in Annex A mode. However, when the number of enabled channels in Annex A framing mode exceeds the limit (18), a warning message is displayed.
We recommend that no more than 54 downstream channels in Annex A mode should be enabled with up to 18 downstream channels per controller to minimize oversubscription of the GigE ports.
Configuration Restrictions for Cisco uBR-MC3GX60V Line Card and Cisco Wideband SPA Downstream Sharing
•
Every Cisco uBR-MC3GX60V MAC-Domain should contain downstream channels from not more than one SPA.
Note
Starting with Cisco IOS Release 12.2(33)SCG, the Cisco uBR-MC3GX60V MAC-Domain can contain downstream channels from more than one SPA.
•
Configure Cisco CMTS WAN Egress Quality of Service (QoS) using Modular Quality of Service Command-Line Interface (MQC) with bandwidth rate-limits on the Ten-Gigabit-Ethernet interface. For more information on how to configure MQC QoS, see MQC QoS on the Cisco CMTS Routers guide.
•
Configure the WAN QoS rate-limiting on the uplink WAN routers link to the Cisco CMTS so that the Cisco CMTS WAN Ingress bandwidth is limited.
•
Configure the cable interface line card upstream bandwidth parameters. Ensure that the total line card ingress bandwidth along with WAN ingress bandwidth, on the Cisco CMTS, does not exceed the Parallel eXpress Forwarding (PXF) memory bandwidth of 17 Gbps.
Additional References
Related Documents
Document Title URLCisco uBR-MC3GX60V Cable Interface Line Card Hardware Installation Guide
Installing Cisco uBR-MC3GX60V Cable Interface Line Cards - Quick Start Guide
Cisco uBR10012 Universal Broadband Router Hardware Installation Guide
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/
installation/guide/hig.htmlCisco uBR10012 Universal Broadband Router Software Configuration Guide
http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/
configuration/guide/scg.htmlCisco IOS Commands for the Cisco CMTS Routers
http://www.cisco.com/en/US/docs/ios/cable/command/reference/
cbl_book.htmlCisco IOS CMTS Cable Software Configuration Guide, Release 12.2SC
Cisco uBR10000 Series Universal Broadband Router Release Notes
http://www.cisco.com/en/US/products/hw/cable/ps2209/
prod_release_notes_list.htmlSoftware Activation on Cisco CMTS Routers
http://www.cisco.com/en/US/docs/cable/cmts/license/
cmts_swact.htmlCisco DOCSIS 3.0 Downstream Solution Design and Implementation Guide
http://www.cisco.com/en/US/docs/cable/cmts/wideband/solution/
guide/release_2.0/ds_solu.html
Standards
Standard TitleCableLabs™ DOCSIS 1.1 specifications
CableLabs™ PacketCable specifications
CableLabs™ PacketCable MultiMedia specifications
http://www.cablelabs.com/packetcable/specifications/
multimedia.html
MIBs
MIB MIBs LinkMIBs for the Cisco Cable Modem Termination System
Cisco CMTS Universal Broadband Series Router MIB Specifications Guide 12.2 SC
http://www.cisco.com/en/US/docs/cable/cmts/mib/12_2sc/reference/guide/ubrmibv5.html
MIBs Supporting Cisco IOS
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL:
Technical Assistance
Feature Information for the Cisco uBR-MC3GX60V Cable Interface Line Card
Table 3 lists the release history for this feature.
Use the Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 3 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
©2010-2013 Cisco Systems, Inc. All rights reserved.
Feedback
