Worldwide [change] |Account |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Catalyst 8500 Series Campus Switch Routers

Release Notes for the Catalyst 8510 and LightStream 1010 ATM Switch for Cisco IOS Release 12.1(5)EY1

Downloads

Table of Contents

Release Notes for the Catalyst 8510 and the
LightStream 1010 ATM Switch for
Cisco IOS Release 212.1(5)EY2

Contents
 Introduction
 System Requirements
 New and Changed Information
 Caveats
 Caveat Symptoms and Workarounds
 Interoperability
 Y2K Compliance
 Related Documentation
 Documentation CD-ROM
 Obtaining Documentation
 Obtaining Technical Assistance

Release Notes for the Catalyst 8510 and the
LightStream 1010 ATM Switch for
Cisco IOS Release 212.1(5)EY2

February 14, 2002

Catalyst 8510 and LightStream 1010 ATM Switch Cisco IOS Release 12.1(5)EY2

Text Part Number: 78-12262-01 Rev. B0

This document describes the features and caveats for Cisco IOS Release 12.1(5)EY2 software for the Catalyst 8510 and the LightStream 1010 ATM switch.

Note   All information pertains to both the Catalyst 8510 and LightStream 1010 ATM switch platforms, unless differences between the platforms are noted in the text.

Contents

This document includes the following sections:

Introduction

The Catalyst 8510 and LightStream 1010 ATM switch provide 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 Releases 12.1 and 12.0, and includes the following sections:

Memory Requirements

The DRAM memory configuration is 64-MB DRAM (MEM-ASP64M), which is the default for both the Catalyst 8510 and LightStream 1010 ATM switch platforms.

Hardware Supported

Table 1 lists the interfaces supported by both the Catalyst 8510 and the LightStream 1010 ATM switch and Cisco IOS Release 12.1(5)EY2 software and their minimum software release requirements. All platform specific requirements are noted in the table.


Table 1: Supported Hardware Modules and their Minimum Software Requirements
Part Number Description Minimum Software Version Required

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

C8510-SPR

Layer 3 Switch Route Processor

W5-6f

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 IMA4

Catalyst 8510
S851R2-12.0.4W

LightStream 1010
SL10R2-12.0.4W

C85MS-8E1-IMA-120

8-port E1 port adapter with IMA

Catalyst 8510
S851R2-12.0.4W

LightStream 1010
SL10R2-12.0.4W

C8510-ARM-64K

ATM router module

S851R2-12.0.10W5

C8510-ACL=

ACL6 daughter card

S851R2-12.0.10W5

C85GE-8X-64K=

8-port Gigabit Ethernet 64K

S851R2-12.0.10W5

C85GE-1X-16K=

1-port Gigabit Ethernet 16K

S851R2-12.0.10W5

C85GE-1X-64K=

1-port Gigabit Ethernet 64K

S851R2-12.0.10W5

C85FE-8T-16K=

8-port 10/100 Fast Ethernet with RJ-45 16K

S851R2-12.0.10W5

C85FE-8T-64K=

8-port 10/100 Fast Ethernet with RJ-45 64K

S851R2-12.0.10W5

C85FE-8F-16K=

8-port 10/100 Fast Ethernet with MT-RJ 16K

S851R2-12.0.10W5

C85FE-8F-64K=

8-port 10/100 Fast Ethernet with MT-RJ 64K

S851R2-12.0.10W5
1ASP = ATM switch processor.
2FC-PCQ = feature card per-class queuing.
3FC-PFQ = feature card per-flow queuing.
4IMA = inverse multiplexing over ATM.
5The LightStream 1010 ATM switch requires the ASP-C with FC-PFQ to support the ATM router module.
6ACL = access control list.


Determining Your Software Release

To determine the version of Cisco IOS software currently running on either the Catalyst 8510 or the LightStream 1010 ATM switch, log into the switch and enter 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.1(5)EY2

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 and LightStream 1010 ATM switch 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:

ht tp://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 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 and the LightStream 1010 ATM switch in Cisco IOS Release 12.1(5)EY2 software.


Table 2: Feature Sets Supported by the Catalyst 8510 and the LightStream 1010 ATM Switch
Feature Set 12.1(5)EY1 12.0(13)W5(19) 12.0(10)W5(18b) 12.0(7)W5(15c) 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

x

x

x

x

SNMP1

x

x

x

x

x

x

x

x

Asynchronous support

x

x

x

x

x

x

x

x

PPP2 (SLIP3/PPP)

x

x

x

x

x

x

x

x

IP4

x

x

x

x

x

x

x

x

NTP5

x

x

x

x

x

x

x

x

TACACS+6

x

x

x

x

x

x

x

x

Telnet

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

Multipoint-to-point
UNI signaling

x

x

x

x

x

x

x

x

Soft VCCs and VPCs

x

x

x

x

x

x

x

x

VP tunneling

x

x

x

x

x

x

x

x

VPI/VCI range support
in ILMI 4.0

x

x

x

x

x

x

x

x

PNNI hierarchy

x

x

x

x

x

x

x

x

ILMI version 4.0

x

x

x

x

x

x

x

x

IISP9

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

Token Ring LANE services

x

x

x

x

x

x

x

x

ATM ARP16 server on ASP

x

x

x

x

x

x

x

x

ATM ARP client on ASP

x

x

x

x

x

x

x

x

ATM tag switch router (TSR)

x

x

x

x

x

x

x

x

Port snooping

x

x

x

x

x

x

x

x

OAM17 F4 and F5

x

x

x

x

x

x

x

x

E.164 address translation

x

x

x

x

x

x

x

x

E.164 autoconversion

x

x

x

x

x

x

x

x

Circuit emulation

x

x

x

x

x

x

x

x

ATM access lists

x

x

x

x

x

x

x

x

ATM accounting

x

x

x

x

x

x

x

x

ATM RMON18

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

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

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

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

x

x

x

x

x

x

x

x

Access lists on ILMI registration

x

x

x

x

x

x

x

x

CUGs

x

x

x

x

x

x

x

x

ATM soft restart

x

x

x

x

x

x

x

x

ATM accounting enhancements

x

x

x

x

x

x

x

x

CISCO-SYSLOG-MIB support

