Release Notes for Catalyst 5000 Family Software Release 6.x [Cisco Catalyst 5000 Series Switches]

Table Of Contents

Release Notes for Catalyst 5000 Family Software Release 6.x

Contents

Release 6.x Memory Requirements

Release 6.x Software Upgrade Path

Release 6.x Supervisor Engine Support Matrix

Supervisor Engine Redundancy

Product and Software Version Support Matrix

Release 6.x Orderable Software Images

New Features for Supervisor Engine Software Release 6.4

New Features for Supervisor Engine Software Release 6.3

New Features for Supervisor Engine Software Release 6.2

New Features for Supervisor Engine Software Release 6.1

Open and Resolved Caveats in Software Release 6.4(23a)

Open Caveats in Software Release 6.4(23a)

Resolved Caveats in Software Release 6.4(23a)

Open and Resolved Caveats in Software Release 6.4(23)

Open Caveats in Software Release 6.4(23)

Resolved Caveats in Software Release 6.4(23)

Open and Resolved Caveats in Software Release 6.4(22)

Open Caveats in Software Release 6.4(22)

Resolved Caveats in Software Release 6.4(22)

Open and Resolved Caveats in Software Release 6.4(21)

Open Caveats in Software Release 6.4(21)

Resolved Caveats in Software Release 6.4(21)

Open and Resolved Caveats in Software Release 6.4(20)

Open Caveats in Software Release 6.4(20)

Resolved Caveats in Software Release 6.4(20)

Open and Resolved Caveats in Software Release 6.4(19)

Open Caveats in Software Release 6.4(19)

Resolved Caveats in Software Release 6.4(19)

Open and Resolved Caveats in Software Release 6.4(18)

Open Caveats in Software Release 6.4(18)

Resolved Caveats in Software Release 6.4(18)

Open and Resolved Caveats in Software Release 6.4(17)

Open Caveats in Software Release 6.4(17)

Resolved Caveats in Software Release 6.4(17)

Open and Resolved Caveats in Software Release 6.4(16)

Open Caveats in Software Release 6.4(16)

Resolved Caveats in Software Release 6.4(16)

Open and Resolved Caveats in Software Release 6.4(15)

Open Caveats in Software Release 6.4(15)

Resolved Caveats in Software Release 6.4(15)

Open and Resolved Caveats in Software Release 6.4(14)

Open Caveats in Software Release 6.4(14)

Resolved Caveats in Software Release 6.4(14)

Open and Resolved Caveats in Software Release 6.4(13)

Open Caveats in Software Release 6.4(13)

Resolved Caveats in Software Release 6.4(13)

Open and Resolved Caveats in Software Release 6.4(12)

Open Caveats in Software Release 6.4(12)

Resolved Caveats in Software Release 6.4(12)

Open and Resolved Caveats in Software Release 6.4(11)

Open Caveats in Software Release 6.4(11)

Resolved Caveats in Software Release 6.4(11)

Open and Resolved Caveats in Software Release 6.4(10)

Open Caveats in Software Release 6.4(10)

Resolved Caveats in Software Release 6.4(10)

Open and Resolved Caveats in Software Release 6.4(9)

Open Caveats in Software Release 6.4(9)

Resolved Caveats in Software Release 6.4(9)

Open and Resolved Caveats in Software Release 6.4(8)

Open Caveats in Software Release 6.4(8)

Resolved Caveats in Software Release 6.4(8)

Open and Resolved Caveats in Software Release 6.4(7)

Open Caveats in Software Release 6.4(7)

Resolved Caveats in Software Release 6.4(7)

Open and Resolved Caveats in Software Release 6.4(6)

Open Caveats in Software Release 6.4(6)

Resolved Caveats in Software Release 6.4(6)

Open and Resolved Caveats in Software Release 6.4(5)

Open Caveats in Software Release 6.4(5)

Resolved Caveats in Software Release 6.4(5)

Open and Resolved Caveats in Software Release 6.4(4a)

Open Caveats in Software Release 6.4(4a)

Resolved Caveats in Software Release 6.4(4a)

Open and Resolved Caveats in Software Release 6.4(4)

Open Caveats in Software Release 6.4(4)

Resolved Caveats in Software Release 6.4(4)

Open and Resolved Caveats in Software Release 6.4(3)

Open Caveats in Software Release 6.4(3)

Resolved Caveats in Software Release 6.4(3)

Open and Resolved Caveats in Software Release 6.4(2)

Open Caveats in Software Release 6.4(2)

Resolved Caveats in Software Release 6.4(2)

Open and Resolved Caveats in Software Release 6.4(1)

Open Caveats in Software Release 6.4(1)

Resolved Caveats in Software Release 6.4(1)

Open and Resolved Caveats in Software Release 6.3(10)

Open Caveats in Software Release 6.3(10)

Resolved Caveats in Software Release 6.3(10)

Open and Resolved Caveats in Software Release 6.3(9)

Open Caveats in Software Release 6.3(9)

Resolved Caveats in Software Release 6.3(9)

Open and Resolved Caveats in Software Release 6.3(8)

Open Caveats in Software Release 6.3(8)

Resolved Caveats in Software Release 6.3(8)

Open and Resolved Caveats in Software Release 6.3(7)

Open Caveats in Software Release 6.3(7)

Resolved Caveats in Software Release 6.3(7)

Open and Resolved Caveats in Software Release 6.3(6)

Open Caveats in Software Release 6.3(6)

Resolved Caveats in Software Release 6.3(6)

Open and Resolved Caveats in Software Release 6.3(5)

Open Caveats in Software Release 6.3(5)

Resolved Caveats in Software Release 6.3(5)

Open and Resolved Caveats in Software Release 6.3(4a)

Open Caveats in Software Release 6.3(4a)

Resolved Caveats in Software Release 6.3(4a)

Open and Resolved Caveats in Software Release 6.3(4)

Open Caveats in Software Release 6.3(4)

Resolved Caveats in Software Release 6.3(4)

Open and Resolved Caveats in Software Release 6.3(3a)

Open Caveats in Software Release 6.3(3a)

Resolved Caveats in Software Release 6.3(3a)

Open and Resolved Caveats in Software Release 6.3(3)

Open Caveats in Software Release 6.3(3)

Resolved Caveats in Software Release 6.3(3)

Open and Resolved Caveats in Software Release 6.3(2a)

Open Caveats in Software Release 6.3(2a)

Resolved Caveats in Software Release 6.3(2a)

Open and Resolved Caveats in Software Release 6.3(2)

Open Caveats in Software Release 6.3(2)

Resolved Caveats in Software Release 6.3(2)

Open and Resolved Caveats in Software Release 6.3(1a)

Open Caveats in Software Release 6.3(1a)

Resolved Caveats in Software Release 6.3(1a)

Open and Resolved Caveats in Software Release 6.3(1)

Open Caveats in Software Release 6.3(1)

Resolved Caveats in Software Release 6.3(1)

Open and Resolved Caveats in Software Release 6.2(3a)

Open Caveats in Software Release 6.2(3a)

Resolved Caveats in Software Release 6.2(3a)

Open and Resolved Caveats in Software Release 6.2(2a)

Open Caveats in Software Release 6.2(2a)

Resolved Caveats in Software Release 6.2(2a)

Open and Resolved Caveats in Software Release 6.2(2)

Open Caveats in Software Release 6.2(2)

Resolved Caveats in Software Release 6.2(2)

Open and Resolved Caveats in Software Release 6.2(1a)

Open Caveats in Software Release 6.2(1a)

Resolved Caveats in Software Release 6.2(1a)

Open and Resolved Caveats in Software Release 6.2(1)

Open Caveats in Software Release 6.2(1)

Resolved Caveats in Software Release 6.2(1)

Open and Resolved Caveats in Software Release 6.1(4b)

Open Caveats in Software Release 6.1(4b)

Resolved Caveats in Software Release 6.1(4b)

Open and Resolved Caveats in Software Release 6.1(3a)

Open Caveats in Software Release 6.1(3a)

Resolved Caveats in Software Release 6.1(3a)

Open and Resolved Caveats in Software Release 6.1(3)

Open Caveats in Software Release 6.1(3)

Resolved Caveats in Software Release 6.1(3)

Open and Resolved Caveats in Software Release 6.1(2a)

Open Caveats in Software Release 6.1(2a)

Resolved Caveats in Software Release 6.1(2a)

Open and Resolved Caveats in Software Release 6.1(2)

Open Caveats in Software Release 6.1(2)

Resolved Caveats in Software Release 6.1(2)

Open and Resolved Caveats in Software Release 6.1(1e)

Open Caveats in Software Release 6.1(1e)

Resolved Caveats in Software Release 6.1(1e)

Open and Resolved Caveats in Software Release 6.1(1c)

Open Caveats in Software Release 6.1(1c)

Resolved Caveats in Software Release 6.1(1c)

Open and Resolved Caveats in Software Release 6.1(1)

Open Caveats in Software Release 6.1(1)

Resolved Caveats in Software Release 6.1(1)

Usage Guidelines, Restrictions, and Troubleshooting

System and Supervisor Engine

Modules and Switch Ports

Transceivers

Spanning Tree

VTP, VLANs, and VLAN Trunks

EtherChannel

SPAN

Multicast

Network Analysis Module and TrafficDirector

CiscoView Images

MIBs

Authentication, Authorization, and Accounting

Documentation Updates for Software Release 6.1

Additional Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Product Alerts and Field Notices

Obtaining Technical Assistance

Cisco Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Release Notes for Catalyst 5000 Family Software Release 6.x

Current Release: 6.4(23a) - January 29, 2007

Previous release: 6.4(23), 6.4(22), 6.4(20), 6.4(19), 6.4(18), 6.4(17), 6.4(16) - Supervisor EngineIIG/IIIG images deferred, 6.4(15) - Supervisor EngineIIG/IIIG images deferred, 6.4(14) - Supervisor EngineIIG/IIIG images deferred, 6.4(13), 6.4(12), 6.4(11), 6.4(10), 6.4(9), 6.4(8), 6.4(7), 6.4(6), 6.4(5), 6.4(4a), 6.4(4), 6.4(3), 6.4(2), 6.4(1), 6.3(10), 6.3(9), 6.3(8), 6.3(7), 6.3(6), 6.3(5), 6.3(4a), 6.3(4), 6.3(3a), 6.3(3), 6.3(2a), 6.3(2), 6.3(1a), 6.3(1), 6.2(3a). 6.2(2a), 6.2(2), 6.2(1a), 6.2(1), 6.1(4b), 6.1(3a), 6.1(3), 6.1(2a), 6.1(2), 6. 1(1e), 6.1(1d), 6.1(1c), 6.1(1)

These release notes describe the features, modifications, and caveats for Catalyst 5000 family supervisor engine software release 6.x and all 6.x maintenance releases. The most current 6.x release is supervisor engine software release 6.4(22).

Note The most current version of these release notes can be found at
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat5000/c5krn/sw_rns/78_11304.htm

Caution We strongly recommend that you read these release notes before using your switch or upgrading your switch software.

Note Although the software image in a new Catalyst 5000 family switch operates correctly, later software images containing the latest upgrades and modifications are released regularly to provide you with the most optimized software available. We strongly recommend that you check for the latest released software images at the World Wide Web locations listed in the "Cisco.com" section.

Note Release notes for prior Catalyst 5000 family software releases were accurate at the time of release. However, for information on the latest caveats and updates to previously released Catalyst 5000 family software releases, refer to the release notes for the latest maintenance release in your software release train. You can access all Catalyst 5000 family release notes at the World Wide Web locations listed in the "Cisco.com" section.

Contents

This document consists of these sections:

•Release 6.x Memory Requirements

•Release 6.x Software Upgrade Path

•Release 6.x Supervisor Engine Support Matrix

•Supervisor Engine Redundancy

•Product and Software Version Support Matrix

•Release 6.x Orderable Software Images

•New Features for Supervisor Engine Software Release 6.4

•New Features for Supervisor Engine Software Release 6.3

•New Features for Supervisor Engine Software Release 6.2

•New Features for Supervisor Engine Software Release 6.1

•Open and Resolved Caveats in Software Release 6.4(23a)

•Open and Resolved Caveats in Software Release 6.4(23)

•Open and Resolved Caveats in Software Release 6.4(22)

•Open and Resolved Caveats in Software Release 6.4(21)

•Open and Resolved Caveats in Software Release 6.4(20)

•Open and Resolved Caveats in Software Release 6.4(19)

•Open and Resolved Caveats in Software Release 6.4(18)

•Open and Resolved Caveats in Software Release 6.4(17)

•Open and Resolved Caveats in Software Release 6.4(16)

•Open and Resolved Caveats in Software Release 6.4(15)

•Open and Resolved Caveats in Software Release 6.4(14)

•Open and Resolved Caveats in Software Release 6.4(13)

•Open and Resolved Caveats in Software Release 6.4(12)

•Open and Resolved Caveats in Software Release 6.4(11)

•Open and Resolved Caveats in Software Release 6.4(10)

•Open and Resolved Caveats in Software Release 6.4(9)

•Open and Resolved Caveats in Software Release 6.4(8)

•Open and Resolved Caveats in Software Release 6.4(7)

•Open and Resolved Caveats in Software Release 6.4(6)

•Open and Resolved Caveats in Software Release 6.4(5)

•Open and Resolved Caveats in Software Release 6.4(4a)

•Open and Resolved Caveats in Software Release 6.4(4)

•Open and Resolved Caveats in Software Release 6.4(3)

•Open and Resolved Caveats in Software Release 6.4(2)

•Open and Resolved Caveats in Software Release 6.4(1)

•Open and Resolved Caveats in Software Release 6.3(10)

•Open and Resolved Caveats in Software Release 6.3(9)

•Open and Resolved Caveats in Software Release 6.3(8)

•Open and Resolved Caveats in Software Release 6.3(7)

•Open and Resolved Caveats in Software Release 6.3(6)

•Open and Resolved Caveats in Software Release 6.3(5)

•Open and Resolved Caveats in Software Release 6.3(4a)

•Open and Resolved Caveats in Software Release 6.3(4)

•Open and Resolved Caveats in Software Release 6.3(3a)

•Open and Resolved Caveats in Software Release 6.3(3)

•Open and Resolved Caveats in Software Release 6.3(2a)

•Open and Resolved Caveats in Software Release 6.3(2)

•Open and Resolved Caveats in Software Release 6.3(1a)

•Open and Resolved Caveats in Software Release 6.3(1)

•Open and Resolved Caveats in Software Release 6.2(3a)

•Open and Resolved Caveats in Software Release 6.2(2a)

•Open and Resolved Caveats in Software Release 6.2(2)

•Open and Resolved Caveats in Software Release 6.2(1a)

•Open and Resolved Caveats in Software Release 6.2(1)

•Open and Resolved Caveats in Software Release 6.1(3a)

•Open and Resolved Caveats in Software Release 6.1(3)

•Open and Resolved Caveats in Software Release 6.1(2a)

•Open and Resolved Caveats in Software Release 6.1(2)

•Open and Resolved Caveats in Software Release 6.1(1e)

•Open and Resolved Caveats in Software Release 6.1(1c)

•Open and Resolved Caveats in Software Release 6.1(1)

•Usage Guidelines, Restrictions, and Troubleshooting

•Documentation Updates for Software Release 6.1

•Additional Documentation

•Obtaining Documentation

•Documentation Feedback

•Cisco Product Security Overview

•Product Alerts and Field Notices

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

Release 6.x Memory Requirements

The Catalyst 5000 family supervisor engine 6.x software releases require a minimum of 64-MB DRAM installed on Supervisor Engine III and 32-MB DRAM installed on Supervisor Engines II G and III G.

Release 6.x Software Upgrade Path

Caution Always back up the switch configuration file before upgrading or downgrading the switch software to avoid losing all or part of the configuration stored in nonvolatile RAM (NVRAM). When you do a software downgrade, the configuration will always be lost. Use the write network command (Supervisor Engine II G or III G) or the copy config tftp command (Supervisor Engine III) to back up your configuration to a Trivial File Transfer Protocol (TFTP) server. Use the copy config flash command on a Supervisor Engine III to back up the configuration to a Flash device.

Catalyst 5000 family supervisor engine software image files are available in the Software Center on Cisco.com, Cisco's Web site (software downloads are available to registered Cisco.com users only):

http://www.cisco.com/pcgi-bin/tablebuild.pl/cat5000-sup

Note Supervisor Engine I, II, and III F, and the Catalyst 2926T, Catalyst 2926F, and Catalyst 2926G series switches are not supported in software release 6.x.

Caution When you upgrade from software release versions 4.5(1), 4.5(2), 4.5(3), 5.1(x), or 5.2(1), the Token Ring module configurations are lost. The workaround is to upload the configuration to a TFTP server before upgrading and reload the configuration after the upgrade is complete. This problem only affects the configuration for the actual Token Ring module and not general configurations such as Token Ring VLANs.

Table 1 shows the supervisor engine software upgrade path to software release 6.x from previous supervisor engine software releases.

Table 1 Catalyst 5000 Family 6.x Software Upgrade Path

Upgrade

Upgrade Path

2.4(4) through 3.2(2) to 6.x

Supervisor Engine III

No restriction. Upgrade directly to software release 6.x.

3.2(3) or later to 6.x

All Supervisor Engines

No restriction. Upgrade directly to software release 6.x.

