Release Notes for Cisco uBR7100 Series

Release Notes for Cisco uBR7100 Series
for Cisco IOS Release 12.3 BC

October 18, 2004

Cisco IOS Release 12.3(9a)BC

OL-6762-01

These release notes for the Cisco uBR7100 series universal broadband routers document the cable-specific, early deployment 12.3 BC train, describing the enhancements and caveats provided in Cisco IOS Release 12.3(9a)BC.

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.

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:

• Introduction

• Early Deployment Releases

• System Requirements

• Feature Support

• New and Changed Information

• Important Notes

• Caveats

• Related Documentation

• Obtaining Documentation

• Obtaining Technical Assistance

Introduction

For information on new features and the Cisco IOS documentation set supported by Cisco IOS Release 12.3(9a)BC, see the "New and Changed Information" section and the "Related Documentation" section.

Overview of Cisco Universal Broadband Routers

The Cisco uBR7100 series universal broadband routers—the Cisco uBR7111, Cisco uBR7111E, Cisco uBR7114, and Cisco uBR7114E—are based on the Data-over-Cable Service Interface Specification (DOCSIS) standards and designed to be installed at small cable operators and multiple dwelling unit (MDU) operators to enable them to offer services such as e-mail, high-speed Internet access, voice, and digital video over a bidirectional cable television and IP backbone network. The universal broadband routers function as the cable modem termination system (CMTS) for subscriber-end devices such as Cisco uBR905, Cisco uBR924, and Cisco uBR925 cable access routers, and other DOCSIS-compliant cable modems (CMs) and set-top boxes (STBs).

Both the Cisco uBR7100 series and Cisco uBR7200 series universal broadband routers allow two-way transmission of digital data and Voice over IP (VoIP) traffic over a hybrid fiber-coaxial (HFC) network. The Cisco uBR7100 series routers support IP routing with a wide variety of protocols and WAN interfaces selections.

Cisco IOS Release 12.3(9a)BC supports the Cisco uBR7111, Cisco uBR7111E, Cisco uBR7114, and Cisco uBR7114E universal broadband routers.

Cisco uBR7100 Series Universal Broadband Routers

The Cisco uBR7100 series routers provide a fixed set of WAN and LAN interfaces with a combination of fixed and modular interfaces, allowing both flexibility and simplicity in configuration. Each Cisco uBR7100 series router includes one modular single-width port adapter, one integrated cable interface with an internal upconverter, and two integrated Fast Ethernet ports. The cable interface is based on the Cisco uBR-MC14C cable interface line card and is not field-replaceable.

The Cisco uBR7100 series routers support IP routing through the following optional WAN and LAN port adapters: Ethernet, Fast Ethernet, serial, High-Speed Serial Interface (HSSI), Packet over SONET (POS) OC-3c, and Asynchronous Transfer Mode (ATM) media. For more information, see Table 4.

Depending on the model, the Cisco uBR7100 series routers support the following two standards:

•Data Over Cable Service Interface Specifications (DOCSIS), which supports the 6 MHz North American channel plans using the ITU J.83 Annex B RF standard. The downstream uses a 6 MHz channel width in the 85 to 860 MHz frequency range, and the upstream supports the 5 to 42 MHz frequency range.

•European Data Over Cable Service Interface Specifications (EuroDOCSIS), which supports the 8 MHz Phase Alternating Line (PAL) and Systeme Electronique Couleur Avec Memoire (SECAM) channel plans using the ITU J.112 Annex A RF standard. The downstream uses an 8 MHz channel width in the 85 to 860 MHz frequency range, and the upstream supports multiple channel widths in the 5 to 65 MHz frequency range.

The Cisco uBR7100 series offers the following models:

•The Cisco uBR7111 and Cisco uBR7111E universal broadband routers provide a cable interface with one downstream port and one upstream port. The downstream port can be output either as an RF signal through the integrated upconverter or as an IF signal for processing by an external upconverter. The Cisco uBR7111 router supports DOCSIS cable plants, and the Cisco uBR7111E supports EuroDOCSIS cable plants.

•The Cisco uBR7114 and Cisco uBR7114E universal broadband routers provide a cable interface with one downstream port and four upstream ports. The downstream port can be output either as an RF signal through the integrated upconverter or as an IF signal for processing by an external upconverter. The Cisco uBR7114 router supports DOCSIS cable plants, and the Cisco uBR7114E supports EuroDOCSIS cable plants.

Cisco uBR7111 and Cisco uBR7111E Universal Broadband Routers

The Cisco uBR7111 and Cisco uBR7111E provide the following major hardware features:

•Integrated network processing engine

•1 upstream cable modem interface

•1 downstream cable modem interface

•2 Fast Ethernet ports

•1 port adapter slot

•1 service adapter slot

•1 AC power supply

•1 Personal Computer Memory Card International Association (PCMCIA) slot that allows for software upgrades through the use of Flash memory cards

Cisco uBR7114 and Cisco uBR7114E Universal Broadband Routers

The Cisco uBR7114 and Cisco uBR7114E provide the following major hardware features:

•Integrated network processing engine

•1 downstream cable modem interface

•4 upstream cable modem interfaces

•2 Fast Ethernet ports

•1 port adapter slot

•1 service adapter slot

•1 AC power supply

•1 Personal Computer Memory Card International Association (PCMCIA) slot that allows for software upgrades through the use of Flash memory cards

Universal Broadband Router Overview

Table 1 provides a quick overview of the major hardware features of the two universal broadband routers.

Table 1 Universal Broadband Router Overview
Supported Hardware	Cisco uBR7111, Cisco uBR7111E	Cisco uBR7114, Cisco uBR7114E
Upstream Cable Modem Interfaces	1	4
Downstream Cable Modem Interfaces	1	1
Fast Ethernet Ports	2	2
Port Adapter Slots	1	1
Service Adapter Slots	1	1
Power Supplies	1	1
PCMCIA Slots	1	1

Early Deployment Releases

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

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

•Cisco uBR7100 Series Universal Broadband Router Release Notes on Cisco.com:

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

•Cisco uBR7100 Series Universal Broadband Router Software Configuration Guide

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

•Cisco Broadband Cable Command Reference Guide

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

Table 2 Early Deployment (ED) Releases for the Cisco uBR7100 Series Routers
ED Release	Additional Software Features¹ and MIBs²	Additional Hardware Features	Hardware Availability
Cisco IOS Release 12.3(9a)BC	• Cisco Broadband Troubleshooter 3.2 • Cisco IOS Release 12.3(9a)BC Command-Line Interface (CLI) Enhancements • DOCSIS Set-Top Gateway Issue 1.0 • MIBs Changes and Updates in Cisco IOS Release 12.3(9a)BC • Subscriber Traffic Management (STM) Version 1.1	•None	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