x

x

x

x

x

x

x

x

CISCO-CONFIG-COPY-
MIB support

x

x

x

x

x

x

x

x

Signaling diagnostics and MIB

x

x

x

x

x

x

x

x

Supplemental AToM MIB

x

x

x

x

x

x

x

x

E1 Frame Relay Port Adapter

x

x

x

x

x

x

x

 

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

x

x

x

x

x

x

x

 

Hierarchical VP Tunnels

x

x

x

x

x

x

x

 

Remote logging for accounting

x

x

x

x

x

x

x

 

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

x

x

x

x

x

x

x

 

PNNI Complex Node Representation

x

x

x

x

x

x

x

 

Support for ATM-Fabric Integration Module in Catalyst 5500

x

x

x

x

x

x

x

 

PNNI explicit paths

x

x

x

x

x

x

 

 

PNNI alternate link selection

x

x

x

x

x

x

 

 

Tag switching CoS

x

x

x

x

x

x

 

 

Network Clock Distribution Protocol

x

x

x

x

x

x

 

 

Simple Gateway Control Protocol

x

x

x

x

x

x

 

 

Inverse Multiplexing over ATM (IMA) groups

x

x

x

x

x

 

 

 

ATM End System Address (AESA) gateway

x

x

x

x

x

 

 

 

ATM overbooking

x

x

x

x

x

 

 

 

Framing overhead

x

x

x

x

x

 

 

 

NCDP MIB Support

x

x

x

x

 

 

 

 

L3-ATM routing and bridging via RFC 1483 (ATM router module)20

x

x

x

 

 

 

 

 

ACL support via ACL daughter card

x

x

x

 

 

 

 

 

Point-to-point subinterfaces. Only point-to-multipoint subinterfaces are supported.

x

 

 

 

 

 

 

 

Port aggregation protocol on EtherChannels

x

 

 

 

 

 

 

 

Power-on-diags

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 Plus.
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.
20You can download the Catalyst 8510 software image on a LightStream 1010 ATM switch to support L3-ATM (via ATM router module). However, the LightStream 1010 ATM switch software image does not include support for the ATM router module.


Release Names, Versions, and Part Numbers

Table 3 lists the release names, versions, and part numbers used with the Catalyst 8510 and LightStream 1010 ATM switch. Platform specific information is noted in the table.


Table 3: Release Name to Version and Part Number Matrix
Release Name Release Version Part Number for 8510 MSR and LightStream 1010 Part Number for 8510 CSR

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-6f

12.0(1a)W5(6f)

—

SRF-8510CSR2-0

W5-9

12.0(3c)W5(9)

SF-WAS5-9

—

W5-11a

12.0(4a)W5(11a)

Catalyst 8510:
S851R2-12.0.4W

LightStream 1010:
SL10R2-12.0.4W

S851R3-12.0.4W

W5-13

12.0(5)W5(13)

—

S851R3-12.0.5W

W5-13b

12.0(5)W5(13b)

—

S851R3-12.0.5MT

W5-13d

12.0(5)W5(13d)

—

S851R3-12.0.5MT

W5-15

12.0(7)W5(15c)

Catalyst 8510:
S851R2-12.0.7W

LightStream 1010:
SL10R2-12.0.7W

—

W5-18

12.0(10)W5(18b)

Catalyst 8510:
S851R2-12.0.10W

LightStream 1010:
SL10R2-12.0.10W

—

W5-18b

12.0(10)W5(18b)

—

S851R3-12.0.10W

W5-19

12.0(13)W5(19)

Catalyst 8510:
S851R2-12.0.13W

LightStream 1010:
SL10R2-12.0.13W

S851R3-12.0.13W

W5-19a

12.0(13)W5(19a)

Catalyst 8510:
S851R2-12.0.13W

LightStream 1010:
SL10R2-12.0.13W

S851R3-12.0.13W

W5-19b

12.0(13)W5(19b)

Catalyst 8510:
S851R2-12.0.13W

LightStream 1010:
SL10R2-12.0.13W

S851R3-12.0.13W

X-5

12.1(5)EY1

Catalyst 8510:
S851R2-12.1.X.5W

LightStream 1010:
SL10R2-12.1.X.5W

S851R3-12.1.X.5W


New and Changed Information

This section includes new features that appear in this and previous releases of Cisco IOS Release 12.0W5 software. The new features are sorted by release number.

New Features in Cisco IOS Release 12.1(5)EY1

The following new features are available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.1(5)EY1.

  • Port aggregation protocol on EtherChannels

  • Power-on-diags

New Features in Cisco IOS Release 12.0(13)W5(19a)

No new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(13)W5(19a).

New Features in Cisco IOS Release 12.0(13)W5(19)

No new features are available for the Catalyst 8510 MSR and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(13)W5(19).

Cisco IOS Release 12.0(13)W5(19) was deferred for the Catalyst 8510 CSR. See caveat CSCds85282 for further information on the deferment.

New Features in Cisco IOS Release 12.0(10)W5(18b)

The following new features are available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(10)W5(18b):

New Features in Cisco IOS Release 12.0(7)W5(15c)

The following new feature is available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(7)W5(15c):

  • NCDP MIB Support

See the "Related Documentation" section for a list of documents that describe this feature.

New Features in Cisco IOS Release 12.0(5)W5(13d)

No new features are available for Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(5)W5(13d).

New Features in Cisco IOS Release 12.0(5)W5(13b)

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(5)W5(13b):

  • IPX cross encapsulation issue resolved

  • Select bugs from IOS mainline

New Features in Cisco IOS Release 12.0(5)W5(13)

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(5)W5(13):

  • BGPx4 routing protocol

  • IP multicast scalability

  • Bridging/IRB over 802.1Q

  • Support for 16 bridge groups with up to 32 interfaces within each bridge group

  • Support for the 1000BASE-ZX extended reach GBIC

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

The following new features are available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(4a)W5(11a):

  • Inverse Multiplexing over ATM (IMA) Port Adapters

  • ATM Overbooking

  • Framing Overhead

  • AESA Gateway

The following new features are available for the Catalyst 8510 CSR in Cisco IOS Release 12.0(4a)WX5(11a):

  • Support for Appletalk routing

  • SPF Neighbor Optimizations

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

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

