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

October 18, 2004

Cisco IOS Release 12.3(9a)BC

OL-6760-01

These release notes for the Cisco uBR10012 universal broadband router document the cable-specific, early deployment 12.3 BC train, describing the enhancements and caveats provided in Cisco IOS Release 12.3(9a)BC. This release includes features in previous Cisco IOS 12.3BC 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(9a)BC, see the "Caveats" 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.3 T located on Cisco.com and the Documentation CD-ROM.

Note You can find the most current Cisco IOS documentation on Cisco.com. This set of electronic documents may contain updates and modifications made after this document was initially published.

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/warp/customer/770/index.shtml. If you do not have a Cisco.com login account, you can find field notices at http://www.cisco.com/warp/public/770/index.shtml.

These release notes describe the following topics:

• Early Deployment Releases

• System Requirements

• Feature Support

• New and Changed Information

• Important Notes

• Caveats

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

Early Deployment Releases

These release notes describe the Cisco IOS Release 12.3(9a)BC for the Cisco uBR10012 universal broadband router. Feature support is cumulative from release to release, unless otherwise noted.

Table 1 lists any features supported by the Cisco uBR10012 router in Cisco IOS Release 12.3(9a)BC. For complete feature information, refer to these additional resources on Cisco.com:

•Cisco uBR10012 Universal Broadband Router Performance Routing Engine Module 2

http://www.cisco.com/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/frus/ub10pre.htm

•Field Replaceable Units (FRUs) documents for the Cisco uBR10012 router:

http://www.cisco.com/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/frus/index.htm

•Cisco uBR10012 Universal Broadband Router Software Configuration Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/scg/index.htm

•Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/

Table 1 Early Deployment (ED) Releases for the Cisco uBR10012 Router
ED Release	Additional Software Features¹ and MIBs²	Additional Hardware Features	Hardware Availability
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

¹Only major features are listed.

²MIB = Management Information Base

System Requirements

This section describes the system requirements for Cisco IOS Release 12.3(9a)BC and includes the following sections:

• Memory Recommendations

• Hardware Supported

• Determining Your Software Release

• Upgrading to a New Software Release

Memory Recommendations

Table 2 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR10012 universal broadband router for Cisco IOS Release 12.3(9a)BC.

Table 2 Memory Recommendations for the Cisco uBR10012 Routers, Cisco IOS Release 12.3(9a)BC Feature Sets
Feature Set	Cisco uBR10012 Route Processor	Software Image	Recommended Flash Memory	Recommended DRAM Memory¹	Runs From
DOCSIS BPI IP Plus	PRE1	ubr10k-k8p6-mz	48MB	512 MB	RAM
DOCSIS BPI IP Plus	PRE2	ubr10k2-k8p6-mz	48MB	1.0 GB	RAM
DOCSIS Base 3 DES	PRE1	ubr10k-k9p6-mz	48MB	512 MB	RAM
DOCSIS Base 3 DES	PRE2	ubr10k2-k9p6-mz	48MB	1.0 GB	RAM

¹DRAM memory is not configurable on the Cisco uBR10012 router.

Hardware Supported

For detailed descriptions of the new hardware features, see the "New Hardware Features in Cisco IOS Release 12.3(9a)BC" section. Cisco IOS Release 12.3(9a)BC supports the following hardware on Cisco uBR10012 routers:

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 broadband processing engines •Cisco uBR10-LCP2-MC16C/MC16E/MC16S cable interface line cards •Cisco uBR10-LCP2-MC28C cable interface line cards 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.
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.

Determining Your Software Release

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

Router> show version

Cisco Internetwork Operating System Software

IOS (tm) 12.3 BC Software (uBR10k-k8p6-mz), Version 12.3(9a)BC, RELEASE SOFTWARE

Upgrading to a New Software Release

For general information about upgrading to a new software release, see Cisco IOS Upgrade Ordering Instructions located at: http://www.cisco.com/warp/public/cc/pd/iosw/prodlit/957_pp.htm.

Feature Support

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/register

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(9a)BC.

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(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" section

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

• "Virtual Interface Support for HCCP N+1 Redundancy" section

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/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/frus/ub_oc48.htm

•Configuring the Cisco uBR10012 OC-48 DPT/POS Interface Module

http://www.cisco.com/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/ub10ksw/oc48pre2.htm

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/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/frus/index.htm

•Quickstart Guide to the Cisco uBR10012 PRE-2 Performance Routing Engine Module 2

http://www.cisco.com/univercd/cc/td/doc/product/cable/ubr10k/ubr10012/frus/index.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ufg_docs.htm

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, 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/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122bc/122bc_15/cblarpfl.htm

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/univercd/cc/td/doc/product/cable/trblshtr/cbt32/cbt32rn.htm

•Spectrum Management for the Cisco CMTS

http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ufg_spec.htm

•Subscriber Traffic Management for the Cisco CMTS

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122bc/122bc_15/ubsubmon.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/stat_cpe.htm

•Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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:

• "Obtaining Documentation" section

•Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122bc/122bc_15/ubrdsg.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/ubrdmic.htm

•Cisco Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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 for the Cisco Cable Modem Termination System

http://www.cisco.com/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/ethrchan.htm

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

• DSG-IF-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/univercd/cc/td/doc/product/cable/cmtsmib/

•SNMP Object Navigator

http://www.cisco.com/pcgi-bin/Support/Mibbrowser/unity.pl

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/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/ubrsamis.htm

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.

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 5 lists the byte definitions for Netflow Version 5 header format.

Table 5 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).¹
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.

¹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 6 lists the byte definitions for Version 5 flow record format.

Table 6 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 3 lists definitions for terms used in the version 8 header.

Table 7 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/products/sw/iosswrel/ps1828/products_configuration_guide_chapter09186a00800ca62d.html

•NetFlow Overview, Version 8

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800ca6cb.html

•Configuring NetFlow (Versions 1 and 5)

http://www.cisco.com/en/US/products/sw/iosswrel/ps1826/products_configuration_guide_chapter09186a00800880f9.html

•Configuring NetFlow (Version 8)

http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_configuration_guide_chapter09186a00800ca6cc.html

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a00800ca7f8.html

•Cisco IOS NetFlow documentation home page

http://www.cisco.com/warp/public/732/Tech/nmp/netflow/netflow_documentation.shtml

•Cisco IOS NetFlow White Papers

http://www.cisco.com/warp/public/732/Tech/nmp/netflow/netflow_techdoc.shtml

•Cisco IOS Software Home Page for NetFlow

http://www.cisco.com/warp/public/732/Tech/nmp/netflow/index.shtml

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/products/hw/cable/ps2217/products_feature_guide_chapter09186a008019b576.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/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ufg_bund.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/ufg_spec.htm

•Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/univercd/cc/td/doc/product/cable/trblshtr/cbt32/cbt32rn.htm

• "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 1.1 works with Network-Based Application Recognition (NBAR) and Access control lists (ACLs) to ensure full network performance to other network subscribers that abide by their service agreements. 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/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122bc/122bc_15/ubsubmon.htm

•Release Notes for Cisco Broadband Troubleshooter Release 3.2

http://www.cisco.com/univercd/cc/td/doc/product/cable/trblshtr/cbt32/cbt32rn.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cfig_nts/tls-cmts.htm

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/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ubrsamis.htm

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/univercd/cc/td/doc/product/software/ios122/122newft/122limit/122bc/122bc_15/mc5x2vif.htm

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/products/hw/cable/ps2217/products_feature_guide_chapter09186a008015096c.html

•Configuring Virtual Interfaces on the Cisco uBR10-MC5X20S/U Card

http://www.cisco.com/en/US/products/hw/modules/ps4969/products_feature_guide09186a00801b17cd.html

Important Notes

The following sections contain important notes about Cisco IOS Release 12.3(9a)BC that apply to the Cisco uBR10012 universal broadband router.

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/univercd/cc/td/doc/product/cable/cab_rout/cmtsfg/ufg_cmon.htm

Cisco Broadband Cable Command Reference Guide
http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/bbcmtscf.htm#wp1130717

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 Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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 Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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 Broadband Cable Command Reference Guide

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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 8 describes the fields displayed by the show controllers cable downstream command.

Table 8 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 Broadband Cable Command Reference Guide (update posted at FCS)

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

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.

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 Broadband Cable Command Reference Guide (update posted at FCS)

http://www.cisco.com/univercd/cc/td/doc/product/cable/bbccmref/index.htm

