cc/td/doc/product/atm/c8510/wa5/12_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for the
Catalyst 8510 MSR for Cisco IOS Release 12.0(4a)W5(11a)

Release Notes for the
Catalyst 8510 MSR for Cisco IOS Release 12.0(4a)W5(11a)

August 22, 2000

Catalyst 8510 MSR Cisco IOS Release 12.0(4a)W5(11a)

This document describes the features and caveats for Cisco IOS Release 12.0(4a)W5(11a) software for the Catalyst 8510 MSR. This software is based on Cisco IOS Release 12.0(4a).

For a list of caveats that apply to Release 12.0(4a)W5(11a) software, refer to the "Caveats" section.

Contents

This document includes the following sections:

Introduction

The Catalyst 8510 MSR provides switched ATM connections to individual workstations, servers, LAN segments, or other ATM switches and routers using fiber-optic, unshielded twisted-pair (UTP), and coaxial cable.

Note The ATM switch processors (hardware version 4.0 or higher) and all port adapters can be installed in the Catalyst 5500 switch chassis.

System Requirements

This section describes the system requirements for Cisco IOS Release 12.0 and includes the following sections:

Memory Requirements

The DRAM memory configuration is 64-MB DRAM (MEM-ASP64M), which is the default for the Catalyst 8510 MSR product.

Hardware Supported

Table 1 lists the interfaces supported by the Catalyst 8510 MSR and Cisco IOS Release 12.0(4a)W5(11a) software and their minimum software release requirements.


Table 1: Supported Interfaces and Their Minimum Software Requirements

Part Number Description Minimum Software Requirement

WAI-OC3-4MM

4-port STS-3c/STM-1 multimode fiber port adapters

WAS1-1

WAI-OC3-4SS

4-port STS-3c/STM-1 single-mode fiber port adapters

WAS1-1

WAI-OC3-4U5

4-port STS-3c/STM-1 UTP-5 port adapters

WAS1-1

WAI-OC3-4SSLR

4-port STS-3c/STM-1 SMF long reach port adapters

WAS3-2

WAI-OC3-1S3M

OC-3 mix port adapter module, 1 IR+ port and 3 MM ports

WAS3-1

WAI-OC12-1MM

1-port STS-12c/STM-4c multimode fiber port adapters

WAS1-2

WAI-OC12-1SS

1-port STS-12c/STM-4c SMF port adapters

WAS1-1

WAI-OC12-1SSLR

1-port STS-12c/STM-4c SMF long reach port adapters

WAS3-2

WAI-ATM25-12P

12-port ATM 25 port adapters with 96-pin telco cable

WAS3-2

WAI-T3-2BNC

2-port DS-3 port adapters

WAS1-1

WAI-E3-2BNC

2-port E3 port adapters

WAS1-1

WAI-T3-4BNC

4-port DS-3 port adapters

WAS3-1

WAI-E3-4BNC

4-port E3 port adapters

WAS3-3

WAI-T1-4RJ48

4-port T1 (ATM) with RJ-48 interface port adapters

WAS3-1

WAI-E1-4RJ48

4-port E1 (ATM) with RJ-48 interface port adapters

WAS3-1

WAI-E1-4BNC

4-port E1 (ATM) with BNC interface port adapters

WAS3-1

WAI-T1C-4RJ48

4-port T1 (circuit emulation) with RJ-48 interface port adapters

WAS3-1

WAI-E1C-4RJ48

4-port E1 (circuit emulation) with RJ-48 interface port adapters

WAS3-1

WAI-E1C-4BNC

4-port E1 (circuit emulation) with BNC interface port adapters

WAS3-1

L1010-PWR-DC

Power supply DC

WAS3-1

L1010-ASP-B-FC1

ASP1 with FC-per-class queuing (FC-PCQ2)

WAS1-3

L1010-ASP-B-FCPFQ

ASP1 with FC-per-flow queuing (FC-PFQ3)

WAS4-1

L1010-ASP-C-FC1

Hot-swappable ASP with FC-PCQ

W5-5

L1010-ASP-C-FCPFQ

Hot-swappable multiservice switch route processor

W5-5

C85MS-4E1-FRRJ48

4-port CE1 with RJ-48c interface Frame Relay port adapters

W5-5

WS-X5165

ATM-Fabric Integration Module for the Catalyst 5500

W5-5

C85MS-1DS3-FRBNC

1-port CDS3 Frame Relay port adapter

W5-9

C85MS-ATM25-4P

4-port 25-Mbps port adapter

W5-9

C85MS-8T1-IMA

8-port T1 port adapter with inverse multiplexing over ATM

S851R2-12.0.4W

C85MS-8E1-IMA-120

8-port E1 port adapter with inverse multiplexing over ATM

S851R2-12.0.4W

1ASP = ATM switch processor.
2FC-PCQ = feature card per-class queuing.
3FC-PFQ = feature card per-flow queuing.

Determining Your Software Release

To determine the version of Cisco IOS software currently running on the Catalyst 8510 MSR, log into the switch and use the show version EXEC command. The following is sample output from the show version command. The version number is indicated on the second line as shown below:

Cisco Internetwork Operating System Software
IOS (tm) LS1010 W5-5 Software (LS1010-WP-M), Version 12.0(4a)W5(11a)

Additional command output lines include more information, such as processor revision numbers, memory amounts, hardware IDs, and partition information.

Other Firmware Code

Some of the port adapters supported on the Catalyst 8510 MSR have upgradeable FPGA and functional images. The FPGA and functional images include caveat fixes, but in most cases, it is not necessary to upgrade. The release notes that describe the caveats from the FPGA and functional images are available on the World Wide Web at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/atm/c8540/fpga_rel/index.htm

For information describing the firmware update process, refer to the section "Maintaining Functional Images (Catalyst 8510 MSR and LightStream 1010)" in the chapter "Managing Configuration Files, System Images, and Functional Images" in the ATM Switch Router Software Configuration Guide.

Feature Set Tables

The Cisco IOS Release software is packaged in feature sets (also called software images) depending on the platform. Each feature set contains a specific set of Cisco IOS features. Table 2 lists the Cisco IOS software feature sets available for the Catalyst 8510 MSR in Cisco IOS Release 12.0(4a)W5(11a) software.


Table 2: Feature Sets Supported by the Catalyst 8510 MSR
Feature Set 12.0(4a)W5(11a) 12.0(1a)W5(9) 12.0(1a)W5(5b) 11.3(3a)WA4(6)

Left-justified E.164 AFI support

x

x

x

x

SNMP1

x

x

x

x

Asynchronous support

x

x

x

x

PPP2 (SLIP3/PPP)

x

x

x

x

IP4

x

x

x

x

NTP5

x

x

x

x