The following new features are available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(1a)W5(9):

  • Network Clock Distribution Protocol (NCDP)

  • Simple Gateway Control Protocol (SGCP)

  • PNNI Alternate Link Selection

  • PNNI Explicit Paths

  • Channelized DS3 Frame Relay Port Adapter

  • Four-port 25-Mbps Port Adapter

  • Tag Switching CoS

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

New Features in Cisco IOS Release 12.0(1a)W5(6f)

No new features are available for the Catalyst 8510 and the LightStream 1010 ATM switch in Cisco IOS Release 12.0(1a)W5(6f).

Caveats

This section lists the caveats and corrected caveats for each release. Use Table 4 to determine the status of a particular caveat and its relevancy to your software release. In the table below, "C" indicates a fixed or closed caveat, and "O" indicates an open or unresolved caveat. Platform specific caveats are appropriately indicated.


Table 4: Caveats and Caveats Corrected Reference
DDTS # 12.1(5)EY1 12.0(13)W5(19a) 12.0(13)W5(19) 12.0(10)W5(18b) 12.0(7)W5(15c) 12.0(4a)W5(11a) 12.0(1a)W5(9) 12.0(1a)W5(5b)

CSCdw65903

C

CSCdt63152

O

 

 

 

 

 

 

 

CSCdt53814

C

 

 

 

 

 

 

 

CSCdt43218

C

 

 

 

 

 

 

 

CSCdt24278

C

 

 

 

 

 

 

 

CSCdt21568

O

 

 

 

 

 

 

 

CSCdt21513

O

 

 

 

 

 

 

 

CSCdt17850

O

 

 

 

 

 

 

 

CSCdt15169

O

 

 

 

 

 

 

 

CSCdt11569

O

 

 

 

 

 

 

 

CSCdt10494

O

 

 

 

 

 

 

 

CSCdt04810

O

 

 

 

 

 

 

 

CSCdt01582

C

 

 

 

 

 

 

 

CSCds85282

O

O

 

 

 

 

 

 

CSCds81263

C

 

 

 

 

 

 

 

CSCds78385

O

 

 

 

 

 

 

 

CSCds69507

C

 

 

 

 

 

 

 

CSCds57646

C

 

 

 

 

 

 

 

CSCds44008

O

O

O

 

 

 

 

 

CSCds27586

O

 

 

 

 

 

 

 

CSCdr86285

O

O

O

O

 

 

 

 

CSCdr86044

C

C

C

C

O

O

O

O

CSCdr79972

C

 

 

 

 

 

 

 

CSCdr76839

C

C

C

C

O

O

O

O

CSCdr70086

C

 

 

 

 

 

 

 

CSCdr68605

C

C

C

C

O

O

O

O

CSCdr68425

C

C

C

C

O

O

O

O

CSCdr62898

O

O

O

O

O

 

 

 

CSCdr61171

C

C

C

C

O

O

O

O

CSCdr51414

C

C

C

C

O

O

O

O

CSCdr50435

C

C

C

C

O

O

O

O

CSCdr49975

C

C

C

C

O

O

O

O

CSCdr48014

C

C

C

C

O

 

 

 

CSCdr44264

C

C

C

C

O

O

O

O

CSCdr43326

C

C

C

C

O

O

O

O

CSCdr36952

O

O

O

O

O

 

 

 

CSCdr36422

C

C

C

C

O

O

O

O

CSCdr35301

O

O

O

O

O

 

 

 

CSCdr32958

O

O

O

O

O

 

 

 

CSCdr30421

O

O

O

O

O

 

 

 

CSCdr28797

O

O

O

O

O

O

O

 

CSCdr26204

C

C

C

C

O

O

O

O

CSCdr25535

C

C

C

C

O

O

 

 

CSCdr20326

C

C

C

C

O

O

O

 

CSCdr07165

C

C

C

C

C

O

 

 

CSCdr02365

O

O

O

O

O

 

 

 

CSCdr01726

O

O

O

O

O

 

 

 

CSCdr00623

C

C

C

C

C

O

 

 

CSCdr00483

C

C

C

C

C

O

 

 

CSCdr00463

C

C

C

C

C

O

 

 

CSCdp97152

C

C

C

C

O

O

O

O

CSCdp94338

C

C

C

C

O

O

O

O

CSCdp85211

C

C

C

C

O

O

O

O

CSCdp80826

O

O

O

O

O

 

 

 

CSCdp79109

O

O

O

O

O

 

 

 

CSCdp75180

C

C

C

C

C

O

 

 

CSCdp72650

C

C

C

C

C

O

 

 

CSCdp66611

C

C

C

C

C

O

 

 

CSCdp63799

C

C

C

C

C

O

 

 

CSCdp57023

C

C

C

C

C

O

 

 

CSCdp53470

C

C

C

C

C

O

 

 

CSCdp51216

C

C

C

C

C

O

 

 

CSCdp50167

O

O

O

O

O

O

 

 

CSCdp49173

C

C

C

C

C

O

 

 

CSCdp43220

C

C

C

C

C

O

 

 

CSCdp43184

C

C

C

C

C

O

 

 

CSCdp29185

C

C

C

C

C

O

 

 

CSCdp20982

C

C

C

C

C

O

 

 

CSCdp20865

O

O

O

O

O

O

 

 

CSCdp20230

C

C

C

C

C

O

 

 

CSCdp16253

C

C

C

C

C

O

 

 

CSCdp15220 (LS1010 ATM Switch)

C

C

C

C

C

O

 

 

CSCdp04109

C

C

C

C

O

O

O

 

CSCdp03740

C

C

C

C

O

O

O

O

CSCdp02816

O

O

O

O

O

O

 

 

CSCdm94019

C

C

C

C

C

C

O

 

CSCdm92990

C

C

C

C

C

C

O

 

CSCdm91060

C

C

C

C

C

C

O

 

CSCdm89519

C

C

C

C

C

C

O

 

CSCdm80806

C

C

C

C

C

O

 

 

CSCdm80628

O

O

O

O

O

O

 

 

CSCdm80015

C

C

C

C

C

O

 

 

CSCdm77939