Caveats

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.

Caveat numbers and brief descriptions for Cisco IOS Release 12.3(9a)BC (only) are listed in this section.

Cisco IOS Release 12.3M is the parent release train for Cisco IOS 12.3(9a)BC. Unless otherwise noted, Cisco IOS Release 12.3(9a)BC maintains support for the changes and caveat resolutions introduced in earlier releases of Cisco IOS Release 12.3M.

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 to enter the following URL in your web browser or go to
http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

Open Caveats for Release 12.3(9a)BC

Table 9 lists only severity 1 and 2 caveats and select severity 3 caveats for the Cisco IOS 12.3(9a)BC release.

Table 9 Open Caveats for Cisco IOS Release 12.3(9a)BC
DDTS ID Number	Description
CSCeb25866	Under certain conditions, the number of service flows on an interface, as reported by "show cable load-balance load", does not match the real number of service flows. There are no known workarounds.
CSCec04915	Intermittent ping failure is seen on the GE. There are no known workarounds.
CSCec35079	Under certain load conditions, modems may be stuck in init(rc) or other pre-registration states. This can occur if upstream service flows have a high priority and a guaranteed minimum bandwidth, and if the upstream capacity is completely consumed by traffic associated with such service flows. In this condition, new modems trying to come online may not receive any bandwidth grants, and may thus be stuck forever in init(rc) or other pre-initialization states until the traffic is reduced. With some modem types, it is also observed that affected modems start to request bandwidth with SID 0. Note that this condition _only_ occurs if, with above mentioned conditions, the upstream utilization is _constantly_ at its capacity, i.e., well above 90%. The upstream utilization can be checked with the command show interface <interface> mac-scheduler <n> where <interface> is the cable interface and <n> is the upstream channel. The output of this command will include the line Avg upstream channel utilization : xx% The problem described in this ddts entry will only be seen if "xx" is constantly above 90% (and if upstream flows have a guaranteed minimum bandwidth). There are no known workarounds.
CSCed07010	If before the PRE switchover, the protect interface was in Shut state and we do a no-shut after the PRE switchover, the protect interface may stay stuck in NON_FUNCTIONAL state. Workaround: Do a hw-module reset of the protect interface.
CSCed89210	When there is heavy traffic on the backhaul interface and the uBR10k is reloaded, then it is possible that the PXF gets reloaded 20 seconds after bootup, with an error message: C10KEVENTMGR-1-MINOR_FAULT: PXF DMA New Work Queue High Error' Workaround: Ensure that the traffic coming to the router is not very heavy immediately after bootup.
CSCee00895	In the uBR10k, packets switched by PXF are counted as process switched packets for the backhaul interfaces. These erroneous counts are displayed in "show interface switching" output.
CSCee32618	The CMTS may report the following error and trace back: `%GENERAL-3-EREVENT: No current_if_info` There are no known workarounds.
CSCee39660	The CMTS may report a traceback error during a PRE switch over. There are no known workarounds.
CSCee41060	pstream Timing offsets not synced over to Protect linecard causing modem time alignments and drop packets. Workaround: Wait for a new modem to come online or a modem to flap, or shut/no shut the affected upstream port(s). Alternative workaround: Configure a high safety value in the dynamic map advance CLI command.
CSCee62626	For systems with 25K or modem modems, the RP will become sluggish and the modem registration will become extremely slow. Workaround: Shut down bundle slaves or other LCs until approximately 75% of the modems on the non shut cards have registered, then no shut the shut down cards.
CSCee94943	SID not provided when running command "sh hard pxf cable source-verify". This issue was seen internally while testing modem reset the modem needs to be assign to a subinterface via DHCP. There are no known workarounds.
CSCef01314	The RF Switch takes 2~5 seconds for an SNMP-response. When doing "sh hccp channel switch", it is talking to each module in the RF Switch that comprises the bitmap and taking an extremely long time to timeout, instead of just talking to the RF Switch to verify connectivity. The snmp RW string is "private" by default, but can be changed in the RF Switch. If the RW "private" string is changed or deleted in the uBR, it could have adverse affects on communications between the devices as well. Workaround: Make a hard-break possible to stop the command from executing. Then do "sh hccp g m channel" to look at each individual member of a group individually.
CSCef14781	The PRE may report the error below during a PRE swicthover: `%UBR10K-3-QUEUEFULL: Unable to enqueue since the queue is full` There are no known workarounds.
CSCef28979	If the host IP address is changed after the CM is online, the host IP address is not synched to the Standby PRE or Protect LC. This would cause delays in traffic recovery after a PRE or LC switch-over. There are no known workarounds.
CSCef30185	The following "Unknown type" error messages may appearing at the CMTS console after the following actions do N+1 switchover (or) shut/noshut on cable interface: `Jul 29 09:06:44.899: Unknown type 16843263` `Jul 29 09:06:44.899: Unknown type -16709634` There are no known workarounds.
CSCef31547	Cisco modems and possibly modems using BRCM3300 chip could have timing problems and ranging issues on the MC520s card when running in sparse mode. There are no known workarounds.
CSCef36045	Bundle entries on ubr10000 do not get aged. There are no known workarounds.
CSCef48680	A uBR10K running 12.2(15)BC2b may experience multiple PRE reloads and switchovers due to keepalive timeout triggered because of IPC cache exhaustion. The following messages are seen in the logs before the reload: `%IPC-3-NOBUFF: The main IPC message header cache is empty` `-Traceback= 6062E120 6062EA28 6062E990 60622CE4 606243A4 60E1464C 6065F90C 6068DB48 60034980` `%C10K-2-RPRTIMEOUT_CRASH: Performing crashdump and switchover due to keepalive timeout` `%Software-forced reload` The Primary PRE performs a switchover to the Secondary PRE automatically. There are no known workarounds.
CSCef49675	CMTS CPE Host entry will be deleted if after the arp time-out the arp response is not received from CPE, and arp refresh fails, in which case the arp entry is also deleted. However there are certain cases which is not consistent with the above behavior, and where the arp entry is deleted but the host entry is not deleted. These cases are as follows: 1. If line protocol on the master interface flaps. 2. If the interface ip address is removed and added again. 3. If Sub-interface is deleted and re-added. 4. If Dynamic Arp entry is removed by using the config command no arp
CSCef52564	It is possible when using the ubr10k with RF Switches and HA configured that DOCSIS sync message restoration does not resume within the specification requirement of <200 msec. There are no known workarounds.
CSCef54302	A uBR10K with redundant PREs might run into a situation where dir on sec-disk0: and sec-bootflash: does not yield relevant output. The error message "Error Sending Request" is generated when a "dir sec-disk0:" and "dir sec-bootflash" is performed. This issue may occur due to heavy load (huge number of cable modems on the CMTS). There are no known workarounds.
CSCef55523	A uBR10012 CMTS running IOS 12.2(15)BC2d may not pass traffic on Gigabit Ethernet interfaces after a reload/upgrade. Workaround: Reload the CMTS.
CSCef60827	A ubr10012 running 12.2(15)BC2d could hang if OSPF hello packets are sent out the cable interface. Note that OSPF adjacencies are not supported on cable interfaces. Workaround: Configure all cable interfaces as "passive-interface".
CSCef61006	After a PRE switchover, standby PRE reloads unexpectedly when configuration mode is entered and exited on the active PRE. Workaround: Wait until the standby PRE is in Hot Standby before entering the configuration mode on the active PRE.
CSCef64537	HCCP unlock command causes a CMTS to reload intermittently. This issue is observed with the HCCP unlock command. There are no known workarounds.
CSCef66578	The output of "show cable modem connectivity" display huge value. This issue occurs in Cisco IOS software version 12.2(15)BC2b and 12.2(15)BC2c. There are no known workarounds.
CSCef67230	A 520 card can loose its IPC connectivity to its PRE causing the PRE to fail keepalive to the card and subsequently resetting the CLC causing all modems on the 520 card to go offline. There are no known workarounds.
CSCef75363	After a N+1 switchover, the ARP entry for CPE devices may not be automatically created until subscriber traffic forces an ARP refresh. This may add a small delay to traffic recovery during the ARP request/response exchange. Workaround. CPE traffic will recover without any user intervention.
CSCef78175	For cm-created qos profiles for docsis 1.0 modems, on a ubr10000 after a "clear cable modem all delete", if an LC switchover is initiated, the qos profile internal reference count used in addition/deletion of qos profiles will get messed up - the switchover leads to incorrect values for reference count on the PRE and the switched over LC. There are no known workarounds.
CSCef79820	The mac-scheduler is not cleared properly with non packetcable call. As a result, the mac-scheduler is full little by little after every a call and can not make a call due to DSA_MULTIPLE_ERRORS. This issue occurs in the docsis-mode is tdma-atdma (mix) mode in Cisco IOS software version 12.2(15)BC2a later. Workaround: Use "cable upstream x shutdown" and "no cable upstream x shutdown".
CSCef86372	A UBR10K may reload unexpectedly. The following unusual entry was observed in logs just before the reload: `%C10K-5-REDCHANGE: EHSA Register changed Prev.` This issue could be related to redundancy configured with no standby PRE. There are no known workarounds.
CSCef87118	In version 12.2(15)BC2c, the DHCPD Receive process may hold memory when DMIC is used. When DMIC is used, about 368 bytes of memory is lost on the CMTS for each config file used for the modem. This loss would keep growing till the system runs out of memory. There are no known workarounds.
CSCef87302	Add Option 82 to DHCPRENEW & DHCPRELEASE messages that pass through the CMTS which is a relay agent. The feature has to be implemented for both modem and CPE DHCP traffic. There are no known workarounds.
CSCef92997	UBR7200 unexpectedly reloads with software forced reload after: `Aug 10 13:58:27.692: %SYS-2-FREEFREE: Attempted to free unassigned memory at 638BB58C, alloc 60945BC4, dealloc 60946A9C` `Aug 10 13:58:27.696: %SYS-6-BLKINFO: Attempt to free a block that is in use blk 638BB564, words 118, alloc 60945BC4, Free, dealloc 60946A9C, rfcnt 0` `Aug 10 13:58:27.728: %SYS-2-MALLOCFAIL: Memory allocation of 328 bytes failed from 0x60914A58, alignment 0` `Pool: Processor Free: 408351600 Cause: Mempool corrupt` `Alternate Pool: None Free: 0 Cause: No Alternate pool` There are no known workarounds.
CSCef93561	With a large number of modems, the system may report IPC errors during a N+1 switch over. There are no known workarounds.
CSCef93714	Illegal cloned modems still receive Cable service even in reject (pk) state. There are no known workarounds.
CSCin79597	In a fully loaded CMTS, after doing a OIR on working CLC some of the modems, may get reset on some Downstreams. There are no known workarounds.