TACACS+6

x

x

x

x

Telnet

x

x

x

x

Point-to-point and point-to-multipoint permanent VCCs7 and VPCs8

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.0)

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 3.1)

x

x

x

x

Point-to-point and point-to-multipoint switched VCCs and VPCs (UNI 4.0)

x

x

x

x

Multipoint-to-point UNI signaling

x

x

x

x

Soft VCCs and VPCs

x

x

x

x

VP tunneling

x

x

x

x

VPI/VCI range support in ILMI 4.0

x

x

x

x

PNNI hierarchy

x

x

x

x

ILMI version 4.0

x

x

x

x

IISP9

x

x

x

x

LANE10 client (LEC11) and LANE Services (LES12/BUS13/LECS14) on ASP15

x

x

x

x

Token Ring LANE services

x

x

x

x

ATM ARP16 server on ASP

x

x

x

x

ATM ARP client on ASP

x

x

x

x

ATM tag switch router (TSR)

x

x

x

x

Port snooping

x

x

x

x

OAM17 F4 and F5

x

x

x

x

E.164 address translation

x

x

x

x

E.164 autoconversion

x

x

x

x

Circuit emulation

x

x

x

x

ATM access lists

x

x

x

x

ATM accounting

x

x

x

x

ATM RMON18

x

x

x

x

Multiple, weighted, dynamic thresholds for selective packet marking and discard

x

x

x

x

Shaped VP tunnels for CBR traffic (FC-PFQ only)

x

x

x

x

Substitution of other service categories in shaped VP tunnels (FC-PFQ feature cards only)

x

x

x

x

Dual leaky bucket policing (FC-PFQ feature cards only)

x

x

x

x

Scheduler/Service Class/PVC configuration for FC-PFQ feature cards

x

x

x

x

Logical multicast support (up to 254 leaves per output port, per point-to-multipoint VC) (FC-PFQ feature cards only)

x

x

x

x

Network clocking enhancements for smooth switchover (FC-PFQ feature cards only)

x

x

x

x

Per-VC or per-VP nondisruptive snooping (FC-PFQ feature cards only)

x

x

x

x

Support for non-zero MCR19 on ABR connections (FC-PFQ feature cards only)

x

x

x

x

Access lists on ILMI registration

x

x

x

x

CUGs

x

x

x

x

ATM soft restart

x

x

x

x

ATM accounting enhancements

x

x

x

x

CISCO-SYSLOG-MIB support

x

x

x

x

CISCO-CONFIG-COPY-MIB support

x

x

x

x

Signaling diagnostics and MIB

x

x

x

x

Supplemental AToM MIB

x

x

x

x

E1 Frame Relay Port Adapter

x

x

x

Frame Relay to ATM Interworking Features on the Channelized E1 Port Adapter

x

x

x

Hierarchical VP Tunnels

x

x

x

Remote logging for accounting

x

x

x

Tag Switching VC-Merge on Non-UBR VP Tunnels and Hierarchical VP Tunnels

x

x

x

PNNI Complex Node Representation

x

x

x

Support for ATM-Fabric Integration Module in Catalyst 5500

x

x

x

PNNI explicit paths

x

x

PNNI alternate link selection

x

x

Tag switching CoS

x

x

Network Clock Distribution Protocol

x

x

Simple Gateway Control Protocol

x

x

Inverse Multiplexing over ATM (IMA) groups

x

ATM End System Address (AESA) gateway

x

ATM overbooking

x

Framing overhead

x

1SNMP = Simple Network Management Protocol.
2PPP = Point-to-Point Protocol.
3SLIP = Serial Line Internet Protocol.
4IP = Internet Protocol.
5NTP = Network Time Protocol.
6TACACS+ = Terminal Access Controller Access Control System.
7VCCs = virtual channel connections.
8VPCs = virtual path connections.
9IISP = Interim-Interswitch Signaling Protocol.
10LANE = LAN Emulation.
11LEC = LAN Emulation Client.
12LES = LAN Emulation Server.
13BUS = broadcast and unknown server.
14LECS = LAN Emulation Configuration Server.
15ASP = ATM switch processor.
16ARP = Address Resolution Protocol.
17OAM = Operation, Administration, and Maintenance.
18RMON = Remote Monitoring.
19MCR = minimum cell rate.

Release Names, Versions, and Part Numbers

Table 3 lists the release names, versions, and part numbers used with the Catalyst 8510 MSR.


Table 3:
Release Name Release Version Part Number

WAS1-1

11.1.(4)

SF-WAS1-11.1.4

WAS1-2

11.1.(410)

SF-WAS1-11.1.410

WAS1-3

11.1.(6)

SF-WAS1-11.1.6

WAS1-4

11.1.(8)

SF-WAS1-11.1.8

WAS1-5

11.1.(9)

SF-WAS1-11.1.9

WAS1-6

11.1.(11)

SF-WAS1-11.1.11

WAS2-1

11.1.(410)

SF-WAS2-11.1.410

WAS2-2

11.1.(6)

SF-WAS2-11.1.6

WAS2-3

11.1.(8)

SF-WAS2-11.1.8

WAS2-4

11.1.(9)

SF-WAS2-11.1.9

WAS2-5

11.1.(11)

SF-WAS2-11.1.11

WAS3-1

11.2(2)WA3(1a)

SF-WAS3-11.2.2

WAS3-2

11.2(5)WA3(2b)

SF-WAS3-11.2.5

WAS3-3

11.2(8)WA3(3)

SF-WAS3-11.2.8

WAS3-4

11.2(10)WA3(4)

SF-WAS3-11.2.10

WAS3-5

11.2(12)WA3(5)

SF-WAS3-5

WAS3-6

11.2(15)WA3(6)

SF-WAS3-6

WAS3-7

11.2(15)WA3(7)

SF-WAS3-7

WAS4-1

11.2.0(8.0.1)FWA4(1)

SF-WAS4-11.2.8.1S

WAS4-2

11.3(0.8)TWA4(2)

SF-WAS4-2

WAS4-4

11.3(2a)WA4(4)

SF-WAS4-4

WAS4-6

11.3(3a)WA4(6)

SF-WAS4-6

WAS4-7

12.0(2a)

SF-WAS4-7

W5-5

12.0(1a)W5(5b)

SF-WAS5-5

W5-9

12.0(3c)W5(9)

SF-WAS5-9

W5-11a

12.0(4a)W5(11a)

S851R2-12.0.4W

Release Name to Version and Part Number Matrix

New and Changed Information

This section lists new features that appear in this and previous releases of Cisco IOS Release 12.0W5 software.

New Features in Release 12.0(4a)W5(11a)

The following new features are available for the in Cisco IOS Release 12.0(4a)W5(11a):