C

C

C

C

C

O

 

 

CSCdm77907

C

C

C

C

C

O

 

 

CSCdm58868

C

C

C

C

C

C

O

 

CSCdm56393

C

C

C

C

C

C

O

 

CSCdm52827

C

C

C

C

C

C

O

 

CSCdm48886

C

C

C

C

C

O

O

 

CSCdm46569

C

C

C

C

C

C

O

 

CSCdm44497

C

C

C

C

C

C

O

 

CSCdm43851 (Catalyst 8510)

C

C

C

C

C

C

O

 

CSCdm36800

O

O

O

O

O

O

 

 

CSCdm36790

C

C

C

C

C

C

O

 

CSCdm36745

C

C

C

C

C

C

O

 

CSCdm34634

C

C

C

C

C

C

O

 

CSCdm32506

C

C

C

C

C

C

O

 

CSCdm29650

C

C

C

C

C

C

C

O

CSCdm29503

C

C

C

C

C

C

O

O

CSCdm23579

C

C

C

C

C

C

C

O

CSCdm20257

C

C

C

C

C

C

C

O

CSCdm19670

C

C

C

C

C

C

O

 

CSCdm19073

C

C

C

C

C

C

C

O

CSCdm19018

C

C

C

C

C

C

C

O

CSCdm15900

C

C

C

C

C

C

C

O

CSCdm11577

C

C

C

C

C

C

C

O

CSCdm08234

C

C

C

C

C

C

O

O

CSCdm07874

C

C

C

C

C

C

C

O

CSCdm06168

C

C

C

C

C

C

O

 

CSCdm04013

C

C

C

C

C

C

C

O

CSCdk90147

C

C

C

C

C

C

C

O

CSCdk90091

C

C

C

C

C

C

C

O

CSCdk88859

C

C

C

C

C

O

 

 

CSCdk87959
(Catalyst 8510)

C

C

C

C

C

O

 

 

CSCdk84355

C

C

C

C

C

C

C

O

CSCdk84269

C

C

C

C

C

C

O

O

CSCdk82708

C

C

C

C

C

C

C

O

CSCdk79426

C

C

C

C

C

C

O

O

CSCdk78881

C

C

C

C

C

C

O

 

CSCdk78469

C

C

C

C

C

C

C

O

CSCdk77032

C

C

C

C

C

C

C

O

CSCdk76280

C

C

C

C

C

C

C

O

CSCdk73733

O

O

O

O

O

O

O

O

CSCdk73583

C

C

C

C

C

C

C

O

CSCdk69639

C

C

C

C

C

C

C

O

CSCdk63547

C

C

C

C

C

C

C

O

CSCdk62547

C

C

C

C

C

C

C

O

CSCdk57536

O

O

O

O

O

O

O

O

CSCdk56557

O

O

O

O

O

O

O

O

CSCdk52436

O

O

O

O

O

O

O

 

CSCdk49213

C

C

C

C

C

C

C

O

CSCdk47516

O

O

O

O

O

O

O

O

CSCdk42052

O

O

O

O

O

O

 

 

CSCdk41001

C

C

C

C

C

C

C

O

CSCdk33601

C

C

C

C

C

C

C

O

CSCdk27725

C

C

C

C

C

C

O

O

CSCdk26482

C

C

C

C

C

C

O

O

CSCdk25256

O

O

O

O

O

O

O

O

CSCdk22791

C

C

C

C

C

C

C

O

CSCdk22484

C

C

C

C

C

C

C

O

CSCdk17977

C

C

C

C

C

C

C

O

CSCdk10398

O

O

O

O

O

O

O

O

CSCdk07378

O

O

O

O

O

O

O

O

CSCdk03049

C

C

C

C

C

C

C

O

CSCdj85853

O

O

O

O

O

O

O

O

CSCdj84981

C

C

C

C

C

C

O

 

CSCdj84379

O

O

O

O

O

O

O

O

CSCdj84344

C

C

C

C

C

C

C

O

CSCdj82930

O

O

O

O

O

O

O

O

CSCdj80396

O

O

O

O

O

O

O

O

CSCdj78305

O

O

O

O

O

O

O

O

CSCdj71876

C

C

C

C

C

C

O

O

CSCdj71109

O

O

O

O

O

O

O

O

CSCdj68412

O

O

O

O

O

O

O

O

CSCdj54954

O

O

O

O

O

O

O

O

CSCdj47998

C

C

C

C

C

C

C

O

CSCdj42967

O

O

O

O

O

O

O

O

CSCdj31762

C

C

C

C

C

C

C

O

CSCdj25772

O

O

O

O

O

O

O

O

CSCdj18678

O

O

O

O

O

O

O

O

CSCdj18430

O

O

O

O

O

O

O

O

CSCdj13565

O

O

O

O

O

O

O

O

CSCdj11070

C

C

C

C

C

C

O

 

CSCdj10889

O

O

O

O

O

O

O

O

CSCdj01757

O

O

O

O

O

O

O

O

CSCdj01016

C

C

C

C

O

O

O

O

CSCdi92142

O

O

O

O

O

O

O

O

CSCdi83275

O

O

O

O

O

O

O

O

CSCdi82954

O

O

O

O

O

O

O

O

CSCdi75584

O

O

O

O

O

O

O

O

CSCdi74229

O

O

O

O

O

O

O

O

CSCdi55937

O

O

O

O

O

O

O

O


Caveat Symptoms and Workarounds

This section summarizes caveat symptoms and suggested workarounds for the Catalyst 8510 and the LightStream 1010 ATM switch. The maximum number of ELAN LES/BUS pairs that the ATM switch processor interface supports is 10. On configuring a Frame Relay NIW/SIW PVC, a small number of discarded frames are occasionally seen due to CRC errors. These discards happen even without passing traffic.

Symptom: An error can occur with management protocol processing.

Symptom: HSRP cannot be configured on Cisco IOS Release 12.1(5)EY1 image on the Catalyst 8510 MSR platform.

Workaround: None.

Symptom: An ATM router module port configured for transparent bridging and in blocking state may forward certain frames.

Workaround: Ensure that a non-ATM router module port is in blocking state. If this is not feasible, physically shutdown the ATM router module port that is in blocking state.

