Part 3: Cable Interface: Downstream and Upstream Features - Wideband Modem Resiliency [Cisco uBR10000 Series Universal Broadband Routers]

Table Of Contents

Wideband Modem Resiliency

Finding Feature Information

Contents

Prerequisites for Wideband Modem Resiliency

Restrictions for Wideband Modem Resiliency

Information About Wideband Modem Resiliency

CM-STATUS Messages

RF Channel Event Dampening Time

How a CMTS Responds to RF Impairment Recovery

How to Configure Wideband Modem Resiliency

Specifying Trigger Thresholds for Downstream Events

Specifying Persistence Time for RF Channels

Changing Default CM-STATUS Configuration

Verifying Wideband Modem Resiliency

What to Do Next

Modifying CM-STATUS Reports for Events

Enabling SNMP Traps for Wideband Resiliency Events

Enabling Wideband Resiliency Trap Notifications

Setting the Trap Interval

Configuration Example for Wideband Modem Resiliency

Additional References

Related Documents

Standards

MIBs

Technical Assistance

Feature Information for Wideband Modem Resiliency

Wideband Modem Resiliency

First Published: December 17, 2008

Last Updated: Jan 20, 2013

The Wideband Modem Resiliency feature provides reliable service in the event of non-primary RF channel disruptions to ensure that a cable modem remains operational. With the implementation of this feature, the Cable Modem Termination System (CMTS) does not force a cable modem to perform a MAC reset if the cable modem loses connectivity to the CMTS on one or all of its non-primary RF channels.

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 see a list of the releases in which each feature is supported, see the "Feature Information for Wideband Modem Resiliency" section.

Use Cisco Feature Navigator to find information about platform support and Cisco IOS, Catalyst OS, and Cisco IOS XE 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 Wideband Modem Resiliency

•Restrictions for Wideband Modem Resiliency

•Information About Wideband Modem Resiliency

•How to Configure Wideband Modem Resiliency

•Configuration Example for Wideband Modem Resiliency

•Additional References

•Feature Information for Wideband Modem Resiliency

Prerequisites for Wideband Modem Resiliency

Table 1 shows the hardware compatibility prerequisites for the Wideband Modem Resiliency feature.

Table 1 Cable Hardware Compatibility Matrix for Wideband Modem Resiliency

CMTS Platform

Processor Engine

Cable Interface Line Cards

Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.2(33)SCB and later

•PRE2

•PRE4

Cisco IOS Release 12.2(33)SCB and later

•Cisco uBR10-MC5X20S/U/H

Cisco IOS Release 12.2(33)SCC and later

•Cisco UBR-MC20X20V

Cisco uBR7225VXR Universal Broadband Router

Cisco IOS Release 12.2(33)SCD and later

•NPE-G2

Cisco IOS Release 12.2(33)SCD and later

•Cisco uBR-MC88V

Cisco uBR7246VXR Universal Broadband Routers

Cisco IOS Release 12.2(33)SCD and later

•NPE-G2

Cisco IOS Release 12.2(33)SCD and later

•Cisco uBR-MC88V

Restrictions for Wideband Modem Resiliency

The Wideband Modem Resiliency feature has the following restrictions:

•This feature provides resiliency support only for downstream RF channel disruptions in Cisco IOS Release 12.2(33)SCB and later. This feature does not support any upstream-related resiliency.

•The CMTS cannot move a w-online cable modem to a bonding group that contains an RF channel that is not a member of the original Receive Channel Configuration (RCC) for the wideband cable modem.

Information About Wideband Modem Resiliency

The Wideband Modem Resiliency feature enables the Cisco uBR10012 or Cisco uBR7200 series router to interact with DOCSIS 3.0-compliant cable modems. This interaction helps provide reliable service in the event of non-primary channel disruptions of layer 1 and/or layer 2 connections, and loss of quadrature amplitude modulation (QAM) lock and/or MAC Domain Descriptor (MDD) timeout. If a cable modem loses connectivity with the CMTS on one or all of its non-primary RF channels, the CMTS does not force the cable modem to perform a MAC reset and enables the cable modem to remain operational.