• Supported Hardware

• Determining Your Software Release

• Upgrading to a New Software Release

Memory Recommendations

Table 3 displays the memory recommendations of the Cisco IOS feature sets for the Cisco uBR7100 series universal broadband routers for Cisco IOS Release 12.3(9a)BC. Cisco uBR7100 series routers are available with a 16-MB or 20-MB Type II PCMCIA Flash memory card.

Table 3 Memory Recommendations for the Cisco uBR7100 Series Routers,
Cisco IOS Release 12.3(9a)BC Feature Sets
Feature Set	Software Image	Recommended Flash Memory	Recommended DRAM Memory	Runs From
Two-Way Data/VoIP Images
DOCSIS Two-Way	ubr7100-p-mz	16 MB Flash	128 MB DRAM	RAM
DOCSIS Two-Way IP Plus	ubr7100-is-mz	16 MB Flash	128 MB DRAM	RAM
DOCSIS Two-Way with BPI	ubr7100-k8p-mz	16 MB Flash	128 MB DRAM	RAM
DOCSIS Two-Way IP Plus with BPI	ubr7100-ik8s-mz	16 MB Flash	128 MB DRAM	RAM
Boot Image
UBR7100 Boot Image	ubr7100-boot-mz	None	None	—

The image subset legend for Table 3 is as follows:

•i = IP routing, MPLS-VPN support, and noncable interface bridging, including Network Address Translation (NAT)

•k8 = DOCSIS Baseline Privacy and MPLS-VPN support

•p = IP routing with Intermediate System-to-Intermediate System (IS-IS) and Border Gateway Protocol (BGP); MPLS-VPN support; no NAT

•s = "Plus" features: NAT and Inter-Switch Link (ISL)

Note All images support all of the hardware listed in the "Supported Hardware" section, unless otherwise indicated.

Supported Hardware

Cisco IOS Release 12.3(9a)BC supports the following Cisco uBR7100 series routers:

•Cisco uBR7111

•Cisco uBR7114

•Cisco uBR7111E

•Cisco uBR7114E

Port Adapter Cards

Table 4 lists and describes the port adapters supported by Cisco uBR7100 series routers in Cisco IOS Release 12.3(9a)BC.

Note Table 4 identifies some port adapters for the Cisco uBR7100 series routers that are in an end-of-life (EOL) stage. See the following product bulletin for more details on these EOL port adapters:

http://www.cisco.com/warp/partner/synchronicd/cc/general/bulletin/rt/1438_pp.htm

Table 4 Cisco uBR7100 Series Port Adapter Releases
WAN Technology	Product Number and Description	Introduced in Release¹	End-of-Life
Ethernet
	PA-4E—4-port Ethernet 10BASE-T port adapter	12.2(4)XF1	No
	PA-8E—8-port Ethernet 10BASE-T port adapter	12.2(4)XF1	Yes
Fast Ethernet
	PA-FE-TX—1-port 100BASE-TX Fast Ethernet port adapter	12.2(4)XF1	No
	PA-FE-FX—1-port 100BASE-FX Fast Ethernet port adapter	12.2(4)XF1	No
	PA-2FE-TX—2-port 100BASE-TX Fast Ethernet port adapter	12.2(4)XF1	No
	PA-2FE-FX—2-port 100BASE-FX Fast Ethernet port adapter	12.2(4)XF1	No
Serial
	PA-E3—1-port high-speed serial E3 interface port adapter	12.2(4)XF1	No
	PA-T3—1-port T3 serial interface port adapter	12.2(4)XF1	No
	PA-T3+—1-port T3 serial interface port adapter enhanced	12.2(4)BC1	No
	PA-2E3—2-port high-speed serial E3 interface port adapter	12.2(4)XF1	No
	PA-2T3—2-port T3 serial interface port adapter	12.2(4)XF1	No
	PA-2T3+—2-port T3 serial interface port adapter enhanced	12.2(4)BC1	No
	PA-4T+—4-port synchronous serial port adapter	12.2(4)XF1	No
	PA-4E1G-75—4-port unbalanced (75-ohm) E1-G.703/G.704 synchronous serial port adapter	12.2(4)XF1	No
	PA-4E1G-120—4-port balanced (120-ohm) E1-G.703/G.704 synchronous serial port adapter	12.2(4)XF1	No
	PA-8T-232—8-port EIA/TIA-232 synchronous serial port adapter	12.2(4)XF1	Yes
	PA-8T-V35—8-port V.35 synchronous serial port adapter	12.2(4)XF1	No
	PA-8T-X21—8-port X.21 synchronous serial port adapter	12.2(4)XF1	Yes
	PA-MC-2T1—2-port multichannel DS1 Integrated Services Digital Network (ISDN) Primary Rate Interface (PRI) single-wide port adapter	12.2(4)XF1	Yes
	PA-MC-4T1—4-port multichannel DS1 ISDN PRI single-wide port adapter	12.2(4)XF1	No
HSSI
	PA-H—1-port HSSI port adapter	12.2(4)XF1	Yes
	PA-2H—2-port HSSI port adapter	12.2(4)XF1	No
ATM
	PA-A3-E3—1-port E3 ATM, PCI-based, single-width port adapter, that uses an E3 interface with a coaxial cable BNC connector	12.2(8)BC1	No
	PA-A3-OC3MM—1-port OC-3c ATM, PCI-based multimode port adapter	12.2(4)XF1	No
	PA-A3-OC3SMI—1-port OC-3c ATM, PCI-based single-mode intermediate reach port adapter	12.2(4)XF1	Yes
	PA-A3-OC3SML—1-port OC-3c ATM, PCI-based single-mode long reach port adapter	12.2(4)XF1	No
	PA-A3-8T1/IMA—ATM inverse multiplexer over ATM port adapter with 8 T1 ports	12.2(4)XF1	No
Packet over SONET	PA-POS-OC3SMI—1-port OC3 single-mode, intermediate reach port adapter	12.2(4)XF1	No

¹The number in this column indicates the Cisco IOS release in which the interface was introduced in this train.

Determining Your Software Release