Resolved Caveats for Release 12.3(9a)BC

Table 10 lists only severity 1 and 2 caveats and select severity 3 caveats for the Cisco IOS 12.3(9a)BC release.

Table 10 Resolved Caveats for Cisco IOS Release 12.3(9a)BC
DDTS ID Number	Description
CSCea08812	If a client leaves the multicast group the CMTS will continue to forward multicast traffic on that interface. This issue is observe when running multicast over bundle interfaces. This only causes a performance problem because unnecessary traffic is consuming the available bandwidth. There are no known workarounds.
CSCea68692	If the crypto key generate rsa command is configured on a Cisco uBR10K CMTS with dual performance routing engines (PREs), the command fails to synchronize to the secondary PRE. This issue is a duplicate of CSCdw08393. This issue is observed with a crypto key generate rsa command with dual PRE on uBR10K. Workaround: Reset the secondary PRE.
CSCea82892	The clear cable flap-list all save-counters does not save the counters. This issue is seen only in ubr10k. There are no known workarounds.
CSCeb71709	The uBR can only support 1 root certificate, which means that which ever certificate is loaded (North American) or European, BPI+ can only be enabled for those cards on which that type of certificate is loaded. There are no known workarounds.
CSCec07639	When DMIC is configured and a large number of cable modems attempt to connect to the CMTS at the same time, the system may experience high CPU utilization and the modem may have trouble going past state init (o) and may even reset and re-range. The issue is particularly severe when a large number of Cisco cable modems are connected to the system and the config file is greater than 4096 bytes in size. Workaround: Disable DMIC. Alternative Workaround: Edit the config file so that it is less than 4096 bytes in length.
CSCec27338	Network Based Access Recognition (NBAR) is used to classify packet streams. When packet streams contain packets that are fragmented it's important that all the fragments for a packet traverse the same router running NBAR. If some packets are dropped or routed around a particular router running NBAR then that can cause high CPU. This is a result of the fragment table getting too large when all fragments of a packet are not presented to NBAR. There are no known workarounds.
CSCec48483	Upon reloading both the Active and Standby PREs, after the system comes up, the protect line card comes up fine. But the working line card is in down state. This is a rare condition that is not easily reproducible. Workaround: hw_module reset the working line card.
CSCec68998	Per interface diversion counts are not available in uBR10k. Further, the number of these packets being enqueued to the process level is also not available through any show command. There are no known workarounds.
CSCec83821	The CMTS may fail to register modems correctly when the TFTP-Enforce command is enabled. The CMTS may display the message below: `%UBR10000-4-REGISTRATION_BEFORE_TFTP_MARK: Registration request unexpected: Cable Modem did not attempt TFTP. Modem marked with #. CM Mac Addr <xxxx.xxxx.xxxx>` There are no known workarounds.
CSCed21438	The CMTS rewrites the IP source of the DHCP OFFER to the pc client and changes it to the PRIMARY subnet on the Cable interface which breaks ACL's that are installed in the CM DOCSIS config file. This issue occurs when running "cable dhcp-giaddr policy" where the relay- agent is smart enough to decide how to populate the giaddr with the correct subnet depending whether the BROADCAST is coming from a PC or cable modem. The CMTS is following the rule according to RFC 1542 with regards to the giaddr, yet the spec does NOT specify clear cut rules for the source IP address of the packet. Cisco implementation rewrites the IP Source to the cable modem subnet during the OFFER. This is not wrong but under certain conditions where security filters reside in the DOCSIS config file get broken. There are no known workarounds.
CSCed26897	Every frequency hop leads to an upstream re-init which in current SW can case a 300ms delay in servicing UGS. The issue is made more sever because frequency hopping on upstreams that have no modems on them is happening to frequently and a result cases a lot of UGS interruption There are no known workarounds.
CSCed29019	When C10K gige card is directly connected to cat4k gige card, link negotiation between the two fails. C10K says that link is UP, cat4k says link is DOWN. A 15 msec delay is needed to allow autonegotiation between these 2 interfaces. There are no known workarounds.
CSCed46270	In rare circumstances, the traceback described in this DDTS may be seen on the RP console. This is caused due to a race condition in the previous HCCP switchover. Traffic to and from modems on the subinterface affected will be impacted. Workaround: Perform another HCCP (LC) switchover to clear the problem.
CSCed49070	The standby PRE could reload during boot up due to inconsistencies. No action is required by the user. There are no known workarounds.
CSCed53225	Due to excessive memory fragmentation, call to malloc fails even though available free memory may be greater than the requested size. There are no known workarounds.
CSCed55021	A CMTS with a large number of cable modems connected may exhibit high CPU in the DHCPD Receive process as many cable modems all attempt to come online. As modems come online successfully, the CPU utilization will gradually decrease. This issue may be exacerbated by having an unusually large number of secondary IP addresses configured on cable interfaces. Workaround: Reduce the number of secondary IP addresses configured on a cable interface. Alternative workaround: Deliberately reduce the rate at which cable modems may come online by manually increasing the cable insertion-interval to a large value such as 250 or 500ms.
CSCed65223	Similar issue has been reported in CSCea05180 for the 10K routers. However, UBR10000 is also encountering the same issue. Basically, the ifHCOutOctets counters are impossibly high for gig interfaces. This issue has seen on UBR10000 running 12.2(15)BC1. However, ifHCInOctets counters seem to be fine. There are no known workarounds.
CSCed65409	Bogus ARP entries are created when multiple DHCP servers reply with their offers. This can significantly increase memory consumption when many CMs are trying to register. It also causes the router to perform unnecessary arp entry addition. This is a result of bad sync. There are no known workarounds.
CSCed68829	Some modems might not be queried from SNMP cdxCmCpeTable and linecard CLI "show cable device access-group". Workaround: shut/no shut cable interface.
CSCed68879	Running 12.1(15)BC1b, and noticed that for some of his MC16S cards, snmp returns a value for docsIfSigQSignalNoise that seems about 1000x higher than expected, whereas CNR measurement on the interface shows that noise is in range Workaround: For MC16S cards use the CNR value from 'show interface cable' command line output rather than snmp response from docsIfSigQSignalNoise for problem determination. There are no known workarounds for MC16B and/or MC16C cards.
CSCed70180	Certain modems, when configured in routing mode, might not be able to pass IP traffic when DMIC is enabled on the CMTS with IOS version 12.2(15)BC1b. The cable modem is able to ping the directly connected interface on the CMTS but it cannot ping beyond the CMTS. An extended ping from the CMTS to the cable modem RF interface also fails. Workaround: Disable DMIC on the CMTS.
CSCed71560	UBR10K running 15BC1b fails dhcp for CPE inside a Motorola DCT5000 when no bundle entry is found for an incoming dhcp packet. The issue is restricted to only such settop boxes - modems always come online ok on the same ubr10k and cable line card. Workaround: Follow the following steps: 1. Feed the failing DCT CPE mac addr to the following CLI: `sh ip arp vrf internet <CPE mac addr>` The CLI output will give you the cable interface(s) that has to be cleaned up for offending IP addr entries in the CMTS bundling table. 2. To find out offending IP entries in the CMTS bundle table, use the CMTS hidden CLI of: `sh int cx/y/z buck rp` Any "host" entry in the output that has the IP field "unavailable" is an offending entry. This entry has to be removed from the CMTS by invoking: `clear cable host <offending IP's mac addr>` 3. Once all offending CMTS bundle entries are removed, reload the modem in the DCT5000 and now both modem and CPE will show up as registered on the CMTS.
CSCed72979	Cable Line Cards may become unresponsive under certain conditions. If this happens, the card will go offline, but it will not reboot itself. It has to be reset manually using the hw-module reset command. There are no known workarounds.
CSCed75425	Clearing counters on a uBR10k can cause SRP interface rate counters to be incorrectly reset to 0. There are no known workarounds.
CSCed76837	If there are lots of CM/CPE in the linecard, the SNMP query MIB tables related the CM/CPE info will possibly have SNMP-3-CPUHOG message and trackback. Also the CM/CPE may have connection problem (drop offline or lose VPN). The MIB tables are listed below. They are all invoke the same API to get the sorted table which the entry is searched. `CISCO-DOCS-EXT-MIB:cdxCmCpeTable,` `DOCS-IF-MIB:docsIfCmtsMacToCmTable` `DOCS-QOS-MIB:docsQosCmtsMacToSrvFlowTable` `CISCO-DOCS-REMOTE-QUERY-MIB:cdrqCmtsCmStatusTable` After the fix: 1. All the SNMP query for above tables will get info from RP/NPE only, so LC will not be affected. 2. The SNMP query Get EXACT will have real time response. 3. SNMP Get NEXT for above MIB tables is too expensive in a big system since it needs to go through whole CM/CPE in order to know which CM/CPE is the next entry of the query. Users are recommended to use SNMP GET EXACT to retrieve the info for a specific device. In order to prevent CPU spiking for GET NEXT for above MIB tables, In the CMTS which number of devices (CM/CPE) is greater than 1000, the SNMP query GET NEXT will not get any entries returned. GetBulk has also the same problem as GetNext since internally, it searches for the next entry. GET NEXT/GET BULK support is back via CSCed90740.
CSCed76871	The CMTS may print the following messages after an extended period of calls which caused by some MTAs sending messages with old gate ID. There is no effect for ongoing calls nor the new calls to be established: `Pktcbl(gdb): Fail to find IE, gate=<gateid>` There are no known workarounds.
CSCed79616	Specific running configuration may not be synched to the Standby PRE. After switch-over, behavior is cannot be predicted. Workaround: Do not configure the CMTS from multiple VTY sessions.
CSCed83401	This issue is found by reviewing the code. Whether it happens and what form it takes is unknown. There are no known workarounds.
CSCed83593	Dangling DS service flows This issue occurs with LC switchovers. There are no known workarounds.
CSCed84052	On the uBR10k, the throughput for a backhaul queue can decrease significantly intermittently. This issue will rectify itself when the affected queue or some other queue on that affected link becomes active (packets get enqueued to an empty queue) or becomes inactive (queue is drained and becomes empty. This issue is less of an issue in the production environment where the pair of default queues on the GigE are continuously being used and so are going active and inactive. If instead, there are 2 GigE links with the backhaul routes being equal cost paths, only one queue will be used per GigE link so that the chance of another queue coming active is lower. Even in this case, when the high priority queue goes active or inactive due to routing protocol traffic, the problem will be fixed automatically. There are no known workarounds.
CSCed86358	A cable line card running IOS may crash. In some cases if the card does not have enough memory, it will crash to ROMMON and will not automatically reboot. This issue may occur under the following conditions: •HCCP must be configured on the linecard •Secondary service flows must be configured via the cable modem config file •A modem must have at one time been online and then gone offline and remain offline during an hccp switchover. The service flows for that modem are not deallocated when it goes offline and are the source of the crash. •Performing a "show cable tech" or "show int CableX/Y/Z sid" after the switchover will access the sids that were not deallocated and may crash either the card that has become Active or, if another switchover is done, the card that is Standby. There are no known workarounds.
CSCed87070	A ubr10000 Series router with mc5x20 cards may produce the following error when Spectrum Groups are added: `router#cable upstream 1 spectrum-group 14` `Mar 3 10:17:07.213: %UBR10000-3-NOMEM: No more inuse sets.` `router#cable upstream 1 spectrum-group 14` `Mar 3 10:17:07.213: Cable5/0/0 U1: shared attach failed` CPU subsequently spikes to 90% mostly in the interrupt context. A reload may be required in order to recover. There are no known workarounds.
CSCed87675	IPM stuck is prematurely triggerred, when it is indicated in the overrun register, also punt packets per interface are accounted better. There are no known workarounds.
CSCed87992	Low bandwidth downstream service flows can get more than the configured max_rate if the packet size in the flow is large. Workaround: Configure max_rate to be greater than 100kbps.
CSCed89815	A bus error may occur on a Cisco router when you enter the trace command such as, for example, the trace www.a.net command. When you enter the show version EXEC command, the following error messages may be displayed: `System returned to ROM by bus error at PC 0xXXXXXXXX, address 0xYYYYYYYY` `0xXXXXXXXX represents the program counter at which the router reloads;` `0xYYYYYYYY represents the address at which the router reloads.` This issue is observed on a Cisco router that runs Cisco IOS Release 12.2(15)BC1 but may also occur in Release 12.3 or 12.3 T. For more information on bus errors, refer to the following URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1831/products_tech_note09186a 00800cdd51.shtml There are no known workarounds.
CSCed91422	The RP CPU on a uBR10k can go to 100% while handling invalid packets being sent from the CPEs on the upstream when source-verify or source-verify dhcp is configured. There are no known workarounds.
CSCed91708	On MC520 cable line cards, the input packet rate and input bit rate, as shown in the show interface <interface> command, can become very small when the input packet count is greater than 2^31, but has not yet wrapped back to 0. The input rates will return to correct values when the input packet count has wrapped through 0. There are no known workarounds.
CSCed92381	This issue will happen if each cable interface of a Cable line card does not share the same TEK lifetime. Workaround: Make all cable interfaces of a Cable line card share the same TEK lifetime.
CSCee01374	The PRE may unexpectedly reloads when multiple simultaneous config sessions are executed via VTY and HCCP is configured in the cable interfaces. There are no known workarounds.
CSCee01627	In 12.2(15)BC2a and BC2b, on a ubr10k, for bursty traffic, packets can be erroneously marked as non-conforming even when the average data rate is below the configured max rate. There are no known workarounds.
CSCee02150	After a CMTS is loaded, the "IP Input" process is consuming a few percentage points of the CPU as shown by 'show proc cpu sort'. It is possible that worms on CPEs behind modems are scanning IP ports in the network. This will result in arp request packets being broadcast and passing through the arp filter. This change allows the operator to see on a per-modem basis which modems are the highest source of the traffic and thus which end users and modems to focus on for applying counter-measures such as ACLs. There are no known workarounds.
CSCee03345	If on a system with hccp configured, the protect line card unexpectedly reloads and then hangs during crashinfo collection, it may lead to sync-pulse failure on all the other working line cards and followed by power cycle of all the working line cards There are no known workarounds.
CSCee08163	The PRE may hang during an N+1 line card switchover with "cable source verify dhcp" enabled. It is caused due to a race condition in the code. There are no known workarounds.
CSCee08290	If modems are deleted/reset in bulk using the clear cable modem all delete/reset command, it may cause a CPU-Hog message or may sometimes cause the cable line card to reset. There are no known workarounds.
CSCee11695	When the CMTS is configured with "cable source-verify dhcp", and bundling is configured, and ip pkts from CPE are being source verified, the lease query response may be incorrectly dropped, leading to the CMTS continuously sending lease query requests and dropping lease query acks. There are no known workarounds.
CSCee13327	Fib index may not be correctly set for DHCP CPE's in pxf source-verify tables (affects mainly customers with MPLS VPN and source-verify dhcp configured) The output of "show pxf cable source-verify \| i <sid>" will show different Fib Index for CM and CPE or multiple entries for the same IP address and SID but different Fib index. Workaround: Do not configure "cable source-verify [dhcp]".
CSCee14029	Excessive source verify punts to the RP on the uBR10k can render the router unusable temporarily. Workaround: Unconfigure source-verify.
CSCee15965	Executing "show srp topology" for a uBR10k OC-12 SRP linecard gives false "Last received topology pkt" and "Last topology change was" values. This issue occurs when the OC-12 SRP card is on the ring, interface up, transmitting topology packets. No other particular conditions. There are no known workarounds.
CSCee16606	Cable intercept might not send copy of Downstream packets to the collection server, only Upstream packets might appear on the collection server. This issue is seen with IOS 12.2(15)BC1b image. There are no known workarounds.
CSCee20385	Under some congestion/traffic conditions, routing updates such as ISIS may get dropped. There are no known workarounds other than to investigate and throttle the traffic conditions causing the congestion.
CSCee20869	In order to protect from DOS service attacks on the CMTS, it is decided to add per SID basis throttling of lease queries and global rate limit for lease queries initiated by downstream traffic. This is meant to reduce the CPU utilization of DHCP Receive process & ISR context when "cable source-verify dhcp" and "no cable arp" is configured. There are no known workarounds.
CSCee21114	When "source-verify dhcp" and "no cable arp" is configured, DHCP lease query response for dst address of pkts coming from the back-haul is dropped. CPE is unreachable from the back-haul until the CPE itself send an ARP or IP packet. Workaround: Do not configure "no cable arp".
CSCee22333	Working line-cards may reload during a LC switch-over. The number of line-cards that fail is random. There are no known workarounds.
CSCee24107	The slot preference algorithim gives preference to PRE-A to become the active after a reload. This algorithm sometimes was not working, and PRE-B become the active on reload. Workaround: Do a PRE swtichover (redundancy force failover) if PRE-B became active.
CSCee24435	After the PXF is reloaded in a uBR10k, some CMs may get stuck in init (o) or init (t) state. Workaround: "clear cable modem <mac> delete" for these CMs.
CSCee24903	CMTS crashes when issuing show hard pxf cpu context command. There are no known workarounds.
CSCee25855	The Linecard that is becoming active could reload unexpectedly. There are no known workarounds.
CSCee26361	A DHCPACK or DHCPNACK with a chaddr == 0 is not forwarded by the Cisco DHCP stack to the cable CMTS code when the CMTS is a relay agent. The DHCP stack must forward such a reply to the CMTS code so that the CMTS can make a decision on an active or inactive lease on the DHCP server. There are no known workarounds.
CSCee27549	SNMP query does not detect specific modems via cdxCmCpeCmStatusIndex in new IOS code 12.2(15)BC1c code. The issue exhibit only for few cable modems on ubr10k chassis. Its noticed that same cable modem, for which snmp poll is failing, appeared under multiple cable interfaces. There are no known workarounds.
CSCee27859	With VI configured, there is delay between switchover of interfaces on the same LC (CSCee40287). A CLI switchover command issued during this time window when one onterface on the card is ready to switch while others are still not, could lead to traceback or linecard reload. There are no known workarounds.
CSCee30001	On a system running traffic, a large number of cm_unreg diversions is seen even if all modems are online. The percentage of diversions fluctuates between about 0.1% to 0.6% of traffic. This causes additional RP CPU load of up to 9% (interrupt) with 330,000 pps system throughput. There are no known workarounds.
CSCee31581	Configuring hccp on interface immediately after taking interface out of shutdown causes the working interface to be stuck down. Workaround: Delay configuring hccp until the interface is up or configure hccp before taking the interface out of shutdown to avoid this issue.
CSCee32609	The CMTS may report a CPU hog error when processing GetBulk SNMP requests. There are no known workarounds.
CSCee32628	The CMTS may report the error below: `%UBR10000-3-NOMEM: Failed to get buffer from flap-list private pool.` There are no known workarounds.
CSCee35423	PRE may unexpectedly reload if an interface is shut down and then immediately unconfigure HCCP on it. There are no known workarounds.
CSCee35624	The Line Card may unexpectedly reload after a N+1 switchover. There are no known workarounds.
CSCee39458	When configured "snmp-server ifindex persist", and the linecard with less number of downstreams is replaced by the linecard with more number of downstreams, SNMP query next entry for the following MIB tables could possibly miss entries. DOCS-QOS-MIB: •docsQosPktClassTable, •docsQosParamSetTable, •docsQosServiceFlowTable, •docsQosServiceFlowStatsTable, •docsQosUpstreamStatsTable, •docsQosDynamicServiceStatsTable, •docsQosPHSTable There are no known workarounds.
CSCee40287	With VI configured, all interfaces on the LC must switch simultaneously. However, it is possible to experience a several seconds delay between switchover of the interfaces on the same card. That leads to the situation where one interface on the LC is ready for switchover several seconds before other interfaces become ready. CLI switchovers issued during this delay can lead to instability. Workaround: Wait for all interfaces on the LC to be ready for switchover before issuing CLI switchover.
CSCee41512	The line card in the CMTS may report IPC errors and reload. This happens after a few LC switchovers with BPI+ enabled. There are no known workarounds.
CSCee44564	When entering the cable upstream max-ports command, there is a small probability to get a spurious memory access. The condition _may_ possibly result in an unexpected reload, though none has been seen yet. This will be seen only if spectrum management is active at the same time. Workaround: Shut down interface before entering the cable upstream max-ports command. Alternative workaround one: Disable spectrum management before entering the cable upstream max-ports command. Alternative workaround two: Ensure there is no Spectrum Management activity before entering the cable upstream max-ports command.
CSCee45280	A router may display the following message repeatedly: `SLOT 8/0: Apr 27 16:55:34.715 CST: %UBR10000-3-OVERLAPIP_CM: Interface Cable8/0/3, IP address` `10.40.137.175 assigned to CM 0040.7b79.f380 has been reassigned.` `SLOT 8/1: Apr 27 16:55:59.263 CST: %UBR10000-3-OVERLAPIP_CM: Interface Cable8/1/4, IP address` `10.41.4.92 assigned to CM 00a0.731e.645b has been reassigned.` `SLOT 7/1: Apr 27 16:56:04.326 CST: %UBR10000-3-OVERLAPIP_CM: Interface Cable7/1/2, IP address` `10.42.0.212 assigned to CM 0040.7b76.e656 has been reassigned.` `Apr 27 16:57:18.006 CST: %REDUNDANCY-5-PEER_MONITOR_EVENT: Primary detected a secondary insertion` `(raw-event=PEER_FOUND(4))` `Apr 27 16:57:18.006 CST: %REDUNDANCY-5-PEER_MONITOR_EVENT: Primary detected a secondary insertion` `(raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))` `Apr 27 16:59:48.161 CST: %SYS-3-CPUHOG: Task ran for 4644 msec (102/84), process = REDUNDANCY FSM,` `PC = 6045A524.` `-Traceback= 6045A52C 6045A710 604852FC 604850F0 604E5614 604E5688 60478F6C 604597F0 60459D00` `6015022C 60145FF8 6014A23C 60F9AA64 6014A5A8 6014AA7C 6014AC1C` This issue is observed on a Cisco uBR1000 universal broadband router that is running Cisco IOS Release 12.2(15)BC01b. There are no known workarounds.
CSCee46449	Multicast packets punted when destination going out the POS interface. There are no known workarounds.
CSCee47418	If a line-card switch-over is performed with at least 3500 modems, 3us3ds service flows, 20-30% modems will go offline during the switch-over. Modems will re-range and come back online. There are no known workarounds.
CSCee52001	Under rare circumstances, an ASSERTION FAILED message followed by a reload may be seen on ubr10000, in or around line 416 of sch_rp_docsis11.c. This will be followed by endless ASSERTION FAILED messages in or around lines 430 and 437. If there is no console connection when the problem occurs, and the console connection is created later, the system may display random characters forever, and it will not respond to any external events. System must be hard reset (power cycled) to recover if there is no secondary PRE. This issue is seen in 12.2(15)BC1, 12.2(15)BC2, and possibly in all ubr10k SW images. The issue is more likely to occur with small arp timeout values. There are no known workarounds. However, it is recommended not to change the ARP timeout from its default value.
CSCee53014	A c10720 gives an error message when writing crashinfo. The error message is of the following form: `07:15:05: %SYS-3-INVMEMINT: Invalid memory action (malloc) at interrupt level` There are no known workarounds.
CSCee57481	UBR10K-6-CM_INCONSISTENCY messages may be seen on the RP console after a LineCard failover. This issue is seen if modems on a particular upstream (or downtream) are forced offline and re-range on another upstream (or downstream). There are no known workarounds.
CSCee57955	THe CMTS may unexpectedly reload during a N+1 transition. There are no known workarounds.
CSCee60322	When query next entry for object in DOCS-IF-MIB:docsIfCmtsCmStatusTable, possibly no response from SNMP agent. Mibwalk the whole table possibly miss some entries. Workaround: Use get exact to query the entry.
CSCee62732	Call cannot be made if DS slack term exceeded. Workaround: Change the DS slack term in Call agent to 0. If one is using the Cisco BTS 3.5.X version, one can use the following command to change the slack term in their EMS system: `change ca-config type=DQOS-DS-SLACK-TERM; value=0` However, it is noticed in customer site, that this affects voice quality where choppy voice is heard, and impact service to customer.
CSCee63917	When performing "show run" multiple times, the value displayed for the cable shared secret changes. There is no performance impact, or negative behavior on the uBR itself, but some management systems regard this as a configuration change. This issue occurs in all IOS versions on uBR7100, uBR7200, uBR10K when "cable shared secret" or "cable secondary-shared secret" are configured. Workaround: Configure the network management tools to ignore the value after "cable shared secret".
CSCee64987	The Cable Arp Filter commands are not removed from the Protect line after a revert. This has no operational impact on the CMTS. Workaround: If the Protect card is no longer used in an hccp configuration, manually remove the following commands that would have been inappropriately been left on the Protect's configuration: no cable arp filter reply no cable arp filter request
CSCee65665	The CMTS may display the error below during an N+1 switch over. `GENERAL-3-EREVENT: No current_if_info` There are no known workarounds.
CSCee66747	HCCP may get into an inconsistent state (Protect does not load the Working config completely) if back-to-back switchovers (Protect to Working1 and Working2 to Protect) are performed very quickly (via a cut n paste). There are no known workarounds.
CSCee69887	A dual SRP ring fails to become active completely due to an is-type mismatch. The output of the show clns neighbors command indicates that a certain system interface remains in the "Init" state indefinitely, although the output of the show ip interface brief command shows that this interface is up. This issue is observed when a dual SRP ring is configured on three routers that run Cisco IOS Release 12.2 S. There are no known workarounds.
CSCee69951	The src-verify lease query filtering functionality may has the following issues 1. Can configure threshold for downstream filter to greater than 255 even though it is not supported 2. Counter does not increment with filter threshold is set to 0. 3. Clear counters does not clear the filter counters There are no known workarounds.
CSCee71684	In certain cases, a classifier entry will not work after a switchover. There are no known workarounds.
CSCee76039	With 12.2(15)BC2d images, encrypted multicast will not work. Workaround: Do not to encrypt multicast traffic.
CSCee78223	If the modem docsis config file is BPI enabled and, if the modem got marked/locked with dynamic-secret. if the modem tries to register again without theft of service, then the modem seems to gets flap continuously. Workaround: Perform a "clear cable modem <mac-addr> lock".
CSCee78261	When CMTS is configured with spectrum group, issue the no cable spectrum-group command introducing some memory leaks. Moreover, the USs in the removed spectrum group have some bogus freq reassigned with 12.3BC image. There are no known workarounds.,
CSCee79463	`The system can sometimes unexpectedly reload when the following messages flood the screen:` `Jun 8 17:40:15.923: %UBR10000-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE:` `<132>CMTS[DOCSIS]:<66030207> Auth Invalid - Message(Key Request)` `Authentication Failure . CM` `Mac Addr <0000.39ef.4a55>` `Jun 8 17:40:31.083: %UBR10000-3-AUTH_INVALID_INVALID_KEY_SEQUENCE_NUMBER:` `<132>CMTS[DOCSIS]:<66030206> Auth Invalid - Invalid Key Sequence` `Number. CM Mac Addr` `<0000.3979.c454>` `Jun 8 17:40:31.087: %UBR10000-3-AUTH_INVALID_MESSAGE_AUTHENTICATION_FAILURE:` `<132>CMTS[DOCSIS]:<66030207> Auth Invalid - Message(Key Request)` `Authentication Failure . CM` `Mac Addr <0000.3979.c454>` `Jun 8 17:42:05.347: %UBR10000-3-INVALIDSIDPOSITION: Invalid SID (81)` `position for` `interface Cable8/1/0: CM 0007.0e03.38c5:Is used by CM 0000.0000.0000 SFID 0` `SID 0. SID` `container info: start 81 end 54` `-Traceback= 602C8110 602C8310 602C8B6C 602B5870 6035124C 605538E8 605538CC` `*Jun 8 17:42:45.363: %UBR10000-3-INVALIDSIDPOSITION: Invalid SID (81)` `position for` `interface Cable8/1/0: CM 0007.0e03.38c5:Is used by CM 0000.0000.0000 SFID 0` `SID 0. SID` `container info: start 81 end 54` `-Traceback= 602C8110 602C8310 602C8B6C 602B5870 6035124C 605538E8 605538CC` `CMTS-R7264#` There are no known workarounds.
CSCee84392	In a MPLS/VPN environment cable modem using DOCSIS 1.0 becomes unreachable. The CPE attached to it is still reachable. The current issue has been detected while resetting the modem The sub-interface where the MOdem is assign to, is configure with "cable source-verify dhcp" and "no cable arp". Workaround: Make sure "no cable arp" is unconfigured from the sub-interface default is "cable arp".
CSCee93770	When modems simultaneously go offline on multiple line cards, the N+1 protocol may get into an inconsistent state. Modems cannot come online and the system does not recover. Some interfaces remain in an Updown Down state and modems can never come back online. Workaround: Hardware Module reset the Protect line card. Alternative workaround: shut/no shut the non-functional interfaces.
CSCef00658	CMTS does not drop dhcp packets that it should for some dhcp packets that have either yiaddr or chaddr as zero IP and mac addr respectively. There are no known workarounds.
CSCef02178	The default ranging-backoff value should be changed from "auto" to values of 3 6. Workaround: Hard code the ranging-backoff values to 3 6.
CSCef04085	After a N+1 switch over, traffic modem counters are not updated while the modem is active on the Protect line card. There are no known workarounds.
CSCef04614	Improve cable modem bringup performance on a ubr10k. There are no known workarounds.
CSCef09586	If DHCP server in one of the configured VRF's has IP address that is matching broadcast address of the IP subnetwork used in another VRF (another subinterface) than cable modems will not come on-line and stay in init(d). If customer has DHCP server in VRF1 using IP address 10.2.16.15 and configure ip address 10.2.16.1 255.255.255.240 on subinterface that belongs to VRF2, problem will occur. This issue has been noticed with following tested images: 12.2(11)BC2, 12.2(15)BC1d. Workaround: Changing IP address of the DHCP server or changing IP address scope in another VRF will resolve the issue.
CSCef10097	With Dynamic UGS serv-flows based Voice Calls, on LC switchover the uBR10K-LC could unexpectedly reload. The specifics of problem scenario is: BPI+ is on, a voice call (dynamic serv-flow) gets established and then gets destroyed. An LC switchover here, could unexpectedly reload the LC. The issue does not happen with all voice calls stay active. There are no known workarounds.
CSCef13047	DOCSIS 1.0+ on ubr10k running 12.2(15)BC2b drops downstream voice packets resulting in one-way voice. There are no known workarounds.
CSCef18997	Data transmission rate in a downstream direction for 256QAM modulation take place with higher rate than configured in a cable modem profile. This can be observed with following CMTS commands: •show interface cable service-flow verbose •show cable modem qos verbose This issue has been noticed with MC16E and MC520U cards with FTP and UDP traffic. The issue Problem is specific to Annex A and has not been noticed with 64QAM. There are no known workarounds.
CSCef23937	N+1 switchovers will NOT work properly in a setup which does NOT have RF switch between the Working and Protect LC. Workaround: Have a dummy config line in the HCCP config for RF switch even if there is no RF switch physically present.
CSCef24484	Cable modem are associated to wrong sub-interface in a MPLS VPN setup. This issue occurs when 2 DHCP server are defined/reacheable from each sub-interfaces networks. Workaround: Clear cable modem xxxx.xxxxx.xxxx del.
CSCef27859	This code improves the modem bringup performance for a ubr10k CMTS. This CMTS has much higher number of cable modems on it compared to the ubr7200 and that is why this code is being committed to take care of the higher modem count. There are no known workarounds.
CSCef28577	Traceback could occur for 1.0+ modem during DSA. There are no known workarounds.
CSCef29003	IOS COPS clients may not interoperate with some COPS servers. If the COPS server send to IOS a COPS message containing an Error Object with an Error-Code in range 12-15, IOS will reject the message. This violates RFC 2748 (see section 2.2.8). There are no known COPS applications at this time that are known to fail due to this issue, but it could affect future (versions of) COPS applications. There are no known workarounds.
CSCef30093	The following error message and traceback may observed at active PRE, while standby PRE is loading after an unexpected reload. `Jul 27 07:31:37.911 UTC: %SYS-3-MGDTIMER: Running timer, init, timer = 63093AE0.` The unexpected reload is tracked in a different DDTS (CSCef27187). There are no known workarounds.
CSCef31956	This is a bug to improve reverse arp lookup on the CMTS for modem bringup. There are no known workarounds.
CSCef32610	It is possible to mis-configure the vi connectors in a way that will result in two upstreams using the same connector (without freq stacking). Workaround: Until more checks are added to the code, the user must perform the checks on the virtual connectors to avoid the connectors conflict.
CSCef35754	IPC communications with a cable linecard fails. The user will see a recoverable ironbus fault followed by an IPC failure. Modems will eventually go offline and new modems will not be able to come online. The card will not be configurable. `Jul 21 02:08:56.212: %C10KEVENTMGR-1-IRONBUS_FAULT: Ironbus Event 5/0 - <Software-Initiated Event>, Restarting Ironbus` `Jul 21 02:08:56.203: C10K_API_CMD_BARIUM_DISABLE command` `SLOT 5/0: Jul 21 02:08:56.227: %IPCGRP-6-BARENBDISAB: Barium interface disabled` `Jul 21 02:08:56.276: %C10KEVENTMGR-1-IRONBUS_SUCCESS: Ironbus Event 5/0 - <Software-Initiated Event>, Restart Successful` `Jul 21 02:08:56.231: C10K_API_CMD_BARIUM_ENABLE command` `SLOT 5/0: Jul 21 02:09:29.195: %REQGRP-3-SYSCALL: System call for command 103 (slot6/0) : ipc_send_message failed (Cause: timeout)` `-Traceback= 60456A38 60457A98 60458084` `%No response from slot 5/0. Command aborted` A recoverable ironbus fault must occur on a cable line card subslot. IPC will fail if HCCP is or is not configured. Note that if two ironbus faults occur within 4 seconds, the subslot will be reset and the IPC connection will be recovered. Workaround: Reset the subslot that had the ironbus fault and the IPC connection to the linecard will be recovered.
CSCef38356	If the bandwidth command is configured on a cable interface it can cause incorrect bandwidth to be given to the downstream service flows on a uBR10k. Workaround: Unconfigure bandwidth command from the cable interface.
CSCef42849	Timing violation in PRE2/PRE1 temperature sensor routine. Since the temperature sensor routines violate timing requirements, the temperature reading fails in new device from a new vendor. Workaround: The failure occurs only in new temperature sensor from new vendor. Note All old type of sensors are not effected. No workaround is needed.
CSCef42977	Under heavy loads (around 500 kpps), the uBR10k PXF can stop dequeuing packets from the low priority queues (default data queues). Workaround: The issue can be rectified by a PXF reload (microcode reload pxf).
CSCef43462	Unable to obtain SNMP MIB info correctly after PRE switchover, but able to obtain ifDescr correctly. However, some interface info are missing. This issue occurs in PRE redundancy with Cisco uBR10012 Cisco IOS software version 12.2(15)BC2b and 12.2(15)BC2c. Workaround: Reload PRE or the CLI "cable upstream max-ports..." would force the PRE to download the snmpinfo to CLC automatically.
CSCef44517	Immediately after booting up, a PRE-1 may crash with the following error: `%ERR-1-GT64120 (PCI-1): Fatal error, PCI retry counter expired GT=0xB4000000,` `cause=0x00001000,` `mask=0x00D01D00, real_cause=0x00001000 bus_err_high=0x00000000,` `bus_err_low=0x00000000,` `addr_decode_err=0x00000470` The fault is limited to PRE-1 version 08 with Texas Instrument PCI bridge chips. This version can be identified by the Top Assy. Part Number visually (on the box) or in the show chassis CLI command: `Top Assy. Part Number : 800-17437-08` `^^^` Workaround: Upgrade IOS to 12.2(15)BC1e or higher or upgrade IOS to 12.2(15)BC2d or higher.
CSCef46191	A specifically crafted Transmission Control Protocol (TCP) connection to a telnet or reverse telnet port of a Cisco device running Internetwork Operating System (IOS) may block further telnet, reverse telnet, Remote Shell (RSH), Secure Shell (SSH), and in some cases Hypertext Transport Protocol (HTTP) access to the Cisco device. Telnet, reverse telnet, RSH and SSH sessions established prior to exploitation are not affected. All other device services will operate normally. Services such as packet forwarding, routing protocols and all other communication to and through the device are not affected. Cisco will make free software available to address this vulnerability. Workarounds, identified below, are available that protect against this vulnerability. The Advisory is available at http://www.cisco.com/warp/public/707/cisco-sa-20040827-telnet.shtml
CSCef49148	On a UBR10K router, after configuring both the primary shared secret and the secondary shared secret on cable interfaces using the cable shared-secret and cable shared-secondary-secret commands, and the length of the secondary shared secret is longer than the primary, the cable line card (MC28C, MC5x20) may reload unexpectedly. There are no known workarounds.
CSCef49769	The 2x8 LC on the Ubr10k can run very high CPU utilization for moderate amounts of upstream traffic. LCP1 is more susceptible than LCP2 due to lower base CPU performance. The 5x20 LC is not affected by this issue. This can cause box-wide issues as the LC throttles the PXF severely. Workarounds: Reduce load on the affect linecard by moving CMs to a different LC. If you have an LCP1 based 2x8 linecard, replace with LCP2 Replace 2x8 linecard with 5x20 linecard.
CSCef52235	An Ubr10k running either 12.2(15)BC2c or 12.2(15)BC1b will run into the following issues when a 2x8 LC is running at 100% CPU: 1. No telnet access, only the console port works. 2. Modems that are online cannot come back online, the get stuck in init(rc). 3. Message that is being seen when the CMTS becomes unreachable: `%C10KEVENTMGR-1-MINOR_FAULT: PXF DMA Full OCQ Wait Error` 4. Traffic slowing down for all the linecards, especially the backhaul interfaces The issue was seen on a uBR10K with 16,000 CM's. Workaround: Reduce load on the LC running at 100% CPU. Alternative workaround: Reload the PXF microcode.
CSCef53390	The sample rate range is calculated based on the monitoring duration as compared to the previous (STM1.0) constant range of 10 - 30 minutes. The range is calculated as follows: •The maximum memory to be used per line card for STM is 10 MBytes. •The maximum number of modems that can be supported is 6000 per line card. Now, per sample memory consumption is 8 bytes hence approximately, the maximum number of samples that can be allowed are 10 * 10 ^ 6 / (6 * 10 ^ 3 * 2 * 8) ~ 100. Hence, given the duration the sample rate would be calculated as duration / 100 = sample rate only if the duration happens to be more than 1440. For monitoring duration less than 1440, the sample rate range would be 10 - 30 minutes. Hence, with STM 1.0 if someone had the duration as 2 days and the sample rate was 20 minutes, that command would fail when we try to restore that configuration in STM1.1 as now the range would be 28 to 86 minutes. The feature to convert the STM1.0 configuration to STM1.1 was committed through CSCee58978. There are no known workarounds.
CSCef56071	Enforce-rule configured via SNMP is not effective at the CMTS. The same rule when configured thru CLI does not have any issues. There are no known workarounds.
CSCef56516	SNR values can lower then expected with MC520U card. This issue is observed if virtual connectors 16,17,18,19 are used. There are no known workarounds.
CSCef57375	On an ubr7246VXR CMTS router, when MC28U card is configured as cable bundle slave and multicast static-group is configured on master on start-up configuration, after reload, the MC28U card interface fails to populate its multicast bundle entries to the cable bundle forwarding table. There are no known workarounds.
CSCef58105	Show cable modem offline does not correctly show the previous state of the modem when going through the provisioning steps. There are no known workarounds.
CSCef60697	Fix chassis unexpectedly reloads due to acl processing of fragmented packets. The ubr10k will crash when the RP processor processes a 0th fragmented packet on an interface that has an ACL attached. This issue occurs when an ACL is attached to an interface & the packet is a 0th fragmented packet. There are no known workarounds.
CSCef60926	In a 1.0+ redundant environment, if a switchover is issued using the hccp x switch y command, new downstream dynamic service flows do not will not be established on all new call attempts through protect card. There are no known workarounds.
CSCef63012	During a N+1 switchover, the following CPUHOG error message may appear at the PROTECTOR CLC as well at RP: `%SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs` `(1200/1160),process = HCCP_DATA_P1.` There are no known workarounds.
CSCef65077	The PRE-2 FIB code has been modified so that packets with the PUNT adjacency flag now get a new divert-code of PS_DIVERT_CODE_FIB_RP_PUNT. Packets with the RECEIVE adjacency flag continue to get PS_DIVERT_CODE_FIB_RP_DEST, but the RP_DEST divert-code has now been assigned a priority of 5 (instead of zero). The RP_PUNT divert-code gets a priority of zero. The treatment of GLEAN adjacencies remains the same: `adjacency old old new new` `flag div-code priority div-code priority` `-------------------------------------------------------` `GLEAN FIB_RP_GLEAN 0 FIB_RP_GLEAN 0` `PUNT FIB_RP_DEST 0 FIB_RP_PUNT 0` `RECEIVE FIB_RP_DEST 0 FIB_RP_DEST 5` SNMP and telnet traffic gets the RECEIVE adjacency flag, and will now be diverted with high priority. This DDTS was created when it was shown that on the PRE-2, SNMP and telnet traffic timed-out under congestion conditions. Testing shows that the problem has been fixed. See Test-Results and email-trail attachments. There are no known workarounds.
CSCef65495	If the bandwidth command is configured on a cable interface it can cause incorrect bandwidth to be given to the downstream service flows on a uBR10k. Workaround: Unconfigure bandwidth command from the cable interface.
CSCef68419	A Cisco UBR 10000 running IOS 12.2BC images may crash by a Sgtrap exception if an extremely low bandwidth value is specified under a Cable Interface: `CMD: 'bandwidth 10 ' 12:01:34 Tue Sep 7 2004` `Sep 7 09:01:35.359: %SYS-5-CONFIG_I: Configured from console` `CMD: 'sho cable modem flap` `Unexpected exception, CPU signal 5, PC = 0x6012CB08` `-Traceback= 6012CB08 6012D65C 603180E0 60318BA0 603063C4 60306878 60315FCC` `6050BD68` `6050BD4C` There are no known workarounds.
CSCef68700	Active PRE2 (Secondary) crashed with Bus Error Exception and System Switched to Standby (Primary) PRE2. There are no known workarounds.
CSCef69368	When toaster VTMS receives excessive OCQ flow off from a linecard of to-rp link, it can cause severe performance degradation of VTMS or it can lockup the timing wheel causing VTMS not to service any linecard. This issue occurs when excessive OCQ flow off from linecard e.g in presence of over subscription of link. There are no known workarounds.
CSCef70056	After a CLI switch over, CPE devices on the slave interfaces may lose connectivity. Workaround: Reload the CPE device.
CSCef77451	After issuing the test crash command the output pauses before printing out the menu options. When this pause is observed hitting <Enter> will allow the menu be printed and the user to select an option. There are no known workarounds.
CSCef78292	CPUHOG traceback appears on the RP console during switchover. This issue occurs on large-scale systems, >35K CMs, possibly scrypt kiddies. Also, cable bundle has to be configured and switchover has to be configured and performed within this bundle. There are no known workarounds.
CSCef82436	When we have more than 2K modems ranging on an active interface, the standby LC can reload unexpectedly, while synching those ranged sids into its inter-db. There are no known workarounds.
CSCef83416	After a switchover to the Protect LC, new BPI/PHS modems coming online on the Protect LC may not be pingable nor can user traffic be sent to them. This issue occurs in a 2+1 or a larger system. It does not occur in a 1+1 system. Workaround: Disable BPI/PHS.
CSCef83933	LC HA: N+1 using 520U card will not work after switch over when BPI/PHS and Virtual Interface are configured. There are no known workarounds.
CSCef85824	The router may reload as a result of the following CLI commands: `show tech` `show pxf cpu queue <cable interface>` `show cr10k <cable interface> queue be` `show cr10k <cable interface> queue ll` `show cr10k <cable interface> queue cir` The Memory allocation scheme changed from standard malloc to chunks. This resulted in a mismatch of memory management routines: `chunk_lock to be used in place of mem_lock.` There are no known workarounds.,
CSCin54055	DOCSIS1.0 Qos profile created by CM is not seen in "show cable qos profile" CLI output after PRE switchover. There are no known workarounds.
CSCin71529	When the cable QoS permission for the modems is disabled, the qos profile created by the modem may not be removed from the QoS profile table. Also, if a cable interface is shutdown or if one issues a "clear cable modem cax/y/z all delete" on the CMTS, the qos profile feature gets broken for deletion of qos profiles - the profile should be deleted, but it won't since the internal reference count of the profile is messed up. There are no known workarounds.
CSCin71861	If 255 CPE's are configured behind CM's in the system, the primary PRE will reload unexpectedly. Workaround: Configure some small number of allowable CPE's like 15 to 25.
CSCin74377	When CMTS is configured with the shared spectrum group using time scheduled bands and then removal of spectrum group definition may cause CMTS to reload unexpectedly. Spectrum management software module is modified to remove the spectrum group in the proper sequence. There are no known workarounds.
CSCin75900	The networks connected to the CPE router (in case of business customers) become unreachable after PRE switchover if "cable source-verify [dhcp]" is configured on the CMTS (sub) interface associated with the modem. There are no known workarounds.
CSCin75998	When both "cable tftp-enforce" and DMIC CLIs are configured, tftp-enforce may not get the precedence over DMIC. There are no known workarounds.
CSCin76192	Traceback can be observed in an image with a fix for CSCee32628 during flap list aging. There are no known workarounds.
CSCin78666	While doing a MIB walk with a fully loaded CMTS The mib walk may gets into loop with the object "docsQosParamSetServiceClassName". There are no known workarounds.
CSCin82115	If the UGS docsis1.1 config file is provisioned to the toshiba modem with BPI+ enabled traffic may get stuck after switchover. There are no known workarounds.

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at this URL:

http://www.cisco.com

Translated documentation is available at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.

Ordering Documentation

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

Documentation Feedback

You can submit comments electronically on Cisco.com. In the Cisco Documentation home page, click the Fax or Email option in the "Leave Feedback" section at the bottom of the page.

You can email your comments to bug-doc@cisco.com.

You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you with these tasks:

•Streamline business processes and improve productivity

•Resolve technical issues with online support

•Download and test software packages

•Order Cisco learning materials and merchandise

•Register for online skill assessment, training, and certification programs

If you want to obtain customized information and service, you can self-register on Cisco.com. To access Cisco.com, go to this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Cisco TAC inquiries are categorized according to the urgency of the issue:

•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.

•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.

•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

The Cisco TAC resource that you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

You can use the Cisco TAC Web Site to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to this URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:

http://www.cisco.com/register/

If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC Web Site, you can open a case online by using the TAC Case Open tool at this URL:

http://www.cisco.com/tac/caseopen

If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.

Table Of Contents