Note In some cases, when upgrading to software release 6.x from release 4.4(1) or earlier, a "Corrupted nvlog area" error is generated. This error is harmless and can be safely ignored.

Release 6.x Supervisor Engine Support Matrix

Catalyst 5000 family switches support these supervisor engine modules in software release 6.x:

•Supervisor Engine II G

•Supervisor Engine III

•Supervisor Engine III G

Some supervisor engine models are not supported in some switch chassis. Table 2 shows which supervisor engine models are supported in which Catalyst 5000 family switch chassis.

The supervisor engines are compatible with specific software releases. For more information, see the "Product and Software Version Support Matrix" section.

Table 2 Supervisor Engine Chassis Support Matrix

Switch Chassis

Supervisor Engine II G

Supervisor Engine III

Supervisor Engine III G

Catalyst 5002 (155 W power supplies)

Yes

No

Yes

Catalyst 5002 (175 W power supplies with PFC¹)

Yes

Yes

Yes

Catalyst 5000

Yes

Yes

Yes

Catalyst 5505

Yes

Yes

Yes

Catalyst 5509

Yes

Yes

Yes

Catalyst 5500

Yes

Yes

Yes

¹PFC=power factor correction

Supervisor Engine Redundancy

You can install redundant supervisor engines in your switch if the following conditions are met:

•The switch must be a Catalyst 5500 series switch.

•The supervisor engines must be Supervisor Engine II G, III, or III G in the following configurations:

–Two Supervisor Engine IIIs with EARL 1

–Two Supervisor Engine IIIs with the NFFC

–Two Supervisor Engine IIIs with the NFFC II

–Two Supervisor Engine II Gs without the RSFC

–Two Supervisor Engine II Gs with the RSFC

–Two Supervisor Engine III Gs without the RSFC

–Two Supervisor Engine III Gs with the RSFC

–One Supervisor Engine II G with the RSFC and one Supervisor Engine II G without the RSFC

–One Supervisor Engine III G with the RSFC and one Supervisor Engine III G without the RSFC

The following redundant configurations are supported:

•Supervisor Engine III with NFFC and Supervisor Engine III with NFFC-A

•Supervisor Engine III with NFFCII and Supervisor Engine III with NFFCII-A

MLS is not supported for traffic on the redundant supervisor engine ports when the supervisor engine in standby mode has the NFFC or NFFCII. MLS is supported for traffic on the redundant supervisor engine ports when the supervisor engine in standby mode has the NFFC-A or NFFCII-A.

For more information on configuring supervisor engines for redundant operation, refer to the Catalyst 5000 Family Software Configuration Guide.

Product and Software Version Support Matrix

Table 3 lists the minimum supervisor engine version and the recommended supervisor engine version for Catalyst 5000 family modules and chassis.

Note There might be additional minimum software version requirements for intelligent modules (modules that run an additional, separate software image). Refer to the software release notes for the module type for more information.

Note Software Release 5.5(7a) is the General Deployment (GD) release for the Catalyst 5000 family switches.

Table 3 Product and Supervisor Engine Software Version Matrix

Product Number

(append with
"=" for spares)

Product Description

Minimum Supervisor Engine Software Version

Recommended Supervisor Engine Software Version

Supervisor Engine II G

WS-X5540

Supervisor Engine II G base module

5.1(1a)

6.3(5)

Supervisor Engine III

WS-X5530-E1

Supervisor Engine III base module

3.1(1)

6.3(5)

WS-X5530-E2

Supervisor Engine III base module
with NFFC

4.1(1)

6.3(5)

WS-X5530-E2A

Supervisor Engine III base module
with enhanced NFFC

4.5(4)

6.3(5)

WS-X5530-E3

Supervisor Engine III base module
with NFFC II

4.3(1a)

6.3(5)

WS-X5530-E3A

Supervisor Engine III base module
with enhanced NFFC II

4.5(4)

6.3(5)

Supervisor Engine III G

WS-X5550

Supervisor Engine III G
2-port 1000BASE-X uplinks

5.1(1a)

6.3(5)

Supervisor Engine Uplink Modules

WS-U5531-FETX

2-port 10/100BASE-TX
Fast Ethernet uplink module

3.1(1)

6.3(5)

WS-U5533-FEFX-MMF

2-port 100BASE-FX
MMF Fast Ethernet uplink module

WS-U5535-FEFX-SMF

2-port 100BASE-FX
SMF Fast Ethernet uplink module

WS-U5537-FETX

4-port 10/100BASE-TX
Fast EtherChannel uplink module

4.3(1a)

6.3(5)

WS-U5534-GESX

2-port 1000BASE-SX
Gigabit Ethernet uplink module

4.1(1)

6.3(5)

WS-U5536-GELX

2-port 1000BASE-LX/LH
Gigabit Ethernet uplink module

WS-U5538-FEFX-MMF

4-port 100BASE-FX
MMF MT-RJ Fast EtherChannel uplink module

4.5(1)

6.3(5)

Supervisor Engine III Feature Cards

WS-F5521=

NetFlow Feature Card (NFFC)

4.1(1)

6.3(5)

WS-F5521A=¹

NetFlow Feature Card (NFFC-A)

4.5(4)

6.3(5)

WS-F5531=²

NFFC II

4.3(1a)

6.3(5)

WS-F5531A=

NFFC II-A

4.5(4)

6.3(5)

WS-F5541=

Route Switch Feature Card (RSFC)

5.1(1a)

6.3(5)

Ethernet, Fast Ethernet, and Gigabit Ethernet

WS-X5010

24-port 10BASE-T Ethernet Telco

1.1

6.3(5)

WS-X5011

12-port 10BASE-FL Ethernet MMF ST

1.2

WS-X5012

48-port 10BASE-T Ethernet

2.4(1)

6.3(5)

WS-X5012A

48-port 10BASE-T Ethernet Telco

4.2(1)

6.3(5)

WS-X5013

24-port 10BASE-T Ethernet RJ-45

2.2(1)

6.3(5)

WS-X5014

48-port, 2-slot 10BASE-T Ethernet

4.2(1)

6.3(5)

WS-X5015-MT

24-port 10BASE-FL Ethernet MT-RJ

5.1(1)

6.3(5)

WS-X5020

48-port, 4-segment 10BASE-T Ethernet Telco

2.1(1)

6.3(5)

WS-X5111

12-port 100BASE-FX Fast Ethernet MMF SC

1.4

WS-X5113

12-port 100BASE-TX Fast Ethernet RJ-45

1.2

WS-X5114

12-port (6-port SMF, 6-port MMF)
100BASE-FX Fast Ethernet SC

2.1(5)

WS-X5201

12-port 100BASE-FX Fast EtherChannel SC

2.3(1)

WS-X5201R

12-port 100BASE-FX backbone Fast Ethernet SC

4.1(2)

6.3(5)

WS-X5203

12-port 10/100BASE-TX Fast EtherChannel RJ-45

2.3(1)

6.3(5)

WS-X5213³

12-port 10/100BASE-TX Fast Ethernet RJ-45

1.5(4)

WS-X5213A

12-port 10/100BASE-TX Fast Ethernet RJ-45

2.1(7)

WS-X5223

24-port, 3-segment
100BASE-TX Fast Ethernet RJ-45

2.2(1)

WS-X5224

24-port 10/100BASE-TX RJ-45

2.4(2)

WS-X5225R

24-port 10/100BASE-TX Fast Ethernet RJ-45

4.1(2)

6.3(5)

WS-X5234-RJ45

24-port 10/100BASE-TX Fast Ethernet RJ-45

4.5(1)

6.3(5)

WS-X5236-FX-MT

24-port 100BASE-FX Fast Ethernet MMF MT-RJ

WS-X5239-RJ21

36-port 10/100BASE-TX Fast Ethernet Telco

5.1(2a)

6.3(5)

WS-X5403

3-port 1000BASE-X Gigabit Ethernet

4.1(1)

6.3(5)

WS-X5410

9-port, 2-slot 1000BASE-X
Gigabit EtherChannel module⁴

4.2(1)

WS-X5237-FX-MT

24-port 100BASE-FX Fast Ethernet SMF MT-RJ

5.4(2)

6.3(5)

Gigabit Interface Converters (GBICs)

WS-G5484=

1000BASE-SX GBIC

4.1(1)

6.3(5)

WS-G5486=

1000BASE-LX/LH GBIC

WS-G5487=

1000BASE-ZX GBIC

4.5(1)

Token Ring

WS-X5030

16-port Token Ring module, UTP/FTP, RJ-45

3.1(1)

6.3(5)

WS-X5031

16-port Token Ring module, Volition, VF-45

FDDI/CDDI

WS-X5101

1 Dual-attach Multimode FDDI MIC

1.3

6.3(5)

WS-X5103

1 Dual-attach CDDI RJ-45

WS-X5104

1 Dual-attach Single-Mode FDDI ST

WS-X5105

1 Dual-attach Multimode FDDI SC

ATM

WS-X51533

1-port OC-3 UTP RJ-45

1.4

6.3(5)

WS-X51543

1-port OC-3 Single-Mode SC

WS-X51553

1-port OC-3 Multimode SC

WS-X5156

1 Dual PHY OC-3 UTP RJ-45

2.1(5)

WS-X5157

1 Dual PHY OC-3 Single-Mode SC

WS-X5158

1 Dual PHY OC-3 Multimode SC

WS-X5161

1 Dual PHY OC-12 MMF SC, MPOA/LANE

3.2(1)

6.3(5)

WS-X5162

1 Dual PHY OC-12 SC, MPOA/LANE

WS-X5166

1 Dual PHY DS3, BNC connectors

3.1(1)

WS-X5167

1 Dual PHY OC-3 MMF SC, MPOA/LANE

3.2(1)

WS-X5168

1 Dual PHY OC-3 SMF SC, MPOA/LANE

Route Switch Module

WS-X5302

Route Switch Module

2.3(1)

6.3(5)

Fabric Integration Modules

WS-X5165

ATM fabric integration module

4.3(1a)

6.3(5)

WS-X5305

Layer 3 fabric integration module

4.4(1)

Network Analysis Module

WS-X5380

Network Analysis Module (32-MB DRAM)

4.3(1a)

6.3(5)

WS-X5381

Network Analysis Module (128-MB DRAM)

4.3(1a)

6.3(5)

Modular Chassis

WS-C5000

Catalyst 5000 chassis (5-slot)

1.1

6.3(5)

WS-C5002

Catalyst 5002 chassis (2-slot)

2.2(1)

6.3(5)

WS-C5500

Catalyst 5500 chassis (13-slot)

WS-C5505

Catalyst 5505 chassis (5-slot)

2.3(1)

WS-C5509

Catalyst 5509 chassis (9-slot)

4.2(1)

6.3(5)

¹Latest hardware revision of the NFFC.

²Latest hardware revision of the NFFC II.

³The WS-X5213, WS-X5153, WS-X5154, and WS-X5155 modules have been moved to end-of-life (EOL) status.

⁴The Gigabit EtherChannel module (WS-X5410) is supported with Supervisor Engine I or II or in a Catalyst 5000 chassis with supervisor engine software release 4.3(1) or later in conjunction with Gigabit EtherChannel module software release 4.3(1) or later. This hardware was not fully tested with the Gigabit EtherChannel module in earlier releases.

Release 6.x Orderable Software Images

Table 4 lists the software versions and applicable ordering information for Catalyst 5000 family supervisor engine software release 6.x.

Note CiscoView images are available approximately 2 weeks after the Flash images are released.

Table 4 Release 6.x Orderable Software Image Matrix

Software Version

Filename

Orderable Product Number

Flash on System

Orderable Product Number

Spare Upgrade (Floppy Media)

Supervisor Engine II G and III G

6.1(1)

cat5000-supg.6-1-1.bin

SC5K-SUPG-6.1.1

SC5K-SUPG-6.1.1=

6.1(1) Flash image
with SSH¹

cat5000-supgk9.6-1-1.bin

SC5K-SUPGK9-6.1.1

SC5K-SUPGK9-6.1.1=

6.1(1c)

cat5000-supg.6-1-1c.bin

SC5K-SUPG-6.1.1

SC5K-SUPG-6.1.1=

6.1(1c) Flash image
with SSH

cat5000-supgk9.6-1-1c.bin

SC5K-SUPGK9-6.1.1

SC5K-SUPGK9-6.1.1=

6.1(1e)

cat5000-supg.6-1-1e.bin

SC5K-SUPG-6.1.1

SC5K-SUPG-6.1.1=

6.1(1e) Flash image
with SSH

cat5000-supgk9.6-1-1e.bin

SC5K-SUPGK9-6.1.1

SC5K-SUPGK9-6.1.1=

6.1(2)

cat5000-supg.6-1-2.bin

SC5K-SUPG-6.1.2

SC5K-SUPG-6.1.2=

6.1(2) Flash image
with SSH

cat5000-supgk9.6-1-2.bin

SC5K-SUPGK9-6.1.2

SC5K-SUPGK9-6.1.2=

6.1(2a)

cat5000-supg.6-1-2a.bin

SC5K-SUPG-6.1.2

SC5K-SUPG-6.1.2=

6.1(2a) Flash image
with SSH

cat5000-supgk9.6-1-2a.bin

SC5K-SUPGK9-6.1.2

SC5K-SUPGK9-6.1.2=

6.1(3)

cat5000-supg.6-1-3.bin

SC5K-SUPG-6.1.3

SC5K-SUPG-6.1.3=

6.1(3) Flash image
with SSH

cat5000-supgk9.6-1-3.bin

SC5K-SUPGK9-6.1.3

SC5K-SUPGK9-6.1.3=

6.1(3a)

cat5000-supg.6-1-3a.bin

SC5K-SUPG-6.1.3a

SC5K-SUPG-6.1.3a=

6.1(3a) Flash image
with SSH

cat5000-supgk9.6-1-3a.bin

SC5K-SUPGK9-6.1.3a

SC5K-SUPGK9-6.1.3a=

6.1(3a)

cat5000-supg.6-1-3a.bin

SC5K-SUPG-6.1.3

SC5K-SUPG-6.1.3=

6.1(3a) Flash image
with SSH

cat5000-supgk9.6-1-3a.bin

SC5K-SUPGK9-6.1.3

SC5K-SUPGK9-6.1.3=

6.1(4b)

cat5000-supg.6-1-4b.bin

SC5K-SUPG-6.1.4b

SC5K-SUPG-6.1.4b=

6.1(4b) Flash image
with SSH

cat5000-supgk9.6-1-4b.bin

SC5K-SUPGK9-6.1.4b

SC5K-SUPGK9-6.1.4b=

6.2(1)

cat5000-supg.6-2-1.bin

SC5K-SUPG-6.2.1

SC5K-SUPG-6.2.1=

6.2(1) Flash image
with SSH

cat5000-supgk9.6-2-1.bin

SC5K-SUPGK9-6.2.1

SC5K-SUPGK9-6.2.1=

6.2(1a)

cat5000-supg.6-2-1a.bin

SC5K-SUPG-6.2.1a

SC5K-SUPG-6.2.1a=

6.2(1a) Flash image
with SSH

cat5000-supgk9.6-2-1a.bin

SC5K-SUPGK9-6.2.1a

SC5K-SUPGK9-6.2.1a=

6.2(1a)

cat5000-supg.6-2-1a.bin

SC5K-SUPG-6.2.1

SC5K-SUPG-6.2.1=

6.2(1a) Flash image
with SSH

cat5000-supgk9.6-2-1a.bin

SC5K-SUPGK9-6.2.1

SC5K-SUPGK9-6.2.1=

6.2(2)

cat5000-supg.6-2-2.bin

SC5K-SUPG-6.2.2

SC5K-SUPG-6.2.2=

6.2(2) Flash image
with SSH

cat5000-supgk9.6-2-2.bin

SC5K-SUPGK9-6.2.2

SC5K-SUPGK9-6.2.2=

6.2(2a)

cat5000-supg.6-2-2a.bin

SC5K-SUPG-6.2.2

SC5K-SUPG-6.2.2=

6.2(2a) Flash image
with SSH

cat5000-supgk9.6-2-a2.bin

SC5K-SUPGK9-6.2.2

SC5K-SUPGK9-6.2.2=

6.2(3a)

cat5000-supg.6-2-3a.bin

SC5K-SUPG-6.2.3

SC5K-SUPG-6.2.3=

6.2(3a) Flash image
with SSH

cat5000-supgk9.6-2-3a.bin

SC5K-SUPGK9-6.2.3

SC5K-SUPGK9-6.2.3=

6.2(2a)

cat5000-supg.6-2-2a.bin

SC5K-SUPG-6.2.2

SC5K-SUPG-6.2.2=

6.2(2a) Flash image
with SSH

cat5000-supgk9.6-2-2a.bin

SC5K-SUPGK9-6.2.2

SC5K-SUPGK9-6.2.2=

6.3(1)

cat5000-supg.6-3-1.bin

SC5K-SUPG-6.3.1

SC5K-SUPG-6.3.1=

6.3(1) Flash image
with SSH

cat5000-supgk9.6-3-1.bin

SC5K-SUPGK9-6.3.1

SC5K-SUPGK9-6.3.1=

6.3(1a)

cat5000-supg.6-3-1a.bin

SC5K-SUPG-6.3.1

SC5K-SUPG-6.3.1=