A DOCSIS 3.0-qualified CMTS transmits data to one or more DOCSIS 3.0-compliant cable modems using multiple RF channels. For a cable modem, one of the RF channels is used as the primary RF channel, and the rest of the channels are considered non-primary channels. The primary RF channel is defined as the downstream (DS) RF channel on which the cable modem receives DOCSIS MAC messages needed for upstream timing and synchronization.

This feature enables the CMTS to collect and analyze data related to RF channel disruptions per cable modem to assist in identifying the impairment.

CM-STATUS Messages

Cable modems use CM-STATUS messages to report events to the CMTS. A DOCSIS 3.0-compliant cable modem does not perform a MAC reset when reporting DS RF channel failures through CM-STATUS messages. The CMTS does not send an acknowledgement to the cable modem when it receives a CM-STATUS message. The CMTS might not receive a CM-STATUS message, if the message gets corrupted during transmission. To prevent this occurrence, the CMTS sends the following two parameters to the cable modem using the primary MDD message for each event type:

•Maximum reports

•Maximum hold-off time

The maximum reports parameter specifies how many reports should be sent each time a particular event occurs. The maximum hold-off time parameter defines the amount of time (in units of 20 milliseconds) a cable modem should wait between transmissions of the CM-STATUS messages when the maximum reports parameter is greater than one.

RF Channel Event Dampening Time

The Wideband Modem Resiliency feature enables the CMTS to reduce the occurrence of a particular RF channel event by using the cable rf-change-dampen-time command. This command can also be used to prevent premature cable modem reconfiguration in the event of a prolonged outage. For example, the failover time of a remote edge-QAM device (EQAM) may be 10 seconds. Using the cable rf-change-dampen-time command, you can specify the dampening time such that an EQAM failover does not inadvertently trigger a mass reconfiguration of wideband cable modems.

How a CMTS Responds to RF Impairment Recovery

When cable modems report the recovery from downstream RF channel failures and their default downstream service flow has been moved to their primary downstream channel, the response of the CMTS is different between the following two Cisco IOS releases:

•Cisco IOS Release 12.2(33)SCB and later—If a cable modem reports that full service has been restored after downstream RF channel failures, the CMTS forces the cable modem to perform a MAC reset.

•Cisco IOS Release 12.2(33)SCC and later—If a cable modem reports that full service has been restored, the CMTS does not force the cable modem to perform a MAC reset, and the cable modem is kept w-online (the wideband downstream service is restored by the original wideband interface without a MAC reset).

How to Configure Wideband Modem Resiliency

The following tasks describe how to configure the Wideband Modem Resiliency feature on a Cisco uBR10012 or Cisco uBR7200 series router:

•Specifying Trigger Thresholds for Downstream Events (required)

•Specifying Persistence Time for RF Channels (optional)

•Changing Default CM-STATUS Configuration (optional)

•Verifying Wideband Modem Resiliency (optional)

•Modifying CM-STATUS Reports for Events (optional)

•Enabling SNMP Traps for Wideband Resiliency Events (optional)

•Enabling Wideband Resiliency Trap Notifications (optional)

•Setting the Trap Interval (optional)

Specifying Trigger Thresholds for Downstream Events

When a cable modem reports a downstream channel impairment via a CM-STATUS message, the cable modem can no longer reliably receive data on that channel. The Cisco CMTS must not use that channel to transmit data to the cable modem. The Cisco CMTS uses the following three options to prevent the use of the impaired channel(s):

•Option 1—Suspend the RF channel(s) from the wideband interface used by that cable modem.

•Option 2—Move the default downstream service flow from its wideband interface to its primary channel interface (modular or cable).