To determine the version of Cisco IOS software running on the Cisco Cisco uBR7100 series 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 (ubr7100-k8p-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 the following location on Cisco.com:

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

DOCSIS System Interoperability on the Cisco uBR7100 Series CMTS

This section describes the operation of primary interoperability features in the Cisco Cisco uBR7100 series 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 Cisco uBR7100 series 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.

Note Cisco IOS Release 12.3(9a)BC does not support telco-return cable modems or STBs.

Configuring the CMTS Cable Interface When in Routing Mode

If you have configured a Cisco cable modem for routing mode and are also using the cable-modem dhcp-proxy nat command on the cable modem, you must configure the corresponding cable interface on the Cisco uBR7200 series router with the cable dhcp-giaddr policy command. Otherwise, the cable interface could flap and the CM could go offline unpredictably.

DOCSIS 1.0 and 1.0+ Extensions

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

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

DOCSIS 1.1 Extensions

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

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

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

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

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

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

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

•Several QoS models are supported for the upstream.

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

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

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

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

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

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

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

•Layer 2 fragmentation on the upstream prevents large data packets from affecting real-time traffic, such as voice and video. Large data packets are fragmented and then transmitted in the 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 uBR7100 series 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.

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 uBR7100 series routers for Cisco IOS Release 12.3(9a)BC.

No New Hardware Features in Release 12.3(9a)BC

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

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 uBR7100 series router:

• Cable ARP Filter Enhancement

• Cisco Broadband Troubleshooter 3.2

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

• DOCSIS Set-Top Gateway Issue 1.0

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

• Subscriber Traffic Management (STM) Version 1.1

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 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 cable modems, 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 four 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 one to five seconds, with a default of two 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:

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801eefa9.html

Cisco Broadband Troubleshooter 3.2

Cisco IOS Release 12.3(9a)BC introduces support for the Cisco Broadband Troubleshooter (CBT) Version 3.2 on the Cisco uBR7100 series universal broadband router, with newly supported interoperability for the following additional software features:

• 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 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 uBR7100 series router:

• Cable ARP Filter Enhancement

• 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 uBR7100 series 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 uBR7100 Series routers, 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

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 uBR7100 series routers.

• CISCO-CABLE-METERING-MIB

• CISCO-CABLE-QOS-MONITOR MIB

• CISCO-ENHANCED-MEMPOOL-MIB

• CISCO-PROCESS-MIB

• CISCO-CABLE-SPECTRUM-MIB

• DOCS-QOS-MIB

For additional information about Cisco Broadband Cable 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

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-METERING-MIB on the Cisco uBR7100 series universal broadband routers. The CISCO-CABLE-METERING-MIB contains objects that provide subscriber account and billing information in the Subscriber Account Management Interface Specification (SAMIS) format. 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).

This MIB has the following constraints:

•The packet counters displayed by CLI commands are reset to zero whenever the Cisco CMTS router is rebooted.

•The packet counters displayed by SNMP commands are retained across router resets.

•These counters are 64-bit values and could rollover to zero during periods of heavy usage.

For additional SAMIS information, refer to the following resources:

•Usage Based Billing for the Cisco CMTS

http://www.cisco.com/en/US/products/hw/cable/ps2217/products_feature_guide09186a00801ef1d7.html

CISCO-CABLE-QOS-MONITOR MIB

Cisco IOS Release 12.3(9a)BC introduces additional features for the CISCO-CABLE-QOS-MONITOR MIB, including the following:

•Clarified the descriptions of a number of objects.

•Added a number of objects in the ccqmCmtsEnforceRuleTable to support DOCSIS 1.1 and DOCSIS 2.0 cable modems and to support peak and off-peak monitoring.

•Added the ccqmCmtsIfBwUtilTable to provide thresholds for downstream/upstream bandwidth utilization.

•Deprecated and removed ccqmCmtsEnfRuleByteCount.

CISCO-ENHANCED-MEMPOOL-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR7100 series universal broadband routers. The CISCO-ENHANCED-MEMPOOL-MIB enables you to monitor CPU and memory utilization for "intelligent" line cards and broadband processing engines on the Cisco uBR7100 series routers.

CISCO-PROCESS-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-PROCESS-MIB on the Cisco uBR7100 series universal broadband routers. 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 uBR7100 series routers.

CISCO-CABLE-SPECTRUM-MIB

Cisco IOS Release 12.3(9) introduces support for the CISCO-CABLE-SPECTRUM-MIB on the Cisco uBR7100 series universal broadband routers, 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 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 uBR-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).

DOCS-QOS-MIB

Cisco IOS Release 12.3(9) introduces additional MIB object enhancements for the DOCS-QOS-MIB on the Cisco uBR7100 series universal broadband routers:

•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.

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 uBR10012, Cisco uBR7246VXR and Cisco uBR7100 series 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.

MIB Constraints

The DSG-IF-MIB has the following constraints:

•This is an experimental MIB that can be obsoleted and replaced without prior notice, when the DSG specification is finalized.

•This MIB is supported only in Cisco IOS Release 12.3(9a)BC and later releases. It is not supported for the version of DSG that was implemented in Cisco IOS Release 12.2(15)BC1.

•This MIB is not supported in Cisco IOS Release 12.1 EC.

•This MIB is not supported on Cisco uBR7100 routers.

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 uBR7100 series universal broadband routers. 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

Important Notes

The following sections contain important notes about Cisco IOS Release 12.3(9a)BC that apply to Cisco uBR7100 series universal broadband routers.

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 uBR7100 series universal broadband routers:

• cable source-verify

• show cable tech-support

• show controllers cable

• show tech-support

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— •interval—
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— •interval—

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

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 uBR7100 series router on which Cisco IOS Release 12.3(9a)BC is installed.

Router# show cable tech-support

----------------------------------- Slot 1/0 -----------------------------------

------------------ show cable modem Cable1/0 ------------------

MAC Address    IP Address      I/F       MAC         Prim RxPwr  Timing  Num BPI

                                         State       Sid  (dB)   Offset  CPE Enb

------------------ show cable modem Cable1/0 connectivity ------------------

Prim  1st time    Times  %online     Online time            Offline time

Sid   online      Online          min     avg     max     min     avg     max

------------------ show interface Cable1/0 sid ------------------

Sid  Prim  MAC Address    IP Address      Type Age      Admin   Sched  Sfid

                                                        State   Type

------------------ show interface Cable1/0 sid counter ------------------

Sid  Req-polls  BW-reqs    Grants     Packets    Frag       Concatpkts

     issued     received   issued     received   complete   received

------------------ show interface Cable1/0 sid association ------------------

Sid  Prim Online     IP Address      MAC Address    Interface     VRF Name

------------------ show interface Cable1/0 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

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] ]

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.

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 uBR-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. This enhanced command is supported on the Cisco uBR10012, Cisco uBR7246VXR and Cisco uBR7100 Series universal broadband routers.

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 uBR-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 1/0 on a Cisco uBR7100 series router:

Router# show controllers c1/0 downstream

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

Table 5 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 1 on port 0 on a Cisco uBR7100 series router on which Cisco IOS Release 12.3(9a)BC is installed.

Router# show controllers c1/0