See the "Related Documentation"section for a list of documents that describe these features.

New Features in Release 12.0(1a)W5(9)

The following new features are available for the Catalyst 8510 MSR in Cisco IOS Release 12.0(1a)W5(9).

See the "Related Documentation"section for a list of documents that describe these features.

Caveats

This section lists the caveats for each release. Use Table 4 to determine if a particular caveat applies to your software release, or if a particular caveat was corrected in your software release. These caveats are described in detail in the following sections:


Table 4: Release Caveats and Caveats Corrected Reference 
DDTS Number Software Release Software Release Software Release
12.0(4a)W5(11a) 12.0(1a)W5(9) 12.0(1a)W5(5b)
Corrected Caveat Corrected Caveat Corrected Caveat

CSCdi55937

x

x

x

CSCdi74229

x

x

x

CSCdi75584

x

x

x

CSCdi82954

x

x

x

CSCdi83275

x

x

x

CSCdi92142

x

x

x

CSCdj01016

x

x

x

CSCdj01757

x

x

x

CSCdj10889

x

x

x

CSCdj11070

x

x

CSCdj13565

x

x

x

CSCdj18430

x

x

x

CSCdj18583

x

x

x

CSCdj18678

x

x

x

CSCdj25772

x

x

x

CSCdj31762

x

x

CSCdj42967

x

x

x

CSCdj47998

x

x

CSCdj54954

x

x

x

CSCdj68412

x

x

x

CSCdj71109

x

x

x

CSCdj71876

x

x

x

CSCdj78305

x

x

x

CSCdj80396

x

x

x

CSCdj82930

x

x

x

CSCdj84344

x

x

CSCdj84379

x

x

x

CSCdj84981

x

x

CSCdj85853

x

x

x

CSCdk03049

x

x

CSCdk07378

x

x

x

CSCdk10398

x

x

x

CSCdk17977

x

x

CSCdk22484

x

x

CSCdk22791

x

x

CSCdk25256

x

x

x

CSCdk26482

x

x

x

CSCdk27725

x

x

x

CSCdk33601

x

x

CSCdk41001

x

x

CSCdk42052

x

CSCdk47516

x

x

x

CSCdk49213

x

x

CSCdk52436

x

x

CSCdk56557

x

x

x

CSCdk57536

x

x

x

CSCdk62547

x

x

CSCdk63547

x

x

CSCdk69639

x

x

CSCdk73583

x

x

CSCdk73733

x

x

x

CSCdk76280

x

x

CSCdk77032

x

x

CSCdk78469

x

x

CSCdk78881

x

x

CSCdk79426

x

x

x

CSCdk82708

x

x

CSCdk84269

x

x

x

CSCdk84355

x

x

CSCdk88859

x

CSCdk90091

x

x

CSCdk90147

x

x

CSCdm04013

x

x

CSCdm06168

x

x

CSCdm07874

x

x

CSCdm08234

x

x

x

CSCdm11577

x

x

CSCdm15900

x

x

CSCdm19018

x

x

CSCdm19073

x

x

CSCdm19670

x

x

CSCdm20257

x

x

CSCdm23579

x

x

CSCdm29503

x

x

x

CSCdm29650

x

x

CSCdm32506

x

x

CSCdm34634

x

x

CSCdm36745

x

x

CSCdm36790

x

x

CSCdm36800

x

CSCdm38218

x

x

CSCdm 43851

x

x

CSCdm44497

x

x

CSCdm46569

x

x

CSCdm48886

x

x

CSCdm52827

x

x

CSCdm56393

x

x

CSCdm58868

x

x

CSCdm77907

x

CSCdm77939

x

CSCdm80015

x

CSCdm80628

x

CSCdm80806

x

CSCdm89519

x

x

CSCdm91060

x

x

CSCdm92990

x

x

CSCdm94019

x

x

CSCdp02816

x

CSCdp04109

x

CSCdp16253

x

CSCdp20865

x

Cisco IOS Release 12.0(4a)W5(11a) Caveats Corrected