•Option 3—Move all the downstream service flows (primary and unicast secondary service flows) from its wideband interface to its primary channel interface (modular or cable).

Choosing option 1 retains all the remaining operational DS channels active, option 2 retains only a single DS channel, and option 3 retains all DS channels. Option 1 affects all cable modems that are receiving service via the affected wideband interface, while options 2 and 3 only affect the cable modem reporting the impairment.

To control which option the Cisco CMTS uses when an RF impairment is reported, use the cable rf-change-trigger command. This command enables you to configure thresholds (percent and count) for an event before the event triggers an action for the cable modem. This command also enables you to configure a secondary keyword to move all the secondary downstream service flows of a cable modem to the primary channel interface.

Because the CM-STATUS messages are received sequentially, the decision to use options 1, 2, or 3 is made based on whether the trigger threshold is reached or not, and if the secondary keyword is configured. Table 2 lists the cable rf-change-trigger command conditions and the corresponding options selected by the Cisco CMTS.

Table 2 Conditions for Selecting RF Impairment Handling Options

rf-change-trigger Threshold Reached

secondary Keyword Configured

RF Impairment Handling Option Selected by the Cisco CMTS

YES

NA

Option 1

NO

NO

Option 2

NO

YES

Option 3

If the trigger thresholds for an event are not configured, the state of the non-primary RF channels always remains up, and the cable modems that report RF failures are reset after the dampening time specified in the cable rf-change-dampen-time command expires. If both thresholds are configured, then both the thresholds must be reached before changing the RF channel state to down.

In addition to not meeting the configured rf-change-trigger, a cable modem that reports impairments has its downstream service flows modified in option 2 or option 3, to provide reliable service in the following conditions:

•If the count exceeds the specified number of cable modems but the percent threshold is not reached.

•If the percent threshold is reached but the count does not reach the specified number of cable modems.

•If all non-primary channels of the cable modem are reported down.

Additionally with option 3, only those unicast secondary service flows (static or dynamic) which share the same wideband interface as the primary service flow, are moved to the primary channel interface (modular or cable). Any new dynamic service flows are created on the primary channel interface.

A suspended RF channel is restored for all affected wideband interfaces when a specified number of cable modems report (via CM-STATUS) that the channel connectivity is restored. The Wideband Modem Resiliency feature defines the specified number of cable modems as half of the configured count or percentage of rf-change-trigger, or both. For example, if the count is 20 and the percent is 10, then the number of cable modems reporting recovery should reduce the count to 10 and the percent to 5 for the suspended RF channel to be restored.

When either option 2 or option 3 is chosen by the Cisco CMTS, the service flows are not moved back to the original wideband interface until all the impaired RF channels are restored. However, with option 3 the existing dynamic secondary service flows, which are transitory in nature, are not moved back to the wideband interface even when all RF channels are restored.

Table 3 lists the various RF channel impairment handling options that the cable modem chooses and their applicable Cisco IOS releases.

Table 3 Release Specific Behavior for RF Impairment Handling options

RF Impairment Handling Options

Applicable Cisco IOS Releases

Option 1

Cisco IOS Release 12.2(33)SCB and later releases.

Option 2

Cisco IOS Release 12.2(33)SCC and later releases.

Option 3

Default behavior in Cisco IOS Release 12.2(33)SCB and SCB-based releases. All downstream service flows (primary or secondary) are moved to primary channel interface.

Configurable behavior in Cisco IOS Release 12.2(33)SCE4 and later releases. The decision to move all secondary service flows can be configured using the cable rf-change-trigger command. For more information, see the Cisco IOS CMTS Cable Command Reference guide.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable rf-change-trigger [percent value] [count number] [secondary]

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

cable rf-change-trigger [percent value] [count number] [secondary]
Example:

Router(config)# cable rf-change-trigger percent 50 count 1 secondary

Specifies the amount of time an event must persist before it triggers an action for the reporting cable modem.