The following example illustrates memory statistics for the specified slot/port on the Cisco uBR7100 router:

Router# show controllers c1/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/port on the Cisco uBR7100 series router:

Router# show controllers c1/0 upstream

 Cable1/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/port on the Cisco uBR7100 series router:

Router# show controllers c1/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 uBR7100 series router:

Router# show controllers c1/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

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. 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.
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 6 lists only severity 1 and 2 caveats and select severity 3 caveats for the Cisco IOS 12.3(9a)BC release.

Table 6 Open Caveats for Cisco IOS Release 12.3(9a)BC
DDTS ID Number	Description
CSCee80483	UBR7246VXR running 12.2(15)BC2a unexpectedly reloads due to watchdog timeout. UBR7246VXR crashes due to watchdog timeout when a cable modem entry is cleared per the following snip: `clear cable modem X.X.X.X delete` `UBR7200-3-BADARPDELETE: Tried to remove arp entry for X.X.X.X that is not dynamicProcess aborted on watchdog timeout, process = DHCPD Receive.` `+++++++++` X.X.X.X represents IP address of the cable modem. 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.
CSCef96146	Frequent log messages are generated complaining about some apparent problem with one of the fans: `%ENVM-3-BLOWER: Fan 1 may have failed` The fan appears to be working fine with no cooling problem. So far this has been reported only on the UBR7200s running some 12.2(15)BC2 image, like 2a or 2b. There are no known workarounds.
CSCef89495	A UBR7200 running an IOS release 12.2(15)BC2b image may unexpectedly reload with a bus error at address D0d0dxx, presumptively after issuing a show controller cableX/Y command. There are no known workarounds.
CSCef67544	Upstream rate shaping has a negative affect on per-modem US speeds when exceeding typical speeds of 3 Mbps. Using a 28U linecard with 12.2(15)BC2c code and special configurations to allow per-modem speeds on the US exceeding 10 Mbps. Workaround: Instead of using the default setting of cab upstream x rate-limit-token-bucket shaping, drop the shaping keyword when offering rates higher than ~5 Mbps or so.
CSCef79717	The default fair-queue command changes the queueing strategy under cable interfaces from the default of WFQ to FIFO. Problem is seen with 12.2(15)BC2c and earlier images. Workaround: Configure "fair-queue" under the cable interface to change the queueing strategy from FIFO back to the default of FIFO.

Resolved Caveats for Release 12.3(9a)BC

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