Symptom: The IP PAT tree becomes programmed incorrectly for 1483 SVC after removing the ARM card. If an SVC is configured on an ARM/ARM2 card and the card is OIRed, the adjacency available across the SVC will remain valid in the EPIF/XPIF cam. This results in packets destined to that adjacency to disappear.

Workaround: Before OIRing an ARM/ARM2 card, remove any sub-interfaces that have a SVC configurations, then proceed to do the OIR.

Symptom: The ARM sets the CLP of all cells to 1 when bridging is configured over a 1483 PVC. This happens for cells being transmitted over the 1483 PVC only.

Workaround: None.

Symptom: The ARM1 interface shut downs when entering the epc portstuck-manual-reload command with IP traffic. This only occurs when running the epc portstuck-manual-reload command several times.

Workaround: None.

Symptom: Spurious memory access at lss_arm_atm_adjacency_mac is observed after there is a CLI epc portstuck-manual-reload command entered on two ARM1 interfaces, while two Catalyst 8540 MSRs are connected. There are spurious memory access to both 8540m.

This has no functionality impact.

Workaround: None.

Symptom: The outbound ACL fails to filter packets in the subinterface when the static ARP is configured and the ACL is used with it. If a static ARP is configured and the same address is moved from an interface to a subinterface of the same interface, the static ARP entry remains associated with the main interface itself.

Workaround: When the IP address is reconfigured to a subinterface of a main interface, you then need to delete and reconfigure the ARP address.

Symptom: After configuring an ipx network between a Catalyst 8540 MSR and a Catalyst 8540 MSR, and a Catalyst 7500, old buffers detected messages being displayed on the Catalyst 8540 MSR. This occurs with an ATM interface and a Fast Ethernet interface. The Encap is 11 (Novell-Ether). This does not impact any functionality.

Workaround: None.

Symptom: Oversized packets on the ARM2 interface are observed when it is a member of a BVI. This console output relates to the oversized packets on the ARM2 interface. The following message is displayed:

    00:41:36: %TBRIDGE-4-GIANT: Giant received on ATM3/0/1, 1514 exceeds 1500
DA 0100.5e00.0005 SA 0001.4274.ee09 [0x080045C0]
The system recovers from this. The cause of this may be temporary congestion in the switch fabric, leading to the loss of the last cell of the packet.

Workaround: None.

Symptom: The ARM (8540-ARM-64K) indicates outgoing packets when on an interface that is in an admin down state.

This was observed on Cisco Internetwork Operating System Software IOS (tm) PNNI Software (cat8540m-WP-M), Version 12.0(10)W5(18c). This does not impact the functionality.

Workaround: None.

Symptom: While executing a series of shutdown/no shutdown commands on the ARM interface with a large number of CLIP clients (more than 32), the following error message appears on the console:

    00:58:16: %SYS-3-MGDTIMER: Uninitialized timer, timer stop, timer = 644B0550.
-Process= "ATM ARP INPUT", ipl= 0, pid= 30
-Traceback= 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50shut
 
Enter hex value: 600CE1BC 600CF2A4 60792B0C 60796850 60797744 600BBA64 600BBA50
0x600CE1BC:mgd_timer_complain_uninit(0x600ce190)+0x2c
0x600CF2A4:mgd_timer_stop(0x600cf26c)+0x38
0x60792B0C:atm_arp_stampvc(0x60792ad4)+0x38
0x60796850:atm_inarp_rcvdreq(0x6079620c)+0x644
0x60797744:atm_arp_process(0x60796f30)+0x814
0x600BBA64:r4k_process_dispatch(0x600bba50)+0x14
0x600BBA50:r4k_process_dispatch(0x600bba50)+0x0
This does not impact functionality. Enter the shutdown command, followed by the no shutdown command to recover.

Workaround: None.

Symptom: On Cisco IOS Release 12.0(10)W5(18b), when the module with c8510-ACL is in the Catalyst 5500 chassis, the show hardware command does not show the ACL daughter card.

Workaround: None.

Symptom: In the Cisco IOS release image ls1010-wp-mz.120-13.W5.19, the LS1010 power on diagnostic test causes the IOS not to boot while the ARM and Fast Ethernet modules are installed.

Workaround: Upgrade to Cisco IOS release image version ls1010-wp-mz.120-13.W5.19a.

Symptom: The IP CEF adjacencies are reported as invalid when using the ARM configured with LANE clients on the Catalyst 8540 MSR. The router reports an invalid cached adjacency for ip addresses that is not reachable through the LANE interface when running the show ip cef <ip address> command.

For example:

    show ip cef 207.18.18.0
 207.18.18.0/24, version 25, cached adjacency to ATM11/0/0.1
 0 packets, 0 bytes
   via 207.18.19.1, ATM11/0/0.1, 0 dependencies
     next hop 207.18.19.1, ATM11/0/0.1
     invalid cached adjacency
With an invalid cache adjacency, all the packets destined to this address will be sent to the route processor for processing.

The CEF adjacency will be invalid until a LANE data direct VC and valid LE-ARP entry are established on the adjacent device. As soon as the data direct VC and LE-ARP entry are established, the adjacency will be reported as valid.

Workaround: None.

Symptom: IPX traceroute is skipping the middle hop when the middle router is a Catalyst 8540 CSR/MSR; all IPX packets are cut-through switched and not given to the route processor.

Workaround: None.

Symptom: If the HSRP has been configured on a Catalyst 8500 running an Cisco IOS Release 12.0(10)W5(18c), and the ARM is removed and then reinserted, the HSRP configuration is lost.

Workaround: None.

Symptom: When a ping command is entered from one member of a BVI to the outside, it causes some pings between members of the BVI to timeout.

Workaround: None.

Symptom: Under certain conditions, the Catalyst 8510 does not have a certain MAC address in the CAM table. This leads to flooding of L2 traffic for a short time, until the MAC addresses are learned.

Workaround: Issue a clear br gr command.

Symptom: The sub-interfaces of an ARM (ARM1 or 2) may appear to receive the INARP packets even though the main interface is shut down. The upper layer finally discards the packet based on the state of the interface. There is no impact to any functionality.