•percent value—(Optional) Indicates the percentage of cable modems that must report that a particular non-primary RF channel is down before that channel is removed from the bonding group with that NP RF channel configured. The valid range is from 1 to 100. The default value is 0.

•count number—(Optional) Specifies the number of cable modems reporting an impairment for a non-primary downstream channel. The default value is 0.

•secondary—(Optional) Configures the Cisco CMTS to move the unicast secondary service flows to primary interface, when the number of cable modems reporting RF channel impairment is less than the configured (percent or count) threshold.

Note Only those unicast secondary service flows, which share the same wideband interface as the primary interface, are moved to the primary channel interface.

Specifying Persistence Time for RF Channels

To configure the amount of time a non-primary RF channel must remain in its current state (either up or down), use the cable rf-change-dampen-time command.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable rf-change-dampen-time seconds

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

cable rf-change-dampen-time seconds
Example:

Router(config)# cable rf-change-dampen-time 10

Specifies the amount of time in seconds for a non-primary RF channel to remain in its new state. The default value is 30.

Changing Default CM-STATUS Configuration

To change the default configuration values of "Event Holdoff Timer" and "Number of Reports per Event" for any or all events, use the cable cm-status command.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable cm-status {all | event} [holdoff {timer | default} | reports {reportvalue | default}]

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

cable cm-status {all | event} [holdoff {timer | default} | reports {reportvalue | default}]
Example:

Router(config-if)# cable cm-status 1 holdoff 1

Sets the holdoff timer (in milliseconds) and the number of reports per event value.

•event—CM-STATUS event. The valid range is from 1 to 10.

•timer—Holdoff timer value. The valid range is from 1 to 65535. The default value is 50.

•reportvalue—Report value. The valid range is from 0 to 255. The default value is 2.

Verifying Wideband Modem Resiliency

Use the following show commands to verify the state of RF channels and the other configuration details:

•show interface rf-status

•show cable rf-status

•show cable modem wideband rcs-status

•show cable modem

To verify the logical up and down state for each of the configured RF channels for a wideband interface, use the show interface rf-status command as shown in the following example:

Cisco uBR10012 universal broadband router:
Router# show interface wideband-cable 1/0/0:3 rf-status
	Logical
RF  Status
--  ------
17  UP
18  UP
19  UP
Cisco uBR7200 series universal broadband router:
Router# show interface wideband-cable 5/1:0 rf-status
            Logical
Resource    RF  Status
-----------------------
5/1         0   UP
            1   UP
            2   UP
To verify the logical up and down state of the specified channel number, or the logical state of all RF channels, use the show cable rf-status command as shown in the following example:

Router# show cable rf-status
          Logical  Flap    Flap
RF        Status   Counts  Time
--------  -------  ------  ----
1/0/0 0   UP       0       
      1   UP       0       
      2   UP       0       
      3   UP       0       
      5   UP       0       
      6   UP       0       
      7   UP       0       
      8   UP       0       
      9   UP       0       
      10  UP       0       
      11  UP       0       
      12  UP       0       
      13  UP       0       
      14  UP       0       
      15  UP       0       
      16  UP       0       
To verify details of events for each RF channel in the cable modem's Receive Channel Configuration (RCC), use the show cable modem wideband rcs-status command as shown in the following example:
Router# show cable modem 0019.474a.c0ba wideband rcs-status
CM  : 0019.474a.c0ba
RF  : 1/0/0 10
  Status                   : UP
  FEC/QAM Failure          : 0         
  Dup FEC/QAM Failure      : 0         
  FEC/QAM Recovery         : 0         
  Dup FEC/QAM Recovery     : 0         
  MDD Failure              : 0         
  Dup MDD Failure          : 0         
  MDD Recovery             : 0         
  Dup MDD Recovery         : 0         
  Flaps                    : 0         
  Flap Duration            : 00:00
