Guest

Cisco uBR10000 Series Universal Broadband Routers

Release Notes for the Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC

  • Viewing Options

  • PDF (5.7 MB)
  • Feedback
Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC

Table Of Contents

Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC

Contents

Early Deployment Releases

System Requirements

Memory Recommendations

Supported Hardware

DOCSIS System Interoperability on the Cisco uBR10012 CMTS

Cisco IOS Release 12.3(13a)BC and DOCSIS 1.1 System Interoperability

DOCSIS 1.0 Baseline Privacy

Cable Modem Interoperability

DOCSIS 1.0 and 1.0+ Extensions

DOCSIS 1.1 Extensions

DOCSIS 1.1 Quality of Service

Determining the Software Version

Upgrading to a New Software Release

Feature Set Tables

New and Changed Information

New Hardware Features in Cisco IOS Release 12.3(23)BC10

New Software Features in Cisco IOS Release 12.3(23)BC10

New Hardware Features in Cisco IOS Release 12.3(23)BC9

New Software Features in Cisco IOS Release 12.3(23)BC9

Open Source Software Licenses for Cisco Universal Broadband Routers

New Hardware Features in Cisco IOS Release 12.3(21a)BC9

New Software Features in Cisco IOS Release 12.3(21a)BC9

New Hardware Features in Cisco IOS Release 12.3(23)BC8

New Software Features in Cisco IOS Release 12.3(23)BC8

New Hardware Features in Cisco IOS Release 12.3(23)BC7

New Software Features in Cisco IOS Release 12.3(23)BC7

SAMIS CLC-RP Traffic Throttling

M-CMTS Enhancement

Three Step Dynamic Modulation

Enhanced Show Tech

Cable Modem QoS Information

Direct Load for Cable Modems

New Hardware Features in Cisco IOS Release 12.3(23)BC6

New Software Features in Cisco IOS Release 12.3(23)BC6

New Hardware Features in Cisco IOS Release 12.3(23)BC5

New Software Features in Cisco IOS Release 12.3(23)BC5

New Hardware Features in Cisco IOS Release 12.3(23)BC4

New Software Features in Cisco IOS Release 12.3(23)BC4

New Hardware Features in Cisco IOS Release 12.3(21a)BC8

New Software Features in Cisco IOS Release 12.3(21a)BC8

New Hardware Features in Cisco IOS Release 12.3(23)BC3

New Software Features in Cisco IOS Release 12.3(23)BC3

New Hardware Features in Cisco IOS Release 12.3(23)BC2

New Software Features in Cisco IOS Release 12.3(23)BC2

Subscriber Traffic Management (STM) Version 1.2

Upstream Utilization Optimization

New Hardware Features in Cisco IOS Release 12.3(21a)BC7

New Software Features in Cisco IOS Release 12.3(21a)BC7

New Hardware Features in Cisco IOS Release 12.3(23)BC1

Cisco 1000BASE-T SFP Module

New Software Features in Cisco IOS Release 12.3(23)BC1

PacketCable Subscriber ID Support

MxN MAC Domain DS Load Balancing

Line Card High Availability (HA) Support for WB Cable Modems

Bypass the 24 Hour Timer for WB CM Use of Failed RF Channels

Voice Support on WB Modems

Dynamic Bandwidth Sharing for Wideband and Modular Cable Interfaces

New Hardware Features in Cisco IOS Release 12.3(21a)BC6

New Software Features in Cisco IOS Release 12.3(21a)BC6

New Hardware Features in Cisco IOS Release 12.3(21a)BC5

New Software Features in Cisco IOS Release 12.3(21a)BC5

New Hardware Features in Cisco IOS Release 12.3(23)BC

DOCSIS Timing & Control Card (DTCC)

New Software Features in Cisco IOS Release 12.3(23)BC

DOCSIS 3.0 Downstream Solution

New Hardware Features in Cisco IOS Release 12.3(21a)BC4

New Software Features in Cisco IOS Release 12.3(21a)BC4

New Hardware Features in Cisco IOS Release 12.3(17b)BC9

New Software Features in Cisco IOS Release 12.3(17b)BC9

New Hardware Features in Cisco IOS Release 12.3(21a)BC3

New Software Features in Cisco IOS Release 12.3(21a)BC3

Control Point Discovery (CPD)

New Hardware Features in Cisco IOS Release 12.3(21a)BC2

New Software Features in Cisco IOS Release 12.3(21a)BC2

New Hardware Features in Cisco IOS Release 12.3(21a)BC1

New Software Features in Cisco IOS Release 12.3(21a)BC1

New Hardware Features in Cisco IOS Release 12.3(21)BC

Cisco Wideband SIP

Cisco Wideband SPA

New Software Features in Cisco IOS Release 12.3(21)BC

Automatic Virtual Interface Bundles

Cable DHCP Enhancements

Cable Duplicate MAC Address Reject

DOCSIS 3.0 Downstream Channel Bonding

Enhanced Rate Bandwidth Allocation (ERBA) on the Cisco uBR10012 Router

HCCP Switchover Enhancements

NSF Lite

PacketCable Client Accept Timeout

Per Downstream Static Multicast

RF Switch Firmware Version 3.60

SAMIS Source Address Management

Service Flow Admission Control

Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia

New Hardware Features in Cisco IOS Release 12.3(17b)BC8

New Software Features in Cisco IOS Release 12.3(17b)BC8

New Hardware Features in Cisco IOS Release 12.3(17b)BC7

New Software Features in Cisco IOS Release 12.3(17b)BC7

New Hardware Features in Cisco IOS Release 12.3(17b)BC6

New Software Features in Cisco IOS Release 12.3(17b)BC6

New Hardware Features in Cisco IOS Release 12.3(17b)BC5

New Software Features in Cisco IOS Release 12.3(17b)BC5

New Hardware Features in Cisco IOS Release 12.3(17b)BC4

Cisco uBR10-MC5X20H Interface Line Card

New Software Features in Cisco IOS Release 12.3(17b)BC4

Downstream Load Balancing Distribution with Upstream Load Balancing

New Hardware Features in Cisco IOS Release 12.3(17b)BC3

New Software Features in Cisco IOS Release 12.3(17b)BC3

New Hardware Features in Cisco IOS Release 12.3(17a)BC2

New Software Features in Cisco IOS Release 12.3(17a)BC2

Cisco Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS

DOCSIS1.0 TOS Overwrite

New Hardware Features in Cisco IOS Release 12.3(17a)BC1

New Software Features in Cisco IOS Release 12.3(17a)BC1

New Hardware Features in Cisco IOS Release 12.3(17a)BC

New Software Features in Cisco IOS Release 12.3(17a)BC

Cable Monitor Enhancements

CNEM Compliance

DOCSIS 2.0 SAMIS ECR Data Set

DSX Messages and Synchronized PHS Information

Dynamic Channel Change (DCC) for Load Balancing

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

High Availability Support for Encrypted IP Multicast

IPv6 over L2VPN

Management Information Base (MIB) Changes and Enhancements

Pre-equalization Control for Cable Modems

PXF ARP Filter

PXF Divert Rate Limiting

show cable modem Command Changes

Secure Socket Layer Server for Usage-Based Billing

SSM Mapping

New Hardware Features in Cisco IOS Release 12.3(13a)BC6

New Software Features in Cisco IOS Release 12.3(13a)BC6

New Hardware Features in Cisco IOS Release 12.3(13a)BC5

New Software Features in Cisco IOS Release 12.3(13a)BC5

New Hardware Features in Cisco IOS Release 12.3(13a)BC4

New Software Features in Cisco IOS Release 12.3(13a)BC4

New Hardware Features in Cisco IOS Release 12.3(13a)BC3

New Software Features in Cisco IOS Release 12.3(13a)BC3

New Hardware Features in Cisco IOS Release 12.3(13a)BC2

New Software Features in Cisco IOS Release 12.3(13a)BC2

New Hardware Features in Cisco IOS Release 12.3(13a)BC1

New Software Features in Cisco IOS Release 12.3(13a)BC1

New Hardware Features in Cisco IOS Release 12.3(13a)BC

Cisco Half-Height Gigabit Ethernet Line Card

Processor/IO Memory for the PRE1 Route Processor Module

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

New Software Features for Cisco IOS Release 12.3(13a)BC

Access Control List Support for COPS Intercept

Admission Control for the Cisco CMTS

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Backup Path Testing for the Cisco RF Switch

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

COPS TCP Support for the Cisco Cable Modem Termination System

cops ip dscp

cops tcp window-size

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

DOCSIS 1.0 Concatenation Override

DOCSIS BPI+ Multiple Root Certificate Support

Dynamic SID/VRF Mapping Support

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

High Availability Features

MIBs Enhancements

Multicast QoS Support on the Cisco uBR10012 CMTS

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Optional Upstream Scheduler Modes

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

PacketCable Multimedia for the Cisco CMTS

Service Independent Intercept (SII) Support

Transparent LAN Service and Layer 2 Virtual Private Networks

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

New Hardware Features in Cisco IOS Release 12.3(9a)BC9

New Software Features in Cisco IOS Release 12.3(9a)BC9

New Hardware Features in Cisco IOS Release 12.3(9a)BC8

New Software Features in Cisco IOS Release 12.3(9a)BC8

New Hardware Features in Cisco IOS Release 12.3(9a)BC7

New Software Features in Cisco IOS Release 12.3(9a)BC7

New Hardware Features in Cisco IOS Release 12.3(9a)BC6

New Software Features in Cisco IOS Release 12.3(9a)BC6

New Hardware Features in Cisco IOS Release 12.3(9a)BC5

New Software Features in Cisco IOS Release 12.3(9a)BC5

New Hardware Features in Cisco IOS Release 12.3(9a)BC4

New Software Features in Cisco IOS Release 12.3(9a)BC4

New Hardware Features in Cisco IOS Release 12.3(9a)BC3

New Software Features in Cisco IOS Release 12.3(9a)BC3

New Hardware Features in Cisco IOS Release 12.3(9a)BC2

New Software Features in Cisco IOS Release 12.3(9a)BC2

New Hardware Features in Cisco IOS Release 12.3(9a)BC1

New Software Features in Cisco IOS Release 12.3(9a)BC1

New Hardware Features in Cisco IOS Release 12.3(9a)BC

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

DOCSIS System Interoperability on the Cisco uBR10012 CMTS

New Software Features for Cisco IOS Release 12.3(9a)BC

Cable ARP Filter Enhancement

Cisco Broadband Troubleshooter 3.2

Cisco CMTS Static CPE Override

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

DOCSIS Set-Top Gateway Issue 1.0

Dynamic Shared Secret (DMIC) with OUI Exclusion

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

CISCO-CABLE-METERING-MIB

Additional Information

CISCO-CABLE-QOS-MONITOR MIB

CISCO-CABLE-SPECTRUM-MIB

CISCO-ENHANCED-MEMPOOL-MIB

CISCO-PROCESS-MIB

DOCS-QOS-MIB

DSG-IF-MIB

NetFlow Accounting Versions 5 and 8 Support

NetFlow Version 5 Features and Format

NetFlow Version 8 Features and Format

Additional Information about NetFlow on the Cisco CMTS

PacketCable 1.0 With CALEA

SFID Support for Multicast and Cable Interface Bundling

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Subscriber Traffic Management (STM) Version 1.1

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Usage Based Billing (SAMIS)

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

MIBs

MIB Changes and Enhancements for Cisco IOS Release 12.3(21)BC:

MIB Constraints and Notes

MIB Changes and Enhancements for Cisco IOS Release 12.3(17a)BC:

Important Notes

How to Upgrade to Cisco IOS Release 12.3(21)BC

Symptoms of Corrupted NVRAM

Conditions of Corrupted NVRAM

New Command Information for Cisco IOS Release 12.3(21)BC

cable throttle-ranging

card

clear cable modem reset

hw-module reload

hw-module shutdown

show cable modem summary

show cable modem wideband

show interface wideband-cable

Restrictions for Cisco IOS Release 12.3(17a)BC

New Command Information for Cisco IOS Release 12.3(13a)BC3

debug cable classifiers

New Command Information for Cisco IOS Release 12.3(13a)BC2

cable service flow activity-timeout

Restrictions for Cisco IOS Release 12.3(13a)BC

Restrictions for Cisco IOS Release 12.3(9a)BC

New and Changed Command Reference for Cisco IOS Release 12.3(9a)BC

cable logging layer2events

cable source-verify

cable submgmt default

show cable tech-support

show controllers cable

show tech-support

Caveats for Cisco IOS Release 12.3 BC

Open Caveats for Release 12.3(23)BC10

Resolved Caveats for Release 12.3(23)BC10

Open Caveats for Release 12.3(23)BC9

Resolved Caveats for Release 12.3(23)BC9

Open Caveats for Release 12.3(21a)BC9

Resolved Caveats for Cisco 12.3(21a)BC9

Open Caveats for Release 12.3(23)BC8

Resolved Caveats for Release 12.3(23)BC8

Open Caveats for Release 12.3(23)BC7

Resolved Caveats for Release 12.3(23)BC7

Open Caveats for Release 12.3(23)BC6

Resolved Caveats for Release 12.3(23)BC6

Open Caveats for Release 12.3(23)BC5

Resolved Caveats for Release 12.3(23)BC5

Open Caveats for Release 12.3(23)BC4

Resolved Caveats for Release 12.3(23)BC4

Open Caveats for Release 12.3(21a)BC8

Resolved Caveats for Release 12.3(21a)BC8

Open Caveats for Release 12.3(23)BC3

Resolved Caveats for Release 12.3(23)BC3

Open Caveats for Release 12.3(23)BC2

Resolved Caveats for Release 12.3(23)BC2

Open Caveats for Release 12.3(21a)BC7

Resolved Caveats for Release 12.3(21a)BC7

Open Caveats for Release 12.3(23)BC1

Resolved Caveats for Release 12.3(23)BC1

Open Caveats for Release 12.3(21a)BC6

Resolved Caveats for Release 12.3(21a)BC6

Open Caveats for Release 12.3(21a)BC5

Resolved Caveats for Release 12.3(21a)BC5

Open Caveats for Release 12.3(23)BC

Resolved Caveats for Release 12.3(23)BC

Open Caveats for Release 12.3(21a)BC4

Resolved Caveats for Release 12.3(21a)BC4

Open Caveats for Release 12.3(17b)BC9

Resolved Caveats for Release 12.3(17b)BC9

Open Caveats for Release 12.3(21a)BC3

Resolved Caveats for Release 12.3(21a)BC3

Open Caveats for Release 12.3(21a)BC2

Resolved Caveats for Release 12.3(21a)BC2

Open Caveats for Release 12.3(21a)BC1

Resolved Caveats for Release 12.3(21a)BC1

Open Caveats for Release 12.3(21)BC

Resolved Caveats for Release 12.3(21)BC

Open Caveats for Release 12.3(17b)BC8

Resolved Caveats for Release 12.3(17b)BC8

Open Caveats for Release 12.3(17b)BC7

Resolved Caveats for Release 12.3(17b)BC7

Open Caveats for Release 12.3(17b)BC6

Resolved Caveats for Release 12.3(17b)BC6

Open Caveats for Release 12.3(17b)BC5

Resolved Caveats for Release 12.3(17b)BC5

Open Caveats for Release 12.3(17b)BC4

Resolved Caveats for Release 12.3(17b)BC4

Open Caveats for Release 12.3(17b)BC3

Resolved Caveats for Release 12.3(17b)BC3

Open Caveats for Release 12.3(17a)BC2

Resolved Caveats for Release 12.3(17a)BC2

Open Caveats for Release 12.3(17a)BC1

Resolved Caveats for Release 12.3(17a)BC1

Open Caveats for Release 12.3(17a)BC

Resolved Caveats for Release 12.3(17a)BC

Open Caveats for Release 12.3(13a)BC6

Resolved Caveats for Release 12.3(13a)BC6

Open Caveats for Release 12.3(13a)BC5

Resolved Caveats for Release 12.3(13a)BC5

Open Caveats for Release 12.3(13a)BC4

Resolved Caveats for Release 12.3(13a)BC4

Open Caveats for Release 12.3(13a)BC3

Resolved Caveats for Release 12.3(13a)BC3

Open Caveats for Release 12.3(13a)BC2

Resolved Caveats for Release 12.3(13a)BC2

Open Caveats for Release 12.3(13a)BC1

Resolved Caveats for Release 12.3(13a)BC1

Open Caveats for Release 12.3(13a)BC

Resolved Caveats for Release 12.3(13a)BC

Open Caveats for Release 12.3(9a)BC9

Resolved Caveats for Release 12.3(9a)BC9

Open Caveats for Release 12.3(9a)BC8

Resolved Caveats for Release 12.3(9a)BC8

Open Caveats for Release 12.3(9a)BC7

Resolved Caveats for Release 12.3(9a)BC7

Open Caveats for Release 12.3(9a)BC6

Resolved Caveats for Release 12.3(9a)BC6

Open Caveats for Release 12.3(9a)BC5

Resolved Caveats for Release 12.3(9a)BC5

Open Caveats for Release 12.3(9a)BC4

Resolved Caveats for Release 12.3(9a)BC4

Open Caveats for Release 12.3(9a)BC3

Resolved Caveats for Release 12.3(9a)BC3

Open Caveats for Release 12.3(9a)BC2

Resolved Caveats for Release 12.3(9a)BC2

Open Caveats for Release 12.3(9a)BC1

Resolved Caveats for Release 12.3(9a)BC1

Open Caveats for Release 12.3(9a)BC

Resolved Caveats for Release 12.3(9a)BC

Documentation Updates

Changes

Related Documentation

Release-Specific Documents

Platform-Specific Documents

Feature Modules

Cisco Feature Navigator

Cisco IOS Software Documentation Set

Documentation Modules

Release 12.3 Documentation Set

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco uBR10012 Universal Broadband Router for Cisco IOS Release 12.3BC


Revised: February 28, 2011, OL-6760-49

The release notes for Cisco IOS Release 12.3BC for the Cisco uBR10012 universal broadband routers describe the enhancements and caveats for all releases in the cable-specific, early deployment, 12.3BC release trains. Some of the most recent releases in 12.3BC include 12.3(17b)BCx-, 12.3(21a)BCx-, and 12.3(23)BCx-based releases.

These release notes are updated with each release in the train. For a list of the software caveats that apply to Cisco IOS Release 12.3(23)BC8, see the "Caveats for Cisco IOS Release 12.3 BC" section and Caveats for Cisco IOS Release 12.3 T. Use these release notes in conjunction with the cross-platform Release Notes for Cisco IOS Release 12.3T located on Cisco.com and the Documentation CD-ROM.

Use these release notes with Cross-Platform Release Notes for Cisco IOS Release 12.3 T located on Cisco.com.

Cisco recommends that you view the field notices for this release to see if your software or hardware platforms are affected. If you have an account on Cisco.com, you can find field notices at http://www.cisco.com/en/US/customer/support/tsd_products_field_notice_summary.html. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/en/US/support/tsd_products_field_notice_summary.html.

Contents

These release notes describe the following topics:

Early Deployment Releases

System Requirements

DOCSIS System Interoperability on the Cisco uBR10012 CMTS

Feature Set Tables

New and Changed Information

MIBs

Important Notes

Caveats for Cisco IOS Release 12.3 BC

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

Early Deployment Releases

These release notes describe the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.3(21a)BC9, which is an early deployment (ED) release based on Cisco IOS Release 12.3 T. Early deployment releases contain fixes for software caveats and support for new Cisco hardware and software features.

Table 1 shows recent early deployment releases for the CiscouBR10012 universal broadband router.

Table 1 Early Deployment Releases for the Cisco uBR10012 Universal Broadband Router 

ED Release
Additional Software Features
Additional Hardware Features
Availability

Cisco IOS Release 12.3(23)BC10

None

None

None

Cisco IOS Release 12.3(23)BC9

None

None

None

Cisco IOS Release 12.3(21a)BC9

None

None

None

Cisco IOS Release 12.3(23)BC8

None

None

None

Cisco IOS Release 12.3(23)BC7

SAMIS CLC-RP Traffic Throttling

M-CMTS Enhancement

Three Step Dynamic Modulation

Enhanced Show Tech

Cable Modem QoS Information

Direct Load for Cable Modems

The following commands are introduced in Cisco IOS Release 12.3(23)BC7:

show cable modem service-flow

cable upstream equalization-error-recovery

cable upstream threshold hysteresis

cable metering data-per-session

The following commands are modified in Cisco IOS Release 12.3(23)BC7:

show tech support

cable upstream modulation

show cable hop history

show cr10k-rp

show pxf cpu queue

show cable metering verbose

cable metering destination

See New Software Features in Cisco IOS Release 12.3(23)BC7 for details.

None

Now

Cisco IOS Release 12.3(23)BC6

The following command is modified in Cisco IOS Release 12.3(23)BC6:

show controllers modular-cable

See New Software Features in Cisco IOS Release 12.3(23)BC6 for details.

None

Now

Cisco IOS Release 12.3(23)BC5

The following command is modified in Cisco IOS Release 12.3(23)BC5:

show controllers modular-cable

See New Software Features in Cisco IOS Release 12.3(23)BC5 for details.

None

Now

Cisco IOS Release 12.3(23)BC4

None

None

Now

Cisco IOS Release 12.3(21a)BC8

None

None

Now

Cisco IO S Release 12.3(23)BC3

None

None

Now

Cisco IOS Release 12.3(23)BC2

Subscriber Traffic Management (STM) Version 1.2

Upstream Utilization Optimization

None

Now

Cisco IOS Release 12.3(21a)BC7

None

None

Now

Cisco IOS Release 12.3(23)BC1

PacketCable Subscriber ID Support

MxN MAC Domain DS Load Balancing

Line Card High Availability (HA) Support for WB Cable Modems

Bypass the 24 Hour Timer for WB CM Use of Failed RF Channels

Voice Support on WB Modems

Dynamic Bandwidth Sharing for Wideband and Modular Cable Interfaces

Cisco 1000BASE-T SFP Module

Now

Cisco IOS Release 12.3(21a)BC6

None

None

Now

Cisco IOS Release 12.3(21a)BC5

None

None

Now

Cisco IOS Release 12.3(23)BC

DOCSIS 3.0 Downstream Solution

DOCSIS Timing & Control Card (DTCC)

Now

Cisco IOS Release 12.3(21a)BC4

None

None

Now

Cisco IOS Release 12.3(17b)BC9

None

None

Now

Cisco IOS Release 12.3(21a)BC3

Control Point Discovery (CPD)

None

Now

Cisco IOS Release 12.3(21a)BC2

None

None

Now

Cisco IOS Release 12.3(21a)BC1

None

None

Now

Cisco IOS Release 12.3(21)BC

Automatic Virtual Interface Bundles

Cable DHCP Enhancements

Cable Duplicate MAC Address Reject

DOCSIS 3.0 Downstream Channel Bonding

Enhanced Rate Bandwidth Allocation (ERBA) on the Cisco uBR10012 Router

HCCP Switchover Enhancements

NSF Lite

PacketCable Client Accept Timeout

Per Downstream Static Multicast

RF Switch Firmware Version 3.60

Service Flow Admission Control

Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia

Cisco Wideband SIP

Cisco Wideband SPA

Now

Cisco IOS Release 12.3(17b)BC8

None

None

Now

Cisco IOS Release 12.3(17b)BC7

None

None

Now

Cisco IOS Release 12.3(17b)BC6

None

None

Now

Cisco IOS Release 12.3(17b)BC5

None

None

Now

Cisco IOS Release 12.3(17b)BC4

Downstream Load Balancing Distribution with Upstream Load Balancing

None

Now

Cisco IOS Release 12.3(17b)BC3

None

None

Now

Cisco IOS Release 12.3(17a)BC2

Cisco Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS

DOCSIS1.0 TOS Overwrite

None

Now

Cisco IOS Release 12.3(17a)BC1

None

None

Now

Cisco IOS Release 12.3(17a)BC

Cable Monitor Enhancements

CNEM Compliance

Dynamic Channel Change (DCC) for Load Balancing

DOCSIS 2.0 SAMIS ECR Data Set

DSX Messages and Synchronized PHS Information

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

High Availability Support for Encrypted IP Multicast

Management Information Base (MIB) Changes and Enhancements

Pre-equalization Control for Cable Modems

PXF ARP Filter

PXF Divert Rate Limiting

SAMIS Source Address Management

Secure Socket Layer Server for Usage-Based Billing

SSM Mapping

None

Now

Cisco IOS Release 12.3(13a)BC6

None

None

Now

Cisco IOS Release 12.3(13a)BC5

None

None

Now

Cisco IOS Release 12.3(13a)BC4

None

None

Now

Cisco IOS Release 12.3(13a)BC3

None

None

Now

Cisco IOS Release 12.3(13a)BC2

None

None

Now

Cisco IOS Release 12.3(13a)BC1

None

None

Now

Cisco IOS Release 12.3(13a)BC

Access Control List Support for COPS Intercept

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Backup Path Testing for the Cisco RF Switch

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

COPS TCP Support for the Cisco Cable Modem Termination System

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

DOCSIS 1.0 Concatenation Override

DOCSIS BPI+ Multiple Root Certificate Support

Dynamic SID/VRF Mapping Support

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

High Availability Features:

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Global N+1 Redundancy

Shutdown and No Shutdown Enhancement for Cable Interfaces

Low Latency Queuing (LLQ), see Optional Upstream Scheduler Modes

Multicast QoS Support on the Cisco uBR10012 CMTS

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Optional Upstream Scheduler Modes

Cisco Half-Height Gigabit Ethernet Line Card

Now

 

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

PacketCable Multimedia for the Cisco CMTS

Service Independent Intercept (SII) Support

Subinterface support in ifTable Object

Transparent LAN Service and Layer 2 Virtual Private Networks

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

   

Cisco IOS Release 12.3(9a)BC9

None

None

Now

Cisco IOS Release 12.3(9a)BC8

None

None

Now

Cisco IOS Release 12.3(9a)BC7

None

None

Now

Cisco IOS Release 12.3(9a)BC6

None

None

Now

Cisco IOS Release 12.3(9a)BC5

None

None

Now

Cisco IOS Release 12.3(9a)BC4

None

None

Now

Cisco IOS Release 12.3(9a)BC3

None

None

Now

Cisco IOS Release 12.3(9a)BC2

None

None

Now

Cisco IOS Release 12.3(9a)BC1

None

None

Now

Cisco IOS Release 12.3(9a)BC

Cable ARP Filter Enhancement

Cisco Broadband Troubleshooter 3.2

Cisco CMTS Static CPE Override

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

DOCSIS Set-Top Gateway Issue 1.0

Dynamic Shared Secret (DMIC) with OUI Exclusion

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

NetFlow Accounting Versions 5 and 8 Support

PacketCable 1.0 With CALEA

SFID Support for Multicast and Cable Interface Bundling

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Subscriber Traffic Management (STM) Version 1.1

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Usage Based Billing (SAMIS)

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

DOCSIS System Interoperability on the Cisco uBR10012 CMTS

Now


System Requirements

This section describes the system requirements for Cisco IOS Release upto 12.3(23)BC8 and includes the following sections:

Memory Recommendations

Supported Hardware

Determining the Software Version

Determining the Software Version

Upgrading to a New Software Release

Feature Set Tables

Memory Recommendations

Table 2 Memory Recommendations for the Cisco uBR10012 Universal Broadband Router 

Platforms
Feature Sets
Cisco uBR10012 Route Processor
Software Image
Flash
Memory
Recommended
DRAM
Memory
Recommended
Runs
From

Cisco uBR10012

DOCSIS BPI IP Plus

PRE1

ubr10k-k8p6-mz

48 MB

512 MB

RAM

PRE2

ubr10k2-k8p6-mz

48 MB

1.0 GB

RAM

DOCSIS Base 3 DES

PRE1

ubr10k-k9p6-mz

48 MB

512 MB

RAM

PRE2

ubr10k2-k9p6-mz

48 MB

1.0 GB

RAM


Supported Hardware

This section describes the hardware supported by the Cisco uBR10012 Universal Broadband Router in Cisco IOS Release 12.3(21a)BC9.

For detailed descriptions of the new hardware features, see the "New and Changed Information" section.

Table 3 provides the list of hardware supported by the Cisco uBR10012 Universal Broadband Router.

.

Table 3 Cisco uBR10012 Universal Broadband Router Supported Hardware 

Cable Interface Line Cards

Up to eight of the following broadband processing engines and cable interface line cards can be housed in a chassis in any combination:

Cisco uBR10-MC5X20S/U/H Cable Interface Line Card

Cisco uBR10-LCP2-MC16C/MC16E/MC16S Cable Interface Line Card

Cisco uBR10-LCP2-MC28C Cable Interface Line Card

Note The Cisco uBR10-LCP2-MC16C/MC16E/MC16S and the Cisco uBR10-LCP2-MC28C are end of sale as of June 2005. For additional information, refer to END-OF-LIFE NOTICE, NO. 2600:

http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_end-of-life_notice0900aecd80183921.html

Note The Cisco uBR7200 Series MC28U BPE does not support the Cisco uBR10012 router, though the Cisco MC28U BPE physically fits into the Cisco uBR10012 router chassis.

Cisco Half-Height Gigabit Ethernet Line Card

The Gigabit Ethernet (GigE) line card is a half-height, single-port, full-bandwidth Gigabit Ethernet line card providing multiple GigE links to the IP backbone. The Cisco half-height GigE line card also supports DOCSIS wideband capability through the Cisco uBR10000 universal broadband router.

Network Uplink Line Cards

Up to four line cards with any combination of the following WAN choices:

Cisco uBR10-SRP-OC12SML DPT WAN Line Card for the Cisco uBR10012 Router

Cisco uBR10012 OC-48 DPT/POS interface module

Cisco uBR10-1GE Gigabit Ethernet (GigE) uplink line card

Cisco uBR10-1OC12/P-SMI OC-12 POS uplink line card

Cisco uBR10-SRP-OC12SML Dynamic Packet Transport (DPT) WAN card

Timing, Communication and Control Plus (TCC+) Card

The TCC+ card can connect to an external reference Stratum 3 clock source that is traceable to a Stratum 1 source. Two such sources can be connected for redundancy.

The TCC+ card also monitors the cable line cards and power supply use, as well as control the LCD display screen on the chassis. Two cards can be installed for redundancy.

Performance Routing Engine 2 (PRE2)

The new Cisco uBR10012 Series PRE2 effectively doubles the bandwidth available to each slot on the router as supported by cable interface line cards or Cisco Broadband Processing Engines.

The PRE2 module introduces support for full-duplex Gigabit Ethernet ports, and increases the supported connections to 1.6 Gbps in full duplex (each direction per half-slot). Full-slot modules can now have up to 3.2 Gbps to and from the PRE2 module. This is twice the connection rate of the Cisco uBR10012 PRE1 route processor module.

Performance Routing Engine (PRE or PRE1)

One PRE or PRE1 module performs layer 2 and layer 3 packet processing, as well as routing and system management functions. Two PRE or PRE1 modules can be installed for redundancy.

Note The PRE1 module is functionally identical to the PRE module except that it adds support for the Error Checking and Correction (ECC) feature, which can automatically correct single-bit memory errors.

Note The Cisco uBR10012 PRE1 module supports an Ethernet port to a LAN for a 10BASE-T or 100BASE-T connection for network management. The PRE1 module supports connections of 800 Mbps in full duplex (each direction) per half-slot.

AC-Input Power Entry Module (PEM)

The Cisco uBR10012 router ships with two AC power entry modules (AC PEMs) that provide a redundant power supply to the system. One AC PEM can provide sufficient power for a fully configured chassis, so that if one AC PEM fails, the other automatically begins providing power for the entire router, without impacting system operations.

The AC PEMs use standard 200-240 VAC (50/60 Hz) input power obtained through power receptacles on the front panel of each PEM. The two AC PEMs convert the AC power to provide filtered, redundant, and load shared DC power to the Cisco uBR10012 chassis.


Caution The Cisco uBR10012 router does not support mixing AC and DC PEMs. Both PEMs must be either AC PEMs or DC PEMs.

DC-input Power Entry Module (PEM)

The Cisco uBR10012 router may ship with two DC PEMs to provide power to the chassis. The use of two PEMs provide power balancing and redundancy, as well as the ability to hot-swap a single power supply when needed.


Caution The Cisco uBR10012 router does not support mixing AC and DC PEMs. Both PEMs must be either AC PEMs or DC PEMs.

Fan Assembly Module

The fan assembly module contains four fans that are capable of cooling the chassis even with the failure of a single fan. The fan assembly is dual-speed, providing additional cooling when the chassis temperature exceeds the nominal operating range.



Note The Cisco uBR10012 router is compatible with Cisco Broadband Troubleshooter 3.2 and Cisco Cable Manager 2.3.


DOCSIS System Interoperability on the Cisco uBR10012 CMTS

This section describes the operation of primary interoperability features in the Cisco uBR10012 router. For additional DOCSIS information, refer to the following document on Cisco.com:

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

Cisco IOS Release 12.3(13a)BC and DOCSIS 1.1 System Interoperability

Cisco IOS Release 12.3(13a)BC and earlier releases in this release train support several powerful new features for the Cisco uBR10012 CMTS. In addition to maintaining DOCSIS support from earlier Cisco IOS releases, Cisco IOS Release 12.3(13a)BC enhances DOCSIS support in these general categories:

Admission Control and other features for enhanced DOCSIS Quality of Service, as provisioned by CableLabs® DOCSIS 1.1 and DOCSIS 2.0 Interface Specifications:

http://www.cablemodem.com/specifications/specifications20.html 

Advanced-mode DOCSIS Set-top Gateway (A-DSG) 1.1, as provisioned by CableLabs® DOCSIS Set-top Gateway (DSG) Interface Specification, through SP-a-I03-041124, in a status of "Issued(03):

http://www.cablelabs.com/cablemodem/specifications/gateway.html

CableLabs® PacketCable 1.0 and 1.5 Support for Emergency Services and Voice

http://www.cablelabs.com/packetcable/specifications/ 

CableLabs® PacketCable Multimedia (PCMM):

PacketCable Multimedia Specification, PKT-SP-MM-I02-040930

http://www.cablelabs.com/packetcable/specifications/multimedia.html 

Additional High Availability and Security features as described elsewhere in this document.

DOCSIS 1.0 Baseline Privacy

DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and cable modem. BPI ensures that a cable modem, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for services only it is authorized to access.

To enable BPI, choose software at both the CMTS and cable modem that support this mode of operation. Select a Cisco IOS image that supports BPI. BPI must be enabled using the DOCSIS configuration file.

The cable modem must also support BPI. Cable modems must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment.


Note RSA stands for Rivest, Shamir, and Adelman, inventors of a public-key cryptographic system.


Cable Modem Interoperability

The Cisco uBR10012 router supports DOCSIS 1.1-based, two-way interoperability for cable modems that support basic Internet access, Voice over IP (VoIP), or Virtual Private Networks (VPNs).

EuroDOCSIS cable modems or set-top boxes (STBs) with integrated EuroDOCSIS CMs using Cisco uBR-MC16E cable interface line cards and Cisco IOS Release 12.2(4)BC1 or higher. EuroDOCSIS operation support includes 8-MHz Phase Alternating Line (PAL) or Systeme Electronique Couleur Avec Memoire (SECAM) channel plans.

DOCSIS 1.0 and 1.0+ Extensions

Earlier releases of Cisco IOS software for the uBR10012 router provide support for the original DOCSIS 1.0 standard, featuring basic best-effort data traffic and Internet access over the coaxial cable network. The DOCSIS 1.0+ extensions provides Quality of Service (QoS) enhancements for real-time traffic, such as voice calls, in anticipation of full DOCSIS 1.1 support.


Note All DOCSIS 1.0 extensions are activated only when a cable modem or Cisco uBR924 that supports these extensions solicits services using dynamic MAC messages or the feature set. If the cable modems in your network are pure DOCSIS 1.0-based, they receive regular DOCSIS 1.0 treatment from the Cisco CMTS.


DOCSIS 1.1 Extensions

The DOCSIS 1.1 specification provides the following functional enhancements over DOCSIS 1.0 coaxial cable networks:

Enhanced Quality of Service (QoS) gives priority for real-time traffic such as voice and video.

The DOCSIS 1.0 QoS model (a Service IDs (SID) associated with a QoS profile) has been replaced with a service flow model (SFID). This allows greater flexibility in assigning QoS parameters to different types of traffic and in responding to changing bandwidth conditions.

Multiple service flows per cable modem supported in either direction due to packet classifiers.

Support for multiple service flows per cable modem allows a single cable modem to support a combination of data, voice, and video traffic.

Greater granularity is available in QoS per cable modem (in either direction), using unidirectional service flows.

Dynamic MAC messages are supported to create, modify, and tear down QoS service flows dynamically when requested by a DOCSIS 1.1 cable modem.

Several QoS models are supported for the upstream.

Best effort-Data traffic is sent on a non-guaranteed best-effort basis.

Committed Information Rate (CIR) supports the guaranteed minimum bandwidth for data traffic.

Unsolicited Grants (UGS) support constant bit rate (CBR) traffic, such as voice, that is characterized by fixed size packets at fixed intervals.

Real Time Polling (rtPS) supports Real Time service flows, such as video, that produce unicast, variable size packets at fixed intervals.

Unsolicited Grants with Activity Detection (USG-AD) support the combination of UGS and RTPS, to accommodate real time traffic that might have periods of inactivity (such as voice using silence suppression). The service flow uses UGS fixed grants while active, but switches to RTPS polling during periods of inactivity to avoid wasting unused bandwidth.

Enhanced time-slot scheduling mechanisms support guaranteed delay/jitter sensitive traffic on the shared multiple access upstream link.

Payload header suppression (PHS) conserves link-layer bandwidth by suppressing unnecessary packet headers on both upstream and downstream traffic flows.

Layer 2 fragmentation on the upstream prevents large data packets from affecting real-time traffic, such as voice and video. Large data packets are fragmented and then transmitted in the time slots that are available between the time slots used for the real-time traffic.

Concatenation allows a cable modem to send multiple MAC frames in the same time slot, as opposed to making an individual grant request for each frame. This avoids wasting upstream bandwidth when sending a number of very small packets, such as TCP acknowledgement packets.

DOCSIS 1.1 cable modems can coexist with DOCSIS 1.0 and 1.0+ cable modems in the same network—the Cisco uBR10012 router provides the levels of service that are appropriate for each cable modem.

DOCSIS 1.1 Quality of Service

The DOCSIS 1.1 QoS framework is based on the following objects:

Service class: A collection of settings maintained by the CMTS that provide a specific QoS service tier to a cable modem that has been assigned a service flow within a particular service class.

Service flow: a unidirectional sequence of packets receiving a service class on the DOCSIS link.

Packet classifier: A set of packet header fields used to classify packets onto a service flow to which the classifier belongs.

PHS rule: A set of packet header fields that are suppressed by the sending entity before transmitting on the link, and are restored by receiving entity after receiving a header-suppressed frame transmission. Payload header suppression increases the bandwidth efficiency by removing repeated packet headers before transmission.

In DOCSIS 1.1, the basic unit of QoS is the service flow, which is a unidirectional sequence of packets transported across the RF interface between the cable modem and CMTS. A service flow is characterized by a set of QoS parameters such as latency, jitter, and throughput assurances.

Every cable modem establishes a primary service flow in both the upstream and downstream directions. The primary flows maintain connectivity between the cable modem and CMTS at all times.

In addition, a DOCSIS 1.1 cable modem can establish multiple secondary service flows. The secondary service flows can either be permanently created (they persist until the cable modem is reset or powered off) or they can be created dynamically to meet the needs of the on demand traffic being transmitted.

Each service flow has a set of QoS attributes associated with it. These QoS attributes define a particular class of service and determine characteristics such as the maximum bandwidth for the service flow and the priority of its traffic. The class of service attributes can be inherited from a preconfigured CMTS local service class (class-based flows), or they can be individually specified at the time of the creation of the service flow.

Each service flow has multiple packet classifiers associated with it, which determine the type of application traffic allowed to be sent on that service flow. Each service flow can also have a Payload header suppression (PHS) rule associated with it to determine which portion of the packet header will be suppressed when packets are transmitted on the flow.

Determining the Software Version

To determine the version of Cisco IOS software running on your Cisco uBR10012 universal broadband router, log in to the Cisco uBR10012 universal broadband router and enter the show version EXEC command:

Router> show version
Cisco Internetwork Operating System Software 
IOS (tm) Software (uBR10k-k8p6-mz), Version 12.3(17b)BC9, EARLY DEPLOYMENT RELEASE 
SOFTWARE

Upgrading to a New Software Release

For information about selecting a new Cisco IOS software release, please refer to How to Choose a Cisco IOS Software Release at:

http://www.cisco.com/en/US/partner/products/sw/iosswrel/ps1834/products_tech_note09186a00800fb9d9.shtml

For information about upgrading to a new software release, refer to the appropriate platform-specific document:

Cisco uBR10012 Series Universal Broadband Routers

http://www.cisco.com/en/US/partner/docs/interfaces_modules/shared_port_adapters/configuration/ubr10012/12.3_21_bc/swsipspa_book.html 

For Cisco IOS Upgrade Ordering Instructions, refer to the document at the following location:

http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm

To choose a new Cisco IOS software release by comparing feature support or memory requirements, use Cisco Feature Navigator. Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS and Catalyst OS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.

Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:

http://www.cisco.com/go/fn

To choose a new Cisco IOS software release based on information about defects that affect that software, use Bug Toolkit at:

http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

Feature Set Tables

Cisco IOS software is packaged in feature sets that consist of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. Each feature set contains a specific set of Cisco IOS features.


Caution Cisco IOS images with strong encryption (including, but not limited to 168-bit (3DES) data encryption feature sets) are subject to U.S. government export controls and have limited distribution. Strong encryption images to be installed outside the United States are likely to require an export license. Customer orders may be denied or subject to delay because of U.S. government regulations. When applicable, the purchaser/user must obtain local import and use authorizations for all encryption strengths. Please contact your sales representative or distributor for more information, or send an e-mail to export@cisco.com.

The feature set tables have been removed from the Cisco IOS Release 12.3 release notes to improve the usability of the release notes documentation. The feature-to-image mapping that was provided by the feature set tables is available through Cisco Feature Navigator.

Cisco Feature Navigator is a web-based tool that enables you to determine which Cisco IOS software images support a specific set of features and which features are supported in a specific Cisco IOS image. You can search by feature or by feature set (software image). Under the release section, you can compare Cisco IOS software releases side by side to display both the features unique to each software release and the features that the releases have in common.

To access Cisco Feature Navigator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://www.cisco.com/web/siteassets/account/index.html

Cisco Feature Navigator is updated regularly when major Cisco IOS software releases and technology releases occur. For the most current information, go to the Cisco Feature Navigator home page at the following URL:

http://www.cisco.com/go/fn 

For frequently asked questions about Cisco Feature Navigator, see the FAQs at the following URL:

http://www.cisco.com/support/FeatureNav/FNFAQ.html 

Determining Which Software Images (Feature Sets) Support a Specific Feature

To determine which software images (feature sets) in Cisco IOS Release 12.3 support a specific feature, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:


Step 1 From the Cisco Feature Navigator home page, click Feature.

Step 2 To find a feature, use either "Search by full or partial feature name" or "Browse features in alphabetical order." Either a list of features that match the search criteria or a list of features that begin with the number or letter selected from the ordered list will be displayed in the text box on the left side of the web page.

Step 3 Select a feature from the left text box, and click the Add button to add a feature to the Selected Features text box on the right side of the web page.


Note To learn more about a feature in the list, click the Description button below the left box.


Repeat this step to add additional features. A maximum of 20 features can be chosen for a single search.

Step 4 Click Continue when you are finished selecting features.

Step 5 From the Major Release drop-down menu, choose 12.3.

Step 6 From the Release drop-down menu, choose the appropriate maintenance release.

Step 7 From the Platform Family drop-down menu, select the appropriate hardware platform. The "Your selections are supported by the following:" table will list all the software images (feature sets) that support the feature(s) that you selected.


Determining Which Features Are Supported in a Specific Software Image (Feature Set)

To determine which features are supported in a specific software image (feature set) in Cisco IOS Release 12.3, go to the Cisco Feature Navigator home page, enter your Cisco.com login, and perform the following steps:


Step 1 From the Cisco Feature Navigator home page, click Compare/Release.

Step 2 In the "Find the features in a specific Cisco IOS release, using one of the following methods:" box, choose 12.3 from the Cisco IOS Major Release drop-down menu.

Step 3 Click Continue.

Step 4 From the Release drop-down menu, choose the appropriate maintenance release.

Step 5 From the Platform Family drop-down menu, choose the appropriate hardware platform.

Step 6 From the Feature Set drop-down menu, choose the appropriate feature set. The "Your selections are supported by the following:" table will list all the features that are supported by the feature set (software image) that you selected.


New and Changed Information

The following sections list the new hardware and software features supported by the Cisco uBR10012 router for Cisco IOS Release 12.3(21a)BC9:

For more information about these features, refer to the documents listed in the "Related Documentation" section.

New Hardware Features in Cisco IOS Release 12.3(23)BC10

There are no new hardware features in Cisco IOS Release 12.3(23)BC10.

New Software Features in Cisco IOS Release 12.3(23)BC10

There are no new software features in Cisco IOS Release 12.3(23)BC10.

New Hardware Features in Cisco IOS Release 12.3(23)BC9

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC9.

New Software Features in Cisco IOS Release 12.3(23)BC9

There are no new software features supported in Cisco IOS Release 12.3(23)BC9.

Open Source Software Licenses for Cisco Universal Broadband Routers

For information on Open Source Software License MPL 1.1, refer to the following URL:

http://www.cisco.com/en/US/docs/cable/cmts/license/cable_licensing.html

New Hardware Features in Cisco IOS Release 12.3(21a)BC9

There is no new hardware feature supported in Cisco IOS Release 12.3(21a)BC9.

New Software Features in Cisco IOS Release 12.3(21a)BC9

There is no new software feature supported in Cisco IOS Release 12.3(21a)BC9.

New Hardware Features in Cisco IOS Release 12.3(23)BC8

There is no new hardware feature supported in Cisco IOS Release 12.3(23)BC8.

New Software Features in Cisco IOS Release 12.3(23)BC8

There is no new software feature supported in Cisco IOS Release 12.3(23)BC8.

New Hardware Features in Cisco IOS Release 12.3(23)BC7

There is no new hardware feature supported in Cisco IOS Release 12.3(23)BC7.

New Software Features in Cisco IOS Release 12.3(23)BC7

The following software features are new in Cisco IOS Release 12.3(23)BC7.

SAMIS CLC-RP Traffic Throttling

The SAMIS CLC-RP traffic throttling feature limits or throttles the data collection between the cable line card and the route processor. This functionality is achieved using the new cable metering data-per-session command. This feature also reduces the congestion in the Broadband Processing Engine (BPE) due to the SAMIS data collection from CLC to RP.

The following commands are new or modified:

cable metering data-per-session

show cable metering verbose

cable metering destination

M-CMTS Enhancement

The following commands are modified in Cisco IOS Release 12.3(23)BC7. The commands are upgraded to provide better display of the route processor service flow and queue information.

show cr10k-rp

show pxf cpu queue

Three Step Dynamic Modulation

Cisco IOS Release 12.3(33)BC7 introduces Three Step Dynamic Modulation, which allows you to create and use a third modulation profile in the Dynamic Upstream Modulation feature, as against the existing 16-QAM and quadrature phase-shift keying (QPSK) modulation profiles. The feature now permits 64-QAM based modulation profile to increase the upstream throughput and to satisfy the demand for new spectrum management.

The 64-QAM modulation profile is a more bandwidth-efficient modulation scheme and has a higher throughput than the other two modulation profiles.

For more details on Three Step Dynamic Modulation and the Dynamic Upstream Modulation feature, refer to Spectrum Management and Advanced Spectrum Management for the Cisco CMTS guide at the following location: http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html.

The Cisco IOS Release 12.3(23)BC7 introduces or modifies the following commands:

The cable upstream threshold hysteresis command was introduced to allow configurable hysteresis values for spectrum management channel upgrade thresholds.

The cable upstream modulation command was enhanced to accept up to three profiles, instead of the existing two.

The show cable hop history command was enhanced to display the modulation profile number when a change occurs.

Enhanced Show Tech

A new keyword, cmts, has been added to the show tech-support command to provide debugging information specific to a cable interface or a modem for the following universal broadband routers:

Cisco uBR10012 router

Cisco uBR7200 series

Cisco uBR7225VXR router

For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:

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

Cable Modem QoS Information

A new command, show cable modem service-flow, is introduced to provide information about all service flows associated with a particular modem.

For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:

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

Direct Load for Cable Modems

A new command, cable upstream equalization-error-recovery, is introduced to enable the CMTS to send Type-Length-Value (TLV) Type 9 in the DOCSIS RNG-RSP MAC management messages. The TLV Type 9 helps CMs come online if the TLV Type 4 convolved method causes CMs to go offline.

For details about this command, see the Cisco IOS CMTS Cable Command Reference at the following URL:

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

New Hardware Features in Cisco IOS Release 12.3(23)BC6

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC6.

New Software Features in Cisco IOS Release 12.3(23)BC6

The following command is modified in Cisco IOS Release 12.3(23)BC6:

show controllers modular-cable

The command output was modified to capture the SPA sensor temperature readings and error packet information.

The error information contains details about the:

Timestamp of the captured error packet.

Interrupt state which indicates the error type.

Packet length.

Blaze header part of the packet.

For additional information about this or other commands, refer to the Cisco IOS CMTS Cable Command Reference at http://www.cisco.com/en/US/docs/ios/cable/command/reference/cbl_book.html

New Hardware Features in Cisco IOS Release 12.3(23)BC5

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC5.

New Software Features in Cisco IOS Release 12.3(23)BC5

The following command is modified in Cisco IOS Release 12.3(23)BC5:

show controllers modular-cable

The command output was modified to capture the SPA sensor temperature readings and error packet information.

The error information contains details about the:

Timestamp of the captured error packet.

Interrupt state which indicates the error type.

Packet length.

Blaze header part of the packet.

New Hardware Features in Cisco IOS Release 12.3(23)BC4

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC4.

New Software Features in Cisco IOS Release 12.3(23)BC4

There are no new software features supported in Cisco IOS Release 12.3(23)BC4.

New Hardware Features in Cisco IOS Release 12.3(21a)BC8

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC8.

New Software Features in Cisco IOS Release 12.3(21a)BC8

There are no new software features supported in Cisco IOS Release 12.3(21a)BC8.

New Hardware Features in Cisco IOS Release 12.3(23)BC3

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC3.

New Software Features in Cisco IOS Release 12.3(23)BC3

There are no new software features supported in Cisco IOS Release 12.3(23)BC3.

New Hardware Features in Cisco IOS Release 12.3(23)BC2

There are no new hardware features supported in Cisco IOS Release 12.3(23)BC2.

New Software Features in Cisco IOS Release 12.3(23)BC2

The following software features are new in Cisco IOS Release 12.3(23)BC2.

Subscriber Traffic Management (STM) Version 1.2

The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM is a simple bandwidth management tool which works as a low CPU alternative to Network-Based Application Recognition (NBAR) and access control lists (ACLs), however, using STM does not mean that NBAR and ACLs have to be turned off; STM can be applied along with NBAR and ACLs. STM also works in conjunction with the Cisco Broadband Troubleshooter to support additional network management and troubleshooting functions in the Cisco CMTS.

The STM Version 1.2 feature is enhanced in Cisco IOS Release 12.3(23)BC2 with the following support on the Cisco uBR7246VXR and Cisco uBR10012 Universal Broadband Routers:

Support was added for the Cisco Wideband SPA (Cisco uBR10012 router only).

Support for suspension of the cable modem (CM) penalty period at a certain time of day.

Support for weekday and weekend traffic monitoring.

Support of up to 40 total enforce rules.

Support for service providers to change subscriber service classes for a particular modem using the cable modem service-class-name command.

Addition of the following SNMP objects to the CISCO-CABLE-QOS-MONITOR-MIB:

ccqmCmtsEnfRulePenaltyEndTime

ccqmCmtsEnfRuleWkndOff

ccqmCmtsEnfRuleWkndMonDuration

ccqmCmtsEnfRuleWkndAvgRate

ccqmCmtsEnfRuleWkndSampleRate

ccqmCmtsEnfRuleWkndFirstPeakTime

ccqmCmtsEnfRuleWkndFirstDuration

ccqmCmtsEnfRuleWkndFirstAvgRate

ccqmCmtsEnfRuleWkndSecondPeakTime

ccqmCmtsEnfRuleWkndSecondDuration

ccqmCmtsEnfRuleWkndSecondAvgRate

ccqmCmtsEnfRuleWkndOffPeakDuration

ccqmCmtsEnfRuleWkndOffPeakAvgRate

ccqmCmtsEnfRuleWkndAutoEnforce

The following commands are new or modified:

cable modem service-class-name

penalty-period

show cable qos enforce-rule verbose

weekend duration

weekend off

weekend peak-time1

For detailed information about this feature, see the Subscriber Traffic Management on the Cisco CMTS Routers document at:

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_sbsbr_tfmgt.html

Upstream Utilization Optimization

The Upstream (US) Utilization Optimization feature on the Cisco Cable Modem Termination System (CMTS) routers provides higher upstream throughput. It provides the following benefits and functions on a Cisco CMTS router:

Group configuration mode enables rate-adapt eligibility on all cable modem upstream flows.

Local configuration mode enables rate-adapt eligibility on a specific upstream, provides configuration of selective parameters, and provides that local configuration overrides any global configuration.

The following commands are new or modified:

cable upstream rate-adapt (global)

cable upstream rate-adapt (interface)

show cable rate-adapt

show interface cable sid

show interface cable upstream

For detailed information about this feature, see the Upstream Utilization Optimization on the Cisco CMTS Routers document at:

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_upstream_rate_adapt.html

New Hardware Features in Cisco IOS Release 12.3(21a)BC7

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC7.

New Software Features in Cisco IOS Release 12.3(21a)BC7

There are no new software features supported in Cisco IOS Release 12.3(21a)BC7.

New Hardware Features in Cisco IOS Release 12.3(23)BC1

The Cisco 1000BASE-T SFP module is introduced in Cisco IOS Release 12.3(23)BC1.

Cisco 1000BASE-T SFP Module

The Cisco 1000BASE-T SFP (Small Form-Factor Pluggable) module support for the Half-Height Gigabit Ethernet Line Card is introduced in Cisco IOS Release 12.3(23)BC1. SFP modules are input/output devices that plug into a Gigabit Ethernet (GE) port to interface with a fiber-optic or copper Ethernet media. The modules are used on Cisco platforms that have Gigabit Ethernet interfaces.The product ID of the Cisco 1000BASE-T SFP module is GLC-T.

The Cisco 1000BASE-T SFP connects a Cisco Gigabit Interface Converter (GBIC) port to Category 5, Category 5e and Category 6 wiring via a standard RJ-45 interface. The maximum Category 5 wiring distance is 100m. The module provides with an option of connecting to a backhaul network interface.

The SFP-GE-T is a Copper SFP supported on the Cisco Wideband SPA.The SFP-GE-T provides full-duplex Gigabit Ethernet connectivity to high-end workstations and between wiring closets over an existing copper network infrastructure. The SFP-GE-T maximum cabling distance is 328 feet (100 m).

For more information on the Cisco 1000BASE-T SFP, see http://www.cisco.com/en/US/docs/routers/7200/install_and_upgrade/gbic_sfp_modules_install/5067g.html

For more information on the Cisco 1000 BASE-T SFP-GE-T, see

http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/install_upgrade/uBR10012/ubrsov.html#wp1241789

New Software Features in Cisco IOS Release 12.3(23)BC1

The following software features are new in Cisco IOS Release 12.3(23)BC1.

PacketCable Subscriber ID Support

Subscriber ID is added to all Gate Control messages and enhances error codes returned from the Cable Modem Termination System (CMTS).

Previously, the Gate ID was unique only to individual CMTS systems, with the CMTS proxying all CMS (Call Management Server) Gate control messaging through a central device which manages the CMTS connections on the behalf of the CMS. The CMS had a single Common Open Policy Service (COPS) association to the proxy device. Therefore, the Gate IDs could be duplicated when using multiple CMTS systems.

The new PacketCable Subscriber ID feature adds a Subscriber ID to each Gate Control message to disambiguate the Gate IDs between the CMS and proxy device. The Subscriber ID parameter is added to the following COPS messages:

GATE-INFO

GATE-DELETE

GATE-OPEN

GATE-CLOSE

The Subscriber ID is available at the CMS and is used in the Gate-Set messages. Additionally, the error codes returned from CMTS or its proxy are enhanced to include more specific information about gate operation failures.

To enable this feature, a new command is introduced: packetcable gate send-subscriberID used in global configuration mode. For more information, see the Cisco IOS CMTS Cable Command Reference Guide.

MxN MAC Domain DS Load Balancing

Prior to the introduction of this new feature, load balancing configuration using the cable load-balance group policy (us-groups-across-ds) command only considered upstream (US) load balancing across different downstream (DS) channels. This was sufficient if an US channel was not associated to more than one DS channel. However, for an MxN MAC domain, it is possible to have one US channel associated to multiple DS channels. In this case, it is necessary to further balance the DS load, once the US load is sufficiently balanced.

With the new feature, once the us-groups-across-ds policy is configured, CMTS attempts to balance the DS load on top of the balanced US load and among DS channels associated to the same US. The method and policy used for DS load balancing are based on the configuration in the DS load balancing group associated to the corresponding DS channels.

There are no new or modified commands for this feature.

Line Card High Availability (HA) Support for WB Cable Modems

Wideband cable modems remain online whenever there is a failure or switchover of a 520 MD host line card, 520 guardian line card, 520 host or 520 guardian on the same line card, or a performance routing engine (PRE).

There are no new or modified commands for this feature.

Bypass the 24 Hour Timer for WB CM Use of Failed RF Channels

When the CM sends a request to the CMTS for bonded service, the CMTS assigns the best available bonding group that is compatible with the CM. The CM then attempts to acquire the non-primary DS RF channels that are members of that bonding group. If the CM is unable to acquire one or more of the channels, it returns an error code causing the CMTS to mark all of the assigned RF channels as unacceptable for that CM. In prior versions, the channels so marked could not be reassigned to the same CM for up to 24 hours.

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

There are no new or modified commands for this feature.

Voice Support on WB Modems

CMTS supports voice services on voice-enabled wideband (WB) cable modems. Committed information rate (CIR) downstream service flows on WB interfaces are supported. You can reserve up to 90% of the wideband interface bandwidth. If multiple MAC domains (MDs) are sharing a WB interface, the available link rate is distributed evenly between all MDs that share the WB interface. If the MDs that share the WB interface are on the same line card, they share the CIR pool.

To display the reserved and available bandwidth, you can use the show-module bay all association wideband command. To display the reserved and available bandwidth for wideband interfaces, you can use the show interface wideband-cable command. For more information, see the Cisco IOS CMTS Cable Command Reference Guide.

There are no new commands introduced for this feature. However, the user must first enable packet cable or multimedia packet cable to enable the voice support feature.

Dynamic Bandwidth Sharing for Wideband and Modular Cable Interfaces

Dynamic bandwidth sharing (DBS) is the dynamic allocation of bandwidth for wideband (WB) and modular cable (MC) interfaces sharing the same downstream channel. The bandwidth available to each WB, MC, or narrowband channel is not a fixed value-it depends on the configuration and the traffic load on the WB or MC.

DBS is achieved using a new type of modality called a link queue. Link queues represent a specific share of bandwidth on a particular channel. Link queues are only used to calculate the effective bandwidth of a channel, and such link queues are activated and deactivated according to the state of activity on a specific channel. DBS and static bandwidth allocations are configured at the WB or MC interface level. By default, bandwidth for a WB or MC channel is statically allocated. When DBS is enabled on an interface, the static bandwidth percentage is converted to a committed information rate (CIR) value for the corresponding link queue. The interface CIR value represents the guaranteed portion of the interface bandwidth and is used for admission control of the service flows with minimum reserved rate. When DBS is enabled, you can also specify the remaining ratio value of the excess bandwidth for the link queue. If DBS is enabled and no bandwidth percentage is specified, no bandwidth is reserved for the WB or MC interface and the interface is effectively in protocol down state where link queues are not created.

Dynamic bandwidth sharing does not preclude static bandwidth configuration. If a static portion of bandwidth is configured on any radio frequency (RF) channel that one or more DBS-enabled channel utilizes, that portion is subtracted from the RF link's CIR. Therefore, such a portion is always reserved and is not available to dynamic WB or MC interfaces. The DBS feature continues working across line card and performance routing engine (PRE) switchovers with no loss of functionality.

For more information on the DBS please see http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_dyn_bw_sharing.html

The following commands are new in Cisco IOS Release 12.3(23)BC1.

cable dynamic-bw-sharing

debug cr10k-rp dbs-queue

show pxf cable controller

The following commands are modified in Cisco IOS Release 12.3(23)BC1.

cable rf-bandwidth-percent

cable rf-channel

show pxf cpu queue

For a detailed description of the commands please refer the Cisco IOS CMTS Cable Command Reference.

New Hardware Features in Cisco IOS Release 12.3(21a)BC6

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC6.

New Software Features in Cisco IOS Release 12.3(21a)BC6

There are no new software features supported in Cisco IOS Release 12.3(21a)BC6.

New Hardware Features in Cisco IOS Release 12.3(21a)BC5

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC5.

New Software Features in Cisco IOS Release 12.3(21a)BC5

There are no new software features supported in Cisco IOS Release 12.3(21a)BC5.

New Hardware Features in Cisco IOS Release 12.3(23)BC

The DOCSIS Timing & Control Card (DTCC) is introduced in Cisco IOS Release 12.3(23)BC.

DOCSIS Timing & Control Card (DTCC)

On the Cisco uBR10012 universal broadband router, the DOCSIS Timing & Control Card (DTCC) acts as a secondary processor that performs the following functions:

In the default DTI mode, a 10.24 MHz clock and 32-bit DOCSIS timestamp are generated by the DTI Server, propagated to DTI client using DTI protocol, and distributed by DTI client to each cable interface line card.

Allows software to independently power off any or all cable interface line cards.

Drives the LCD panel used to display system configuration and status information.

Monitors the supply power usage of the chassis.

Two RJ-45 cables with the DTI server, which, in turn, can generate the clock using its own oscillator or external timing reference inputs such as GPS or network clock.

When two DTCC cards are installed, they are configured as active (primary) and backup (redundant). If the DTCC card in the first slot is working at system power-up, it automatically becomes the active card and the DTCC card in the second slot becomes the backup card. The DTCC cards monitor each other's priority information, so that if the active card fails, the active card role is transferred to the redundant backup card without loss of data.

Each DTCC card contains two RJ-45 connectors labeled Primary and Secondary, on the front panel. See Xref_Colorparanum[FC_FigureCap,FCW_FigureCapW]on page *. These connectors are for a primary and secondary (redundant) Stratum 3 external clock reference source that is traceable to a Stratum 1 clock source. The external reference source allows the Cisco uBR10012 router's reference clock to be synchronized to the Stratum 1 clock source, providing a free-running DOCSIS-quality clock reference and time stamp to the cable interface line cards.

If present, the primary DTI link is used. If it is lost, the secondary DTI link (if present) on the active DTCC card is used. If the active DTCC card stops functioning, control is transferred to the backup DTCC card, which then uses its primary and secondary clock reference sources. If neither card has a valid clock reference source, In DTI mode, all M-CMTS elements should have common timing source. The internal clock of DTI client cannot be used to provide DOCSIS clock and timestamp. High availability strategies (active/backup card, active/backup ports) should be used to prevent loss of common timing source.

New Software Features in Cisco IOS Release 12.3(23)BC

The following software features are new in Cisco IOS Release 12.3(23)BC:

DOCSIS 3.0 Downstream Solution

The DOCSIS 3.0 Downstream Solution, Release 2.0, provides the following capabilities:

Primary-capable downstream channels from the SPA

Primary-capable channels are SPA DS channels (also known as SPA RF channels) associated with the upstream channels from the Cisco uBR10-MC5X20 line card. A SPA downstream channel is made primary-capable via Channel Grouping Domain (CGD) configuration. A primary-capable downstream channel can carry narrowband traffic as well as wideband traffic. An RF channel is considered primary-capable when it has been associated with one or more upstream channels from a Cisco uBR10-MC5X20 cable interface and this RF channel can carry DOCSIS MAC management messages (MMM) including SYNC messages, Mini-slot Allocation Packet (MAP) messages, and Upstream Channel Descriptors (UCD). They may also carry primary MAC Domain Descriptor (MDD) messages for DOCSIS 3.0 modems.Such an RF channel downstream is referred to as a primary-capable downstream. A DOCSIS Timing Interface (DTI) server which interfaces with the EQAM device and the Cisco uBR10k DTCC is used to synchronize DOCSIS MAC-layer messages. The interface represented by a single primary-capable downstream represents the narrowband portion of the RF channel.

A SPA downstream channel, whether primary-capable or not, can always be part of a bonded channel that carries bonded data traffic.

An RF channel can be shared by the associated modular-cable interface and by the wideband interfaces. The bandwidth of each RF channel can be configured to be statically divided between the modular-cable and wideband interfaces. Each RF channel's bandwidth can be used for wideband channels or narrowband channels or for a combination of the two.

A primary downstream channel is a primary-capable channel that is being used as a narrowband channel or as part of a wideband channel. A SPA downstream channel may only be a primary-capable downstream channel for a single MAC domain. However, the same SPA downstream channel may be part of one or more bonded channels (wideband interface) that serve multiple MAC domains. A primary downstream channel of one MAC domain can serve as non-primary downstream channel of another MAC domain. The total available bandwidth of a primary downstream channel, which is 96 percent, is split between the primary-capable downstream and non-primary-capable downstream channels. The remaining 4 percent is reserved for DOCSIS MAP and SYNC bandwidth.

This capability:

Increases legacy downstream port density

Allows legacy and bonded modems to share the same SPA DS channels

Supports 3-channel bonding for 3-channel modems and 8-channel bonding for Linksys modems on the SPA DS channels

Extensible MAC domain support via Channel Grouping Domain

A Channel Grouping Domain (CGD) is a collection of primary-capable downstream channels that are associated with a common set of upstream channels. A CGD is always specified within the context of a MAC domain to which all the downstream and upstream channels belong. The downstream channel local to the MAC domain on the Cisco uBR10-MC5X20 line card is always primary-capable, but a SPA downstream channel has to be made primary-capable by explicit CGD configuration. A CGD provides the additional flexibilty of associating a subset of the upstream channels within a MAC domain to any of the primary-capable downstream channels, including the local downstream channels. When an upstream channel is associated with a downstream channel, its information is included in the MAP and UCD messages sent through that downstream channel. Multiple CGD configurations may be included in the same MAC domain, allowing the flexibility of the MAC domain to include various primary-capable downstream channels associated with common or different sets of upstream channels.

This capability:

Provides support for multiple primary-capable channels per MAC domain

Allows flexible upstream and downstream associations within a MAC domain

Allows association of bonded channel to MAC domains

Primary-capable downstream channel selection

Provides primary-capable downstream channel selection to facilitate channel bonding and reliability of voice-enabled modems.

Primary Downstream Channel Selection for Bonding Capable Modems

In order to fully utilize downstream bonding capacity, it is desired to force downstream bonding (wideband) capable modems to register on a primary-capable channel that is part of an operational downstream bonding group.

A downstream bonding capable modem is identified upon cable modem registration. A modem is downstream bonding capable if the modem reports a multiple-tuner receive capacity and a Remote Copy Protocol (RCP) known by the CMTS in REG-REQ. A wideband media terminal adapter (MTA) will be treated also as DS bonding-capable modems, therefore subject to the same primary channel selection policy.

The primary channel selection for bonding capable modems can be enabled through the global DS channel selection configuration. By default, if such configuration is not present, downstream bonding capable modems will be allowed to operate on a primary channel even it is not included in any load balancing group.

At any time after the system is up, enabling the primary channel selection for bonding capable modems will not affect existing modems in the system. The operator has to manually reset the bonding capable modems through the clear cable modem command either globally or at the per-MAC domain level.

Primary Downstream Channel Selection for Narrowband Modems

The primary downstream channel selection for narrowband modems is intended to provide the operator the flexibility to segregate non-bonding capable modems to specific types of DS channels with the following two options:

Redirecting Modems that Access a CMTS with Legacy DOCSIS INIT-RNG-REQ at Initialization

Moving Non-Bonding Capable Modems to Bonding-Disabled Primary Channels

Downstream Channel Selection for Voice-Enabled Cable Modems

This downstream channel selection option provides the operator the ability to provide high-availability for voice services by restricting voice-enabled modems to Cisco uBR10-MC5X20 downstream channels.

High availability

Provides high availability support for modems on SPA DS channels. The Cisco DOCSIS 3.0 Downstream Solution, Release 2.0 provides higher system availability for voice services by providing the ability to restrict voice services only to Cisco uBR10-MC5X20 line cards. This allows the CMTS to make an attempt to move the voice modems to the hosting Cisco uBR10-MC5X20 line cards of Cisco uBR10-MC5X20 downstream channels in the same load balancing group.

DOCSIS 1.x/2.0 and legacy feature support on SPA DS channels

Provides support for DOCSIS 1.x/2.0 modems on SPA downstream channels. The following legacy features are supported on the SPA downstream channels:

Load balancing

Virtual interface bundling

Full DOCSIS Quality of Service (QoS)

Committed Information Rate (CIR) Admission Control

Bonded multicast

Non-bonded multicast

DOCSIS Set-top Gateway (DSG)

Subscriber Accounting and Management Interface Specification (SAMIS)

Multiprotocol Label Switching (MPLS)/Virtual Private Network (VPN)

Baseline Privacy Interface (BPI)/Baseline Privacy Interface Plus (BPI+)

Payload Header Suppression (PHS)

Packet Cable and PacketCable™ Multimedia (PCMM)

Cable modem flaplist

Source Verify (with Dynamic Host Configuration Protocol (DHCP) option)

Computer Assisted Law Enforcement Act (CALEA)/Service Independent Intercept (SII)/Packet Intercept

Cable modem remote query

DOCSIS Packet filters

Cable Address Resolution Protocol (ARP)

DOCSIS 3.0 support on SPA DS channels

The Cisco DOCSIS 3.0 Downstream Solution is an industry-standard DOCSIS 3.0 implementation of channel bonding. With channel bonding, bandwidth is increased by combining or bonding multiple RF channels to create a wideband channel. The Cisco DOCSIS 3.0 Downstream Solution extensions affect the CMTS and the cable modem as well as the provisioning and network management systems. A 3-channel cable modem that performs 3-channel bonding must be able to access three SPA RF channels of which at least one RF channel must be a primary-capable channel that is used for modem registration.

The core of the Downstream 3.0 downstream solution is the sending of DOCSIS packets for a given service flow across multiple RF channels, offering significant increases in the peak downstream data rate that can be provided to a single cable modem. The transmit framer in the Cisco Wideband SPA "stripes" the DOCSIS packets for a given flow and transmits them across the multiple RF channels of the wideband channel. When the packets are received at the wideband cable modem, the modem's receiver framer uses a sequence number embedded in each DOCSIS packet to reassemble the packets into the original flow.

The Cisco DOCSIS 3.0 Downstream Solution defines a wideband channel as a unique combination of downstream RF channels from the same SPA. The wideband CMTS manages up to 64 wideband channels (32 wideband channels per Wideband SPA). A wideband cable modem uses a wideband channel. Many wideband cable modems can share the same wideband channel.

The Cisco Wideband SPA on the Cisco uBR10012 router provides DOCSIS 3.0 channel bonding for DOCSIS Network processing. In the Cisco DOCSIS 3.0 Downstream Solution, Release 2.0, for the wideband downstream channel, the Wideband SPA uses its Gigabit Ethernet port to send data traffic to the EQAM device. This EQAM device uses one or more QAM output channels, depending on how the wideband channel is configured, to send striped packets to the wideband cable modem. In Cisco DOCSIS 3.0 Downstream Solution Release 2.0, channel bonding is used for downstream wideband channels only. A downstream wideband channel can combine up to three RF channels for a total bandwidth of over hundreds of megabits to gigabits per second with bonded modems supporting data rates of up to 292 Mbps.

In Release 2.0, channel bonding is used for downstream wideband channels only.

With the Linksys WCM300-NA modem, a downstream wideband channel can combine up to eight RF channels for a total bandwidth of up to approximately 292 Mbps (at 6 MHz and 256 QAM).

With the Scientific Atlanta DPC2505 modem, a downstream wideband channel can combine up to three RF channels for a total bandwidth of over 100 Mbps (at 6 MHz and 256 QAM).

New Hardware Features in Cisco IOS Release 12.3(21a)BC4

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC4.

New Software Features in Cisco IOS Release 12.3(21a)BC4

There are no new software features supported in Cisco IOS Release 12.3(21a)BC4.

New Hardware Features in Cisco IOS Release 12.3(17b)BC9

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC9.

New Software Features in Cisco IOS Release 12.3(17b)BC9

There are no new software features supported in Cisco IOS Release 12.3(17b)BC9.

New Hardware Features in Cisco IOS Release 12.3(21a)BC3

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC3.

New Software Features in Cisco IOS Release 12.3(21a)BC3

The following software features are new in Cisco IOS Release 12.3(21a)BC3:

Control Point Discovery (CPD)

The Control Point Discovery (CPD) can be used to discover the IP address of a control point between the requestor and a media endpoint. It can be used by CMS (call management server), DF (delivery function for CALEA), or PS (policy server for Packetcable multimedia) to discover the IP address of the CMTS connected to the media endpoint. The CMTS needs to interpret and respond to the CPD messages.

New Hardware Features in Cisco IOS Release 12.3(21a)BC2

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC2.

New Software Features in Cisco IOS Release 12.3(21a)BC2

There are no new software features supported in Cisco IOS Release 12.3(21a)BC2.

New Hardware Features in Cisco IOS Release 12.3(21a)BC1

There are no new hardware features supported in Cisco IOS Release 12.3(21a)BC1.

New Software Features in Cisco IOS Release 12.3(21a)BC1

There are no new software features supported in Cisco IOS Release 12.3(21a)BC1.

New Hardware Features in Cisco IOS Release 12.3(21)BC

The following hardware features are new in Cisco IOS Release 12.3(21)BC:

Cisco Wideband SIP

The Cisco Wideband SPA interface processor (SIP) is a carrier card that inserts into a Cisco uBR10012 router slot like a line card. Each Wideband SIP supports two Cisco Wideband SPAs. The Wideband SIP provides no network connectivity on its own.

The Cisco Wideband SIP occupies two full height slots on the uBR10012 router. When the uBR1012 router is used as a wideband CMTS, slots 1/0 and 2/0 are used for the Wideband SIP. Online insertion and removal (OIR) is supported for both the Wideband SIP and the individual Wideband SPAs.

The Cisco Wideband SIP requires the Cisco uBR10012 Performance Routing Engine 2 (PRE-2).

For more information on the Cisco Wideband SIP, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide .

Cisco Wideband SPA

The Cisco Wideband shared port adapter (SPA) is a single-wide, half-height SPA that implements the DOCSIS 3.0 Downstream Channel Bonding feature. The Wideband SPA is used for downstream data traffic only. It has one active and one redundant Gigabit Ethernet port. The active port sends downstream data traffic to one or more external edge QAM devices.

The Cisco uBR10012 router can support up to two Wideband SPAs. Each Wideband SPA can support up to 12 logical wideband channels (bonding groups). Depending on how it is configured, each Wideband SPA allows up to 24 RF channels. Each logical wideband channel consists of multiple RF channels. The Cisco IOS CLI includes a set of commands to configure the Wideband SPA on the Cisco uBR10012 router.

The two Gigabit Ethernet ports on the Wideband SPA use small form-factor (SFP) modules. The SFP module is an input/output (I/O) device that plugs into a Gigabit Ethernet SFP port on the Wideband SPA, linking the port with an edge QAM device through a fiber-optic network.

For more information on the Cisco Wideband SPA, see the Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide .

New Software Features in Cisco IOS Release 12.3(21)BC

The following software features are new in Cisco IOS Release 12.3(21)BC:

Automatic Virtual Interface Bundles

All cable bundles are now automatically converted and configured to be in a virtual bundle, and standalone cable interfaces must be manually configured to be in a virtual bundle to operate properly.

Previously, new virtual interface bundles and bundle members required reconfiguration, and there could also be standalone interfaces not part of a bundle at all.

The following guidelines describe the automatic virtual interface bundling:

The former rules for bundle master are applicable to the new virtual bundle interface.

The former rules for bundle slaves are applicable to the new virtual bundle members.

All cable bundles are automatically converted and configured to be in a virtual bundle after loading the software image.

The virtual bundle interface accumulates the counters from members; counters on member links are not cleared when they are added to the bundle. If a bundle-only counter is desired, clear the bundle counter on the members before loading the image.

A maximum of 40 virtual interface bundles are supported, with the numeric range from 1 to 255.

The virtual bundle interface remains configured unless specifically deleted, even if all members in the bundle are deleted.

This feature supports subinterfaces on the virtual bundle interface.

Bundle-aware configurations are supported on the virtual bundle interface.

Bundle-unaware configurations are supported on each bundle member.

If the bundle interface existed in earlier Cisco IOS releases, the earlier cable configurations re-appear after upgrade.

For more information, see the Cable Interface Bundling and Virtual Interface Bundling for the Cisco CMTS chapter in the Cisco CMTS Feature Guide.

Cable DHCP Enhancements

When using an external DHCP server, the Cisco CMTS supports a number of options that can enhance operation of the cable network in certain applications.

Dynamic Cable Helper Address Selection

The cable helper-address command has been expanded to further specify where to forward DHCP packets based on origin: from a cable modem, MTA, STB, or other cable devices:

cable helper-address address [ cable-modem | host | mta | stb ]

This enables load-balancing of DHCP requests from cable modems and CPE devices by specifying different DHCP servers according to the cable interface or subinterface. You can also specify separate servers for cable modems and CPE devices.

When the mta or stb option is used, you must also use the cable dhcp-parse option-optnum command to parse the DHCP options.

If you specify only one option, the other types of devices (cable modem, host, mta, or stb) will not be able to connect with a DHCP server. You must specify each desired option in a separate command.

You may specify more than one helper address on each cable interface by repeating the command. You can specify more than 16 helper addresses, but the Cisco IOS software uses only the first 16 valid addresses.

If you do not specify an option, the helper-address will support all cable devices, and the associated DHCP server will accept DHCP packets from all cable device classes.

Cable Node Location Reporting

The DHCP Relay Agent can now be used to identify cloned modems or gather geographical information for E911 and other applications. Using the cable dhcp-insert command, users configure the CMTS to insert downstream, upstream, or hostname descriptors into DHCP packets:

cable dhcp-insert {downstream-description | hostname | upstream-description}

A DHCP server can then utilize such information to detect cloned modems or extract geographical information. Multiple types of strings can be configured as long as the maximum relay information option size is not exceeded.

Multiple types of descriptor strings can be configured as long as the maximum relay information option size is not exceeded.

show cable modem docsis device-class

The show cable modem docsis device-class command is now supported.

For more information on these enhancements and related commands, see the Cisco Broadband Cable Command Reference Guide and the "DHCP, ToD, and TFTP Services for the Cisco Cable Modem Termination System" chapter in the Cisco CMTS Feature Guide.

Cable Duplicate MAC Address Reject

Cisco IOS Release 12.3(21)BC introduces a DOCSIS 1.1-compliant and above security enhancement that helps to eliminate denial-of-service (DOS) attacks that are caused by cloned cable modems. A clone is presumed to be one of two physical cable modems on the same Cisco CMTS chassis with the same HFC interface MAC address. The cloned cable modem may be DOCSIS 1.0 or greater, and may be semi-compliant or non-compliant with portions of the DOCSIS specifications.

This feature is enabled by default on the Cisco CMTS, and has no associated command-line interface (CLI) configuration commands. This feature creates a new log message. By default, this message appears in the syslog, but may be moved into the cable layer2 event log using the configuration command cable logging layer2events.

For additional information about this feature, its causes, and the introduction of the new cable privacy bpi-plus-enforce command, which enforces DOCSIS 1.1 BPI+ on the cable network, refer to the following documents on Cisco.com and the Internet:

Cable Duplicate MAC Address Reject for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_ccmd.html

Cisco IOS CMTS Cable Command Reference

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

DOCSIS 3.0 Downstream Channel Bonding

Cisco IOS Release 12.3(21)BC introduces the DOCSIS 3.0 Downstream Channel Bonding feature, which is the key feature of the Cisco Cable Wideband Solution, Release 1.0. This feature and the Cisco Cable Wideband Solution require the following components:

Cisco uBR10012 router

Cisco SIP (SPA Interface Processor) for the 1-Gbps Wideband SPA

Cisco 1-Gbps Wideband SPA (Shared Port Adapter)

The Cisco Cable Wideband Solution, Release 1.0, also requires these major components: edge QAM (EQAM) device and wideband cable modem.

In the Cisco Cable Wideband Solution, Release 1.0, the DOCSIS 3.0 Downstream Channel Bonding feature supports downstream wideband channels consisting of multiple bonded RF channels. The solution provides wideband data services over existing hybrid fiber coax (HFC) networks. With wideband data services, multiple RF channels are aggregated into a single logical wideband channel (bonding group) that delivers higher bandwidth to the wideband cable modem than was previously possible with DOCSIS 2.0 technology. This aggregation of RF channels is referred to generically as "channel bonding."

The Cisco Cable Wideband Solution, Release 1.0, can be deployed in parallel with DOCSIS 1.X/2.0 technology. The CMTS supports DOCSIS 1.X/ 2.0 modems on non-wideband ports while wideband cable modems deliver higher-speed throughput on the wideband ports.

For more information on the Cisco Cable Wideband Solution, Release 1.0, and the Cisco Wideband SIP and Cisco Wideband SPA, see these documents:

Cisco Cable Wideband Solution Design and Implementation Guide, Release 1.0

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

Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide

http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/install_upgrade/uBR10012/hwsipspa.html

Cisco uBR10012 Universal Broadband Router SIP and SPA Software Configuration Guide

http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/ubr10012/12.3_23_bc/sipsp_d3.html

Enhanced Rate Bandwidth Allocation (ERBA) on the Cisco uBR10012 Router

Cisco IOS Release 12.3(21)BC introduces the ERBA feature on the Cisco uBR10012 CMTS with Performance Routing Engine 2 (PRE2) modules.

For additional information about ERBA in Cisco IOS Release 12.3(21)BC, refer to these documents on Cisco.com:

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

Cisco IOS CMTS Cable Command Reference

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

HCCP Switchover Enhancements

Beginning in Cisco IOS Release 12.3(21)BC, the Cisco uBR10012 universal broadband router supports the HCCP Switchover Enhancements feature, with the following new support:

Performance improvements for traffic recovery during line card switchover under certain scalability limits. Within the required network scalability limits, the HCCP Switchover Enhancements feature provides the following switchover benefits:

Less than 1-second voice call recovery.

Less than 20-second data recovery.

To prevent false switchovers, the keepalive failure logic is modified.

For faster line card switchovers, the member subslot protect command has been modified to add the [config slot/subslot] option. When using the new config option, you can preload upstream connectors on an HCCP protected interface to emulate the most common line card connector assignments.

The HCCP Switchover Enhancements feature in Cisco IOS Release 12.3(21)BC has the following restrictions:

The feature is supported on the Cisco uBR10012 router with the Cisco Performance Routing Engine 2 (PRE2) only.

The feature is supported by the following line cards on the Cisco uBR10012 router: Cisco UBR10-MC5X20S, Cisco UBR10-MC5X20U, and Cisco UBR10-MC5X20H

The line card switchover performance improvements are valid for networks scaling to less than 5000 cable modems per line card, and less than 1000 voice calls per line card.

The working and protect line cards must have the same channel width.

Upconverter failure detection is not included as part of the line card switchover performance improvements.

Virtual interface bundling is required. If you are upgrading from an earlier Cisco IOS software release and virtual bundling is not configured upon startup, the Cisco IOS software will automatically generate a virtual bundling configuration. Therefore, beginning in Cisco IOS Release 12.3(21)BC, Layer 3 information cannot be configured directly at the cable interface. The maximum number of virtual bundle interfaces supported is 40, and bundle numbers can be between 1-255.

Tracking of HCCP interfaces is removed. The hccp track command is obsolete.

In prior releases, a switchover could be triggered due to a keepalive failure no matter how many cable modems were online for an upstream. This resulted in false switchovers. In Cisco IOS Release 12.3(21)BC, keepalive failure detection is now enabled only for upstreams that have 15 or greater modems online. A switchover due to keepalive failure will trigger only if there is not any traffic on all of the upstreams associated with an interface that is enabled for keepalive.

For more information refer to the Cisco CMTS Feature Guide at:

N+1 Redundancy for the Cisco Cable Modem Termination System

NSF Lite

The NSF Lite features RPR+ scaling and switchover performance enhancements. These enhancements will improve switchover times by keeping the Standby RP link state & Docsis(modem database) in full-sync with the Primary RP thus, enabling the Standby RP to begin forwarding traffic immediately after a switchover.

NSF Lite also provides routing enhancments for the OSPF NSF to minimize traffic outage during switchover.IDB-State Sync.

For additional information about Route Processor Redundancy Plus on the Cisco uBR10012 Universal Broadband Router, refer to the following documents on Cisco.com:

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html 

PacketCable Client Accept Timeout

Cisco IOS Release 12.3(21)BC introduces support for setting timeout values for COPS Telnet connections on the Cisco CMTS, and for clearing COPS telnet sessions.

Network or Cisco CMTS telnet errors can cause incomplete COPS sessions to be created. This new timeout timer enables the clearing and cleaning of allocated resources for the stale COPS Telnet sessions on the Cisco CMTS. This feature supports COPS for PacketCable on the Cisco CMTS.

If the Connection between a PacketCable CMS and the Cisco CMTS is not completely established, and the PacketCable CMS does not correctly terminate the session by sending a TCP FIN message, the connection otherwise shows a COPS server in the output of the show cops server command.

The timeout timer applies to each COPS Telnet connection on the Cisco CMTS, and expiration of this timeout setting triggers the termination of the Telnet session and clears supporting resources on the Cisco CMTS.

To set the timeout timer for Telnet COPS sessions on the Cisco CMTS, use the following command in global configuration mode. To remove this timeout timer, use the no form of this command.

packetcable timer client-accept seconds

no packetcable timer client-accept seconds

Syntax Description

seconds

The timeout value in seconds, beyond which the Telnet COPS session is terminated, and associated resources on the Cisco CMTS are cleared.

Range from 300 seconds (five minutes) to 1800 seconds (30 minutes).


To clear all COPS Telnet sessions and associated resources on the Cisco CMTS, use the following command in global configuration mode:

clear cops connection

For additional information, refer to the following documents on Cisco.com:

PacketCable and PacketCable MultiMedia for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_pktcable_mm_ps2209_TSD_Products_Configuration_Guide_Chapter.html

COPS Engine Operation on the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_cops_eng_op_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Cisco IOS CMTS Cable Command Reference

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

Per Downstream Static Multicast

The IOS IGMP Static-Group feature was first introduced back in Release 11.2, while the Source Specific Multicast (SSM) extension was added in Release 12.0(6)T. This allows network administrators to configure the router to be a statically connected member of the specified group on the interface. All multicast traffic destined to that particular group will be forwarded out on that configured interface.

Beginning in Cisco IOS Release 12.3(21)B, the Cisco uBR10012 universal broadband router supports the Per Downstream Static Multicast feature. This feature provides several multicast enhancements and makes it possible to control the replication of static IP multicast streams within a cable bundle using the cable igmp static-group command on the physical cable downstream interface.

For additional information, refer to the following documents on Cisco.com:

Advanced-mode DOCSIS Set-Top Gateway 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_docsis_gw12_ps2209_TSD_Products_Configuration_Guide_Chapter.html

RF Switch Firmware Version 3.60

Cisco RF Switch Firmware 3.60 is available to support N+1 Redundancy on the Cisco uBR10012 router. This Firmware version must be used with Cisco IOS Release 12.3(21)BC. Cisco RF Switch Firmware Version 3.60 provides the following changes, resolutions, enhancements, and updates:

To help handle an increase in the SNMP traffic, Version 3.60 changes the network buffering to allocate a larger pool of (number of) buffers, with a new number of 100 buffers total.

Version 3.60 reduces the maximum packet size to 600 bytes. This combination of a larger number of buffers with smaller maximum packet size helps with handling large bursts of inbound packets that were discarded in previous versions of Cisco RF Switch Firmware.

Version 3.60 resolves a previous bug in the SNMP agent to help further with the above items. In prior versions of Cisco RF Switch firmware, the SNMP agent blocked traffic just after packet reception, waiting to allocate a buffer in which to place the output response. If no buffer was available (as would be the case if a large burst of incoming packets occurred), the agent would timeout, and the system would generate a watchdog timeout. Now, the agent uses a private buffer for the output response, and only requests a packet buffer after completing the snmp operation. If no buffer is available, the output response is discarded, and the agent continues processing inbound packets.

Version 3.60 adds the noverify option to the copy command, enabling you to override the file type verification, and place a file in either the flash (FL:) or bootflash (BF:) device. Version 3.60 updates the online help to reflect this new option. This new option provides the ability to place a copy of the main application into the bootflash, so that normal system operation is restarted in the case of a system crash, instead of having the "sys>" prompt as in previous versions of Firmware.

Version 3.60 resolves a previous issue in which concurrent access to the RF switch modules via the command-line interface and SNMP would cause random errors and crashes. The firmware now allows simultaneous usage of telnet, console, and SNMP operation. This issue was observed primarily if the show version and test module commands were used at the same time that SNMP status polling operations were occurring. This previous issue also affected a number of additional commands.

For additional information about Cisco RF Switch Firmware Version 3.60, refer to the following documents on Cisco.com:

Release Notes for Cisco RF Firmware, Version 3.60

https://www.cisco.com/en/US/products/hw/cable/ps2929/prod_release_notes_list.html

Cisco RF Switch Firmware Configuration Guide, Version 3.60

https://www.cisco.com/en/US/products/hw/cable/ps2929/products_installation_and_configuration_guides_list.html

Cisco RF Switch Firmware Command Reference Guide, Version 3.60

https://www.cisco.com/en/US/docs/cable/rfswitch/ubr3x10/command/reference/rfswcr36.html

N+1 Redundancy for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

SAMIS Source Address Management

Cisco IOS Release 12.3(21)BC introduces Subscriber Account Management Interface Specification (SAMIS) enhancements which will provide the ability to set the source of the usage based billing packets originated by the router using the cable metering command. This enables the ip address to be set as the source of the loopback interface, similar to what is done for telnet or ftp (ip ftp source-interfacelo0).

For additional information about Subscriber Account Management Interface Specification (SAMIS), refer to the following document on Cisco.com:

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_sbsbr_tfmgt_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Service Flow Admission Control

Cisco IOS Release 12.3(21)BC introduces Service Flow Admission Control (SFAC) on the Cisco Cable Modem Termination System.

SFAC on the Cisco CMTS is a mechanism that gracefully manages service flow admission requests when one or more resources are not available to process and support the incoming service request. Lack of such a mechanism not only causes the new request to fail with unexpected behavior but could potentially cause the flows that are in progress to have quality related problems. SFAC monitors such resources constantly, and accepts or denies requests depending on the resource availability.

SFAC enables you to provide a reasonable guarantee about the Quality of Service (QoS) to subscribers at the time of call admission, and to enable graceful degradation of services when resource consumption approaches critical levels. SFAC reduces the impact of unpredictable traffic demands in circumstances that would otherwise produce degraded QoS for subscribers.

SFAC uses two event types for resource monitoring and management—cable modem registration and dynamic service (voice call) requests. When either of these two events occurs on the Cisco CMTS, SFAC verifies that the associated resources conform to the configured limits prior to admitting and supporting the service call request.

SFAC is not a mechanism to apply QOS to the traffic flows. Scheduling and queuing are some of the mechanisms used for implementing the QOS. The QOS is applied on per packet basis. SFAC checks are performed before the flow is admitted.

SFAC in Cisco IOS Release 12.3(21)BC monitors the following resources on the Cisco CMTS.

CPU utilization—SFAC monitors CPU utilization on the Cisco CMTS, and preserves QoS for existing service flows when new traffic would otherwise compromise CPU resources on the Cisco CMTS.

Memory resource utilization (I/O, Processor, and combined total)—SFAC monitors one or both memory resources and their consumption, and preserves QoS in the same way as with CPU utilization.

Bandwidth utilization for upstream and downstream—SFAC monitors upstream and downstream bandwidth utilization, and associated service classes, whether for data or dynamic service traffic.

For complete configuration and operation information, refer to the following documents on Cisco.com:

Service Flow Admission Control for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_svflw_ad_ctl_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Cisco CMTS MIB Specifications Guide

http://www.cisco.com/en/US/products/hw/cable/ps2209/prod_technical_reference_list.html

Stateful Switchover (SSO) for PacketCable and PacketCable MultiMedia

Cisco IOS Release 12.3(21)BC enhances high availability support that enables the synchronization of PacketCable and PacketCable MultiMedia (PCMM) gates during switchover events on the Cisco CMTS. This enhancement is enabled by default with Cisco IOS Release 12.3(21)BC and later supporting releases on the Cisco uBR10012 router and Cisco uBR7246VXR router.

This enhancement requires no additional configuration commands for line card redundancy in the Cisco N+1 Redundancy feature, nor the RPR+ Redundancy feature on the Cisco uBR10012 router. However, this functionality uses the existing per-interface HCCP commands that are used to associate the Working and Protect interfaces in the case of N+1 Redundancy.

This feature introduces the new debug packetcable hccp command to troubleshoot HCCP information specific to PacketCable and PCMM gates.

For additional information, refer to the following documents on Cisco.com:

PacketCable and PacketCable MultiMedia for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_pktcable_mm_ps2209_TSD_Products_Configuration_Guide_Chapter.html

N+1 Redundancy for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_nplus1_redun_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Cisco IOS CMTS Cable Command Reference

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

New Hardware Features in Cisco IOS Release 12.3(17b)BC8

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC8.

New Software Features in Cisco IOS Release 12.3(17b)BC8

There are no new software features supported in Cisco IOS Release 12.3(17b)BC8.

New Hardware Features in Cisco IOS Release 12.3(17b)BC7

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC7.

New Software Features in Cisco IOS Release 12.3(17b)BC7

There are no new software features supported in Cisco IOS Release 12.3(17b)BC7.

New Hardware Features in Cisco IOS Release 12.3(17b)BC6

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC6.

New Software Features in Cisco IOS Release 12.3(17b)BC6

There are no new software features supported in Cisco IOS Release 12.3(17b)BC6.

New Hardware Features in Cisco IOS Release 12.3(17b)BC5

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC5.

New Software Features in Cisco IOS Release 12.3(17b)BC5

There are no new software features supported in Cisco IOS Release 12.3(17b)BC5.

New Hardware Features in Cisco IOS Release 12.3(17b)BC4

The following hardware feature is new in Cisco IOS Release 12.3(17b)BC4:

Cisco uBR10-MC5X20H Interface Line Card

Similar to the Cisco uBR10-MC5X20S and U cable interface line cards, the Cisco uBR10-MC5X20H line card is a 20 by 16 inch cards designed specifically for the Cisco uBR10012 router. It transmits and receives RF signals between the subscriber and the headend over hybrid fiber-coaxial (HFC) system.

Upstream data, from the subscriber, comes through the upstream ports (US0-US19), which the line card processes, configures and sends across the backplane to the WAN/backhaul card and out to the Internet.

Downstream data, to the subscriber, comes from the Internet through the WAN/backhaul card, and across the backplane to the cable interface line card, which processes, configures, and sends the data out through the appropriate downstream port (DS0-DS4) to be combined with the rest of the downstream signals in the headend.

The Cisco uBR10-MC5X20H line card supports both DOCSIS and EuroDOCSIS cable modem networks, in addition to downstream channels in the 70 to 860 MHz range, and upstream channels in the 5 to 65 MHz range. Each downstream port includes an onboard integrated upconverter. The cable interface line card supports Annex B and Annex A radio frequency (RF) data rates, channel widths, and modulation schemes and has DOCSIS MAC management and spectrum management capabilities. DOCSIS 2.0, A-TDMA rates are also supported.

The Cisco uBR10-MC5X20H has double the line card CPU speed, memory, and flash memory as the Cisco uBR10-MC5X20U, allowing support of Voice over IP (VoIP) at much higher call loads and a higher percentage of modems running advanced DOCSIS features that typically consume line card CPU resources.

New Software Features in Cisco IOS Release 12.3(17b)BC4

The following software features are new in Cisco IOS Release 12.3(17b)BC4:

Downstream Load Balancing Distribution with Upstream Load Balancing

Cisco IOS Release 12.3(17b)BC4 introduces further enhancements to downstream load balancing, resulting in equalized upstream load balancing group members. This enhancement synchronizes the pending statistic between different cable interface line cards in the load balancing group.

This enhancement performs downstream load balancing that accounts for loads on upstream channels in the same upstream load balancing group, rather than on the basis of the entire downstream channel load. Prior Cisco IOS releases may not have distributed cable modems evenly over individual upstream channels, nor in a way that accounted for downstream and upstream segment loads that account for one another.

This enhancement applies when downstream load balancing occurs on a headend system with separate upstream load balancing segments; the upstream segments are spread over multiple downstreams segments. This enhancement provides an alternative downstream load balancing scheme that accounts and makes use of per-upstream loads rather than total downstream loads.

For additional information about Load Balancing on the Cisco CMTS, refer to the following documents on Cisco.com:

Load Balancing and Dynamic Channel Change on the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/ubr_load-bal_dcc.html

Cisco Broadband Cable Command Reference Guide

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

New Hardware Features in Cisco IOS Release 12.3(17b)BC3

There are no new hardware features supported in Cisco IOS Release 12.3(17b)BC3.

New Software Features in Cisco IOS Release 12.3(17b)BC3

There are no new software features supported in Cisco IOS Release 12.3(17b)BC3.

New Hardware Features in Cisco IOS Release 12.3(17a)BC2

There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC2.

New Software Features in Cisco IOS Release 12.3(17a)BC2

The following software features are new in Cisco IOS Release 12.3(17a)BC2:

Cisco Advanced-Mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS

Cisco IOS Release 12.3(17a)BC2 introduces certified support for advanced-mode DOCSIS Set-Top Gateway (DSG) Issue 1.2. DSG Issue 1.2 introduces support for the latest DOCSIS Set-Top specification from CableLabs™:

DOCSIS Set-top Gateway (DSG) Interface Specification, CM-SP-DSG-I05-050812

Cisco Advanced-mode DSG 1.2 is certified by CableLabs™, and is a powerful tool in support of latest industry innovations. Advanced-mode DSG 1.2 offers substantial support for enhanced DOCSIS implementation in the Broadband Cable environment. The set-top box dynamically learns the overall environment from the Cisco Cable Modem Termination System (CMTS), to include MAC address, traffic management rules, and classifiers. DSG 1.2 supports the DOCS-DSG-IF-MIB as one component of this functionality:

For additional information, refer to the following document on Cisco.com:

Advanced-mode DOCSIS Set-Top Gateway 1.2 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdsg12.html

Cisco CMTS Universal Broadband Router MIB Specifications Guide, Rel 12.3(17a)BC2

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

DOCSIS1.0 TOS Overwrite

Currently, ToS overwrite requires the creation of static cable QoS profiles, which are then assigned to the ToS fields. This implementation works well if only a few different service types are offered. However, scalability issues arise when large numbers of service types are presented; each requiring a static QoS profile in order to perform ToS overwrite.

The Default DOCSIS 1.0 ToS Overwrite feature eliminates the need to create multiple QoS profiles in order to perform type-of-service (ToS) overwrite by automatically bounding all DOCSIS 1.0 Cable Modem (CM) created profiles to a default ToS overwrite.

New Hardware Features in Cisco IOS Release 12.3(17a)BC1

There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC1:

New Software Features in Cisco IOS Release 12.3(17a)BC1

There are no new software features supported in Cisco IOS Release 12.3(17a)BC1.

New Hardware Features in Cisco IOS Release 12.3(17a)BC

There are no new hardware features supported in Cisco IOS Release 12.3(17a)BC.

New Software Features in Cisco IOS Release 12.3(17a)BC

The following software features are new in Cisco IOS Release 12.3(17a)BC:

Cable Monitor Enhancements

CNEM Compliance

Dynamic Channel Change (DCC) for Load Balancing

DOCSIS 2.0 SAMIS ECR Data Set

DSX Messages and Synchronized PHS Information

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

High Availability Support for Encrypted IP Multicast

IPv6 over L2VPN

Management Information Base (MIB) Changes and Enhancements

Pre-equalization Control for Cable Modems

PXF ARP Filter

PXF Divert Rate Limiting

Secure Socket Layer Server for Usage-Based Billing

SSM Mapping

Cable Monitor Enhancements

Cisco IOS Release 12.3(17a)BC introduces the following enhancements to the cable monitor feature:

Access Control Lists are now supported on the Cisco uBR-MC5X20U/D and Cisco uBR-MC28U cable interface line cards

Unconditional downstream sniffing now enables downstream packets to be monitored, either for MAC or data packets. This enhancement supports both DOCSIS and Ethernet packet encapsulation.

For additional information about this enhancements to the cable monitor feature, refer to the following documents on Cisco.com:

Cable Monitor and Intercept Features on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

CNEM Compliance

The Consistent Network Element Manageability (CNEM) Compliance feature enhances the network management capability of the CMTS platform by enabling the CMTS platform to be compliant with CNEM 1.3 requirements.

CNEM 1.3 requirements are designed to enable element management systems, with a minimum amount of effort, to maximize their coverage across the Cisco product line of network elements.

For additional information, refer to the following document on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

DOCSIS 2.0 SAMIS ECR Data Set

The Usage-Based Billing feature for the Cisco Cable Modem Termination System (CMTS) provides subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. The SAMIS format is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.

Release 12.3(17a)BC provides enhancements to the OSSI specifications, and billing reports (billing record format), added support to the CISCO-CABLE-METERING-MIB, which contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, added support for DCC and DCC for Load balancing and Downstream LLQ.

For additional information, refer to the following document on Cisco.com:

Usage-Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_use-bsd_bill_ps2209_TSD_Products_Configuration_Guide_Chapter.html

DSX Messages and Synchronized PHS Information

Cisco IOS Release 12.3(17a)BC introduces support for PHS rules in a High Availability environment. In this release, and later releases, PHS rules synchronize and are supported during a switchover event of these types:

Route Processor Redundancy Plus (RPR+), with Active and Standby Performance Routing Engines (PREs)

HCCP N+1 Redundancy, with Working and Protect cable interface line cards

For additional information about these enhancements, and related High Availability features, refer to the following documents on Cisco.com:

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Route Processor Redundancy Plus for the Cisco uBR10012 Router

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html

Dynamic Channel Change (DCC) for Load Balancing

Cisco IOS Release 12.3(17a)BC introduces Dynamic Channel Change (DCC) and DCC for Load Balancing on the Cisco CMTS.

DCC in DOCSIS 1.1 dynamically changes cable modem upstream or downstream channels without forcing a cable modem to go offline, and without re-registration after the change. DCC supports four different initializations, instead of one, as in earlier DOCSIS support.

DCC and DCC for load balancing is supported on the Cisco uBR7246VXR router and the Cisco uBR10012 router with distributed cable interface line cards, including the Cisco MC28U and the Cisco MC5X20S/U/H.

Load Balancing techniques allow for moving cable modems with DCC by using configurable initialization techniques.

DCC allows line card channel changes across separate downstream channels in the same cable interface line card, with the DCC initialization techniques ranging from 0 to 4.

DCC transfers cable modem state information from the originating downstream channel to the target downstream channel, and maintains synchronization of the cable modem information between the cable interface line card and the Network Processing Engine (NPE) or Route Processor (RP).

When the target channel is in ATDMA mode, only DOCSIS 2.0-capable modems can be successfully load balanced. (Only DOCSIS 2.0-capable modems can operate on an ATDMA-only upstream channel.) Cisco recommends identical channel configurations in a load balancing group.

Dynamic Channel Change for Load Balancing entails the following new or enhanced commands in Cisco IOS Release 12.3(17a)BC, and later releases:

Global Configuration Commands

cable load-balance group group-num dcc-init-technique <0-4>

cable load-balance group group-num policy { pcmm | ugs }

cable load-balance group group-num threshold {load | pcmm | stability | ugs} <1-100>

cable load-balance group group-num threshold load <1-100> {minimum}

cable load-balance group group-num threshold load <1-100> {enforce}

Testing Command

test cable dcc mac-addr {slot/port | slot/subslot/port} target-us-channel-id ranging-technique

For configuration, command reference, testing, and examples for DCC on the Cisco CMTS, refer to the following documents on Cisco.com:

Load Balancing and Dynamic Channel Change (DCC) on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html

Cisco Broadband Cable Command Reference Guide

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

Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012

Cisco IOS Release 12.3(17a)BC introduces Generic Routing Encapsulation (GRE) Tunneling on the Cisco uBR10012.

Generic Route Encapsulation (GRE) is a tunneling protocol that can encapsulate a variety of packet types inside IP tunnels, creating a virtual point-to-point link to Cisco routers at remote points over an IP internetwork.

Globally Configured HCCP 4+1 and 7+1 Redundancy on the Cisco uBR10012 Router

Cisco IOS Release 12.3(17a)BC introduces support for globally-configured HCCP N+1 Redundancy on the Cisco uBR10012 router. Cisco IOS Release 12.3(17a)BC supports both 4+1 and 7+1 Redundancy, in these High Availability configurations:

7+1 Redundancy, supporting the Cisco uBR10012 router with two Cisco RF Switches

In this configuration, seven Working cable interface line cards are supported by one Protect cable interface line card. Two Cisco RF Switches are connected to seven MC5X20U/D cable interface line cards. Switchover events apply to an entire line card, rather than on an interface level, as in previous Cisco IOS releases supporting 7+1 Redundancy. Global configuration makes this High Availability feature easier to configure and use. 7+1 Redundancy is the default redundancy scheme for the Cisco uBR10012 router in Cisco IOS Release 12.3(17a)BC.

4+1 Redundancy, supporting the Cisco uBR10012 router with one Cisco RF Switch

In this configuration, four Working cable interface line cards are supported by one Protect line card. One Cisco RF Switch is connected to five cable interface line cards. Switchover events apply to an entire line card.

Either form of N+1 Redundancy supports the Cisco uBR-MC5X20U/D broadband processing engine (BPE) on the Cisco uBR10012 router.


Note N+1 Redundancy requires that all BPEs in the Cisco uBR10012 router be the same. Only the Cisco uBR-MC5X20U/D BPE is supported.



Note Cisco IOS Release 12.3(17a)BC introduces simplified global configuration commands, supporting 4+1 or 7+1 Redundancy on the Cisco uBR10012 router. However, earlier configuration commands are not supported when Global-level N+1 Redundancy is configured on the Cisco uBR10012 router.


For additional information about HCCP 4+1 Redundancy, refer to the following document on Cisco.com:

N+1 Redundancy for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

High Availability Support for Encrypted IP Multicast

Cisco IOS Release 12.3(17a)BC introduces support for IP Multicast streams during switchover events in a High Availability environment. This feature is supported for Route Processor Redundancy Plus (RPR+), N+1 Redundancy, and encrypted BPI+ streams.

For additional information about IP Multicast and High Availability, refer to these documents on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Dynamic Shared Secret for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_dyn_sh_sec_ps2209_TSD_Products_Configuration_Guide_Chapter.html

IP Multicast in Cable Networks, White Paper

http://www.cisco.com/en/US/technologies/tk648/tk828/technologies_case_study0900aecd802e2ce2.html

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_nplus1_redun_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Route Processor Redundancy Plus for the Cisco uBR10012 Router

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_feature_guide09186a00801a24e0.html

IPv6 over L2VPN

Beginning with Cisco IOS Release 12.3(17a)BC, the Cisco uBR10012 router now supports IPv6 using Layer 2 VPNs based on SID to 802.1q mapping. The Cisco uBR10012 router already supported Transparent LAN service with Layer 2 VPNs in Cisco IOS Release 12.3(13a)BC and later releases. As more Internet users switch to IPv6, the Cisco IPv6 protocol support helps enable the transition. IPv6 fixes a number of limitations in IPv4, such as limited numbers of available IPv4 addresses in addition to improved routing and network auto-configuration. This feature allows customers to introduce IPv6 into their network with minimal operational impact.

For additional information about this feature, refer to the following documents on Cisco.com:

IPv6 Documentation: overview, technology, design and configuration information

http://www.cisco.com/en/US/tech/tk872/tsd_technology_support_protocol_home.html

Management Information Base (MIB) Changes and Enhancements

MIB enhancements in Cisco IOS Release 12.3(17a)BC provide enhanced management features that enable the Cisco uBR 7200 Series router and the Cisco uBR10012 router to be managed through the Simple Network Management Protocol (SNMP). These enhanced management features allow you to:

Use SNMP set and get requests to access information in Cisco CMTS universal broadband routers.

Reduce the amount of time and system resources required to perform functions like inventory management.

A standards-based technology (SNMP) for monitoring faults and performance on the router.

Support for SNMP versions (SNMPv1, SNMPv2c, and SNMPv3).

Notification of faults, alarms, and conditions that can affect services.

For additional information, refer to the following document on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Pre-equalization Control for Cable Modems

Cisco IOS Release 12.3(17a)BC introduces pre-equalization control for cable modems on a per-modem basis. This feature enhances support for pre-equalization control on an interface basis, using the Organizational Unique Identifier (OUI), which is also supported.

When pre-equalization is enabled on an upstream interface, this feature allows you to disable pre-equalization adjustment selectively, for a specific cable modem or a group of cable modems. This feature prevents cable modems from flapping when processing pre-equalization requests sent from the Cisco CMTS.

Restrictions

This feature observes the following restrictions in Cisco IOS Release 12.3(17a)BC:

For pre-equalization to be supported on a per-modem basis, the cable modem must send verification of pre-equalization after it registers with the Cisco CMTS.

The option of excluding the OUI is a global configuration. For the cable modem on which OUI is excluded, the excluded OUI is disabled for all interfaces. This method uses a list of OUI values, recording which modems are sent and not sent pre-equalization.

able pre-equalization exclude

To exclude a cable modem from pre-equalization during registration with the Cisco CMTS, use the cable pre-equalization exclude command in global configuration mode. Exclusion is supported for a specified cable modem, or for a specified OUI value for the entire interface. To remove exclusion for the specified cable modem or interface, use the no form of this command. Removing this configuration returns the cable modem or interface to normal pre-equalization processes during cable modem registration.

cable pre-equalization exclude {oui | modem} mac-addr

no cable pre-equalization exclude {oui | modem} mac-addr

Syntax Description

oui

Organizational Unique identifier for the interface specified. Using this keyword excludes the specified OUI during cable modem registration for the associated interface.

modem

Cable Modem identifier for the cable modem specified. Using this keyword excludes the cable modem.

mac-addr

Identifier for the OUI or cable modem to be excluded.


Command Default

Pre-equalization is enabled by default on the Cisco router, and for cable modems that have a valid and operational DOCSIS configuration file. When enabled, pre-equalization sends ranging messages for the respective cable modems. When disabled with the new exclude command, pre-equalization is excluded for the respective cable modems.

Command Modes

Global configuration mode

Command History

Release
Modification

12.3(17a)BC

This command was introduced to the Cisco uBR10012 router and the Cisco uBR7246VXR router.


Usage Guidelines

The pre-equalization exclusion feature should be configured for the running configuration of the Network Processing Engine (NPE), the Performance Routing Engine (PRE), and the line card console.

Examples

The following example configures pre-equalization to be excluded for the specified cable modem. Pre-equalization data is not sent for the corresponding cable modem:

Router(config)# cable pre-equalization exclude modem mac-add

The following example configures pre-equalization to be excluded for the specified OUI value of the entire interface. Pre-equalization data is not sent for the corresponding OUI value of the entire interface:

Router(config)# cable pre-equalization exclude oui mac-addr

The following series of commands configures pre-equalization on the Cisco uBR10012 router with MC5X20U BPEs. On the PRE Console, configure the following commands.

Router# conf t
Enter configuration commands, one per line.  End with CNTL/Z.
Router(config)# cable pre-equalization exclude oui 00.09.04
Router(config)# end
Router# show run
Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04

On the line card console for the same Cisco uBR10012 router, verify the configuration with the following command:

Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.04

The following series of commands configures pre-equalization on the Cisco uBR72436VXR router with MC28U cable interface line cards. On the Network Processing Engine (NPE) console, configure and verify with the following commands.

Router# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# cable pre-equalization exclude oui 00.09.24
Router(config)# end
Router# show run
02:58:10: %SYS-5-CONFIG_I: Configured from console by consolen
Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24

On the line card console for the same Cisco uBR7246VXR router, verify the configuration with the following command:

Router# show running-config | inc oui
cable pre-equalization exclude oui 00.09.24

After either of these exclusion methods for pre-equalization are configured, you can verify that all ranging messages do not include pre-equalization data. Use the following debug commands in global configuration mode:

debug cable range

debug cable interface cx/x/x mac-addr

Verify the ranging message for the non-excluded cable modems include pre-equalization data, and for the excluded cable modems, the ranging messages do not include such data.

The following example removes pre-equalization exclusion for the specified OUI and interface. This results in the cable modem or OUI to return to normal pre-equalization functions. Ranging messages resume sending pre-equalization data.

Router(config)# no cable pre-equalization exclude { oui | modem } mac-addr

Removal of this feature can be verified with the following debug command:

debug cable interface cx/x/x mac-ad—Verifies the ranging message for all non-excl modems include pre-eq data, and for the excluded modems ranging messages do not include pre-eq data.

For additional information about this or other commands, refer to the following documents on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

PXF ARP Filter

Cisco IOS Release 12.3(17a)BC introduces PXF ARP Filter feature. The ARP filter now has a PXF component that filters ARP packets for identified "ARP offenders", thereby decreasing ARP punt rate and RP CPU usage.

For additional information, refer to the following document on Cisco.com

Cable ARP Filtering

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_cbl_arp_fltr_ps2209_TSD_Products_Configuration_Guide_Chapter.html

PXF Divert Rate Limiting

Cisco IOS Release 12.3(17a)BC introduces PXF Divert Rate Limiting feature. Rate-limiting on the divert path causes packets that will cause congestion to toRP queues to be dropped, before any packets have been queued, so valid packets are unaffected.

For additional information, refer to the following document on Cisco.com

Cable ARP Filtering

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_cbl_arp_fltr_ps2209_TSD_Products_Configuration_Guide_Chapter.html

show cable modem Command Changes

Cisco IOS Release 12.3(17a)BC introduces changes for two versions of the show cable modem command.

show cable modem mac summary

The information displayed with this command is revised. The DOCSIS 2.0 column in the Quality of Service (QoS) Provision Mode field has been removed, as this field is not applicable to QoS provisioning in DOCSIS 2.0.

Command Output in Cisco IOS Release 12.3(17a)BC and Later Releases

Router# show cable modem mac summary 
                            Cable Modem Summary
                            -------------------
                         Mac Version                 QoS Provision Mode
Interface       Total   DOC2.0  DOC1.1  DOC1.0   Reg/Online   DOC1.1  DOC1.0
Cable5/1/0/U0   10      0       2       8        10           0       10

Command Output in Cisco IOS Release 12.3(13a)BC and Earlier Releases

Router# show cable modem mac summary
                            Cable Modem Summary
                            -------------------
                         Mac Version                 QoS Provision Mode
Interface       Total   DOC2.0  DOC1.1  DOC1.0   Reg/Online   DOC2.0  DOC1.1  DOC1.0
Cable8/0/0/U0   8       0       5       3        5            0       5       0

show cable modem phy

The information displayed with this command is revised. The MicroReflec column (MicroReflections) has been removed, and the DOCSIS Prov (DOCSIS Provider) column has been added in its place. This new column contains DOCSIS version information.

Command Output in Cisco IOS Release 12.3(17a)BC and Later Releases

Router#show cable modem phy 
MAC Address    I/F         Sid  USPwr  USSNR  Timing  DSPwr  DSSNR  Mode  DOCSIS
                                (dBmV) (dB)   Offset  (dBmV) (dB)         Prov 
0003.e350.9a3f C5/1/0/U0   1    0.00   30.23  2811    0.00   -----  tdma  1.0
0050.734e.c1a1 C5/1/0/U0   2    0.00   30.47  2811    0.00   -----  tdma  1.0
0007.0e01.1749 C5/1/0/U0   3    0.00   30.65  2808    0.00   -----  tdma  1.0
0007.0e00.90dd C5/1/0/U0   4    0.00   30.66  2806    0.00   -----  tdma  1.0
0003.e350.9ad3 C5/1/0/U0   5    0.00   30.47  2810    0.00   -----  tdma  1.0
0003.e38f.f4e5 C5/1/0/U0   6    0.00   30.36  2813    0.00   -----  tdma  1.0
0003.e350.9b97 C5/1/0/U0   7    0.00   30.44  2812    0.00   -----  tdma  1.0
0003.e350.9bed C5/1/0/U0   8    0.00   30.16  2814    0.00   -----  tdma  1.0
0003.e308.455d C5/1/0/U0   9    0.00   30.79  2811    0.00   -----  tdma  1.0
0003.6bd6.bfaf C5/1/0/U0   10   0.00   30.40  2813    0.00   -----  tdma  1.0

Command Output in Cisco IOS Release 12.3(13a)BC and Earlier Releases

Router#show cable modem phy
MAC Address    I/F         Sid  USPwr  USSNR  Timing MicroReflec DSPwr  DSSNR  Mode
                                (dBmV)  (dB)   Offset (dBc)      (dBmV)   (dB)     
0008.0e06.7b14 C8/0/0/U0   1    0.00   30.36  1938   0            0.00  -----  tdma 
0050.f112.5977 C8/0/0/U0   2    0.00   30.36  1695   0            0.00  -----  tdma 
0090.837b.b0b9 C8/0/0/U0   3    0.00   30.64  1187   0            0.00  -----  tdma 
0007.0e03.6e99 C8/0/0/U0   5    0.00   30.36  2747   0            0.00  -----  tdma 
0007.0e04.5091 C8/0/0/U0   6    0.00   30.94  2746   0            0.00  -----  tdma 
0006.5314.81d9 C8/0/0/U0   7    0.00   30.36  2745   0            0.00  -----  tdma 
0003.6b1b.ee63 C8/0/0/U0   8    0.00   31.26  2745   0            0.00  -----  tdma 
0030.eb15.84e7 C8/0/0/U0   12   0.00   30.36  1157   0            0.00  -----  tdma 

For additional information about this or other commands, refer to the following documents on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

Secure Socket Layer Server for Usage-Based Billing

Cisco IOS Release 12.3(17a)BC introduces support for the Secure Socket Layer (SSL) Server, used with the Usage-Based Billing feature of the Cisco CMTS. Usage-Based Billing implements the DOCSIS Subscriber Account Management Interface Specification (SAMIS) format.

This new capability enables the configuration of the SSL server between the Cisco CMTS and a collection server. Configuration, certificate creation, and debug commands are added or enhanced to support the SSL Server and certificates with the Usage-Based Billing feature.

For additional information, refer to the following document on Cisco.com:

Usage-Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_use-bsd_bill_ps2209_TSD_Products_Configuration_Guide_Chapter.html

SSM Mapping

Cisco IOS Release 12.3(17a)BC introduces Source-Specific Multicast (SSM) Mapping support on the Cisco uBR10012 router.

When the SSM Mapping feature is configured, if a router receives an IGMP version 1 or version 2 membership report for a particular group G, the router translates this in one or more SSM (S, G) channel memberships, such as IGMPv3 (S, G) INCLUDE membership reports) for the well known sources associated with this group.

When the router receives an IGMP version 1 or version 2 membership report for group G, the router uses SSM mapping to determine one or more source IP addresses (Si) for group G. SSM mapping then translates the membership report as an IGMP version 3 report INCLUDE (G, [S1, G], [S2, G]...[Sn, G] and continues as if it had received an IGMP version 3 report. The router then sends out PIM joins toward (S1, G) to (Sn, G) and continues to be joined to these groups as long as it continues to receive the IGMP version 1 or version 2 membership reports and as long as the SSM mapping for the group remains the same.

When SSM Mapping feature is statically configured on the router, the source address or addresses (S) can be discovered either by a statically configured table on the router or by consulting a DNS. When the statically configured table is changed, or when the DNS mapping changes, the router will leave join to the current sources associated with the joined groups.

For additional information about this feature, refer to the following documents on Cisco.com:

Source Specific Multicast (SSM) Mapping

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html

New Hardware Features in Cisco IOS Release 12.3(13a)BC6

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC6:

New Software Features in Cisco IOS Release 12.3(13a)BC6

There are no new software features supported in Cisco IOS Release 12.3(13a)BC6.

New Hardware Features in Cisco IOS Release 12.3(13a)BC5

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC5:

New Software Features in Cisco IOS Release 12.3(13a)BC5

There are no new software features supported in Cisco IOS Release 12.3(13a)BC5.

New Hardware Features in Cisco IOS Release 12.3(13a)BC4

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC4:

New Software Features in Cisco IOS Release 12.3(13a)BC4

There are no new software features supported in Cisco IOS Release 12.3(13a)BC4.

New Hardware Features in Cisco IOS Release 12.3(13a)BC3

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC3:

New Software Features in Cisco IOS Release 12.3(13a)BC3

There are no new software features supported in Cisco IOS Release 12.3(13a)BC3.

New Hardware Features in Cisco IOS Release 12.3(13a)BC2

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC2:

New Software Features in Cisco IOS Release 12.3(13a)BC2

There are no new software features supported in Cisco IOS Release 12.3(13a)BC2.

New Hardware Features in Cisco IOS Release 12.3(13a)BC1

There are no new hardware features supported in Cisco IOS Release 12.3(13a)BC1.

New Software Features in Cisco IOS Release 12.3(13a)BC1

There are no new software features supported in Cisco IOS Release 12.3(13a)BC1.

New Hardware Features in Cisco IOS Release 12.3(13a)BC

The following hardware features are new in Cisco IOS Release 12.3(13a)BC:

Cisco Half-Height Gigabit Ethernet Line Card

Processor/IO Memory for the PRE1 Route Processor Module

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco Half-Height Gigabit Ethernet Line Card

Cisco IOS Release 12.3(13a)BC introduces support for the new Cisco Half-Height Gigabit Ethernet line card (HHGE) for the Cisco uBR10012 router. The HHGE line card is a half-height, single-port, full-bandwidth Gigabit Ethernet line card providing multiple GigE links to the IP backbone. The HHGE line card also supports DOCSIS wideband capability through the Cisco uBR10012 universal broadband router.

The HHGE line card supports IEEE 802.3z-compliant Ethernet interface that can run up to 1 Gbps in full duplex mode. The HHGE line card supports single Ethernet interfaces based on SFP GBIC technology, supporting 1000BASE-SX and 1000BASE-LX/LH physical interfaces with SFP modules. It provides full-duplex 1 Gbps data rate with the PRE-2 performance routing engine module.

The following SFPs are supported by this line card:

1000BASE-SX SFP—The SFP-GE-S, 1000BASE-SX SFP operates on ordinary multimode fiber optic link spans of up to 550 meters in length.

1000BASE-LX/LH SFP—The SFP-GE-L-SM, 1000BASE-LX/LH SFP operates on ordinary single-mode fiber optic link spans of up to 10,000 meters in length.

1000BASE-ZX SFP—The GLC-ZX-SM, 1000BASE-ZX SFP operates on ordinary single-mode fiber optic link spans of up to 70 kilometers (km) in length.

Link spans of up to 100 km are possible using premium single-mode fiber or dispersion-shifted single-mode fiber. The SFP provides an optical link budget of 23 dB—the precise link span length depends on multiple factors such as fiber quality, number of splices, and connectors.

Restrictions

The HHGE line card cannot be used in slot 1 (subslot 1 or 0), or slot 2 (subslot 1 or 0) in the Cisco uBR10012 universal broadband router.

Additional Information

For additional information about the Cisco Half-Height Gigabit Ethernet Line Card, refer to the following documents on Cisco.com:

Cisco uBR10012 Universal Broadband Router Half-Height Gigabit Ethernet Line Card Installation Quick Start

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubr_hh_ge/quick/start/ubr_hhge.html

Upgrading to the Half-Height Gigabit Ethernet Line Card for the Cisco uBR10012 Universal Broadband Router

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubr_hh_ge/quick/start/ubr_hhge.html

Configuring the Half-Height Gigabit Ethernet Line Card for the Cisco uBR10012 Universal Broadband Router

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubr_hh_ge/configuration/guide/hhgefm10.html

Cisco uBR10012 Universal Broadband Router Hardware Installation Guide

http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/guide/u10kspec.html

Processor/IO Memory for the PRE1 Route Processor Module

Cisco IOS Release 12.3(13a)BC introduces support for and availability of additional processor and input/output (I/O) memory for PRE1 route processor modules on the Cisco uBR10012 router.

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Commencing with Cisco IOS Release 12.3(9a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:

PacketCable 1.0 With CALEA

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Commencing with Cisco IOS Release 12.3(13a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these and additional features:

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

DOCSIS BPI+ Multiple Root Certificate Support

PacketCable Multimedia for the Cisco CMTS

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

The Cisco uBR10012 OC-48 DPT/POS interface module supports both PRE1 and PRE2 performance routing engine modules in the Cisco uBR10012 router chassis. The Cisco OC-48 DPT/POS interface module is a dual-mode module, providing interface support for Packet over SONET (POS) or Spatial Reuse Protocol (SRP).

For additional information about installing and configuring the Cisco uBR10012 OC-48 DPT/POS interface module, refer to these documents on Cisco.com:

Cisco uBR10012 OC-48 DPT/POS Interface Module (FRU Installation Guide)

http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/field_replaceable_units/ub_oc48.html

Configuring the Cisco uBR10012 OC-48 DPT/POS Interface Module

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubr_oc48_dpt_pos/configuration/guide/oc48pre2.html

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 performance routing engine 2 (PRE2) route processing modules.

The Cisco uBR10012, which is qualified for PacketCable 1.0, Data over Cable Service Interface Specifications (DOCSIS) 1.1 and EuroDOCSIS 1.1, is built to meet the current and future needs of multiple system operators (MSOs). With full Layer 3 routing capabilities and industry-leading capacity and scalability, the Cisco uBR10012 delivers the highest level of performance for mass deployment of next-generation IP services.

The Cisco uBR10012 is designed to meet the services, performance, and reliability required for large-scale multiservice applications. The Cisco uBR10012 allows cable providers to deliver value-added IP services with consistent high performance. Based on Cisco IOS® Software—the standard in routing technology—the Cisco uBR10012 offers the most advanced networking and routing options available.

The Cisco uBR10012 features these components:

Eight cable line cards to connect to the cable plant

Four high-performance WAN interfaces to connect to the IP backbone and external networks

Two Cisco Timing, Communication, and Control Plus (TCC+) cards to monitor the line cards and power supply

Two Cisco Performance Routing Engine (PRE) modules with Parallel Express Forwarding (PXF) processors for consistent, high-performance throughput, even with multiple services enabled

Two Power Entry Modules (PEMs) for uninterrupted power supply

Benefits of the Cisco uBR10012 PRE2 include the following:

Provides up to 6.2 mpps of processing power in the Cisco uBR10012 router

Backplane supports up to 6.4 Gbps duplex per slot

Uses Cisco patented PXF technology to provide maximum IP services performance

Supports processor redundancy— for enabling 99.999-percent network uptime

Supports Route Processor Redundancy Plus (RPR+) High Availability functions in the Cisco uBR10012 CMTS headend

Table 4 provides additional details about the features and benefits of the Cisco uBR10012 PRE2.

Table 4 Features and Benefits of Cisco uBR10012 PRE2

Features
Benefits

Provides up to 6.2-mpps processing.

The Cisco uBR10012 router with PRE2 provides the IP services and performance that service providers require when deploying new revenue-generating services. In contrast to other CMTS products that support only distributed processing or only centralized processing, the Cisco uBR10012 supports a mix of distributed, centralized, and parallel processing. This ensures optimized performance to a comprehensive suite of line-rate IP services.

Uses Cisco patented PXF technology to provide maximum IP services performance.

PXF technology provides the Cisco uBR10012 router with performance and consistent high throughput, even with multiple, simultaneous services enabled. Using PXF, the Cisco uBR10012 router enables service providers to turn on multiple services without experiencing performance degradation. This is crucial when service providers look to upgrade customers to new types of services. In addition, PXF is a software-based technology that enables the Cisco uBR10012 router to implement new services without upgrading hardware—thereby providing investment protection and saving customers time and money.

Supports processor redundancy—for enabling 99.999-percent network uptime.

Each Cisco uBR10012 chassis supports up to two PRE2 modules for redundancy. The Cisco uBR10012 router is designed to support 99.999-percent uptime and coupled with a superior set of high-availability features and functions.


Upgrading from Cisco uBR10012 PRE or PRE1 Modules to Cisco uBR10012 PRE2 Modules

For information about insertion, removal and upgrade of Field Replaceable Units such as the PRE2 modules, refer to the following document on Cisco.com:

Cisco uBR10012 Universal Broadband Router Performance Routing Engine Module 2

http://www.cisco.com/en/US/docs/interfaces_modules/cable/performance_routing_engine/installation/guide/pre5096.html

Cisco Performance Routing Engine (ESR-PRE2) Upgrade Installation

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_quick_start09186a00802b5eaa.html

New Software Features for Cisco IOS Release 12.3(13a)BC

This section describes the following new software features and CLI command changes for Cisco IOS Release 12.3(13a)BC and the Cisco uBR10012 router:

Access Control List Support for COPS Intercept

Admission Control for the Cisco CMTS

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Backup Path Testing for the Cisco RF Switch

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

COPS TCP Support for the Cisco Cable Modem Termination System

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

DOCSIS 1.0 Concatenation Override

DOCSIS BPI+ Multiple Root Certificate Support

Dynamic SID/VRF Mapping Support

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

High Availability Features:

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Global N+1 RedundancyShutdown and No Shutdown Enhancement for Cable Interfaces

MIBs Enhancements

Multicast QoS Support on the Cisco uBR10012 CMTS

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Optional Upstream Scheduler Modes

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

PacketCable Multimedia for the Cisco CMTS

Service Independent Intercept (SII) Support

Transparent LAN Service and Layer 2 Virtual Private Networks

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

Access Control List Support for COPS Intercept

Cisco IOS Release 12.3(13a)BC introduces enhanced support for Access Control Lists (ACLs) and associated commands for the Common Open Policy Service (COPS) feature.

To configure access control lists (ACLs) for inbound connections to all COPS listener applications on the Cisco CMTS, user the cops listeners access-list command in global configuration mode. To remove this setting from the Cisco CMTS, us the no form of this command.

cops listeners access-list {acl-num | acl-name}

no cops listeners access-list {acl-num | acl-name}

Syntax Description

acl-num

Alphanumeric identifier of up to 30 characters, beginning with a letter that identifies the ACL to apply to the current interface.

acl-name

Numeric identifier that identifies the access list to apply to the current interface. For standard access lists, the valid range is 1 to 99; for extended access lists, the valid range is 100 to 199.



Note When using Access Control Lists (ACLs) with cable monitor and the Cisco uBR10012 router, combine multiple ACLs into one ACL, and then configure cable monitor with the consolidated ACL.


Additional Information

Refer also the Service Independent Intercept (SII) feature in this document. For additional information, refer to the following documents on Cisco.com:

Configuring COPS for RSVP, Cisco IOS Versions 12.2 and 12.3

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_cops_eng_op_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_mon_intrcpt_ps2209_TSD_Products_Configuration_Guide_Chapter.html

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_pktcable_mm_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml

Admission Control for the Cisco CMTS

Cisco IOS Release 12.3(13a)BC introduces Admission Control for the Cisco Cable Modem Termination System (CMTS).

Admission Control for the Cisco Cable Modem Termination System (CMTS) is a multifaceted feature that implements a Quality of Service (QoS) policy on the CMTS Headend. Admission Control establishes efficient resource and bandwidth utilization in a way that was not possible in prior Cisco IOS releases.

Admission Control monitors multiple system-level resources on the Cisco CMTS, and performs automatic resource allocation on a service-request basis. Admission Control maintains optimal system-level operation by preventing resource consumption that would otherwise degrade the performance for the entire Cisco CMTS. Furthermore, Admission Control can allocate upstream or downstream bandwidth resources to specific DOCSIS traffic types, and maintain such prioritization amidst very dynamic traffic conditions.

Admission Control uses two event types for resource monitoring and management—cable modem registration and dynamic service (voice call) requests. When either of these two events occurs on the Cisco CMTS, Admission Control verifies that the associated resources conform to the configured limits prior to admitting and supporting the service call request.

Admission Control is not a mechanism to apply QOS to the traffic flows. Scheduling and queuing are some of the mechanisms used for implementing the QOS. The QOS is applied on a per-packet basis. Admission Control checks are performed before the flow is committed.

Admission Control in Cisco IOS Release 12.3(13)BC monitors the following resources on the Cisco CMTS.

CPU utilization—Admission Control monitors CPU utilization on the Cisco CMTS, and preserves QoS for existing service flows when new traffic would otherwise compromise CPU resources on the Cisco CMTS.

Memory resource utilization (I/O, Processor, and combined total)—Admission Control monitors one or both memory resources and their consumption, and preserves QoS in the same way as CPU utilization.

Bandwidth utilization for upstream and downstream—Admission Control monitors upstream and downstream bandwidth utilization, and associated service classes, whether for data or dynamic service traffic.

Cisco IOS Release 12.3(13a)BC introduces new configuration, debug and show commands for Admission Control on the Cisco CMTS. For additional information, refer to the following document on Cisco.com:

Admission Control for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_adm.html

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1

Cisco IOS Release 12.3(13a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.1 on the Cisco uBR10012 router. DSG 1.1 builds on and supports the enhancements of DOCSIS Set-Top Gateway Issue 1.0 in the prior Cisco IOS 12.3(9a)BC release.

A-DSG 1.1 introduces powerful support for DOCSIS 1.1 and DOCSIS 2.0, and the latest DOCSIS DSG specifications. The benefits provided by A-DSG include the following:

Retains the essential nature of out of band (OOB) messaging, but moves it to a modern technology base.

Replaces single-vendor, low-density, special-purpose equipment on the network, with significantly increased subscriber bandwidth and traffic.

Consolidates cable modem and STB data traffic on a shared DOCSIS channel.

Increases high-speed data (HSD) services to cable TV subscribers over the DOCSIS 1.1 infrastructure,

Extends support for DOCSIS 1.1 digital video broadcast traffic.

Enables shared or dedicated support for either HSD or video traffic.

Supports one- or two-way operations, and advanced, two-way interactive applications such as streaming video, Web browsing, e-mail, real-time chat applications, and targeted advertising services.

These powerful advantages maximize the performance and return of hybrid fiber-coaxial (HFC) plant investments.

Changes from Cisco DSG 1.0

DSG Issue 1.0 is oriented to the DOCSIS DSG-I01 specifications, while DSG Issue 1.1 is oriented towards DOCSIS DSG-I02 specifications, to include the new Advanced Mode DSG (A-DSG).

The following DSG 1.1 features are supported in 12.3(13a)BC while continuing support for Basic Mode DSG:

DSG 1.1 enables the learning of dynamic tunnel definitions. DSG 1.0 only had static tunnel definitions (programmed into the set-top box).

DSG 1.1 features new Cisco IOS command-line interface (CLI) configuration and show commands for A-DSG configuration and network information.

Unlike earlier issues of DSG, Advanced-mode DSG (A-DSG) uses a DOCSIS MAC Management Message called the Downstream Channel Descriptor (DCD) message, and this DCD message manages the DSG Tunnel traffic. The DCD message is sent once per second on each downstream and is used by the DSG Client to determine which tunnel and classifier to use.

The DCD has a DSG address table located in the DOCSIS MAC management message. The primary difference between DSG 1.0 (and earlier issues) and A-DSG 1.1 is that advanced mode uses DCD messages to manage the DSG tunnels.

The DCD message contains a group of DSG Rules and DSG Classifiers, including the following:

DSG rules and rule priority

DSG classifiers

DSG channel list type/length value (TLV)

DSG client identifier (whether broadcast, CA System, application, or MAC-level)

DSG timer list

DSG upstream channel ID (UCID) list

Vendor-specific information field

Prerequisites for DSG 1.1

Cisco IOS release 12.3(13a)BC or a later 12.3 BC release are required.

Cisco DSG 1.1 is supported on the Cisco uBR10012 router with PRE1 or PRE2 performance routing engine modules.

Cisco DSG 1.1 is supported on the Cisco uBR10012 router with the following cable interface line cards and broadband processing engines (BPEs):

Cisco uBR10-LCP2-MC16C/MC16E/MC16S Cable Interface Line Card


Note The Cisco uBR10-LCP2-MC16x (C, E, S) cable interface line cards are end of sale. For additional information, refer to END-OF-LIFE NOTICE, NO. 2600 at the following location:
http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_end-of-life_notice0900aecd80183921.html


Cisco uBR10-LCP2-MC28C Cable Interface Line Card

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Restrictions and Caveats for DSG 1.1

Cisco DSG 1.1 has the following restrictions:

Cisco DSG 1.1 does not support Service Flow Quality of Service (QoS), which is available at Layer 3.

Cisco DSG 1.1 does not support tunnel security, but strictly access control lists (ACLs).

Cisco DSG 1.1 does not support subinterfaces.

Cisco DSG 1.1 does not support HCCP N+1 interoperability.

Cisco DSG 1.1 does not support SNMP MIBS for A-DSG.

Additional Information about DSG 1.1

Advanced-mode DOCSIS Set-Top Gateway Issue 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_docsis_gw12_ps2209_TSD_Products_Configuration_Guide_Chapter.html

DOCSIS Set-Top Gateway (DSG) for the Cisco CMTS

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00802065c8.html

Cisco DOCSIS Set-top Gateway White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_white_paper09186a00801b3f0f.shtml

CableLabs DOCSIS Set-top Gateway (DSG) Interface Specification SP-DSG-I03-041124

Advanced Spectrum Management Support on the Cisco uBR10012 CMTS

Cisco IOS release 12.3(13a)BC introduces Advanced Spectrum Management for the Cisco uBR10012 router, with the following enhancements:

Supports additional software functionality for the Cisco uBR10-LCP2-MC16C/E/S cable interface line card and the Cisco MC5x20S/U broadband processing engine.


Note The Cisco uBR10-LCP2-MC16x (C, E, S) cable interface line cards are end of sale. For additional information, refer to END-OF-LIFE NOTICE, NO. 2600 at the following location:
http://www.cisco.com/en/US/prod/collateral/video/ps8806/ps5684/ps2209/prod_end-of-life_notice0900aecd80183921.html


Supports spectrum analyzer functionality.

Supports proactive channel management and hopping decisions, so as to avoid the negative impact of ingress noise, and to maintain uninterrupted subscriber service.

Offers flexible configuration choices, allowing MSOs to determine the priority of the actions to be taken when ingress noise on the upstream channel exceeds the allowable thresholds. The configurable actions are frequency hopping, switching the modulation profile, and reducing the channel width.

Performs Cisco Network Registrar (CNR) calculations using DSP algorithms in real-time on a per-interface and a per-modem basis.

Intelligently determines when to modify the frequency, channel width, or modulation profile, based on CNR calculations in the active channel, the number of missed station maintenance polls, and the number of correctable or non-correctable Forward Error Correction (FEC) errors. Previously, channel hopping occurred when the number of missed station maintenance polls exceeded a user-defined threshold or the SNR reported by the Broadcom chip exceeded the DOCSIS thresholds.

Enhances the Dynamic Upstream Modulation feature for the Cisco uBR-MC16S line card. This feature supports dynamic modulation using two upstream profiles. The primary profile (typically using 16-QAM or a mixed modulation profile) remains in effect at low noise conditions, but if upstream conditions worsen, the cable modems switch to the secondary profile (typically using QPSK modulation) to avoid going offline. When the noise conditions improve, the modems are moved back to the primary profile.

Commands for Enhanced Spectrum Management

A variety of commands for enhanced spectrum management now provide new options.

cable upstream n threshold cnr-profile1 threshold1-in-dB cnr-profile2 threshold2-in-dB corr-fec fec-corrected uncorr-fec fec-uncorrected

cable upstream n upstream threshold snr-profiles threshold1-in-dB threshold2-in-dB

cable upstream n threshold corr-fec corrfec-threshold

cable upstream n threshold uncorr-fec uncorrfec-threshold

show cable hop n upstream history

show cable hop n upstream threshold


Note For additional information and examples, see "Configuring Proactive Channel Management" and "Verifying the Spectrum Management Configuration" in Spectrum Management for the Cisco CMTS, at the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html


For additional information about spectrum management and advanced spectrum management on the Cisco CMTS, refer to the following documents on Cisco.com:

Spectrum Management and Advanced Spectrum Management for the Cisco CMTS

 http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html

Advanced Spectrum Management Feature for the Cisco uBR-MC16S Cable Interface Line Card

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_spctrm_mgt.html

Backup Path Testing for the Cisco RF Switch

Cisco IOS Release 12.3(13a)BC introduces the show hccp channel switch Cisco IOS command, wherein the Cisco RF Switch communicates with each module in the chassis to provide information as programmed in the RF Switch module bitmap. Cisco IOS Release 12.3(13a)BC performs polling every 10 seconds in response to this command, and reports RF Switch information as stored in cache. In normal operation, the switch requires from two to five seconds for SNMP response.

If SNMP errors are detected in response to this command, the switch may require a significantly longer timeout period. Cisco IOS Release 12.3(13a)BC introduces a keyboard break sequence to disrupt this timeout in such circumstances.

To introduce a break for the show hccp channel switch command, use the Ctrl-Shift-6-x break sequence—hold Ctrl-Shift keys, then press 6 then x.

After the break sequence, use the show hccp g m channel command to examine each individual HCCP member of a group, as required.

For additional information about HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy on the Cisco CMTS" chapter in the Cisco Cable Modem Termination System Feature Guide:

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html#wp1043160

Cisco IOS CMTS Cable Command Reference

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

Cable Monitor Support for Cisco MC5x20U-D and Cisco MC28U Broadband Processing Engines

Cisco IOS Release 12.3(13a)BC introduces support for the Cable Monitor feature for the Cisco MC5x20U-D broadband processing engine (BPE) and the Cisco MC28U cable interface line card. These field replaceable units (FRUs) apply to the Cisco uBR10012 router, and the latter to the Cisco uBR7246VXR router. This feature enables intercept and monitoring capabilities for DOCSIS-compliant frames.


Note The cable monitor feature does not support Access Control Lists (ACLs) for intelligent cable interface line cards such as the Cisco MC28U or Cisco MC16U in the Cisco uBR7246VXR router, or any intelligent cable interface line card in the Cisco uBR10012 router.



Note When using ACLs with cable monitor and the Cisco uBR10012 router, combine multiple ACLs into one ACL, and then configure cable monitor with the consolidated ACL.


The Cable Monitor and Intercept features for Cisco Cable Modem Termination System (CMTS) routers provide a software solution for monitoring and intercepting traffic coming from a cable network. This feature also gives service providers Lawful Intercept capabilities, such as those required by the Communications Assistance for Law Enforcement Act (CALEA).

The following example configures cable monitor for a specific interface and the associated MAC addresses:

Router(config)# interface Cable3/0
Router(config-if)# cable monitor interface GigabitEthernet0/1
mac-address 000e.5cc8.fa5f
packet-type data ethernet
Router(config-if)# 
mac-address 000e.5cac.59f8
packet-type data ethernet

To display cable monitor configuration and status information, use the show interfaces command in Privileged EXEC mode:

Router# show interfaces cable 3/0 monitor
US/ Time Outbound  Flow     Flow Type      Flow  Packet MAC   MAC	Encap
DS  Stmp Interface Type     Identifier     Extn. Type   Extn. Type	Type
all  no    Gi0/1   mac-addr 000e.5cc8.fa5f yes   data   no     -	ethernet
all  no    Gi0/1   mac-addr 000e.5cac.59f8 yes   data   no     -	ethernet

To display and monitor traffic statistics and counters over time, use the show cable modem counters and the show interfaces commands in Privileged EXEC mode, as illustrated:

Router# show interfaces cable 3/0 monitor
US/ Time Outbound  Flow     Flow Type      Flow  Packet MAC   MAC	Encap
DS  Stmp Interface Type     Identifier     Extn. Type   Extn. Type	Type
all  no    Gi0/1   mac-addr 000e.5cc8.fa5f yes   data   no     -	ethernet
all  no    Gi0/1   mac-addr 000e.5cac.59f8 yes   data   no     -	ethernet
Router# show cable modem 000e.5cac.59f8  counters
MAC Address    US Packets   US Bytes   DS Packets   DS Bytes
000e.5cac.59f8 7537986      3828867645 7199188      3711248288
Router# show interfaces GigabitEthernet 0/1
GigabitEthernet0/1 is up, line protocol is up 
  Hardware is BCM1250 Internal MAC, address is 000e.d6bd.2001 (bia 000e.d6bd.2001)
  Description: ***Sonde_analyse_trafic***
  Internet address is 82.216.52.1/30
  MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Full-duplex, 100Mb/s, media type is RJ45
  output flow-control is XON, input flow-control is XON
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input 00:00:08, output 00:00:01, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/5/0 (size/max/drops/flushes); Total output drops:361
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     1094862 packets input, 70425672 bytes, 0 no buffer
     Received 0 broadcasts, 5 runts, 0 giants, 0 throttles
     0 input errors, 10 CRC, 0 frame, 0 overrun, 0 ignored
     0 watchdog, 37 multicast, 0 pause input
     0 input packets with dribble condition detected
     188665 packets output, 29355747 bytes, 0 underruns       <<< 188665 packets
     0 output errors, 0 collisions, 6 interface resets
     0 babbles, 0 late collision, 0 deferred
     12 lost carrier, 0 no carrier, 0 pause output
     0 output buffer failures, 0 output buffers swapped out

When cable monitor is active, counters for the above commands should increase over time. For additional information about cable monitoring on the Cisco CMTS, refer to these documents on Cisco.com:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Cisco IOS CMTS Cable Command Reference

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

COPS TCP Support for the Cisco Cable Modem Termination System

Cisco IOS Release 12.3(13a)BC introduces optimized support for the Common Open Policy Service (COPS) feature for the Cisco uBR10012 router. This feature supports two new configuration commands for enabling and setting COPS processes. The COPS feature in Cisco 12.3(13a)BC enables the following COPS functions:

COPS DSCP Marking for the Cisco CMTS

This feature allows you to change the DSCP marking for COPS messages that are transmitted or received by the Cisco router. Differentiated Services Code Point (DSCP) values are used in Quality of Service (QoS) configurations on a Cisco router. DSCP summarizes the relationship between DSCP and IP precedence.

Cisco IOS Release 12.3(13a)BC supports this function with the cops ip dscp command in global configuration mode.

COPS TCP Window Size for the Cisco CMTS

This feature allows you to override the default TCP receive window size that is used by COPS processes. This setting can be used to prevent the COPS server from sending too much data at one time.

Cisco IOS Release 12.3(13a)BC supports this function with the cops tcp window-size command in global configuration mode.


Note These two commands affect all TCP connections with all COPS servers.


cops ip dscp

To specify the marking for COPS messages that are transmitted by the Cisco router, use the cops ip dscp command in global configuration mode. To remove this configuration, use the no form of this command.

cops ip dscp x

no cops ip dscp

Syntax Description

x

This value specifies the markings with which COPS messages are transmitted. The following values are supported:

0-63—DSCP value ranging from 0-63.

af11—Use AF11 dscp (001010)

af12—Use AF12 dscp (001100)

af13—Use AF13 dscp (001110)

af21—Use AF21 dscp (010010)

af22—Use AF22 dscp (010100)

af23—Use AF23 dscp (010110)

af31—Use AF31 dscp (011010)

af32—Use AF32 dscp (011100)

af33—Use AF33 dscp (011110)

af41—Use AF41 dscp (100010)

af42—Use AF42 dscp (100100)

af43—Use AF43 dscp (100110)

cs1—Use CS1 dscp (001000) [precedence 1]

cs2—Use CS2 dscp (010000) [precedence 2]

cs3—Use CS3 dscp (011000) [precedence 3]

cs4—Use CS4 dscp (100000) [precedence 4]

cs5—Use CS5 dscp (101000) [precedence 5]

cs6—Use CS6 dscp (110000) [precedence 6]

cs7—Use CS7 dscp (111000) [precedence 7]

default—Use default dscp (000000)

ef—Use EF dscp (101110)


Defaults

For messages transmitted by the Cisco router, the default DSCP value is 0.

For incoming connections to the Cisco router, by default, the COPS engine takes the DSCP value used by the COPS server that initiates the TCP connection.

Usage Guidelines

The cops ip dscp command allows the Cisco router to re-mark the COPS packets for either incoming or outbound connections.

This command affects all TCP connections with all COPS servers.

This command does not affect existing connections to COPS servers. Once you issue this command, this function is supported only for new connections after that point in time.

Examples

The following example illustrates the cops ip dscp command with supported command variations:

Router(config)# cops ip dscp ?
 <0-63>   DSCP value 
 af11     Use AF11 dscp (001010) 
 af12     Use AF12 dscp (001100) 
 af13     Use AF13 dscp (001110) 
 af21     Use AF21 dscp (010010) 
 af22     Use AF22 dscp (010100) 
 af23     Use AF23 dscp (010110) 
 af31     Use AF31 dscp (011010) 
 af32     Use AF32 dscp (011100) 
 af33     Use AF33 dscp (011110) 
 af41     Use AF41 dscp (100010) 
 af42     Use AF42 dscp (100100) 
 af43     Use AF43 dscp (100110) 
 cs1      Use CS1  dscp (001000) [precedence 1] 
 cs2      Use CS2  dscp (010000) [precedence 2] 
 cs3      Use CS3  dscp (011000) [precedence 3] 
 cs4      Use CS4  dscp (100000) [precedence 4] 
 cs5      Use CS5  dscp (101000) [precedence 5] 
 cs6      Use CS6  dscp (110000) [precedence 6] 
 cs7      Use CS7  dscp (111000) [precedence 7] 
 default  Use default dscp (000000) 
 ef       Use EF   dscp (101110) 

Additional COPS Information

Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.

For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Configuring COPS for RSVP

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll

COPS for RSVP

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll

cops tcp window-size

To override the default TCP receive window size on the Cisco CMTS, use the cops tcp window-size command in global configuration mode. This setting allows you to prevent the COPS server from sending too much data at one time. To return the TCP window size to a default setting of 4K, use the no form of this command.

cops tcp window-size bytes

no cops tcp window-size

Syntax Description

bytes

This is the TCP window size setting in bytes. This value can range from 516 to 65535 bytes.


Defaults

The default COPS TCP window size is 4000 bytes.

Usage Guidelines

This command does not affect existing connections to COPS servers. Once you issue this command, this function is supported only for new connections after that point in time.

Examples

The following example configures the TCP window size to be 64000 bytes.

Router(config)# cops tcp window-size 64000 

The following example illustrates online help for this command:

Router(config)# cops tcp window-size ? 
 <516-65535>  Size in bytes 

Additional COPS Information

Cisco 12.3(13a)BC also supports Access Control Lists (ACLs) for use with COPS. Refer to the "Access Control List Support for COPS Intercept" section.

For additional information about configuring COPS on the Cisco CMTS, refer to the following documents on Cisco.com:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Configuring COPS for RSVP

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll

COPS for RSVP

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.htmll

DHCP MAC Address Exclusion List for cable-source verify dhcp Command

Cisco IOS Release 12.3(13a)BC introduces the ability to exclude trusted MAC addresses from standard DHCP source verification checks, as supported in previous Cisco IOS releases for the Cisco CMTS. This feature enables packets from trusted MAC addresses to pass when otherwise packets would be rejected with standard DHCP source verification. This feature overrides the cable source-verify command on the Cisco CMTS for the specified MAC address, yet maintains overall support for standard and enabled DHCP source verification processes. This feature is supported on Performance Routing Engine 1 (PRE1) and PRE2 modules on the Cisco uBR10012 router chassis.

To enable packets from trusted source MAC addresses in DHCP, use the cable trust command in global configuration mode. To remove a trusted MAC address from the MAC exclusion list, use the no form of this command. Removing a MAC address from the exclusion list subjects all packets from that source to standard DHCP source verification.

cable trust mac-address

no cable trust mac-address

Syntax Description

mac-address

The MAC address of a trusted DHCP source, and from which packets will not be subject to standard DHCP source verification.


Usage Guidelines

This command and capability are only supported in circumstances in which the Cable Source Verify feature is first enabled on the Cisco CMTS.

When this feature is enabled in addition to cable source verify, a packet's source must belong to the MAC Exclude list on the Cisco CMTS. If the packet succeeds this exclusionary check, then the source IP address is verified against Address Resolution Protocol (ARP) tables as per normal and previously supported source verification checks. The service ID (SID) and the source IP address of the packet must match those in the ARP host database on the Cisco CMTS. If the packet check succeeds, the packet is allowed to pass. Rejected packets are discarded in either of these two checks.

Any trusted source MAC address in the optional exclusion list may be removed at any time. Removal of a MAC address returns previously trusted packets to non-trusted status, and subjects all packets to standard source verification checks on the Cisco CMTS.

For additional information about the enhanced Cable Source Verify DHCP feature, and general guidelines for its use, refer to the following documents on Cisco.com:

IP Address Verification for the Cisco uBR7200 Series Cable Router

http://www.cisco.com/en/US/docs/ios/12_0t/12_0t7/feature/guide/sourcver.html

Filtering Cable DHCP Lease Queries

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblsrcvy.html

Cisco IOS CMTS Cable Command Reference

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

CABLE SECURITY, Cable Source-Verify and IP Address Security, White Paper

http://www.cisco.com/en/US/tech/tk86/tk803/technologies_tech_note09186a00800a7828.shtml

DOCSIS 1.0 Concatenation Override

Cisco IOS release 12.3(13a)BC introduces support for the DOCSIS 1.0 concatenation override feature on the Cisco uBR10012 router. This feature provides the ability to disable concatenation on DOCSIS 1.0 cable modems, even in circumstances where concatenation is otherwise supported for the upstream channel.

DOCSIS 1.0 concatenation allows the cable modem to make a single-time slice request for multiple packets, and to send all packets in a single large burst on the upstream. Concatenation was introduced in the upstream receive driver in the previous Cisco IOS releases that supported DOCSIS 1.0 +. Per-SID counters were later added in Cisco IOS release 12.1(4)CX for debugging concatenation activity.

In some circumstances, overriding concatenation on DOCSIS 1.0 cable modems may be preferable, and Cisco IOS release 12.3(13a)BC supports either option.


Note Even when DOCSIS 1.0 concatenation is disabled with this feature, concatenation remains enabled for cable modems that are compliant with DOCSIS 1.1 or DOCSIS 2.0.


To enable DOCSIS 1.0 concatenation override with Cisco IOS release 12.3(13a)BC and later releases, use the new docsis10 keyword with the previously supported cable upstream n concatenation command in privileged EXEC mode:

cable upstream n concatenation docsis10

Syntax Description

n

Specifies the upstream port number. Valid values start with 0 for the first upstream port on the cable interface line card.


Examples

The following example illustrates DOCSIS 1.0 concatenation override on the Cisco uBR10012 router:

Router# no cable upstream 0 concatenation docsis10

In this example, DOCSIS 1.0 cable modems are updated with REG-RSP so that they are not permitted to use concatenation.

For additional information about this command, refer to the Cisco IOS CMTS Cable Command Reference on Cisco.com:

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

DOCSIS BPI+ Multiple Root Certificate Support

Cisco IOS Release 12.3(13a)BC introduces support for multiple DOCSIS root certificates with Baseline Privacy Interface Plus (BPI+) on the Cisco CMTS. This feature enables the Cisco CMTS to support either North American or European cable modems, with the following guidelines for implementation:

In circumstances in which it is necessary to change from North American root certificates to European root certificates, or vice versa, it is necessary to over write the existing root certificate on the Cisco CMTS, and to reload the Cisco CMTS with the reload or restart command.

The Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE) supports both North American and European root certificates at the same time, and simultaneous root certificate support is a requirement in this case.

Dynamic SID/VRF Mapping Support

Cisco IOS release 12.3(13a)BC introduces support for dynamic service ID (SID) and VRF mapping on the Cisco CMTS, to support Voice over IP (VoIP) with MPLS. Formerly, the MPLS SID mapping feature only applied to provisioned service flows. This feature enables the mapping of all PacketCable DQoS service flows to one particular VRF.

For additional information, refer to the following:

Mapping Service Flows to MPLS VPN on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/sfidmpls.html

Enhanced Rate Bandwidth Allocation (ERBA) Support for DOCSIS 1.0 Cable Modems

Cisco IOS release 12.3(13a)BC introduces Enhanced Rate Bandwidth Allocation (ERBA) support for DOCSIS 1.0 cable modems and the Cisco uBR10012 router. ERBA allows DOCSIS1.0 modems to burst their temporary transmission rate up to the full line rate for short durations of time. This capability provides higher bandwidth for instantaneous bandwidth requests, such as those in Internet downloads, without having to make changes to existing service levels in the QoS Profile.

This feature enables MSOs to set the DOCSIS 1.0 cable modems burst transmissions, with mapping to overriding DOCSIS 1.1 QoS profile parameters on the Cisco CMTS. DOCSIS 1.0 cable modems require DOCSIS 1.0 parameters when registering to a matching QoS profile. This feature enables maximum downstream line rates, and the ERBA setting applies to all cable modems that register to the corresponding QoS profile.


Note QoS definitions must previously exist on the Cisco CMTS headend to support this feature.


ERBA for DOCSIS 1.0 cable modems is supported with these new or enhanced commands or keywords in Cisco IOS release 12.3(13a)BC:

cable qos pro max-ds-burst burst-size

show cable qos profile n [verbose]

To define ERBA on the downstream for DOCSIS 1.0 cable modems, use the cable qos promax-ds-burst command in global configuration mode. To remove this ERBA setting from the QoS profile, use the no form of this command.

cable qos pro max-ds-burst burst-size

no cable qos pro max-ds-burst

Syntax Description

burst-size

The QoS profile's downstream burst size in bytes.


To display ERBA settings as applied to DOCSIS 1.0 cable modems and QoS profiles on the Cisco CMTS, use the show cable qos profile command in Privileged EXEC mode.

The following example of the cable qos profile command in global configuration mode illustrates changes to the cable qos profile command. Fields relating to the ERBA feature are shown in bold for illustration:

Router(config)# cable qos pro 10 ?
  grant-interval       Grant interval
  grant-size           Grant size
  guaranteed-upstream  Guaranteed Upstream
  max-burst            Max Upstream Tx Burst
  max-ds-burst        Max Downstream Tx burst (cisco specific) 
  max-downstream       Max Downstream
  max-upstream         Max Upstream
  name                 QoS Profile name string (cisco specific) 
  priority             Priority
  privacy              Cable Baseline Privacy Enable
tos-overwrite        Overwrite TOS byte by setting mask bits to value 

The following example of the show cable qos profile command illustrates that the maximum downstream burst has been defined, and is a management-created QoS profile:

Router# show cable qos pro
ID  Prio Max       Guarantee Max        Max   TOS  TOS   Create  B     IP prec.
         upstream  upstream  downstream tx    mask value by      priv  rate
         bandwidth bandwidth bandwidth  burst                    enab  enab
1   0    0         0         0          0     0xFF 0x0   cmts(r) no    no
2   0    64000     0         1000000    0     0xFF 0x0   cmts(r) no    no
3   7    31200     31200     0          0     0xFF 0x0   cmts    yes   no
4   7    87200     87200     0          0     0xFF 0x0   cmts    yes   no
6   1    90000     0         90000      1522  0xFF 0x0   mgmt    yes   no
10  1    90000     0         90000      1522  0x1  0xA0  mgmt    no    no
50  0    0         0         96000      0     0xFF 0x0   mgmt    no    no
51  0    0         0         97000      0     0xFF 0x0   mgmt    no    no

The following example illustrates the maximum downstream burst size in sample QoS profile 10 with the show cable qos prof verbose command in privileged EXEC mode:

Router# show cable qos pro 10 ver
Profile Index                           10
Name
Upstream Traffic Priority               1
Upstream Maximum Rate (bps)             90000
Upstream Guaranteed Rate (bps)          0
Unsolicited Grant Size (bytes)          0
Unsolicited Grant Interval (usecs)      0
Upstream Maximum Transmit Burst (bytes) 1522
Downstreamam Maximum Transmit Burst (bytes) 100000
IP Type of Service Overwrite Mask       0x1
IP Type of Service Overwrite Value      0xA0
Downstream Maximum Rate (bps)           90000
Created By                              mgmt
Baseline Privacy Enabled                no

Usage Guidelines

If a cable modem registers with a QoS profile that matches one of the existing QoS profiles on the Cisco CMTS, then the maximum downstream burst size, as defined for that profile, is used instead of the default DOCSIS QoS profile of 1522.

For example, a DOCSIS 1.0 configuration that matches QoS profile 10 in the previous examples would be as follows:

03 (Net Access Control)         = 1
04 (Class of Service Encodings Block)
   S01 (Class ID)               = 1
   S02 (Maximum DS rate)        = 90000
   S03 (Maximum US rate)        = 90000
   S06 (US burst)               = 1522
   S04 (US Channel Priority)    = 1
   S07 (Privacy Enable)         = 0

The maximum downstream burst size (as well as the ToS overwrite values) are not explicitly defined in the QoS configuration file because they are not defined in DOCSIS. However, because all other parameters are a perfect match to profile 10 in this example, then any cable modem that registers with these QoS parameters has a maximum downstream burst of 100000 bytes applied to it.

For further illustration, consider a scenario in which packets are set in lengths of 1000 bytes at 100 packets per second (pps). Therefore, the total rate is a multiplied total of 1000, 100, and 8, or 800kbps.

To change these settings, two or more traffic profiles are defined, with differing downstream QoS settings as desired. Table 5 provides two examples of such QoS profiles for illustration:

Table 5 Sample QoS Profiles with Differing ERBA (Maximum Downstream) Settings

QoS Profile Setting
QoS Profile 101
QoS Profile 102

Maximum Downstream Transmit Burst (bytes)

max-burst 4000

max-burst 4000

Maximum Downstream Burst (bps)

max-ds-burst 20000

max-ds-burst 5000

Maximum Downstream Bandwidth

max-downstream 100

max-downstream 100


In this scenario, both QoS profiles are identical except for the max-ds-burst size, which is set to 5000 in QoS profile 101 and 5000 in QoS profile 102.

Optimal Settings for ERBA

DOCSIS allows the setting different token bucket parameters for each service flow, including the token bucket burst size. When burst sizes are closer to 0, QoS is enforced in a stricter manner, allowing a more predictable sharing of network resources, and as a result easier network planning.

When burst sizes are larger, individual flows can transmit information faster (lower latency), although the latency variance can be larger as well.

For individual flows, a larger burst size is likely to be better. As long as the system is not congested, a large burst size reduces the chances of two flows transmitting at the same time, because each burst is likely to take less time to transmit. However, as channel bandwidth consumption increases, it is probably that large burst traffic would exceed the thresholds of buffer depths, and latency is longer than with well shaped traffic.

For additional information about the cable qos profile command and configuring QoS profiles, refer to the following documents on Cisco.com:

Cisco Broadband Cable Command Reference Guide

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

Configuring DOCSIS 1.1 on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

High Availability Features

Cisco IOS release 12.3(13a)BC introduces several High Availability features on the Cisco uBR10012 router:

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Global N+1 Redundancy

PacketCable Emergency 911 Cable Interface Line Card Prioritization

PacketCable Emergency 911 Services Listing and History

Shutdown and No Shutdown Enhancement for Cable Interfaces

Automatic Revert Feature for HCCP N+1 Redundancy Switchover Events

Cisco IOS release 12.3(13a)BC introduces the Auto-Revert feature for the Cisco uBR10012 router, to further enhance HCCP N+1 Redundancy on the Cisco CMTS. With this feature, when a switchover event is performed in manual fashion, from the HCCP Protect line card, and the Protect line card has a hardware fault, HCCP automatically reverts back to the HCCP Working line card. This is a very helpful feature, in that periodic switchovers can be performed for regular maintenance or testing purposes, yet subscriber service is not interrupted should such switchovers reveal unexpected problems with HCCP Protect line cards.

For further information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco Broadband Cable Command Reference Guide

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

Global N+1 Redundancy

Cisco IOS release 12.3(13a)BC introduces the Global N+1 Linecard Redundancy (or, HCCP Rapid Configuration) feature on the Cisco uBR10012 router to streamline the configuration of N+1 line card redundancy. The feature implements a simpler command-line interface (CLI) to establish the Working and Protect line card relationships, which no longer requires configuration of the legacy hccp interface configuration commands.

For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco Broadband Cable Command Reference Guide

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

Shutdown and No Shutdown Enhancement for Cable Interfaces

Cisco IOS release 12.3(13a)BC introduces a new behavior with the [no] shutdown interface configuration command. In HCCP N+1 Redundancy schemes, an interface that is shut down with the shutdown command does not create an HCCP Switchover event for the associated Working or Protect interface. Instead, cable modems go offline and return online when the no shutdown command is issued.

For additional information about this feature and HCCP N+1 Redundancy on the Cisco CMTS, refer to these documents on Cisco.com:

"N+1 Redundancy for the Cisco Cable Modem Termination System," Cisco CMTS Feature Guide

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/uFGnpls1.html

Cisco Broadband Cable Command Reference Guide

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

MIBs Enhancements

Subinterface support in ifTable Object

Cisco IOS Release 12.3(13a)BC introduces enhanced SNMP MIB support in which subinterface information is included in the ifTable for the associated device. This enhanced ifTable provides new subinterface information in addition to the main interface information previously supported in earlier Cisco IOS releases.

This subinterface MIB information is only supported in the ifTable if an IP address is assigned to the subinterface and the main interface under which it resides. This subinterface MIB information is not supported when the IP address of a main or subinterface is removed with the no interface command in interface configuration mode.

For additional information about the ifTable and SNMP MIBs for the Cisco CMTS, refer to the following document on Cisco.com:

Cisco CMTS MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Multicast QoS Support on the Cisco uBR10012 CMTS

Cisco IOS Release 12.3(13a)BC introduces support for Multicast downstream QoS feature. This feature provides the ability to assign static mapping to a multicast group. The Multicast downstream QoS feature uses the existing infrastructure (DOCSIS 1.1 service flow) to assign a multicast service identifier (SID) to a multicast group used in the Baseline Privacy Interface (BPI) encryption feature.

When disabled, the Multicast downstream QoS feature does not impact any other features. The multicast packets to downstream cable interfaces are sent to the default service flow.

This feature is being implemented in response to CSCeg22989 which states, multicast traffic is not classified to any service flow, and therefore ends up queued on the default service flow. The default service flow has no specific QoS guarantees assigned to it. So once the interface approaches congestion level, multicast packets may be dropped.

Restrictions

The multicast definitions are per-bundle, not per interface. This means that all downstreams in a bundle share the same multicast to QoS association. The downstreams will create their own service flows according to the same QoS parameters.

Multicast to QoS definitions can not be assigned per sub-interface

Multicast SIDs are not deleted when a group becomes idle (no response to IGMP reports).

The QoS assignments for a multicast group can not be changed dynamically. If the user wishes to change them then a new "cable match" command must be configured.

Multicast QoS is not supported with Multicast Echo on the Cisco uBR10012 router. Multicast; however, MultiCast Echo is supported on the Cisco uBR10012 for packets that go through multicast forwarding (arrive to the router on a WAN interface).

New and Changed Commands

cable match address

Use the existing "cable match" command to assign QoS to a multicast group, with BPI either enabled or disabled.

Router# cable match address <number>|<name> [service-class <name> [bpi-enable]]
Router# no cable match address [<number>|<name> [service-class <name> [bpi-enable]]] 

debug cable mcast-qos

Use this command to turn on CMTS Multicast Qos debugging.

Router# debug cable mcast-qos

Online Offline Diagnostics (OOD) Support for the Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.3(13a)BC introduces support for Online Offline Diagnostics (OOD) in the field for the Cisco uBR1002 router, including support in a high availability environment with HCCP N+1 Redundancy. The Online Offline Diagnostics (OOD) feature introduces a Field Diagnostic tool that provides a method of testing and verifying line card hardware problems.

This feature is supported on the following field replaceable units (FRUs) of the Cisco uBR10012 router:

Cisco uBR10012 PRE1 and PRE2 Performance Routing Engine (PRE1 and PRE2) modules

Cisco uBR10K-MC520S/U broadband processing engine (BPE)

Cisco uBR10012 OC-48 DPT/POS WAN interface module

To view a list of hardware on the Cisco uBR10012 router that is supported by Field Diagnostics, refer to the following document:

Online Offline Diagnostics - Field Diagnostics on Cisco uBR10012 Router User's Guide

http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/troubleshooting/fdub10k.html

If you would like to perform a hardware diagnostic test on a line card in your Cisco uBR10000 series router, an OOD Field Diagnostic image can be downloaded free of charge from Cisco Systems and used to test whether the line card problems are indeed due to faulty hardware. The test results verify whether or not the hardware is faulty.

Optional Upstream Scheduler Modes

With this feature, the user is able to select either Unsolicited Grant Services (UGS) or Real Time Polling Service (rtPS) scheduling types, as well as packet-based or TDM-based scheduling. Low latency queueing (LLQ) emulates a packet-mode-like operation over the Time Division Multiplex (TDM) infrastructure of DOCSIS. As such, the feature provides the typical tradeoff between packets and TDM: with LLQ, the user has more flexibility in defining service parameters for UGS or rtPS, but with no guarantee (other than statistical distribution) regarding parameters such as delay and jitter.

Restrictions

To ensure proper operation, Call Admission Control (CAC) must be enabled. When the Low Latency Queueing (LLQ) option is enabled, it is possible for the upstream path to be filled with so many calls that it becomes unusable, making voice quality unacceptable. CAC must be used to limit the number of calls to ensure acceptable voice quality, as well as to ensure traffic other than voice traffic.

Even if CAC is not enabled, the default (DOCSIS) scheduling mode blocks traffic after a certain number of calls.

Unsolicited Grant Services with Activity Detection (UGS-AD) and Non Real Time Polling Service (nrtPS) are not supported.

New and Changed Commands

cable upstream n scheduling type

Use this new command to turn the various scheduling modes on or off, where n specifies the upstream port.

Router(config-if)# [no] cable upstream n scheduling type [ugs | rtps] mode [llq | docsis]

For additional information about scheduler enhancements on the Cisco CMTS, refer to the following:

Cisco CMTS Feature Guide — Configuring Upstream Scheduler Modes on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/cmtsfg.html

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

PacketCable Emergency 911 Cable Interface Line Card Prioritization

Cisco IOS Release 12.3(13a)BC introduces PacketCable Emergency 911 cable interface line cad prioritization on the Cisco CMTS. This feature enables cable interface line cards that are supporting an Emergency 911 call to be given automatic priority over cable interface line cards supporting non-emergency voice calls, even in the case of HCCP switchover events. In such cases, Protect HCCP line card interfaces automatically prioritize service to Emergency 911 voice calls, should Working HCCP cable interface line cards be disrupted. This feature is enabled by default in Cisco IOS release 12.3(13a)BC, and may not be disabled with manual configuration.


Note Emergency 911 cable interface line card prioritization applies only to PacketCable voice calls.


During HCCP switchover events, cable modems recover in the following sequence in Cisco IOS release 12.3(13a)BC:

1. Cable modems supporting Emergency 911 voice traffic

2. Cable modems supporting non-emergency voice traffic

3. Cable modems that are nearing a T4 timeout event, in which service would be disrupted

4. Remaining cable modems

To view information about Emergency 911 voice events and cable interface line card prioritization on the Cisco CMTS, use the show hccp <int x> <int y> modem and show hccp event-history commands in privileged EXEC mode.

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml

PacketCable Emergency 911 Services Listing and History

Cisco IOS release 12.3(13a)BC introduces enhanced informational support for PacketCable Emergency 911 calls on the Cisco CMTS, to include the following information and related history:

active Emergency 911 calls

recent Emergency 911 calls

regular voice calls

voice calls made after recent Emergency 911 calls

This feature is enabled and supported with the following new Cisco IOS command-line interface (CLI) configuration and show commands:

cable high-priority-call-window <minutes>

show cable calls [ interface cx/y | slot z ]

show cable calls [interface | slot] for the Cisco uBR 7200 Series

show cable calls [interface | slot/subslot] for the Cisco uBR10012 router

show cable modem [ip_addr | mac_addr | interface] calls

To set the call window (in minutes) during which the Cisco CMTS maintains records of Emergency 911 calls, use the cable high-priority-call-window command in global configuration mode. To remove the call window configuration from the Cisco CMTS, use the no form of this command:

cable high-priority-call-window <minutes>

no cable high-priority-call-window

The following command example configures the call window on the Cisco uBR10012 router to be 1 minute in length:

Router(config)# cable high-priority-call-window 1

To observe Emergency 911 calls made within the configured window, use the show cable calls command in privileged EXEC mode:

show cable calls

The following command example illustrates that one Emergency 911 call was made on the Cable8/1/1 interface on the Cisco uBR10012 router during the window set for high priority calls:

Router# show cable calls
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  1                 1               0                 0              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0 
Total       1                 1               0                 0 
 
   

The following command example illustrates the change on the Cisco uBR10012 router when this Emergency 911 calls ends:

Router# show cable calls
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 0               0                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0 
Total       0                 0               0                 1 

The following command example illustrates available information when making a voice call from the same MTA to another MTA on the same interface:

Router# show cable calls
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 2               1                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0 
Total       0                 2               1                 1 

The following command example illustrates available information when a voice call from the same MTA to another MTA on the same interface ends:

Router# show cable calls
Interface   ActiveHiPriCalls  ActiveAllCalls  PostHiPriCallCMs  RecentHiPriCMs
Cable5/0/0  0                 0               0                 0              
Cable5/0/1  0                 0               0                 0              
Cable5/1/0  0                 0               0                 0              
Cable5/1/1  0                 0               0                 0              
Cable5/1/2  0                 0               0                 0              
Cable5/1/3  0                 0               0                 0              
Cable5/1/4  0                 0               0                 0              
Cable6/0/0  0                 0               0                 0              
Cable6/0/1  0                 0               0                 0              
Cable7/0/0  0                 0               0                 0              
Cable7/0/1  0                 0               0                 0              
Cable8/1/0  0                 0               0                 0              
Cable8/1/1  0                 0               0                 1              
Cable8/1/2  0                 0               0                 0              
Cable8/1/3  0                 0               0                 0              
Cable8/1/4  0                 0               0                 0 
Total       0                 0               0                 1 

The following example illustrates the show cable modem calls command on the Cisco uBR10012 router over a period of time, with changing call status information:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:39

The following example illustrates that call information disappears when a call ends:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)

The following example illustrates a new Emergency 911 call on the Cisco CMTS:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    HV                  1:30

The following example illustrates a the end of the Emergency 911 call on the Cisco CMTS:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:3 

The following example illustrates a non-emergency voice call on the Cisco CMTS from the same MTA:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.ca36.f97d 10.10.155.25    C8/1/1/U0 5     V                    -
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    RV                  0:30

The following example illustrates a the end of the non-emergency voice call on the Cisco CMTS:

Router# show cable modem calls
Cable Modem Call Status Flags:
H: Active high priority calls
R: Recent high priority calls
V: Active voice calls (including high priority)
MAC Address    IP Address      I/F       Prim  CMCallStatus  LatestHiPriCall
                                         Sid                    (min:sec)
0000.cab7.7b04 10.10.155.38    C8/1/1/U0 18    R                   0:36

For additional informationabout PacketCable Emergency 911 calls on the Cisco CMTS, refer to the following documents on Cisco.com:

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml

PacketCable Multimedia for the Cisco CMTS

Cisco IOS Release 12.3(13a)BC introduces support for PacketCable Multimedia (PCMM) on the Cisco uBR10012 universal broadband router, and fully supports the CableLabs PacketCable Multimedia Specification, PKT-SP-MM-I02-040930.

http://www.cablelabs.com/packetcable/specifications/multimedia.html

As described by CableLabs, some key features of the PCMM service delivery framework include the following:

Simple, powerful access to DOCSIS 1.1 QoS mechanisms supporting both time and volume-based network resource authorizations

Abstract, event-based network resource auditing and management mechanisms

A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces

More specifically, Cisco IOS Release 12.3(13a)BC expands or changes several PacketCable functions in earlier Cisco IOS releases, including the following:

Additional COPS Decision Messages—PCMM supports additional COPS decision messages, such as the following. The new objects for messages, such as Gate-Set, Gate-Set-Ack and Gate-Info, include different traffic profile definitions, different gate object formats, with additional objects for gate state reporting and flow utilization.

Gate-Set

Gate-Set-Ack

Gate-Set-Err

Gate-Info

Gate-Info-Ack

Gate-Info-Err

Gate-Delete

Gate-Delete-Ack

Gate-Delete-Err

State-Report

Different COPS client and UDP port for COPS sessions—PCMM uses a different COPS client type than does basic PacketCable, and PCMM uses a different UDP port for its COPS sessions. This can help to distinguish between PacketCable and PCMM COPS sessions on the Cisco CMTS.

MultiMedia State Machine—PCMM supports a different MultiMedia state machine than does PacketCable. The following are machine state changes introduced in PCMM with Cisco IOS Release 12.3(13a)BC:

PCMM gates are all unidirectional. In PacketCable, each gate is associated with both an upstream and downstream service flow. Although unidirectional flows are allowed, a bidirectional phone connection only has one gate.

PCMM differs in that each gate is now unidirectional, and is associated with only one service flow. As a result, the gate info element structure in PCMM differs significantly from that of PacketCable. PCMM only needs to maintain one set of service flow information, rather than maintaining both upstream and downstream information as does PacketCable.

DOCSIS DSX service flow information is now maintained on the Cisco CMTS. With PacketCable, gates are authorized, reserved, or committed first on the Cisco CMTS with a specific gate ID, and then the Cisco CMTS initiates a DSX exchange using the reserved or committed gate ID in the message. With PacketCable, the cable modem must issue the DSX message and create the service flows. However, with PCMM, when a gate is reserved or committed, the DSX message is generated and sent immediately by the Cisco CMTS. Therefore, the Policy Server sends all of the service flow information necessary to setup the service flow to the Cisco CMTS instead of the cable modem. This causes a major change in the state machine that controls the gate allocation procedures.

New timer definitions and event actions are supported on PCMM. New timer definitions and timer event actions are supported for proper behavior of the net state machine. Some of the timers used with PacketCable have been eliminated, while the events associated with other times have changed for PCMM.

New state transitions that did not exist in PacketCable 1.x have been added to PCMM. Specifically, a gate can now be transitioned back from Committed to Authorized or Reserved state.

Cable interface line cards and broadband processing engines perform distributed DOCSIS functions. The Cisco MC28U cable interface line card on the Cisco uBR7200 series routers, and all the line cards on the Cisco uBR10012 router, are considered distributed, because the DOCSIS functionality is performed by the line card processor. The GCP signaling for PCMM and the gate state machine will executed on the NPE or RP processor. Because of the split in this functionality, IPC signaling resides between the gate state machine and the DOCSIS layer processing.

Event management—Event management messages have been modified to include information on the modified traffic profiles, and to match changes in the PCMM state machine. In addition, objects have been added to help support Gate usage and Gate commit time objects, used for usage limit based and time based gates.

For additional information about PacketCable and PacketCable Multimedia on the Cisco CMTS, refer to the following documents on Cisco.com:

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_pkcb.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml

"PacketCable is a CableLabs®-led initiative that is aimed at developing interoperable interface specifications for delivering advanced, real-time multimedia services over two-way cable plant. Built on top of the industry's highly successful cable modem infrastructure, PacketCable networks use Internet protocol (IP) technology to enable a wide range of multimedia services, such as IP telephony, multimedia conferencing, interactive gaming, and general multimedia applications." (PacketCable.com)

CableLabs® describes key features of the PacketCable Multimedia IP service delivery framework as follows:

Simple, powerful access to DOCSIS® 1.1 QoS mechanisms supporting both time and volume-based network resource authorizations

Abstract, event-based network resource auditing and management mechanisms

A robust security infrastructure that provides integrity and appropriate levels of protection across all interfaces

PacketCable™ is a registered trademark of CableLabs®. Additional information and specifications are available online at the following CableLabs websites:

PacketCable website

http://www.cablelabs.com/packetcable/

PacketCable Multimedia specifications

http://www.cablelabs.com/packetcable/specifications/multimedia.html

Service Independent Intercept (SII) Support

Cisco CMTS supports the Communications Assistance for Law Enforcement Act (CALEA) for voice and data. Cisco IOS Release 12.3(13a)BC introduces support for Service Independent Intercept (SII) on the Cisco uBR10012 CMTS. Cisco SII provides a more robust level of the lawful intercept (LI) options offered in the Packet Intercept feature. Cisco SII is the next level of support for judicially authorized electronic intercept, to include dial access, mobile wireless, tunneled traffic, and Resilient Transport Protocol (RTP) for voice and data traffic on the Cisco CMTS. SII on the Cisco CMTS includes these functions:

Packet intercept on specified or unspecified interfaces or ports

Packet intercept on virtual interface bundles

Corresponding SNMP MIB enhancements for each of these functions, as intercept requests are initiated by a mediation device (MD) using SNMPv3


Note At the time of publication, the Cisco IOS 12.3 BC release train does not support virtual private networks with the SII feature. The CISCO-TAP-MIB does not specify any particular VPN, so this MIB is not assigned to a particular instance of VPN routing/forwarding (VRF). For restrictions on this platform, see "Overview of CISCO-TAP-MIB" in Cable Monitor and Intercept Features for the Cisco CMTS. See Additional Information.



Note No new CLI commands are provided for this feature in Cisco IOS Release 12.3(13a)BC.


Cisco IOS Release 12.3(13a)BC enables full Multiple Service Operator (MSO) compliance with SII and LI regulations. Service providers worldwide are legally required to allow government agencies to conduct surveillance on the service provider's traditional telephony equipment. The objective of the SII feature is to enable service providers with New World networks that legally allow government agencies to conduct electronic network surveillance.

Lawful Intercept (LI) describes the process and judicial authority by which law enforcement agencies conduct electronic surveillance of circuit and packet-mode communications. LI is authorized by judicial or administrative order and implemented for either voice or data traffic on the Cisco CMTS. Table 6 lists the differences between packet intercept and SII features as implemented on the Cisco uBR10012.

Table 6 Differences Between Packet Intercept and SII Features on the Cisco uBR10012

Feature
Packet Intercept
Service Independent Intercept

Interface Type

Cable

Cable

IP Masks

255.255.255.255 or 0.0.0.0

255.255.255.255 or 0.0.0.0

L4 Ports

Any single port or 0-65535

Any single port or 0-65535

Protocol

UDP

Any

TOS/DSCP

Not supported

Supported


Additional Information

For additional information, refer to the following documents:

Configuring COPS for RSVP, Cisco IOS Versions 12.2 and 12.3

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cops.html

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

PacketCable and PacketCable Multimedia on the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Cisco PacketCable Primer White Paper

http://www.cisco.com/en/US/products/hw/cable/ps2209/products_white_paper09186a0080179138.shtml

Transparent LAN Service and Layer 2 Virtual Private Networks

Cisco IOS Release 12.3(13a)BC introduces the following changes or requirements for the TLS feature with Layer 2 VPNs:

When the TLS feature is used with Layer 2 VPNs, the participating cable modems must have the Baseline Privacy Interface security feature (BPI) enabled. Otherwise, the Cisco CMTS drops such Layer 2 traffic in the upstream or downstream.

Information about customer premises equipment (CPE) does not display in the output of the show cable modem command.

Refer to the following documents on Cisco.com for additional TLS information:

TLS for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/tls-cmts.html

TLS Over Cable - TAC Document #60027

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_configuration_example09186a008029160d.shtml

Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE

Cisco IOS Release 12.3(13a)BC introduces support for virtual interface bundling on the Cisco uBR10012 universal broadband router and the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE), and the Cisco uBR7246VXR router.

In prior Cisco IOS releases, cable interface bundling was limited to physical interfaces as master or slave interfaces, and show commands did not supply bundle information.

Virtual interface bundling removes the prior concepts of master and slave interfaces, and introduces these additional changes:

Virtual interface bundling uses bundle interface and bundle members instead of master and slave interfaces.

The virtual bundle interface is virtually defined, as with IP loopback addresses, for example.

Virtual interface bundling supports bundle information in multiple show ip interface commands.

Virtual interface bundling prevents loss of connectivity on physical interfaces should there be a failure, problematic online insertion and removal (OIR) of one line card in the bundle, or erroneous removal of configuration on the master interface.

Virtual interface bundling supports and governs the following Layer 3 settings for the bundle member interfaces:

IP address

IP helper-address

source-verify and lease-timer functions

cable dhcp-giaddr (The giaddr field is set to the IP address of the DHCP client.)

Protocol Independent Multicast (PIM)

Access control lists (ACLs)

Sub-interfaces

For additional configuration information, examples, and guidelines for virtual interface bundling, refer to the following documents on Cisco.com:

Cable Interface Bundling and Virtual Interface Bundling for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

Virtual Interfaces and Frequency Stacking Configuration on MC5x20S and MC28U Line Cards

http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml

Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_cbl_if_bundlg_ps2209_TSD_Products_Configuration_Guide_Chapter.html

New Hardware Features in Cisco IOS Release 12.3(9a)BC9

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC9.

New Software Features in Cisco IOS Release 12.3(9a)BC9

There are no new software features supported in Cisco IOS Release 12.3(9a)BC9.

New Hardware Features in Cisco IOS Release 12.3(9a)BC8

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC8.

New Software Features in Cisco IOS Release 12.3(9a)BC8

There are no new software features supported in Cisco IOS Release 12.3(9a)BC8.

New Hardware Features in Cisco IOS Release 12.3(9a)BC7

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC7.

New Software Features in Cisco IOS Release 12.3(9a)BC7

There are no new software features supported in Cisco IOS Release 12.3(9a)BC7.

New Hardware Features in Cisco IOS Release 12.3(9a)BC6

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC6.

New Software Features in Cisco IOS Release 12.3(9a)BC6

There are no new software features supported in Cisco IOS Release 12.3(9a)BC6.

New Hardware Features in Cisco IOS Release 12.3(9a)BC5

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC5.

New Software Features in Cisco IOS Release 12.3(9a)BC5

There are no new software features supported in Cisco IOS Release 12.3(9a)BC5.

New Hardware Features in Cisco IOS Release 12.3(9a)BC4

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC4.

New Software Features in Cisco IOS Release 12.3(9a)BC4

There are no new software features supported in Cisco IOS Release 12.3(9a)BC4.

New Hardware Features in Cisco IOS Release 12.3(9a)BC3

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC3.

New Software Features in Cisco IOS Release 12.3(9a)BC3

There are no new software features supported in Cisco IOS Release 12.3(9a)BC3.

New Hardware Features in Cisco IOS Release 12.3(9a)BC2

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC2.

New Software Features in Cisco IOS Release 12.3(9a)BC2

There are no new software features supported in Cisco IOS Release 12.3(9a)BC2.

New Hardware Features in Cisco IOS Release 12.3(9a)BC1

There are no new hardware features supported in Cisco IOS Release 12.3(9a)BC1.

New Software Features in Cisco IOS Release 12.3(9a)BC1

There are no new software features supported in Cisco IOS Release 12.3(9a)BC1.

New Hardware Features in Cisco IOS Release 12.3(9a)BC

The following hardware features are new in Cisco IOS Release 12.3(9a)BC:

Cisco uBR10-MC5X20S/U Broadband Processing Engine

Commencing with Cisco IOS Release 12.3(9a)BC, the Cisco uBR10-MC5X20S/U cable interface line card supports these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:

PacketCable 1.0 With CALEA

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Cisco uBR10012 OC-48 DPT/POS Interface Module Support for the Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

The Cisco uBR10012 OC-48 DPT/POS interface module supports both PRE1 and PRE2 performance routing engine modules in the Cisco uBR10012 router chassis. The Cisco OC-48 DPT/POS interface module is a dual-mode module, providing interface support for Packet over SONET (POS) or Spatial Reuse Protocol (SRP).

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 OC-48 DPT/POS interface module with these additional DOCSIS and High Availability features on the Cisco uBR10012 CMTS:

NetFlow Accounting Versions 5 and 8 Support

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

For additional information about installing and configuring the Cisco uBR10012 OC-48 DPT/POS interface module, refer to these documents on Cisco.com:

Cisco uBR10012 OC-48 DPT/POS Interface Module (FRU Installation Guide)

http://www.cisco.com/en/US/docs/cable/cmts/ubr10012/installation/field_replaceable_units/ub_oc48.html

Configuring the Cisco uBR10012 OC-48 DPT/POS Interface Module

http://www.cisco.com/en/US/docs/interfaces_modules/cable/line_cards/ubr_oc48_dpt_pos/configuration/guide/oc48pre2.html

Cisco uBR10012 Performance Routing Engine 2 (PRE2) Modules

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco uBR10012 performance routing engine 2 (PRE2) route processing modules.

The Cisco uBR10012, which is qualified for PacketCable 1.0, Data over Cable Service Interface Specifications (DOCSIS) 1.1 and EuroDOCSIS 1.1, is built to meet the current and future needs of multiple system operators (MSOs). With full Layer 3 routing capabilities and industry-leading capacity and scalability, the Cisco uBR10012 delivers the highest level of performance for mass deployment of next-generation IP services.

The Cisco uBR10012 is designed to meet the services, performance, and reliability required for large-scale multiservice applications. The Cisco uBR10012 allows cable providers to deliver value-added IP services with consistent high performance. Based on Cisco IOS® Software—the standard in routing technology—the Cisco uBR10012 offers the most advanced networking and routing options available.

The Cisco uBR10012 features these components:

Eight cable line cards to connect to the cable plant

Four high-performance WAN interfaces to connect to the IP backbone and external networks

Two Cisco Timing, Communication, and Control Plus (TCC+) cards to monitor the line cards and power supply

Two Cisco Performance Routing Engine (PRE) modules with Parallel Express Forwarding (PXF) processors for consistent, high-performance throughput, even with multiple services enabled

Two Power Entry Modules (PEMs) for uninterrupted power supply

Benefits of the Cisco uBR10012 PRE2 include the following:

Provides up to 6.2 mpps of processing power in the Cisco uBR10012 router

Backplane supports up to 6.4 Gbps duplex per slot

Uses Cisco patented PXF technology to provide maximum IP services performance

Supports processor redundancy— for enabling 99.999-percent network uptime

Supports Route Processor Redundancy Plus (RPR+) High Availability functions in the Cisco uBR10012 CMTS headend

Table 7 provides additional details about the features and benefits of the Cisco uBR10012 PRE2.

Table 7 Features and Benefits of Cisco uBR10012 PRE2

Features
Benefits

Provides up to 6.2-mpps processing.

The Cisco uBR10012 router with PRE2 provides the IP services and performance that service providers require when deploying new revenue-generating services. In contrast to other CMTS products that support only distributed processing or only centralized processing, the Cisco uBR10012 supports a mix of distributed, centralized, and parallel processing. This ensures optimized performance to a comprehensive suite of line-rate IP services.

Uses Cisco patented PXF technology to provide maximum IP services performance.

PXF technology provides the Cisco uBR10012 router with performance and consistent high throughput, even with multiple, simultaneous services enabled. Using PXF, the Cisco uBR10012 router enables service providers to turn on multiple services without experiencing performance degradation. This is crucial when service providers look to upgrade customers to new types of services. In addition, PXF is a software-based technology that enables the Cisco uBR10012 router to implement new services without upgrading hardware—thereby providing investment protection and saving customers time and money.

Supports processor redundancy—for enabling 99.999-percent network uptime.

Each Cisco uBR10012 chassis supports up to two PRE2 modules for redundancy. The Cisco uBR10012 router is designed to support 99.999-percent uptime and coupled with a superior set of high-availability features and functions.


Upgrading from Cisco uBR10012 PRE or PRE1 Modules to Cisco uBR10012 PRE2 Modules

For information about insertion, removal and upgrade of Field Replaceable Units such as the PRE2 modules, refer to the following document on Cisco.com:

Cisco uBR10012 Universal Broadband Router Performance Routing Engine Module 2

http://www.cisco.com/en/US/docs/interfaces_modules/cable/performance_routing_engine/installation/guide/pre5096.html

DOCSIS System Interoperability on the Cisco uBR10012 CMTS

This section describes the operation of primary interoperability features in the Cisco uBR10012 router. For additional DOCSIS information, refer to the following document on Cisco.com:

DOCSIS 1.1 for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_docs.html

DOCSIS 1.0 Baseline Privacy

DOCSIS baseline privacy interface (BPI) gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and cable modem. BPI ensures that a cable modem, uniquely identified by its Media Access Control (MAC) address, can obtain keying material for services only it is authorized to access.

To enable BPI, choose software at both the CMTS and cable modem that support this mode of operation. Select a Cisco IOS image that supports BPI. BPI must be enabled using the DOCSIS configuration file.

The cable modem must also support BPI. Cable modems must have factory-installed RSA private/public key pairs to support internal algorithms to generate key pairs prior to first BPI establishment.


Note RSA stands for Rivest, Shamir, and Adelman, inventors of a public-key cryptographic system.


Cable Modem Interoperability

The Cisco uBR10012 router supports DOCSIS-based two-way interoperability for cable modems that support basic Internet access, Voice over IP (VoIP), or Virtual Private Networks (VPNs).

EuroDOCSIS cable modems or set-top boxes (STBs) with integrated EuroDOCSIS CMs using Cisco uBR-MC16E cable interface line cards and Cisco IOS Release 12.2(4)BC1 or higher. EuroDOCSIS operation support includes 8-MHz Phase Alternating Line (PAL) or Systeme Electronique Couleur Avec Memoire (SECAM) channel plans.

DOCSIS 1.0 and 1.0+ Extensions

Earlier releases of Cisco IOS software for the uBR10012 router provide support for the original DOCSIS 1.0 standard, featuring basic best-effort data traffic and Internet access over the coaxial cable network. The DOCSIS 1.0+ extensions provides Quality of Service (QoS) enhancements for real-time traffic, such as voice calls, in anticipation of full DOCSIS 1.1 support.


Note All DOCSIS 1.0 extensions are activated only when a cable modem or Cisco uBR924 that supports these extensions solicits services using dynamic MAC messages or the feature set. If the cable modems in your network are pure DOCSIS 1.0-based, they receive regular DOCSIS 1.0 treatment from the Cisco CMTS.


DOCSIS 1.1 Extensions

The DOCSIS 1.1 specification provides the following functional enhancements over DOCSIS 1.0 coaxial cable networks:

Enhanced Quality of Service (QoS) gives priority for real-time traffic such as voice and video.

The DOCSIS 1.0 QoS model (a Service IDs (SID) associated with a QoS profile) has been replaced with a service flow model (SFID). This allows greater flexibility in assigning QoS parameters to different types of traffic and in responding to changing bandwidth conditions. See the "SFID Support for Multicast and Cable Interface Bundling" section.

Multiple service flows per cable modem supported in either direction due to packet classifiers.

Support for multiple service flows per cable modem allows a single cable modem to support a combination of data, voice, and video traffic.

Greater granularity is available in QoS per cable modem (in either direction), using unidirectional service flows.

Dynamic MAC messages are supported to create, modify, and tear down QoS service flows dynamically when requested by a DOCSIS 1.1 cable modem.

Several QoS models are supported for the upstream.

Best effort-Data traffic is sent on a non-guaranteed best-effort basis.

Committed Information Rate (CIR) supports the guaranteed minimum bandwidth for data traffic.

Unsolicited Grants (UGS) support constant bit rate (CBR) traffic, such as voice, that is characterized by fixed size packets at fixed intervals.

Real Time Polling (rtPS) supports Real Time service flows, such as video, that produce unicast, variable size packets at fixed intervals.

Unsolicited Grants with Activity Detection (USG-AD) support the combination of UGS and RTPS, to accommodate real time traffic that might have periods of inactivity (such as voice using silence suppression). The service flow uses UGS fixed grants while active, but switches to RTPS polling during periods of inactivity to avoid wasting unused bandwidth.

Enhanced time-slot scheduling mechanisms support guaranteed delay/jitter sensitive traffic on the shared multiple access upstream link.

Payload header suppression (PHS) conserves link-layer bandwidth by suppressing unnecessary packet headers on both upstream and downstream traffic flows.

Layer 2 fragmentation on the upstream prevents large data packets from affecting real-time traffic, such as voice and video. Large data packets are fragmented and then transmitted in the timeslots that are available between the timeslots used for the real-time traffic.

Concatenation allows a cable modem to send multiple MAC frames in the same timeslot, as opposed to making an individual grant request for each frame. This avoids wasting upstream bandwidth when sending a number of very small packets, such as TCP acknowledgement packets.

DOCSIS 1.1 cable modems can coexist with DOCSIS 1.0 and 1.0+ cable modems in the same network—the Cisco uBR10012 router provides the levels of service that are appropriate for each cable modem.

DOCSIS 1.1 Quality of Service

The DOCSIS 1.1 QoS framework is based on the following objects:

Service class: A collection of settings maintained by the CMTS that provide a specific QoS service tier to a cable modem that has been assigned a service flow within a particular service class.

Service flow: a unidirectional sequence of packets receiving a service class on the DOCSIS link.

Packet classifier: A set of packet header fields used to classify packets onto a service flow to which the classifier belongs.

PHS rule: A set of packet header fields that are suppressed by the sending entity before transmitting on the link, and are restored by receiving entity after receiving a header-suppressed frame transmission. Payload header suppression increases the bandwidth efficiency by removing repeated packet headers before transmission.

In DOCSIS 1.1, the basic unit of QoS is the service flow, which is a unidirectional sequence of packets transported across the RF interface between the cable modem and CMTS. A service flow is characterized by a set of QoS parameters such as latency, jitter, and throughput assurances.

Every cable modem establishes a primary service flow in both the upstream and downstream directions. The primary flows maintain connectivity between the cable modem and CMTS at all times.

In addition, a DOCSIS 1.1 cable modem can establish multiple secondary service flows. The secondary service flows can either be permanently created (they persist until the cable modem is reset or powered off) or they can be created dynamically to meet the needs of the on demand traffic being transmitted.

Each service flow has a set of QoS attributes associated with it. These QoS attributes define a particular class of service and determine characteristics such as the maximum bandwidth for the service flow and the priority of its traffic. The class of service attributes can be inherited from a preconfigured CMTS local service class (class-based flows), or they can be individually specified at the time of the creation of the service flow.

Each service flow has multiple packet classifiers associated with it, which determine the type of application traffic allowed to be sent on that service flow. Each service flow can also have a Payload header suppression (PHS) rule associated with it to determine which portion of the packet header will be suppressed when packets are transmitted on the flow.

New Software Features for Cisco IOS Release 12.3(9a)BC

This section describes the following new software features and CLI command changes for Cisco IOS Release 12.3(9a)BC and the Cisco uBR10012 router:

Cable ARP Filter Enhancement

Cisco Broadband Troubleshooter 3.2

Cisco CMTS Static CPE Override

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

DOCSIS Set-Top Gateway Issue 1.0

Dynamic Shared Secret (DMIC) with OUI Exclusion

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

NetFlow Accounting Versions 5 and 8 Support

PacketCable 1.0 With CALEA

SFID Support for Multicast and Cable Interface Bundling

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Subscriber Traffic Management (STM) Version 1.1

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Usage Based Billing (SAMIS)

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual Interface Support for HCCP N+1 Redundancy

Cable ARP Filter Enhancement

The cable arp filter command, introduced with Cisco IOS Release 12.2(15)BC2b, enables service providers to filter ARP request and reply packets. This prevents a large volume of such packets from interfering with the other traffic on the cable network.

Cisco IOS Release 12.3(9a)BC introduces enhanced command option syntax for the cable arp filter command, where number and window-size values are optional for reply-accept and request-send settings.

To control the number of Address Resolution Protocol (ARP) packets that are allowable for each Service ID (SID) on a cable interface, use the cable arp command in cable interface configuration mode. To stop the filtering of ARP broadcasts for CMs, use the no form of this command.

cable arp filter {reply-accept number window-size | request-send number window-size}

no cable arp filter {reply-accept | request-send}

default cable arp filter {reply-accept | request-send}

Syntax Description

reply-accept number window-size

Configures the cable interface to accept only the specified number of ARP reply packets every window-size seconds for each active Service ID (SID) on that interface. The cable interface drops ARP reply packets for a SID that would exceed this number.

number = (Optional) Number of ARP reply packets that is allowed for each SID within the window time period. The allowable range is 0 to 20 packets, with a default of 4 packets. If number is 0, the cable interface drops all ARP reply packets. If not specified, this value uses default.

window-size = (Optional) Size of the window time period, in seconds, in which to monitor ARP replies. The valid range is 1 to 5 seconds, with a default of 2 seconds.

request-send number window-size

Configures the cable interface to send only the specified number of ARP request packets every window-size seconds for each active SID on that interface. The cable interface drops ARP requests for a SID that would exceed this number.

number = (Optional) Number of ARP request packets that is allowed for each SID within the window time period. The allowable range is 0 to 20 packets, with a default of 4 packets. If number is 0, the cable interface does not send any ARP request packets.

window-size = (Optional) Size of the window time period, in seconds, in which to monitor ARP requests. The valid range is 1 to 5 seconds, with a default of 2 seconds.


Cisco IOS Release 12.3(9a)BC also removes a prior caveat with HCCP Protect interfaces. Previously, in the event of a revert-back HCCP N+1 switchover, manual removal of cable arp filter reply and cable arp filter request configurations may have been required afterward on Protect interfaces.

For more information about ARP Filtering, refer to the following document on Cisco.com:

Cable ARP Filtering

http://www.cisco.com/en/US/docs/cable/cmts/feature/cblarpfl.html

Cisco Broadband Troubleshooter 3.2

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco Broadband Troubleshooter (CBT) Version 3.2 on the Cisco uBR10012 universal broadband router, with newly supported interoperability for the following additional software features:

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Subscriber Traffic Management (STM) Version 1.1

Multiple Service Operators (MSO) provide a variety of services such as TV, video on demand, data, and voice telephony to subscribers. Network Administrators and radio frequency (RF) technicians need specialized tools to resolve RF problems in the MSO's cable plant. Cisco Broadband Troubleshooter 3.2 (CBT 3.2) is a simple, easy-to-use tool designed to accurately recognize and resolve such issues.

The user can select up to three different cable modems (CMs) under the same CMTS or three different upstreams under the same CMTS. In addition, CBT 3.2 introduces the ability to display upstreams and cable modems combined (mixed) on the same trace window for monitoring and for playback.


Note CBT 3.2 resolves the former CBT 3.1 caveat CSCee03388. With CBT 3.1, trace windows did not support the mixing of upstreams or cable modems.


For additional information about CBT 3.2, spectrum management and STM 1.1, refer to the following documents on Cisco.com:

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html

Spectrum Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html

Subscriber Traffic Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html

Cisco CMTS Static CPE Override

The cable submgmt static-cpe-override command enables Multiple Service Operators (MSOs) to override network DHCP settings on CPE devices when performing troubleshooting with a laptop computer and console connection to the Cisco universal broadband router.

For additional information about using the cable submgmt static-cpe-override command, refer to these documents on Cisco.com:

"cable submgmt default" section

Cisco CMTS Static CPE Override

http://www.cisco.com/en/US/docs/cable/cmts/feature/stat_cpe.html

Cisco IOS CMTS Cable Command Reference

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

Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements

Cisco IOS Release 12.3(9a)BC introduces or enhances the following CLI commands for the Cisco uBR10012 router:

cable arp filter

cable logging layer2events

cable source-verify

show cable tech-support

show controllers cable

show tech-support

For additional information about these command changes, refer to these resources:

"Related Documentation" section

Cisco IOS CMTS Cable Command Reference

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

DOCSIS Set-Top Gateway Issue 1.0

Cisco IOS Release 12.3(9a)BC introduces support for DOCSIS Set-Top Gateway (DSG) Issue 1.0 on the Cisco uBR10012 universal broadband router. The DOCSIS Set-Top Gateway (DSG) feature allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing DOCSIS networks. This allows MSOs and other service providers to combine both DOCSIS and STB operations over one, open, vendor-independent network, without any change to the existing network or cable modems.

DSG is a CableLabs® specification that allows the Cisco CMTS to provide a class of cable services known as out-of-band (OOB) messaging to set-top boxes (STBs) over existing Data-over-Cable Service Interface Specifications (DOCSIS) cable networks. DSG 1.0 allows cable Multi-System Operators (MSOs) and other service providers to combine both DOCSIS and STB operations over a single, open and vendor-independent network without requiring any changes to the existing DOCSIS network infrastructure.

At the time of this Cisco publication, the CableLabs® DOCSIS DSG specification is in the current status of "Issued" as characterized by stability, rigorous review in industry and cross-vendor interoperability.

For additional information about configuring and using DSG 1.0 on the Cisco uBR10012 router, refer to the following document on Cisco.com:

DOCSIS Set-Top Gateway for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdsg12.html

Dynamic Shared Secret (DMIC) with OUI Exclusion

Cisco IOS Release 12.3(9a)BC introduces the option of excluding the Organizational Unique Identifiers (OUIs) from being subjected to the DMIC check. The new cable dynamic-secret exclude command allow specific cable modems to be excluded from the Dynamic Shared Secret feature on the following Cisco CMTS platforms:

Cisco uBR7246VXR universal broadband router

Cisco uBR10012 universal broadband router

The Dynamic Shared Secret feature automatically creates a unique DOCSIS shared secret on a per-modem basis, creating a one-time use DOCSIS configuration file that is valid only for the current session. This ensures that a DOCSIS configuration file that has been downloaded for one cable modem can never be used by any other modem, nor can the same modem reuse this configuration file at a later time.

This patent-pending feature is designed to guarantee that all registered modems are using only the quality of service (QoS) parameters that have been specified by the DOCSIS provisioning system for that particular modem at the time of its registration.

For additional command information, refer to the following document on Cisco.com:

Configuring a Dynamic Shared Secret for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrdmic.html

Cisco IOS CMTS Cable Command Reference

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

EtherChannel Support on the Cisco uBR10012 Universal Broadband Router

Cisco IOS Release 12.3(9a)BC introduces support for Gigabit EtherChannel (GEC) on the Cisco uBR10012 universal broadband router with the PRE2 performance routing engine modules. Cisco IOS Release 12.3(9) supports Gigabit Ethernet interfaces for IEEE 802.1Q inter-VLAN trunking with increased bandwidth on the Cisco uBR10012 router.


Note FastEtherChannel (FEC) interfaces and ATM trunking are not supported on the Cisco uBR10012 router.



Note Cisco IOS Release 12.3(9a)BC introduces support for Gigabit EtherChannel (GEC) on the Cisco uBR10012 universal broadband router with the PRE2 performance routing engine modules.


EtherChannel provides Gigabit Ethernet (GE) speeds by grouping multiple GE-speed ports into a logical port channel that supports speeds up to 8 Gbps. This provides fault-tolerant, high-speed links between switches, routers and servers.

Trunking is configured between the switch and the router to provide inter-VLAN communication over the network. Trunking carries traffic from several VLANs over a point-to-point link between the two network devices. In a campus network, trunking is configured over an EtherChannel link to carry the multiple VLAN information over a high-bandwidth channel.

For additional information about configuring EtherChannel on the Cisco uBR10012 router, refer to the following document on Cisco.com:

EtherChannel on the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_ethr.html

MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC

Cisco IOS Release 12.3(9a)BC adds the following new MIB support for the Cisco uBR10012 router.

CISCO-CABLE-METERING-MIB

CISCO-CABLE-QOS-MONITOR MIB

CISCO-CABLE-SPECTRUM-MIB

CISCO-ENHANCED-MEMPOOL-MIB

CISCO-PROCESS-MIB

DOCS-QOS-MIB

For additional information about MIBs for the Cisco CMTS, refer to the following resources on Cisco.com:

Cisco CMTS Universal Broadband Router MIB Specifications Guide

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

SNMP Object Navigator

http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en

CISCO-CABLE-METERING-MIB

The CISCO-CABLE-METERING-MIB contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format, also known as Usage-Based Billing on the Cisco CMTS. This format is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.

The MODULE-IDENTITY for the CISCO-CABLE-METERING-MIB is ciscoCableMeteringMIB, and its top-level OID is 1.3.6.1.4.1.9.9.424 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.ciscoCableMeteringMIB).


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


Additional Information

For additional SAMIS information, refer to the following resources:

"Usage Based Billing (SAMIS)" section

Usage Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_use-bsd_bill_ps2209_TSD_Products_Configuration_Guide_Chapter.html

CISCO-CABLE-QOS-MONITOR MIB

Cisco IOS Release 12.3(9a)BC introduces additional features for the CISCO-CABLE-QOS-MONITOR MIB, including the following:

Clarified the descriptions of a number of objects.

Added a number of objects in the ccqmCmtsEnforceRuleTable to support DOCSIS 1.1 and DOCSIS 2.0 cable modems and to support peak and off-peak monitoring.

Added the ccqmCmtsIfBwUtilTable to provide thresholds for downstream/upstream bandwidth utilization.

Deprecated and removed ccqmCmtsEnfRuleByteCount.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-CABLE-SPECTRUM-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router, with these additional MIB object enhancements:

ccsFlapListMaxSize and ccsFlapListCurrentSize SNMP objects provide additional description for cable flap lists.

Added the ccsCmFlapTable to replace the ccsFlapTable. The new object uses downstream, upstream and Mac as indices to replace the ccsFlapTable object.

The enhanced ccsSNRRequestTable object provides a table of SNR requests with modified description.

Added the ccsUpSpecMgmtUpperBoundFreq object to assist with spectrum management on the Cisco CMTS.

Added the ccsCompliance5 object.

Added ccsCmFlapResetNow to reset the flap list for a particular cable modem.

Updated the descriptions for ccsFlapListMaxSize, ccsFlapListCurrentSize, and ccsSNRRequestTable.

The following objects are also now deprecated:

ccsFlapPowerAdjustThreshold

ccsFlapMissThreshold

ccsFlapResetAll

ccsFlapClearAll

ccsFlapLastClearTime

The maximum number of entries in the flap-list was changed from a maximum of 8191 for the entire router, to the following:

8191 entries for each Broadband Processing Engine (BPE) cable interface, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U.

8191 maximum flap-list entries for all non-BPE cable interfaces, such as the Cisco uBR-MC16C, Cisco uBR-MC16S, and Cisco uBR-MC28C.

Two objects are now used to track the flap list size:

ccsFlapListMaxSize—Reflects the flap list size, as configured by the cable flap-list size command.

ccsFlapListCurrentSize—Reflects the current size of the flap list for each MAC domain (downstream).


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-ENHANCED-MEMPOOL-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR10012 universal broadband router. The CISCO-ENHANCED-MEMPOOL-MIB enables you to monitor CPU and memory utilization for "intelligent" line cards and broadband processing engines on the Cisco uBR10012 router. These include the Cisco MC16X and MC28X series line cards.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


CISCO-PROCESS-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-PROCESS-MIB on the Cisco uBR10012 universal broadband router with PRE2 modules.The CISCO-PROCESS-MIB enables you to monitor CPU and memory utilization for RF cards, cable interface line cards and broadband processing engines on the Cisco uBR10012 router.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


DOCS-QOS-MIB

Cisco IOS Release 12.3(9) introduces additional MIB object enhancements for the DOCS-QOS-MIB on the Cisco uBR10012 universal broadband router:

Updated with the DOCSIS operations support system interface (OSSI) v2.0-N-04.0139-2.

The default values of docsQosPktClassIpSourceMask and docsQosPktClassIpDestMask objects are set to 0xFFFFFFFF.


Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


DSG-IF-MIB

The DSG-IF-MIB defines objects that are used to configure, control, and monitor the operation of the DOCSIS Set-top Gateway (DSG) 1.0 feature on Cisco uBR7200 series and Cisco uBR10012 routers.


Note The MODULE-IDENTITY for the DSG-IF-MIB is dsgIfMib, and its top-level OID is 1.3.6.1.4.1.9.9.999 (iso.org.dod.internet.private.enterprises.cisco.ciscoMgmt.dsgIfMib). Because this is an experimental MIB, its top-level OID is expected to change when the DSG specifications are finalized.



Note Refer to the Cisco CMTS Universal Broadband Router MIB Specifications Guide on Cisco.com for additional information and MIBs constraints.


NetFlow Accounting Versions 5 and 8 Support

Cisco IOS Release 12.3(9a)BC introduces support for NetFlow Accounting Versions 5 and 8 on the Cisco uBR10012 router.


Note The Cisco uBR10012 router requires the PRE2 performance routing engine module to support NetFlow in Cisco IOS Release 12.3(9a)BC, and later releases in the 12.3 BC train. Also note that performance with packets-per-second (PPS) is reduced by 50% when NetFlow is enabled, as two passes per packet are required.


NetFlow enables you to collect traffic flow statistics on your routing devices. NetFlow provides network administrators with access to "call detail recording" information from their data networks. Exported NetFlow data can be used for a variety of purposes, including network management and planning, enterprise accounting and departmental chargebacks, ISP billing, data warehousing and data mining for marketing purposes.

NetFlow is based on identifying packet flows for ingress IP packets. It does not require any connection-setup protocol either between routers or to any other networking device or end station and does not require any change externally—either to the traffic or packets themselves or to any other networking device.

NetFlow is completely transparent to the existing network, including end stations and application software and network devices like LAN switches. Also, NetFlow is performed independently on each internetworking device, it need not be operational on each router in the network. Using NetFlow Data Export (NDE), you can export data to a remote workstation for data collection and further processing. Network planners can selectively invoke NDE on a router or on a per-subinterface basis to gain traffic performance, control, or accounting benefits in specific network locations.

NetFlow Version 5 Features and Format

NetFlow exports flow information in UDP datagrams in one of two formats. The version 1 format was the initially released version, and version 5 is a later enhancement to add Border Gateway Protocol (BGP) autonomous system (AS) information and flow sequence numbers.

In NetFlow Version 1 and Version 5 formats, the datagram consists of a header and one or more flow records. The first field of the header contain the version number of the export datagram. Typically, a receiving application that accepts either format allocates a buffer big enough for the biggest possible datagram from either format and uses the version from the header to determine how to interpret the datagram. The second field in the header is the number of records in the datagram and should be used to index through the records.

All fields in either version 1 or version 5 formats are in network byte order. Table 5 and Table 6 describe the data format for version 1, and Table 7 and Table 8 describe the data format for version 5.

We recommend that receiving applications check datagrams to ensure that the datagrams are from a valid NetFlow source. We recommend you first check the size of the datagram to make sure it is at least long enough to contain the version and count fields. Next we recommend you verify that the version is valid (1 or 5) and that the number of received bytes is enough for the header and count flow records (using the appropriate version).

Because NetFlow export uses UDP to send export datagrams, it is possible for datagrams to be lost. To determine whether or not flow export information is lost, the version 5 header format contains a flow sequence number. The sequence number is equal to the sequence number of the previous plus the number of flows in the previous datagram. After receiving a new datagram, the receiving application can subtract the expected sequence number from the sequence number in the header to get the number of missed flows.

Table 8 lists the byte definitions for NetFlow Version 5 header format.

Table 8 NetFlow Version 5 Header Format

Bytes
Content
Description

0-3

version and count

NetFlow export format version number and number of flows exported in this packet (1-30).1

4-7

SysUptime

Current time in milliseconds since router booted

8-11

unix_secs

Current seconds since 0000 UTC 1970.

12-15

unix_nsecs

Residual nanoseconds since 0000 UTC 1970.

16-19

flow_sequence

Sequence counter of total flows seen.

20-23

reserved

Unused (zero) bytes.

1 NetFlow Version 5 export packets (set with ip flow-export command) allow the number of records stored in the datagram to be a variable between 1 and 30.


Table 9 lists the byte definitions for Version 5 flow record format.

Table 9 NetFlow Version 5 Flow Record Format

Bytes
Content
Description

0-3

srcaddr

Source IP address.

4-7

dstaddr

Destination IP address.

8-11

nexthop

Next hop router's IP address.

12-15

input and output

Input and output interface's SNMP index.

16-19

dPkts

Packets in the flow.

20-23

dOctets

Total number of Layer 3 bytes in the flow's packets.

24-27

First

SysUptime at start of flow.

28-31

Last

SysUptime at the time the last packet of flow was received.

32-35

srcport and dstport

TCP/UDP source and destination port number or equivalent.

36-39

pad1, tcp_flags, prot, and tos

Unused (zero) byte, Cumulative OR of TCP flags, IP protocol (for example, 6=TCP, 17=UDP), and IP type-of-service.

40-43

src_as and dst_as

AS of the source and destination, either origin or peer.

44-47

src_mask, dst_mask, and pad2

Source and destination address prefix mask bits, pad 2 is unused (zero) bytes.


NetFlow Version 8 Features and Format

NetFlow exports flow information in UDP datagrams in one of several formats. Version 8, a new data export version, has been added to support data exports from aggregation caches. Version 8 allows for export datagrams to contain a subset of the usual version 5 export data, which is valid for a particular aggregations scheme type.

Figure 1 illustrates the NetFlow Version 8 header format.

Figure 1 Version 8 Header Format

Table 10 lists definitions for terms used in the version 8 header.

Table 10 Terms and Definitions for Version 8 Headers

Term
Definition

Version

The flow export format version number. In this case, the number is "8".

Count

The number of export records in the datagram.

System Uptime

The number of milliseconds since the router was last booted.

UNIX Seconds

The number of seconds since 0000 Universal Time Code (UTC) 1970.

UNIX Nanoseconds

The number of residual nanoseconds since 0000UTC 1970.

Sequence Number

Sequence counter of total flows sent for this export stream.

Engine Type

The type of switching engine. RP=0 and LC=1.

Engine ID

The slot number of the NetFlow switching engine.

Aggregation

The type of aggregation scheme being used.

Aggregation Version

The aggregation subformat version number. The current value is "2".


Additional Information about NetFlow on the Cisco CMTS

For additional information about configuring NetFlow Accounting on Cisco CMTS, refer to the following documents on Cisco.com:

NetFlow Overview, Version 5

http://www.cisco.com/en/US/docs/net_mgmt/netflow_collection_engine/5.0/user/guide/overview.html

NetFlow Overview, Version 8

http://www.cisco.com/en/US/prod/collateral/iosswrel/ps6537/ps6555/ps6601/prod_presentation0900aecd80311f57.pdf

Configuring NetFlow (Versions 1 and 5)

http://www.cisco.com/en/US/docs/net_mgmt/netflow_collection_engine/5.0/installation/guide/config.html

Configuring NetFlow (Version 8)

http://www.cisco.com/en/US/docs/net_mgmt/netflow_collection_engine/6.0/tier_one/installation/guide/install_1.html Toolkit

Cisco IOS NetFlow White Papers

http://www.cisco.com/en/US/products/ps6601/prod_white_papers_list.html

Cisco IOS Software Home Page for NetFlow

http://www.cisco.com/en/US/products/ps6601/products_ios_protocol_group_home.html

PacketCable 1.0 With CALEA

Cisco IOS Release 12.3(9a)BC introduces DOCSIS 1.1 support for PacketCable 1.0 with Communications Assistance for Law Enforcement Act (CALEA) on the Cisco uBR10012 universal broadband router with the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE).

PacketCable is a program initiative from Cablelabs and its associated vendors to establish a standard way of providing packet-based, real-time video and other multimedia traffic over hybrid fiber-coaxial (HFC) cable networks. The PacketCable specification is built upon the Data-over-Cable System Interface Specifications (DOCSIS) 1.1, but it extends the DOCSIS protocol with several other protocols for use over non-cable networks, such as the Internet and the public switched telephone network (PSTN).

This allows PacketCable to be an end-to-end solution for traffic that originates or terminates on a cable network, simplifying the task of providing multimedia services over an infrastructure composed of disparate networks and media types. It also provides an integrated approach to end-to-end call signaling, provisioning, quality of service (QoS), security, billing, and network management.

Cisco IOS Release 12.2(11)BC1 and later releases in the Cisco IOS 12.3 release train support the PacketCable 1.0 specifications and the CALEA intercept capabilities of the PacketCable 1.1 specifications.

For additional information about configuring PacketCable on the Cisco CMTS, refer to the following document on Cisco.com:

Configuring PacketCable on the Cisco CMTS

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_pktcable_mm_ps2209_TSD_Products_Configuration_Guide_Chapter.html

SFID Support for Multicast and Cable Interface Bundling

Cisco IOS Release 12.3(9a)BC removes the prior restriction in Caveat CSCea45592 that prevented the creation of DOCSIS 1.1 upstream packet classifiers and service flow IDs (SFIDs) when configuring multicast groups with bundled cable interfaces. Cable interface bundling now supports SFIDs on Multicast groups.


Note SFIDs map individual CPE devices to separate MPLS-Virtual Private Network (VPN) interfaces.



Note Cisco IOS Release with the Cisco uBR10012 router does not support overlapping IP addresses with MPLS-VPN.


For additional configuration information, refer to the following document on Cisco.com:

Cable Interface Bundling for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

CBT 3.2 Spectrum Management Support with the Cisco uBR10-MC5X20S/U BPE

Cisco IOS Release 12.3(9a)BC introduces support for remote spectrum management for the Cisco uBR10012 router. Cisco uBR10012 spectrum management supports interoperability with these enhancements to the Cisco CMTS in Cisco IOS 12.3(9a)BC:

Cisco Broadband Troubleshooter 3.2, supporting the Cisco uBR10-MC5X20S/U Broadband Processing Engine (BPE)

Subscriber Traffic Management (STM) Version 1.1

Additional supported spectrum management functions are available on the Cisco uBR10012 router. For a complete list, and the latest information about Spectrum Management on the Cisco uBR10012 router, refer to the following documents on Cisco.com:

Spectrum Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_spec.html

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html

"Subscriber Traffic Management (STM) Version 1.1" section

Subscriber Traffic Management (STM) Version 1.1

Cisco IOS Release 12.3(9a)BC introduces support for Subscriber Traffic Management (STM) through Version 1.1 on the Cisco uBR10012 universal broadband router. STM 1.1 supports DOCSIS 1.1-compliant cable modems.

The STM feature enables service providers to identify and control subscribers who exceed the maximum bandwidth allowed under their registered quality of service (QoS) profiles. STM is a simple bandwidth management tool which works as a low CPU alternative to Network-Based Application Recognition (NBAR) and access control lists (ACLs), however, using STM does not mean that NBAR and ACLs have to be turned off; STM can be applied along with NBAR and ACLs. STM 1.1 also works in conjunction with the Cisco Broadband Troubleshooter 3.2 to support additional network management and troubleshooting functions in the Cisco CMTS.

STM 1.1 extends earlier STM functions to monitor a subscriber's traffic on DOCSIS 1.1 primary service flows and supports these additional features:

Cisco Broadband Troubleshooter (CBT) 3.2 supports STM 1.1.

DOCSIS 1.0-compliant and DOCSIS 1.1-compliant cable modem are supported.

Monitoring and application of traffic management policies are applied on a service-flow basis.

Monitoring window duration increased from seven to 30 days.

For additional information about STM 1.1 and Cisco CBT 3.2, refer to the following document on Cisco.com:

Subscriber Traffic Management for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubsubmon.html

Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/en/US/products/sw/netmgtsw/ps530/prod_release_notes_list.html

Transparent LAN Service (TLS) on the Cisco uBR10012 Router with IEEE 802.1Q

Cisco IOS 12.3(9a)BC introduces support for the Transparent LAN Service over Cable feature on the Cisco 10012 router. This feature enhances existing Wide Area Network (WAN) support to provide more flexible Managed Access for multiple Internet service provider (ISP) support over a hybrid fiber-coaxial (HFC) cable network.

This feature allows service providers to create a Layer 2 tunnel by mapping an upstream service identifier (SID) to an IEEE 802.1Q Virtual Local Area Network (VLAN).

For additional information about configuring TLS on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:

Transparent LAN Service over Cable

http://www.cisco.com/en/US/docs/cable/cmts/feature/tls-cmts.html


Note Cisco TLS for the Cisco uBR10012 router requires the PRE2 performance routing engine module with Cisco IOS Release 12.3(9a)BC or a later release in the Cisco IOS 12.3BC train.


Usage Based Billing (SAMIS)

Cisco IOS Release 12.3(9a)BC introduces the Usage-Based Billing feature on the Cisco uBR10012 router. This feature provides subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. SAMIS is specified by the Data-over-Cable Service Interface Specifications (DOCSIS) Operations Support System Interface (OSSI) specification.

The CISCO-CABLE-METERING-MIB is also introduced with Cisco IOS Release 12.3(9a)BC in support of SAMIS.

For additional information about configuring and monitoring Usage-Based Billing (SAMIS) on the Cisco uBR10012 CMTS, refer to the following document on Cisco.com:

Usage Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/ubrsamis.html

Virtual Interface and Frequency Stacking Support on the Cisco uBR10-MC5X20S/U BPE

Virtual interfaces (VI) and frequency stacking (FS) are two features that allow user-configurable MAC domains and multiple frequencies on one physical connector.

Virtual interfaces allow up to eight upstreams (USs) per downstream (DS). A virtual interface links an upstream (US) port to a physical connector.

Cisco IOS Release 12.3(9a)BC introduces Virtual Interface Support for HCCP N+1 Redundancy with the Cisco uBR10-MC5X20S/U BPE.

Frequency stacking allows two frequencies to be configured on one physical connector.

Cisco IOS Release 12.3(9a)BC introduces support for frequency stacking on the Cisco uBR10012 router.

The Cisco uBR10-MC5X20S/UBPE can be configured (initially) to match the DS and US configuration of an existing line card, and then the cable operator can modify the configurations according to their needs. This supports different DS-to-US port ratios as such combination ratios evolve (1x6 » 1x4 » 1x1). For example, the line card can be used in 1x1 configuration for a business customer and in 1x7 configuration for residential customers.

For additional information about configuring virtual interfaces and frequency stacking, refer to the following document on Cisco.com:

Virtual Interfaces and Frequency Stacking Configuration on MC5x20S and MC28U Linecards

http://www.cisco.com/en/US/tech/tk86/tk804/technologies_white_paper09186a0080232b49.shtml

Configuring Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/interfaces_modules/cable/broadband_processing_engines/ubr10_mc5x20s_u_h/feature/guide/mc5x2vif.html

Virtual Interface Support for HCCP N+1 Redundancy

Cisco IOS Release 12.3(9a)BC introduces support for HCCP N+1 Redundancy for virtual interfaces configured on the Cisco uBR10012 universal broadband router using the Cisco uBR10-MC5X20S/U BPE.

HCCP N+1 Redundancy is an important step toward high availability on CMTS and telecommunications networks that use broadband media. HCCP N+1 Redundancy can help limit Customer Premises Equipment (CPE) downtime by enabling robust automatic switchover and recovery in the event that there is a localized disruption in service.

Beginning with Cisco IOS Release 12.2(15)BC2a, HCCP N+1 Redundancy adds synchronization between HCCP Working interface configurations and those inherited upon switchover to HCCP Protect interfaces. This makes the configuration of both easier and switchover times faster.

For additional information about configuring virtual interfaces in HCCP N+1 redundancy on the Cisco CMTS, refer to the following document on Cisco.com:

N+1 Redundancy for the Cisco Cable Modem Termination System

http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_nplus1_redun_ps2209_TSD_Products_Configuration_Guide_Chapter.html

Configuring Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

MIBs

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

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

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to cco-locksmith@cisco.com. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL:

http://tools.cisco.com/RPF/register/register.do

MIB Changes and Enhancements for Cisco IOS Release 12.3(21)BC:

The DOC-QOS-MIB enhancement in Cisco IOS Release 12.3(21)BC added new tables to support SNMP QoS MIB query time in a large scale system with much less CPU consumption. The overall performance is better in multiple SNMP query sessions on the six tables than a single session. However, this solution has the following restrictions:

The ideal number of multiple sessions is around 7-10. Even though up to 128 multiple sessions are supported, it is not recommended to have more than 30 multiple sessions.

The improvement may not be visible in a small scale system. For example less than 100 CM per LC.

If multiple SNMP sessions all query the 6 enhanced DOCS-QOS-MIB tables with the same number of objects per session as the single-session query then the per session response time could be better than the single SNMP session with the same number of MIB objects. Please note, the aggregated CPU utilization for multiple sessions is still higher than the single session query on the CMTS. It is under the condition that both RP and line card CPU utilizations are not stressed.


Note The number of multiple sessions should equal the number of parallel object queries.


MIB Constraints and Notes

This MIB is supported only in Cisco IOS Release 12.2(4)BC1 through Release 12.2(11)BC3 to support DOCSIS 1.1 operations. The MIB is deprecated in later releases to conform with the DOCSIS 2.0 specifications.

.

Table 11 DOCS-QOS-MIB Constraints 

MIB Object
Notes
docsQosCmtsMacToSrvFlowTable

Do not use GET-NEXT requests to retrieve the rows of this table, because it could require lengthy, time-consuming searches on the MAC address, which could consume excessive amounts of CPU processor time when the table is large. Instead, retrieve the individual rows using a GET request that uses the device's MAC address as the table index. This avoids possible performance problems and also ensures that the retrieved rows contain the most current, real-time data for those devices.

A GET request for docsQosCmtsMacToSrvFlowTable returns NULL if the router is already processing another request for this table (either by an SNMP GET or CLI show command). A null is also returned if the router is processing a request for any other table that is indexed by CM or CPE MAC address, such as cdxCmCpeEntry, cdrqCmtsCmStatusTable, and docsIfCmtsMacToCmTable.

Wait until the first request is done and then repeat the request for docsQosCmtsMacToSrvFlowTable.

docsQosParamSetTable

This table describes the set of DOCSIS 1.1 QOS parameters defined in a managed device.

docsQosParamSetMaxTrafficBurst

Valid only for Best Effort, non-Real-Time Polling, and Real-Time Polling bursts. For all other bursts, this object reports 0.

docsQosServiceClassDirection

docsQosServiceClassSchedulingType

These objects must be set together as part of the same SET request when configuring a downstream service class.

docsQosParamSetEntry**

Identifies a unique set of QoS parameters.

docsQosServiceFlowStatsTable

Reports the downstream traffic counters for cable modems that are provisioned for DOCSIS 1.1 and DOCSIS 2.0 operation. For DOCSIS 1.0 cable modems, use the cdxCmtsServiceExtTable in CISCO-DOCS-EXT-MIB.

docsQosServiceFlowStatsEntry**

Describes a set of service flow statistics. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127)."

docsQosPHSTable

This table describes set of payload header suppression entries.

docsQosPHSEntry**

 
docsQosPktClassTable
 

docsQosPktClassEntry**

An entry in this table that provides a single packet classifier rule.

docsQosServiceFlowTable
 

docsQosServiceFlowEntry**

Describes a service flow. An entry in the table exists for each Service Flow ID. The ifIndex is an ifType of docsCableMaclayer(127).

docsQosUpstreamStatsTable
 

docsQosUpstreamStatsEntry**

Describes a set of upstream service flow statistics.

docsQosServiceFlowLogTable

Logs deleted DOCSIS 1.1 and DOCSIS 2.0 service flows, but this table does not contain any information until after logging is specifically enabled using the cable sflog command in global configuration mode.

docsQosDynamicServiceStatsTable

(not applicable for Docsis 1.0 modems)

docsQosDCCReqs

Read-only.The number of Dynamic Channel Change Request messages traversing an interface. This count is nonzero only on downstream direction rows.

docsQosDCCRsps

Read-only. The number of Dynamic Channel Change Response messages traversing an interface. This count is nonzero only on upstream direction rows.

docsQosDCCAcks

Read-only. The number of Dynamic Channel Change Acknowledgement messages traversing an interface. This count is nonzero only on downstream direction rows.

docsQosDCCs

Read-only. The number of successful Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows.

docsQosDCCFails

Read-only. The number of failed Dynamic Channel Change transactions. This count is nonzero only on downstream direction rows.

**The SNMP query sessions have been improved in these tables.



Note For detailed information about load balancing and dynamic channel change on CMTS, go to the following URL:
http://www.cisco.com/en/US/docs/cable/cmts/troubleshooting_batch9/cmtslbg.html


MIB Changes and Enhancements for Cisco IOS Release 12.3(17a)BC:

MIB enhancements in Cisco IOS Release 12.3(17a)BC provide enhanced management features that enable the Cisco uBR 7200 Series router and the Cisco uBR 10012 router to be managed through the Simple Network Management Protocol (SNMP). These enhanced management features allow you to:

Use SNMP set and get requests to access information in Cisco CMTS universal broadband routers

Reduce the amount of time and system resources required to perform functions like inventory management

A standards-based technology (SNMP) for monitoring faults and performance on the router

Support for SNMP versions (SNMPv1, SNMPv2c, and SNMPv3)

Notification of faults, alarms, and conditions that can affect services

For a complete list of changes to the Cisco CMTS Universal Broadband Router MIB Specifications Guide, go to the Revision History table:

http://www.cisco.com/en/US/docs/cable/cmts/mib/reference/guide/mibv5ubr.html

Important Notes

The following sections contain important notes about Cisco IOS Release 12.3(23)BC7 that apply to the Cisco uBR10012 universal broadband router universal broadband router.

How to Upgrade to Cisco IOS Release 12.3(21)BC

In circumstances in which non-volatile memory (NVRAM) becomes corrupted on the Cisco CMTS, configurations and feature behavior may become corrupted or lost, looping behavior in NVRAM may result, and additional measures to resolve corrupted NVRAM and lost configurations would be required.

This issue can be generated by upgrading to later Cisco IOS releases from prior Cisco IOS releases that do not contain resolution to a specific and known issue. This issue is not limited to Cisco IOS releases installed on the Cisco universal broadband routers.

Symptoms of Corrupted NVRAM

This issue is displayed with the following symptoms in the case of the Cisco CMTS:

A router may display the following error message:

NV: Invalid Pointer value(6357F3CC) in private configuration structure

This error message is displayed either when the router boots, or when you enter one of the following commands:

write memory

copy running-config startup-config

copy file

nvram:startup-config

Conditions of Corrupted NVRAM

This symptom is observed under the following conditions:

The Cisco router runs one of the following Cisco IOS Releases, as the outgoing image to be upgraded:

Interim Cisco IOS Release 12.3(19.7)

Interim Cisco IOS Release 12.4(6.5)

Interim Cisco IOS Release 12.4(6.5)T

Certain later releases

When upgrading to Cisco IOS Release 12.3(21)BC, the following upgrade procedure prevents corruption to NVRAM, retains configurations made in earlier releases, and successfully installs Cisco IOS Release 12.3(21)BC images. This procedure is subject to the feature restrictions and prerequisites of Cisco IOS Release 12.3(21)BC, described in these release notes.

Prerequisites

Cisco strongly recommends that you back up your configuration files prior to performing this upgrade, or any upgrade.

SUMMARY STEPS

Perform these steps to upgrade to Cisco IOS 12.3(21)BC, after TFTP file transfer operations are complete.

1. enable

2. configure terminal

3. erase /all nvram:

4. write memory

5. copy file

6. reload

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 

erase /all nvram:

or

erase nvram:

or

write erase

Example:

Router# erase /all nvram:

The first command option for this step erases the entire NVRAM.

Either of the final two command options erase only the configuration files in NVRAM.

Step 4 

write memory

Example:

Router# write memory

(Optional) Copies the running configuration to startup configuration.

Step 5 

copy file

Example:

Router# copy <saved-config> startup-config

(Optional) Copies a saved configuration, if different from the running configuration, to the startup configuration.

file—saved configuration file to be copied to the startup configuration

Step 6 

reload

Example:

Router# reload

Boots the router with the latest Cisco IOS release image.

New Command Information for Cisco IOS Release 12.3(21)BC

Cisco IOS Release 12.3(21)BC introduces support and modifications to the following commands for Cisco Cable Modem Termination System (CMTS) universal broadband routers.

Refer to the following sections for more information:

cable throttle-ranging

card

clear cable modem reset

hw-module reload

hw-module shutdown

show cable modem summary

show cable modem wideband

show interface wideband-cable

cable throttle-ranging

To enable faster cable modem registration times, use the cable throttle-ranging command in global configuration mode. To disable faster cable modem registration times, use the no form of this command.

cable throttle-ranging

no cable throttle-ranging

Syntax Description

This command has no arguments or keywords

Defaults

This command is disabled by default.

Command Modes

Global configuration

Command History

Release
Modification

12.3(21)BC

This command was introduced.

Usage Guidelines

The cable throttle-ranging command enables faster cable modem registration times on the CMTS.

Reload the Cisco CMTS with a Cisco IOS Release  12.3(21)BC image and configure the cable throttle-ranging command on the CMTS. Once the cable throttle-ranging has been configured, save the new configuration and reload the Cisco CMTS again. Faster cable modem registration times will now be enabled on the Cisco CMTS.


Note The cable throttle-ranging command is only available on an ubr10k CMTS.


Examples

The following example shows how to enable Fast CM registration feature on a Cisco CMTS:

Router# cable throttle-ranging

Router(config)#

Related Commands

There are no related commands for this command.

card

To preprovision a slot in the Cisco uBR10012 universal broadband router for a particular interface card, so that you can configure the interface without it being physically present in the slot, use the card command in global configuration mode. To remove the preprovisioning for a card, so that the physical slot reports being empty, use the no form of this command.

card {slot/subslot | slot/subslot/bay} card-type

no card {slot/subslot | slot/subslot/bay}

Syntax Description

slot/subslot

Identifies the chassis slot and subslot for the card. The following are the valid values:

slot = 1 to 8

subslot = 0 or 1

slot/subslot/bay

Identifies the chassis slot and subslot for the Cisco Wideband SIP, and the bay number in the SIP where the Cisco Wideband SPA is located. The following are the valid values:

slot = 1 to 3

subslot = 0 or 1 (0 is always specified)

bay = 0 (upper bay) or 1 (lower bay)

card-type

Specifies the type of card that should be used to preprovision the slot. See Table 12 for a list of the supported cards.



Note The list of supported card types depends on the Cisco IOS software release being used. See the release notes for your release for the complete list of cards that are supported.


Defaults

An empty card slot is not preprovisioned and cannot be configured or displayed.

Command Modes

Global configuration

Command History

Release
Modification

12.2(1)XF1

This command was introduced for the Cisco uBR10012 router, and for the following line cards:

Cisco uBR-LCP-MC28C cable interface line card

Cisco uBR-LCP-MC28C-BNC cable interface line card

Cisco uBR10-1GE Gigabit Ethernet (GigE) uplink line card

Cisco uBR10-1OC12/P-SMI OC-12 POS uplink line card

12.2(4)XF1

Support was added for the Cisco uBR-LCP-MC16C and Cisco uBR-LCP-MC16E cable interface line cards.

12.2(4)BC1

Support was added for the Cisco uBR10-SRP-OC12SML DPT WAN uplink line card.

12.2(8)BC1

Support was added for the Cisco LCP2 line card processor, and all of its combinations with the supported cable interface line cards.

12.2(11)BC3

Support was added for the Cisco uBR10012 OC-48 DPT/POS Interface Module uplink line card and Cisco uBR-MC5X20S cable interface line card.

12.2(15)CX1

Support was added for the Cisco uBR-MC16U/X and Cisco uBR-MC28U/X cable interface line cards.

12.2(15)BC2

Support was added for the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR-MC5X20U cable interface line cards.

12.3(21)BC

Support was added for the Cisco Wideband SIP and Wideband SPA.


Usage Guidelines

This command preprovisions a slot in the Cisco uBR10012 router to accept a particular line card, so that you can configure the interface without the card being physically present in the chassis. This command allows system administrators to plan for future configurations, without having to wait for the physical hardware to first arrive. When the line card does arrive, the installer can bring the card online by inserting the card into the chassis and connecting the necessary cables, without having to do any further configuration using the command-line interface.

The type of card must be appropriate for the slot being specified. Slots 1/1 and 2/1 are reserved for TCC+ utility cards. Slots 1/0 through 4/0 are reserved for network uplink line cards. Slot 5/0 through 8/1 are reserved for cable interface line cards. Slot 0/0 is reserved for the FastEthernet interface on the PRE1 module and cannot be specified in this command.

Table 12 lists the types of cards that are supported as card-types for the card command:

Table 12 Card Types Supported by the card Command 

Card Type
Description

1cable-mc16c

Preprovisions a slot for a Cisco uBR-LCP-MC16C or Cisco uBR-LCP2-MC16C cable interface line card.

1cable-mc16e

Preprovisions a slot for a Cisco uBR-LCP-MC16E or Cisco uBR-LCP2-MC16E cable interface line card.

1cable-mc16s

Preprovisions a slot for a Cisco uBR-LCP-MC16S or Cisco uBR-LCP2-MC16S cable interface line card.

1gigethernet-1

Preprovisions a slot for a Cisco uBR10-1GE Gigabit Ethernet (GigE) uplink line card.

1oc12pos-1

Preprovisions a slot for a Cisco uBR10-1OC12/P-SMI OC-12 POS uplink line card.

1oc48dpt-pos-1

Preprovisions a slot for a Cisco uBR10012 OC-48 DPT/POS Interface Module uplink line card.

24rfchannel-spa-1

Preprovisions a bay in the Cisco Wideband SIP for the Cisco 1-Gbps Wideband Shared Port Adapter (SPA).

2cable-mc28bnc

Preprovisions a slot for a Cisco uBR-LCP-MC28C-BNC or Cisco uBR-LCP2-MC28C-BNC cable interface line card.

2cable-mc28c

Preprovisions a slot for a Cisco uBR-LCP-MC28C or Cisco uBR-LCP2-MC28C cable interface line card.

2cable-tccplus

Preprovisions a slot for a Timing, Control, and Communications Plus (TCC+) utility card.

Note This option is informational only, because slots 1/1 and 2/1 can be used only for the TCC+ card.

2jacket-1

Preprovisions a slot for the Cisco Wideband SPA Interface Processor (SIP).

2oc12srp-sm-lr

Preprovisions a slot for a Cisco uBR10-SRP-OC12SML DPT WAN uplink line card.

5cable-mc520s-d

Preprovisions a slot for a Cisco uBR10-MC5X20S-D cable interface line card.

5cable-mc520u-d

Preprovisions a slot for a Cisco uBR10-MC5X20U-D cable interface line card.



Tip When a card has been preprovisioned and is not physically present in the chassis, the show interface command for that slot displays the message "Hardware is not present." Some show commands might also list the preprovisioned card in their displays. In addition, using the card command does not change the output of the ENTITY-MIB, which shows only the equipment that is physically installed in the router.


When a line card is inserted in the Cisco uBR10012 chassis, the router performs the following actions, depending on whether the card slot is preprovisioned for the card:

If the inserted line card matches the type of line card preprovisioned for the slot, the system applies the preprovisioned configuration to the line card.

If the line card slot was not preprovisioned, the system applies a basic configuration to the line card and adds that configuration to the running configuration file.

If the line card slot was preprovisioned for one type of line card, but another type of line card has been inserted, the system replaces the preprovisioned configuration (in the running configuration file) with a basic configuration for the line card that was actually inserted. The startup configuration file is not changed.


Tip Use the show running-config | include card command to display which slots, if any, are preprovisioned for a particular card type.


The no card version of the command removes the preprovisioning information from the given card slot. This also removes all configuration information for that card slot, as well as any information in the SNMP MIB database about the card and its card slot.

Examples

The following example shows a list of supported card types for Cisco IOS Release 12.2(8)BC1, and then shows that slot 8/0 is being preprovisioned for a Cisco uBR-LCP2-MC28C cable interface line card. The cable interface for slot 8/0 can then be configured.

Router# config t 
Router(config)# card 5/0 ? 
  1cable-mc16c    create a uBR10000 line card with MC16C
  1cable-mc16e    create a uBR10000 line card with MC16E
  1gigethernet-1  create a GE_1_PORT cardtype
  1oc12pos-1      create a OC12POS_1_PORT cardtype
  2cable-mc28bnc  create a uBR10000 line card with MC28C, BNC connector
  2cable-mc28c    create a uBR10000 line card with MC28C
  2oc12srp-sm-lr  create a uBR10000 oc12 SRP card with SM LR 
Router(config)# card 8/0 2cable-mc28c 
Router(config)# int c8/0 
Router(config-if)# 
 
   

The following example shows the output from the show interface command for a preprovisioned cable interface. The second line of the output shows that the hardware is not present.

Router# show interface c8/0/0 
Cable8/0/0 is initializing, line protocol is down 
  Hardware is not present
  Hardware is UBR10000 CLC, address is 0001.6440.d160 (bia 0001.6440.d160)
  MTU 1500 bytes, BW 27000 Kbit, DLY 1000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation MCNS, loopback not set
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output never, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue :0/40 (size/max)
  5 minute input rate 0 bits/sec, 0 packets/sec
  5 minute output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     0 packets output, 0 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
Router# 
 
   

The following examples show the two steps required to preprovision the Wideband SIP and Wideband SPA.

The Wideband SIP is preprovisioned with the card command and 2jacket-1 as the card type. For example:

Router# configure terminal
Router(config)# card 1/0 2jacket-1
Router(config)#
 
   

The Wideband SPA is preprovisioned with the card command and 24rfchannel-spa-1 as the card type. For example:

Router# configure terminal
Router(config)# card 1/0/0 24rfchannel-spa-1
Router(config)# 
 
   

The preceding card command creates 12 wideband channels on the Wideband SPA.

Related Commands

Command
Description

show interface cable

Displays the current configuration and status of a cable interface.


clear cable modem reset

To remove one or more CMs from the Station Maintenance List and reset them, use the clear cable modem reset command in privileged EXEC mode.

clear cable modem {mac-addr | ip-addr | [cable slot/port] {all | oui string | reject} } reset

clear cable modem {mac-addr | ip-addr | [cable slot/subslot/port] {all | oui string | reject | wideband registered-traditional-docsis} } reset

Syntax Description

mac-addr

Specifies the 48-bit hardware address (MAC address) of an individual CM, or of any CPE devices or hosts behind that CM.

ip-addr

Specifies the IP address of an individual CM, or of any CPE devices or hosts behind that CM.

cable slot/port

(Optional) Identifies the a interface and downstream port on the Cisco uBR7100 series and Cisco uBR7200 series routers.

On the Cisco uBR7100 series router, the only valid value is 1/0. On the Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0 or 1, depending on the cable interface.

cable slot/subslot/port

(Optional) Identifies a cable interface on the Cisco uBR10012 router. The following are the valid values:

slot = 5 to 8

subslot = 0 or 1

port = 0 to 4 (depending on the cable interface)

all

Removes all the CMs from the Station Maintenance List. (This option is valid only on the Release 12.1 EC train.)

oui string

Removes and resets all CMs that match the specified Organization Unique Identifier (OUI). The string parameter can be either the three byte hexadecimal string (such as 00.00.0C) or a vendor name that has been defined using the cable modem vendor command.

reject

Removes and resets all CMs that are currently in one of the reject states (see the description of these states in the show cable modem command).

wideband registered-traditional-docsis

If you specify wideband, removes and resets all wideband CMs. If you specify wideband registered-traditional-docsis, removes and resets all wideband CMs that are registered as traditional DOCSIS modems.


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.1(2) EC

This command was introduced.

12.2(4)BC1

Support was added to the Release 12.2 BC train.

12.2(11)BC2

Support was added for the oui and reject options.

12.2(11)BC3

The all option was removed from the Release 12.2 BC train, and replaced with the interface option.

12.2(15)BC1

The cable interface was made an optional keyword for this command.

12.3(21)BC

Support was added for the wideband and registered-traditional-docsis keywords.


Usage Guidelines

This command instructs the Cisco CMTS to stop sending DOCSIS station maintenance messages to one or more CMs, which effectively terminates the link to those CMs. A CM responds to this by resetting itself. Depending on when the CM received the last station maintenance message, it can take up to 30 seconds before the CM detects the missing station maintenance messages and resets itself.

In some circumstances, the customer premises equipment (CPE) devices behind a CM stops receiving traffic after the CM is reset. This is because the CMTS still has the CPE device listed in its address tables, but the CM does not after being reset, so the traffic passes through the CMTS but is dropped by the CM. To resolve this situation, the CPE device should simply send some type of traffic to the CM, such as a ping packet. (You can also resolve this situation by using the clear arp-cache command on the Cisco CMTS router to clear the router's address table, but this is not recommended, because it temporarily interrupts all traffic on the router.)


Note The clear cable modem all reset command can result in the CPU utilization temporarily reaching 100 percent for a couple of minutes, as the CPU processes the command for all CMs. The CPU utilization will return to normal within a couple of minutes.



Caution The clear cable modem all reset command should normally be used only on a test or lab network. If used on a large network, it could impact service for a significant period of time, as it would force all CMs to simultaneously reset and reregister with the Cisco CMTS.


Tip You can also specify the MAC address or IP address for a CPE device or host, and the Cisco CMTS resets the CM that is associated with that CPE device in its internal database.


Examples

The following example shows how to reset the CM at 172.23.45.67:

Router# clear cable modem 172.23.45.67 reset
Router#
 
   

The following example shows how to reset all CMs that have a OUI that has been defined as having the vendor name of Cisco using the cable modem vendor command:

Router# clear cable modem oui Cisco reset
Router#
 
   

The following example shows how to reset all CMs that are currently in one of the reject states:

Router# clear cable modem reject reset
Router#
 
   

The following example shows how to reset all wideband CMs that are registered as traditional DOCSIS modems.:

Router# clear cable modem wideband registered-traditional-docsis reset
MAC Address    IP Address      I/F       MAC            Prim  BG  DSID  MD-DS-SG
                                         State          Sid   ID
0018.6852.825c 80.18.0.9       C5/0/0/U0 online         1     0   256   N/A
0018.6852.8286 80.18.0.10      C5/0/0/U0 online         2     0   264   N/A
0016.92fb.55be 80.18.0.7       C5/0/0/U0 online         3     0   288   N/A
0016.92f0.9104 80.18.0.5       C5/0/0/U0 online         4     0   280   N/A
0016.92fb.55c0 80.18.0.6       C5/0/0/U0 online         5     0   272   N/A
 
   

Router#

Related Commands

Command
Description

clear cable flap-list

Resets the flap-list table for a specific CM or for all CMs.

clear cable modem counters

Resets the flapping counters of a CM to zero.

clear cable modem delete

Removes one or more CMs from the internal address and routing tables.

clear cable modem lock

Resets the lock on one or more CMs.

clear cable modem offline

Removes all offline CMs from the internal address and routing tables, or clears all flap list counters for offline CMs.

show cable modem

Displays the current status for one or more CMs.


hw-module reload

To reload the software in and restart a Cisco 1-Gbps Wideband SPA, use the hw-module reload command in privileged EXEC mode.

hw-module bay slot/subslot/bay reload

Syntax Description

bay slot/subslot/bay

Reloads the SPA in the location specified by the slot/subslot/bay argument. The following are the valid values:

slot = 1 to 3

subslot = 0 or 1 (0 is always specified)

bay = 0 (upper bay) or 1 (lower bay)


Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(21)BC

This command was introduced for the Cisco uBR10012 universal broadband router.


Usage Guidelines

The hw-module reload command reloads the software in and restarts a Cisco 1-Gbps Wideband SPA.

Examples

The following example shows reloads the Cisco Wideband SPA in slot 1, subslot 0, bay 1.

Router# hw-module bay 1/0/1 reload 
Router#

Related Commands

Command
Description

hw-module shutdown

Shuts down a PRE1 module, line card, SIP, or SPA.


hw-module shutdown

To shut down a particular Performance Routing Engine (PRE1) module, line card, Wideband SIP or Wideband SPA, use the hw-module shutdown command in global configuration mode. To activate a specific PRE1, line card, Wideband SIP or Wideband SPA, use the no form of this command.

hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/subslot |
bay slot/subslot/bay} shutdown [unpowered]

no hw-module {main-cpu | pre {A|B} | sec-cpu | slot slot-number | subslot slot/subslot |
bay slot/subslot/bay} shutdown

Syntax Description

main-cpu

Shuts down the PRE1 module that is currently acting as the active PRE1 module.

pre {A|B}

Shuts down the PRE1 module that is physically in either PRE slot A (left slot) or PRE slot B (right slot).

sec-cpu

Shuts down the PRE1 module that is currently acting as the standby PRE1 module.

slot slot-number

Shuts down the line cards that are physically present in the specified slot-number (valid range is 1 to 8).

subslot slot/subslot

Shuts down the line card or SIP that is physically present in the slot with the specified slot and subslot numbers. The following are the valid values:

slot = 1 to 8

subslot = 0 or 1

bay slot/subslot/bay

Shuts down the SPA in the location specified by the slot/subslot/bay argument. The following are the valid values:

slot = 1 to 3

subslot = 0 or 1 (0 is always specified)

bay = 0 (upper bay) or 1 (lower bay)

unpowered

Used with the Wideband SPA, shuts down the SPA and its interfaces, and leaves them in an administratively down state without power.


Defaults

No default behavior or values

Command Modes

Global configuration

Command History

Release
Modification

12.2(4)XF

This command was introduced for the Cisco uBR10012 router.

12.3(21)BC

Support was added for the Cisco Wideband SIP and Cisco 1-Gbps Wideband SPA.


Usage Guidelines

The hw-module shutdown command shuts down a particular Performance Routing Engine (PRE1) module, line card, Wideband SIP or Wideband SPA. To activate a specific PRE1, line card, Wideband SIP, or Wideband SPA, use the no form of this command.


Caution Shutting down the active PRE1 module will trigger a switchover, so that the standby PRE1 module becomes the active PRE1 module.

Examples

The following example shows the standby PRE1 module being shut down:

Router(config)# hw-module sec-cpu shutdown 
Router(config)#
 
   

The following example shows the active PRE1 module being shut down (which will trigger a switchover to the standby PRE1 module):

Router(config)# hw-module main-cpu shutdown 
Router(config)# 
 
   

The following example shows the PRE1 module in PRE1 slot B being shut down:

Router(config)# hw-module pre B shutdown 
Router(config)# 

Note The hw-module pre B shutdown command shuts down the PRE1 module that is physically present in slot B, regardless of whether the module is the active or standby PRE1 module.


The following example shows how to deactivate and verify deactivation for the Cisco Wideband SPA located in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the "admin down" in the Operational Status field.

Router# configure terminal
Router(config)# hw-module bay 1/0/0 shutdown unpowered
%SPAWBCMTS-4-SFP_MISSING: Wideband-Cable 1/0/0, 1000BASE-SX SFP missing from port 0
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:1, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:2, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:3, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:4, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:5, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:6, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:7, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:8, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:9, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:10, changed state to down
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:11, changed state to down
...
Router# show hw-module bay 1/0/0 oir
 
   
Module         Model              Operational Status
-------------- ------------------ -------------------------
bay 1/0/0      SPA-24XDS-SFP      admin down
 
   

The following example shows how to activate and verify activation for the Cisco Wideband SPA located in slot 1, subslot 0, bay 0. In the output of the show hw-module bay oir command, notice the "ok" in the Operational Status field.

Router# configure terminal
Router(config)# no hw-module bay 1/0/0 shutdown
%SPAWBCMTS-4-SFP_OK: Wideband-Cable 1/0/0, 1000BASE-SX SFP inserted in port 0
%SPAWBCMTS-4-SFP_LINK_OK: Wideband-Cable 1/0/0, port 0 link changed state to up
%SNMP-5-LINK_UP: LinkUp:Interface Wideband-Cable1/0/0:0 changed state to up
%LINK-3-UPDOWN: Interface Cable1/0/0:0, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:1, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:2, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:3, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:4, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:5, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:6, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:7, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:8, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:9, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:10, changed state to up
%LINK-3-UPDOWN: Interface Wideband-Cable1/0/0:11, changed state to up
%LINEPROTO-5-UPDOWN: Line protocol on Interface Wideband-Cable1/0/0:0, changed state to up
...
Router# show hw-module bay 1/0/0 oir
 
   
Module         Model              Operational Status
-------------- ------------------ -------------------------
bay 1/0/0      SPA-24XDS-SFP      ok
 
   

Related Commands

Command
Description

hw-module reset

Resets a PRE1 module or line card.

hw-module-reload

Reloads the software in and restarts a Cisco 1-Gbps Wideband SPA.

redundancy force-failover main-cpu

Forces a manual switchover between the active and standby PRE1 modules.


show cable modem summary

To display a summary of CMs on one or more cable interfaces, use the show cable modem command in privileged EXEC mode.

show cable modem summary [total]

show cable modem summary interface1 [interface2] total

show cable modem summary interface1 [interface2] upstream port1 port2 total

show cable modem cable slot/port [upstream port] summary

show cable modem cable slot/subslot/port [upstream port] summary

Syntax Description

total

(Optional) Displays a footer line showing the totals for each column.

interface1

(Optional) Cable interface to be summarized. The interface1 parameter can take the following forms:

cable slot/port—On the Cisco uBR7100 series router, the only valid value is 1/0. On the Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0 or 1, depending on the cable interface.

cable slot/subslot/port—On the Cisco uBR10012 router, slot can range from 5 to 8, subslot can be either 0 or 1, and port can range from 0 to 4 (depending on the interface).

interface2

(Optional) Second cable interface, specifying a range of cable interfaces to be summarized. The interface2 parameter has the same form as interface1.

Note When specifying a range of cable interfaces, interface1 must be the lower-numbered interface and interface2 must be the higher-numbered interface.

upstream port1 port2

(Optional) Specifies a range of upstream ports on the cable interfaces to be summarized. The port1 and port2 parameters can start at 0, and port2 must be a higher-numbered port than port1.

upstream port

(Optional) Specifies a specific upstream port to be summarized. This option can be specified only when summarizing a single cable interface.


Command Modes

Privileged EXEC

Command History

Release
Modification

11.3XA

This command was introduced.

12.1(4)CX and 12.2(4)BC1

Support was added for the Cisco uBR10012 router.

12.1(6)EC

The total option was supported for the Cisco uBR7100 series and Cisco uBR7200 series routers.

12.1(11b)EC

The upstream Description field was added to the show cable modem summary display in Cisco IOS Release 12.1 EC.

12.2(8)BC1

The total option was supported for the Cisco uBR10012 universal broadband router.

12.2(15)BC2

The upstream Description field was added to the show cable modem summary display in Cisco IOS Release 12.2 BC.

12.3(21)BC

Support was added for wideband modem output.


Usage Guidelines

This command displays a summary of CMs for a single cable interface or upstream, or for a range of cable interfaces or upstreams. The following possible combinations are possible for this command:

show cable modem summary total—Displays a summary and a total for all CMs on the chassis.

show cable modem summary cable x/0 total—Displays a summary of CMs on a specified card.

show cable modem summary cable x/0 upstream port1 port2 total—Displays a summary of CMs on the specified card and specified range of ports. The port1 value must be less than the port2 value.

show cable modem summary cable x/0 cable y/0 total—Displays a summary of CMs on the specified range of cards.

show cable modem summary cable x/0 cable y/0 upstream port1 port2 total—Displays a summary of CMs on the specified range of ports on the specified range of cards.


Note Also see the information about this command's behavior in a Hot Standby Connection-to-Connection Protocol (HCCP) configuration, see the "Operation with Hot Standby Connection-to-Connection Protocol (HCCP) Configuration" section on page 3-63.


Examples

The following example shows typical output for the default form of the show cable modem summary command on a Cisco uBR7200 series router:

Router# show cable modem summary 
 
   
Interface     Total      Active      Registered   Description 
              Modems     Modems      Modems
Cable3/0/U0   165         141         141         Line 32/1
Cable3/0/U1   209         172         170         Line 32/2
Cable3/0/U2   262         207         203         Line 32/3
Cable3/0/U3   256         194         188         Line 32/4
Cable5/0/U0   746         714         711         Line 41/1
Cable6/0/U0   806         764         759         Line 42/2
 
   
Router# 

Note The Description field appears in Cisco IOS Release 12.1(11b)EC, 12.2(15)BC2, and later releases, and shows the string configured for the upstream using the cable upstream description command.


The following example shows typical output for the show cable modem summary command with the total option on a Cisco uBR7200 series router:

Router# show cable modem summary total 
 
   
Interface     Total      Active      Registered   Description 
              Modems     Modems      Modems
Cable5/0/U0     746        714         711        Node1 
Cable6/0/U1     806        764         759        Node3
 
   
Total:         1552       1478        1470
 
   
Router# 
 
   

The following example shows sample output for the show cable modem summary command with the total option for a Cisco uBR10012 router:

Router# show cable modem summary total
Interface                       Cable Modem                    Description
            Total Reg   Unreg Offline Wideband initRC initD initIO initO
C5/0/0/U0   84    84    0     0       84       0      0     0      0     
C5/0/0/U1   84    84    0     0       84       0      0     0      0     
C5/0/0/U2   83    83    0     0       83       0      0     0      0     
C5/0/0/U3   83    83    0     0       83       0      0     0      0     
<<output omitted>>
 
   
Total:      8020  8020  0     0       8016     0      0     0      0 
 
   
Router# 
 
   

The following example shows sample output for the show cable modem summary total command for a range of interfaces on the Cisco uBR10012 router:

Router# show cable modem summary c5/1/1 c5/1/2 total
Interface                       Cable Modem                    Description
            Total Reg   Unreg Offline Wideband initRC initD initIO initO
C5/1/1/U0   84    84    0     0       84       0      0     0      0     
C5/1/1/U1   84    84    0     0       83       0      0     0      0     
C5/1/1/U2   83    83    0     0       83       0      0     0      0     
C5/1/1/U3   83    83    0     0       83       0      0     0      0     
C5/1/2/U0   84    84    0     0       84       0      0     0      0     
C5/1/2/U1   84    84    0     0       84       0      0     0      0     
C5/1/2/U2   83    83    0     0       83       0      0     0      0     
C5/1/2/U3   83    83    0     0       83       0      0     0      0     
 
   
Total:      668   668   0     0       667      0      0     0      0     
 
   
Router# 
 
   

The following example shows sample output for the show cable modem summary total command for a range of interfaces and upstreams on the Cisco uBR10012 router:

Router# show cable modem summary c5/1/1 c5/1/2 upstream 0 1 total
Interface                       Cable Modem                    Description
            Total Reg   Unreg Offline Wideband initRC initD initIO initO
C5/1/1/U0   84    84    0     0       84       0      0     0      0     
C5/1/1/U1   84    84    0     0       83       0      0     0      0     
C5/1/2/U0   84    84    0     0       84       0      0     0      0     
C5/1/2/U1   84    84    0     0       84       0      0     0      0     
 
   
Total:      336   336   0     0       335      0      0     0      0     
 
   
 
   
Router# 
 
   

Note When displaying a summary for a range of ports or cable interfaces, the first port or cable interface (for example, u0 or c4/0) must be lower-numbered than the second port or interface (for example, u6 or c6/0). If you specify the higher-numbered port or interface first, the display shows no CMs connected.


Table 13 describes the fields shown in the show cable modem summary displays:

Table 13 Descriptions for the show cable modem summary Fields 

Field
Description

Interface

The cable interface line card providing the upstream for the CMs.

Total Modems or Total

Total number of CMs, registered, unregistered, and offline for this interface.

Registered Modems or Reg

Total number of CMs that have registered and are online on this interface. This number might be different from the Total Modems number if some modems are offline or not fully registered.

Unregistered Modems

Total number of CMs that are either offline and not currently communicating with the CMTS, or attempting to come online but are not yet registered.

Offline

Total number of CMs that were online or attempted to register but are no longer communicating with the CMTS.

Wideband

CM is registered as a wideband CM.

init(rc)

MAC state of CM is init(rc).

init(d)

MAC state of CM is init(d).

init(io)

MAC state of CM is init(io).

init(o)

MAC state of CM is init(o).

Description

Description entered for this upstream using the cable upstream description command.



Note For information on MAC states, see the show cable modem command.



Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to show commands using the exec prompt timestamp command in line configuration mode.


Related Commands

Command
Description

show cable modem

Displays information for the registered and unregistered CMs.

show cable modem access-group

Displays the access groups for the CMs on a particular cable interface.

show cable modem calls

Displays voice call information for a particular CM, identified either by its IP address or MAC address.

show cable modem connectivity

Displays connectivity statistics for one or more CMs.

show cable modem counters

Displays downstream and upstream traffic counters for one or more CMs.

show cable modem cpe

Displays the CPE devices accessing the cable interface through a particular CM.

show cable modem offline

Displays a list of the CMs that are marked as offline with the Cisco CMTS.

show cable modem registered

Displays a list of the CMs that are marked as registered with the Cisco CMTS.

show cable modem remote-query

Displays information collected by the remote-query feature.

show cable modem unregistered

Displays a list of the CMs that are marked as unregistered with the Cisco CMTS.

show cable modem vendor

Displays the vendor name or Organizational Unique Identifier (OUI) for the CMs on each cable interface.

show interface cable modem

Displays information about the CMs connected to a particular cable interface.

show interface cable sid

Displays cable interface information.

show cable modem wideband

Displays information for a wideband CMs.


show cable modem wideband

To display information for registered and unregistered wideband CMs, use the show cable modem wideband command in privileged EXEC mode.

show cable modem wideband [registered-traditional-docsis]

show cable modem [ip-address | mac-address | cable slot/subslot/port] wideband

Syntax Description

ip-address

(Optional) Identifies the IP address of a specific wideband CM to be displayed. If you specify the IP address for a CPE device behind a CM, information for that CM is displayed.

mac-address

(Optional) Identifies the MAC address of a specific wideband CM to be displayed. You can also specify the MAC address for a CPE device behind a wideband CM, and information for that wideband CM will be displayed.

cable slot/subslot/port

(Optional) Identifies a cable interface on the Cisco uBR10012 router. The following are the valid values:

slot = 5 to 8

subslot = 0 or 1

port = 0 to 4 (depending on the cable interface)

registered-traditional-docsis

(Optional) Displays information for wideband CMs that are currently registered as traditional DOCSIS modems.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(21)BC

This command was introduced for the Cisco uBR10012 universal broadband router.


Usage Guidelines

This command displays information for a one or more wideband CMs. Optionally, the CMs for which to display information can be identified IP address, MAC address, or cable interface.

If a wideband-capable CM is not able to register as a wideband CM (for example, if no wideband channel is available), the CM attempts to register as a traditional DOCSIS modem. The registered-traditional-docsis keyword limits the set of wideband CMs for which to display information to wideband-capable CMs that are currently registered as DOCSIS 1.X or DOCSIS 2.0 modems.

Examples

The following example shows typical output for the default form of the show cable modem wideband command on a Cisco uBR10012 router:

Router# show cable modem wideband                                              
MAC Address    IP Address      I/F       MAC          Prim  BG	DSID MD-DS-SG
                                         State        Sid   ID 
0014.bfbe.3cc0 1.11.0.1        C5/0/1/U0 w-online(pt)  3    24     24   N/A     
0016.92f0.90d6 1.11.0.4        C5/0/1/U0 w-online(pt)  5    24     272  1       
0014.bfbe.3cb8 1.11.0.2        C6/0/1/U0 w-online(pt)  3    36     36   N/A     
0016.92f0.90d8 1.11.0.3        C6/0/1/U0 w-online(pt)  5    36     274  1
 
   
Router#
 
   

Table 14 describes the fields that are shown in the show cable modem wideband display:

Table 14 Descriptions for the show cable modem wideband Fields 

Field
Description

MAC Address

The MAC address for the CM.

IP Address

The IP address that the DHCP server has assigned to the CM.

I/F

The cable interface providing the upstream for this CM.

MAC State

The current state of the MAC layer.

Prim SID

The primary SID assigned to this CM.

Bonding Group ID

The identifier of the primary wideband channel.

DSID

The Downstream Service Identifier.

MD-DS-SG

The MAC Domain Downstream Service Group, the downstream channels of a single MAC domain that reach the cable modem.


Table 15 shows the possible values for the MAC State field for a wideband CM modem that registers as a traditional DOCSIS modem:

Table 15 Descriptions for the MAC State Field (for Traditional DOCSIS Modems) 1  

MAC State Value
Description
Registration and Provisioning Status Conditions

init(r1)

The CM sent initial ranging.

init(r2)

The CM is ranging. The CMTS received initial ranging from the CM and has sent RF power, timing offset, and frequency adjustments to the CM.

init(rc)

Ranging has completed.

Note If a CM appears to be stuck in this state, it could be that the CM is able to communicate successfully on the cable network, but that the upstream is at capacity and does not have any additional bandwidth to allow the CM to finish registration and come online. Either manually move one or more CMs to other upstreams, or enable load balancing on the upstream using the cable load-balance group commands.

init(d)

The DHCP request was received, as DHCPDISCOVER. This also indicates that the first IP broadcast packet has been received from the CM.

init(dr)

The DHCP request has been sent to the cable modem.

init(i)

The cable modem has received the DHCPOFFER reply (DHCPACK) from the DHCP server that has assigned an IP address to the modem, but the modem has not yet replied with a DHCPREQUEST message requesting that particular IP address, nor has it sent an IP packet with that IP address.

Note If a CM appears to be stuck in this state, the CM has likely received the DHCPOFFER reply from the DHCP server, but this reply might have contained one or more invalid options for that particular CM.

init(io)

The Cisco CMTS has seen the DHCP offer as sent to the cable modem from the DHCP server that has assigned an IP address to the modem.

init(o)

The CM has begun to download the option file (DOCSIS configuration file) using the Trivial File Transfer Protocol (TFTP), as specified in the DHCP response. If the CM remains in this state, it indicates that the download has failed.

init(t)

Time-of-day (TOD) exchange has started.

resetting

The CM is being reset and will shortly restart the registration process.

Non-error Status Conditions

cc(r1)

The CM had registered and was online, but has received a Downstream Channel Change (DCC) or Upstream Channel Change (UCC) request message from the CMTS. The CM has begun moving to the new channel, and the CMTS has received the CM's initial ranging on the new downstream or upstream channel. At the MAC layer, the CM is considered offline because it is not yet passing traffic on the new channel, but this state does not trigger the flap-list counters.

cc(r2)

This state should normally follow cc(r1) and indicates that the CM has finished its initial ranging on the new channel, and is currently performing continuous ranging on the new channel. At the MAC layer, the CM is considered offline because it is not yet passing traffic on the new channel, but this state does not trigger the flap-list counters.

offline

The CM is considered offline (disconnected or powered down).

online

The CM has registered and is enabled to pass data on the network.

online(d)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. The CM does not forward traffic to or from the CPE devices, but the CMTS can continue to communicate with the CM using DOCSIS messages and IP traffic (such as SNMP commands).

Note If BPI was enabled in the DOCSIS configuration file sent to the CM, assume that the CM is using BPI encryption, unless other messages show that the BPI negotiation and key assignments have failed.

online(pkd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and KEK is assigned.

Note This state is equivalent to the online(d) and online(pk) states.

online(ptd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and TEK is assigned. BPI encryption is now being performed.

Note This state is equivalent to the online(d) and online(pt) states.

online(pk)

The CM registered, BPI is enabled and KEK is assigned.

online(pt)

The CM registered, BPI is enabled and TEK is assigned. BPI encryption is now being performed.

Note If network access was disabled in the DOCSIS configuration file sent to the CM, the network disabled status takes precedence, and the MAC status field shows online(d) instead of online(pt) even when BPI encryption is enabled and operational.

Note If an exclamation point (!) appears in front of one of the online states, it indicates that the cable dynamic-secret command has been used with either the mark or reject option, and that the cable modem has failed the dynamic secret authentication check.

expire(pk)

The CM registered, BPI is enabled, KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value.

expire(pkd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value.

Note This state is equivalent to the online(d) and expire(pk) states.

expire(pt)

The CM registered, BPI is enabled, TEK was assigned, but the current TEK expired before the CM could successfully renew a new KEK value.

expire(ptd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, TEK was assigned, but the current TEK expired before the CM could successfully renew a new KEK value.

Note This state is equivalent to the online(d) and expire(pt) states.

Error Status Conditions

reject(m)

The CM attempted to register but registration was refused due to a bad Message Integrity Check (MIC) value. This also could indicate that the shared secret in the DOCSIS configuration file does not match the value configured on the CMTS with the cable shared-secret command.

In Cisco IOS Release 12.1(11b)EC1 and Cisco IOS Release 12.2(8)BC2 or later releases, this could also indicate that the cable tftp-enforce command has been used to require that a CM attempt a TFTP download of the DOCSIS configuration file before registering, but the CM did not do so.

reject(c)

The CM attempted to register, but registration was refused due to a a number of possible errors:

The CM attempted to register with a minimum guaranteed upstream bandwidth that would exceed the limits imposed by the cable upstream admission-control command.

The CM has been disabled because of a security violation.

A bad class of service (COS) value in the DOCSIS configuration file.

The CM attempted to create a new COS configuration but the CMTS is configured to not permit such changes.

The CM failed the timestamp check for its DOCSIS configuration file. (This could indicate a possible theft-of-service attempt, or a problem with the synchronization of the clocks on the CM and CMTS.)

reject(pk)

KEK key assignment is rejected, BPI encryption has not been established.

reject(pkd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because KEK key assignment was rejected.

Note This state is equivalent to the online(d) and reject(pk) states.

reject(pt)

TEK key assignment is rejected, BPI encryption has not been established.

reject(ptd)

The CM registered, but network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because TEK key assignment was rejected.

Note This state is equivalent to the online(d) and reject(pt) states.

reject(ts)

The CM attempted to register, but registration failed because the TFTP server timestamp in the CM registration request did not match the timestamp maintained by the CMTS. This might indicate that the CM attempted to register by replaying an old DOCSIS configuration file used during a prior registration attempt.

reject(ip)

The CM attempted to register, but registration failed because the IP address in the CM request did not match the IP address that the TFTP server recorded when it sent the DOCSIS configuration file to the CM. IP spoofing could be occurring.

reject(na)

The CM attempted to register, but registration failed because the CM did not send a Registration-Acknowledgement (REG-ACK) message in reply to the Registration-Response (REG-RSP) message sent by the CMTS. A Registration-NonAcknowledgement (REG-NACK) is assumed.

1 The CM MAC state field can also be retrieved using SNMP by getting the value of the cdxCmtsCmStatusValue object in the CISCO-DOCS-EXT-MIB.



Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to show commands using the exec prompt timestamp command in line configuration mode.


Table 16 shows the possible values for the MAC state field for a wideband-capable CM that registers as a wideband modem:

Table 16 Additional MAC States for a Wideband Cable Modem  

MAC State Value
Description
Non-error Status Conditions

w-online

The WCM has registered and is enabled to pass data on the network.

w-online(d)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. The CM does not forward traffic to or from the CPE devices, but the WCMTS can continue to communicate with the WCM using DOCSIS messages and IP traffic (such as SNMP commands).

Note If BPI was enabled in the DOCSIS configuration file sent to the WCM, assume that the CM is using BPI encryption, unless other messages show that the BPI negotiation and key assignments have failed.

w-online(pkd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and KEK is assigned.

Note This state is equivalent to the w-online(d) and w-online(pk) states.

w-online(pt)

The WCM registered, BPI is enabled and TEK is assigned. BPI encryption is now being performed.

Note If network access was disabled in the DOCSIS configuration file sent to the WCM, the network disabled status takes precedence, and the MAC status field shows w-online(d) instead of w-online(pt) even when BPI encryption is enabled and operational.

w-online(ptd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled and TEK is assigned. BPI encryption is now being performed.

Note This state is equivalent to the w-online(d) and w-online(pt) states.

w-online(pk)

The WCM registered, BPI is enabled and KEK is assigned.

w-expire(pk)

The WCM registered, BPI is enabled, KEK was assigned, but the current KEK expired before the WCM could successfully renew a new KEK value.

w-expire(pkd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value.

Note This state is equivalent to the w-online(d) and w-expire(pk) states.

w-expire(pt)

The WCM registered, BPI is enabled, TEK was assigned, but the current TEK expired before the WCM could successfully renew a new KEK value.

w-expire(ptd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI is enabled, TEK was assigned, but the current TEK expired before the WCM could successfully renew a new KEK value.

Note This state is equivalent to the w-online(d) and w-expire(pt) states.

Error Status Conditions

w-reject(pk)

KEK key assignment is rejected, BPI encryption has not been established.

w-reject(pkd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because KEK key assignment was rejected.

Note This state is equivalent to the w-online(d) and w-reject(pk) states.

w-reject(pt)

TEK key assignment is rejected, BPI encryption has not been established.

w-reject(ptd)

The WCM registered, but network access for CPE devices using this WCM has been disabled through the DOCSIS configuration file. In addition, BPI encryption was not established because TEK key assignment was rejected.

Note This state is equivalent to the w-online(d) and w-reject(pt) states.


Related Commands

Command
Description

show cable modem vendor

Associates the name of a vendor with its Organizational Unique Identifier (OUI).

show cable modem

Displays information for the registered and unregistered CMs.

show cable modem summary

Displays displays voice call information for a particular CM, identified either by its IP address or MAC address.

show cable modem classifiers

Displays information about the classifiers for a particular CM.

show cable modem cnr

Displays information about the upstream carrier-to-noise ratio (CNR) for a particular cable modem.

show cable modem connectivity

Displays connectivity statistics for one or more CMs.

show cable modem errors

Displays error statistics for one or more CMs.

show cable modem flap

Displays flap list statistics for one or more cable modems.

show cable modem maintenance

Displays station maintenance (SM) error statistics for one or more cable modems.

show cable modem remote-query

Displays information collected by the remote-query feature.

show cable modulation-profile

Displays modulation profile group information.

show interface cable modem

Displays information about the CMs connected to a particular cable interface.

show interface cable sid

Displays cable interface information.


show interface wideband-cable

To display the current configuration and status for a wideband channel, use the show interface wideband-cable command in privileged EXEC mode.

show interface wideband-cable slot/subslot/bay:wideband_channel [options]

Syntax Description

slot/subslot/bay:wideband-channel

Identifies a Wideband SIP and SPA on the Cisco uBR10012 router and the wideband channel number. The following are the valid values:

slot = 1 to 3

subslot = 0 or 1 (always 0)

bay = 0 (upper bay) or 1 (lower bay)

wideband-channel = 0 to 11

options

The following non-cable specific options generate information for wideband cable interfaces:

accounting—Displays the number of packets of each protocol type that was sent through the interface.
description—Displays the description entered for the interface.
privacy—Displays privacy group information.
stats—Displays packets that were switched.
summary—Displays interface summary information.
switching—Displays interface switching information.

Note Some other non-cable specific options do not generate any meaningful information for wideband cable interfaces.



Note For information on the non-cable specific options, see the Cisco IOS Release 12.3 documentation on Cisco.com and the Customer Documentation CD-ROM.


Command Modes

Privileged EXEC

Command History

Release
Modification

12.3(21)BC

This command was introduced on the uBR10012 universal broadband router.


Examples

The following is a sample output for the show interface wideband-cable command: 
 
   
Router# show interface wideband-cable 1/0/0:1 
 
   
Wideband-Cable1/0/0:1 is up, line protocol is up 
  Hardware is Wideband CMTS Cable interface, address is 0012.001a.8897 (bia 
0012.001a.8897)
  MTU 1500 bytes, BW 74730 Kbit, DLY 1000 usec, 
     reliability 255/255, txload 1/255, rxload 1/255
  Encapsulation MCNS, loopback not set
  Keepalive set (10 sec)
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:09, output hang never
  Last clearing of "show interface" counters never
  Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
  Queueing strategy: fifo
  Output queue: 0/40 (size/max)
  30 second input rate 0 bits/sec, 0 packets/sec
  30 second output rate 0 bits/sec, 0 packets/sec
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
     24224 packets output, 1222002 bytes, 0 underruns
     0 output errors, 0 collisions, 0 interface resets
     0 output buffer failures, 0 output buffers swapped out
 
   
Router#
 
   

Table 17 describes the fields shown in the show interface wideband-cable display.

Table 17 show interface wideband-cable Field Descriptions  

Field
Description

Wideband-Cable slot/subslot/bay:wb-channel is up/...administratively down

Indicates whether the interface hardware is currently active or taken down by the administrator.

line protocol is up/...administratively down

Indicates whether the software processes that handle the line protocol believe the interface is usable or if it has been taken down by the administrator.

hardware

Hardware type and address.

Internet address

Internet address followed by subnet mask.

MTU

Maximum transmission unit (MTU) of the interface.

BW

Bandwidth of the interface in kilobits per second.

DLY

Delay of the interface in microseconds.

rely

Reliability of the interface as a fraction of 255, calculated as an exponential average over 5 minutes. (For example, 255/255 is 100 percent reliability.)

load

Load on the interface as a fraction of 255, calculated as an exponential average over 5 minutes. (For example, 255/255 is complete saturation.)

Encapsulation

Encapsulation method assigned to this interface.

Keepalive set

Keepalive time interval.

ARP type

Type of Address Resolution Protocol (ARP) and timeout value assigned.

Last input

Number of hours, minutes, and seconds since the last packet was successfully received by an interface.

output

Number of hours, minutes, and seconds since the last packet was successfully sent by an interface.

Last clearing of "show interface" counters

Time at which the counters that measure cumulative statistics (such as number of bytes sent and received) were last reset to zero.

Queueing strategy

Displays the type of queueing configured for this interface. In the following example output, the type of queueing configured is first-in first-out (FIFO).

Output queue

Number of packets in the output queue. The format of this number is A/B, where A indicates the number of packets in the queue, and B indicates the maximum number of packets allowed in the queue.

drops

Indicates the number of packets dropped because of a full queue.

input queue/drops

Number of packets in the input queue. The format of this number is A/B, where A indicates the number of packets in the queue, and B indicates the maximum number of packets allowed in the queue.

drops

Indicates the number of packets dropped because of a full queue.

Five minute input rate
Five minute output rate

Average number of bits and packets sent per second in the last five minutes. The five-minute interval is the default time period for statistics collection and can be changed for each individual cable interface using the load-interval command in interface configuration mode.

Note These statistics are calculated using a decayed averaging method, where only the average is stored over the interval period, not the individual samples. Every time a sample average is taken, a percentage of the sample and a percentage of the average are added together to create the new average. If traffic stops for a time period, these statistics do not immediately go to zero but drop with a decay rate of about 70 percent per time period.

For example, if the interface is passing 1,000 packets per second (pps) before traffic stops, the show interface cable command shows the rate being 300 pps at the end of the first time interval. The rate then drops to 90 pps at the end of the second time interval, and so forth.

packets input

Total number of error-free packets received by the system.

bytes input

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer

Number of received packets discarded because there was no buffer space in the main system.

Received broadcast

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the medium's minimum packet size.

giants

Number of packets that are discarded because they are bigger than the standard Ethernet Maximum Transmission Unit (MTU) size. For Ethernet packets, RFC 1757 defines giants as "the total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and were otherwise well formed."

Note In addition, to account for the different Ethernet and other packet encapsulations on the network, packets are considered giants when they exceed the configured MTU size plus 114 bytes.

input errors

Total number of errors received on the interface. This count includes runts and giants, which are shown above, as well as other errors, such as no buffers, and CRC, frame, overrun, and ignored counts. This count can also include DOCSIS protocol errors such as an invalid SID in the DOCSIS frame, a bad extended header length, corrupted concatenated packets, and invalid bandwidth requests.

CRC

Indicates the number of times the cyclic redundancy checksum (CRC) generated by the originating LAN station or far-end device does not match the checksum calculated from the data received.

frame

Number of packets received incorrectly having a CRC error and a non-integer number of octets.

overrun

Number of times the receiver hardware was unable to forward received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers.

packets output

Total number of messages sent by the system.

bytes

Total number of bytes, including data and MAC encapsulation, sent by the system.

underruns

Number of times the sender has been running faster than the receiving device can handle.

output errors

Sum of all errors that prevented the final transmission of packets out of the interface being examined.

collisions

Not applicable.

interface resets

Number of times an interface has been completely reset.

output buffer failures

Number of times the output buffer has failed.

output buffer swapped out

Number of times the output buffer has been swapped out.



Tip In Cisco IOS Release 12.1(12)EC, Release 12.2(8)BC1, and later releases, you can add a timestamp to show commands using the exec prompt timestamp command in line configuration mode.


Related Commands

Command
Description

show interface cable downstream

Displays information about the downstream on the cable interface.

show interface cable sid

Displays information by service identifier (SID) of each CM on the network.

show interface cable signal-quality

Displays information about the cable signal quality.

show interface cable upstream

Displays information about one or all upstreams on the cable interface.


Restrictions for Cisco IOS Release 12.3(17a)BC

When upgrading the CiscouBR10012 Performance Routing Engine 1 (PRE1) modules to Cisco uBR10012 PRE2 modules, you must reconfigure the cable intercept feature when enabled on a slave interface. For additional information about the Cable Intercept feature, cable interface bundling, or virtual master interfaces in cable interface bundling, refer to the following documents on Cisco.com:

Cable Interface Bundling and Virtual Interface Bundling for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_bund.html

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Cisco IOS CMTS Cable Command Reference

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

New Command Information for Cisco IOS Release 12.3(13a)BC3

Cisco IOS Release 12.3(13a)BC3 introduces support for the debug cable classifier command, which displays debugging information supporting DOCSIS packet classifiers.

debug cable classifiers

To display debugging messages for DOCSIS packet classifiers, use the debug cable classifiers command in privileged EXEC mode. To stop the display of debugging messages, use the no form of this command.

debug cable classifiers

no debug cable classifiers

Syntax Description

No additional keywords or syntax components are required.

Command Modes

Privileged EXEC mode

Defaults

DOCSIS packet classifier debugging is disabled by default.

Command History

Release
Modification

12.3(13a)BC3

This command was introduced on the Cisco uBR10012 and Cisco uBR7246VXR universal broadband routers.


Usage Guidelines

The debug cable classifiers command provides detailed information about the allocation, removal, activation and deactivation of packet classifiers. Generally, classifiers are used to identify IP packets by source port, destination port, or type of service. Classifiers are associated with service flows. For example, packet classifiers are dynamically created in most Voice over IP (VoIP) deployments and this debug command can be used to troubleshoot issues related to these classifiers as VOIP calls are created and torn down.

Because this command can produce a large volume of debug information, use this command only when you have also enabled debugging for a particular MAC address, set of MAC addresses, or a MAC address mask, using the debug cable mac-address command.

For additional debug command information, refer to the following document on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

Examples

The following example enables classifier debugging for a single MAC address:

Router# debug cable mac-address 000a.73fa.dbaa
Router# debug cable classifiers
CMTS Packet Classifiers debugging is on

The following enables classifier debugging for all MAC addresses with Organizational Unique Identifier (OUI) OUI 0013.11:

Router# debug cable mac-addr 0013.1100.0000 ffff.ff00.0000
Routerv# debug cable classifiers                           
CMTS Packet Classifiers debugging is on

The following example illustrates sample output of the debug cable classifiers command for the given MAC addresses:

Feb  7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 
st 2 dir 0 prov 1 adm 1 act 1
Feb  7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 2 dir 
0 prov 1 adm 0 act 0
Feb  7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 
st 2 dir 1 prov 2 adm 2 act 2
Feb  7 18:43:50.181: CFR cmts_remove_cm_srv_flow_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 2 dir 
1 prov 2 adm 0 act 0
Feb  7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 
st 2 dir 0 prov 3 adm 0 act 0
Feb  7 18:43:50.181: CFR cmts_deactivate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 
st 1 dir 0 prov 3 adm 3 act 0
Feb  7 18:43:50.181: CFR cmts_activate_us_srv_flow_act_cfrs 000a.73fa.dbaa sid 1 sfid 3 st 
2 dir 0 prov 3 adm 3 act 3
Feb  7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 
st 2 dir 1 prov 4 adm 0 act 0
Feb  7 18:43:50.181: CFR cmts_deactivate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 
st 1 dir 1 prov 4 adm 4 act 0
Feb  7 18:43:50.181: CFR cmts_activate_ds_srv_flow_act_cfrs 000a.73fa.dbaa sid 0 sfid 4 st 
2 dir 1 prov 4 adm 4 act 4
Feb  7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 1 pri 0 ord 0 dir 0 st 2 
phsi 0
Feb  7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 2
Feb  7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 1 pri 1 ord 0 dir 0 st 1 
phsi 0
Feb  7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 
0 dir 0 type 0 cfrid 0 pri 1 ord 0 dir 0 st 1 phsi 0
Feb  7 18:43:50.181: CFR cmts_set_cfr_params 000a.73fa.dbaa cfrid 2 pri 0 ord 0 dir 1 st 2 
phsi 0
Feb  7 18:43:50.181: CFR cmts_activate_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 0 dir 1 st 2
Feb  7 18:43:50.181: CFR cmts_add_pkt_cfr 000a.73fa.dbaa cfrid 2 pri 1 ord 1 dir 1 st 1 
phsi 0
Feb  7 18:43:50.181: CFR cmts_handle_cfr_parsed_data CFR_ADD 000a.73fa.dbaa sfid 0 action 
0 dir 1 typ

Related Commands

Command
Description

debug cable dynsrv

Displays information about DOCSIS 1.1 dynamic service flow messages.

debug cable qos

Activates quality-of-service (QoS) debugging.


New Command Information for Cisco IOS Release 12.3(13a)BC2

Cisco IOS Release 12.3(13a)BC2 introduces support for the cable service flow activity-timeout command, which enables the configuration of dynamic service flow timeout settings apart from a PacketCable environment.

cable service flow activity-timeout

To configure the activity timeout for dynamic cable service flows in DOCSIS 1.1 environments, where PacketCable is inactive, use the cable service flow activity-timeout command in global configuration mode. To remove the activity timer once configured, use the no form of this command.

cable service flow activity-timeout n

no cable service flow activity-timeout [<n>]

Syntax Description

n

The timeout length in seconds. Valid range is 0 - 65535 seconds. Setting this value to 0 configures the service flow to never timeout.


Defaults

The default timeout length for a DOCSIS 1.0+ cable service flow is 300 seconds (five minutes).

Command Modes

Global configuration

Command History

Release
Modification

12.3(13a)BC

This command was introduced to support DOCSIS 1.1 service flow operation in non-Packet-Cable environments.


Usage Guidelines

Dynamic service flows in DOCSIS 1.0+ are created with a default activity timeout of 300 seconds. This enables the deletion of idle service flows after five minutes. This new command enables such functions within DOCSIS 1.1 environments with a wide range of timeout length options.

In DOCSIS 1.1, the default inactivity timeout is often set by the application that triggers the creation of dynamic service flows. PacketCable frequently performs this function when supported on the Cisco CMTS. However, this new command configures inactivity timeout where PacketCable is not active on the Cisco CMTS.


Note When PacketCable is supported, PacketCable sets the inactivity timeout from the PacketCable gate, and the PacketCable activity overrides timeout values set with this command. This is the case even where the inactivity timeout is set to zero, which configures the service flow to never timeout.


Apart from PacketCable, this command enables the cable modem to control the setup of the dynamic service flows, and to remove inactive service flows. During the creation of service flows, all Upstream and Downstream flows in the request are checked to see if the configured activity timeout needs to be applied.

Examples

The following example in global configuration mode configures the cable modems connected to the Cisco CMTS to use activity timeout of zero, which means that related service flows do not timeout in a non-PacketCable environment:

Router(config)# cable service flow activity-timeout 0

Related Commands

Command
Description

cable qos profile

Creates a DOCSIS 1.0 QoS profile.

cable service flow inactivity-threshold

Sets the amount of time a dynamic service-flow can be present in the system without any activity (DOCSIS 1.1 operation).

cable service-flow inactivity-timeout

Sets the amount of time a dynamic service-flow can be present in the system without any activity (DOCSIS 1.0 operation).

show cable service-class

Displays the service classes that have been created.


Restrictions for Cisco IOS Release 12.3(13a)BC

The following restrictions apply to Cisco IOS Release 12.3(13aq)BC:

Cisco IOS Release 12.3(13a)BC with the Cisco uBR10012 router does not support overlapping IP addresses with MPLS-VPN.

When upgrading the Cisco uBR10012 Performance Routing Engine 1 (PRE1) modules to Cisco uBR10012 PRE2 modules, you must reconfigure the cable intercept feature when enabled on a slave interface. For additional information about the Cable Intercept feature, cable interface bundling, or virtual master interfaces in cable interface bundling, refer to the following documents on Cisco.com:

"Virtual Interface Bundling on the Cisco uBR10-MC5X20S/U BPE" section

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Cisco IOS CMTS Cable Command Reference

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

Restrictions for Cisco IOS Release 12.3(9a)BC

The following restrictions apply to Cisco IOS Release 12.3(9a)BC:

Cisco IOS Release 12.3(9a)BC with the Cisco uBR10012 router does not support overlapping IP addresses with MPLS-VPN.

When upgrading the Cisco uBR10012 Performance Routing Engine 1 (PRE1) modules to Cisco uBR10012 PRE2 modules, you must reconfigure the cable intercept feature when enabled on a slave interface. For additional information about the Cable Intercept feature or cable interface bundling, refer to the following documents on Cisco.com:

Cable Monitor and Intercept Features for the Cisco CMTS

http://www.cisco.com/en/US/docs/cable/cmts/feature/guide/ufg_cmon.html

Cisco IOS CMTS Cable Command Reference

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

New and Changed Command Reference for Cisco IOS Release 12.3(9a)BC

Cisco IOS Release 12.3(9a)BC introduces or enhances the following Cisco IOS commands for the Cisco uBR10012 router:

cable logging layer2events

cable source-verify

cable submgmt default

show cable tech-support

show controllers cable

show tech-support

cable logging layer2events

To save selected (low priority) DOCSIS events that are specified in CMTS MIB Registry to the cable logging buffer (instead of to the general logging buffer), use the cable logging layer2events command in global configuration mode. To disable the logging of DOCSIS events to the cable logging buffer, use the no form of this command.

cable logging layer2events

no cable logging layer2events

Syntax Description

This command has no additional arguments or keywords.

Defaults

DOCSIS events are saved to the general logging buffer on the Cisco CMTS by default.

Command Modes

Global configuration mode

Command History

Release
Modification

12.3(9a)BC

This command was introduced on the Cisco uBR10012 and Cisco uBR7246VXR universal broadband routers.


Usage Guidelines

Use the show cable logging command to check whether the logging feature is enabled and the status of the logging buffer.

Examples

The following example shows how to clear the log buffer that contains a bad IP source address error messages:

Router# show cable logging summary
Cable logging: BADIPSOURCE Enabled
Total buffer size (bytes): 1000000
Used buffer size (bytes) : 36968
Logged messages : 231
Router# clear cable logging badipsource
Router# show cable logging summary
Cable logging: BADIPSOURCE Enabled
Total buffer size (bytes): 1000000
Used buffer size (bytes) : 0
Logged messages : 0

Related Commands

Command
Description

cable logging badipsource

Logs error messages about bad IP source addresses on the cable interfaces to a separate log buffer,

show cable logging

Indicates whether the logging feature is enabled and the status of the logging buffer.


For additional information about logging events on the Cisco CMTS, refer to the following document on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

cable source-verify

To enable verification of IP addresses or service IDs (SIDs) for CMs and CPE devices on the upstream, use the cable source-verify command in global configuration, cable interface configuration or subinterface configuration modes. To disable verification, use the no form of this command.

Cable Interface and Subinterface Configuration Modes

cable source-verify [dhcp | leasetimer value | leasequery-filter upstream query-num interval]

no cable source-verify

Global Configuration Mode

cable source-verify leasequery-filter downstream query-num interval

no cable source-verify

Syntax Description

dhcp

(Optional) Specifies that queries will be sent to verify unknown source IP addresses in upstream data packets.

Note Do not enable the local DHCP server on the Cisco CMTS and configure local DHCP address pools, using the ip dhcp pool command, when using this option, because this prevents DHCP address validation.

leasetimer value

(Optional) Specifies the time, in minutes, for how often the router should check its internal CPE database for IP addresses whose lease times have expired. The valid range for value is 1 to 240 minutes, with a default of 60 minutes.

Note The leasetimer option takes effect only when the dhcp option is also used on an interface. Also, this option is supported only on the master interface and cannot be configured on subinterfaces. Configuring it for a master interface automatically applies it to all subinterfaces.

leasequery-filter upstream query-num interval

(Optional) Enables upstream lease queries to be defined on a per-SID basis to reduce the chance of Denial of Service attacks.

query-num— Number of leased queries per SID.

interval—Size of timer window in seconds.

leasequery-filter downstream query-num interval

(Optional) Enables downstream lease queries to be defined on a per-SID basis to reduce the chance of Denial of Service attacks.

query-num— Number of leased queries for an unknown SID.

interval—Size of timer window in seconds.


Defaults

Disabled. When the dhcp option is specified, the leasetimer option is set by default to 60 minutes.

Command Modes

Global configuration, Cable interface configuration or subinterface configuration


Note Configuring the cable source-verify command on the master interface of a bundle will configure it for all of the slave interfaces in the bundle as well.


Command History

Release
Modification

11.3 XA

This command was introduced.

12.0(7)T

The dhcp keyword was added.

12.0(10)SC, 12.1(2)EC

Support was added for these trains.

12.1(3a)EC

Subinterface support was added.

12.1(13)EC, 12.2(11)BC1

The leasetimer keyword was added.

12.2(15)BC1

The verification of CPE devices was changed when using the dhcp keyword.

12.2(15)BC2

Support for verifying CMs and CPE devices that are on a different subnet than the cable interface was enhanced to use Reverse Path Forwarding (RFP).

12.3(9a)BC

In order to protect the Cisco CMTS from denial of service attacks, Cisco IOS Release 12.3(9a)BC adds the option of using a per SID basis for deriving lease queries from CPE devices. This release also introduces a global rate limit for lease queries initiated by downstream traffic. These enhancements reduce the CPU utilization of DHCP Receive and ISR processes when the Cisco CMTS is configured with the cable source-verify dhcp and no cable arp commands.


For additional information about this and other commands, refer to the following document on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

cable submgmt default

To enable the Cisco CMTS Static CPE Override feature on the Cisco CMTS, use the cable submgmt default command in global configuration mode. This command enables field technicians to add a temporary CPE device behind the subscriber's cable modem. The temporary CPE device shares the same SID settings as the original CPE device, even though the temporary CPE device has a different MAC address. The original CPE device automatically changes from dhcp cpe to static cpe in the CMTS host routing tables, and the CPE device continues to receive service with the same SID. To disable Cisco CMTS Static CPE Override on the Cisco CMTS, use the no form of this command. This automatically updates the routing tables and enables the MAC address from the technician's laptop for a future field service connection at a different location.

cable submgmt default {active | filter-group {cm | cpe} | learnable | max-cpe}

no cable submgmt default

Syntax Description

active

Keyword enables Cisco CMTS Static CPE Override, granting local CPE control for subscriber management filtering (as defined by existing SID settings).

filter-group {cm | cpe}

Keyword enables one ore more temporary CPE devices to inherit the characteristics of an existing filter group, either on the downstream or the upstream of the cable modem (cm) or the CPE device (cpe).

filter-group cm {downstream | upstream}—This keyword combination enables one or more temporary CPE devices to inherit and filter by the default downstream cable modem group, or by the default upstream cable modem group.

filter-group cpe {downstream | upstream}—This keyword combination enables one or more temporary CPE devices to inherit and filter by the default downstream CPE group, or by the default upstream CPE group.

learnable

Keyword automatically enables one or more temporary CPE devices to learn and to operate within the CPE IP address(es) in the Cisco CMTS routing table.

max-cpe

Keyword sets the maximum number of IP addresses to be permitted behind a cable modem while the Cisco CMTS Static CPE Override feature is enabled. This keyword enables multiple temporary CPE devices in the range of 0 to 1024.


Defaults

This command is disabled by default.

Command Modes

Global configuration mode

Command History

Release
Modification

12.3(9a)BC

This feature was introduced on Cisco uBR10012 and Cisco uBR7200 series universal broadband routers.


Usage Guidelines

Prior to using this command, the first (existing) DHCP CPE device maintains its DHCP dynamic MAC address behind the cable modem. The SID is assigned to this IP address.

However, by enabling Static CPE override, you gain the following states and options on two CPE devices behind the cable modem.

The SID definition on the first CPE device is assigned a different static IP address. This enables you to change the existing (dynamic) DHCP IP address to a static IP address without first clearing the DHCP CPE host entries from the Cisco CMTS. The CPE IP state changes from dhcp to static cpe.

This static override allows a second CPE device with a second MAC address behind the same cable modem with SID1 to be assigned same IP address as the first CPE device.


Note The second CPE device changes from dhcp cpe to static CPE in the CMTS host tables.


Examples

The following example enables Cisco CMTS Static CPE Override in the field, enabling more or more additional CPE devices to be added behind a subscriber's cable modem:

Router(config)# cable submgmt default active

The following example configures the Cisco CMTS to accept a temporary CPE device, which inherits and filters by the subscriber's default downstream cable modem group:

Router(config)# cable submgmt default filter-group cm downstream

The following example configures the Cisco CMTS to accept a temporary CPE device, and to update the temporary CPE device with the current routing table from the Cisco CMTS:

Router(config)# cable submgmt default learnable

The following example configures the Cisco CMTS to accept a maximum of five temporary CPE devices behind a subscriber's cable modem:

Router(config)# cable submgmt default max-cpe 5

Related Commands

Command
Description

show cable host

Displays the CPE devices (hosts) residing behind a specified cable modem (MAC address).


show cable tech-support

Cisco IOS Release 12.3(9a)BC introduces changes to the output of the show cable tech-support command. This change allows users with large numbers of online cable modems to collect the necessary information without consuming the console session for a long period of time.

To display general information about the router when reporting a problem, use the show cable tech-support command in privileged EXEC mode.

show cable tech-support [cable slot/port | cable slot/subslot/port]

Syntax Description

cable slot/port

(Optional) Displays information only for the specified cable interface on the Cisco uBR7100 series and Cisco uBR7200 series routers.

On the Cisco uBR7100 series router, the only valid value is 1/0. On the Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0 or 1, depending on the cable interface.

cable slot/subslot/port

(Optional) Displays information only for the specified cable interface on the Cisco uBR10012 router. The following are the valid values:

slot = 5 to 8

subslot = 0 or 1

port = 0 to 4 (depending on the cable interface)


Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Privileged EXEC

Command History

Release
Modification

11.2

This command was introduced.

12.1(1a)T1

This command was modified to include information about the cable clock card.

12.2(15)BC2

This command added several show pxf commands to the display on the Cisco uBR10012 router.

12.3(9a)BC

The output of the command was significantly shortened by moving a number of show commands (the ones that display information about individual cable modems) to the show tech-support command. Also, added support for an option to display information about only one specific cable interface.


Examples

The following example illustrates the cable modem and interface information for the Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed.

Router# show cable tech-support
----------------------------------- Slot 8/1 -----------------------------------
------------------ show cable modem Cable8/1/0 ------------------
MAC Address    IP Address      I/F       MAC         Prim RxPwr  Timing  Num BPI
                                         State       Sid  (dB)   Offset  CPE Enb
------------------ show cable modem Cable8/1/0 connectivity ------------------
Prim  1st time    Times  %online     Online time            Offline time
Sid   online      Online          min     avg     max     min     avg     max
------------------ show interface Cable8/1/0 sid ------------------
Sid  Prim  MAC Address    IP Address      Type Age      Admin   Sched  Sfid
                                                        State   Type
------------------ show interface Cable8/1/0 sid counter ------------------
Sid  Req-polls  BW-reqs    Grants     Packets    Frag       Concatpkts
     issued     received   issued     received   complete   received
------------------ show interface Cable8/1/0 sid association ------------------
Sid  Prim Online     IP Address      MAC Address    Interface     VRF Name
------------------ show interface Cable8/1/0 modem 0 ------------------
SID   Priv bits  Type      State       IP address      method    MAC address
------------------ show cable modem Cable8/1/1 ------------------
MAC Address    IP Address      I/F       MAC         Prim RxPwr  Timing  Num BPI
                                         State       Sid  (dB)   Offset  CPE Enb
------------------ show cable modem Cable8/1/1 connectivity ------------------
Prim  1st time    Times  %online     Online time            Offline time
Sid   online      Online          min     avg     max     min     avg     max
------------------ show interface Cable8/1/1 sid ------------------
Sid  Prim  MAC Address    IP Address      Type Age      Admin   Sched  Sfid
                                                        State   Type
------------------ show interface Cable8/1/1 sid counter ------------------
Sid  Req-polls  BW-reqs    Grants     Packets    Frag       Concatpkts
     issued     received   issued     received   complete   received
------------------ show interface Cable8/1/1 sid association ------------------
Sid  Prim Online     IP Address      MAC Address    Interface     VRF Name
------------------ show interface Cable8/1/1 modem 0 ------------------
SID   Priv bits  Type      State       IP address      method    MAC address

For additional information about this and other commands, refer to the following document on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

show controllers cable

Cisco IOS Release 12.3(9a)BC adds the tech-support keyword to the show controllers cable command. This change allows users with large numbers of online cable modems to collect the necessary line card information without consuming the console session for a long period of time.

Additional and related improvements are also available for the show tech-support command.

To display information about the interface controllers for a cable interface on the Cisco CMTS router, use the show controllers cable command in user EXEC or privileged EXEC mode.

show controllers cable {slot/port | slot/subslot/port} [downstream | upstream [port] | [mem-stat] [memory] [proc-cpu] [tech-support] ]

Syntax Description

slot/port

Identifies the cable interface and downstream port on the Cisco uBR7100 series and Cisco uBR7200 series routers.

On the Cisco uBR7100 series router, the only valid value is 1/0. On the Cisco uBR7200 series router, slot can range from 3 to 6, and port can be 0 or 1, depending on the cable interface.

slot/subslot/port

Identifies the cable interface on the Cisco uBR10012 router. The following are the valid values:

slot = 5 to 8

subslot = 0 or 1

port = 0 to 4 (depending on the cable interface)

downstream

(Optional) Displays downstream interface status.

upstream

(Optional) Displays upstream interface status.

port

(Optional) Specifies the desired upstream port. Valid values start with 0 for the first upstream port on the cable interface line card.

mem-stat

(Optional) Displays the output from the show memory statistics command to display a summary of memory statistics for a Broadband Processing Engine (BPE) cable interface line card.

memory

(Optional) Displays the output from the show memory command to display a summary of memory statistics, including the memory as it is allocated per process, for a Broadband Processing Engine (BPE) cable interface line card.

proc-cpu

(Optional) Displays the output from the show processes cpu command to display the processor status for a Broadband Processing Engine (BPE) cable interface line card.

tech-support

(Optional, privileged EXEC mode only) Displays the output from the show cable tech-support command for a Broadband Processing Engine (BPE) cable interface line card.


Command Modes

User EXEC, Privileged EXEC

Command History

Release
Modification

11.3 NA

This command was introduced.

12.0(2)XC

This command was modified to show a number of additional fields.

12.1(5)EC1

Support was added for the Cisco uBR7100 series router, including information about the Cisco uBR7100 series integrated upconverter.

12.2(1)XF1

Support was added for the Cisco uBR10012 router.

12.0(16)SC2, 12.1(10)EC1, 12.2(4)BC1b

The algorithm for calculating the SNR value was enhanced for a more accurate value.

12.2(15)CX

Support was added for the Cisco uBR-MC28U/X cable interface line card, including the display of the number of packets dropped because they were for a Service Flow ID (SFID) of 0.

12.2(15)BC2b

The mem-stat, memory, and proc-cpu options were added to obtain processor information from the onboard processor on Broadband Processing Engine (BPE) cable interface line cards, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U cards.

12.3(9a)BC

The tech-support option was added in order to improve command behavior. Additional information required during technical support is also available with alternate commands such as show tech-support and show cable tech-support.


Usage Guidelines

The mem-stat, memory, and proc-cpu keywords execute the related command on the processor that runs on added to obtain the relevant information from the onboard processor on Broadband Processing Engine (BPE) cable interface line cards, such as the Cisco uBR-MC16U/X, Cisco uBR-MC28U/X, and Cisco uBR10-MC5X20S/U cards. This allows you to obtain information that is specific for that particular cable interface card, as opposed to having to run these commands on the entire router.


Note The mem-stat, memory, and proc-cpu options are not available for cable interface line cards that do not contain an onboard processor (for example, the Cisco uBR-MC16C cable interface line card).


Examples

The following is sample output for the downstream connection for cable interface 8/1/0 on a Cisco uBR10012 router:

Router# show controllers c8/1/0 downstream
 Cable8/1/0 Downstream is up
  Frequency not set, Channel Width 6 MHz, 64-QAM, Symbol Rate 5.056941 Msps
  FEC ITU-T J.83 Annex B, R/S Interleave I=32, J=4
  Downstream channel ID: 0
  Dynamic Services Stats:
  DSA: 0  REQs  0 RSPs  0 ACKs
  0 Successful DSAs  0 DSA Failures
  DSC: 0  REQs  0 RSPs  0 ACKs
  0 Successful DSCs  0 DSC Failures
  DSD:  0 REQs  0 RSPs
  0 Successful DSDs  0 DSD Failures
  DCC: 0  REQs  0 RSPs  0 ACKs
  0 Successful DCCs  0 DCC Failures

Table 18 describes the fields displayed by the show controllers cable downstream command.

Table 18 show controllers cable downstream Field Descriptions  

Field
Description
Cable

Slot number/port number indicating the location of the Cisco cable interface line card.

Downstream is up

Indicates that the RF downstream interface is enabled.

Frequency

Transmission frequency of the RF downstream. (This information may not match the current transmission frequency, which is external on CMTS platforms that use an external upconverter.)

Channel Width

Indicates the width of the RF downstream channel.

QAM

Indicates the modulation scheme.

Symbol Rate

Indicates the transmission rate (in number of symbols per second).

FEC ITU-T

Indicates the Motion Picture Experts Group (MPEG) framing standard.

R/S Interleave I/J

Indicates Reed Solomon framing based on ITU S.83-B.


Examples

The following example illustrates the information from the show controllers cable command for slot/subslot/port 8/1/0 on a Cisco uBR10012 router on which Cisco IOS Release 12.3(9a)BC is installed.

Router# show controllers c8/1/0
Interface Cable8/1/0
Hardware is MC28C(F-connector)
 BCM3210 revision=0x56B2
 idb 0x61329EB0 MAC regs 0x3E104000 PLX regs 0x3E000000
 rx ring entries 1024 tx ring entries 128 MAP tx ring entries 128
 Rx ring 0xC1AD080 shadow 0x613AAB38 head 0
 Tx ring 0xC1AF0C0 shadow 0x613ABBA8 head 34 tail 34 count 0
 MAP Tx ring 0xC1AF500 shadow 0x613AC018 head 52 tail 52 count 0
 Timestamp is from TCCplus card
 throttled 0 enabled 0 disabled 0
 Rx: spurious 0 framing_err 0 hcs_err 0 no_buffer 0 short_pkt 0
     no_enqueue 0 no_enp 0 miss_count 0 latency 0
     invalid_sid 0 invalid_mac 0 bad_ext_hdr_pdu 0 concat 0 bad-concat 0
 Tx:  full 0 drop 0 stuck 0 latency 20
 MTx: full 0 drop 0 stuck 0 latency 10
 Slots 0 NoUWCollNoEngy 0 FECorHCS 1 HCS 1
 Req 3842362657 ReqColl 0 ReqNoise 0 ReqNoEnergy 3842362657
 ReqData 32 ReqDataColl 0 ReqDataNoise 0 ReqDataNoEnergy 32
 Rng 0 RngColl 0 RngNoise 0
 FECBlks 1 UnCorFECBlks 1 CorFECBlks 0
 MAP FIFO overflow 0, Rx FIFO overflow 0, No rx buf 0
 DS FIFO overflow 0, US FIFO overflow 0, US stuck 0
 Bandwidth Requests= 0x0
 --More--

The following example illustrates memory statistics for the specified slot/subslot/port on the Cisco uBR10012 router:

Router# show controllers c8/1/0 mem-stat
                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
Processor   60F3FB40   185337024     8644376   176692648   176557288   176638828
      I/O    C000000    67108864     6679384    60429480    60429480    60405696

The following example illustrates upstream information for the specified slot/subslot/port on the Cisco uBR10012 router:

Router# show controllers c8/1/0 upstream
 Cable8/1/0 Upstream 0 is up
  Frequency 25.008 MHz, Channel Width 1.600 MHz, QPSK Symbol Rate 1.280 Msps
  Spectrum Group is overridden
  SNR - Unknown - no modems online.
  Nominal Input Power Level 0 dBmV, Tx Timing Offset 0
  Ranging Backoff automatic (Start 0, End 3)
  Ranging Insertion Interval automatic (60 ms)
  Tx Backoff Start 3, Tx Backoff End 5
  Modulation Profile Group 1
  Concatenation is enabled
  Fragmentation is enabled
  part_id=0x3137, rev_id=0x03, rev2_id=0xFF
  nb_agc_thr=0x0000, nb_agc_nom=0x0000
  Range Load Reg Size=0x58
  Request Load Reg Size=0x0E
  Minislot Size in number of Timebase Ticks is = 4
  Minislot Size in Symbols = 32
  Bandwidth Requests = 0x0
  Piggyback Requests = 0x0
  Invalid BW Requests= 0x0
  Minislots Requested= 0x0
  Minislots Granted  = 0x0
  Minislot Size in Bytes = 8
  Map Advance (Dynamic) : 2180 usecs
  UCD Count = 320676
  DES Ctrl Reg#0 = C000C043, Reg#1 = 0

The following example illustrates CPU processes for the specified slot/subslot/port on the Cisco uBR10012 router:

Router# show controllers c8/1/0 proc-cpu
CPU utilization for five seconds: 1%/1%; one minute: 1%; five minutes: 1%
 PID Runtime(ms)   Invoked      uSecs   5Sec   1Min   5Min TTY Process
   1           4         1       4000  0.00%  0.00%  0.00%   0 Chunk Manager
   2           0    128036          0  0.00%  0.00%  0.00%   0 Load Meter
   3         248       395        627  0.00%  0.00%  0.00%   0 CR10K IPC MSG Pr
   4      428012    384113       1114  0.07%  0.07%  0.07%   0 CR10K NonBlk Xmt
   5       43392     65009        667  0.00%  0.00%  0.00%   0 Check heaps
   6           8       561         14  0.00%  0.00%  0.00%   0 Pool Manager
   7           0         1          0  0.00%  0.00%  0.00%   0 AAA_SERVER_DEADT
   8           0         2          0  0.00%  0.00%  0.00%   0 Timers
   9           0         2          0  0.00%  0.00%  0.00%   0 AAA high-capacit
  10           0     10680          0  0.00%  0.00%  0.00%   0 ARP Input
  11           0         1          0  0.00%  0.00%  0.00%   0 Entity MIB API
  12           0         2          0  0.00%  0.00%  0.00%   0 Serial Backgroun

The following example illustrates memory processor information for the specified slot/subslot/port on the Cisco uBR10012 router:

Router# show controllers c8/1/0 memory
                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
Processor   60F3FB40   185337024     8644376   176692648   176557288   176638828
      I/O    C000000    67108864     6679384    60429480    60429480    60405696
          Processor memory
 Address      Bytes     Prev     Next Ref     PrevF    NextF Alloc PC  what
60F3FB40 0000020004 00000000 60F4498C 001  -------- -------- 60113308  Managed Chunk Queue 
Elements
60F4498C 0000001504 60F3FB40 60F44F94 001  -------- -------- 60126F88  List Elements
60F44F94 0000005004 60F4498C 60F46348 001  -------- -------- 60126FCC  List Headers
60F46348 0000000048 60F44F94 60F463A0 001  -------- -------- 6055D4E4  *Init*
60F463A0 0000000028 60F46348 60F463E4 001  -------- -------- 604C12B4  *Init*
60F463E4 0000000048 60F463A0 60F4643C 001  -------- -------- 6055D4E4  *Init*
60F4643C 0000000200 60F463E4 60F4652C 001  -------- -------- 6014BE28  *Init*
60F4652C 0000004260 60F4643C 60F475F8 001  -------- -------- 60065A2C  TTY data
60F475F8 0000002004 60F4652C 60F47DF4 001  -------- -------- 60069164  TTY Input Buf

The following example illustrates the first information for the tech-support option for the specified slot/subslot/port on the Cisco uBR10012 router:

Router# show controllers c8/1/0 tech-support
------------------ show version ------------------
Cisco Internetwork Operating System Software
IOS (tm) 7200 Software (UBR10KCLC-LC-M), Experimental Version 12.3(20040708:1441
55) [bguckel-geo_cable-l2 102]
Copyright (c) 1986-2004 by cisco Systems, Inc.
Compiled Mon 12-Jul-04 11:28 by bguckel
Image text-base: 0x60008EB8, data-base: 0x60CB0000
ROM: System Bootstrap, Version 12.2(20011031:221132) [maheshj-cr10k-rommon 15],
DEVELOPMENT SOFTWARE
BOOTLDR: 7200 Software (UBR10KCLC-LC-M), Experimental Version 12.2(20011107:2331
03) [janez-v122_2_xf_throttle.Nov5A 101]
clc_8_1 uptime is 1 week, 9 hours, 54 minutes
System returned to ROM by power-on
System restarted at 08:59:44 UTC Wed Jul 21 2004
Running default software
cisco uBR10K CLC (NPE-CLC) processor (revision A) with 196608K/65536K bytes of m
emory.
Processor board ID
R7000 CPU at 262MHz, Implementation 39, Rev 2.1, 256KB L2 Cache
6 slot midplane, Version 1.0

For additional information about this and other commands, refer to the following document on Cisco.com:

Cisco IOS CMTS Cable Command Reference

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

show tech-support

Cisco IOS Release 12.3(9a)BC shortens the output of the show tech-support command on the Cisco uBR10012 and the Cisco uBR7246VXR routers. This change allows users with large numbers of online cable modems to collect information without consuming the console session for a long period of time.

To display general information about the Cisco CMTS router when reporting a problem to Cisco technical support, use the show tech-support command in privileged EXEC mode.

show tech-support [page] [password] [cef | ipc | ipmulticast | isis | mpls | ospf | rsvp]


Note The show tech-support command automatically displays the output of a number of different show commands. The exact output depends on the platform, configuration, and type of protocols being used.



Note The show tech-support includes most of the information shown in the show cable tech-support command.


Syntax Description

page

(Optional) Causes the output to display a page of information at a time. Use the Return key to display the next line of output or use the space bar to display the next page of information. If not used, the output scrolls (that is, does not stop for page breaks).

password

(Optional) Leaves passwords and other security information in the output. If not used, passwords and other security-sensitive information in the output are replaced with the label "<removed>" (this is the default).

cef

(Optional) Displays information about the Cisco Express Forwarding (CEF) protocol configuration and status.

ipc

(Optional) Displays information about interprocess communications on the Cisco router.

ipmulticast

(Optional) Displays information about the IP multicast configuration and status.

isis

(Optional) Displays information about the Connectionless Network Service (CLNS) and Intermediate System-to-Intermediate System (IS-IS) routing protocol configuration and status.

Note IS-IS support is provided only on CMTS platforms running Cisco IOS images that have a "-p-" as part of the image name.

mpls

(Optional) Displays information about Multiprotocol Label Switching (MPLS) on the Cisco router, which instructs the routers and the switches in the network on where to forward the packets based on preestablished IP routing information.

Note Cisco IOS Release with the Cisco uBR10012 router does not support overlapping IP addresses with MPLS Virtual Private Networks (VPN).

ospf

(Optional) Displays information about the Open Shortest Path First (OSPF) routing algorithm and status on the Cisco router.

rsvp

(Optional) Displays information about the IP Resource Reservation Protocol (RSVP) configuration and status.


For additional information about this and other commands, refer to the following document on Cisco.com (updated through Cisco IOS Release 12.3(9a)BC):

Cisco IOS CMTS Cable Command Reference

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

Caveats for Cisco IOS Release 12.3 BC

Caveats describe unexpected behavior in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only selected severity 3 caveats are included in the caveats document.

Cisco IOS Release 12.3 mainline is the parent release train for12.3(23)BC7. Unless otherwise noted, Cisco IOS Release 12.3(23)BC7 maintains support for the changes and caveat resolutions introduced in earlier releases of Cisco IOS Release 12.3 mainline.


Note If you have an account on Cisco.com, you can use the Bug Toolkit to find select caveats of any severity. To reach the Bug Toolkit, log in to Cisco.com and click Technical Support: Tools & Utilities: Software BUG TOOLKIT (under Configuration Tools). Another option is http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs


Open Caveats for Release 12.3(23)BC10

Table 19 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(23)BC10.

Table 19 Open Caveats for Cisco IOS Release 12.3(23)BC10 

DDTS ID Number
Description

CSCeh33888

Symptoms: A Cisco uBR7246VXR router may reload with the configurations set during the last watchdog reset.

Conditions: This issue occurs on a Cisco uBR7246VXR router having a Cisco uBR7200-NPE-G1 processor board, and running Cisco IOS Release 12.3(9a)BC.

Workaround: There is no workaround.

CSCsl50133

Symptoms: The Cisco uBR7246VXR router reloads with the following message:

No crashinfo
No tracebacks
Last reload reason: Unknown reason
Last reset from watchdog reset

Conditions: This issue occurs on a Cisco uBR7246VXR router with UBR7200-NPE-G1, running Cisco IOS Release 12.3(17b)BC4.

Workaround: There is no workaround.

CSCsz98503

Symptoms: There is a time delay of a few minutes when multiple cable modems go off on a random upstream. These losses are usually accompanied by a spike in the error per second rate or by an MER drop and a decrease in docsIfSigQUnerroreds MIB. However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.

Conditions: This issue occurs on the Cisco uBR10-MC5X20H line cards.

Workaround: There is no workaround.

CSCtc49858

Symptoms: Users with lower privilege levels than "Enable access" may not be able to execute some "show cable" command options, since they do not carry over the right privilege level as their parent.

For example, in Enabled mode:

UBR10K-1#show cable mac-domain Cable6/0/4 ?
  cgd-associations          CGD Downstream Association
  downstream-service-group  MAC Domain service groups  <==== Available 
under Enable mode.

Now, when you assign this command to user mode with a different privilege level:

  privilege exec level 1 show cable mac-domain

Not all command options under the show cable mac-domain parent command are available. In this example, the downstream-service-group option is not available:

UBR10K-1#enable 1
UBR10K-1>show cable mac-domain Cable6/0/4 ?
  cgd-associations  CGD Downstream Association
UBR10K-1>show cable mac-domain Cable6/0/4 downstream-service-group
                                                 ^
% Invalid input detected at '^' marker.

But, the other option is available:

UBR10K-1>show cable mac-domain c6/0/4 cgd-associations 
Load for five secs: 4%/1%; one minute: 3%; five minutes: 2%
Time source is NTP, 13:00:09.089 EDT Mon Oct 12 2009
CGD Host  Resource  DS Channels            Upstreams (AllUS)   Active 
Remote DS

This is not the correct behavior for privilege level command, as it should grant the same privilege for all command options comfigurable for the defined command.

Conditions: This issue occurs with the show cable mac-domain command and its "downstream-service-group" option that displays DS channel information for Wideband cable modems. All the Cisco IOS releases 12.3BC, 12.2(33)SCB, and 12.2(33)SCC are affected.

Workaround: Repeat the privilege level command in a more granular way.

For example, for the example explained above, the command needs to be repeated for each interface as follows:

privilege exec level 1 show cable mac-domain c5/0/0 
downstream-service-group
privilege exec level 1 show cable mac-domain c5/0/1 
downstream-service-group
privilege exec level 1 show cable mac-domain c5/0/2 
downstream-service-group
...
...
privilege exec level 1 show cable mac-domain c8/1/4 
downstream-service-group

CSCtc78090

Symptoms: The downstream frequency override (DFO) retry counter is not incremented from #0.

Conditions: This issue occurs while configuring "cable service attribute ds-bonded downstream-type bonding-enabled [enforce]". After the wideband cable modem goes online(NB) with "ds-bonded downstream-type bonding-enabled enforce", power on and off the wideband cable modem. The DFO retry counter should be incremented after this but this does not occur.

Workaround: There is no workaround.

CSCth01285

Symptoms: Multicast traffic is not forwarded across DOCSIS Set-Top Gateway (DSG) tunnels on modular and legacy downstreams.

Conditions: This issue is observed on Cisco uBR10012 router.

Workaround: Re-configure the DSG tunnels.


Resolved Caveats for Release 12.3(23)BC10

Table 20 lists only severity 1 and 2 caveats and select severity 3 resolved caveats for Cisco IOS Release 12.3(23)BC10.

Table 20 Resolved Caveats for Cisco IOS Release 12.3(23)BC10 

DDTS ID Number
Description

CSCsz45567

A device running Cisco IOS Software, Cisco IOS XE Software, or Cisco IOS XR Software is vulnerable to a remote denial of service condition if it is configured for Multiprotocol Label Switching (MPLS) and has support for Label Distribution Protocol (LDP).

A crafted LDP UDP packet can cause an affected device running Cisco IOS Software or Cisco IOS XE Software to reload. On devices running affected versions of Cisco IOS XR Software, such packets can cause the device to restart the mpls_ldp process. A system is vulnerable if configured with either LDP or Tag Distribution Protocol (TDP).

Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available.

This advisory is posted at:

http://www.cisco.com/warp/public/707/cisco-sa-20100324-ldp.shtml

CSCsz53710

Symptoms: Cannot ping or provision a Multimedia Terminal Adaptor (MTA) that has no IP connectivity.

Conditions: This issue occurs while upgrading to Cisco IOS Release 12.2(33)SCB2.

Workaround: Reset the MTA.

CSCsz75186

Cisco IOS Software is affected by a denial of service vulnerability that may allow a remote unauthenticated attacker to cause an affected device to reload or hang. The vulnerability may be triggered by a TCP segment containing crafted TCP options that is received during the TCP session establishment phase. In addition to specific, crafted TCP options, the device must have a special configuration to be affected by this vulnerability.

Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100324-tcp.shtml

CSCtc44253

Symptoms: The accumulated timing offset of a modem goes to a negative value. The following error message is displayed on the CMTS:

"%UBR10000-4-BADTXOFFSET: Bad timing offset -182443 detected for cable modem 000a.73cc.c7b7. "

Conditions: This issue occurs on the Cisco uBR10-MC5X20 line card.

Workaround: There is no workaround.

CSCte07585

Symptoms: The standby PRE crashes during the cable modem entry cleanup.

Conditions: This issue is seen on the Cisco uBR10012 (PRE 2) running the Cisco IOS Release 12.2(33)SCB4. This issue is seen when there are many cable modems and service flows on the network and there is congestion between the active and standby Router Processors, which could lead to the IPC packet drop.

Workaround: There is no workaround.

CSCte19290

Symptoms: PRE crashes after OIR or crash of the cable line card.

Conditions: This issue occurs when a bundle member cable line card is removed from the system before it is removed from the running configuration. This crashes the active PRE and the cable line card. This problem does not occur with every OIR, however, it occurs when there is a punted packet associated with the OIR/crashed interface.

Workaround: Remove the cable line card from the bundle configuration (running config) before OIR of the card.

CSCtf48376

Symptoms: A crash occurs on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB5 with PRE-4.

Conditions: This issue occurs when the show cable modem ip service flow verbose command is executed several times.

Workaround: Delete the fiber node configuration and reconfigure it.

CSCti25339

Symptoms: Cisco IOS device may experience a device reload.

Conditions: This issue occurs when the Cisco IOS device is configured for SNMP and receives certain SNMP packets from an authenticated user. Successful exploitation causes the affected device to reload. This vulnerability could be exploited repeatedly to cause an extended DoS condition.

Workaround: There is no workaround.

PSIRT Evaluation:

The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are 6.8/5.6:

https://intellishield.cisco.com/security/alertmanager/cvssCalculator.do?dispatch=1&version=2&vector=AV:N/AC:L/Au:S/C:N/I:N/A:C/E:F/RL:OF/RC:C

CVE ID CVE-2010-3050 has been assigned to document this issue.

Additional information on Cisco's security vulnerability policy can be found at the following URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

CSCti81896

Symptoms: When the ingress cancellation feature is enabled, all modems on an upstream may momentarily go offline and then recover within minutes. This problem is not observed when the ingress cancellation feature is disabled.

Conditions: This issue occurs because the Rogue modems may transmit during ingress cancellation idle period. During this period, modems should not transmit. One or more modems consistently transmitting at this time period can create poor ingress cancellation performance for the burst receiver, and in the worst case situation, it can cause all modems to go offline momentarily until the upstream receiver re-adapts.

Workaround: Disable the ingress cancellation feature for that upstream, for which the rogue modems failures are encountered.

CSCtk09023

Symptoms: The service flow ID does not appear under scm service-flow main but appears under service-flow detail.

Conditions: This issue occurs with Cisco IOS Release 12.3(23)BCx, Cisco IOS Release 12.2(33)SCBx, Cisco IOS Release 12.2(33)SCCx and Cisco IOS Release 12.2(33)SCDx. The Cisco uBR10012 router may have service flow mismatch between the route processor and the cable line card when there is a high CPU usage by the line card or when there is a huge traffic load on the IPC bus due to mass cable modem registration events like an RF node failure. This affects both the upstream and downstream secondary service flows that are local or remote. When the downstream is remote, the CMTS reports 0 blaze index error for the affected downstream service flow.

For example,

scm 0011.e6fe.55ce service-flow
Sfid  Dir Curr  Sid   Sched  Prio MaxSusRate  MaxBrst   MinRsvRate  
Throughput 
          State       Type
26429 US  act   5290  BE     1    1024000     10000000  0           68         
26441 US  act   5296  NRTPS  4    64000       3044      32000       0 
<-- Here
26430 DS  act   N/A   BE     1    6600000     12000000  0           0          
26442 DS  act   N/A   BE     4    64000       96000     32000       0          
 
        
UPSTREAM SERVICE FLOW DETAIL:
SFID  SID   Requests   Polls      Grants     Delayed    Dropped    
Packets   
                                             Grants     Grants
26429 5290  86         0          86         0          0          30        
26439 5290  86         0          86         0          0          30        
<-- Here
 
        

Workaround: There is no workaround.

CSCtl79450

Symptoms: High CPU usage during SNMP polling using OID docsQosMacToSrvFlowTable.

Conditions: This issue occurs during SNMP query on the docsQosMacToSrvFlowTable when the cable interfaces are located at the end of the list resulting in a search loop.

Workaround: Stop querying this table.


Open Caveats for Release 12.3(23)BC9

Table 21 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(23)BC9.

Table 21 Open Caveats for Cisco IOS Release 12.3(23)BC9 

DDTS ID Number
Description

CSCsv63445

Symptoms: The clear cable modem command does not reset the modular-host tables.

Conditions: This issue occurs in the following conditions when you have:

not configured any fiber nodes.

brought some narrow-band modems online from the SPA downstream.

used the clear cable modem all reset command to reset the modems.

After execute the clear cable modem all reset command, all the statistics, baseline privacy interface (BPI), and payload header suppression (PHS) indexes in the modular-host tables are expected to be freed, but are not freed.

This causes a leak in the statistics, baseline privacy interface (BPI), and payload header suppression (PHS) indexes and raises a Cable Modem Transmission System (CMTS) scalability issue, that is, CMTS is unable to support the stated number of modems online from the SPA downstream.

Workaround: There is no workaround.

CSCsz22219

Symptoms: The Cisco uBR10000 series universal broadband router with PRE2 running Cisco IOS Releases 12.3(23)BC, Cisco IOS Releases 12.3(21a)BC, or Cisco IOS Releases 12.2(33)SCB crashes.

Conditions: This issue occurs when the PRE2 is running either Cisco IOS Releases 12.3(23)BC, Cisco IOS Releases 12.3(21a)BC, or Cisco IOS Releases 12.2(33)SCB, enabling ESR-HH-1GE. The cable source-verify dhcp command is executed but no cable line card is configured or inserted.

Workaround: Configure or insert the cable line card in the Cisco CMTS.

CSCsz49382

Symptoms: Cable modems do not respond to Layer 3 pings.

Conditions: This issue occurs only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U line cards when PRE-EQ (equalization-coefficient) is configured.

Workaround: Reset the cable line card.

CSCsz98503

Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs off a (random) upstream. These losses are usually accompanied by a spike of error per second rate or drop in modulation error ratio (MER) and a decrease in the docsIfSigQUnerroreds.

However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.

Conditions: This issue occurs on Cisco uBR10-MC5X20H line cards.

Workaround: There is no workaround.

CSCta32429

Symptoms: Non-bonding cable modems are wrongly registered in bonded channels.

Workaround: There is no workaround.

CSCta38298

Symptoms: Active PRE fails over to the secondary reporting.

Conditions: This issue is observed in Cisco IOS Release 12.3(23)BC7.

Workaround: There is no workaround.

CSCtb93407

Symptoms: The system logs record a line-card crash (8/0), which is immediately followed by a PRE failover.

Conditions: There is no query on the MIB object, cefcFRUPowerSupplyGroupTable, when the failover occurs.

Workaround: There is no workaround.

CSCtc39722

Symptoms: Modems do not come online, or once online quickly return to the offline state, on interfaces with modular remote primary.

The show cable modem primary summary total command displays the non-zero blaze indices stay non-zero:

Conditions: This issue occurs on a PRE failover event and when modems are on a domain that has only modular remote primaries.

This issue is observed on Cisco uBR10000 with PRE2 running Cisco IOS Release 12.3(23)BC7.

Workaround: Power cycle the affected line card.

CSCtc49858

Symptoms: If you have lower privilege levels than Enable Access, you may not be able to execute some show cable command options.

Conditions: This issue occurs because the parent privilege level is not carried over correctly. This issue is observed on the Cisco CMTS with the Cisco IOS Release 12.3BC, Cisco IOS Release 12.2SCB, and Cisco IOS Release 12.2SCC.

Workaround: Repeat the privilege level command for each interface.

CSCtc59089

Symptoms: The cable line card (CLC) crashes when a specific 3-way call scenario is initiated.

Conditions: This issue occurs where multiline AT attachments (ATAs) are placed behind CMs in a PCMM setup.

Workaround: There is no workaround.

CSCtc78090

Symptoms: The downstream frequency override (DFO) retry counter does not rise beyond the number zero.

Conditions: This issue occurs when you execute the cable service attribute ds-bonded downstream-type bonding-enabled [enforce] command and then power on and off the wideband cable modem.

Workaround: There is no workaround.

CSCtc78143

Symptoms: The standby PRE crashes with a value of signal 10 after a spurious memory access.

The crash only affects redundancy and has no impact on services.

Workaround: There is no workaround.

CSCtc99509

Symptoms: Cisco Wideband SPA sends only "sync Tx" packets.

Conditions: This issue is observed after Cisco Wideband SPA reloads and when a DOCSIS timing interface (DTI) server is used.

Workaround: Reload the jacket card, reload Edge Quadrature Amplitude Modulation (EQAM), and reboot.


Resolved Caveats for Release 12.3(23)BC9

Table 22 lists only severity 1 and 2 caveats and select severity 3 open caveats for Cisco IOS Release 12.3(33)BC9.

Table 22 Resolved Caveats for Cisco IOS Release 12.3(23)BC9 

DDTS ID Number
Description

CSCek76084

Symptoms: A packetcable validate type length value (TLV) traceback occurs after a release complete (RLC) upgrade.

Conditions: This issue is caused by an invalid service flow (NULL pointer). It occurs when a Dynamic Service Change (DSC) request is made. The DSC fetches the service flow from the service flow ID (SFID) and accesses it without checking whether the pointer is NULL.

CSCsg67817

Symptoms: Malformed H.245 packets crashes the IOS-based H.323 gateway.

Conditions: This issue occurs when the H.323 gateway is configured.

Workaround: There is no workaround.

CSCsj22874

Symptoms: The interprocess communication (IPC) connection between two line cards does not function correctly, which causes load-balance data synchronize information loss or HCCP synchronization loss. This issue also affects the Blaze index assignment if the Guardian line card is one of the affected line cards.

Conditions: This issue occurs when there are three or more Cisco 520 line cards in a router. This issue occurs during system bootup or if three or more line cards have crashed or have reset at the same time.

Workaround: If a service (Guardian, load-balance, or HCCP) or card is affected, reset the affected line cards.

CSCsk20999

Symptoms: In the object type syntax, ifStackEntry, the cable bundle interface is displayed as ifStackHigherLayer for modular downstream interfaces.

Conditions: This issue occurs when the ifStackEntry MIB object is queried using SNMP.

CSCsk78448

Symptoms: An error message is displayed when the show pxf cpu stati drop <interface> command is executed when the interface is not supported by toasters, such as Ethernet, FastEthernet, and so on.

Conditions: This issue occurs while executing the show pxf cpu stati drop command on interfaces, such as Ethernet, FastEthernet, and so on.

Workaround: There is no workaround.

CSCsw14622

Symptoms: For deleted service flows, the last character in the "Service Class Name" field is dropped from the Subscriber Account Management Interface Specification (SAMIS) records and the SNMP MIB object docsQosServiceFlowLogServiceClassName.

Conditions: This issue is seen when the dynamic service flows associated with PCMM calls are deleted. The last character is missing from the service class name in the MIB object "docsQosServiceFlowLogServiceClassName" and SAMIS records

Workaround: There is no workaround.

CSCsw51992

Symptoms: Invalid or corrupt values seen for OctetsPassed and PacketsPassed fields in the SAMIS records.

Conditions: This issue occurs in the Cisco CMTS with Wideband SPA configured while querying the service flow counters using SAMIS, SNMP, or executing the show commands.

Workaround: There is no workaround.

CSCsx19200

Symptoms: A cable line card (CLC) crashes when one of its upstreams is shut down.

Conditions: This issue occurs only if the upstream route and its associated downstream are configured in load-balance groups.

Workaround: There is no workaround.

CSCsx63989

Symptoms: The output "sid" is incorrect in the show cable modem x.x.x.x service-flow [verbose] command.

Conditions: This issue occurs in the Cisco IOS Release 12.3(23)BC and Cisco IOS Release 12.2(33)SCB.

Workaround: There is no workaround.

CSCsx70889

Symptoms: Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.

Workaround: Cisco has released free software updates that address this vulnerability.

This advisory is posted at http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20090923-tunnels

CSCsx94352

Symptoms: The wideband cable interface is not able to pass traffic.

Conditions: This issue occurs because the bonded channel to RF channel mapping configuration is missing from the SPA.

Workaround: There is no workaround.

CSCsy55647

Symptoms: The ESR-PRE2 processor module crashes and the crash information logs display the following:

%UBR10K-6-US_SFID_INCONSISTENCY: US-SF found: SFID xxxx, type 0, sid 
0(yyyy), MAC 
aaaa.aaaa.aaaa(bbbb.bbbb.bbbb), prim_sid xxx(yyy)CMD: 'no cable ser-
vice attribute 
voice-enabled downstream-type HA-capable'
 
        

Conditions: This issue occurs in Cisco IOS Release 12.3(23)BC4.

Workaround: There is no workaround.

CSCsy55849

Symptoms: The show controller modular-cable command output displays invalid voltage measurement readings.

Conditions: This issue occurs on the 24 RF channel SPA.

Workaround: Re-execute the show controller modular-cable command.

CSCsy66170

Symptoms: After a PRE switchover, the wideband interfaces status on SPA drop offline. The wideband modems on these wideband interfaces also drop offline.

Conditions: This issue occurs when the primary PRE and secondary PRE boot up at same time.

Workaround: Boot up the secondary PRE much later than the primary PRE, or boot up the secondary PRE when the primary PRE is already up and running.

CSCsz38104

Symptoms: The H.323 implementation in Cisco IOS software contains a vulnerability that can be exploited remotely to cause a device running Cisco IOS software to reload.

Cisco has released free software updates that address this vulnerability.