Workaround: None.

Symptom: The output of the EXEC command show atm controllers atm 2/0/0 is incorrect. Interfaces with spurious card/subcard/port IDs are displayed, duplicating valid interface displays.

Workaround: None.

Symptom: Release message uses the wrong cause and diag information.

Workaround: None.

Symptom: The ARM always signals a fixed value for the PCR if LANE is configured on the ARM. The hidden CLI will give a way to signal the user-configured PCR. This will help with ATM traffic shaping/policing by the ATM nodes in between.

Workaround: None.

Symptom: Insufficient options for the show vc traffic and show vp traffic commands.

Workaround: None.

Symptom: The IP adjacencies are not being cleared from the gigabit ethernet card quickly. The sh epc ip-address command was issued on the adjacency, it was found that the entry for the host on vlan2 was still there and took some time to clear. As soon as it did clear, the ping command works again.

Workaround: None.

Symptom: The following message can appear when a peer devices transmits an incorrect signalling packet:

    SYS-2-BADSHARE: Bad refcount in datagram_done
This can lead to a memory corruption.

Workaround: None.

Symptom: Cannot create a soft VC with 95% of PVP.

Workaround: None.

Symptom: Per-VC drop counters are not consistent. This applies only to non-packet discard connections. The inconsistencies are between the three per-VC statistics: total RX cell drops, RX UPC violations, and RX clp0 q full drops. The total of RX UPC violations and RX Clp0 q full drops exceeds the total RX cell drops count. However, the total RX cell drops is accurate.

Workaround: None.

Symptom: A timeout system crash can occur when a shutdown/no shutdown command sequence is issued on an interface with several bridge groups configured. The following console message appears:

    %SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = PIM Process.
Workaround: None.

Symptom: In a switch equipped with circuit emulation service port adapters, the shutdown of the CBR interface does not affect the device connected to it.

Workaround: None.

Symptom: IP PIM Sparse-Mode using multipoint signaling over ATM might fail when the PNNI path is switched to the redundant link.

Workaround: Use regular point-to-point SVC connections instead of multipoint signaling, or use IP PIM Dense Mode.

Symptom: Cannot set ifAdminStatus object on CES interfaces.

Workaround: None.

Symptom: Open Shortest Path First (OSPF) updates might be corrupted on a Cisco 7500 series router using Multiprotocol Label Switching (MPLS) with Cisco Express Forwarding (CEF) output features enabled (including "service policy output"). IP routes are temporarily deleted from the IP routing table and a loss of connectivity might occur.

Workaround: Configure the ip cef global configuration command, save the configuration by using the copy running-config start-config command, and reload the switch. An alternative workaround would be to enter the memory cache-policy io uncached command. However, entering this command might affect packet switching performance.

Symptom: The switch crashed after a shutdown/no shutdown command sequence on interface ATM 0 when 230 SVCs were configured on the route processor port.

Workaround: None.

Symptom: The atmVcCrossConnectAdminStatus entries might disappear.

Workaround: None.

Symptom: The switch router will crash and hang when ip http server is configured and a browser connects to http://<router-ip>/%%. This defect can be exploited to produce a denial of service (DoS) attack. This information has been announced on public Internet mailing lists which are widely read by both security professionals and by security "crackers," and should be considered public information.

Workaround: Disable the IP http server with the following command: no ip http server
Alternatively, the administrator can block port 80 connections to the switch router via access lists or other firewall methods. For further information, refer to the security advisory available at http://www.cisco.com/warp/public/707/advisory.html.

Symptom: VP Tunnel deletions leave behind stray SVC blocks.

Workaround: None.

Symptom: ifOutOctets wrapping at 3000000 on an ATM interface.

Workaround: None.

Symptom: CPU hog by OIR handler.

Workaround: None.

Symptom: Multicast stats shows an incorrect rate in kbps.

Workaround: None.

Symptom: HVPT: Incorrect scheduling values installed for low PCR. When a HVPT with a PCR of 2 kbps is configured on a OC-3 interface, this results in the cell starving of WKVC on the main interface.

Workaround: None.

Symptom: When a switch is running release 12.0(4a)W5(11a) and the OSPF area range command is used, the summary LSA created might get stuck in the database and not be flushed after the command is removed from the configuration.

Workaround: None.

Symptom: A failure trap is not generated when an IMA group gets deleted. The function which sends the trap is called from the alarms processing action function. In case of group deletion the driver stops sending alarm processing commands and thus it will not sense any group state changes that cause a trap to be generated.

Workaround: None.

Symptom: DS3 Frame Relay port adapter firmware hangs with 16 channel groups oversubscribed.

Workaround: None.

Symptom: A bus error exception might occur when adding parties to a root connection.

Workaround: None.

Symptom: The output from the show bridge commands are incomplete.

Workaround: None.

Symptom: The ILMI status of shaped and hierarchical tunnel subinterfaces that are down (not shutdown) appear stuck in the Restarting state after a shutdown/no shutdown command sequence.

Workaround: None.

Symptom: Soft PVCs might be disabled on subinterfaces.

Workaround: None.

Symptom: The Frame Relay/ATM port leg might go out of sync while attempting to delete a connection and port snooping is enabled.

Workaround: Disable snooping on the ATM port before attempting to delete a Frame Relay PVC.

Symptom: The show controller command does not reflect T1 loopback configuration.

Workaround: None.

Symptom: The switch might fail to periodically send poll PDUs when running 12.0 code with UNI version set to 3.0. This might result in no_response_timer expirations and flapping of the SSCOP link.

Workaround: Configure UNI 3.1 on the interface.

Symptom: ATM Feature request for ILMI-STATUS SNMP MIB.

Workaround: None.

Symptom: ATM signalling would not generate the connect ACK message and would result in conformance test failure.

Workaround: None.

Symptom: OAM F5 loopback cells are not passing across 25-Mbps port adapter interfaces.

Workaround: Configure the global configuration command no atm oam intercept end-to-end on the switch.