RF  : 1/0/0 11
  Status                   : UP
  FEC/QAM Failure          : 0         
  Dup FEC/QAM Failure      : 0         
  FEC/QAM Recovery         : 0         
  Dup FEC/QAM Recovery     : 0         
  MDD Failure              : 0         
  Dup MDD Failure          : 0         
  MDD Recovery             : 0         
  Dup MDD Recovery         : 0         
  Flaps                    : 0         
  Flap Duration            : 00:00
To verify the basic receive statistics for all possible event code types for the specified cable modem, use the show cable modem command as shown in the following example:
Router# show cable modem cm-status                        
I/F    MAC Address    Event            TID   Count Error Dups  Time
C7/0   001c.ea2b.79b2 MDD timeout      0     0     1     0     Jan 11 11:29:22
                      QAM failure      0     0     1     0     Jan 11 11:29:02
                      MDD recovery     0     0     1     0     Jan 11 11:30:20
                      QAM recovery     0     0     1     0     Jan 11 11:30:13
C7/0   001c.ea2b.78b0 MDD timeout      0     0     1     0     Jan 11 11:29:16
                      QAM failure      0     0     1     0     Jan 11 11:28:53
                      MDD recovery     0     0     1     0     Jan 11 11:29:59
                      QAM recovery     0     0     1     0     Jan 11 11:29:46
Router# show cable modem 001c.ea2b.79b2 cm-status 
I/F    MAC Address    Event            TID   Count Error Dups  Time
C7/0   001c.ea2b.79b2 MDD timeout      0     0     1     0     Jan 11 11:29:22
                      QAM failure      0     0     1     0     Jan 11 11:29:02
                      MDD recovery     0     0     1     0     Jan 11 11:30:20
                      QAM recovery     0     0     1     0     Jan 11 11:30:13
Router# show cable modem cable 7/0 cm-status
I/F    MAC Address    Event            TID   Count Error Dups  Time
C7/0   001c.ea2b.79b2 MDD timeout      0     0     1     0     Jan 11 11:29:22
                      QAM failure      0     0     1     0     Jan 11 11:29:02
                      MDD recovery     0     0     1     0     Jan 11 11:30:20
                      QAM recovery     0     0     1     0     Jan 11 11:30:13
C7/0   001c.ea2b.78b0 MDD timeout      0     0     1     0     Jan 11 11:29:16
                      QAM failure      0     0     1     0     Jan 11 11:28:53
                      MDD recovery     0     0     1     0     Jan 11 11:29:59
                      QAM recovery     0     0     1     0     Jan 11 11:29:46
What to Do Next

To modify the default configuration of events for CM-STATUS reports, proceed to the "Modifying CM-STATUS Reports for Events" section.

Modifying CM-STATUS Reports for Events

You can enable or modify the following ten CM-STATUS events per interface using the cable cm-status enable command:

1. Secondary channel MDD time-out

2. QAM/FEC lock failure

3. Sequence out of range

4. MDD recovery

5. QAM/FEC lock recovery

6. T4 time-out

7. T3 re-tries exceeded

8. Successful ranging after T3 re-tries exceeded

9. CM operating on battery backup

10. CM returned to A/C power

The following events are enabled by default on a cable or modular cable interface:

•Secondary channel MDD time-out

•QAM/FEC lock failure

•Sequence out of range

•MDD recovery

•QAM/FEC lock recovery

SUMMARY STEPS

1. enable

2. configure terminal

3. interface cable {slot/port | slot/subslot/port}

4. cable cm-status enable range

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

interface cable {slot/port | slot/subslot/port}
Example:

Router(config)# interface cable8/0/0

Specifies the cable interface line card on a Cisco CMTS router:

•slot—Chassis slot number of the cable interface line card.

Cisco uBR7246VXR router: The valid range is from 3 to 6.

Cisco uBR7225VXR router: The valid range is from 1 to 2.