6.3(1a) Flash image
with SSH

cat5000-supgk9.6-3-1a.bin

SC5K-SUPGK9-6.3.1

SC5K-SUPGK9-6.3.1=

6.3(2)

cat5000-supg.6-3-2.bin

SC5K-SUPG-6.3.2

SC5K-SUPG-6.3.2=

6.3(2) Flash image
with SSH

cat5000-supgk9.6-3-2.bin

SC5K-SUPGK9-6.3.2

SC5K-SUPGK9-6.3.2=

6.3(2a)

cat5000-supg.6-3-2a.bin

SC5K-SUPG-6.3.2

SC5K-SUPG-6.3.2=

6.3(2a) Flash image
with SSH

cat5000-supgk9.6-3-2a.bin

SC5K-SUPGK9-6.3.2

SC5K-SUPGK9-6.3.2=

6.3(3)

cat5000-supg.6-3-3.bin

SC5K-SUPG-6.3.3

SC5K-SUPG-6.3.3=

6.3(3) Flash image
with SSH

cat5000-supgk9.6-3-3.bin

SC5K-SUPGK9-6.3.3

SC5K-SUPGK9-6.3.3=

6.3(3a)

cat5000-supg.6-3-3a.bin

SC5K-SUPG-6.3.3

SC5K-SUPG-6.3.3=

6.3(3a) Flash image
with SSH

cat5000-supgk9.6-3-3a.bin

SC5K-SUPGK9-6.3.3

SC5K-SUPGK9-6.3.3=

6.3(4)

cat5000-supg.6-3-4.bin

SC5K-SUPG-6.3.4

SC5K-SUPG-6.3.4=

6.3(4) Flash image
with SSH

cat5000-supgk9.6-3-4.bin

SC5K-SUPGK9-6.3.4

SC5K-SUPGK9-6.3.4=

6.3(4a)

cat5000-supg.6-3-4a.bin

SC5K-SUPG-6.3.4

SC5K-SUPG-6.3.4=

6.3(4a) Flash image
with SSH

cat5000-supgk9.6-3-4a.bin

SC5K-SUPGK9-6.3.4

SC5K-SUPGK9-6.3.4=

6.3(5)

cat5000-supg.6-3-5.bin

SC5K-SUPG-6.3.5

SC5K-SUPG-6.3.5=

6.3(5) Flash image
with SSH

cat5000-supgk9.6-3-5.bin

SC5K-SUPGK9-6.3.5

SC5K-SUPGK9-6.3.5=

6.3(6)

cat5000-supg.6-3-6.bin

SC5K-SUPG-6.3.6

SC5K-SUPG-6.3.6=

6.3(6) Flash image
with SSH

cat5000-supgk9.6-3-6.bin

SC5K-SUPGK9-6.3.6

SC5K-SUPGK9-6.3.6=

6.3(7)

cat5000-supg.6-3-7.bin

SC5K-SUPG-6.3.7

SC5K-SUPG-6.3.7=

6.3(7) Flash image
with SSH

cat5000-supgk9.6-3-7.bin

SC5K-SUPGK9-6.3.7

SC5K-SUPGK9-6.3.7=

6.3(8)

cat5000-supg.6-3-8.bin

SC5K-SUPG-6.3.8

SC5K-SUPG-6.3.8=

6.3(8) Flash image
with SSH

cat5000-supgk9.6-3-8.bin

SC5K-SUPGK9-6.3.8

SC5K-SUPGK9-6.3.8=

6.3(9)

cat5000-supg.6-3-9.bin

SC5K-SUPG-6.3.9

SC5K-SUPG-6.3.9=

6.3(9) Flash image
with SSH

cat5000-supgk9.6-3-9.bin

SC5K-SUPGK9-6.3.9

SC5K-SUPGK9-6.3.9=

6.3(10)

cat5000-supg.6-3-10.bin

SC5K-SUPG-6.3.10

SC5K-SUPG-6.3.10=

6.3(10) Flash image
with SSH

cat5000-supgk9.6-3-10.bin

SC5K-SUPGK9-6.3.10

SC5K-SUPGK9-6.3.10=

6.4(1)

cat5000-supg.6-4-1.bin

SC5K-SUPG-6.4.1

SC5K-SUPG-6.4.1=

6.4(1) Flash image
with SSH

cat5000-supgk9.6-4-1.bin

SC5K-SUPGK9-6.4.1

SC5K-SUPGK9-6.4.1=

6.4(2)

cat5000-supg.6-4-2.bin

SC5K-SUPG-6.4.2

SC5K-SUPG-6.4.2=

6.4(2) Flash image
with SSH

cat5000-supgk9.6-4-2.bin

SC5K-SUPGK9-6.4.2

SC5K-SUPGK9-6.4.2=

6.4(3)

cat5000-supg.6-4-3.bin

SC5K-SUPG-6.4.3

SC5K-SUPG-6.4.3=

6.4(3) Flash image
with SSH

cat5000-supgk9.6-4-3.bin

SC5K-SUPGK9-6.4.3

SC5K-SUPGK9-6.4.3=

6.4(4)

cat5000-supg.6-4-4.bin

SC5K-SUPG-6.4.4

SC5K-SUPG-6.4.4=

6.4(4) Flash image
with SSH

cat5000-supgk9.6-4-4.bin

SC5K-SUPGK9-6.4.4

SC5K-SUPGK9-6.4.4=

6.4(4a)

cat5000-supg.6-4-4a.bin

SC5K-SUPG-6.4.4

SC5K-SUPG-6.4.4=

6.4(4a) Flash image
with SSH

cat5000-supgk9.6-4-4a.bin

SC5K-SUPGK9-6.4.4

SC5K-SUPGK9-6.4.4=

6.4(5)

cat5000-supg.6-4-5.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(5) Flash image
with SSH

cat5000-supgk9.6-4-5.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(6)

cat5000-supg.6-4-6.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(6) Flash image
with SSH

cat5000-supgk9.6-4-6.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(7)

cat5000-supg.6-4-7.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(7) Flash image
with SSH

cat5000-supgk9.6-4-7.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(8)

cat5000-supg.6-4-8.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(8) Flash image
with SSH

cat5000-supgk9.6-4-8.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(9)

cat5000-supg.6-4-9.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(9) Flash image
with SSH

cat5000-supgk9.6-4-9.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(10)

cat5000-supg.6-4-10.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(10) Flash image
with SSH

cat5000-supgk9.6-4-10.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(11)

cat5000-supg.6-4-11.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(11) Flash image
with SSH

cat5000-supgk9.6-4-11.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(12)

cat5000-supg.6-4-12.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(12) Flash image
with SSH

cat5000-supgk9.6-4-12.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(13)

cat5000-supg.6-4-13.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(13) Flash image
with SSH

cat5000-supgk9.6-4-13.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(17)

cat5000-supg.6-4-17.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(17) Flash image
with SSH

cat5000-supgk9.6-4-17.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(18)

cat5000-supg.6-4-18.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(18) Flash image
with SSH

cat5000-supgk9.6-4-18.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(19)

cat5000-supg.6-4-19.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(19) Flash image
with SSH

cat5000-supgk9.6-4-19.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(20)

cat5000-supg.6-4-20.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(20) Flash image
with SSH

cat5000-supgk9.6-4-20.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(21)

cat5000-supg.6-4-21.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(21) Flash image
with SSH

cat5000-supgk9.6-4-21.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

6.4(22)

cat5000-supg.6-4-22.bin

SC5K-SUPG-6.4

SC5K-SUPG-6.4=

6.4(22) Flash image
with SSH

cat5000-supgk9.6-4-22.bin

SC5K-SUPGK9-6.4

SC5K-SUPGK9-6.4=

Supervisor Engine III

6.1(1)

cat5000-sup3.6-1-1.bin

SC5K-SUP3-6.1.1

SC5K-SUP3-6.1.1=

6.1(1) Flash image
with SSH¹

cat5000-sup3k9.6-1-1.bin

SC5K-SUP3K9-6.1.1

SC5K-SUP3K9-6.1.1=

6.1(1a) Flash image
with CiscoView²

cat5000-sup3cv.6-1-1a.bin

SC5K-SUP3CV-6.1.1

SC5K-SUP3CV-6.1.1=

6.1(1a) Flash image
with CiscoView and SSH¹

cat5000-sup3cvk9.6-1-1a.bin

SC5K-SUP3CVK9-6.1.1

SC5K-SUP3CVK9-6.1.1=

6.1(1c)

cat5000-sup3.6-1-1c.bin

SC5K-SUP3-6.1.1

SC5K-SUP3-6.1.1=

6.1(1c) Flash image
with SSH

cat5000-sup3k9.6-1-1c.bin

SC5K-SUP3K9-6.1.1

SC5K-SUP3K9-6.1.1=

6.1(1c) Flash image
with CiscoView2

cat5000-sup3cv.6-1-1c.bin

SC5K-SUP3CV-6.1.1

SC5K-SUP3CV-6.1.1=

6.1(1c) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-1c.bin

SC5K-SUP3CVK9-6.1.1

SC5K-SUP3CVK9-6.1.1=

6.1(1e)

cat5000-sup3.6-1-1e.bin

SC5K-SUP3-6.1.1

SC5K-SUP3-6.1.1=

6.1(1e) Flash image
with SSH

cat5000-sup3k9.6-1-1e.bin

SC5K-SUP3K9-6.1.1

SC5K-SUP3K9-6.1.1=

6.1(1e) Flash image
with CiscoView2

cat5000-sup3cv.6-1-1e.bin

SC5K-SUP3CV-6.1.1

SC5K-SUP3CV-6.1.1=

6.1(1e) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-1e.bin

SC5K-SUP3CVK9-6.1.1

SC5K-SUP3CVK9-6.1.1=

6.1(2)

cat5000-sup3.6-1-2.bin

SC5K-SUP3-6.1.2

SC5K-SUP3-6.1.2=

6.1(2) Flash image
with SSH

cat5000-sup3k9.6-1-2.bin

SC5K-SUP3K9-6.1.2

SC5K-SUP3K9-6.1.2=

6.1(2) Flash image
with CiscoView2

cat5000-sup3cv.6-1-2.bin

SC5K-SUP3CV-6.1.2

SC5K-SUP3CV-6.1.2=

6.1(2) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-2.bin

SC5K-SUP3CVK9-6.1.2

SC5K-SUP3CVK9-6.1.2=

6.1(2a)

cat5000-sup3.6-1-2a.bin

SC5K-SUP3-6.1.2

SC5K-SUP3-6.1.2=

6.1(2a) Flash image
with SSH

cat5000-sup3k9.6-1-2a.bin

SC5K-SUP3K9-6.1.2

SC5K-SUP3K9-6.1.2=

6.1(2a) Flash image
with CiscoView2

cat5000-sup3cv.6-1-2a.bin

SC5K-SUP3CV-6.1.2

SC5K-SUP3CV-6.1.2=

6.1(2a) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-2a.bin

SC5K-SUP3CVK9-6.1.2

SC5K-SUP3CVK9-6.1.2=

6.1(3)

cat5000-sup3.6-1-3.bin

SC5K-SUP3-6.1.3

SC5K-SUP3-6.1.3=

6.1(3) Flash image
with SSH

cat5000-sup3k9.6-1-3.bin

SC5K-SUP3K9-6.1.3

SC5K-SUP3K9-6.1.3=

6.1(3) Flash image
with CiscoView2

cat5000-sup3cv.6-1-3.bin

SC5K-SUP3CV-6.1.3

SC5K-SUP3CV-6.1.3=

6.1(3) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-3.bin

SC5K-SUP3CVK9-6.1.3

SC5K-SUP3CVK9-6.1.3=

6.1(3a)

cat5000-sup3.6-1-3a.bin

SC5K-SUP3-6.1.3

SC5K-SUP3-6.1.3=

6.1(3a) Flash image
with SSH

cat5000-sup3k9.6-1-3a.bin

SC5K-SUP3K9-6.1.3

SC5K-SUP3K9-6.1.3=

6.1(3a) Flash image
with CiscoView2

cat5000-sup3cv.6-1-3a.bin

SC5K-SUP3CV-6.1.3

SC5K-SUP3CV-6.1.3=

6.1(3a) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-3a.bin

SC5K-SUP3CVK9-6.1.3

SC5K-SUP3CVK9-6.1.3=

6.1(3a)

cat5000-sup3.6-1-3a.bin

SC5K-SUP3-6.1.3a

SC5K-SUP3-6.1.3a=

6.1(3a) Flash image
with SSH

cat5000-sup3k9.6-1-3a.bin

SC5K-SUP3K9-6.1.3a

SC5K-SUP3K9-6.1.3a=

6.1(4b)

cat5000-sup3.6-1-4b.bin

SC5K-SUP3-6.1.4b

SC5K-SUP3-6.1.4b=

6.1(4b) Flash image
with SSH

cat5000-sup3k9.6-1-4b.bin

SC5K-SUP3K9-6.1.4b

SC5K-SUP3K9-6.1.4b=

6.1(4b) Flash image
with CiscoView2

cat5000-sup3cv.6-1-4b.bin

SC5K-SUP3CV-6.1.4b

SC5K-SUP3CV-6.1.4b=

6.1(4b) Flash image
with CiscoView and SSH2

cat5000-sup3cvk9.6-1-4b.bin

SC5K-SUP3CVK9-6.1.4b

SC5K-SUP3CVK9-6.1.4b=

6.2(1)

cat5000-sup3.6-2-1.bin

SC5K-SUP3-6.2.1

SC5K-SUP3-6.2.1=

6.2(1) Flash image
with SSH

cat5000-sup3k9.6-2-1.bin

SC5K-SUP3K9-6.2.1

SC5K-SUP3K9-6.2.1=

6.2(1a)

cat5000-sup3.6-2-1a.bin

SC5K-SUP3-6.2.1a

SC5K-SUP3-6.2.1a=

6.2(1a) Flash image
with SSH

cat5000-sup3k9.6-2-1a.bin

SC5K-SUP3K9-6.2.1a

SC5K-SUP3K9-6.2.1a=

6.2(1a)

cat5000-sup3.6-2-1a.bin

SC5K-SUP3-6.2.1

SC5K-SUP3-6.2.1=

6.2(1a) Flash image
with SSH

cat5000-sup3k9.6-2-1a.bin

SC5K-SUP3K9-6.2.1

SC5K-SUP3K9-6.2.1=

6.2(2)

cat5000-sup3.6-2-2.bin

SC5K-SUP3-6.2.2

SC5K-SUP3-6.2.2=

6.2(2) Flash image
with SSH

cat5000-sup3k9.6-2-2.bin

SC5K-SUP3K9-6.2.2

SC5K-SUP3K9-6.2.2=

6.2(2) Flash image
with CiscoView

cat5000-sup3cv.6-2-2.bin

SC5K-SUP3CV-6.2.2

SC5K-SUP3CV-6.2.2=

6.2(2) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-2-2.bin

SC5K-SUP3CVK9-6.2.2

SC5K-SUP3CVK9-6.2.2=

6.2(2a)

cat5000-sup3.6-2-2a.bin

SC5K-SUP3-6.2.2

SC5K-SUP3-6.2.2=

6.2(2a) Flash image
with SSH

cat5000-sup3k9.6-2-2a.bin

SC5K-SUP3K9-6.2.2

SC5K-SUP3K9-6.2.2=

6.2(2a) Flash image
with CiscoView

cat5000-sup3cv.6-2-2a.bin

SC5K-SUP3CV-6.2.2

SC5K-SUP3CV-6.2.2=