Symptom: When disabling the Cisco Discovery Protocol (CDP) on an ATM interface that has been configured as a LEC, the CDP configuration is not saved to NVRAM.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Symptom: After hotswapping an OC-3 LR port adapter with an OC-3 MM port adapter, the system might fail unexpectedly.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port, the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Symptom: On a running release 11.3(3a)WA4(6), if an atm ping command is issued after a VC is removed via a link failure, a bus error might cause the system to fail unexpectedly.
Symptom: Soft VP and PVP cannot coexist due to VPI allocation errors.
Symptom: TR-LEC currently processes all registration requests received on its control distribute VC. It should only be doing this if the LEC id in the registration message matches up with its own LEC id.
Symptom: The does not accept PVCs terminating on its CPU port over point-to-point subinterfaces.
Symptom: CES (CBR) might show the interface as up while in loss of signal (LOS). Also, it does not send AIS while the interface is shut down or the uplink ATM was broken (when configured as structured mode).
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Symptom: The advertised priority is not updated for PGL if configured to match the advertised priority.
Symptom: When issuing a show running-config command the might fail unexpectedly, due to a bus error.
Symptom: The soft pvc count might not be included in atmfAtmLayerConfiguredVCCs.
Symptom: Configuring a channelized E1(CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the linecode violation and LES counters to increment continually.
Symptom: When forwarding a call setup from one VP tunnel to another, the might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.
Symptom: If a show debugging command is issued on a that is configured as a PNNI "childless uncle," an infinite loop condition might occur that will cause a watchdog timeout.
Symptom: When polling the sysObjectID of a Catalyst 8510 MSR, it returns 190, which is the sysObjectID of a Catalyst 8510 CSR. This situation causes a problem in Cisco Works for Switched Internetworks (CWSI), because the MSR has ATM interfaces. By mistaking an MSR for a CSR, ATMDirector will not work with the Catalyst 8510 MSR.
Symptom: On a PNNI signalling link, the Promina 4000 NET switch sends a message that prompts the system to send a CALL PROCEEDING message and then a RELEASE message with a cause code 8a ("VPCI/VCI unacceptable"). When the call goes out on a uni3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.
Symptom: For the 12.0(4a)W5(11a) release, the units for the atm soft vc command are not backwards-compatible with the 11.3(3a)WA4(6) release.
Symptom: Issuing the atm snoop interface command might cause the FC1 system to fail unexpectedly.
Symptom: After resetting an ATM interface, the soft VCs terminating on that interface might not come up for certain VPI/VCI values.
Symptom: Following a system reload, the OC-3c and OC-12c port adapters come up without a problem. If a new module is inserted after the reload the module is recognized, but none of the ports send out any information. The input cell increments, but the output cell count does not increment.
Symptom: The Digital Crossconnect Unit (DCU) on the T1/E1 CES port adapter might malfunction unexpectedly.
Symptom: The ILMI keepalive feature resets the interface on the second retry following a link failure. This behavior might occur despite having configured the system to allow up to five retries.
Symptom: Despite having enough bandwidth, Resource Management might reject some soft PVCs.
Symptom: Under certain circumstances, the might display inaccurate traffic statistics on NNI or UNI interfaces.

Cisco IOS Release 12.0(4a)W5(11a) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8510 MSR for Cisco IOS Release 12.0(4a)W5(11a).

Symptom: Remote defect identification (RDI) cells sent by an end point in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.
Workaround: None.
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order to validate clients.
If different emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (via portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
Symptom: Cell loss might occur while hot swapping a power supply.
Workaround: None.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
Symptom: In a Catalyst 8510 MSR equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
Symptom: If there are multiple parallel paths to the same destination on a Catalyst 8510 MSR with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of 4 parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
Symptom: While setting up a large number of calls, the system generates the following error message:
%SYS-3-CPUHOG: Task ran for 5852 msec (0/0), process = Exec, PC = 6008DBB4
Workaround: None.
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch that had the closed physical interface.
Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. I t might be better to do any dropping prior to multiplexing onto the VP, so that a packet discard can be performed. Packet discard cannot be performed on the VP trunk.
Workaround: None.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: ILMI does not come up upon reload of VP-MUX (VUNI)
ILMI on the tunnel interface, which is connected to the far end peer device through a VP-MUX switch and virtual UNI, is occasionally unable to come up and stay in state of "WaitDevType" right after reloading the VP-MUX switch. This situation can be cleared by shutting down the tunnel interface, disabling ILMI followed by a no shutdown command on the tunnel interface. After the interface settles down, ILMI on the tunnel can then be reenabled by shutting down the interface, entering the atm ilmi-enable command and also the atm auto-configuration command, if desired. Reenable the tunnel interface with a no shutdown command.
Workaround: None.
Symptom: Non-zero generic flow control (GFC) field is not reset to zero when passing through the Catalyst 8510 MSR.
When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).
Workaround: None.
Symptom: When loading a software version 11.3 or later image on a switch with a software version 11.2 or earlier image, LEC and other LANE components might fail to come up if they are configured using an ATM address whose first 19 bytes are the same as the active ATM address of the switch.
The ATM address of the switch along with the first 128 values for its selector byte should be reserved for use by PNNI. Starting with the 11.3 software version, PNNI supports hierarchy and registers an ATM address for all PNNI nodes using the switch ATM address with various selector byte values.
Workaround: If LANE components fail to come up because their ATM addresses conflict with the reserved ATM addresses for PNNI, reconfigure the LANE components using different addresses. It is recommended that LANE applications use the addresses shown by the show lane default-atm-addresses command, which eliminates this problem.
Symptom: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation
While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: On a configured with 32 MB RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.
This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a system configured with 64 MB RAM.
Workaround: None.
Symptom: Spurious memory access on show ip route when SONICT interface is shut down.
If you shut down a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():
Workaround: None.
Symptom: The following message appears on the neighboring ATM switch after using the reload command:
%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background
Workaround: None.
Symptom: Power-on diagnostics displays an NVRAM-Config failure following the second power cycle after you use the write erase command if the write memory command has not been used between power cycles.
This failure occurs only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.
Workaround: After using the write erase command, use the write memory command before power cycling the switch.
Symptom: The Frame Relay port adapter firmware might report CRC errors on a PVC if it receives traffic using the same VPI/VCI/DLCI as the PVC being configured. The errors only occur while the firmware is still configuring the VC. Once the PVC has been configured, the CRC errors are discontinued. Since the frames appear like zero-length AAL5 packets while the firmware is still configuring the VC, the firmware does not increment discard bytes, but only increments discard frames due to the CRC error counter.
Workaround: Do not allow traffic to pass on the VC while it is being configured on the port adapter.
Symptom: The CES ABCD bits are not user configurable when a fault occurs.
Workaround: None.
Symptom: The does not support a PVP tunnel with a VPI value of 0. The IOS relates subinterface 0 to the main interface so interface atm x/y/z.0 represents the main interface x/y/z. If the user attempts to create a PVP tunnel with a VPI value of 0, the system should return an error on interface atm x/y/z.0.
Workaround: None.
Symptom: Under certain conditions, the ATM link on an IMA port adapter might come up with different linecodes at both ends.
Workaround: Use the show controller command to list line code violations occurring on the line. Then use the shutdown command on the interface to clear the counter. Use the no shutdown command to reenable the interface.
Symptom: Under certain conditions, the ATM link on an IMA port adapter might come up with a different framing mode.
Workaround: None.
Under certain conditions, the line code violation (LCV) counter on an IMA port adapter might not be updated.
Workaround: None.
Symptom: A T1 CES interface does not send out a remote alarm indication (RAI) in the reverse direction upon detecting an alarm indication signal (AIS).
Workaround: None.
Symptom: Under certain conditions, the ATM link on an IMA port adapter might come up when the other end has been shut down.
Workaround: None.
Symptom: The show ncdp path root command might not display any information when you access the switch through the Ethernet port.
Workaround: Access the switch using the console port.
Symptom: The debug ncdp packets, debug ncdp errors, and debug ncdp events commands do not display any information when you access the switch through the Ethernet port.
Workaround: Access the switch using the console port.
Symptom: The loopback configured on an ATM interface is retained even after that interface becomes a member of an IMA group.
Workaround: Issue a no ima command on the interface, followed by a no shutdown command to bring up the ATM interface.The loopback can be disabled now. Issue a shutdown command on the ATM interface and configure the interface as a member of an IMA group.
Symptom: The FDL configuration on an IMA interface is not restored after an OIR of the port adapter.
Workaround: Reconfigure the FDL after an OIR.

Cisco IOS Release 12.0(1a)W5(9) Caveats Corrected

Symptom: SNMP SET to a CES port causes the switch to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.
Symptom: Catalyst 8510 MSR Ethernet does not receive CDP multicast packets. However, the switchCatalyst 8510 MSR does send out CDP multicast packets.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Symptom: The show atm vc interface vpi vci command displays incorrect transmit (TX) cell counter values on the VC-merged leg of the connection.
Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, running UNI 3.1, by way of a Catalyst 8510 MSR.
Symptom: ATM Accounting: Exception in validblock_diagnose because resources at destination switch were not available for soft-VC setup.
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck until a shutdown command followed by a no shutdown command sequence is issued on the interface.
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Symptom: The show controller atm card/subcard/port command displays the incorrect interface type after hot swapping the port adapter.
Symptom: Frame Relay soft PVCs are not released when the line protocol goes down.
When the Local Management Interface (LMI) configured on a Frame Relay interface brings down the line protocol of that interface, the soft PVCs originating from or terminating on that Frame Relay interface are not released.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM cards.
Symptom: Frame Relay soft VC configuration is not possible using SNMP.
You can not configure Frame Relay soft VCs using the casfVcEndptTable in SNMP.
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
Symptom: A Catalyst 8510 MSR with 8 LAN emulation clients configured on the CPU and 300 point-to-point and 60 point-to-multipoint connections crashes unexpectedly at the find-buddy function, due to an infinite loop.
Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, UBR-rt.
A Catalyst 8510 MSR that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces.
An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
Symptom: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Symptom: When running tag switching, no tag is created for the default route.
Symptom: Some ports on an ATM25 port adapter might on occasion go into an alarm state.
Under certain conditions the ATM25 port adapter might go into an alarm state as indicated by the red LED on the port adapter.
Symptom: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Symptom: In release 11.3 on the ATM25 port adapter, you cannot exceed the number of leaves in a p2mp connection beyond 32.
Symptom: The atm soft-vc command does not disable OAM intercept.
When the ordering of OAM cells must be preserved in the cell-flow, OAM intercept must be disabled. The atm soft-vc command to disable this does not work for soft PVCs.
Symptom: Catalyst 8510 MSR uses backward parameters in QoS IE for PtMP calls.
This might cause incompatibility with other vendors' implementations.
Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Symptom: The granularity of the switch rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.
Symptom: Under certain circumstances, the lane server-bus ethernet command might cause the following exception:
Unexpected exception, CPU signal 10, PC = 0x605CB430
Symptom: The switch rejects calls with extended QoS parameters.
When ATM QoS for cdv is configured and you specify a soft VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft VC does not come up .
Symptom: Incorrect coding of the information element "call state".
Information element "call state" incorrectly sets the coding standard to 00 (ITU-T coding standard) instead of 11 as specified in the PNNI specification. This can cause compatibility problems with other vendors' implementations.

Cisco IOS Release 12.0(1a)W5(9) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8510 MSR for Cisco IOS Release 12.0(1a)W5(9).

Symptom: Remote defect identification (RDI) cells sent by an end point in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.
Workaround: None.
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX LED lights up.
Workaround: None.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order to validate clients.
If different emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: When disabling the Cisco Discovery Protocol (CDP) on an ATM interface that has been configured as a LEC, the CDP configuration is not saved to NVRAM.
Workaround: None.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (via portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
Symptom: Cell loss might occur while hot swapping a power supply.
Workaround: None.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
Symptom: In a Catalyst 8510 MSR equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
Symptom: If there are multiple parallel paths to the same destination on a Catalyst 8510 MSR with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of 4 parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
Symptom: While setting up a large number of calls, the system generates the following error message:
%SYS-3-CPUHOG: Task ran for 5852 msec (0/0), process = Exec, PC = 6008DBB4

Workaround: None.
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch that had the closed physical interface.
Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. I t might be better to do any dropping prior to multiplexing onto the VP, so that a packet discard can be performed. Packet discard cannot be performed on the VP trunk.
Workaround: None.
Symptom: After hotswapping an OC-3 LR port adapter with an OC-3 MM port adapter, the system might fail unexpectedly.
Workaround: None.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface will over-subscribe and, potentially, affect the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: ILMI does not come up upon reload of VP-MUX (VUNI)
ILMI on the tunnel interface, which is connected to the far end peer device through a VP-MUX switch and virtual UNI, is occasionally unable to come up and stay in state of "WaitDevType" right after reloading the VP-MUX switch. This situation can be cleared by shutting down the tunnel interface, disabling ILMI followed by a no shutdown command on the tunnel interface. After the interface settles down, ILMI on the tunnel can then be reenabled by shutting down the interface, entering the atm ilmi-enable command and also the atm auto-configuration command, if desired. Reenable the tunnel interface with a no shutdown command.
Workaround: None.
Symptom: Non-zero generic flow control (GFC) field is not reset to zero when passing through the Catalyst 8510 MSR.
When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).
Workaround: None.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port, the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
Symptom: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation
While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: On a configured with 32 MB RAM, IPC traffic between the port adapter driver and the firmware can experience a transient failure when the port adapter firmware crashes under heavy traffic conditions. The port adapter recovers from this transient failure if it is reset after waiting for about 2 minutes.
This IPC failure, which is due to an unexpected firmware crash under a heavy load, does not occur on a system configured with 64 MB RAM.
Workaround: None.
Symptom: Spurious memory access on show ip route when SONICT interface is shut down.
If you shut down a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():
Workaround: None.
Symptom: The following message appears on the neighboring ATM switch after using the reload command:
%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background
Workaround: None.
Symptom: Power-on diagnostics displays an NVRAM-Config failure following the second power cycle after you use the write erase command if the write memory command has not been used between power cycles.
This failure occurs only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.
Workaround: After using the write erase command, use the write memory command before power cycling the switch.
Symptom: On a running release 11.3(3a)WA4(6), if an atm ping command is issued after a VC is removed via a link failure, a bus error might cause the system to fail unexpectedly.
Workaround: Reload the system via power reset.
Symptom: Soft VP and PVP cannot coexist due to VPI allocation errors.
Workaround: None.
Symptom: TR-LEC currently processes all registration requests received on its control distribute VC. It should only be doing this if the LEC id in the registration message matches up with its own LEC id.
Workaround: None.
Symptom: The does not accept PVCs terminating on its CPU port over point-to-point subinterfaces.
Workaround: None.
Symptom: CES (CBR) might show the interface as up while in loss of signal (LOS). Also, it does not send AIS while the interface is shut down or the uplink ATM was broken (when configured as structured mode).
Workaround: None.
Symptom: 1CT3 and 4CE1 do not support DS1 MIB (RFC 1406). Also 1CT3 does not support DS3 MIB (RFC 1407).
Workaround: None.
Symptom: The advertised priority is not updated for PGL if configured to match the advertised priority.
Workaround: None.
Symptom: When issuing a show running-config command the might fail unexpectedly, due to a bus error.
Workaround: None.
Symptom: The soft pvc count might not be included in atmfAtmLayerConfiguredVCCs.
Workaround: None.
Symptom: Configuring a channelized E1(CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the linecode violation and LES counters to increment continually.
Workaround: None.
Symptom: When forwarding a call setup from one VP tunnel to another, the might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.
Workaround: None.
Symptom: If a show debugging command is issued on a that is configured as a PNNI "childless uncle," an infinite loop condition might occur that will cause a watchdog timeout.
Workaround: None.
Symptom: When polling the sysObjectID of a Catalyst 8510 MSR, it returns 190, which is the sysObjectID of a Catalyst 8510 CSR. This situation causes a problem in Cisco Works for Switched Internetworks (CWSI), because the MSR has ATM interfaces. By mistaking an MSR for a CSR, ATMDirector will not work with the Catalyst 8510 MSR.
Workaround: None.
Symptom: On a PNNI signalling link, the Promina 4000 NET switch sends a message that prompts the system to send a CALL PROCEEDING message and then a RELEASE message with a cause code 8a ("VPCI/VCI unacceptable"). When the call goes out on a uni3.1 interface, this cause code should be mapped to VPI/VCI assignment failure. This mapping does not occur for PNNI links.
Workaround: None.
Symptom: For the 12.0(4a)W5(11a) release, the units for the atm soft vc command are not backwards-compatible with the 11.3(3a)WA4(6) release.
Workaround: None.
Symptom: The does not support a PVP tunnel with a VPI value of 0. The IOS relates subinterface 0 to the main interface so interface atm x/y/z.0 represents the main interface x/y/z. If the user attempts to create a PVP tunnel with a VPI value of 0, the system should return an error on interface atm x/y/z.0.
Workaround: None.
Symptom: Issuing the atm snoop interface command might cause the FC1 system to fail unexpectedly.
Workaround: None.
Symptom: After resetting an ATM interface, the soft VCs terminating on that interface might not come up for certain VPI/VCI values.
Workaround: None.
Symptom: Following a system reload, the OC-3c and OC-12c port adapters come up without a problem. If a new module is inserted after the reload the module is recognized, but none of the ports send out any information. The input cell increments, but the output cell count does not increment.
Workaround: None.
Symptom: The Digital Crossconnect Unit (DCU) on the T1/E1 CES port adapter might malfunction unexpectedly.
Workaround: None.
Symptom: The ILMI keepalive feature resets the interface on the second retry following a link failure. This behavior might occur despite having configured the system to allow up to five retries.
Workaround: None.
Symptom: Despite having enough bandwidth, Resource Management might reject some soft PVCs.
Workaround: None.
Symptom: Under certain circumstances, the might display inaccurate traffic statistics on NNI or UNI interfaces.
Workaround: None.

Cisco IOS Release 12.0(1a)W5(5b) Caveats

This section describes unsupported features and limitations, caveats, and some potentially unexpected behavior by the Catalyst 8510 MSR for Cisco IOS Release 12.0(1a)W5(5b).

Symptom: Remote defect identification (RDI) cells sent by an end point in response to alarm indication signal (AIS) cells generated at an intermediate switch with a fault condition on an interface are not propagated beyond the intermediate switch. The intermediate switch removes the connection leg entries for both interfaces participating in the connection when a fault is discovered on one of the interfaces, even though the other interface might still be up. As a result, the RDI cells are dropped at the intermediate switch.
Workaround: None.
Symptom: When more than 1000 SVCs are active on an interface and the shutdown command is entered, all SVCs on that interface are released and the following message appears:
%SYS-3-CPUHOG
This message indicates that the release process runs for a long time before returning control to the kernel, which can then schedule other tasks. This process does not affect normal operation of the switch.
Workaround: None.
Symptom: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.
Workaround: None.
Symptom: The receiver circuitry on DS3 port adapters can interpret noise as a valid signal. This signal is framed incorrectly and does not contain real data. The DS3 controller interprets the signal as a bad signal instead of no signal, and the red RX light emitting diode (LED) lights up.
Workaround: None.
Symptom: When a large number of LANE clients come up and down constantly over extended periods of time, the system can run out of AAL5 buffers and the following message appears:
%AAL5-3-INTERNAL_ERROR: No more big aal5 pkts
In most cases, the system continues to function normally, but occasionally the system denies additional calls from end systems.
Workaround: Toggle the interface to reinitialize all connections and restore normal operation.
Symptom: A LECS, using Cisco IOS Version 11.2(X), expects all LESs to establish an individual control VC to the LECS in order to validate clients.
If different Emulated Local Area Networks (ELANs), using Cisco IOS Release 11.1(X), are configured on multiple subinterfaces of the same physical interface, then all LESs multiplex the control messages (which validate the clients) into a single VC.
For example, see the following LES router configuration: 
atm1/0.1    sysa_70k_31_a1.1_LAN sysa_70k_31_a1.1_LAN
atm1/0.2    sysa_70k_31_a1.2_LAN sysa_70k_31_a1.2_LAN
atm1/0.3    sysa_70k_31_a1.3_LAN sysa_70k_31_a1.3_LAN
atm1/0.4    sysa_70k_31_a1.4_LAN sysa_70k_31_a1.4_LAN
This configuration of an LECS sends the following warning messages to the console stating that an LES of one ELAN is attempting to obtain information about another ELAN:
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.1_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.2_LAN'
%LANE-4-LECS_WARNING: interface ATM2/0/0: elan 'sysa_70k_31_a1.4_LAN' LES asking for elan 
'sysa_70k_31_a1.3_LAN'
The clients are still allowed to join the ELAN. Disregard the warning message.
Workaround: None.
Symptom: You can create variable bit rate (VBR), available bit rate (ABR), and unspecified bit rate (UBR) VCs across the switch with peak cell rate (PCR) values greater than the interface line rate. However, the actual allocated bandwidth continues to be:
Workaround: None.
Symptom: When one of the installed power supplies is powered OFF, and you are copying an image to bootflash, a power supply failure message appears.
Workaround: None.
Symptom: The call attempt counters for PortSelectGroups might not count the outgoing calls on its NNI interfaces because of switch crankback attempts. This might result in a discrepancy between the call attempt counters shown on Portselgroup representing the interface on which the call came in and the counters shown on the PortSelgroup representing the interface over which an attempt was made to forward the call. This problem might occur when a call fails.
Workaround: None.
Symptom: ATM RMON data collection is not supported on subinterfaces or tunnels. The atm rmon collect command is accepted on hardware interfaces only; it is ignored on subinterfaces. SNMP and NVGEN support (via portSelTable) is not possible until the Interfaces MIB (RFC 1573) entries are added for tunnel subinterfaces. ATM RMON counters for a hardware interface do not include any of the traffic through tunnels configured on the interface.
Workaround: None.
Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.
Workaround: None.
Symptom: Supporting ABR VP tunnels requires interaction between VP flow-control and VC marking that neither FC-PCQ nor FC-PFQ hardware can perform. The configuration of an ABR VP tunnel subinterface is prevented.
Workaround: None.
Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.
Workaround: None.
Symptom: Cell loss might occur while hot swapping a power supply.
Workaround: None.
Symptom: SNMP SET to a CES port causes the switch to hang.
If you attempt to do an SNMP SET on the ifAdminStatus of a virtual ATM port associated with a CES card, the switch stops working.
Workaround: None.
Symptom: When memory is almost or completely exhausted and a soft PVC goes down, it might not come back up, leaving it in a releasing or inactive state.
Workaround: None.
Symptom: Catalyst 8510 MSR Ethernet does not receive CDP multicast packets. However, the Catalyst 8510 MSR does send out CDP multicast packets.
Workaround: None.
Symptom: In a Catalyst 8510 MSR equipped with an FC-PFQ, the maximum number of cells available for use is 64511. The number of cells in the switch fabric is 65535.
Workaround: None.
Symptom: If there are multiple parallel paths to the same destination on a Catalyst 8510 MSR with a FC-PFQ feature card installed, the tag switching VCs (TVCs) should be load balanced on a per network prefix basis over these parallel paths (up to a maximum of 4 parallel paths) instead of being VC merged. Load balancing does not happen in some cases and the TVCs might be VC merge and go out of the switch as a single VC.
Workaround: None.
Symptom: The Catalyst 8510 MSR switch does not currently support maxvc-number negotiation through ILMI.
Workaround: None.
Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.
Workaround: Reboot the switch.
Symptom: IP host-routing does not disable when specified.
Workaround: Enable and disable ip routing and then save the configuration to NVRAM.
Symptom: While setting up a large number of calls, the system generates the following error message:
%SYS-3-CPUHOG: Task ran for 5852 msec (0/0), process = Exec, PC = 6008DBB4
Workaround: None.
Symptom: Open shortest path first (OSPF) does not recognize more than four parallel interfaces. This might cause some tag switching VCs (TVCs) to not get switched to other interfaces if a tunnel carrying the TVCs is shut down.
Workaround: Enter a clear ip route command on the switch on the interface that was shut, or a clear ip route command on all the switches to bring everything back up. If the clear ip route command does not bring everything back up, enter a shutdown/no shutdown command sequence on the UNI interfaces of the switch that had the closed physical interface.
Symptom: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.
Workaround: None.
Symptom: The granularity provided by the FC-PFQ feature card scheduling hardware does not allow an exact match of all requested cell rates. To satisfy the traffic contract guarantee, the next higher available scheduling value is used. A shaped VP tunnel is used frequently to pass data to a WAN VP trunk, and limits the traffic transmitted to the scheduled rate. This can cause cells to be dropped in the WAN. I t might be better to do any dropping prior to multiplexing onto the VP, so that a packet discard can be performed. Packet discard cannot be performed on the VP trunk.
Workaround: None.
Symptom: When you set the ROM monitor environment variable boot to a nonexistent file (using the Cisco IOS command boot system flash) and the configuration register is set to 0x2102 (autoboot), the switch hangs during the subsequent reload command issued by the software.
Workaround: Power-cycle the switch; a break character is sent to the switch to force it to the ROM monitor prompt. You can then manually reboot the switch.
Symptom: The show atm vc interface vpi vci command displays incorrect transmit (TX) cell counter values on the VC-merged leg of the connection.
Workaround: None.
Symptom: Funnel VCs can jeopardize quality of service (QoS) for services.
The current multipoint-to-point funnel implementation can compromise the QoS guarantees of other connections (guaranteed services) when the application that created the funnel SVC malfunctions. For example, if the application were to transmit traffic on more than one leg of the funnel SVC simultaneously, the rate scheduler on the output interface over-subscribes and, potentially, affects the peak cell rate (PCR), sustained cell rate (SCR), and maximum cell rate (MCR) guarantees for other VCs on the interface.
Workaround: None.
Symptom: ILMI does not come up upon reload of VP-MUX (VUNI)
ILMI on the tunnel interface, which is connected to the far end peer device through a VP-MUX switch and virtual UNI, is occasionally unable to come up and stay in state of "WaitDevType" right after reloading the VP-MUX switch. This situation can be cleared by shutting down the tunnel interface, disabling ILMI followed by a no shutdown command on the tunnel interface. After the interface settles down, ILMI on the tunnel can then be reenabled by shutting down the interface, entering the atm ilmi-enable command and also the atm auto-configuration command, if desired. Reenable the tunnel interface with a no shutdown command.
Workaround: None.
Symptom: Another vendor's router, when running UNI 4.0, cannot connect a VC to a Cisco router, running UNI 3.1, by way of a Catalyst 8510 MSR.
Workaround: None.
Symptom: ATM Accounting: Exception in validblock_diagnose because resources at destination switch were not available for soft-VC setup.
Workaround: None.
Symptom: When a large amount of data is sent out of the Ethernet interface, the interface can become overwhelmed and start generating the error message:
%SONICT-3-INTERNAL_ERROR: sonic_send: no free tbufs
The interface stops sending data and the transmitter remains stuck until a shutdown command followed by a no shutdown command sequence is issued on the interface.
Workaround: None.
Symptom: Non-zero generic flow control (GFC) field is not reset to zero when passing through the Catalyst 8510 MSR.
When cells with a non-zero GFC field are received on a PVC, they are switched on the exit port without changing the GFC field. The switch should reset to zero all GFC bits from cells received with non-zero GFC at the user network interface (UNI).
Workaround: None.
Symptom: The following error message appears when using the show atm interface resource atm card/subcard/port.subport command:
Tunnel:%ATMCORE-3-INTERNAL_ERROR: show_atm_int_rm: Cannot find phylo
This error message appears because the tunnel specified in the CLI has been deleted and the software has released all the structures pertaining to that tunnel.
Workaround: None.
Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo
When snoop-VC is configured on a port the switch returns these internal error messages.
%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr
Workaround: These messages can be ignored; they do not affect the snooping functionality.
Symptom: ADD Party over Tunnel does not work.
On a source node, if you are adding a subsequent leaf to a VP tunnel that is out of bandwidth, PNNI might reject the route request (for the leaf) leading to an eventual rejection of the ADD party by signaling.
Symptom: The show controller atm card/subcard/port command displays the incorrect interface type after hot swapping the port adapter.
Workaround: None.
Symptom: Tag switching and Tag Discovery Protocol (TDP) memory fragmentation
While running tag switching with a very large number of destinations, continuous toggling of VC Merge (which forces all the TDP sessions to restart) on the switch for a very extended period of time (for example, overnight) causes memory fragmentation in the TDP process.
Workaround: None.
Symptom: Frame Relay soft-VC is not released when line protocol goes down.
When the Local Management Interface (LMI) configured on a Frame Relay interface brings down the line protocol of that interface, the soft-PVCs originating from or terminating on that Frame Relay interface are not torn down.
Workaround: None.
Symptom: Spurious memory access on show ip route when SONICT interface is shutdown.
If you shutdown a 10-Mbps port and then use the show ip route command, spurious memory access appears in the print_route_preamble():
Workaround: None.
Symptom: The following message appears on the neighbor ATM switch after using the reload command:
%SYS-3-CPUHOG: Task ran for 3984 msec (24/11), process = Net Background
Workaround: None.
Symptom: The DS1 MIB objects do not work for T1/E1 ATM cards.
Workaround: None.
Symptom: Frame Relay soft-VC configuration is not possible using SNMP.
You can not configure Frame Relay soft-VCs using the casfVcEndptTable in SNMP.
Workaround: None.
Symptom: Disabling tag switching on an interface that carries tagged VCs (TVCs) does not remove the TVCs. Reenabling tag switching on that interface will put it in the "not TDP ready" state.
Workaround: None.
Symptom: A Catalyst 8510 MSR with 8 LAN emulation clients configured on the CPU and 300 point-to-point and 60 point-to-multipoint connections crashes unexpectedly at the find-buddy function, due to an infinite loop.
Workaround: None.
Symptom: Power-on diagnostics will display an NVRAM-Config failure following the second power-cycle after you use the write erase command if the write memory command has not be used between power-cycles.
This failure will occur only if you use the write erase command and the power-on diagnostics runs twice without the write memory command being used.
Workaround: After using the write erase command, use the write memory command before power cycling the switch.
Symptom: Connections where end-to-end delay IE is included in the connect message might fail. Examples of these connections include UNI40, CBR, UBR-rt.
A Catalyst 8510 MSR that is an intermediate switch passes a bad CONNECT message from one side to another. The CONNECT message shows up as a CONNECT packet that is longer than the actual contents, with junk bytes at the end.
Workaround: None.
Symptom: The PNNI SNMP agent is not able to discover and allow PNNI-related configurations on ATM subinterfaces.
An alignment error message is printed when an SNMP walk (or other SNMP get next) request is issued.
Workaround: None.
Symptom: PNNI does not clean up and release some of its data structures properly, following process termination. A PNNI process is terminated when the associated node is either disabled or removed. As a result of not freeing the data structures, the associated memory is lost until the next reload.
Workaround: None.
Symptom: Soft VP and PVP cannot coexist due to VPI allocation errors.
Workaround: None.
Symptom: When running tag switching, no tag is created for the default route.
Workaround: None.
Symptom: TR-LEC currently processes all registration requests received on its control distribute VC. It should only be doing this if the LEC id in the registration message matches up with its own LEC id.
Workaround: None.
Symptom: Some ports on an ATM25 port adapter might on occasion go into an alarm state.
Under certain conditions the ATM25 port adapter might go into an alarm state as indicated by the red LED on the port adapter.
Workaround: None.
Symptom: A software crash might occur on the switch running software release 11.2(15)WA3(6). The crash is related to PNNI; the crashing function is pnni_link_av.
Workaround: None.
Symptom: A crash might occur while removing subinterfaces using the no interface command.
Workaround: None.
Symptom: AAL5 CRC errors are not accounted for at the physical interface.
The show atm interface command does not display CRC errors seen at the physical interface level. These errors are not logged under AAL5 CRC.
Workaround: None.
Symptom: In release 11.3 on the Ibis port adapter, you cannot exceed the number of leaves in a p2mp connection beyond 32.
Workaround: None
Symptom: CES (CBR) might show the interface as up while in loss of signal (LOS). Also, it does not send AIS while the interface is shut down or the uplink ATM was broken (when configured as structured mode).
Workaround: None.
Symptom: The atm soft-vc command does not disable OAM intercept.
When the ordering of OAM cells must be preserved in the cell-flow, OAM intercept must be disabled. The atm soft-vc command to disable this does not work for soft PVCs.
Workaround: None.
Symptom: Catalyst 8510 MSR uses backward parameters in QoS IE for PtMP calls.
This might cause incompatibility with other vendors' implementations.
Workaround: None.
Symptom: When a call setup traverses a switch running PNNI on the ingress side and IISP (versions 3.0 or 3.1) on the egress side, the message might be corrupted.
Workaround: None.
Symptom: The granularity of the switch rate scheduler is such that rates are rounded down (when converting from bits per second to cells per second) when in fact they should be rounded up.
Workaround: None.
Symptom: Under certain circumstances, the lane server-bus ethernet command might cause the following exception:
Unexpected exception, CPU signal 10, PC = 0x605CB430
Workaround: None.
Symptom: The switch rejects calls with extended QoS parameters.
When ATM QoS for cdv is configured and you specify a soft VC (whether CBR or VBR-RT) from a UNI port which has negotiated a UNI 4.0 connection, this soft VC does not come up.
Workaround: None.
Symptom: The advertised priority is not updated for PGL if configured to match the advertised priority.
Workaround: None.
Symptom: Incorrect coding of the information element "call state".
Information element "call state" incorrectly sets the coding standard to 00 (ITU-T coding standard) instead of 11 as specified in the PNNI specification. This can cause compatibility problems with other vendors' implementations.
Workaround: None.

Documentation Updates

An Update to the ATM Switch Router Command Reference publication was created to reflect information added after printing the manual.

Related Documentation

The following sections describe the documentation available for the Catalyst 8510 MSR. Typically, these documents consist of hardware installation guides, software installation guides, Cisco IOS configuration and command references, system error messages, and feature modules, which are updates to the Cisco IOS documentation. Documentation is available as printed manuals or electronic documents, except for feature modules, which are available online only.

The most up-to-date documentation can be found on the Web via Cisco Connection Online (CCO) and the Documentation CD-ROM. These electronic documents might contain updates and modifications made after the hard-copy documents were printed.

These release notes should be used in conjunction with the documents listed in these sections.

Platform Documents

Following is a list of the platform-specific documentation available for the Catalyst 8510 MSR:

Software Documents

Following is a list of the software documentation available for the Catalyst 8510 MSR:

Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your product.

Note If you purchased your product from a reseller, you can access CCO as a guest. CCO is Cisco Systems' primary real-time support channel. Your reseller offers programs that include direct access to CCO services.

For service and support for a product purchased directly from Cisco, use CCO.

Software Configuration Tips on the Cisco TAC Home Page

For helpful tips on configuring Cisco products, follow this path on CCO:

Service & Support: Technical Documents (button on left margin)

"Hot Tips" are popular tips and hints gathered from Cisco's Technical Assistance Center (TAC). Most of these documents are also available from the TAC's Fax-on-Demand service. To access Fax-on-Demand and receive documents at your fax machine, call 888-50-CISCO (888-502-4726). From international areas, call 650-556-8409.

The following sections are provided from the Technical Documents Web page:

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.





hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Aug 22 14:14:41 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.