Cisco uBR10012 router: The valid range is from 5 to 8.

•subslot—(Cisco uBR10012 only) Secondary slot number of the cable interface line card. Valid subslots are 0 or 1.

•port—Downstream port number.

Cisco uBR7246VXR and Cisco uBR7225VXR routers: The valid port value is 0 or 1.

Cisco uBR10012 router: The valid range is from 0 to 4 (depending on the cable interface).

Step 4

cable cm-status enable range
Example:

Router(config-if)# cable cm-status enable 6-9

Enables a particular CM-STATUS event on a primary cable interface. The valid range is from 1 to 10.

The following events are enabled by default on cable and modular cable interfaces:

•Secondary channel MDD time-out

•QAM/FEC lock failure

•Sequence out of range

•MDD recovery

•QAM/FEC lock recovery

To disable a CM-STATUS event, use the no form of the cable cm-status enable command.

Enabling SNMP Traps for Wideband Resiliency Events

You can enable Simple Network Management Protocol (SNMP) traps for Wideband Resiliency specific events using the snmp-server enable traps docsis-resil command.

SUMMARY STEPS

1. enable

2. configure terminal

3. snmp-server enable traps docsis-resil [resil-events]

4. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

snmp-server enable traps docsis-resil [resil-events]
Example:

Router(config)# snmp-server enable traps docsis-resil rf-up

Enables SNMP traps for wideband resiliency specific events. Traps can be sent for specific events using the resil-events option:

•cm-pmode—Enables the wideband resiliency cable modem partial service trap.

•cm-recover—Enables the wideband resiliency cable modem full service trap.

•event—Enables the wideband resiliency event trap.

•rf-down—Enables the wideband resiliency RF channel down status trap.

•rf-up—Enables the wideband resiliency RF channel up status trap.

To disable sending of the trap, use the no form of this command.

Step 4

exit
Example:

Router(config)# exit

Exits global configuration mode.

Enabling Wideband Resiliency Trap Notifications

You can enable Wideband Resiliency trap notifications to a specific SNMP host using the snmp-server host traps docsis-resil command.

SUMMARY STEPS

1. enable

2. configure terminal

3. snmp-server host ipaddr traps string docsis-resil

4. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

snmp-server host ipaddr traps string docsis-resil
Example:

Router(config)# snmp-server host 172.17.2.0 traps snmphost01 docsis-resil

Enables wideband resiliency traps for a specific SNMP host.

•ipaddr—IPv4 or IPv6 address of the SNMP notification host.

•string—SNMPv1 community string, SNMPv2c community string, or SNMPv3 username.

To disable, use the no form of this command.

Step 4

exit
Example:

Router(config)# exit

Exits global configuration mode.

Setting the Trap Interval

You can set the interval at which traps must be sent for Wideband Resiliency related events for each cable modem using the cable resiliency traps-interval command.

SUMMARY STEPS

1. enable

2. configure terminal

3. cable resiliency traps-interval count

4. exit

DETAILED STEPS

Command or Action

Purpose

Step 1

enable
Example:

Router> enable

Enables privileged EXEC mode.

•Enter your password if prompted.

Step 2

configure terminal
Example:

Router# configure terminal

Enters global configuration mode.

Step 3

cable resiliency traps-interval count
Example:

Router(config)# cable resiliency traps-interval 0

Sets the time interval at which traps must be sent for each cable modem.

•count—Time interval (in seconds) at which the traps must be sent for each cable modem. The valid range is from 0 to 86400. The default value is 1.

To disable, use the no form of this command.

Step 4

exit
Example:

Router(config)# exit

Exits global configuration mode.

Configuration Example for Wideband Modem Resiliency

The following example shows how to configure the Wideband Modem Resiliency feature by specifying the dampening time and persistence thresholds for non-primary RF channels:
Router# configure terminal
Router(config)# cable rf-change-dampen-time 40
Router# configure terminal
Router(config)# cable rf-change-trigger percent 50 count 1
Router# configure terminal
Router(config)# cable cm-status 1 holdoff 1
Additional References