6.2(2a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-2-2a.bin

SC5K-SUP3CVK9-6.2.2

SC5K-SUP3CVK9-6.2.2=

6.2(3a)

cat5000-sup3.6-2-3a.bin

SC5K-SUP3-6.2.3

SC5K-SUP3-6.2.3=

6.2(3a) Flash image
with SSH

cat5000-sup3k9.6-2-3a.bin

SC5K-SUP3K9-6.2.3

SC5K-SUP3K9-6.2.3=

6.2(3a) Flash image
with CiscoView

cat5000-sup3cv.6-2-3a.bin

SC5K-SUP3CV-6.2.3

SC5K-SUP3CV-6.2.3=

6.2(3a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-2-3a.bin

SC5K-SUP3CVK9-6.2.3

SC5K-SUP3CVK9-6.2.3=

6.3(1)

cat5000-sup3.6-3-1.bin

SC5K-SUP3-6.3.1

SC5K-SUP3-6.3.1=

6.3(1) Flash image
with SSH

cat5000-sup3k9.6-3-1.bin

SC5K-SUP3K9-6.3.1

SC5K-SUP3K9-6.3.1=

6.3(1) Flash image
with CiscoView

cat5000-sup3cv.6-3-1.bin

SC5K-SUP3CV-6.3.1

SC5K-SUP3CV-6.3.1=

6.3(1) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-1.bin

SC5K-SUP3CVK9-6.3.1

SC5K-SUP3CVK9-6.3.1=

6.3(1a)

cat5000-sup3.6-3-1a.bin

SC5K-SUP3-6.3.1

SC5K-SUP3-6.3.1=

6.3(1a) Flash image
with SSH

cat5000-sup3k9.6-3-1a.bin

SC5K-SUP3K9-6.3.1

SC5K-SUP3K9-6.3.1=

6.3(1a) Flash image
with CiscoView

cat5000-sup3cv.6-3-1a.bin

SC5K-SUP3CV-6.3.1

SC5K-SUP3CV-6.3.1=

6.3(1a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-1a.bin

SC5K-SUP3CVK9-6.3.1

SC5K-SUP3CVK9-6.3.1=

6.3(2)

cat5000-sup3.6-3-2.bin

SC5K-SUP3-6.3.2

SC5K-SUP3-6.3.2=

6.3(2) Flash image
with SSH

cat5000-sup3k9.6-3-2.bin

SC5K-SUP3K9-6.3.2

SC5K-SUP3K9-6.3.2=

6.3(2) Flash image
with CiscoView

cat5000-sup3cv.6-3-2.bin

SC5K-SUP3CV-6.3.2

SC5K-SUP3CV-6.3.2=

6.3(2) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-2.bin

SC5K-SUP3CVK9-6.3.2

SC5K-SUP3CVK9-6.3.2=

6.3(2a)

cat5000-sup3.6-3-2a.bin

SC5K-SUP3-6.3.2

SC5K-SUP3-6.3.2=

6.3(2a) Flash image
with SSH

cat5000-sup3k9.6-3-2a.bin

SC5K-SUP3K9-6.3.2

SC5K-SUP3K9-6.3.2=

6.3(2a) Flash image
with CiscoView

cat5000-sup3cv.6-3-2a.bin

SC5K-SUP3CV-6.3.2

SC5K-SUP3CV-6.3.2=

6.3(2a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-2a.bin

SC5K-SUP3CVK9-6.3.2

SC5K-SUP3CVK9-6.3.2=

6.3(3)

cat5000-sup3.6-3-3.bin

SC5K-SUP3-6.3.3

SC5K-SUP3-6.3.3=

6.3(3) Flash image
with SSH

cat5000-sup3k9.6-3-3.bin

SC5K-SUP3K9-6.3.3

SC5K-SUP3K9-6.3.3=

6.3(3) Flash image
with CiscoView

cat5000-sup3cv.6-3-3.bin

SC5K-SUP3CV-6.3.3

SC5K-SUP3CV-6.3.3=

6.3(3) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-3.bin

SC5K-SUP3CVK9-6.3.3

SC5K-SUP3CVK9-6.3.3=

6.3(3a)

cat5000-sup3.6-3-3a.bin

SC5K-SUP3-6.3.3

SC5K-SUP3-6.3.3=

6.3(3a) Flash image
with SSH

cat5000-sup3k9.6-3-3a.bin

SC5K-SUP3K9-6.3.3

SC5K-SUP3K9-6.3.3=

6.3(3a) Flash image
with CiscoView

cat5000-sup3cv.6-3-3a.bin

SC5K-SUP3CV-6.3.3

SC5K-SUP3CV-6.3.3=

6.3(3a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-3a.bin

SC5K-SUP3CVK9-6.3.3

SC5K-SUP3CVK9-6.3.3=

6.3(4)

cat5000-sup3.6-3-4.bin

SC5K-SUP3-6.3.4

SC5K-SUP3-6.3.4=

6.3(4) Flash image
with SSH

cat5000-sup3k9.6-3-4.bin

SC5K-SUP3K9-6.3.4

SC5K-SUP3K9-6.3.4=

6.3(4) Flash image
with CiscoView

cat5000-sup3cv.6-3-4.bin

SC5K-SUP3CV-6.3.4

SC5K-SUP3CV-6.3.4=

6.3(4) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-4.bin

SC5K-SUP3CVK9-6.3.4

SC5K-SUP3CVK9-6.3.4=

6.3(4a)

cat5000-sup3.6-3-4a.bin

SC5K-SUP3-6.3.4

SC5K-SUP3-6.3.4=

6.3(4a) Flash image
with SSH

cat5000-sup3k9.6-3-4a.bin

SC5K-SUP3K9-6.3.4

SC5K-SUP3K9-6.3.4=

6.3(4a) Flash image
with CiscoView

cat5000-sup3cv.6-3-4a.bin

SC5K-SUP3CV-6.3.4

SC5K-SUP3CV-6.3.4=

6.3(4a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-4a.bin

SC5K-SUP3CVK9-6.3.4

SC5K-SUP3CVK9-6.3.4=

6.3(5)

cat5000-sup3.6-3-5.bin

SC5K-SUP3-6.3.5

SC5K-SUP3-6.3.5=

6.3(5) Flash image
with SSH

cat5000-sup3k9.6-3-5.bin

SC5K-SUP3K9-6.3.5

SC5K-SUP3K9-6.3.5=

6.3(5) Flash image
with CiscoView

cat5000-sup3cv.6-3-5.bin

SC5K-SUP3CV-6.3.5

SC5K-SUP3CV-6.3.5=

6.3(5) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-5.bin

SC5K-SUP3CVK9-6.3.5

SC5K-SUP3CVK9-6.3.5=

6.3(6)

cat5000-sup3.6-3-6.bin

SC5K-SUP3-6.3.6

SC5K-SUP3-6.3.6=

6.3(6) Flash image
with SSH

cat5000-sup3k9.6-3-6.bin

SC5K-SUP3K9-6.3.6

SC5K-SUP3K9-6.3.6=

6.3(6) Flash image
with CiscoView

cat5000-sup3cv.6-3-6.bin

SC5K-SUP3CV-6.3.6

SC5K-SUP3CV-6.3.6=

6.3(6) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-6.bin

SC5K-SUP3CVK9-6.3.6

SC5K-SUP3CVK9-6.3.6=

6.3(7)

cat5000-sup3.6-3-7.bin

SC5K-SUP3-6.3.7

SC5K-SUP3-6.3.7=

6.3(7) Flash image
with SSH

cat5000-sup3k9.6-3-7.bin

SC5K-SUP3K9-6.3.7

SC5K-SUP3K9-6.3.7=

6.3(7) Flash image
with CiscoView

cat5000-sup3cv.6-3-7.bin

SC5K-SUP3CV-6.3.7

SC5K-SUP3CV-6.3.7=

6.3(7) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-7.bin

SC5K-SUP3CVK9-6.3.7

SC5K-SUP3CVK9-6.3.7=

6.3(8)

cat5000-sup3.6-3-8.bin

SC5K-SUP3-6.3.8

SC5K-SUP3-6.3.8=

6.3(8) Flash image
with SSH

cat5000-sup3k9.6-3-8.bin

SC5K-SUP3K9-6.3.8

SC5K-SUP3K9-6.3.8=

6.3(8) Flash image
with CiscoView

cat5000-sup3cv.6-3-8.bin

SC5K-SUP3CV-6.3.8

SC5K-SUP3CV-6.3.8=

6.3(8) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-8.bin

SC5K-SUP3CVK9-6.3.8

SC5K-SUP3CVK9-6.3.8=

6.3(9)

cat5000-sup3.6-3-9.bin

SC5K-SUP3-6.3.9

SC5K-SUP3-6.3.9=

6.3(9) Flash image
with SSH

cat5000-sup3k9.6-3-9.bin

SC5K-SUP3K9-6.3.9

SC5K-SUP3K9-6.3.9=

6.3(9) Flash image
with CiscoView

cat5000-sup3cv.6-3-9.bin

SC5K-SUP3CV-6.3.9

SC5K-SUP3CV-6.3.9=

6.3(9) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-9.bin

SC5K-SUP3CVK9-6.3.9

SC5K-SUP3CVK9-6.3.9=

6.3(10)

cat5000-sup3.6-3-10.bin

SC5K-SUP3-6.3.10

SC5K-SUP3-6.3.10=

6.3(10) Flash image
with SSH

cat5000-sup3k9.6-3-10.bin

SC5K-SUP3K9-6.3.10

SC5K-SUP3K9-6.3.10=

6.3(10) Flash image
with CiscoView

cat5000-sup3cv.6-3-10.bin

SC5K-SUP3CV-6.3.10

SC5K-SUP3CV-6.3.10=

6.3(10) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-3-10.bin

SC5K-SUP3CVK9-6.3.10

SC5K-SUP3CVK9-6.3.10=

6.4(1)

cat5000-sup3.6-4-1.bin

SC5K-SUP3-6.4.1

SC5K-SUP3-6.4.1=

6.4(1) Flash image
with SSH

cat5000-sup3k9.6-4-1.bin

SC5K-SUP3K9-6.4.1

SC5K-SUP3K9-6.4.1=

6.4(1) Flash image
with CiscoView

cat5000-sup3cv.6-4-1.bin

SC5K-SUP3CV-6.4.1

SC5K-SUP3CV-6.4.1=

6.4(1) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-1.bin

SC5K-SUP3CVK9-6.4.1

SC5K-SUP3CVK9-6.4.1=

6.4(2)

cat5000-sup3.6-4-2.bin

SC5K-SUP3-6.4.2

SC5K-SUP3-6.4.2=

6.4(2) Flash image
with SSH

cat5000-sup3k9.6-4-2.bin

SC5K-SUP3K9-6.4.2

SC5K-SUP3K9-6.4.2=

6.4(2) Flash image
with CiscoView

cat5000-sup3cv.6-4-2.bin

SC5K-SUP3CV-6.4.2

SC5K-SUP3CV-6.4.2=

6.4(2) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-2.bin

SC5K-SUP3CVK9-6.4.2

SC5K-SUP3CVK9-6.4.2=

6.4(3)

cat5000-sup3.6-4-3.bin

SC5K-SUP3-6.4.3

SC5K-SUP3-6.4.3=

6.4(3) Flash image
with SSH

cat5000-sup3k9.6-4-3.bin

SC5K-SUP3K9-6.4.3

SC5K-SUP3K9-6.4.3=

6.4(3) Flash image
with CiscoView

cat5000-sup3cv.6-4-3.bin

SC5K-SUP3CV-6.4.3

SC5K-SUP3CV-6.4.3=

6.4(3) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-3.bin

SC5K-SUP3CVK9-6.4.3

SC5K-SUP3CVK9-6.4.3=

6.4(4)

cat5000-sup3.6-4-4.bin

SC5K-SUP3-6.4.4

SC5K-SUP3-6.4.4=

6.4(4) Flash image
with SSH

cat5000-sup3k9.6-4-4.bin

SC5K-SUP3K9-6.4.4

SC5K-SUP3K9-6.4.4=

6.4(4) Flash image
with CiscoView

cat5000-sup3cv.6-4-4.bin

SC5K-SUP3CV-6.4.4

SC5K-SUP3CV-6.4.4=

6.4(4) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-4.bin

SC5K-SUP3CVK9-6.4.4

SC5K-SUP3CVK9-6.4.4=

6.4(4a)

cat5000-sup3.6-4-4a.bin

SC5K-SUP3-6.4.4

SC5K-SUP3-6.4.4=

6.4(4a) Flash image
with SSH

cat5000-sup3k9.6-4-4a.bin

SC5K-SUP3K9-6.4.4

SC5K-SUP3K9-6.4.4=

6.4(4a) Flash image
with CiscoView

cat5000-sup3cv.6-4-4a.bin

SC5K-SUP3CV-6.4.4

SC5K-SUP3CV-6.4.4=

6.4(4a) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-4a.bin

SC5K-SUP3CVK9-6.4.4

SC5K-SUP3CVK9-6.4.4=

6.4(5)

cat5000-sup3.6-4-5.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(5) Flash image
with SSH

cat5000-sup3k9.6-4-5.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(5) Flash image
with CiscoView

cat5000-sup3cv.6-4-5.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(5) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-5.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(6)

cat5000-sup3.6-4-6.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(6) Flash image
with SSH

cat5000-sup3k9.6-4-6.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(6) Flash image
with CiscoView

cat5000-sup3cv.6-4-6.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(6) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-6.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(7)

cat5000-sup3.6-4-7.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(7) Flash image
with SSH

cat5000-sup3k9.6-4-7.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(7) Flash image
with CiscoView

cat5000-sup3cv.6-4-7.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(7) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-7.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(8)

cat5000-sup3.6-4-8.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(8) Flash image
with SSH

cat5000-sup3k9.6-4-8.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(8) Flash image
with CiscoView

cat5000-sup3cv.6-4-8.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(8) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-8.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(9)

cat5000-sup3.6-4-9.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(9) Flash image
with SSH

cat5000-sup3k9.6-4-9.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(9) Flash image
with CiscoView

cat5000-sup3cv.6-4-9.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(9) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-9.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(10)

cat5000-sup3.6-4-10.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(10) Flash image
with SSH

cat5000-sup3k9.6-4-10.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(10) Flash image
with CiscoView

cat5000-sup3cv.6-4-10.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(10) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-10.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(11)

cat5000-sup3.6-4-11.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(11) Flash image
with SSH

cat5000-sup3k9.6-4-11.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(11) Flash image
with CiscoView

cat5000-sup3cv.6-4-11.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(11) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-11.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(12)

cat5000-sup3.6-4-12.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(12) Flash image
with SSH

cat5000-sup3k9.6-4-12.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(12) Flash image
with CiscoView

cat5000-sup3cv.6-4-12.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(12) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-12.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(13)

cat5000-sup3.6-4-13.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(13) Flash image
with SSH

cat5000-sup3k9.6-4-13.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(13) Flash image
with CiscoView

cat5000-sup3cv.6-4-13.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(13) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-13.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(14)

cat5000-sup3.6-4-14.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(14) Flash image
with SSH

cat5000-sup3k9.6-4-14.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(14) Flash image
with CiscoView

cat5000-sup3cv.6-4-14.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(14) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-14.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(15)

cat5000-sup3.6-4-15.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(15) Flash image
with SSH

cat5000-sup3k9.6-4-15.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(15) Flash image
with CiscoView

cat5000-sup3cv.6-4-15.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(15) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-15.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(16)

cat5000-sup3.6-4-16.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(16) Flash image
with SSH

cat5000-sup3k9.6-4-16.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(16) Flash image
with CiscoView

cat5000-sup3cv.6-4-16.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(16) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-16.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(17)

cat5000-sup3.6-4-17.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(17) Flash image
with SSH

cat5000-sup3k9.6-4-17.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(17) Flash image
with CiscoView

cat5000-sup3cv.6-4-17.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(17) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-17.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(18)

cat5000-sup3.6-4-18.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(18) Flash image
with SSH

cat5000-sup3k9.6-4-18.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(18) Flash image
with CiscoView

cat5000-sup3cv.6-4-18.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(18) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-18.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(19)

cat5000-sup3.6-4-19.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(19) Flash image
with SSH

cat5000-sup3k9.6-4-19.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(19) Flash image
with CiscoView

cat5000-sup3cv.6-4-19.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(19) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-19.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(20)

cat5000-sup3.6-4-20.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(20) Flash image
with SSH

cat5000-sup3k9.6-4-20.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(20) Flash image
with CiscoView

cat5000-sup3cv.6-4-20.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(20) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-20.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(21)

cat5000-sup3.6-4-21.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(21) Flash image
with SSH

cat5000-sup3k9.6-4-21.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(21) Flash image
with CiscoView

cat5000-sup3cv.6-4-21.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(21) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-21.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

6.4(22)

cat5000-sup3.6-4-22.bin

SC5K-SUP3-6.4

SC5K-SUP3-6.4=

6.4(22) Flash image
with SSH

cat5000-sup3k9.6-4-22.bin

SC5K-SUP3K9-6.4

SC5K-SUP3K9-6.4=

6.4(22) Flash image
with CiscoView

cat5000-sup3cv.6-4-22.bin

SC5K-SUP3CV-6.4

SC5K-SUP3CV-6.4=

6.4(22) Flash image
with CiscoView and SSH

cat5000-sup3cvk9.6-4-22.bin

SC5K-SUP3CVK9-6.4

SC5K-SUP3CVK9-6.4=

¹This release has been deferred due to CSCds85763.

²The 6.1(1c) CiscoView, 6.1(2) CiscoView, and 6.1(3) CiscoView images are affected by CSCdu25881. The CiscoView that is embedded in Catalyst OS software will not work after May 11, 2001, because the digital certificates used to sign the Java classes have expired. This problem is resolved in release 6.2(2) CiscoView, which will be available approximately two weeks after the release of 6.2(2). For workarounds and additional information, see the following URL: http://www.cisco.com/warp/public/770/fn13613.shtml

New Features for Supervisor Engine Software Release 6.4

There are no new hardware or software features in software release 6.4.

New Features for Supervisor Engine Software Release 6.3

This section describes the new features available in software release 6.3:

•Text file configuration mode

When you use the text file configuration mode, the system stores its configuration as a text file in nonvolatile storage, either in NVRAM or Flash memory. This text file consists of commands you use to configure various features.

•CDP enhancements

The following CDPv2 enhancements are included in this release:

–Addition of TLVs such as sysName, sysObjectID, management address, and physical location

–Support of a new device ID format called the mac-address format in addition to the original format (as in the device hardware serial number)

–Display of changes corresponding to some parameters such as device ID for the show cdp command

•SNMPv3 counters displayed using the CLI

Use the CLI to display SNMP counters for various MIBs.

•SNMPv3 enhancements

The SNMPv3 implementation in software releases prior to 6.3(1) support RFC2271 through RFC2275. RFC2271 through RFC2275 were replaced with RFC2571 through RFC2576. The SNMPv3 enhancement in 6.3(1) implements RFC2571 through RFC2576.

•Support for the following MIBs:

–CISCO-AAA-CLIENT-MIB

–CISCO-STP-EXTENSION-MIB

–CISCO-SYSTEM-MIB enhancement

–CISCO-SWITCH-ENGINE-MIB Enhancement

New Features for Supervisor Engine Software Release 6.2

This section describes the new features available in software release 6.2:

•Bridge Protocol Data Unit (BPDU) packet filtering

BPDU packet filtering turns off BPDU transmission on PortFast-enabled ports and nontrunking ports.

•BPDU skew detection

BPDU skew detection allows you to troubleshoot slow network convergence caused by skewing.

•IEEE 802.1x

IEEE 802.1x is a client-server-based access control and authentication protocol that restricts unauthorized devices from connecting to a LAN through publicly accessible ports.

•Core dump for debugging

A core dump produces a comprehensive report of images when your system fails due to a software error. The core image is produced in Cisco core file format and is stored in the file system. By examining the core dump file, TAC can analyze the error condition of a terminated process.

•Local command accounting

Local command accounting records the last 100 commands that the user entered into the system.

•Loop guard

The loop guard feature checks that a root port or an alternate root port is receiving BPDUs. If a port is not receiving BPDUs, the loop guard feature puts the port into an inconsistent state, isolating the failure and letting spanning tree converge to a stable topology until the port starts receiving BPDUs again.

•Dynamic port VLAN membership with auxiliary VLANs

Prior to software release 6.2(1), dynamic ports could only belong to one VLAN. You could not enable the dynamic port VLAN feature on ports that carried a native VLAN and an auxiliary VLAN. With software releases 6.2(1) and later, the dynamic ports can belong to two VLANs. The switch port configured for connecting an IP phone can have separate VLANs configured for carrying the following traffic:

–Voice traffic to and from the IP phone (auxiliary VLAN)

–Data traffic to and from the PC connected to the switch through the access port of the IP phone (native VLAN)

•Support for the following MIBs:

–CISCO-CATOS-ACL-QOS-MIB

–CISCO-QOS-POLICY-MIB

–CISCO-STACK-MIB enhancement

–CISCO-STP-EXTENSIONS-MIB enhancement

–CISCO-SWITCH-ENGINE-MIB enhancement

–CISCO-VTP-MIB enhancement

–HC-RMON-MIB enhancement

New Features for Supervisor Engine Software Release 6.1

This section describes the new features available in software release 6.1.

•Jumbo frame support on EtherChannel, trunk ports, and all Ethernet ports

When you enable the jumbo frames feature on a port, the port can switch large frames or jumbo frames. The default maximum transmission unit (MTU) frame size is 1548 bytes for all Ethernet, Fast Ethernet, and Gigabit Ethernet ports. When you enable the jumbo frames feature on a port, the MTU size increases to 9000 or 24000 bytes.

•Secure Shell (SSH) encryption

The Secure Shell encryption feature provides security for Telnet sessions to the switch. Secure Shell encryption supports the DES and 3DES encryption methods and can be used in conjunction with RADIUS and TACACS+ authentication.

•IOS ping command

The -s argument in the IOS ping command allows you to configure the number of packets to ping, the packet size, and the wait time before timing out a response. The wait time can be set as low as 0, which produces a continuous ping.

•Layer 2 Traceroute

The Layer 2 Traceroute utility allows you to identify the physical path that a packet will take when going from a source to a destination. The Layer 2 Traceroute utility determines the path by looking at the forwarding engine tables of the switches in the path.

•MAC address filtering

You can filter traffic based on a host's MAC address so that packets that are tagged with that specific source MAC address are discarded. When you specify a MAC address filter, incoming traffic from that host MAC address will be dropped and packets addressed to that host will not be forwarded.

•Ability to limit console and Telnet login attempts

You can specify how many console and Telnet login attempts to allow and the duration of the lockout after the switch has denied a login attempt.

•Reduced MAC address usage

The MAC address reduction feature is used to enable extended-range VLAN identification. When you enable MAC address reduction on Catalyst 5000 family switches, the pool of MAC addresses used for the VLAN spanning tree are disabled, leaving a single MAC address that identifies the switch.

•Spanning tree root guard

The root guard feature forces a port to become a designated port so that no switch on the other end of the link can become a root switch.

•write tech-support command

The write tech-support command allows you to generate a status report with information about your switch, which you can upload to a TFTP server and send to Cisco TAC.

•System warnings—error counters

Selected debug port counters are polled at a fixed interval and warnings are generated when the count differs from the previous poll.

•Configuration file searchability

You can search for text at the --More-- prompt during a show command by entering a slash character (/) followed by a text string.

•Globally disable EtherChannel

You can disable all EtherChannels on the switch by entering the set port channel all mode off command.

•Globally disable trunking

You can disable all trunks on the switch by entering the set trunk all off command.

•Enhanced support for scripting

When configured from a configuration file, the Catalyst 5000 family switch assumes a positive answer ("yes") to all the confirmation prompts.

•SNMP group access context

When defining the access rights of an SNMP group, you can specify a context string and specify how to match the context string.

Open and Resolved Caveats in Software Release 6.4(23a)

These sections describe open and resolved caveats in supervisor engine software release 6.4(23a):

•Open Caveats in Software Release 6.4(23a)

•Resolved Caveats in Software Release 6.4(23a)

Open Caveats in Software Release 6.4(23a)

There are no open caveats in supervisor engine software release 6.4(23a).

Resolved Caveats in Software Release 6.4(23a)

This section describes resolved caveats in supervisor engine software release 6.4(23a):

•When a supervisor engine switchover is performed on a switch with redundant Supervisor Engine III modules that is running software version 6.4(23), all ports go into the error-disabled state and all non-intelligent switching modules stay in the "other" state.

Workaround: Enable an errdisable-timeout for the "other" state by using the set errdisable-timeout enable other command.

This problem is resolved in software release 6.4(23a). (CSCsh31072)

Open and Resolved Caveats in Software Release 6.4(23)

These sections describe open and resolved caveats in supervisor engine software release 6.4(23):

•Open Caveats in Software Release 6.4(23)

•Resolved Caveats in Software Release 6.4(23)

Open Caveats in Software Release 6.4(23)

This section describes open caveats in supervisor engine software release 6.4(23):

•You can disable the summertime setting by using the set summertime disable command when you are actually in summertime. This command will cause the clock to be set back to offset time. You can define the offset by using the set summertime recurring command or the offset will be set to a default of 60 minutes. (CSCsh11577)

Resolved Caveats in Software Release 6.4(23)

This section describes resolved caveats in supervisor engine software release 6.4(23):

•A Catalyst 5000 series switch running Catalyst operating system release 7.6(14) or later may unexpectedly reload due to a TLB exception.

Workaround: None.

This problem is resolved in software release 6.4(23). (CSCsb91548)

•The supervisor engine might fail over with the following error message:
Last Exception occurred on [date] ...
Software version = 6.4(18)
Error Msg:
PID = 35 cdpdtimer
EPC: 806F1670
The supervisor engine appears to be operating normally when this problem occurs. This problem is resolved in software release 6.4(23). (CSCsd35254)

•Catalyst switches with voice switching modules (24-port FXS) running CatOS 6.4 lose SNMP functionality after a short period of time.

Workaround: None.

This problem is resolved in software release 6.4(23). (CSCse23142)

•Starting in calendar year 2007, daylight savings summertime rules may cause CatOS to generate timestamps (such as in syslog messages) that are off by one hour.

Workaround: Use the set summertime command to manually configure the start date and end date for daylight savings time. Enter the following commands:
Console> (enable) set summertime enable PDT
Summertime is enabled and set to 'PDT'
  Start : Sun Mar 11 2007, 02:00:00
  End   : Sun Nov 4 2007, 02:00:00
  Offset: 60 minutes
  Recurring: yes, starting at 02:00am of second Sunday of March and ending on 0.
Console> (enable) set summertime recurring second Sunday March 02:00 first Sunday 
November 02:00 60
Summertime is enabled and set to 'PDT'
  Start : Sun Mar 11 2007, 02:00:00
  End   : Sun Nov 4 2007, 02:00:00
  Offset: 60 minutes
  Recurring: yes, starting at 02:00am of second Sunday of March and ending on 0.
Console> (enable)
Note This example specifies the United States Pacific time zone.

This workaround will not work if the time in the configuration is modified to a date before November 6, 2006. The limitation is not present while upgrading.

This problem is resolved in software release 6.4(23). (CSCse79110)

Open and Resolved Caveats in Software Release 6.4(22)

These sections describe open and resolved caveats in supervisor engine software release 6.4(22):

•Open Caveats in Software Release 6.4(22)

•Resolved Caveats in Software Release 6.4(22)

Open Caveats in Software Release 6.4(22)

Note For a description of caveats resolved in software release 6.4(22), see the "Resolved Caveats in Software Release 6.4(22)" section.

This section describes the open caveats in supervisor engine software release 6.4(22):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(22)

Note For a description of open caveats in software release 6.4(22), see the "Open Caveats in Software Release 6.4(22)" section.

There are no resolved caveats in software release 6.4(22).

Open and Resolved Caveats in Software Release 6.4(21)

These sections describe open and resolved caveats in supervisor engine software release 6.4(21):

•Open Caveats in Software Release 6.4(21)

•Resolved Caveats in Software Release 6.4(21)

Open Caveats in Software Release 6.4(21)

Note For a description of caveats resolved in software release 6.4(21), see the "Resolved Caveats in Software Release 6.4(21)" section.

This section describes the open caveats in supervisor engine software release 6.4(21):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(21)

Note For a description of open caveats in software release 6.4(21), see the "Open Caveats in Software Release 6.4(21)" section.

There are no resolved caveats in software release 6.4(21).

Open and Resolved Caveats in Software Release 6.4(20)

These sections describe open and resolved caveats in supervisor engine software release 6.4(20):

•Open Caveats in Software Release 6.4(20)

•Resolved Caveats in Software Release 6.4(20)

Open Caveats in Software Release 6.4(20)

Note For a description of caveats resolved in software release 6.4(20), see the "Resolved Caveats in Software Release 6.4(20)" section.

This section describes the open caveats in supervisor engine software release 6.4(20):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(20)

Note For a description of open caveats in software release 6.4(20), see the "Open Caveats in Software Release 6.4(20)" section.

•After entering the set ip unreachable disable command, "destination unreachable" replies continue to be output from the switch.

This problem is resolved in software release 6.4(20). (CSCsb56969)

Open and Resolved Caveats in Software Release 6.4(19)

These sections describe open and resolved caveats in supervisor engine software release 6.4(19):

•Open Caveats in Software Release 6.4(19)

•Resolved Caveats in Software Release 6.4(19)

Open Caveats in Software Release 6.4(19)

Note For a description of caveats resolved in software release 6.4(19), see the "Resolved Caveats in Software Release 6.4(19)" section.

This section describes the open caveats in supervisor engine software release 6.4(19):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(19)

Note For a description of open caveats in software release 6.4(19), see the "Open Caveats in Software Release 6.4(19)" section.

There are no resolved caveats in software release 6.4(19).

Open and Resolved Caveats in Software Release 6.4(18)

These sections describe open and resolved caveats in supervisor engine software release 6.4(18):

•Open Caveats in Software Release 6.4(18)

•Resolved Caveats in Software Release 6.4(18)

Open Caveats in Software Release 6.4(18)

Note For a description of caveats resolved in software release 6.4(18), see the "Resolved Caveats in Software Release 6.4(18)" section.

This section describes the open caveats in supervisor engine software release 6.4(18):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(18)

Note For a description of open caveats in software release 6.4(18), see the "Open Caveats in Software Release 6.4(18)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(18):

•When you enter the reset mindown command on a system with redundant Supervisor Engine IIIs, the standby supervisor engine resets with a TLB exception when the active supervisor engine resets. This issue exists in Catalyst software releases 6.4(1) through 6.4(17).

This problem is resolved in software release 6.4(18). (CSCef73416)

Open and Resolved Caveats in Software Release 6.4(17)

These sections describe open and resolved caveats in supervisor engine software release 6.4(17):

•Open Caveats in Software Release 6.4(17)

•Resolved Caveats in Software Release 6.4(17)

Open Caveats in Software Release 6.4(17)

Note For a description of caveats resolved in software release 6.4(17), see the "Resolved Caveats in Software Release 6.4(17)" section.

This section describes the open caveats in supervisor engine software release 6.4(17):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(17)

Note For a description of open caveats in software release 6.4(17), see the "Open Caveats in Software Release 6.4(17)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(17):

•If you configure Network Time Protocol (NTP) or set the system clock by entering the set time command on a Catalyst 5000 Supervisor Engine IIG or IIIG with software releases 6.4(14), 6.4(15), or 6.4(16), the onboard real time clock (RTC) device goes into an inconsistent state. The output of the show time command displays the time as "0 0000, 00:00:00 utc." You cannot recover the RTC through software, and you need to perform a return material authorization (RMA) on the supervisor engine.

Other supervisor engine versions are not affected by this problem.

This problem is resolved in software release 6.4(17). (CSCin86465)

•If VLAN 1 contains no ports and UDLD is enabled, the trunk ports in the switch go into errdisable status when you reload the switch. If UDLD is not enabled, the trunk status toggles between "trunk" and "nontrunk." Cisco Discovery Protocol (CDP) entries are not found.

Workaround: Keep at least one port in VLAN 1.

This problem is resolved in software release 6.4(17). (CSCeh65691)

Open and Resolved Caveats in Software Release 6.4(16)

These sections describe open and resolved caveats in supervisor engine software release 6.4(16):

•Open Caveats in Software Release 6.4(16)

•Resolved Caveats in Software Release 6.4(16)

Open Caveats in Software Release 6.4(16)

Note For a description of caveats resolved in software release 6.4(16), see the "Resolved Caveats in Software Release 6.4(16)" section.

This section describes the open caveats in supervisor engine software release 6.4(16):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(16)

Note For a description of open caveats in software release 6.4(16), see the "Open Caveats in Software Release 6.4(16)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(16):

•The MIB object "snmpEngineTime" does not report the correct value if the SNMP engine has been active for more than 496 days.

This problem is resolved in software release 6.4(16). (CSCeg61577)

•In software release 6.4(16), the number of TCP-established sessions has been increased from 64 to 128. (CSCeg85630)

Open and Resolved Caveats in Software Release 6.4(15)

These sections describe open and resolved caveats in supervisor engine software release 6.4(15):

•Open Caveats in Software Release 6.4(15)

•Resolved Caveats in Software Release 6.4(15)

Open Caveats in Software Release 6.4(15)

Note For a description of caveats resolved in software release 6.4(15), see the "Resolved Caveats in Software Release 6.4(15)" section.

This section describes the open caveats in supervisor engine software release 6.4(15):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(15)

Note For a description of open caveats in software release 6.4(15), see the "Open Caveats in Software Release 6.4(15)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(15):

•When you enable a SPAN session on a VLAN and reset the switch, the RSFC port might be unreachable from some modules while still reachable from some other modules.

Workaround: Configure port SPAN instead of VLAN SPAN.

This problem is resolved in software release 6.4(15). (CSCef77250)

Open and Resolved Caveats in Software Release 6.4(14)

These sections describe open and resolved caveats in supervisor engine software release 6.4(14):

•Open Caveats in Software Release 6.4(14)

•Resolved Caveats in Software Release 6.4(14)

Open Caveats in Software Release 6.4(14)

Note For a description of caveats resolved in software release 6.4(14), see the "Resolved Caveats in Software Release 6.4(14)" section.

This section describes the open caveats in supervisor engine software release 6.4(14):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(14)

Note For a description of open caveats in software release 6.4(14), see the "Open Caveats in Software Release 6.4(14)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(14):

•You can configure up to 16 MAC address filters per port (entering the set port filter command) on Catalyst 5000 family token ring modules. However, if you configure more than 8 MAC address filters per port, the output of the show config command displays only the first 8 MAC address filters.

Workaround: Enter the show port filter command to display all configured filters.

This problem is resolved in software release 6.4(14). (CSCeg23739)

•When you set the diagnostics level to bypass (set test diaglevel bypass) and then reload the switch, port security does not work as expected.

Workaround: Set the diagnostics level to minimal (set test diaglevel complete) or complete (set test diaglevel complete) and reload the switch.

This problem is resolved in software release 6.4(14). (CSCef50667)

Open and Resolved Caveats in Software Release 6.4(13)

These sections describe open and resolved caveats in supervisor engine software release 6.4(13):

•Open Caveats in Software Release 6.4(13)

•Resolved Caveats in Software Release 6.4(13)

Open Caveats in Software Release 6.4(13)

Note For a description of caveats resolved in software release 6.4(13), see the "Resolved Caveats in Software Release 6.4(13)" section.

This section describes the open caveats in supervisor engine software release 6.4(13):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(13)

Note For a description of open caveats in software release 6.4(13), see the "Open Caveats in Software Release 6.4(13)" section.

There are no resolved caveats in software release 6.4(13).

Open and Resolved Caveats in Software Release 6.4(12)

These sections describe open and resolved caveats in supervisor engine software release 6.4(12):

•Open Caveats in Software Release 6.4(12)

•Resolved Caveats in Software Release 6.4(12)

Open Caveats in Software Release 6.4(12)

Note For a description of caveats resolved in software release 6.4(12), see the "Resolved Caveats in Software Release 6.4(12)" section.

This section describes the open caveats in supervisor engine software release 6.4(12):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(12)

Note For a description of open caveats in software release 6.4(12), see the "Open Caveats in Software Release 6.4(12)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(12):

•The dot3StatsFrameTooLongs counter increases on some trunk ports. This counter should not increase on trunk ports.

This problem is resolved in software release 6.4(12). (CSCee94947)

•A system with a Supervisor Engine III G might hang or reset when you enter the show banner command from a Telnet session.

Workaround: Enter the show config command to display the banner.

This problem is resolved in software release 6.4(12). (CSCed57471)

•After a switchover, the first module/link trap for any module/link might not be sent.

This problem is resolved in software release 6.4(12). (CSCef27093)

Open and Resolved Caveats in Software Release 6.4(11)

These sections describe open and resolved caveats in supervisor engine software release 6.4(11):

•Open Caveats in Software Release 6.4(11)

•Resolved Caveats in Software Release 6.4(11)

Open Caveats in Software Release 6.4(11)

Note For a description of caveats resolved in software release 6.4(11), see the "Resolved Caveats in Software Release 6.4(11)" section.

This section describes the open caveats in supervisor engine software release 6.4(11):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

Resolved Caveats in Software Release 6.4(11)

There are no resolved caveats in software release 6.4(11).

Open and Resolved Caveats in Software Release 6.4(10)

These sections describe open and resolved caveats in supervisor engine software release 6.4(10):

•Open Caveats in Software Release 6.4(10)

•Resolved Caveats in Software Release 6.4(10)

Open Caveats in Software Release 6.4(10)

Note For a description of caveats resolved in software release 6.4(10), see the "Resolved Caveats in Software Release 6.4(10)" section.

This section describes the open caveats in supervisor engine software release 6.4(10):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(10)

Note For a description of open caveats in software release 6.4(10), see the "Open Caveats in Software Release 6.4(10)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(10):

•On a switch running a cryptographic (k9) image, if the value of sshPublicKeySize is nonzero, the SNMP_THREAD process might have a memory leak when sshPublicKeySize is polled.

This problem is resolved in software release 6.4(10). (CSCed95950)

•After accessing the switch through a Telnet session and entering the clear vlan command to clear a large number of VLANs, if the Telnet session automatically logs you out before all of the VLANs are cleared, the VLAN database might be left in an inconsistent state.

Workaround 1: Reset the switch.

Workaround 2: If you need to clear a large number of VLANs, clear it through the switch console rather than a Telnet session.

Workaround 3: If you decide to clear a large number of VLANs through a Telnet session, use the set logout 0 command, and then clear the VLANs.

This problem is resolved in software release 6.4(10). (CSCec19091)

Open and Resolved Caveats in Software Release 6.4(9)

These sections describe open and resolved caveats in supervisor engine software release 6.4(9):

•Open Caveats in Software Release 6.4(9)

•Resolved Caveats in Software Release 6.4(9)

Open Caveats in Software Release 6.4(9)

Note For a description of caveats resolved in software release 6.4(9), see the "Resolved Caveats in Software Release 6.4(9)" section.

This section describes the open caveats in supervisor engine software release 6.4(9):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(9)

Note For a description of open caveats in software release 6.4(9), see the "Open Caveats in Software Release 6.4(9)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(9):

•When you start a Telnet session to the Catalyst switch using certain Telnet clients, the Catalyst switch prompt is not displayed until you press the Enter (return) key.

Workaround: Press the Enter key to get to the Catalyst switch prompt.

This problem is resolved in software release 6.4(9). (CSCed45576)

•A Catalyst 5500 switch with a WS-X5410 module, a Catalyst 4003 switch with a Supervisor Engine I, or a Catalyst 4006 or 4503 switch with Supervisor Engine II does not send dummy multicast packets when UplinkFast operates after you enter the no shutdown command from the original root port. This condition results in lost communication because the switch does not clear the older MAC table on the root port.

This problem is resolved in software release 6.4(9). (CSCec79652)

•After performing a software upgrade, the switch might experience an exception and reset. If this problem occurs, the show log command displays the following error message:
Error Msg:mfree 2:m=0x8c994080
PID = 0 Kernel an 
This problem is resolved in software release 6.4(9). (CSCed48590)

•A Catalyst switch with the Catalyst operating system incorrectly reports an STP root change with the following message:
2003 Jun 09 11:42:28 EST -04:00 %SPANTREE-5-ROOTCHANGE:Root changed for Vlan Y: New 
root port n/m. New Root mac address is XX-XX-XX-XX-XX-XX. 
This is an information message only and should not affect the operation of your switch.

Workaround: Change the logging level on the SPANTREE facility down to level 4.

This problem is resolved in software release 6.4(9). (CSCeb78548)

•The InlineRewrite test may fail when the Layer 2 content-addressable memory (CAM) table is full.

The problem is resolved in software release 6.4(9). (CSCed57768)

Open and Resolved Caveats in Software Release 6.4(8)

These sections describe open and resolved caveats in supervisor engine software release 6.4(8):

•Open Caveats in Software Release 6.4(8)

•Resolved Caveats in Software Release 6.4(8)

Open Caveats in Software Release 6.4(8)

Note For a description of caveats resolved in software release 6.4(8), see the "Resolved Caveats in Software Release 6.4(8)" section.

This section describes the open caveats in supervisor engine software release 6.4(8):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(8)

Note For a description of open caveats in software release 6.4(8), see the "Open Caveats in Software Release 6.4(8)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(8):

•When polling ciscoMemoryPoolTable in the CISCO-MEMORY-POOL MIB, the following mandatory values are not returned:

–ciscoMemoryPoolAlternate INTEGER

–ciscoMemoryPoolValid TruthValue

This problem exists in all 6.4 software releases.

This problem is resolved in software release 6.4(8). (CSCec42170)

Open and Resolved Caveats in Software Release 6.4(7)

These sections describe open and resolved caveats in supervisor engine software release 6.4(7):

•Open Caveats in Software Release 6.4(7)

•Resolved Caveats in Software Release 6.4(7)

Open Caveats in Software Release 6.4(7)

Note For a description of caveats resolved in software release 6.4(7), see the "Resolved Caveats in Software Release 6.4(7)" section.

This section describes the open caveats in supervisor engine software release 6.4(7):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(7)

Note For a description of open caveats in software release 6.4(7), see the "Open Caveats in Software Release 6.4(7)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(7):

•When you enter the show counters mod/port command in a system with a Token Ring module (WS-X5030), the supervisor engine may reload. The mod/port value is the port on the Token Ring module.

This problem is resolved in software release 6.4(7). (CSCec38475)

Open and Resolved Caveats in Software Release 6.4(6)

These sections describe open and resolved caveats in supervisor engine software release 6.4(6):

•Open Caveats in Software Release 6.4(6)

•Resolved Caveats in Software Release 6.4(6)

Open Caveats in Software Release 6.4(6)

Note For a description of caveats resolved in software release 6.4(6), see the "Resolved Caveats in Software Release 6.4(6)" section.

This section describes the open caveats in supervisor engine software release 6.4(6):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(6)

Note For a description of open caveats in software release 6.4(6), see the "Open Caveats in Software Release 6.4(6)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(6):

•A Catalyst 5000 family switch with a group switching Ethernet module (WS-X5020) installed might experience a memory leak when an SNMP client enters the getmany command on the snmpDot3RptMgt object.

This problem is resolved in software release 6.4(6). (CSCeb72141)

Open and Resolved Caveats in Software Release 6.4(5)

These sections describe open and resolved caveats in supervisor engine software release 6.4(5):

•Open Caveats in Software Release 6.4(5)

•Resolved Caveats in Software Release 6.4(5)

Open Caveats in Software Release 6.4(5)

Note For a description of caveats resolved in software release 6.4(5), see the "Resolved Caveats in Software Release 6.4(5)" section.

This section describes the open caveats in supervisor engine software release 6.4(5):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(5)

Note For a description of open caveats in software release 6.4(5), see the "Open Caveats in Software Release 6.4(5)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(5):

•The Catalyst 5000 family switch returns only the hostname when polled for the system name:
sysName 
.1.3.6.1.2.1.1.5
The network management station (NMS) applications are expecting the switch to return the Fully Qualified Domain Name (FQDN).

Workaround: Specify the complete FQDN on the switch by entering the set system name hostname.domain command.

This problem is resolved in software release 6.4(5). (CSCeb37492)

Open and Resolved Caveats in Software Release 6.4(4a)

These sections describe open and resolved caveats in supervisor engine software release 6.4(4a):

•Open Caveats in Software Release 6.4(4a)

•Resolved Caveats in Software Release 6.4(4a)

Open Caveats in Software Release 6.4(4a)

Note For a description of caveats resolved in software release 6.4(4a), see the "Resolved Caveats in Software Release 6.4(4a)" section.

This section describes the open caveats in supervisor engine software release 6.4(4a):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(4a)

Note For a description of open caveats in software release 6.4(4a), see the "Open Caveats in Software Release 6.4(4a)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(4a):

•IGMP multicast entries are not removed from the CAM table.

This problem is resolved in software release 6.4(4a).(CSCeb34010)

Open and Resolved Caveats in Software Release 6.4(4)

These sections describe open and resolved caveats in supervisor engine software release 6.4(4):

•Open Caveats in Software Release 6.4(4)

•Resolved Caveats in Software Release 6.4(4)

Open Caveats in Software Release 6.4(4)

Note For a description of caveats resolved in software release 6.4(4), see the "Resolved Caveats in Software Release 6.4(4)" section.

This section describes the open caveats in supervisor engine software release 6.4(3):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or if an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser. (CSCdu32540)

Resolved Caveats in Software Release 6.4(4)

Note For a description of open caveats in software release 6.4(4), see the "Open Caveats in Software Release 6.4(4)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(4):

•The CISCO-STACK-MIB trap sends an invalid systemGrp. There is no workaround.

This problem is resolved in software release 6.4(4). (CSCeb04226)

•If you enter the ping -s ip_address command (where ip_address is an unreachable address), the following message is not displayed:

ping: Dest Unreachable response from <default_gateway>

This problem is seen only in software release 5.5(3) and later releases, and in software releases 6.x and 7.x.

This problem is resolved in software release 6.4(4). (CSCdx03359)

•When you configure UplinkFast and MLS on a Catalyst 5000 family switch, a flood entry in the CAM table might cause routed packets through the Route Switch Module (RSM) to fail, resulting in dropped packets.

This problem is resolved in software release 6.4(4). (CSCdz44998)

•In a Catalyst 5000 family switch with an ATM module, SNMP queries might timeout.

This problem is resolved in software release 6.4(4) and ATM software releases 12.0(26)W5(28a) and 12.1(20). (CSCea04300)

Open and Resolved Caveats in Software Release 6.4(3)

These sections describe open and resolved caveats in supervisor engine software release 6.4(3):

•Open Caveats in Software Release 6.4(3)

•Resolved Caveats in Software Release 6.4(3)

Open Caveats in Software Release 6.4(3)

Note For a description of caveats resolved in software release 6.4(3), see the "Resolved Caveats in Software Release 6.4(3)" section.

This section describes the open caveats in supervisor engine software release 6.4(3):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a differentiated services code point (DSCP) range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(3)

Note For a description of open caveats in software release 6.4(3), see the "Open Caveats in Software Release 6.4(3)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(3):

•If you configure port security on the WS-5225r or WS-5324 modules, security may be violated by an incorrect MAC address. The system will show that the MAC address was learned from the port, but a MAC address might have been learned from the network.

Workaround: Use the restrict violation action instead of the shutdown caution when you configure port security. This action will cause the incorrect MAC address to be restricted and ignored.

This problem is resolved in software release 6.4(3). (CSCdy81856)

•In certain hardware configurations (for example, one WS-X5225 module and two WS-X5012A modules), the uplink ports on the standby Supervisor Engine III stay in standby mode and fail to enable.

This problem is resolved in software release 6.4(3). (CSCdx66947)

•If a failover occurs on a Catalyst 5500 switch with redundant Supervisor Engine IIIs with uplink modules, the EARL tests are not performed and are marked as unknown (U).

This problem is resolved in software release 6.4(3). (CSCdy03366)

•On a Catalyst 5500 switch with a Supervisor Engine III G and a Gigabit Ethernet switching module (WS-X5403), the ufastMcast (UplinkFast) process may display an artificially high CPU load (approximately 80 percent) when you enter the show proc cpu command.

Workaround: Disable and reenable UplinkFast by entering the set spantree uplinkfast disable command followed by the set spantree uplinkfast enable command.

This problem is resolved in software release 6.4(3). (CSCea18267)

Open and Resolved Caveats in Software Release 6.4(2)

These sections describe open and resolved caveats in supervisor engine software release 6.4(2):

•Open Caveats in Software Release 6.4(2)

•Resolved Caveats in Software Release 6.4(2)

Open Caveats in Software Release 6.4(2)

Note For a description of caveats resolved in software release 6.4(2), see the "Resolved Caveats in Software Release 6.4(2)" section.

This section describes the open caveats in supervisor engine software release 6.4(2):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(2)

Note For a description of open caveats in software release 6.4(2), see the "Open Caveats in Software Release 6.4(2)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(2):

•If you launch the Catalyst Web Interface (CWI) by using Internet Explorer web browser or Netscape web browser, a Catalyst 5000 family switch that is running the 6.3(10) or 6.4(1) CiscoView image may reload.

Workaround: Use the standalone CiscoView image to manage the switch that is running these CiscoView images.

This problem is resolved in software release 6.4(2). (CSCdu46560, CSCdz86825)

•When you enable broadcast suppression on the three-port Gigabit Ethernet switching module (WS-X5403), broadcast suppression fails when the port is disabled then reenabled.

This problem is resolved in software release 6.4(2). (CSCdw67460)

•In software release 6.3, if you have a supervisor engine in slot 1 or slot 2, the show counters command will not work for ports 17 through 22 (for example, show counters 1/17).

This problem is resolved in software release 6.4(2). (CSCdz48414)

•If a connected ATM module runs out of memory, the switch may reload in the CmpOID function.

This problem is resolved in software release 6.4(2). (CSCdz50307)

•The system may reload when MALLOC failures and excessive SNMP processing occurs.

This problem is resolved in software release 6.4(2). (CSCdz59604)

Open and Resolved Caveats in Software Release 6.4(1)

These sections describe open and resolved caveats in supervisor engine software release 6.4(1):

•Open Caveats in Software Release 6.4(1)

•Resolved Caveats in Software Release 6.4(1)

Open Caveats in Software Release 6.4(1)

Note For a description of caveats resolved in software release 6.4(1), see the "Resolved Caveats in Software Release 6.4(1)" section.

This section describes the open caveats in supervisor engine software release 6.4(1):

•If you launch the Catalyst Web Interface (CWI) by using Internet Explorer web browser or Netscape web browser, a Catalyst 5000 family switch that is running the 6.3(10) or 6.4(1) CiscoView image may reload.

Workaround: Use the standalone CiscoView image to manage the switch that is running these CiscoView images. (CSCdu46560, CSCdz86825)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CiscoView image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.4(1)

Note For a description of open caveats in software release 6.4(1), see the "Open Caveats in Software Release 6.4(1)" section.

This section describes the resolved caveats in supervisor engine software release 6.4(1):

•The content-addressable memory (CAM) table of a Catalyst 5000 family switch with a LANE module sometimes points to a virtual connection that does not exist.

Workaround: Clear the CAM table.

This problem is resolved in software release 6.4(1). (CSCdw62710)

•On a Catalyst 5500 with a Supervisor Engine III (WS-X5530), you can forward all broadcast traffic on a switch to one specific port by configuring port security on a specific port and then sending an Ethernet frame to that port with a source MAC address of FFFF.FFFF.FFFF. The switch forwards all broadcast traffic to one port, instead of to all ports on the switch, which affects services such as dynamic host configuration protocol (DHCP) and address resolution protocol (ARP).

Workaround: Disable port security.

This problem is resolved in software release 6.4(1). (CSCdz09749)

Open and Resolved Caveats in Software Release 6.3(10)

These sections describe open and resolved caveats in supervisor engine software release 6.3(10):

•Open Caveats in Software Release 6.3(10)

•Resolved Caveats in Software Release 6.3(10)

Open Caveats in Software Release 6.3(10)

Note For a description of caveats resolved in software release 6.3(10), see the "Resolved Caveats in Software Release 6.3(10)" section.

This section describes the open caveats in supervisor engine software release 6.3(10):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you launch the Catalyst Web Interface (CWI) by using Internet Explorer web browser or Netscape web browser, a Catalyst 5000 family switch that is running the 6.3(10) or 6.4(1) CiscoView image may reload.

Workaround: Use the standalone CiscoView image to manage the switch that is running these CiscoView images. (CSCdz86825)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.3(10)

Note For a description of open caveats in software release 6.3(10), see the "Open Caveats in Software Release 6.3(10)" section.

There are no resolved caveats in supervisor engine software release 6.3(10).

Open and Resolved Caveats in Software Release 6.3(9)

These sections describe open and resolved caveats in supervisor engine software release 6.3(9):

•Open Caveats in Software Release 6.3(9)

•Resolved Caveats in Software Release 6.3(9)

Open Caveats in Software Release 6.3(9)

Note For a description of caveats resolved in software release 6.3(9), see the "Resolved Caveats in Software Release 6.3(9)" section.

This section describes the open caveats in supervisor engine software release 6.3(9):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.3(9)

Note For a description of open caveats in software release 6.3(9), see the "Open Caveats in Software Release 6.3(9)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(9):

•During a core dump, the process may prematurely terminate, which causes the switch to reset and the core dump file to be incomplete.

This problem is resolved in software release 6.3(9). (CSCdx18083)

•When you poll objects in the CISCO-MEMORY-POOL-MIB, high CPU utilization occurs in systems with a WS-X5540 supervisor engine.

This problem is resolved in software release 6.3(9). (CSCdx16304)

Open and Resolved Caveats in Software Release 6.3(8)

These sections describe open and resolved caveats in supervisor engine software release 6.3(8):

•Open Caveats in Software Release 6.3(8)

•Resolved Caveats in Software Release 6.3(8)

Open Caveats in Software Release 6.3(8)

Note For a description of caveats resolved in software release 6.3(8), see the "Resolved Caveats in Software Release 6.3(8)" section.

This section describes the open caveats in supervisor engine software release 6.3(8):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a Common Open Policy Service (COPS) QoS Policy Manager (QPM) server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, you will not know that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CiscoView image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(8)

Note For a description of open caveats in software release 6.3(8), see the "Open Caveats in Software Release 6.3(8)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(8):

•In rare circumstances, if you terminate a ping process by entering ^C (Ctrl-C), the process is terminated but the memory allocated to the process is not released properly.

This problem is resolved in software release 6.3(8). (CSCdx40797)

•When you enter the show top command for an FDDI module, inconsistent utilization results are displayed (Uti %).

This problem is resolved in software release 6.3(8). (CSCdx55791)

•On systems with a Supervisor Engine III (WS-X5530) running 5.5(13a), the show port command or the show counters command reports FCS errors. However, the dot3StatFCSError SNMP object reports zero FCS errors.

This problem is resolved in software release 6.3(8). (CSCdx88030)

Open and Resolved Caveats in Software Release 6.3(7)

These sections describe open and resolved caveats in supervisor engine software release 6.3(7):

•Open Caveats in Software Release 6.3(7)

•Resolved Caveats in Software Release 6.3(7)

Open Caveats in Software Release 6.3(7)

Note For a description of caveats resolved in software release 6.3(7), see the "Resolved Caveats in Software Release 6.3(7)" section.

This section describes the open caveats in supervisor engine software release 6.3(7):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and Java Run Time Environment (JRE) versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

•In rare circumstances, if you terminate a ping process by entering ^C (Ctrl-C), the process is terminated but the memory allocated to the process is not released properly. (CSCdx40797)

Resolved Caveats in Software Release 6.3(7)

Note For a description of open caveats in software release 6.3(7), see the "Open Caveats in Software Release 6.3(7)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(7):

•With SNMP, the switch displays the following error message when modifying the vlanTrunkPortTable:
RESOURCE_UNAVAILABLE_ERROR
This problem exists only in software release 6.3(6).

This problem is resolved in software release 6.3(7). (CSCdx23585)

•In rare circumstances, a designated port might be suspended in the spanning tree listening state and still be transmitting BPDUs. This situation does not introduce problems with spanning tree convergence or cause loops.

This problem is resolved in software release 6.3(7). (CSCdv89566)

•When making a Telnet connection to a switch configured with authentication, authorization, and accounting (AAA) through Shiva Access Manager, the switch sets the TACACS privilege level to 15. Authentication fails if users have a privilege level lower than 15.

Workaround: Configure Shiva Access Manager users to receive privilege level 15.

This problem is resolved in software release 6.3(7). (CSCdx08395)

•In rare circumstances, if you terminate a DNS lookup process by entering ^C (Ctrl-C), the process is terminated but the memory allocated to the process is not released properly.

This problem is resolved in software release 6.3(7). (CSCdx40481)

•On a Catalyst 5000 family switch with IGMP and CGMP disabled, the switch may still process, and respond to, MMLS messages from a router on which MLS Multicast is enabled if that router has added the switch to its list of known MLS Multicast switches. This can cause disruption of traffic that would normally be routed by the external router.

Workaround: Disable MMLS on the external router when IGMP or CGMP is disabled on the Catalyst 5000.

This problem is resolved in software release 6.3(7). CSCdx14758

Open and Resolved Caveats in Software Release 6.3(6)

These sections describe open and resolved caveats in supervisor engine software release 6.3(6):

•Open Caveats in Software Release 6.3(6)

•Resolved Caveats in Software Release 6.3(6)

Open Caveats in Software Release 6.3(6)

Note For a description of caveats resolved in software release 6.3(6), see the "Resolved Caveats in Software Release 6.3(6)" section.

This section describes the open caveats in supervisor engine software release 6.3(6):

•With SNMP, the switch returns "RESOURCE_UNAVAILABLE_ERROR" when modifying the vlanTrunkPortTable. This problem exists only in software release 6.3(6). (CSCdx23585)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(6)

Note For a description of open caveats in software release 6.3(6), see the "Open Caveats in Software Release 6.3(6)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(6):

•Operating systems, such as Windows XP, will attempt authentication by sending frames to the Authenticator PAE on the destination multicast address 01-80-c2-00-00-0f and 01-80-c2-00-00-03. On Catalyst 5000 family switches with EARL1, EARL1+, EARL1++, or EARL1.1, these frames will be forwarded on all ports including spanning tree blocking ports. Because these frames are forwarded on blocked ports, the network will experience a Layer 2 multicast storm.

Workaround 1: Enter the following commands to configure a permanent CAM entry for 01-80-c2-00-00-0f and 01-80-c2-00-00-03 to be directed out an unused port:

–set cam permanent 01-80-c2-00-00-0f mod/port

–set cam permanent 01-80-c2-00-00-03 mod/port

Workaround 2: Follow this procedure to configure Windows XP to not send these frames:

a. Click on the associated Local Area Connection under Network Connections.

b. Click on the Authentication Tab.

c. Uncheck "Network Access Control using IEEE 802.1x."

For additional information, see the following URL:

http://www.cisco.com/warp/public/707/cat5k-8021x-vuln-pub.shtml

This problem is resolved in software release 6.3(6). (CSCdt62732)

•Entering a show mls entry command immediately after the system boots up may cause a system reset. This problem is resolved in software release 6.3(6). (CSCdu18119)

•In rare circumstances, the output from the show mac mod/port command and the output from an SNMP query will report inconsistent values for the "In-Discards" field.

This problem is resolved in software release 6.3(6). (CSCdu30380)

•If a duplex mismatch occurs on an ISL trunk into a Catalyst 5000 family switch, you will see swBusCRCErrorDrop errors on all ports, and you will see RxInnerCRCErrorDrop errors on ports with the duplex mismatch. This mismatch results in dropped traffic between buses.

This problem is resolved in software release 6.3(6). (CSCdw11398)

•On Catalyst 5500 series switches, Gigabit Ethernet autonegotiation is broken on the Gigabit Ethernet uplink module (WS-U5534) in supervisor engine software releases 4.5(11), 4.5(12), and 4.5(13). Autonegotiation fails only if the other end of the link is also connected to a WS-U5534 uplink module. There is no problem if the other end of the link is connected to another Gigabit Ethernet module such as the 3- or 9-port modules.

Turning off autonegotiation to avoid the problem is not recommended because this can lead to spanning-tree loops if you have a unidirectional link. The only workaround is to connect a WS-U5534 uplink module to a different module (not the WS-U5534 uplink module).

This problem is resolved in software release 6.3(6). (CSCdw21589)

•When operating at 10 MB, a disabled port on a WS-X5224, WS-X5012, WS-X5012A, or WS-X5014 module will continue to transmit link pulses. This causes the link-partner port to stay up. There is no workaround. The problem exists in 4.x, 5.x, and 6.x releases of the Catalyst operating software. This problem is resolved in software release 6.3(6). (CSCdw25922)

•Polling objects in the CISCO-MEMORY-POOL-MIB causes high CPU utilization in systems with a WS-X5540 supervisor engine. This problem is resolved in software release 6.3(6). (CSCdx16304)

•In systems running software release 5.5.7 with a WS-U5533 uplink module on the supervisor engine, packet buffer tests might fail if diagnostics are set to be bypassed and ports are disabled. This problem is resolved in software release 6.3(6). (CSCdw95036)

•Deleting an existing snmpVacmAccessEntry produces this message:
Entry not found
This problem is resolved in software release 6.3(6). (CSCdw36075)

•If a port is configured as a nontrunking port and it receives an ISL-encapsulated packet, the port will not be able to remove the ISL header. The default system behavior in this instance is to install ISL system CAM entries and drop the ISL packets. These entries are installed for every active VLAN in the switch. In rare circumstances, this default behavior might cause hash collisions for real MAC addresses due to the amount of system entries being used up. To prevent such collisions, use the new set feature no-isl-entries enable command to disable the creation of these ISL system entries.

Note Because entering the set feature no-isl-entries enable command causes received ISL packets to be flooded on the given VLAN, the command should not be entered on switches that are connected to other switches.

This problem is resolved in software release 6.3(6). (CSCdw86312)

•During initialization of a WS-X5239 module with a non-default configuration, the 802.1x port control parameter is incorrectly set as "none." This incorrect setting creates a condition where the port status shows the port as connected, but the spanning tree status of the port shows the port as not connected. This problem is resolved in software release 6.3(6). (CSCdw65680)

•Supervisor Engine IIIG (WS-X5550) does not populate the sysTrafficMeterTable for all switching buses.

This problem is resolved in software release 6.3(6). (CSCdw66441)

Open and Resolved Caveats in Software Release 6.3(5)

These sections describe open and resolved caveats in supervisor engine software release 6.3(5):

•Open Caveats in Software Release 6.3(5)

•Resolved Caveats in Software Release 6.3(5)

Open Caveats in Software Release 6.3(5)

Note For a description of caveats resolved in software release 6.3(5), see the "Resolved Caveats in Software Release 6.3(5)" section.

This section describes the open caveats in supervisor engine software release 6.3(5):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(5)

Note For a description of open caveats in software release 6.3(5), see the "Open Caveats in Software Release 6.3(5)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(5):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.3(5). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.3(4a)

These sections describe open and resolved caveats in supervisor engine software release 6.3(4a):

•Open Caveats in Software Release 6.3(4a)

•Resolved Caveats in Software Release 6.3(4a)

Open Caveats in Software Release 6.3(4a)

Note For a description of caveats resolved in software release 6.3(4a), see the "Resolved Caveats in Software Release 6.3(4a)" section.

This section describes the open caveats in supervisor engine software release 6.3(4a):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

Resolved Caveats in Software Release 6.3(4a)

Note For a description of open caveats in software release 6.3(4a), see the "Open Caveats in Software Release 6.3(4a)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(4a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.3(4a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.3(4)

These sections describe open and resolved caveats in supervisor engine software release 6.3(4):

•Open Caveats in Software Release 6.3(4)

•Resolved Caveats in Software Release 6.3(4)

Open Caveats in Software Release 6.3(4)

Note For a description of caveats resolved in software release 6.3(4), see the "Resolved Caveats in Software Release 6.3(4)" section.

This section describes the open caveats in supervisor engine software release 6.3(4):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser. (CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies that do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(4)

Note For a description of open caveats in software release 6.3(4), see the "Open Caveats in Software Release 6.3(4)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(4):

•Catalyst 5000 modules may fail to come online after a switch reset with a Supervisor Engine IIG (WS-X5540) in a nonredundant chassis. This problem exists in 5.5(x) and 6.1(x) releases of the Catalyst operating software. The problem usually occurs with WS-X5213(A) modules running FW versions earlier than 3.1(1). After the switch restarts, you will need to reinsert the module. This problem is resolved in software release 6.3(4). (CSCdv00286)

•On a Catalyst 5000 family switch with a Supervisor Engine III, the MIB OID for sysTraffic and sysTrafficPeak show different values than the output of the show system command.

This problem is resolved in software release 6.3(4). (CSCdv60866)

•On a Catalyst 5000 family switch, IGMP is enabled by default when you clear the configuration and reset the switch. IGMP cannot be disabled, and CGMP cannot be enabled.

This problem is resolved in software release 6.3(4). (CSCdw00254)

•When accessing the switch through an HTTP interface, the switch might reset with a TLB exception. This problem is resolved in software release 6.3(4). (CSCdw02887)

Open and Resolved Caveats in Software Release 6.3(3a)

These sections describe open and resolved caveats in supervisor engine software release 6.3(3a):

•Open Caveats in Software Release 6.3(3a)

•Resolved Caveats in Software Release 6.3(3a)

Open Caveats in Software Release 6.3(3a)

Note For a description of caveats resolved in software release 6.3(3a), see the "Resolved Caveats in Software Release 6.3(3a)" section.

This section describes the open caveats in supervisor engine software release 6.3(3a):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(3a)

Note For a description of open caveats in software release 6.3(3a), see the "Open Caveats in Software Release 6.3(3a)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(3a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.3(3a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.3(3)

These sections describe open and resolved caveats in supervisor engine software release 6.3(3):

•Open Caveats in Software Release 6.3(3)

•Resolved Caveats in Software Release 6.3(3)

Open Caveats in Software Release 6.3(3)

Note For a description of caveats resolved in software release 6.3(3), see the "Resolved Caveats in Software Release 6.3(3)" section.

This section describes the open caveats in supervisor engine software release 6.3(3):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(3)

Note For a description of open caveats in software release 6.3(3), see the "Open Caveats in Software Release 6.3(3)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(3):

•After a software upgrade from release 5.4(3) to 5.5(7), the uplink ports on the supervisor engine (WS-X5530) go into failed state. Reloading the switch corrects this problem. This problem is resolved in software release 6.3(3). (CSCdv06726)

•This problem might occur when you Telnet into the switch and are prompted for a password. In software releases prior to 6.x.x, if you press the Enter key three times without entering a password, the connection is closed and the prompt returns to the device where the Telnet session was initiated. In version 6.x.x, the prompt continues to reappear, regardless of how many times you press the Enter key. This problem is resolved in software release 6.3(3). (CSCdv21334)

•The switch might experience a memory leak if TACACS accounting is enabled and multiple Telnet sessions are established (concurrently or nonconcurrently). The memory leak could lead to a system reset or the switch could become unreachable.

Workaround: Disable TACACS accounting and then reset the switch to free up the memory buffers. This problem is resolved in software release 6.3(3). (CSCdv38306)

•The switch might reset because of a rare error condition in the FCP task function. This problem is resolved in software release 6.3(3). (CSCdv51142)

•The switch might be unreachable on the management VLAN and might not appear in the show cdp neighbors command output, even when user traffic is normal. In this situation, the switch displays the "Run out of system memory, screen scrolling disabled" message. This problem is resolved in software release 6.3(3). (CSCdu25416)

Open and Resolved Caveats in Software Release 6.3(2a)

These sections describe open and resolved caveats in supervisor engine software release 6.3(2a):

•Open Caveats in Software Release 6.3(2a)

•Resolved Caveats in Software Release 6.3(2a)

Open Caveats in Software Release 6.3(2a)

Note For a description of caveats resolved in software release 6.3(2a), see the "Resolved Caveats in Software Release 6.3(2a)" section.

This section describes the open caveats in supervisor engine software release 6.3(2a):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(2a)

Note For a description of open caveats in software release 6.3(2a), see the "Open Caveats in Software Release 6.3(2a)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(2a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.3(2a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.3(2)

These sections describe open and resolved caveats in supervisor engine software release 6.3(2):

•Open Caveats in Software Release 6.3(2)

•Resolved Caveats in Software Release 6.3(2)

Open Caveats in Software Release 6.3(2)

Note For a description of caveats resolved in software release 6.3(2), see the "Resolved Caveats in Software Release 6.3(2)" section.

This section describes the open caveats in supervisor engine software release 6.3(2):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(2)

Note For a description of open caveats in software release 6.3(2), see the "Open Caveats in Software Release 6.3(2)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(2):

•Under rare conditions, a Catalyst 5000 family switch running software release 6.1.x and higher might experience memory corruption and a system reset if you clear the existing SSH keys while generating a new key using the set crypto key rsa bit force command. This problem is resolved in software release 6.3(2). (CSCdv47234)

•When a port is configured as dynamic, it is not assigned a VLAN from the VMPS server. This problem occurs only if a port is first configured to be dynamic, next changed to static, then again changed to dynamic. This problem is resolved in software release 6.3(2). (CSCdv34403)

•Under extremely rare conditions, when shortcut entries are programmed in the FIB or MET table, an error, such as a full MET table or a missing Layer 2 entry, might cause the switch to suddenly reset. This problem is resolved in software release 6.3(2). (CSCdu23126)

•Under rare conditions, in systems with a Supervisor Engine II or III G, the ATM module (WS-X5156, WS-X5157, WS-X5158, WS-X5167) might fail to come online after a switchover from the active supervisor engine to the standby supervisor engine.

Workaround: Reset the ATM module by doing one of the following:

–Remove and reinsert the ATM module in the chasis.

–Perform another switchover on the supervisor engines, if both are operational.

This problem is resolved in software release 6.3(2). (CSCdu16999)

•If you configure more than one default gateway, the default gateway might change from the primary to the secondary and back without obvious valid reason. This problem is resolved in software release 6.3(2). (CSCdt73765)

•A BUS error might occur when spanning tree receives a BPDU of abnormal size and is disabled for the VLAN on which the BPDU was received. This problem is resolved in software release 6.3(2). (CSCdu69958)

•You might not be able to include spaces in the "community_string" when using the following CLI command:set snmp community access_type community_string. This problem is resolved in software release 6.3(2). (CSCdv08254)

•A port in PAgP non-silent mode may behave as if in PAgP silent mode if the port has been connected to a non-silent partner. Therefore, the port may be posted to spanning tree after reset and could cause channel disturbance. This problem is resolved in software release 6.3(2). (CSCdu85834)

Open and Resolved Caveats in Software Release 6.3(1a)

These sections describe open and resolved caveats in supervisor engine software release 6.3(1a):

•Open Caveats in Software Release 6.3(1a)

•Resolved Caveats in Software Release 6.3(1a)

Open Caveats in Software Release 6.3(1a)

Note For a description of caveats resolved in software release 6.3(1a), see the "Resolved Caveats in Software Release 6.3(1a)" section.

This section describes the open caveats in supervisor engine software release 6.3(1a):

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(1a)

Note For a description of open caveats in software release 6.3(1a), see the "Open Caveats in Software Release 6.3(1a)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(1a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.3(1a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.3(1)

These sections describe open and resolved caveats in supervisor engine software release 6.3(1):

•Open Caveats in Software Release 6.3(1)

•Resolved Caveats in Software Release 6.3(1)

Open Caveats in Software Release 6.3(1)

Note For a description of caveats resolved in software release 6.3(1), see the "Resolved Caveats in Software Release 6.3(1)" section.

This section describes the open caveats in supervisor engine software release 6.3(1):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.3(1)

Note For a description of open caveats in software release 6.3(1), see the "Open Caveats in Software Release 6.3(1)" section.

This section describes the resolved caveats in supervisor engine software release 6.3(1):

•After restarting an NT server that has a Compaq NC3123 Fast Ethernet NIC connected to a port on a 10/100-Mbps Fast Ethernet switching module (WS-X5225R), the port of the WS-X5225R may stop sending or receiving frames.

Workaround: The following workarounds solve the problem:

–Enter the set port disable mod/port command followed by set port enable mod/port command.

–Remove and insert the cable from the WS-X5225R port or NIC.

–Power down and restart the NT server.

This problem is resolved in software release 6.3(1). (CSCdt40099)

•On a Supervisor Engine II (WS-X5506), the in-band (sc0) interface reports a large number of MIB II ifInErrors, which will increase continuously.

This problem is resolved in software release 6.3(1). (CSCdt91434)

•When the ifOperStatus value for the port changes (the port is enabled and disabled, or the link is brought up and down), the ifLastChange value for the port does not change.

This problem is resolved in software release 6.3(1). (CSCdt69418)

•The Catalyst 5000 family switch may pause indefinitely after the 20 MB Viking Flash PC (PCMCIA) card is hotswapped numerous times (approximately 20).

This problem is resolved in software release 6.3(1). (CSCdu23412)

•After a Spanning Tree topology change, CAM aging time will remain at a short aging time (5 to 15 seconds). This problem occurs on VLANs with forward delay set at a value less than 5.

Workaround: Set the forward delay to 15 on the root switch.

This problem is resolved in software release 6.3(1). (CSCdt78700)

•If you include a control character, such as ^C, in a comment line of a configuration file causes the commands following the comment line to be ignored when the configuration file is copied to the running configuration. This problem occurs with all 6.x software releases prior to 6.3(1).

This problem is resolved in software release 6.3(1). (CSCdu58728)

•Under rare circumstances, the RSFC (module 15) will not come up on a Supervisor Engine III G running software release 5.5.5 through 6.1.2. The following error message will appear on the supervisor console:
RSFC (mod 15, slot 1) error called from 1050c408 err 5
RSFC (mod 15, slot 1) failed, waiting for reset
When you enter the show module command, no status for the RSFC is displayed. All the logical VLAN interfaces in RSFC will be down.

This problem is resolved in software release 6.3(1). (CSCdt92255)

•Authentication protocols (TACACS+, RADIUS, Kerberos) uses a global character array to store the user input (such as passwords). Because the buffer is global, it is shared by all console and Telnet sessions; therefore, it may contain input from multiple Telnet sessions, which might cause incorrect password input for authentication.

This problem is resolved in software release 6.3(1). (CSCdu35551)

•User traffic may not get through active ports in a system with a Supervisor Engine II while a packet buffer test is running.

This problem is resolved in software release 6.3(1). (CSCdu21524)

•Running an on-demand packet buffer test on enabled ports may cause administrative protocol packets to be lost, resulting in network instability. Users are now required to disable the targeted port(s) before running an on-demand packet buffer test. Background testing behavior may still be done on enabled ports.

This problem is resolved in software release 6.3(1). (CSCdu22986)

•The supervisor engine might reset with an exception in ModReset Prcs if you reset the ATM LANE integration module (WS-X5165) which is running 12.1(7.5)E on a Catalyst 5500 switch running the 6.2(2) image with SSH (cat5000 supgk9.6-2-2.bin) with a redundant Supervisor Engine III G

This problem is resolved in software release 6.3(1). (CSCdu36161)

•A Catalyst 5000 with Supervisor Engine III running 4.5(8) or 5.5(6) with CGMP configured will not install a static CAM entry for a multicast receiver on the other end of a port channel.

Workaround: Enable IGMP instead of CGMP on the core switch.

This problem is resolved in software release 6.3(1). (CSCdu05568)

•You may lose the DLSW session when you enable SPAN on two ports across two Token Ring modules on a Catalyst 5500.

This problem is resolved in software release 6.3(1). (CSCds76492)

Open and Resolved Caveats in Software Release 6.2(3a)

These sections describe open and resolved caveats in supervisor engine software release 6.2(3a):

•Open Caveats in Software Release 6.2(3a)

•Resolved Caveats in Software Release 6.2(3a)

Open Caveats in Software Release 6.2(3a)

Note For a description of caveats resolved in software release 6.2(3a), see the "Resolved Caveats in Software Release 6.2(3a)" section.

This section describes the open caveats in supervisor engine software release 6.2(3a):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.2(3a)

Note For a description of open caveats in software release 6.2(3a), see the "Open Caveats in Software Release 6.2(3a)" section.

This section describes the resolved caveats in supervisor engine software release 6.2(3a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.2(3a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.2(2a)

These sections describe open and resolved caveats in supervisor engine software release 6.2(2a):

•Open Caveats in Software Release 6.2(2a)

•Open Caveats in Software Release 6.2(2a)

Open Caveats in Software Release 6.2(2a)

Note For a description of caveats resolved in software release 6.2(2a), see the "Resolved Caveats in Software Release 6.2(2a)" section.

This section describes the open caveats in supervisor engine software release 6.2(2a):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.2(2a)

Note For a description of open caveats in software release 6.2(2a), see the "Open Caveats in Software Release 6.2(2)" section.

This section describes the resolved caveats in supervisor engine software release 6.2(2a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.2(2a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.2(2)

These sections describe open and resolved caveats in supervisor engine software release 6.2(2):

•Open Caveats in Software Release 6.2(2)

•Resolved Caveats in Software Release 6.2(2)

Open Caveats in Software Release 6.2(2)

Note For a description of caveats resolved in software release 6.2(2), see the "Resolved Caveats in Software Release 6.2(2)" section.

This section describes the open caveats in supervisor engine software release 6.2(2):

•If you cannot launch the CV image on Solaris and Netscape clients, or an access control error is generated when you launch the CV image, clear the browser cache or make sure the plug-in and JRE versions match. To make the JRE and plug-in versions match, follow this procedure:

a. Open the Java plug-in Control Panel located at java_plugin_install_directory/j2pi/ ControlPanel (the standard java_plugin_install_directory is /opt/NSCPcom/).

b. Select the Advanced tab, then select the Java Run Time Environment option, and specify "Use Java Plug-in Default."

c. Restart the browser.

(CSCdu32540)

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.2(2)

Note For a description of open caveats in software release 6.2(2), see the "Open Caveats in Software Release 6.2(2)" section.

This section describes the resolved caveats in supervisor engine software release 6.2(2):

•The embedded CiscoView cannot be launched after May 11, 2001.

This problem is resolved in software release 6.2(2). (CSCdu25881)

•Opening configuration dialogs after resizing CiscoView browser window on a Solaris/Netscape Communicator client with Java plugin 1.3.0 causes a Java IllegalComponentStateException error. Workaround: Open the same dialog again.

This problem is resolved in software release 6.2(2). (CSCdu32555)

•Entering the show flash or show tech-support command in a Catalyst 5500 switch with Supervisor Engine II G or III G will fail to yield the CPU on the supervisor engine to other running processes. These commands can adversely affect processes that require periodic "hellos." Processes similar to spanning tree may see spanning tree reconfigured and reconverged, while unidirectional link detection (UDLD) may incorrectly disable a port.

Workaround: Do not issue the show flash or show tech-support commands from the CLI.

This problem is resolved in software release 6.2(2). (CSCdt94706)

•In a configuration with a redundant Supervisor Engine III with 10/100 uplink modules, the redundant supervisor engine does not poll the link status of the uplink ports fast enough. The active supervisor engine might not detect a link up or down on the redundant supervisor engine.

This problem is resolved in software release 6.2(2). (CSCdu08203)

•While running scheduled packet buffer testing on a Catalyst 5500 series switch with a Supervisor Engine II, the packet buffer testing may inaccurately place a supervisor engine uplink port in a faulty status. These packet buffers are not faulty.

This problem is resolved in software release 6.2(2). (CSCdu18288)

•The set option packetbuffer command is ignored. Ports are always set to "faulty" when a packet buffer test fails.

This problem is resolved in software release 6.2(2). (CSCdu19172)

•The value of dot1dTpPortInDiscards object contains same value of object ifInDiscards for a bridge port.

This problem is resolved in software release 6.2(2). (CSCdt71890)

•When you clear a misconfiguration on the non-root switch of a trunk channel, the hello timer does not restart on the root switch of the trunk channel.

This problem is resolved in software release 6.2(2). (CSCdu08407)

•When an ISL trunk port is connected to an access port and QOS is enabled on the switch that has the ISL trunk, the ISL header sets the USER bits in the DA. Currently, the supervisor engine drops only the packets with user bits set to 0 and 1 and forwards the packets with other bits set to the access VLAN of the non-trunk port. The forwarded packets do not go through blocked ports.

This problem is resolved in software release 6.2(2). (CSCdu10858)

•The community string indexing is broken in software release 6.2(1) for indices 0 and 4096. When you poll these indices with ro_community@0 or ro_community@4096 from your workstation SNMP application, the switch times out and does not respond. This also causes the user tracking to discover end stations only in VLAN 1 on the affected switches.

This problem is resolved in software release 6.2(2). (CSCdu18790)

Open and Resolved Caveats in Software Release 6.2(1a)

These sections describe open and resolved caveats in supervisor engine software release 6.2(1a):

•Open Caveats in Software Release 6.2(1a)

•Resolved Caveats in Software Release 6.2(1a)

Open Caveats in Software Release 6.2(1a)

Note For a description of caveats resolved in software release 6.2(1a), see the "Resolved Caveats in Software Release 6.2(1a)" section.

This section describes the open caveats in supervisor engine software release 6.2(1a):

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.2(1a)

Note For a description of open caveats in software release 6.2(1a), see the "Open Caveats in Software Release 6.2(1a)" section.

This section describes the resolved caveats in supervisor engine software release 6.2(1a):

•An error can occur with management protocol processing. Please use the following URL for further information:

http://www.cisco.com/pcgi-bin/bugtool/onebug.pl?bugid=CSCdw67458

This problem is resolved in software release 6.2(1a). (CSCdw67458)

Open and Resolved Caveats in Software Release 6.2(1)

These sections describe open and resolved caveats in supervisor engine software release 6.2(1):

•Open Caveats in Software Release 6.2(1)

•Resolved Caveats in Software Release 6.2(1)

Open Caveats in Software Release 6.2(1)

Note For a description of caveats resolved in software release 6.2(1), see the "Resolved Caveats in Software Release 6.2(1)" section.

This section describes the open caveats in supervisor engine software release 6.2(1):

•If you download a COPS policy that contains a DSCP range to a Catalyst 5000 family switch, the COPS policy will fail to apply, and the following error message is displayed:
%COPS-3-APPLY_CAT5K_FAIL_DSCPRANGE: Applying COPS policy failed since DSCP policy 
range not set to full range 
Catalyst 5000 family switches do not support policies do not contain a full DSCP range. (CSCdr23429)

•The Catalyst 5000 family switches do not support nonzero WRED minimum values. If a COPS QPM server sends a COPS policy with a nonzero WRED minimum value, an error report is not returned to the COPS server. As a result, the user has no indication that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•The clear log command does not clear the exception log for the Network Analysis Module (WS-X5380). (CSCdm32798)

Resolved Caveats in Software Release 6.2(1)

Note For a description of open caveats in software release 6.2(1), see the "Open Caveats in Software Release 6.2(1)" section.

This section describes the resolved caveats in supervisor engine software release 6.2(1):

•The show spanningtree summary command displays 0 values in all fields for all Token Ring VLANs between 700 and 850.

This problem is resolved in software release 6.2(1). (CSCdp02146)

•

Hierarchical Navigation

Cisco Catalyst 5000 Series Switches

Release Notes for Catalyst 5000 Family Software Release 6.x

Downloads

Table Of Contents

Release Notes for Catalyst 5000 Family Software Release 6.x

Contents

Release 6.x Memory Requirements

Release 6.x Software Upgrade Path

Release 6.x Supervisor Engine Support Matrix

Supervisor Engine Redundancy

Product and Software Version Support Matrix

Release 6.x Orderable Software Images

New Features for Supervisor Engine Software Release 6.4

New Features for Supervisor Engine Software Release 6.3

New Features for Supervisor Engine Software Release 6.2

New Features for Supervisor Engine Software Release 6.1

Open and Resolved Caveats in Software Release 6.4(23a)

Open Caveats in Software Release 6.4(23a)

Resolved Caveats in Software Release 6.4(23a)

Open and Resolved Caveats in Software Release 6.4(23)

Open Caveats in Software Release 6.4(23)

Resolved Caveats in Software Release 6.4(23)

Open and Resolved Caveats in Software Release 6.4(22)

Open Caveats in Software Release 6.4(22)

Resolved Caveats in Software Release 6.4(22)

Open and Resolved Caveats in Software Release 6.4(21)

Open Caveats in Software Release 6.4(21)

Resolved Caveats in Software Release 6.4(21)

Open and Resolved Caveats in Software Release 6.4(20)

Open Caveats in Software Release 6.4(20)

Resolved Caveats in Software Release 6.4(20)

Open and Resolved Caveats in Software Release 6.4(19)

Open Caveats in Software Release 6.4(19)

Resolved Caveats in Software Release 6.4(19)

Open and Resolved Caveats in Software Release 6.4(18)

Open Caveats in Software Release 6.4(18)

Resolved Caveats in Software Release 6.4(18)

Open and Resolved Caveats in Software Release 6.4(17)

Open Caveats in Software Release 6.4(17)

Resolved Caveats in Software Release 6.4(17)

Open and Resolved Caveats in Software Release 6.4(16)

Open Caveats in Software Release 6.4(16)

Resolved Caveats in Software Release 6.4(16)

Open and Resolved Caveats in Software Release 6.4(15)

Open Caveats in Software Release 6.4(15)

Resolved Caveats in Software Release 6.4(15)

Open and Resolved Caveats in Software Release 6.4(14)

Open Caveats in Software Release 6.4(14)

Resolved Caveats in Software Release 6.4(14)

Open and Resolved Caveats in Software Release 6.4(13)

Open Caveats in Software Release 6.4(13)

Resolved Caveats in Software Release 6.4(13)

Open and Resolved Caveats in Software Release 6.4(12)

Open Caveats in Software Release 6.4(12)

Resolved Caveats in Software Release 6.4(12)

Open and Resolved Caveats in Software Release 6.4(11)

Open Caveats in Software Release 6.4(11)

Resolved Caveats in Software Release 6.4(11)

Open and Resolved Caveats in Software Release 6.4(10)

Open Caveats in Software Release 6.4(10)

Resolved Caveats in Software Release 6.4(10)

Open and Resolved Caveats in Software Release 6.4(9)

Open Caveats in Software Release 6.4(9)

Resolved Caveats in Software Release 6.4(9)

Open and Resolved Caveats in Software Release 6.4(8)

Open Caveats in Software Release 6.4(8)

Resolved Caveats in Software Release 6.4(8)

Open and Resolved Caveats in Software Release 6.4(7)

Open Caveats in Software Release 6.4(7)

Resolved Caveats in Software Release 6.4(7)

Open and Resolved Caveats in Software Release 6.4(6)

Open Caveats in Software Release 6.4(6)

Resolved Caveats in Software Release 6.4(6)

Open and Resolved Caveats in Software Release 6.4(5)

Open Caveats in Software Release 6.4(5)

Resolved Caveats in Software Release 6.4(5)

Open and Resolved Caveats in Software Release 6.4(4a)

Open Caveats in Software Release 6.4(4a)

Resolved Caveats in Software Release 6.4(4a)