Table 7 Resolved Caveats for Cisco IOS Release 12.3(9a)BC
DDTS ID Number	Description
CSCea85575	Need way to find out how long a currently online cable modem has been online. There are no known workarounds.
CSCeb42687	Following error message will appear on NPE-G1: `*May 30 09:13:05.618: %SYS-3-INTPRINT: Illegal printing attempt from interrupt level.` `-Process= "<interrupt level>", ipl= 5` There are no known workarounds.
CSCeb43381	Incorrect values may be returned for the ifInOctets IF-MIB object. This issue is observed on a Cisco 7200 series that is configured with a Network Processing Engine G1 (NPE-G1) when the ifInOctets counter is polled via Simple Network Management Protocol (SNMP) on a Gigabit Ethernet subinterface that is configured for 802.1q encapsulation. There are no known workarounds.
CSCeb72942	A c7301 may unexpectedly reload during POS-OC3MM port adapter OIR with traffic running through on-board GigE interfaces. Workaround: Stop the traffic and initiate OIR.
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.
CSCec65492	This issue has been observed for both cable interface and gigabit Ethernet interface. One reason is that the moving average algorithm for bit rate takes byte count even when it appears to be in error (negative). This may happen with other interface type also. There are no known workarounds.
CSCec85359	snmpwalk failed OID.1.3.6.1.2.1.10.127.1.3.7 Conditions: This is observed on 7206VXR running IOS 12.1(13)EC3 and having PA-A3-8E1IMA interfaces. Workaround: OIR the linecard.
CSCec86360	On UGS-AD service the CMTS is not sending the extra UGS grant when switching from inactive to active period with incoming frame where the QI (queue Indicator) set ON. There are no known workarounds.
CSCed06848	With DMIC turned on, CMs may not be able to download IOS config files. This issue may occur if a CM is online and tries to download an IOS.cfg file from the same tftp server as specified in the DHCP offer, it will fail. The issue only happens with DMIC turned on and seen on CMs (e.g., Cisco CMs in routing mode), that try downloading a second config file after coming online. There are no known workarounds.
CSCed13018	Native GE interface throttling is always bypassed. This issue e occurs with newer version of BCM chips also the throttling is bypassed, whereas only for older revision it is needed. There are no known workarounds.
CSCed26241	Ubr7246VXR may modify DHCP BootP requests running 12.2(15)BC1. The BootP packet will be decreased in size and may cause the DHCP not to reply to the BootP requests. The behavior is not observed in 12.1(13)EC4. `Example:` `Debugs` `debug ip dhcp server packet & debug ip udp` `With 12.1(13)EC4 (working)` `Dec 11 12:53:49.819: UDP: rcvd src=0.0.0.0(68), dst=255.255.255.255(67),length=308` `Dec 11 12:53:49.819: BOOTP: opcode 1 on interface FastEthernet0/0.50, 0secs, 0 hops` `Dec 11 12:53:49.819: DHCPD: setting giaddr to 192.168.0.1.` `Dec 11 12:53:49.819: UDP: sent src=192.168.0.1(67), dst=10.0.0.1(67),length=328` `Dec 11 12:53:49.819: DHCPD: BOOTREQUEST from 0002.de15.3ed8 forwarded to10.0.0.1.` `Dec 11 12:53:50.091: UDP: rcvd src=10.0.0.1(67), dst=192.168.0.1(67),length=308` `Dec 11 12:53:50.091: DHCPD: forwarding BOOTREPLY to client 0002.de15.3ed8.` `Dec 11 12:53:50.091: DHCPD: creating ARP entry (10.0.0.1,0002.de15.3ed8).` `Dec 11 12:53:50.091: DHCPD: unicasting BOOTREPLY to client 0002.de15.3ed8(10.0.0.1).` `Dec 11 12:53:50.095: UDP: sent src=192.168.0.1(67), dst=10.0.0.1(68),length=328` `With 12.2(15)BC1 (not working)` `.Dec 11 12:46:18.173: UDP: rcvd src=0.0.0.0(68), dst=255.255.255.255(67),length=308` `.Dec 11 12:46:18.173: BOOTP: opcode 1 on interface FastEthernet0/0.50, 0 secs, 0 hops` `.Dec 11 12:46:18.173: DHCPD: setting giaddr to 192.168.0.1.` `.Dec 11 12:46:18.173: DHCPD: adding relay information option.` `.Dec 11 12:46:18.173: UDP: sent src=192.168.0.1(67), dst=10.0.0.1(67),length=249` `.Dec 11 12:46:18.173: DHCPD: BOOTREQUEST from 0002.de15.3ed8 forwarded to 10.0.0.1.` This issue was observed after the ubr7246VXR was upgraded to 12.2(15)BC1 from 12.1(13)EC4. BootP clients (Qam Modulators) sent DHCP BootP requests through the CMTS (ingress FE, egress POS), no cable interfaces involved, on the LAN to the DHCP server. The packets are shortened and the DHCP server may drop the requests due to this fact. Workaround: Revert to 12.1(13)EC4.
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.
CSCed27848	UBR with IOS 12.2(15)BC1 and 12.2(15)BC1a has a problem with loading startup-config after reload with BPI+ configuration and cable modems. When BPI+ is enabled in a cable modems' config file after reload CMTS doesn't load startup-config This is version specific 12.2(15)BC1 and 12.2(15)BC1a seems to have this issue. There are no know workarounds.
CSCed28844	When a gate transits to the "committed" state, then back to "reserved", and to "committed" again, a new gate-open message is sent again, which is not desired. There are no known workarounds.
CSCed29514	A Cisco 7200 series NPE-G1 built-in GE (SBeth) MAC filter may accept NULL DAs (00-00-00-00-00-00). This unintentional behavior may pose a denial of service security risk in customer environments when their networks are flooded with NULL DAs. This issue is observed when NULL DAs are presented to an NPE-G1 GE interface. This situation may be either a third-party vendor product flaw or a third-party vendor documentation error. (The third-party vendor documentation states that NULL DAs may be used for unused MAC Filter entries, implying that they are not accepted.) There are no known workarounds.
CSCed36625	On cable routers, including uBR7200s and uBR10ks, CPE OSs such as Linux and FreeBSD may appear to frequently change the mac address of their gateway IP address. Linux will show: `Dec 15 00:12:17 home /kernel: arp: 192.168.0.1 moved from` `00:01:42:1d:4d:54 to 00:01:42:1d:4d:a8 on dc0` `Dec 15 00:13:26 home /kernel: arp: 192.168.0.1 moved from` `00:01:42:1d:4d:a8 to 00:01:42:1d:4d:54 on dc0` `Dec 15 00:26:17 home /kernel: arp: 192.168.0.1 moved from` `00:01:42:1d:4d:54 to 00:01:42:1d:4d:a8 on dc0` `FreeBSD will show:` `arp: 10.0.0.1 moved from 00:08:e2:33:0c:54 to 00:08:e2:33:0c:70 on ed0` `arp: 10.0.0.1 moved from 00:08:e2:33:0c:70 to 00:08:e2:33:0c:54 on ed0` This issue occurs when cable bundling is configured. Modems and CPEs on the bundle slave interface(s) will experience the problem. Those on the master interface will not experience it. The issue is that the L2 header for arp replies and arp requests are not consistent on a bundle slave. An arp reply will have a source mac in the L2 header of the bundle slave interface. A broadcast arp request will have a source mac of the bundle master and the arp request packets will have a mac source of the bundle master. Workaround: In theory, using a static arp entry on the CPE device binding the gateway IP address to the mac address of the CMTS slave interface will prevent the CPE from changing its arp entry for the gateway.
CSCed53355	When overlapping IP address ranges are configured for cpe's in separate VPN's in an MPLS/VPN configuration, it was observed that the host db on the npe didn't match the host db on the clc for at least one cpe that had an ip address that duplicated another cpe on the same clc. This may cause problems with source-verify and max-host. Workaround: Use unique IP addresses for each cable interface or subinterface.
CSCed56281	Although PPPoE client has connected behind CM, It is not outputted by "show interface cable x/x modem [SID]". This issue occurs only MC16U and/or MC28U. MC16C and/or MC28C has no this defect. There is no affect for communicating of PPPoE client. This is cosmetic problem. There is a mistake made in the fix and it has been corrected by the fix for CSCed75131. So please pick up that fix as well when applying this fix. There are no known workarounds.
CSCed61110	Cisco ubr7200 series CMTS running IOS release 12.2(15)BC1 may experience a software-forced reload after a watchdot timeout in CMTS MAC Timer process. The failure occurred on a platform with NPE-G1, once so far. There are no known workarounds.
CSCed61686	Using a local ToD Server when MPLS/VPN is configured was not routing ToD packets correctly. This fix allows Local ToD Time server to be configured with MPLS/VPN. There are no known workarounds.
CSCed63206	The linecards reload. This issue is caused by an ipc-timeout bcz of buffer depletion. There are no known workarounds.
CSCed64701	Unexpected packet loss at a certain rate and frame size and the overrun incrementing on the interface can be observed on the GigaEthernet Interfaces. There are no known workarounds.
CSCed65148	A UBR7200 may experience a reload with the following given as the cause of the reload in the show version: `System returned to ROM by break at PC 0x607C35F0` There are no known workarounds.
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.
CSCed67484	CSCed14039 fixed A WDT problem for the NPE-G1. A first set of diffs were ported from this DDTS to Cable BC release train in Nov., 2003. Later another set of diffs were committed to the same DDTS that fixes the problem at more of a root cause level. This DDTS was opened to port the 2nd commit against CSCec14039 to the Cable BU branches. As of commit of this DDTS to Cable BU branches, NPE-150 support will break. Cisco has let this NPE-G1 commit moved forward and decided not to support NPE-150 any more. There are no known workarounds.
CSCed68043	ARP Filter counters do not clear. uBR10k and uBR7246 platforms are affected. ARP Filters are enabled and there is arp traffic that is being filtered. The counters in this example show command will not clear: `sqi-vxr2#sho cable arp-filter c3/0` `ARP Filter statistics for Cable3/0:` `Replies Rcvd: 4 total. 4 unfiltered, 0 filtered` `Requests Sent For IP: 4 total. 2 unfiltered, 2 filtered` `Requests Forwarded: 168 total. 14 unfiltered, 154 filtered` There are no known workarounds.
CSCed73075	An NPE-400 unexpectedly reloads. The reload was identified to be missing of CSCec58486 in the Cable BU BC train. This DDTS has been created to port CSCec58486 to 12.2(15)BC2 and 12.2(15)BC1c. There are no known workarounds.
CSCed77196	The ubr7100 does not enforce MAX-CPE on a CMTS interface when it's configured as a member of a bridge group. This is because the method used to glean host information relies on ARP and DHCP packets which may not be available to the CMTS code. As a result if the CMTS bridging code can not find a CPE's SID in the host table it will apply a default QoS setting which may provide a greater than expected downstream bitrate. This change does the following: •Stores the primary upstream SID for each CPE on the CMTS interface in the bridging table and passes the SID value to the CMTS bridging code when packets are bridged in a downstream direction. •Gleans information from upstream packets and adds the MAC address and SID information to the CMTS host tables. Note: It will not glean IP addresses. •Enforces the MAX-CPE setting on downstream packets. The following text was taken from the Release-note enclosure for CSCec86611: ubr7114 running 12.1(13)EC3 is configured in bridge mode.For the test Only 1 CM is connected with DS rate limited to 1 Mbps and with Max-cpe to 1 (without BPI) Initial test with one PC behind the CM is ok (big download limited in DS to 1 Mbps). If now we swap the PC with a new one (new IP address) and reset the CM, the user is able to get up to 7 Mbps for the same download. The problem is the following: The CMTS logs the MAX-cpe errors when seeing the US traffic (as the CMTS still has the old PC in its database) but arp table and bridge table are still polled. So the CMTS is bridging the traffic for this new PC to cable interface even if it is not associated to any SID's. Workaround: CMTS: clear cable host <old_host> ---> so now the new PC is associated to the sid of the CM. CMTS: increase the MAX-CPE to allow the new PC to be associated to the CM and let the old one get removed by timeout. CMTS: use BPI to encrypted dedicated traffic to that CM. CMTS: remove bridging setup. There are no known workarounds.
CSCed78236	SNMP GetBulk of docsQosMIBObjects.1 may cause CPUHOG error message. There are no known workarounds.
CSCed78829	Performance degradation was caused by changing NRNG_CR_ACF and NRNG_CR_TCF registers due to incorrect consideration for performance optimization. This affects only QPSK modulation. Software fix is simply checking for modulation profiles. if all modulation rates are using qpsk, different set of values are applied to these registers. There are no known workarounds.
CSCed83867	uBR7246VXR with NPE-1G and MC28U blades with "cable source-verify dhcp" enabled results in: 1. 100 % CPU load and flooding the CNR with service queries, the contributor to high CPU load is identified to be 'DHCPD Receive' process. 2. The few mac-address in the arp entry shows all zeros Workaround: Turning off the "cable source-verify dhcp" option in the config will bring the CPU back down.
CSCed86260	When two Cable interface are bundled, the ifInUcastPkts of the secondary cable interface is decreasing. There are no known workarounds.
CSCed86429	test cable dsc qos command is broken for DS service flows. Workaround: Use test cable dsc message command.
CSCed88709	When a service-policy that corresponds to a policy-map with no fair-queueing classes is applied outbound on a Cable interface and one class performs shaping the uBR7200 may drop outbound packets and generate error messages similar to the following: `%LINK-4-BADQID: Interface Cable4/0, bad output queue ID specified (265).` Packet drops when the shaping classes becomes active because of traffic rates that exceed the prescribed limits in the class. Workaround: Have at least one class with a fair-queueing configuration in the policy-map. This means using one of the "bandwidth", "priority", or "fair-queue" commands within the policy-map for at least one class.
CSCed89735	An uncorrectable ECC parity error may occur on a Cisco 7200 series that is configured with an NPE-G1. This issue is observed rarely when you enter the show sysctlr or the show tech command on the NPE-G1. Workaround: Do not enter the show sysctlr or the show tech command.
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.
CSCed91527	The Request Collision counter does not appear to be incrementing on the MC8u card, when using the show controller command. There are no known workarounds.
CSCed95046	Source verify is not performed for MC28U interfaces on ubr7200. There are no known workarounds.
CSCed95436	uBR7246VXR may run into a issue with the Total-Kbyte Value being to high when issuing the <Show Subscriber-Usage> command. This behavior has been observed on 12.2(15)BC1 and 12.2(15)BC1b. Example: `uBR7246VXR#show cable subscriber-usage over-consume` `Sfid Mac Address Enforce-rule Total-Kbyte Last-detect Last-penalty Pen` `Name Count time time Flag` `761 0000.0000.0002 RESA1-UP 4294967087 Mar10 21:55:01 Mar10 22:55:01 Act` `762 0000.0000.0002 RESA1-DOWN 4294967270 Mar10 21:55:01 Mar10 22:55:01 Act` `uBR7246VXR#show cable modem 0000.0000.0002 counters` `MAC Address US Packets US Bytes DS Packets DS Bytes` `0000.0000.0002 1631 219278 1467 1187222` `cable qos enforce-rule RESA1-UP` `penalty-period 60` `registered qos-profile 92` `enforced qos-profile 12` `monitoring-duration 120` `activate-rule at-byte-count 38400 upstream enforce` `enabled` `cable qos enforce-rule RESA1-DOWN` `penalty-period 60` `registered qos-profile 92` `enforced qos-profile 12` `monitoring-duration 120` `activate-rule at-byte-count 450000 downstream enforce` `enabled` `cable qos profile 12 max-burst 1544` `cable qos profile 12 max-downstream 575` `cable qos profile 12 max-upstream 128` `cable qos profile 92 max-burst 1544` `cable qos profile 92 max-downstream 1600` `cable qos profile 92 max-upstream 128` This issue was discovered after a period of time. Currently amount of time and circumstances in which the event takes places are being explored. There are no known workarounds.
CSCee00703	Having only server IP and src port in connection info object causes client failed to map to specific session as server src port changes, so COPS msg cannot be sent to proper session. This happens after any TCP reset due to link loss when interface is shut or HA switchover and a new connection is established. This feature is also needed in configuration with multiple connections per each subnet to a single server. As in cable network's packetcable voice deployment, such configuration is required for HA on VXR platform. There are no known workarounds.
CSCee00790	Under certain conditions, the admission of periodic events (ugs/ugsad/nrtps/rtps) could lead to a crash. This is likely to happen only when the channel rate is 160ks/s (not a common channel rate). Workaround: Do not configure the channel for 160ks/s in production networks.
CSCee06228	The SRP protocol on a Cisco uBR7246VXR may not fully initialize during the boot sequence. This issue is observed on a Cisco uBR7246VXR running Cisco IOS Release 12.2(15)BC1b when one SRP side is wrapped. The symptom may also occur on a Cisco 7200 series and is not release-specific. Workaround: Force a wrap by entering the srp ips request forced-switch command and remove this forced wrap. Note that you have to do this manually after a reload/reboot.
CSCee11283	ubr7246vxr(config-if)#cable up 0 power-adjust continue ? <2-15> Power level in dB The default "continue ranging" value in CMTS software to date is 1 dB. This value is an arbitrary value in the software and does not reflect Cisco RF Engineering best practices recommendation of a window of 3-6. The 1 dB window can unnecessarily cause cable modems to attempt to come online and then fall offline and repeat this cycle thus causing customers to have intermittent network connectivity. Workaround: Change the command on the CMTS to open the window by hand: `cable up X power-adjust continue 4`
CSCee12282	A uBR7246VXR CMTS router with output QMC traffic-shaping enabled and active on a cable interface can leak processor pool memory under high load, i.e. when multiple particles are used for packet buffering. Workaround: Remove output QMC shaping command from cable interface to stop leak; reload router to reclaim memory. There are no known workarounds.
CSCee12868	docsIfCmtsCmStatusSignalNoise returns a wrong value. It should represent 10th dB rather than just dB. Workaround: Multiply the received number by 10.
CSCee16342	The CMTS may reload unexpectedly when the following command is issued: `show packetcable gate <gateid>` The unexpected reload occurs if the command is issued during the time duration when that particular gate is being deleted (e.g., as a result of call teardown). There are no known workarounds.,
CSCee17648	MAC Scheduler incorrectly Calculates max-unfrag-sz resulting in packet loss. Workaround: Modify Modulation profile so max burst option matches that of max-unfrag-sz.
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".
CSCee23838	If a downstream packet received at the CMTS is destined for a modem whose ARP entry is incomplete or not present in the CMTS arp database, the CMTS goes into a loop of issuing out DHCP lease queries and receiving ACKs till an upstream packet for the modem populates the ARP database on the CMTS. Workaround: Disable "no cable arp" on the cable interface.
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.
CSCee27443	Second service flow can not be created if Docsis 1.0+ vendor specific encodings are used for data transfer. This is a regression issue which was triggered by CSCeb21271 and CSCdz66185. Workaround: For any TOS except 5, the second DS flow will be created but bandwidth will end up being reserved for those flows.
CSCee27994	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.
CSCee29081	CMTS does nor receive the DHCP response to a DHCP lease query even though the response was sent from the DHCP server. CSCee26361 fixed this problem. What this DDTS is now adding is a check in CMTS code to not continue with dhcp gleaning if a response to a lease query is received by the CMTS. There are no known workarounds.
CSCee32609	The CMTS may report a CPU hog error when processing GetBulk SNMP requests. There are no known workarounds.
CSCee37649	Under high load with BPI active, the ubr7200 may lock up, permitting no console access. Higher level protocols will be unresponsive (for example, the system will not respond to ARP requests). The system may still forward packets. Workaround: Take off the load for a period of time (physically disconnect all connected modems) until the system recovers. Alternative workaround: Disable BPI on systems with constantly high CPU load.
CSCee46169	Old host are getting aged out of the arp table. The same host is not getting aged out of the SID table as evident in a "show interface cable 1/0 modem" <z>. Since the modem never gets aged out of the SID table max CPE is eventually reached. The next CPE to tries to register behind that modem will not be permitted. A duplicate IP error message is inserted into the log. This issue exist only in ridge mode. To allow subsequent cable modem onto that cmts the bad host must be removed from the SID table with a "clear cable host" or the cable modem must be power cycled. There are no known workarounds.
CSCee46490	Users and internal tech support have a need to monitor the status and collect debug information from the RF cards with on-board processors (e.g., MC520 and MC28U). This is currently done by using telnet or if-con to login to the line card and issue show commands to collect the data. Logging into the line card should only be done by the direction of a Cisco support person. New options to the existing "show controllers" CLI command will be added to collect line card data from the NPE. Workaround: Telnet or if-con to the line card.
CSCee47911	The number of errors on the "show interface cable x/y upstream z" has increased dramatically after upgrading to 12.2(15)BC2a. This issue appears on the MC28C. This does not appear to be affecting packet loss. There are no known workarounds.
CSCee49594	The ENTITY-MIB does not recognize the NPE-G1 processor. There are no known workarounds.
CSCee52217	The output for "debug cable l2-vpn conditional" is a bit cryptic because the corresponding SID number is displayed in hex. This DDTS is to request the SID number to be displayed in decimal format to improve usability. There are no known workarounds.
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.
CSCee55444	See CSCed06821 for modem security details which prevents modems from coming online and getting stuck in init(o). Modems which get an ip address which is not the same subnet as the primary ip address of the cable interface can get stuck in init(o). Workaround: Use the ip source-interface loopback 0 command.
CSCee55916	Users can logon to RF line cards with onboard processors without having "service internal" configured on the NPE/PRE. User executes the telnet CLI command to logon to an RF line card without "service internal" configured. There are no known workarounds.
CSCee55989	When SNMP query getnext/getbulk DOCS-QOS-MIB: docsQosCmtsMacToSrvFlowTable (docsQosCmtsIfIndex), NMS will see the infinite loop if the number of CMs is greater than 1000. All the platforms are affected. Workaround: Use cli to get the info. If only docsQosCmtsIfIndex is needed, use the CM mac address, snmp get exact cdxCmCpeIfIndex which is the same value as docsQosCmtsIfIndex.
CSCee61429	The MC28u, MC28x, MC16u, and MC16x real time clock drifts from the NPE clock. Due to a code omission in IOS 12.2(15)CX, 12.2(15)BC1a-e, and 12.2(15)BC2a-d, the real time clock on the MC28u, MC28x, MC16u, and MC16x Cable Line Cards for the uBR7246VXR is not kept in sync with the real time clock on the NPE. The estimated drift is approximately +/- 1.3 minutes per month, and is somewhat temperature sensitive. The linecard clock is updated each time the system is reloaded, but not afterwards. The linecard clock is not updated even if NTP is configured on the NPE. The drift can cause a problem where modems will eventually be in the reject(ts) state if the modem config file is set to contain a timestamp (see CSCef71411) and the drift is greater than 30 seconds. Workaround: If possible, write a script to periodically extract the current time from the NPE and login to the linecard using if-con/if-quit and set the time to the NPE value. Alternative workaround 1: Reload during a service window. Alternative workaround 2: Turn off timestamp.
CSCee64115	Dynamic load balancing across interfaces will not work for the last upstream channel of an interface. This issue is predominantly seen if an interface is added to a load balancing group after the system was booted, and after modems are already online on the system. Workarounds: On an interface supporting Virtual Interfaces, configure an additional upstream channel, but do not use it. If Virtual Interfaces are not supported, ensure that the last US channel on an interface participating in load balancing is a member of a load balancing group with at least two US channels on the affected interface. If that is not applicable to your system, rely on static load balancing.
CSCee66672	High CPU might be seen when OIR cable linecard if CM onoff trap is enabled and throttled. Workaround: Disable the CM onoff trap before OIR: `no cable enable-trap cmonoff-notification`
CSCee67459	Payload header suppression fails with an immediate answer and auto commit functionality on the CMTS. This results in calls to a voice mail server failing, as the CMTS incorrectly processes the DSC messages. There are no known workarounds.
CSCee68920	If running static map advance when using BC2a code, run the command sh controller cx/y uz to verify that using map-advance static default settings in BC2 code yields: `ubr#sh contr c3/0 u0` `Map Advance (Dynamic) : 5480 usecs or higher.` This is extremely high. If the user changes the map-advance from the default of dynamic to static, this bug will add an extra 2000 use of time to the calculation. Because this command is per DS, this could affect upstream throughput for all users on all upstream ports from the same DS port. Workaround: Using the cab map-advance static 100 command will make the calculation more reasonable, but it will display !1024 for all the affected modems in the sh cab mode command.
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.
CSCee70014	Interface load balancing may fail to balance the load under the following circumstances: 1. The highest load upstream channel on the originating interface is associated with a load balancing group. This load balancing group is not configured on the target interface. This issue should be avoided by making sure that load balancing group configurations match on all US channels across load balanced interfaces. 2. The load on the US channel(s) associated with the load balancing group on the target interface have a higher load than the US channel on the originating interface. This issue is not usually a problem and/or is assumed to have only minor operational impact. There are no known workarounds.
CSCee76342	When running PacketCable call, without setting secondary RKS ip address in Event-Generation-Info object in Gate-Set message, the CMTS may unexpectedly reload. Workaround: Set secondary RKS ip address in Event-Generation-Info object 9it can even be a fake one).
CSCee81149	With IOS 12.2(15)CX it is possible to configure 125 KHz steps. With IOS 12.2(15)BC2a it is not possible to configure 125 KHz steps. A change was made to minimum frequency step size since the original release of MC28u in 12.2(15)CX. This was done in order to support alternate suppliers of upconverter modules. This change restricts the step size to 250 Khz increments. That is why 168.125 Mhz is not accepted by 12.2(15)BC2a software. There are no known workarounds.
CSCee91789	Payload Header Suppression causes voice quality to significantly deteriorate. This only impacts Transam on VXR. Legacy LCs are OK. Workaround: Either disable downstream rate limiting or configure max sustain rate and min reserved rate to PHS-off rates.
CSCef04492	snmpwalk on cdrqCmtsCmStatusTable does not show consistent result. There are no known workarounds.
CSCef08652	The cable rate-limit-algorithem queue-per-cir command does not allow communication to the MC28U card. Work-around is to configure it directly on the linecard. 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.
CSCef09770	Each flow appear in a different time with a different sid in docsIfCmtsServiceTable. However, the docsIfCmtsServiceCreateTime are the same for all sid's. There are no known workarounds.
CSCef19398	Momentary (about 1 sec) of ping packet lost was observed when changing downstream modulation rate on another cable interface on the same line card. Once DS cable interface is re-initialized, ping operation returns to normal (successful reception of ping packets). There are no known workarounds.
CSCef20890	A Cisco ubr7246VXR running Cisco IOS Release 12.2(15)BC1 may reload unexpectedly due to a bus error. There are no known workarounds.
CSCef21709	Under rare and unusual conditions, CMTS may unexpectedly reload when heavily loaded with voice and data traffic. There is no way to predict, detect, or know when this is about to happen. There are no known workarounds.
CSCef22962	If BPI is enabled, DSx messages with key sequence number 0 are rejected. Workaround: Wait until the key sequence number changes and retrying the command.
CSCef27859	This code improves the modem bring up 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.
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.
CSCef30671	If BPI is active on multiple service flows on a modem, key activation may fail on secondary service flows. This will occur if the modem requests TEK keys using transmit opportunity associated with secondary SIDs. There are no known workarounds.
CSCef31956	This is a bug to improve reverse arp lookup on the CMTS for modem bring up. There are no known workarounds.
CSCef37495	Sync Pulse failure detection mechanism is not working for N+1/7200 solution. Workaround: Use Fast Failure Detection for crash detection.
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
CSCef54205	If an MTA has multiple lines and both the lines are being used to make calls, call failures could happen in certain scenarios. Scenario 1: Line 1 has a call in progress, meanwhile, Line 2 makes a new call, then hangs up, and makes another new call, then hangs up, and so on. After sometime line 2 will not be able to make a call. Scenario 2: Line 1 is having a call, Line 2 makes a new call. Before Line 2 hangs up, Line 1 hangs up and makes another call. Same for Line 2, it hangs up and makes another call _before_ Line 1 hangs up, and vice versa. After sometime line 1 and 2 will not be able to make new calls. The problem happens because activity count on the CMTS does not get decremented in each of the above scenarios (even if the call on a line goes away). As a result the activity count reaches its limit and new calls are not allowed. However, at any instance, if both lines are disconnected, the activity count will be reset again. Workaround: Increase the activity count on BTS to a large number. This way, even if the activity counts are not decremented at call termination, new calls will be allowed till the activity count is maxed out. When both the lines are terminated, the count will be reset automatically. In the case where the MTA contains 2 lines only, it should not have a big impact since it won't use up a lot of resources even if someone is trying to abuse the system by making multiple calls simultaneously. Moreover, it is a counter issue only, all the actual resources, such as service-flows, gates, etc, they are all freed up.
CSCef59093	Cisco uBR-MC28U cable interface line card may crash in ubr7200 series CMTS running IOS release 12.2(15)BC2b. The issue only occurs with MC28U line card. MC16C in the same chassis works fine. There are no known workarounds.
CSCef73242	Cisco ubr7200 series CMTS running IOS release 12.2(15)BC2b may not guarantee configured QoS levels on Downstream dynamic Service Flows in VoIP networks. The issue can be seen with very high SFIDs (between 32768 and 65535) and when cable modems are provisioned with non-zero Active QoS Timeout. Workaround: Increase the bandwidth for Best Effort (BE) flow.
CSCef74063	Router can crash on under error condition that gate is freed on RP, but not LC prior to resource being allocated through dsa-req from eMTA. Gate lookup failure on RP cause illegal access to stale gate entry pointer, and can crash the RP. This issue does not affect prior release train before 12.3(9)BC. There are no known workarounds.
CSCef86784	Enabling the DOCSIS traps using CLI "snmp-server enable traps docsis-cmts" could result in a traceback. There are no known workarounds.
CSCin21618	A uBR7246 with an OC-12 SRP interface can crash with the following sequence of commands: `test pas oir 2 pull` `test pas oir 2 push` `test pas oir 1 pull` `test pas oir 1 push` Workaround: Do not test pas oir the high slot of a double wide card. test pas oir 1 pull followed by a push can be done repeatedly without error.
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.

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