The following sections provide references related to the Wideband Modem Resiliency feature.

Related Documents

Related Topic

Document Title

Commands on the Cisco CMTS (universal broadband) routers

Cisco IOS CMTS Cable Command Reference

http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

Cisco DOCSIS 3.0 Downstream Solution

Cisco 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

Cisco Cable Wideband Solution Design

Cisco Cable Wideband Solution Design and Implementation Guide

http://www.cisco.com/en/US/docs/cable/cmts/wideband/solution/guide/release_1.0/wb_solu.html

Standards

Standard

Title

CM-SP-MULPIv3.0-I08-080522

DOCSIS 3.0 MAC and Upper Layer Protocol Interface Specification

MIBs

MIB

MIBs Link

CISCO-DOCS-EXT-MIB.my

To locate and download MIBs for selected platforms, Cisco software releases, and feature sets, use Cisco MIB Locator found at the following URL:

http://tools.cisco.com/ITDIT/MIBS/servlet/index

Technical Assistance

Description

Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html

Feature Information for Wideband Modem Resiliency

Table 4 lists the features in this module and provides links to specific configuration information. Only those features that were introduced or modified in Cisco IOS Release 12.2(33)SCB or a later release appear in the table.

Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS 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 4 lists only that Cisco IOS software release, which introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.

Table 4 Feature Information for Wideband Modem Resiliency

Feature Name

Releases

Feature Information

Wideband Modem Resiliency

12.2(33)SCB

The Wideband Modem Resiliency feature provides the best possible service in the event of non-primary RF channel disruptions.

The following sections provide information about this feature:

•How to Configure Wideband Modem Resiliency

•Configuration Example for Wideband Modem Resiliency

The following commands were introduced or modified:

•cable rf-change-dampen-time

•cable rf-change-trigger

•cable cm-status enable

•show interface rf-status

•show cable rf-status

•show cable modem wideband rcs-status

•show cable modem summary wb-rf

•clear cable modem cm-status

•clear cable modem rcs-counts

•clear cable rf-status

•debug cable wbcmts resiliency

•show cable flap-list wb-rf

Bypass the 24 Hour Timer for Wideband Cable Modems

12.2(33)SCB

This feature removes the 24-hour timer required to clear these channels. Once the cable modem successfully completes registration, the list of failed RF channels for that cable modem is cleared. If the RF impairment has been eliminated when the cable modem re-registers, that channel can be reused immediately.

There are no new or modified commands for this feature.

Wideband Modem Resiliency

12.2(33)SCD

In Cisco IOS Release 12.2(33)SCD, this feature was introduced on the Cisco uBR7225VXR and Cisco uBR7246VXR routers.

The following commands were introduced or modified:

•interface cable

•show interface rf-status

•show cable modem

•clear cable modem cm-status

•cable cm-status

Move Secondary Service Flows to Primary Channel Interface.

12.2(33)SCE4

This feature enables the Cisco CMTS to move all the unicast secondary service flows to the primary channel interface, when the number of cable modems reporting the RF-channel impairment is less than the configured trigger threshold.

For more information on this feature, see section Specifying Trigger Thresholds for Downstream Events.

The cable rf-change-trigger command was modified.

Downstream Wideband Resiliency Trap

12.2(33)SCG2

This feature enables SNMP traps for Wideband Resiliency related events and setting of the trap interval.

For more information, see:

•Enabling SNMP Traps for Wideband Resiliency Events

•Enabling Wideband Resiliency Trap Notifications

•Setting the Trap Interval

The following commands were introduced or modified:

•cable resiliency traps-interval

•snmp-server enable traps docsis-resil

•snmp-server host traps docsis-resil

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2008-2013 Cisco Systems, Inc. All rights reserved.