Symptom: The switch might have spurious memory access tags after configuring and unconfiguring tag switching on different ATM interfaces. This is not known to impact tag switching functionality on the switch. The following message might appear on the console:

    *** gd03_tag_stress: Mon Jan 31 08:35:12 2000 949336512 comment         Spurious
  memory accesses on gd03_r55_11: count = 1 ***
 *** gd03_tag_stress: Mon Jan 31 08:35:12 2000 949336512 comment         1C
 1  0x60254C28 0x60236140 0x6009868C 0x60098678
Workaround: None.

Symptom: The switch does not correctly handle extended QoS and end-to-end transit delay IE. This occurs primarily when operating with third-party vendor equipment.

Workaround: None.

Symptom: Multiple tags for the default route might occur with VC-merge.

Workaround: Do not use the tag-switching ip default-route command to assign tags to the default route.

Symptom: VP associated signalling code point not supported between the switch router and the Vswitch on UNI 4.0/IISP interfaces. This is an interoperability problem with the Vswitch. When the tunnels are configured on UNI/IISP interface, the switch router sends connection Id IE with the VP associated signaling code point. This code point is not supported on UNI/IISP links. Hence the Vswitch releases the call.

Workaround: Use the atm signalling vpci [value] command to configure the value of VPCI that is carried in the signaling messages within a VP tunnel.

Symptom: New SVC or soft PVC calls from a LightStream 1010 ATM switch or Catalyst 8510 to a Fore ATM switch across a PNNI interface fail to connect. Connections initiated from the Fore switch do not fail.

Workaround: None.

Symptom: The ifAdminStatus remains UP even when the controller is ADMINDOWN.

Workaround: None.

Symptom: ATMVcCrossConnectLowHighIfIndex implementation problem inconsistent with RFC 1695.

Workaround: None.

Symptom: When an IMA card is present, and the system runs out of memory for any reason, the system might also crash.

Workaround: None.

Symptom: IMA group fails to come up intermittently, especially after reload and on E1 IMA links.

Workaround: Go to one of the IMA interfaces and give the following command:

    Switch(config-if)# fwmon "altrap 00 ff 00 ff 00 ff"
If the group still remains down, it indicates a persisting alarm on the line. The line configuration has to be checked to clear the problem.

Symptom: When hundreds of TVCs in bidirectional mode are repeatedly configured and unconfigured on a switch router, VC resources might be exhausted.

Workaround: None.

Symptom: When configuring the snmp trap receiver with the snmp-server host command, the following error message might appear:

%Bad oid failed to create host entry when configuring snmp host

Workaround: This error message only occurs when SNMP is initially configured on the switch and it is the first time that the snmp-server command is issued. If the command is entered again the error message is not seen.

Symptom: The status of the PVC on the DCE is always ACTIVE. The PVC is not INACTIVE when interface (DTE) is shutdown.

Workaround: None.

Symptom: Some VCs remain DOWN after NVRAM configuration on system reload.

Workaround: The ping succeeds only if the PVC is deleted and re-installed.

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.

Symptom: Performing a shutdown/no shutdown command sequence on an ARM interface, especially when it has configured a large number of LANE clients, might cause an error message like this to appear:

%LANE-3-LANE_ERROR: lecs finder: ILMI hung on interface ATM1/0/0

It indicates an internal timeout occurred. It should try to self-cover and not affect any normal operations.

Workaround: None.

Symptom: Software forced crash in logger_buffer_init.

Workaround: None.

Symptom: The loopback configured on an ATM interface is retained even after that interface becomes a member of an IMA group.

Workaround: Enter 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. Enter the shutdown command on the ATM interface and configure the interface as a member of an IMA group.

Symptom: ASP failed in power-on diagnostics with ws-x5165 installed.

Workaround: If config-reg has to be 0x2101: insert a Flash PC card in either slot 0 or slot1 when reloading the cat5500, OR Set the config-reg to 0x2102.

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: Soft-VCs sometimes come up without ILMI active.

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: Under certain circumstances, the switch router might display inaccurate traffic statistics on NNI or UNI interfaces.

Workaround: None.

Symptom: Despite having enough bandwidth, Resource Management might reject some
soft PVCs.

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: The Digital Crossconnect Unit (DCU) on the T1/E1 CES port adapter might malfunction unexpectedly.

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: 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 line code violation (LCV) counter on an IMA port adapter might not be updated.

Workaround: None.

Symptom: Under certain conditions, the ATM link on an IMA port adapter might come up with a different framing mode.

Workaround: None.

Symptom: Under certain conditions, the ATM link on an IMA port adapter might come up with different line codes 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: 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 count increments, but the output cell count does not increment.

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: Issuing the atm snoop interface command might cause the FC1 system to fail unexpectedly.

Workaround: None.

Symptom: The switch router 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 ATM 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: For the 12.0(7)W5(15c) release, the units for the atm soft vc command are not backwards-compatible with the 12.0(4a)W5(11a) release.

Workaround: None.

Symptom: When polling the sysObjectID of a Catalyst 8510, 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.

Workaround: None.

Symptom: On a PNNI signaling 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: The CES ABCD bits are not user configurable when a fault occurs.

Workaround: None.

Symptom: When forwarding a call setup from one VP tunnel to another, the switch router might drop certain information elements that are considered mandatory. This problem might cause compatibility problems with third-party equipment.

Workaround: None.

Symptom: Configuring a channelized E1 (CE1) Frame Relay 2.048-Mbps ATM port adapter for clear E1 might cause the line code violation and LES counters to increment continually.

Workaround: None.

Symptom: The soft PVC count might not be included in atmfAtmLayerConfiguredVCCs.

Workaround: None.

Symptom: When entering the show running-config command, the switch router might fail unexpectedly due to a bus error.

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.

Symptom: The advertised priority is not updated for PGL if configured to match the advertised priority.

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: Under certain circumstances, the lane server-bus ethernet command might cause the following exception:

Unexpected exception, CPU signal 10, PC = 0x605CB430
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 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: When a call setup traverses a switch running PNNI on the ingress side and IISP (3.0 or 3.1) on the egress side, the message might be corrupted.

Workaround: None.

Symptom: The switch uses backward parameters in QoS IE for PtMP calls. This might cause incompatibility with other vendors' implementations.

Workaround: None.

Symptom: The atm soft-vc command does not disable OAM intercept.

Workaround: When the ordering of OAM cells must be preserved in the cell-flow, OAM intercept must be disabled. Using the atm soft-vc command to disable this does not work for soft PVCs.

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 after the uplink ATM has been broken (when configured as structured mode).

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: The switch router does not accept PVCs terminating on their CPU port over point-to-point subinterfaces.

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: A crash might occur while removing subinterfaces using the no interface command.

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

Symptom: The switch router sends acctngFileFull trap every 10 seconds if the snmp-server enable trap atm is included in the configuration.

Workaround: Remove the snmp-server enable trap atm command from the configuration or use the no atmacct-deb command to turn off the sending of the misinforming trap.

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: 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: When running tag switching, no tag is created for the default route.

Workaround: None.

Symptom: Soft VPs and PVPs cannot coexist due to VPI allocation errors.

Workaround: None.

Symptom: On a switch router running release 11.3(3a)WA4(6), if an atm ping command is entered 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: 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: 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: Connections with end-to-end delay IE included in the connect message might fail. Examples of these connections include UNI40, CBR, UBR-RT. When a switch router that is an intermediate switch passes a bad CONNECT message from one side to the other, 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: 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 been 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.

Note   Power-on diagnostics run only if the switch is powered on. Power-on diagnostics do not run when using the reload command.
Workaround: After using the write erase command, use the write memory command before power cycling the switch.

Symptom: A switch router with 8 LAN emulation clients configured on the CPU, and 300 point-to-point and 60 point-to-multipoint connections could crash unexpectedly due to an infinite loop.

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: Frame Relay soft VC configuration is not possible using SNMP. You cannot configure Frame Relay soft VCs using the casfVcEndptTable in SNMP.

Workaround: None.

Symptom: The DS1 MIB objects do not work for T1/E1 ATM cards.

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: Spurious memory access on show ip route command 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: On a switch router 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 64MB of RAM.

Workaround: None.

Symptom: Frame Relay soft VC is 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 torn down.

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 long period of time (for example, overnight) causes memory fragmentation in the TDP process.

Workaround: None.

Symptom: When loading a software image version 11.3 or later on a switch router with a software image version 11.2 or earlier, 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: The show controller atm card/subcard/port command displays the incorrect interface type after hot swapping the port adapter.

Workaround: None.

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.

Workaround: None.

Symptom: Snooping error: %ATMCORE-3-INTERNAL_ERROR:connUpdateFreeVxiMap:bitMapInfo

When snoop-VC is configured on a port the switch returns this internal error message:

%ATMCORE-3-INTERNAL_ERROR: connUpdateFreeVxiMap: bitMapInfo null ptr

Workaround: This message can be ignored; it does not affect the snooping functionality.

Symptom: When using the show atm interface resource atm card/subcard/port.subport command, the following error message appears:

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: A non-zero generic flow control (GFC) field is not reset to zero when passing through the switch router.

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 a large amount of data is sent out of the Ethernet interface, the interface can become overwhelmed and start generating the following 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 entered on the interface.

Workaround: None.

Symptom: ATM Accounting: Exception in validblock_diagnose because resources at destination switch were not available for soft VC setup.

Workaround: None.

Symptom: A third party vendor, when running UNI 4.0, cannot connect a VC to a Cisco router, running UNI 3.1, by way of a Catalyst 8510 or a LightStream 1010 ATM switch.

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" 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: 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 oversubscribes 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: 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: 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: After hot swapping an OC-3 LR port adapter with an OC-3 MM port adapter, the system might fail unexpectedly.

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 transmission to the scheduled rate. This can cause cells to be dropped in the WAN. It 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: There is a small divergence in the measured output of the shaped VP tunnels at rates of 90 Mbps and above.

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: 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: IP host-routing does not disable when specified.

Workaround: Enable and disable IP routing and then save the configuration to NVRAM.

Symptom: Under some rare conditions (not yet identified), some ports might get stuck in the WaitDevType state.

Workaround: Reboot the switch.

Symptom: The ATM switch does not currently support maxvc-number negotiation through ILMI.

Workaround: None.

Symptom: If there are multiple parallel paths to the same destination on a switch router 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: On a switch router equipped with an FC-PFQ, the maximum number of cells available for use is 64,511. The number of cells in the switch fabric is 65,535.

Workaround: None.

Symptom: The Catalyst 8510 Ethernet or LightStream 1010 ATM switch does not receive CDP multicast packets. However, the switch router does send out CDP multicast packets.

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: 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: Cell loss might occur while hot swapping a power supply.

Workaround: None.

Symptom: SNMP support of the ciscoAtmIfPhysEntryData table and LED information is not available on the 25-MB port adapter.

Workaround: None.

Symptom: The cell count reported on a snooped interface is twice the actual number of cells transmitted.

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 interface's 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: 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: 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 PortSelectGroups representing the interface on which the call came in and the counters shown on the PortSelectGroups 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 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: 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:

  • VBR: sustained cell rate (SCR) + sustained-cell-rate-margin-factor x (PCR - SCR).

  • ABR, UBR: no bandwidth is allocated.

Workaround: None.

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

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: 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: Under very heavy traffic conditions the switch might experience temporary queue cell failures. This should clear after the traffic congestion clears.

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

Interoperability

Starting with the following software releases, hardware and software functionality interoperability exists between CSR interface modules and MSR interface modules by way of the ATM router module on the MSR chassis running an MSR image:

  • Cisco IOS Release 12.0(10)W5(18b) supports interoperability between CSR interface modules and MSR interface modules by way of the ATM router module on the Catalyst 8510 MSR running an MSR image.

Y2K Compliance

Catalyst 8510 and LightStream 1010 ATM systems running Cisco IOS Release 12.0(0.6)W5(1) or later have been certified as Y2K Compliant. For more information, see the following URL: http://www.cisco.com/warp/public/752/2000/.

Related Documentation

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 h ttp://www.cisco.com, h ttp://www-china.cisco.com, or h ttp://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.

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 the following sites:

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

Cisco documentation is available in the following ways:

  • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/public/ordsum.html

  • 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 corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation Feedback

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

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

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasmania 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 documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

  • P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

  • P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

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

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

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

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

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

P1 and P2 level problems are defined as follows:

  • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

  • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.