Cisco Catalyst 6500 Series Switches

Table Of Contents

Release Notes for Catalyst 6000 Family Software Release 6.x

Contents

Release 6.x DRAM Memory Requirements

Boot ROM Requirements

Upgrading the Boot ROM

Flash PC Card Support

Redundant Supervisor Engine Configurations

Product and Software Version Matrix

Unsupported Hardware

Orderable Software Images

Software Image Version Compatibility

Catalyst 6000 Family Features

Features for Supervisor Engine Software Release 6.4

Software Release 6.4 Hardware Features

Software Release 6.4 Software Features

Features for Supervisor Engine Software Release 6.3

Software Release 6.3 Hardware Features

Software Release 6.3 Software Features

Features for Supervisor Engine Software Release 6.2

Software Release 6.2 Hardware Features

Software Release 6.2 Software Features

Features for Supervisor Engine Software Release 6.1

Software Release 6.1 Hardware Features

Software Release 6.1 Software Features

Features for Supervisor Engine Software Release 5.5

Software Release 5.5 Hardware Features

Software Release 5.5 Software Features

Features for Supervisor Engine Software Release 5.4

Software Release 5.4 Hardware Features

Software Release 5.4 Software Features

Features for Supervisor Engine Software Release 5.3

Features for Supervisor Engine Software Release 5.2

Features for Supervisor Engine Software Release 5.1

Usage Guidelines and Restrictions

System and Supervisor Engine

Modules and Switch Ports

EtherChannel

Quality of Service

Multicast

Spanning Tree

Access Control

High Availability

Multilayer Switching

MIBs

VLANs, VTP, and VLAN Trunks

Authentication, Authorization, and Accounting

Auto-MDI/MDIX

CiscoView Images

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(6a)

Open Caveats in Software Release 6.4(6a)

Resolved Caveats in Software Release 6.4(6a)

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(5b)

Open Caveats in Software Release 6.4(5b)

Resolved Caveats in Software Release 6.4(5b)

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

Open Caveats in Software Release 6.4(5a)

Resolved Caveats in Software Release 6.4(5a)

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(3)x1

Open Caveats in Software Release 6.3(3)x1

Resolved Caveats in Software Release 6.3(3)x1

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

Open Caveats in Software Release 6.3(3)x

Resolved Caveats in Software Release 6.3(3)x

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(3)

Open Caveats in Software Release 6.2(3)

Resolved Caveats in Software Release 6.2(3)

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.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(4)

Open Caveats in Software Release 6.1(4)

Resolved Caveats in Software Release 6.1(4)

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(1d)

Open Caveats in Software Release 6.1(1d)

Resolved Caveats in Software Release 6.1(1d)

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(1b)

Open Caveats in Software Release 6.1(1b)

Resolved Caveats in Software Release 6.1(1b)

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

Open Caveats in Software Release 6.1(1a)

Resolved Caveats in Software Release 6.1(1a)

Catalyst Software Image Upgrade Procedure

Troubleshooting

System Troubleshooting

Module Troubleshooting

VLAN Troubleshooting

STP Troubleshooting

Documentation Updates for Software Release 6.1

Related Documentation

Notices

OpenSSL/Open SSL Project

License Issues

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 6000 Family Software Release 6.x

---

Revised: April 02, 2008, OL-2049-34

Current Release
6.4(23)—December 21, 2006
Previous Releases: 6.4(22), 6.4(21), 6.4(20), 6.4(19), 6.4(18), 6.4(17), 6.4(16), 6.4(15), 6.4(14), 6.4(13), 6.4(12), 6.4(11), 6.4(10), 6.4(9), 6.4(8), 6.4(7), 6.4(6a), 6.4(6), 6.4(5b), 6.4(5a), 6.4(5), 6.4(4a), 6.4(4), 6.4(3) - GD release, 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(3)x1, 6.3(3)x, 6.3(3a), 6.3(3), 6.3(2a), 6.3(2), 6.3(1a), 6.3(1), 6.2(3a), 6.2(3), 6.2(2a), 6.2(2), 6.1(4b), 6.1(4), 6.1(3a), 6.1(3), 6.1(2a), 6.1(2), 6.1(1e), 6.1(1d), 6.1(1c), 6.1(1b), 6.1(1a)

---

Caution The Supervisor Engines 1 and 1A are not supported in Catalyst software release 6.4(22). For more information, refer to Product Bulletin No. 2595 at this URL:
http://www.cisco.com/en/US/products/hw/switches/ps708/prod_eol_notice0900aecd8017a5d1.html

---

---

Note For information on the latest caveats and updates for the Cisco 7600 series router, refer to the Cisco IOS Release 12.1(7a)E1 or later MSFC release notes at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm

---

---

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

---

Contents

This document consists of these sections:

•Release 6.x DRAM Memory Requirements

•Boot ROM Requirements

•Upgrading the Boot ROM

•Flash PC Card Support

•Redundant Supervisor Engine Configurations

•Product and Software Version Matrix

•Unsupported Hardware

•Orderable Software Images

•Software Image Version Compatibility

•Catalyst 6000 Family Features

•Usage Guidelines and Restrictions

•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(6a)

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

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

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

•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(3)x1

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

•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(3)

•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.1(4b)

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

•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(1d)

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

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

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

•Catalyst Software Image Upgrade Procedure

•Troubleshooting

•Documentation Updates for Software Release 6.1

•Related 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 DRAM Memory Requirements

The Catalyst 6000 family Supervisor Engine 2 ships with 128-MB DRAM, which fully supports software release 6.x.

The Catalyst 6000 family Supervisor Engine 1 ships with 64-MB DRAM, which fully supports software release 6.x.

Boot ROM Requirements

For Supervisor Engine 1, the minimum boot ROM (ROMMON) required for software release 5.4(1) and later 5.x(x) releases is 5.2(1). The minimum boot ROM required for software releases 6.x(x) and later is 5.2(1). The default (shipping) image for software releases 6.x(x) and later is 5.3(1).

For Supervisor Engine 2, the minimum boot ROM required for software releases 6.2(2) and later
is 6.1(3).

---

Note The supervisor engine boot ROM versions must be identical in redundant systems.

---

Upgrading the Boot ROM

Follow these guidelines to upgrade the Boot ROM (ROMMON) on Supervisor Engine 1 or 1A:

---

Note For Supervisor Engine 2 with boot ROM version 6.1(3) or later, the boot ROM software image can be upgraded through a software download from Cisco.com. Refer to the boot ROM software upgrade procedure at http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_13488.htm

---

•For supervisor engines with an MSFC, due to the location of the boot ROM, upgrading the boot ROM could damage your supervisor engine. This hardware configuration is not field upgradable.

•For supervisor engines with an MSFC2 or no PFC, the boot ROM upgrade can be done in the field.

•The boot ROM upgrade kit part number is WS-X6K-BOOT=.

---

Note The boot ROM upgrade kit is not orderable. If an upgrade is needed, contact the Technical Assistance Center (TAC) to verify your hardware configuration and arrange for delivery of the upgrade kit.

---

•For boot ROM installation information, refer to the Catalyst 6000 Family Supervisor Engine NMP Boot ROM Upgrade Installation Note at http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/78_10142.htm

Flash PC Card Support

The following Flash PC cards are supported on the Catalyst 6500 series switches:

•MEM-C6K-FLC16M(=)

•MEM-C6K-FLC24M(=)

•MEM-C6K-FLC64M(=)

•MEM-C6K-ATA-1-64M(=)

Prior to software release 7.5(1), Supervisor Engine 1 and Supervisor Engine 2 supported the following Flash PC cards:

•16-MB Flash PC card (MEM-C6K-FLC16M=). The device name is slot0:.

•24-MB Flash PC card (MEM-C6K-FLC24M=). The device name is slot0:.

With software release 7.5(1) and later releases, additional Flash PC card support was added as follows:

•64-MB ATA Flash PC card (MEM-C6K-ATA-1-64M=)—Only supported on Supervisor Engine 2. The device name is disk0: and the card requires ROMMON version 7.1(1) or later releases.

•64-MB linear Flash PC card (MEM-C6K-FLC64M=)—Only supported on Supervisor Engine 1. The device name is slot0: and the card requires ROMMON software release 5.3(1) or later releases.

---

Note The MEM-C6K-ATA-1-64M(=) and MEM-C6K-FLC64M= Flash PC cards are not formatted. Although the cards appear to be formatted when first installed, you must format the cards to prevent possible data corruption.

---

---

Note The 16-MB MEM-C6K-FLC16M(=) and 24-MB MEM-C6K-FLC24M(=) linear Flash PC cards are not formatted. Supervisor Engine 1 and Supervisor Engine 2 do not support the same Flash PC card format. To use a Flash PC card with Supervisor Engine 2, you must format the card with Supervisor Engine 2. To use a Flash PC card with Supervisor Engine 1, you must format the card with Supervisor Engine 1.

---

---

Note For Supervisor Engine 1, software release 7.6(1) or later CV images need a 24-MB or 64-MB linear Flash PC card.

With the 24-MB linear Flash PC card with a Supervisor Engine 1/MSFC or a Supervisor Engine 1/MSFC2 with a 16-MB MSFC2 bootflash, you need to put the Catalyst image on the 24-MB linear Flash PC card, the Cisco IOS bootloader on the MSFC bootflash, and the Cisco IOS image on the 16-MB supervisor engine bootflash.

With the 64-MB linear Flash PC card with a Supervisor Engine 1/MSFC or a Supervisor Engine 1/MSFC2 with a 16-MB MSFC2 bootflash, you can put the Catalyst image and the MSFC/MSFC2 Cisco IOS image on the 64-MB linear Flash PC card, and the Cisco IOS bootloader on the MSFC bootflash.

With the 24-MB or 64-MB linear Flash PC card on a Supervisor Engine 1/MSFC2 with 32-MB MSFC2 bootflash, you can put the MSFC2 bootloader and Cisco IOS image on the MSFC2 bootflash, and the Catalyst image can be put on the 24-MB or 64-MB linear Flash PC cards.

---

Redundant Supervisor Engine Configurations

In systems with redundant supervisor engines, both supervisor engines must be identical and have the same daughter card configurations. For example:

•Slot 1—Supervisor Engine 2, PFC2, MSFC2
Slot 2—Supervisor Engine 2, PFC2, MSFC2

•Slot 1—Supervisor Engine 2, PFC2
Slot 2—Supervisor Engine 2, PFC2

•Slot 1—Supervisor Engine 1, PFC, MSFC2
Slot 2—Supervisor Engine 1, PFC, MSFC2

•Slot 1—Supervisor Engine 1, PFC, MSFC1
Slot 2—Supervisor Engine 1, PFC, MSFC1

•Slot 1—Supervisor Engine 1, PFC
Slot 2—Supervisor Engine 1, PFC

•Slot 1—Supervisor Engine 1
Slot 2—Supervisor Engine 1

These configuration requirements apply to all Catalyst 6000 family switches. We do not support configurations that are not identical.

Product and Software Version Matrix

Table 1 lists the minimum supervisor engine version and the current recommended/default supervisor engine software version for Catalyst 6000 family modules and chassis.

---

Note For information about AC power requirements and heat dissipation, refer to the "Power Requirements" section in Chapter 2, "Preparing for Installation," of the Catalyst 6000 Family Installation Guide:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/6000hw/index.htm

For information about power management and determining system power requirements, refer to the "Power Management" section in Chapter 20, "Administering the Switch," of the Catalyst 6000 Family Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_6_3/index.htm

---

---

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

---

Table 1 Minimum and Recommended Supervisor Engine Software Versions 

Product Number append with "=" for spares	Product Description	Minimum Supervisor Software Version	Recommended Supervisor Software Version
Supervisor Engine 2
WS-X6K-S2U-MSFC2	Supervisor Engine 2, dual 1000BASE-X GBIC uplinks, fabric-enabled, CEF, PFC2, and MSFC2 256 MB on supervisor engine, 256 MB on MSFC2 QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	6.1(1d)	6.4(11)
WS-X6K-S2-MSFC2	Supervisor Engine 2, dual 1000BASE-X GBIC uplinks, fabric-enabled, CEF, PFC2, and MSFC2 128 MB on supervisor engine, 128 MB on MSFC2 QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	6.1(1d)	6.4(11)
WS-X6K-S2-PFC2	Supervisor Engine 2, dual 1000BASE-X GBIC uplinks, fabric-enabled, and PFC2 QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	6.1(1d)	6.4(11)
Supervisor Engine 11 , 2
WS-X6K-S1A-MSFC2	Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, PFC, and MSFC2 QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.4(3)	6.4(11)
WS-X6K-SUP1A-MSFC	Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, PFC, and MSFC QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.3(1a)CSX	6.4(11)
WS-X6K-SUP1A-PFC	Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, and PFC QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.3(1a)CSX	6.4(11)
WS-X6K-SUP1A-2GE	Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.3(1a)CSX	6.4(11)
WS-X6K-SUP1-2GE	Supervisor Engine 1, dual 1000BASE-X GBIC uplinks QoS port architecture (Rx/Tx): 1q4t/2q2t	5.1(1)CSX	6.4(11)
Switch Fabric Module
WS-C6500-SFM	Switch Fabric Module to support fabric-enabled modules	6.1(1d)	6.4(11)
WS-X6500-SFM 2	Switch Fabric Module version 2	6.2(2)	6.4(11)
Gigabit Ethernet Switching Modules
WS-X6516-GBIC3	16-port Gigabit Ethernet GBIC switching module, fabric-enabled QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	6.1(1d)	6.4(11)
WS-X6516-GE-TX	16-port 10/100/1000BASE-T Ethernet Module, fabric-enabled QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	6.2(2)	6.4(11)
WS-X6416-GBIC	16-port Gigabit Ethernet GBIC switching module QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.4(2)	6.4(11)
WS-X6416-GE-MT	16-port Gigabit Ethernet MT-RJ QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.3(5a)CSX	6.4(11)
WS-X6316-GE-TX	16-port 1000BASE-TX RJ-45 Gigabit Ethernet QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.4(2)	6.4(11)
WS-X6408A-GBIC	8-port Gigabit Ethernet GBIC QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t	5.3(1a)CSX	6.4(11)
WS-X6408-GBIC	8-port Gigabit Ethernet GBIC QoS port architecture (Rx/Tx): 1q4t/2q2t	5.1(1)CSX	6.4(11)
Fast Ethernet Switching Modules
WS-X6324-100FX-SM WS-X6324-100FX-MM	24-port 100FX single mode or multimode MT-RJ with 128K per-port packet buffers QoS port architecture (Rx/Tx): 1q4t/2q2t	5.4(2)	6.4(11)
WS-X6224-100FX-MT	24-port 100FX Multimode MT-RJ QoS port architecture (Rx/Tx): 1q4t/2q2t	5.1(1)CSX	6.4(11)
Ethernet/Fast Ethernet (10/100) Switching Modules
WS-X6148-RJ-45 WS-X6148-RJ-45V	48-port 10/100BASE-TX RJ-45 with 128K per-port packet buffers (WS-X6148-RJ-45V provides inline power to IP telephones) QoS port architecture (Rx/Tx): 1q4t/2q2t	6.4(1)	6.4(11)
WS-X6148-RJ21 WS-X6148-RJ21V	48-port 10/100BASE-TX RJ-21 with 128K per-port packet buffers (WS-X6148-RJ21V provides inline power to IP telephones) QoS port architecture (Rx/Tx): 1q4t/2q2t	6.4(1)	6.4(11)
WS-X6548-RJ-21	48-port 10/100BASE-TX RJ-21, fabric-enabled QoS port architecture (Rx/Tx): 1p1q0t/1p3q1t	6.2(2)	6.4(11)
WS-X6548-RJ-45	48-port 10/100BASE-TX RJ-45, fabric-enabled QoS port architecture (Rx/Tx): 1p1q0t/1p3q1t	6.2(2)	6.4(11)
WS-X6348-RJ21V	48-port 10/100BASE-TX RJ-21 with 128k per-port packet buffers (WS-X6348-RJ21V provides inline power to IP telephones) QoS port architecture (Rx/Tx): 1q4t/2q2t	6.2(2)	6.4(11)
WS-X6348-RJ-45 WS-X6348-RJ-45V	48-port 10/100BASE-TX RJ-45 with 128k per-port packet buffers (WS-X6348-RJ-45 accepts a field-upgradable voice daughter card to provide inline power to IP telephones. Already installed on WS-X6348-RJ-45V) QoS port architecture (Rx/Tx): 1q4t/2q2t	Without WS-F6K-VPWR: 5.4(2) With WS-F6K-VPWR: 5.5(1)	Without WS-F6K-VPWR: 6.4(11) With WS-F6K-VPWR: 6.4(11)
WS-F6K-VPWR	Inline-power field-upgrade module for the 48-port 10/100BASE-TX RJ-45 and RJ-21 modules	5.5(1)	6.4(11)
WS-X6248-RJ-45	48-port 10/100BASE-TX RJ-45 QoS port architecture (Rx/Tx): 1q4t/2q2t	5.1(1)CSX	6.4(11)
WS-X6248A-TEL	48-port 10/100BASE-TX RJ-21 with 128K per-port packet buffers QoS port architecture (Rx/Tx): 1q4t/2q2t	5.3(2)CSX	6.4(11)
WS-X6248-TEL	48-port 10/100BASE-TX RJ-21 QoS port architecture (Rx/Tx): 1q4t/2q2t	5.2(1)CSX	6.4(11)
Ethernet Switching Modules
WS-X6024-10FL-MT	24-port 10BASE-FL MT-RJ QoS port architecture (Rx/Tx): 1q4t/2q2t	5.3(3)CSX	6.4(11)
Voice Modules
WS-X6624-FXS	24-port FXS analog interface module	5.5(1)	6.4(11)
WS-X6608-T1 WS-X6608-E1	8-port T1/E1 PSTN interface modules	5.5(1)	6.4(11)
FlexWan Module4
WS-X6182-2PA	FlexWAN Module	5.4(2)	6.4(11)
Intrusion Detection System Module5
WS-X6381-IDS	Intrusion Detection System Module	6.1(1d)	6.4(11)
Network Analysis Module6 , 7
WS-X6380-NAM	Network Analysis Module	5.5(1)	6.4(11)
ATM8
WS-X6101-OC12-SMF	Single-port single-mode OC-12 ATM	5.3(2)CSX	6.4(11)
WS-X6101-OC12-MMF	Single-port multimode OC-12 ATM	5.3(2)CSX	6.4(11)
Multilayer Switch Module (MSM)9
WS-X6302-MSM	Multilayer Switch Module	5.2(1)CSX	6.4(11)
Optical Services Module10
4-port Gigabit Ethernet WAN
OSM-4GE-WAN-GBIC	4-port Gigabit Ethernet Optical Services Module	6.1(2)	6.4(11)
OC-12 Packet over SONET11
OSM-2OC12-POS-MM	2-port OC-12c/STM-4c POS Optical Services Module, MM, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-2OC12-POS-SI	2-port OC-12c/STM-4c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-2OC12-POS-SL	2-port OC-12c/STM-4c POS Optical Services Module, SM-LR12 , with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-4OC12-POS-MM	4-port OC-12c/STM-4c POS Optical Services Module, MM, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-4OC12-POS-SI	4-port OC-12c/STM-4c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-4OC12-POS-SL	4-port OC-12c/STM-4c POS Optical Services Module, SM-LR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OC-3 Packet over SONET9
OSM-8OC3-POS-MM	8-port OC-3c/STM-1c POS Optical Services Module, MM, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-8OC3-POS-SI	8-port OC-3c/STM-1c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-8OC3-POS-SL	8-port OC-3c/STM-1c POS Optical Services Module, SM-LR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-16OC3-POS-MM	16-port OC-3c/STM-1c POS Optical Services Module, MM, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-16OC3-POS-SI	16-port OC-3c/STM-1c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OSM-16OC3-POS-SL	16-port OC-3c/STM-1c POS Optical Services Module, SM-LR, with 4 Gigabit Ethernet ports	6.1(2)	6.4(11)
OC-48 Packet over SONET9
OSM-1OC48-POS-SS	1-port OC-48c/STM-16c POS Optical Services Module, SM-SR, with 4 Gigabit Ethernet ports	6.1(3)	6.4(11)
OSM-1OC48-POS-SI	1-port OC-48c/STM-16c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports	6.1(3)	6.4(11)
OSM-1OC48-POS-SL	1-port OC-48c/STM-16c POS Optical Services Module, SM-LR, with 4 Gigabit Ethernet ports	6.1(3)	6.4(11)
Power Supplies
WS-CAC-1000W	1000W AC power supply	5.1(1)CSX	6.4(11)
WS-CAC-1300W	1300W AC power supply	5.1(1)CSX	6.4(11)
WS-CDC-1300W	1300W DC power supply	5.1(1)CSX	6.4(11)
WS-CAC-2500W	2500W AC power supply	5.4(2)	6.4(11)
WS-CDC-2500W	2500W DC power supply	5.4(2)	6.4(11)
WS-CAC-4000W	4000W AC power supply	6.1(3)	6.4(11)
Modular Chassis
WS-C6513	Catalyst 6513 chassis: •13 slots •64 chassis MAC addresses •Supported only with Supervisor Engine 2	6.2(2)	6.4(11)
WS-C6509	Catalyst 6509 chassis: •9 slots •1024 chassis MAC addresses	5.1(1)CSX	6.4(11)
WS-C6509-NEB	Catalyst 6509-NEB chassis: •9 vertical slots •1024 chassis MAC addresses	5.4(2)	6.4(11)
WS-C6009	Catalyst 6009 chassis: •9 slots •1024 chassis MAC addresses	5.1(1)CSX	6.4(11)
WS-C6506	Catalyst 6506 chassis: •6 slots •1024 chassis MAC addresses	5.2(1)CSX	6.4(11)
WS-C6006	Catalyst 6006 chassis: •6 slots •1024 chassis MAC addresses	5.2(1)CSX	6.4(11)
OSR-7609-AC, -DC	Cisco 7609 router chassis: •9 vertical slots •1024 chassis MAC addresses •Supported only with Supervisor Engine 2	6.1(1b)	6.4(11)

1 Not supported in the WS-C6513 chassis. 2 Not supported in software release 6.4(22). For more information, refer to Product Bulletin No. 2595 at this URL: http://www.cisco.com/en/US/products/hw/switches/ps708/prod_eol_notice0900aecd8017a5d1.html 3 The WS-X6516A-GBIC version of this module is not supported in software release 6.x. The WS-X6516A-GBIC version is supported in software release 7.5(1). 4 Refer to the Catalyst 6000 Family FlexWAN Module Installation and Configuration Note. 5 Refer to the Catalyst 6000 Intrusion Detection System Module Installation and Configuration Note. 6 Refer to the Network Analysis Module Installation and Configuration Note. 7 The Network Analysis Module (NAM) application image 1.1(1a) and NAM maintenance image 1.1(1a)m are not supported with supervisor engine software releases 6.3(2) and later. For supervisor engine software releases 6.3(2) and later, use the 1.2 NAM image. 8 Refer to the ATM Configuration Guide and Command Reference. 9 Refer to the Multilayer Switch Module Release Notes. 10 Refer to the Optical Services Module Installation and Configuration Note. 11 Also has four Layer 2 Gigabit Ethernet ports. 12 Single-mode, long reach.

Unsupported Hardware

The Distributed Forwarding Card (WS-F6K-DFC) and 16-port Gigabit Ethernet switching module (WS-X6816-GBIC) are not supported in systems running Catalyst software on the supervisor engine and Cisco IOS software only on the MSFC. These items are supported on systems running Cisco IOS Release 12.1(8a)E or later on both the Supervisor Engine 2 and the MSFC2.

Orderable Software Images

Table 2 lists the software versions and applicable ordering information for the Catalyst 6000 family supervisor engine software.

---

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 downgrading switch software, you will lose your configuration. Use the write network command or the copy config tftp command to back up your configuration to a Trivial File Transfer Protocol (TFTP) server. Use the copy config flash command to back up the configuration to a Flash device.

---

---

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

---

Table 2 Orderable Software Images 

Software Version	Filename	Orderable Product Number1
Supervisor Engine 2
6.4(22) Flash image	cat6000-sup2.6-4-22.bin	SC6K-SUP2-6.4
6.4(22) Flash image (CiscoView)	cat6000-sup2cv.6-4-22.bin	SC6K-SUP2CV-6.4
6.4(22) Flash image (Secure Shell)	cat6000-sup2k9.6-4-22.bin	SC6K-SUP2K9-6.4
6.4(22) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-22.bin	SC6K-SUP2CVK9-6.4
6.4(21) Flash image	cat6000-sup2.6-4-21.bin	SC6K-SUP2-6.4
6.4(21) Flash image (CiscoView)	cat6000-sup2cv.6-4-21.bin	SC6K-SUP2CV-6.4
6.4(21) Flash image (Secure Shell)	cat6000-sup2k9.6-4-21.bin	SC6K-SUP2K9-6.4
6.4(21) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-21.bin	SC6K-SUP2CVK9-6.4
6.4(20) Flash image	cat6000-sup2.6-4-20.bin	SC6K-SUP2-6.4
6.4(20) Flash image (CiscoView)	cat6000-sup2cv.6-4-20.bin	SC6K-SUP2CV-6.4
6.4(20) Flash image (Secure Shell)	cat6000-sup2k9.6-4-20.bin	SC6K-SUP2K9-6.4
6.4(20) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-20.bin	SC6K-SUP2CVK9-6.4
6.4(19) Flash image	cat6000-sup2.6-4-19.bin	SC6K-SUP2-6.4
6.4(19) Flash image (CiscoView)	cat6000-sup2cv.6-4-19.bin	SC6K-SUP2CV-6.4
6.4(19) Flash image (Secure Shell)	cat6000-sup2k9.6-4-19.bin	SC6K-SUP2K9-6.4
6.4(19) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-19.bin	SC6K-SUP2CVK9-6.4
6.4(18) Flash image	cat6000-sup2.6-4-18.bin	SC6K-SUP2-6.4
6.4(18) Flash image (CiscoView)	cat6000-sup2cv.6-4-18.bin	SC6K-SUP2CV-6.4
6.4(18) Flash image (Secure Shell)	cat6000-sup2k9.6-4-18.bin	SC6K-SUP2K9-6.4
6.4(18) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-18.bin	SC6K-SUP2CVK9-6.4
6.4(17) Flash image	cat6000-sup2.6-4-17.bin	SC6K-SUP2-6.4
6.4(17) Flash image (CiscoView)	cat6000-sup2cv.6-4-17.bin	SC6K-SUP2CV-6.4
6.4(17) Flash image (Secure Shell)	cat6000-sup2k9.6-4-17.bin	SC6K-SUP2K9-6.4
6.4(17) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-17.bin	SC6K-SUP2CVK9-6.4
6.4(16) Flash image	cat6000-sup2.6-4-16.bin	SC6K-SUP2-6.4
6.4(16) Flash image (CiscoView)	cat6000-sup2cv.6-4-16.bin	SC6K-SUP2CV-6.4
6.4(16) Flash image (Secure Shell)	cat6000-sup2k9.6-4-16.bin	SC6K-SUP2K9-6.4
6.4(16) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-16.bin	SC6K-SUP2CVK9-6.4
6.4(15) Flash image	cat6000-sup2.6-4-15.bin	SC6K-SUP2-6.4
6.4(15) Flash image (CiscoView)	cat6000-sup2cv.6-4-15.bin	SC6K-SUP2CV-6.4
6.4(15) Flash image (Secure Shell)	cat6000-sup2k9.6-4-15.bin	SC6K-SUP2K9-6.4
6.4(15) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-15.bin	SC6K-SUP2CVK9-6.4
6.4(14) Flash image	cat6000-sup2.6-4-14.bin	SC6K-SUP2-6.4
6.4(14) Flash image (CiscoView)	cat6000-sup2cv.6-4-14.bin	SC6K-SUP2CV-6.4
6.4(14) Flash image (Secure Shell)	cat6000-sup2k9.6-4-14.bin	SC6K-SUP2K9-6.4
6.4(14) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-14.bin	SC6K-SUP2CVK9-6.4
6.4(13) Flash image	cat6000-sup2.6-4-13.bin	SC6K-SUP2-6.4
6.4(13) Flash image (CiscoView)	cat6000-sup2cv.6-4-13.bin	SC6K-SUP2CV-6.4
6.4(13) Flash image (Secure Shell)	cat6000-sup2k9.6-4-13.bin	SC6K-SUP2K9-6.4
6.4(13) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-13.bin	SC6K-SUP2CVK9-6.4
6.4(12) Flash image	cat6000-sup2.6-4-12.bin	SC6K-SUP2-6.4
6.4(12) Flash image (CiscoView)	cat6000-sup2cv.6-4-12.bin	SC6K-SUP2CV-6.4
6.4(12) Flash image (Secure Shell)	cat6000-sup2k9.6-4-12.bin	SC6K-SUP2K9-6.4
6.4(12) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-12.bin	SC6K-SUP2CVK9-6.4
6.4(11) Flash image	cat6000-sup2.6-4-11.bin	SC6K-SUP2-6.4
6.4(11) Flash image (CiscoView)	cat6000-sup2cv.6-4-11.bin	SC6K-SUP2CV-6.4
6.4(11) Flash image (Secure Shell)	cat6000-sup2k9.6-4-11.bin	SC6K-SUP2K9-6.4
6.4(11) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-11.bin	SC6K-SUP2CVK9-6.4
6.4(10) Flash image	cat6000-sup2.6-4-10.bin	SC6K-SUP2-6.4
6.4(10) Flash image (CiscoView)	cat6000-sup2cv.6-4-10.bin	SC6K-SUP2CV-6.4
6.4(10) Flash image (Secure Shell)	cat6000-sup2k9.6-4-10.bin	SC6K-SUP2K9-6.4
6.4(10) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-10.bin	SC6K-SUP2CVK9-6.4
6.4(9) Flash image	cat6000-sup2.6-4-9.bin	SC6K-SUP2-6.4
6.4(9) Flash image (CiscoView)	cat6000-sup2cv.6-4-9.bin	SC6K-SUP2CV-6.4
6.4(9) Flash image (Secure Shell)	cat6000-sup2k9.6-4-9.bin	SC6K-SUP2K9-6.4
6.4(9) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-9.bin	SC6K-SUP2CVK9-6.4
6.4(8) Flash image	cat6000-sup2.6-4-8.bin	SC6K-SUP2-6.4
6.4(8) Flash image (CiscoView)	cat6000-sup2cv.6-4-8.bin	SC6K-SUP2CV-6.4
6.4(8) Flash image (Secure Shell)	cat6000-sup2k9.6-4-8.bin	SC6K-SUP2K9-6.4
6.4(8) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-8.bin	SC6K-SUP2CVK9-6.4
6.4(7) Flash image	cat6000-sup2.6-4-7.bin	SC6K-SUP2-6.4
6.4(7) Flash image (CiscoView)	cat6000-sup2cv.6-4-7.bin	SC6K-SUP2CV-6.4
6.4(7) Flash image (Secure Shell)	cat6000-sup2k9.6-4-7.bin	SC6K-SUP2K9-6.4
6.4(7) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-7.bin	SC6K-SUP2CVK9-6.4
6.4(6a) Flash image	cat6000-sup2.6-4-6a.bin	SC6K-SUP2-6.4
6.4(6a) Flash image (CiscoView)	cat6000-sup2cv.6-4-6a.bin	SC6K-SUP2CV-6.4
6.4(6a) Flash image (Secure Shell)	cat6000-sup2k9.6-4-6a.bin	SC6K-SUP2K9-6.4
6.4(6a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-6a.bin	SC6K-SUP2CVK9-6.4
6.4(6) Flash image	cat6000-sup2.6-4-6.bin	SC6K-SUP2-6.4
6.4(6) Flash image (CiscoView)	cat6000-sup2cv.6-4-6.bin	SC6K-SUP2CV-6.4
6.4(6) Flash image (Secure Shell)	cat6000-sup2k9.6-4-6.bin	SC6K-SUP2K9-6.4
6.4(6) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-6.bin	SC6K-SUP2CVK9-6.4
6.4(5b) Flash image	cat6000-sup2.6-4-5b.bin	SC6K-SUP2-6.4
6.4(5b) Flash image (Secure Shell)	cat6000-sup2k9.6-4-5b.bin	SC6K-SUP2K9-6.4
6.4(5a) Flash image	cat6000-sup2.6-4-5a.bin	SC6K-SUP2-6.4
6.4(5a) Flash image (Secure Shell)	cat6000-sup2k9.6-4-5a.bin	SC6K-SUP2K9-6.4
6.4(5) Flash image	cat6000-sup2.6-4-5.bin	SC6K-SUP2-6.4
6.4(5) Flash image (CiscoView)	cat6000-sup2cv.6-4-5.bin	SC6K-SUP2CV-6.4
6.4(5) Flash image (Secure Shell)	cat6000-sup2k9.6-4-5.bin	SC6K-SUP2K9-6.4
6.4(5) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-5.bin	SC6K-SUP2CVK9-6.4
6.4(4a) Flash image	cat6000-sup2.6-4-4a.bin	SC6K-SUP2-6.4.4a
6.4(4a) Flash image (CiscoView)	cat6000-sup2cv.6-4-4a.bin	SC6K-SUP2CV-6.4.4a
6.4(4a) Flash image (Secure Shell)	cat6000-sup2k9.6-4-4a.bin	SC6K-SUP2K9-6.4.4a
6.4(4a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-4a.bin	SC6K-SUP2CVK9-6.4.4a
6.4(4) Flash image	cat6000-sup2.6-4-4.bin	SC6K-SUP2-6.4.4
6.4(4) Flash image (CiscoView)	cat6000-sup2cv.6-4-4.bin	SC6K-SUP2CV-6.4.4
6.4(4) Flash image (Secure Shell)	cat6000-sup2k9.6-4-4.bin	SC6K-SUP2K9-6.4.4
6.4(4) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-4.bin	SC6K-SUP2CVK9-6.4.4
6.4(3) Flash image	cat6000-sup2.6-4-3.bin	SC6K-SUP2-6.4.3
6.4(3) Flash image (CiscoView)	cat6000-sup2cv.6-4-3.bin	SC6K-SUP2CV-6.4.3
6.4(3) Flash image (Secure Shell)	cat6000-sup2k9.6-4-3.bin	SC6K-SUP2K9-6.4.3
6.4(3) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-3.bin	SC6K-SUP2CVK9-6.4.3
6.4(2) Flash image	cat6000-sup2.6-4-2.bin	SC6K-SUP2-6.4.2
6.4(2) Flash image (CiscoView)	cat6000-sup2cv.6-4-2.bin	SC6K-SUP2CV-6.4.2
6.4(2) Flash image (Secure Shell)	cat6000-sup2k9.6-4-2.bin	SC6K-SUP2K9-6.4.2
6.4(2) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-2.bin	SC6K-SUP2CVK9-6.4.2
6.4(1) Flash image	cat6000-sup2.6-4-1.bin	SC6K-SUP2-6.4.1
6.4(1) Flash image (CiscoView)	cat6000-sup2cv.6-4-1.bin	SC6K-SUP2CV-6.4.1
6.4(1) Flash image (Secure Shell)	cat6000-sup2k9.6-4-1.bin	SC6K-SUP2K9-6.4.1
6.4(1) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-4-1.bin	SC6K-SUP2CVK9-6.4.1
6.3(10) Flash image	cat6000-sup2.6-3-10.bin	SC6K-SUP2-6.3.10
6.3(10) Flash image (CiscoView)	cat6000-sup2cv.6-3-10.bin	SC6K-SUP2CV-6.3.10
6.3(10) Flash image (Secure Shell)	cat6000-sup2k9.6-3-10.bin	SC6K-SUP2K9-6.3.10
6.3(10) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-10.bin	SC6K-SUP2CVK9-6.3.10
6.3(9) Flash image	cat6000-sup2.6-3-9.bin	SC6K-SUP2-6.3.9
6.3(9) Flash image (CiscoView)	cat6000-sup2cv.6-3-9.bin	SC6K-SUP2CV-6.3.9
6.3(9) Flash image (Secure Shell)	cat6000-sup2k9.6-3-9.bin	SC6K-SUP2K9-6.3.9
6.3(9) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-9.bin	SC6K-SUP2CVK9-6.3.9
6.3(8) Flash image	cat6000-sup2.6-3-8.bin	SC6K-SUP2-6.3.8
6.3(8) Flash image (CiscoView)	cat6000-sup2cv.6-3-8.bin	SC6K-SUP2CV-6.3.8
6.3(8) Flash image (Secure Shell)	cat6000-sup2k9.6-3-8.bin	SC6K-SUP2K9-6.3.8
6.3(8) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-8.bin	SC6K-SUP2CVK9-6.3.8
6.3(7) Flash image	cat6000-sup2.6-3-7.bin	SC6K-SUP2-6.3.7
6.3(7) Flash image (CiscoView)	cat6000-sup2cv.6-3-7.bin	SC6K-SUP2CV-6.3.7
6.3(7) Flash image (Secure Shell)	cat6000-sup2k9.6-3-7.bin	SC6K-SUP2K9-6.3.7
6.3(7) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-7.bin	SC6K-SUP2CVK9-6.3.7
6.3(6) Flash image	cat6000-sup2.6-3-6.bin	SC6K-SUP2-6.3.6
6.3(6) Flash image (CiscoView)	cat6000-sup2cv.6-3-6.bin	SC6K-SUP2CV-6.3.6
6.3(6) Flash image (Secure Shell)	cat6000-sup2k9.6-3-6.bin	SC6K-SUP2K9-6.3.6
6.3(6) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-6.bin	SC6K-SUP2CVK9-6.3.6
6.3(5) Flash image	cat6000-sup2.6-3-5.bin	SC6K-SUP2-6.3.5
6.3(5) Flash image (CiscoView)	cat6000-sup2cv.6-3-5.bin	SC6K-SUP2CV-6.3.5
6.3(5) Flash image (Secure Shell)	cat6000-sup2k9.6-3-5.bin	SC6K-SUP2K9-6.3.5
6.3(5) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-5.bin	SC6K-SUP2CVK9-6.3.5
6.3(4a) Flash image	cat6000-sup2.6-3-4a.bin	SC6K-SUP2-6.3.4a
6.3(4a) Flash image (CiscoView)	cat6000-sup2cv.6-3-4a.bin	SC6K-SUP2CV-6.3.4a
6.3(4a) Flash image (Secure Shell)	cat6000-sup2k9.6-3-4a.bin	SC6K-SUP2K9-6.3.4a
6.3(4a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-4a.bin	SC6K-SUP2CVK9-6.3.4a
6.3(4) Flash image	cat6000-sup2.6-3-4.bin	SC6K-SUP2-6.3.4
6.3(4) Flash image (CiscoView)	cat6000-sup2cv.6-3-4.bin	SC6K-SUP2CV-6.3.4
6.3(4) Flash image (Secure Shell)	cat6000-sup2k9.6-3-4.bin	SC6K-SUP2K9-6.3.4
6.3(4) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-4.bin	SC6K-SUP2CVK9-6.3.4
6.3(3)x1 Flash image	cat6000-sup2.6-3-3X1.bin	SC6K-SUP2-6.3.3X1
6.3(3)x Flash image	cat6000-sup2.6-3-3X.bin	SC6K-SUP2-6.3.3X
6.3(3a) Flash image	cat6000-sup2.6-3-3a.bin	SC6K-SUP2-6.3.3a
6.3(3a) Flash image (CiscoView)	cat6000-sup2cv.6-3-3a.bin	SC6K-SUP2CV-6.3.3a
6.3(3a) Flash image (Secure Shell)	cat6000-sup2k9.6-3-3a.bin	SC6K-SUP2K9-6.3.3a
6.3(3a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-3a.bin	SC6K-SUP2CVK9-6.3.3a
6.3(3) Flash image	cat6000-sup2.6-3-3.bin	SC6K-SUP2-6.3.3
6.3(3) Flash image (CiscoView)	cat6000-sup2cv.6-3-3.bin	SC6K-SUP2CV-6.3.3
6.3(3) Flash image (Secure Shell)	cat6000-sup2k9.6-3-3.bin	SC6K-SUP2K9-6.3.3
6.3(3) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-3.bin	SC6K-SUP2CVK9-6.3.3
6.3(2a) Flash image	cat6000-sup2.6-3-2a.bin	SC6K-SUP2-6.3.2a
6.3(2a) Flash image (CiscoView)	cat6000-sup2cv.6-3-2a.bin	SC6K-SUP2CV-6.3.2a
6.3(2a) Flash image (Secure Shell)	cat6000-sup2k9.6-3-2a.bin	SC6K-SUP2K9-6.3.2a
6.3(2a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-2a.bin	SC6K-SUP2CVK9-6.3.2a
6.3(2) Flash image	cat6000-sup2.6-3-2.bin	SC6K-SUP2-6.3.2
6.3(2) Flash image (CiscoView)	cat6000-sup2cv.6-3-2.bin	SC6K-SUP2CV-6.3.2
6.3(2) Flash image (Secure Shell)	cat6000-sup2k9.6-3-2.bin	SC6K-SUP2K9-6.3.2
6.3(2) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-2.bin	SC6K-SUP2CVK9-6.3.2
6.3(1a) Flash image	cat6000-sup2.6-3-1a.bin	SC6K-SUP2-6.3.1a
6.3(1a) Flash image (Secure Shell)	cat6000-sup2k9.6-3-1a.bin	SC6K-SUP2K9-6.3.1a
6.3(1) Flash image	cat6000-sup2.6-3-1.bin	SC6K-SUP2-6.3.1
6.3(1) Flash image (CiscoView)	cat6000-sup2cv.6-3-1.bin	SC6K-SUP2CV-6.3.1
6.3(1) Flash image (Secure Shell)	cat6000-sup2k9.6-3-1.bin	SC6K-SUP2K9-6.3.1
6.3(1) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-3-1.bin	SC6K-SUP2CVK9-6.3.1
6.2(3a) Flash image	cat6000-sup2.6-2-3a.bin	SC6K-SUP2-6.2.3a
6.2(3a) Flash image (Secure Shell)	cat6000-sup2k9.6-2-3a.bin	SC6K-SUP2K9-6.2.3a
6.2(3) Flash image	cat6000-sup2.6-2-3.bin	SC6K-SUP2-6.2.3
6.2(3) Flash image (CiscoView)	cat6000-sup2cv.6-2-3.bin	SC6K-SUP2CV-6.2.3
6.2(3) Flash image (Secure Shell)	cat6000-sup2k9.6-2-3.bin	SC6K-SUP2K9-6.2.3
6.2(3) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-2-3.bin	SC6K-SUP2CVK9-6.2.3
6.2(2a) Flash image	cat6000-sup2.6-2-2a.bin	SC6K-SUP2-6.2.2a
6.2(2a) Flash image (CiscoView)	cat6000-sup2cv.6-2-2a.bin	SC6K-SUP2CV-6.2.2a
6.2(2a) Flash image (Secure Shell)	cat6000-sup2k9.6-2-2a.bin	SC6K-SUP2K9-6.2.2a
6.2(2a) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-2-2a.bin	SC6K-SUP2CVK9-6.2.2a
6.2(2) Flash image	cat6000-sup2.6-2-2.bin	SC6K-SUP2-6.2.2
6.2(2) Flash image (CiscoView)	cat6000-sup2cv.6-2-2.bin	SC6K-SUP2CV-6.2.2
6.2(2) Flash image (Secure Shell)	cat6000-sup2k9.6-2-2.bin	SC6K-SUP2K9-6.1.4
6.2(2) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-2-2.bin	SC6K-SUP2CVK9-6.2.2
6.1(4b) Flash image	cat6000-sup2.6-1-4b.bin	SC6K-SUP2-6.1.4b
6.1(4b) Flash image (Secure Shell)	cat6000-sup2k9.6-1-4b.bin	SC6K-SUP2K9-6.1.4b
6.1(4) Flash image	cat6000-sup2.6-1-4.bin	SC6K-SUP2-6.1.4
6.1(4) Flash image (CiscoView)	cat6000-sup2cv.6-1-4.bin	SC6K-SUP2CV-6.1.4
6.1(4) Flash image (Secure Shell)	cat6000-sup2k9.6-1-4.bin	SC6K-SUP2K9-6.1.4
6.1(4) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-4.bin	SC6K-SUP2CVK9-6.1.4
6.1(3a) Flash image	cat6000-sup2.6-1-3a.bin	SC6K-SUP2-6.1.3a
6.1(3a) Flash image (Secure Shell)	cat6000-sup2k9.6-1-3a.bin	SC6K-SUP2K9-6.1.3a
6.1(3) Flash image	cat6000-sup2.6-1-3.bin	SC6K-SUP2-6.1.3
6.1(3) Flash image (CiscoView)	cat6000-sup2cv.6-1-3.bin	SC6K-SUP2CV-6.1.3
6.1(3) Flash image (Secure Shell)	cat6000-sup2k9.6-1-3.bin	SC6K-SUP2K9-6.1.3
6.1(3) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-3.bin	SC6K-SUP2CVK9-6.1.3
6.1(2a) Flash image	cat6000-sup2.6-1-2a.bin	SC6K-SUP2-6.1.2a
6.1(2a) Flash image (Secure Shell)	cat6000-sup2k9.6-1-2a.bin	SC6K-SUP2K9-6.1.2a
6.1(2) Flash image	cat6000-sup2.6-1-2.bin	SC6K-SUP2-6.1.2
6.1(2) Flash image (CiscoView)	cat6000-sup2cv.6-1-2.bin	SC6K-SUP2CV-6.1.2
6.1(2) Flash image (Secure Shell)	cat6000-sup2k9.6-1-2.bin	SC6K-SUP2K9-6.1.2
6.1(2) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-2.bin	SC6K-SUP2CVK9-6.1.2
6.1(1e) Flash image	cat6000-sup2.6-1-1e.bin	SC6K-SUP2-6.1.1e
6.1(1e) Flash image (Secure Shell)	cat6000-sup2k9.6-1-1e.bin	SC6K-SUP2K9-6.1.1e
6.1(1d) Flash image	cat6000-sup2.6-1-1d.bin	SC6K-SUP2-6.1.1
6.1(1d) Flash image (CiscoView)	cat6000-sup2cv.6-1-1d.bin	SC6K-SUP2CV-6.1.1
6.1(1d) Flash image (Secure Shell)	cat6000-sup2k9.6-1-1d.bin	SC6K-SUP2K9-6.1.1
6.1(1d) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-1d.bin	SC6K-SUP2CVK9-6.1.1
6.1(1c) Flash image (Secure Shell)	cat6000-sup2k9.6-1-1c.bin	not orderable
6.1(1c) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-1c.bin	not orderable
6.1(1b) Flash image	cat6000-sup2.6-1-1b.bin	not orderable
6.1(1b) Flash image (CiscoView)	cat6000-sup2cv.6-1-1b.bin	not orderable
6.1(1b) Flash image (Secure Shell)	cat6000-sup2k9.6-1-1b.bin	not orderable
6.1(1b) Flash image (Secure Shell and CiscoView)	cat6000-sup2cvk9.6-1-1b.bin	not orderable
6.1(1a) Flash image	cat6000-sup2.6-1-1a.bin	not orderable
6.1(1a) Flash image (CiscoView)	cat6000-sup2cv.6-1-1a.bin	not orderable
Supervisor Engine 1
6.4(21) Flash image	cat6000-sup.6-4-21.bin	SC6K-SUP-6.4
6.4(21) Flash image (CiscoView)	cat6000-supcv.6-4-21.bin	SC6K-SUPCV-6.4
6.4(21) Flash image (Secure Shell)	cat6000-supk9.6-4-21.bin	SC6K-SUPK9-6.4
6.4(21) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-21.bin	SC6K-SUPCVK9-6.4
6.4(20) Flash image	cat6000-sup.6-4-20.bin	SC6K-SUP-6.4
6.4(20) Flash image (CiscoView)	cat6000-supcv.6-4-20.bin	SC6K-SUPCV-6.4
6.4(20) Flash image (Secure Shell)	cat6000-supk9.6-4-20.bin	SC6K-SUPK9-6.4
6.4(20) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-20.bin	SC6K-SUPCVK9-6.4
6.4(19) Flash image	cat6000-sup.6-4-19.bin	SC6K-SUP-6.4
6.4(19) Flash image (CiscoView)	cat6000-supcv.6-4-19.bin	SC6K-SUPCV-6.4
6.4(19) Flash image (Secure Shell)	cat6000-supk9.6-4-19.bin	SC6K-SUPK9-6.4
6.4(19) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-19.bin	SC6K-SUPCVK9-6.4
6.4(18) Flash image	cat6000-sup.6-4-18.bin	SC6K-SUP-6.4
6.4(18) Flash image (CiscoView)	cat6000-supcv.6-4-18.bin	SC6K-SUPCV-6.4
6.4(18) Flash image (Secure Shell)	cat6000-supk9.6-4-18.bin	SC6K-SUPK9-6.4
6.4(18) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-18.bin	SC6K-SUPCVK9-6.4
6.4(17) Flash image	cat6000-sup.6-4-17.bin	SC6K-SUP-6.4
6.4(17) Flash image (CiscoView)	cat6000-supcv.6-4-17.bin	SC6K-SUPCV-6.4
6.4(17) Flash image (Secure Shell)	cat6000-supk9.6-4-17.bin	SC6K-SUPK9-6.4
6.4(17) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-17.bin	SC6K-SUPCVK9-6.4
6.4(16) Flash image	cat6000-sup.6-4-16.bin	SC6K-SUP-6.4
6.4(16) Flash image (CiscoView)	cat6000-supcv.6-4-16.bin	SC6K-SUPCV-6.4
6.4(16) Flash image (Secure Shell)	cat6000-supk9.6-4-16.bin	SC6K-SUPK9-6.4
6.4(16) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-16.bin	SC6K-SUPCVK9-6.4
6.4(15) Flash image	cat6000-sup.6-4-15.bin	SC6K-SUP-6.4
6.4(15) Flash image (CiscoView)	cat6000-supcv.6-4-15.bin	SC6K-SUPCV-6.4
6.4(15) Flash image (Secure Shell)	cat6000-supk9.6-4-15.bin	SC6K-SUPK9-6.4
6.4(15) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-15.bin	SC6K-SUPCVK9-6.4
6.4(14) Flash image	cat6000-sup.6-4-14.bin	SC6K-SUP-6.4
6.4(14) Flash image (CiscoView)	cat6000-supcv.6-4-14.bin	SC6K-SUPCV-6.4
6.4(14) Flash image (Secure Shell)	cat6000-supk9.6-4-14.bin	SC6K-SUPK9-6.4
6.4(14) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-14.bin	SC6K-SUPCVK9-6.4
6.4(13) Flash image	cat6000-sup.6-4-13.bin	SC6K-SUP-6.4
6.4(13) Flash image (CiscoView)	cat6000-supcv.6-4-13.bin	SC6K-SUPCV-6.4
6.4(13) Flash image (Secure Shell)	cat6000-supk9.6-4-13.bin	SC6K-SUPK9-6.4
6.4(13) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-13.bin	SC6K-SUPCVK9-6.4
6.4(12) Flash image	cat6000-sup.6-4-12.bin	SC6K-SUP-6.4
6.4(12) Flash image (CiscoView)	cat6000-supcv.6-4-12.bin	SC6K-SUPCV-6.4
6.4(12) Flash image (Secure Shell)	cat6000-supk9.6-4-12.bin	SC6K-SUPK9-6.4
6.4(12) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-12.bin	SC6K-SUPCVK9-6.4
6.4(11) Flash image	cat6000-sup.6-4-11.bin	SC6K-SUP-6.4
6.4(11) Flash image (CiscoView)	cat6000-supcv.6-4-11.bin	SC6K-SUPCV-6.4
6.4(11) Flash image (Secure Shell)	cat6000-supk9.6-4-11.bin	SC6K-SUPK9-6.4
6.4(11) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-11.bin	SC6K-SUPCVK9-6.4
6.4(10) Flash image	cat6000-sup.6-4-10.bin	SC6K-SUP-6.4
6.4(10) Flash image (CiscoView)	cat6000-supcv.6-4-10.bin	SC6K-SUPCV-6.4
6.4(10) Flash image (Secure Shell)	cat6000-supk9.6-4-10.bin	SC6K-SUPK9-6.4
6.4(10) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-10.bin	SC6K-SUPCVK9-6.4
6.4(9) Flash image	cat6000-sup.6-4-9.bin	SC6K-SUP-6.4
6.4(9) Flash image (CiscoView)	cat6000-supcv.6-4-9.bin	SC6K-SUPCV-6.4
6.4(9) Flash image (Secure Shell)	cat6000-supk9.6-4-9.bin	SC6K-SUPK9-6.4
6.4(9) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-9.bin	SC6K-SUPCVK9-6.4
6.4(8) Flash image	cat6000-sup.6-4-8.bin	SC6K-SUP-6.4
6.4(8) Flash image (CiscoView)	cat6000-supcv.6-4-8.bin	SC6K-SUPCV-6.4
6.4(8) Flash image (Secure Shell)	cat6000-supk9.6-4-8.bin	SC6K-SUPK9-6.4
6.4(8) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-8.bin	SC6K-SUPCVK9-6.4
6.4(7) Flash image	cat6000-sup.6-4-7.bin	SC6K-SUP-6.4
6.4(7) Flash image (CiscoView)	cat6000-supcv.6-4-7.bin	SC6K-SUPCV-6.4
6.4(7) Flash image (Secure Shell)	cat6000-supk9.6-4-7.bin	SC6K-SUPK9-6.4
6.4(7) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-7.bin	SC6K-SUPCVK9-6.4
6.4(6a) Flash image	cat6000-sup.6-4-6a.bin	SC6K-SUP-6.4
6.4(6a) Flash image (CiscoView)	cat6000-supcv.6-4-6a.bin	SC6K-SUPCV-6.4
6.4(6a) Flash image (Secure Shell)	cat6000-supk9.6-4-6a.bin	SC6K-SUPK9-6.4
6.4(6a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-6a.bin	SC6K-SUPCVK9-6.4
6.4(6) Flash image	cat6000-sup.6-4-6.bin	SC6K-SUP-6.4
6.4(6) Flash image (CiscoView)	cat6000-supcv.6-4-6.bin	SC6K-SUPCV-6.4
6.4(6) Flash image (Secure Shell)	cat6000-supk9.6-4-6.bin	SC6K-SUPK9-6.4
6.4(6) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-6.bin	SC6K-SUPCVK9-6.4
6.4(5b) Flash image	cat6000-sup.6-4-5b.bin	SC6K-SUP-6.4
6.4(5b) Flash image (Secure Shell)	cat6000-supk9.6-4-5b.bin	SC6K-SUPK9-6.4
6.4(5a) Flash image	cat6000-sup.6-4-5a.bin	SC6K-SUP-6.4
6.4(5a) Flash image (Secure Shell)	cat6000-supk9.6-4-5a.bin	SC6K-SUPK9-6.4
6.4(5) Flash image	cat6000-sup.6-4-5.bin	SC6K-SUP-6.4
6.4(5) Flash image (CiscoView)	cat6000-supcv.6-4-5.bin	SC6K-SUPCV-6.4
6.4(5) Flash image (Secure Shell)	cat6000-supk9.6-4-5.bin	SC6K-SUPK9-6.4
6.4(5) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-5.bin	SC6K-SUPCVK9-6.4
6.4(4a) Flash image	cat6000-sup.6-4-4a.bin	SC6K-SUP-6.4.4a
6.4(4a) Flash image (CiscoView)	cat6000-supcv.6-4-4a.bin	SC6K-SUPCV-6.4.4a
6.4(4a) Flash image (Secure Shell)	cat6000-supk9.6-4-4a.bin	SC6K-SUPK9-6.4.4a
6.4(4a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-4a.bin	SC6K-SUPCVK9-6.4.4a
6.4(4) Flash image	cat6000-sup.6-4-4.bin	SC6K-SUP-6.4.4
6.4(4) Flash image (CiscoView)	cat6000-supcv.6-4-4.bin	SC6K-SUPCV-6.4.4
6.4(4) Flash image (Secure Shell)	cat6000-supk9.6-4-4.bin	SC6K-SUPK9-6.4.4
6.4(4) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-4.bin	SC6K-SUPCVK9-6.4.4
6.4(3) Flash image	cat6000-sup.6-4-3.bin	SC6K-SUP-6.4.3
6.4(3) Flash image (CiscoView)	cat6000-supcv.6-4-3.bin	SC6K-SUPCV-6.4.3
6.4(3) Flash image (Secure Shell)	cat6000-supk9.6-4-3.bin	SC6K-SUPK9-6.4.3
6.4(3) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-3.bin	SC6K-SUPCVK9-6.4.3
6.4(2) Flash image	cat6000-sup.6-4-2.bin	SC6K-SUP-6.4.2
6.4(2) Flash image (CiscoView)	cat6000-supcv.6-4-2.bin	SC6K-SUPCV-6.4.2
6.4(2) Flash image (Secure Shell)	cat6000-supk9.6-4-2.bin	SC6K-SUPK9-6.4.2
6.4(2) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-2.bin	SC6K-SUPCVK9-6.4.2
6.4(1) Flash image	cat6000-sup.6-4-1.bin	SC6K-SUP-6.4.1
6.4(1) Flash image (CiscoView)	cat6000-supcv.6-4-1.bin	SC6K-SUPCV-6.4.1
6.4(1) Flash image (Secure Shell)	cat6000-supk9.6-4-1.bin	SC6K-SUPK9-6.4.1
6.4(1) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-4-1.bin	SC6K-SUPCVK9-6.4.1
6.3(10) Flash image	cat6000-sup.6-3-10.bin	SC6K-SUP-6.3.10
6.3(10) Flash image (CiscoView)	cat6000-supcv.6-3-10.bin	SC6K-SUPCV-6.3.10
6.3(10) Flash image (Secure Shell)	cat6000-supk9.6-3-10.bin	SC6K-SUPK9-6.3.10
6.3(10) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-10.bin	SC6K-SUPCVK9-6.3.10
6.3(9) Flash image	cat6000-sup.6-3-9.bin	SC6K-SUP-6.3.9
6.3(9) Flash image (CiscoView)	cat6000-supcv.6-3-9.bin	SC6K-SUPCV-6.3.9
6.3(9) Flash image (Secure Shell)	cat6000-supk9.6-3-9.bin	SC6K-SUPK9-6.3.9
6.3(9) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-9.bin	SC6K-SUPCVK9-6.3.9
6.3(8) Flash image	cat6000-sup.6-3-8.bin	SC6K-SUP-6.3.8
6.3(8) Flash image (CiscoView)	cat6000-supcv.6-3-8.bin	SC6K-SUPCV-6.3.8
6.3(8) Flash image (Secure Shell)	cat6000-supk9.6-3-8.bin	SC6K-SUPK9-6.3.8
6.3(8) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-8.bin	SC6K-SUPCVK9-6.3.8
6.3(7) Flash image	cat6000-sup.6-3-7.bin	SC6K-SUP-6.3.7
6.3(7) Flash image (CiscoView)	cat6000-supcv.6-3-7.bin	SC6K-SUPCV-6.3.7
6.3(7) Flash image (Secure Shell)	cat6000-supk9.6-3-7.bin	SC6K-SUPK9-6.3.7
6.3(7) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-7.bin	SC6K-SUPCVK9-6.3.7
6.3(6) Flash image	cat6000-sup.6-3-6.bin	SC6K-SUP-6.3.6
6.3(6) Flash image (CiscoView)	cat6000-supcv.6-3-6.bin	SC6K-SUPCV-6.3.6
6.3(6) Flash image (Secure Shell)	cat6000-supk9.6-3-6.bin	SC6K-SUPK9-6.3.6
6.3(6) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-6.bin	SC6K-SUPCVK9-6.3.6
6.3(5) Flash image	cat6000-sup.6-3-5.bin	SC6K-SUP-6.3.5
6.3(5) Flash image (CiscoView)	cat6000-supcv.6-3-5.bin	SC6K-SUPCV-6.3.5
6.3(5) Flash image (Secure Shell)	cat6000-supk9.6-3-5.bin	SC6K-SUPK9-6.3.5
6.3(5) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-5.bin	SC6K-SUPCVK9-6.3.5
6.3(4a) Flash image	cat6000-sup.6-3-4a.bin	SC6K-SUP-6.3.4a
6.3(4a) Flash image (CiscoView)	cat6000-supcv.6-3-4a.bin	SC6K-SUPCV-6.3.4a
6.3(4a) Flash image (Secure Shell)	cat6000-supk9.6-3-4a.bin	SC6K-SUPK9-6.3.4a
6.3(4a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-4a.bin	SC6K-SUPCVK9-6.3.4a
6.3(4) Flash image	cat6000-sup.6-3-4.bin	SC6K-SUP-6.3.4
6.3(4) Flash image (CiscoView)	cat6000-supcv.6-3-4.bin	SC6K-SUPCV-6.3.4
6.3(4) Flash image (Secure Shell)	cat6000-supk9.6-3-4.bin	SC6K-SUPK9-6.3.4
6.3(4) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-4.bin	SC6K-SUPCVK9-6.3.4
6.3(3)x1 Flash image	cat6000-sup.6-3-3X1.bin	SC6K-SUP-6.3.3X1
6.3(3)x Flash image	cat6000-sup.6-3-3X.bin	SC6K-SUP-6.3.3X
6.3(3a) Flash image	cat6000-sup.6-3-3a.bin	SC6K-SUP-6.3.3a
6.3(3a) Flash image (CiscoView)	cat6000-supcv.6-3-3a.bin	SC6K-SUPCV-6.3.3a
6.3(3a) Flash image (Secure Shell)	cat6000-supk9.6-3-3a.bin	SC6K-SUPK9-6.3.3a
6.3(3a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-3a.bin	SC6K-SUPCVK9-6.3.3a
6.3(3) Flash image	cat6000-sup.6-3-3.bin	SC6K-SUP-6.3.3
6.3(3) Flash image (CiscoView)	cat6000-supcv.6-3-3.bin	SC6K-SUPCV-6.3.3
6.3(3) Flash image (Secure Shell)	cat6000-supk9.6-3-3.bin	SC6K-SUPK9-6.3.3
6.3(3) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-3.bin	SC6K-SUPCVK9-6.3.3
6.3(2a) Flash image	cat6000-sup.6-3-2a.bin	SC6K-SUP-6.3.2a
6.3(2a) Flash image (CiscoView)	cat6000-supcv.6-3-2a.bin	SC6K-SUPCV-6.3.2a
6.3(2a) Flash image (Secure Shell)	cat6000-supk9.6-3-2a.bin	SC6K-SUPK9-6.3.2a
6.3(2a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-2a.bin	SC6K-SUPCVK9-6.3.2a
6.3(2) Flash image	cat6000-sup.6-3-2.bin	SC6K-SUP-6.3.2
6.3(2) Flash image (CiscoView)	cat6000-supcv.6-3-2.bin	SC6K-SUPCV-6.3.2
6.3(2) Flash image (Secure Shell)	cat6000-supk9.6-3-2.bin	SC6K-SUPK9-6.3.2
6.3(2) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-2.bin	SC6K-SUPCVK9-6.3.2
6.3(1a) Flash image	cat6000-sup.6-3-1a.bin	SC6K-SUP-6.3.1a
6.3(1a) Flash image (Secure Shell)	cat6000-supk9.6-3-1a.bin	SC6K-SUPK9-6.3.1a
6.3(1) Flash image2	cat6000-sup.6-3-1.bin	SC6K-SUP-6.3.1
6.3(1) Flash image (CiscoView)	cat6000-supcv.6-3-1.bin	SC6K-SUPCV-6.3.1
6.3(1) Flash image (Secure Shell)	cat6000-supk9.6-3-1.bin	SC6K-SUPK9-6.3.1
6.3(1) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-3-1.bin	SC6K-SUPCVK9-6.3.1
6.2(3a) Flash image	cat6000-sup.6-2-3a.bin	SC6K-SUP-6.2.3a
6.2(3a) Flash image (Secure Shell)	cat6000-supk9.6-2-3a.bin	SC6K-SUPK9-6.2.3a
6.2(3) Flash image	cat6000-sup.6-2-3.bin	SC6K-SUP-6.2.3
6.2(3) Flash image (CiscoView)	cat6000-supcv.6-2-3.bin	SC6K-SUPCV-6.2.3
6.2(3) Flash image (Secure Shell)	cat6000-supk9.6-2-3.bin	SC6K-SUPK9-6.2.3
6.2(3) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-2-3.bin	SC6K-SUPCVK9-6.2.3
6.2(2a) Flash image	cat6000-sup.6-2-2a.bin	SC6K-SUP-6.2.2a
6.2(2a) Flash image (CiscoView)	cat6000-supcv.6-2-2a.bin	SC6K-SUPCV-6.2.2a
6.2(2a) Flash image (Secure Shell)	cat6000-supk9.6-2-2a.bin	SC6K-SUPK9-6.2.2a
6.2(2a) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-2-2a.bin	SC6K-SUPCVK9-6.2.2a
6.2(2) Flash image	cat6000-sup.6-2-2.bin	SC6K-SUP-6.2.2
6.2(2) Flash image (CiscoView)	cat6000-supcv.6-2-2.bin	SC6K-SUPCV-6.2.2
6.2(2) Flash image (Secure Shell)	cat6000-supk9.6-2-2.bin	SC6K-SUPK9-6.2.2
6.2(2) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-2-2.bin	SC6K-SUPCVK9-6.2.2
6.1(4b) Flash image	cat6000-sup.6-1-4b.bin	SC6K-SUP-6.1.4b
6.1(4b) Flash image (Secure Shell)	cat6000-supk9.6-1-4b.bin	SC6K-SUPK9-6.1.4b
6.1(4) Flash image	cat6000-sup.6-1-4.bin	SC6K-SUP-6.1.4
6.1(4) Flash image (CiscoView)	cat6000-supcv.6-1-4.bin	SC6K-SUPCV-6.1.4
6.1(4) Flash image (Secure Shell)	cat6000-supk9.6-1-4.bin	SC6K-SUPK9-6.1.4
6.1(4) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-1-4.bin	SC6K-SUPCVK9-6.1.4
6.1(3a) Flash image	cat6000-sup.6-1-3a.bin	SC6K-SUP-6.1.3a
6.1(3a) Flash image (Secure Shell)	cat6000-supk9.6-1-3a.bin	SC6K-SUPK9-6.1.3a
6.1(3) Flash image	cat6000-sup.6-1-3.bin	SC6K-SUP-6.1.3
6.1(3) Flash image (CiscoView)	cat6000-supcv.6-1-3.bin	SC6K-SUPCV-6.1.3
6.1(3) Flash image (Secure Shell)	cat6000-supk9.6-1-3.bin	SC6K-SUPK9-6.1.3
6.1(3) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-1-3.bin	SC6K-SUPCVK9-6.1.3
6.1(2a) Flash image	cat6000-sup.6-1-2a.bin	SC6K-SUP-6.1.2a
6.1(2a) Flash image (Secure Shell)	cat6000-supk9.6-1-2a.bin	SC6K-SUPK9-6.1.2a
6.1(2) Flash image	cat6000-sup.6-1-2.bin	SC6K-SUP-6.1.2
6.1(2) Flash image (CiscoView)	cat6000-supcv.6-1-2.bin	SC6K-SUPCV-6.1.2
6.1(2) Flash image (Secure Shell)	cat6000-supk9.6-1-2.bin	SC6K-SUPK9-6.1.2
6.1(2) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-1-2.bin	SC6K-SUPCVK9-6.1.2
6.1(1e) Flash image	cat6000-sup.6-1-1e.bin	SC6K-SUP-6.1.1e
6.1(1e) Flash image (Secure Shell)	cat6000-supk9.6-1-1e.bin	SC6K-SUPK9-6.1.1e
6.1(1c) Flash image (Secure Shell)	cat6000-supk9.6-1-1c.bin	SC6K-SUPK9-6.1.1
6.1(1c) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-1-1c.bin	SC6K-SUPCVK9-6.1.1
6.1(1b) Flash image3	cat6000-sup.6-1-1b.bin	not orderable
6.1(1b) Flash image (CiscoView)	cat6000-supcv.6-1-1b.bin	not orderable
6.1(1b) Flash image (Secure Shell)	cat6000-supk9.6-1-1b.bin	not orderable
6.1(1b) Flash image (Secure Shell and CiscoView)	cat6000-supcvk9.6-1-1b.bin	not orderable
6.1(1a) Flash image	cat6000-sup.6-1-1a.bin	not orderable
6.1(1a) Flash image (CiscoView	cat6000-supcv.6-1-1a.bin	not orderable

1 Installed on system; append with "=" for spare on floppy media.

Software Image Version Compatibility

With high-availability versioning enabled, you can have two different but compatible images on the active and standby supervisor engines. The active supervisor engine exchanges image version information with the standby supervisor engine and determines whether the images are compatible for enabling high availability. If the active and standby supervisor engines are not running compatible image versions, you cannot enable high availability.

Image versioning is supported in supervisor engine software releases 5.4(1) and later. With versioning enabled, high availability is fully supported with the active and standby supervisor engines running different images as long as the images are compatible. The only fully compatible images are as follows:

•Supervisor Engine 1

–5.5(3) and 5.5(4)

–6.1(3) and 6.1(4)

–6.2(2) and 6.2(3)

–6.3(2) and 6.3(3)

–6.3(4) and 6.3(5)

–6.3(6) and 6.3(7)

•Supervisor Engine 2

–6.1(3) and 6.1(4)

–6.2(2) and 6.2(3)

–6.3(2) and 6.3(3)

Images that are compatible with all modules except Gigabit Ethernet switching modules are as follows:

•Supervisor Engine 1

–5.4(3) and 5.4(4)

–5.5(3) and 5.5(5)

–5.5(4) and 5.5(5)

Images that are compatible with Gigabit Ethernet switching modules but not compatible with 10/100BASE-T modules are as follows:

•Supervisor Engine 1

–5.5(6a) and 5.5(7)

Images that are compatible with all modules except the SFM/SFM2 and fabric-enabled modules are as follows:

•Supervisor Engine 2

–6.3(4) and 6.3(5)

–6.3(6) and 6.3(7)

---

Note Attempting to run incompatible image versions could result in configuration loss.

---

Catalyst 6000 Family Features

These sections describe the Catalyst 6000 family features:

•Features for Supervisor Engine Software Release 6.4

•Features for Supervisor Engine Software Release 6.3

•Features for Supervisor Engine Software Release 6.2

•Features for Supervisor Engine Software Release 6.1

•Features for Supervisor Engine Software Release 5.5

•Features for Supervisor Engine Software Release 5.4

•Features for Supervisor Engine Software Release 5.3

•Features for Supervisor Engine Software Release 5.2

•Features for Supervisor Engine Software Release 5.1

Features for Supervisor Engine Software Release 6.4

These sections describe the features in software release 6.4, 21 January, 2003:

•Software Release 6.4 Hardware Features

•Software Release 6.4 Software Features

---

Note Maximum switching performance is achieved when all switch components are fabric enabled. The presence of nonfabric-enabled switching modules might impact overall switching performance.

---

Software Release 6.4 Hardware Features

Software release 6.4 provides initial support for these modules:

•48-port 10/100BASE-TX RJ-45 with 128K per-port packet buffers (WS-X6148-RJ-45V provides inline power to IP telephones)

•48-port 10/100BASE-TX RJ-21 with 128K per-port packet buffers (WS-X6148-RJ21V provides inline power to IP telephones)

---

Note Software releases 6.1(1) and later do not support the same Flash PC card format as earlier software releases. To use a Flash PC card with software releases 6.1(1) and later, format the card with software releases 6.1(1) and later.

---

Software Release 6.4 Software Features

Software release 6.4 provides support for these software features:

•In software release 6.4(11) and later releases, improved supervisor engine failover rates with high availability enabled are as follows: In flow through, truncated, and compact modes, the Supervisor Engine 1 and Supervisor Engine 2 failover time is less than 500 ms.

•NVRAM monitoring

The NVRAM monitoring feature is a background process that allows the system to recover when data in NVRAM is corrupted.

Features for Supervisor Engine Software Release 6.3

These sections describe the features in software release 6.3:

•Software Release 6.3 Hardware Features

•Software Release 6.3 Software Features

---

Note Maximum switching performance is achieved when all switch components are fabric enabled. The presence of nonfabric-enabled switching modules might impact overall switching performance.

---

Software Release 6.3 Hardware Features

There is no new hardware being introduced in software release 6.3.

---

Note Software releases 6.1(1) and later do not support the same Flash PC card format as earlier software releases. To use a Flash PC card with software releases 6.1(1) and later, format the card with software releases 6.1(1) and later.

---

Software Release 6.3 Software Features

Software release 6.3 provides support for these software features:

•Single router mode (SRM) redundancy

SRM redundancy is an alternative to having both MSFC2s in a chassis active at the same time.

Note that SRM redundancy requires Cisco IOS Release 12.1(8a)E2 and SRM redundancy configuration information will be available when Release 12.1(8a)E2 is posted to Cisco.com. At that time, refer to the "Configuring Redundancy" chapter of the online version of the Catalyst 6000 Family Software Configuration Guide, Release 6.3, for detailed configuration procedures.

•Private VLANs on the sc0 interface

The sc0 management interface can be assigned to a private VLAN.

•EtherChannel enhancements

An EtherChannel is preserved even if it contains only one port. In software releases prior to 6.3(1), if you have a 2-port channel and one link is removed, the remaining link is removed and added back to spanning tree, which causes a loss of connection on the channel until the link is forwarding again.

•Text file configuration mode

When you use 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 entered by you to configure various features.

•Support for NetFlow version 8

•CDPv2 enhancements

–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 "old-style" format (as in the device hardware serial number).

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

•Increase QoS ACLs

The maximum number of QoS ACLs that can be stored in NVRAM has been increased from 250 to 500. The maximum number of security ACLs (VACLs) remains the same at 250.

•Ethernet link debounce timer feature

The debounce time is the time a module's firmware waits before notifying the supervisor engine of a link change at the physical layer when a link goes down. If the link is up and then goes down and remains down for a time interval longer than the debounce time, then the supervisor engine is notified. As soon as the link is up again, the timer is reset. If the link is down and then goes up, the supervisor engine is notified immediately. The debounce timer value is hard-coded in the supervisor engine depending upon the type of module being used. The link debounce feature can be enabled on a per-port basis on Ethernet modules.

•Display SNMPv3 counters using the CLI

Use the CLI to display SNMPv3 counters for various MIBs.

•Autostate enhancements

A VLAN interface will not transition to the up state until at least one port in the VLAN is forwarding traffic.

•SNMPv3 enhancements

The SNMPv3 implementation in software releases prior to 6.3(1) supports RFC 2271 through
RFC 2275. RFC 2271 through RFC 2275 were replaced with RFC 2571 through RFC 2576. The SNMPv3 enhancement in software release 6.3(1) implements RFC 2571 through RFC 2576.

•Support for the following MIBs:

–CISCO-AAA-CLIENT-MIB

–CISCO-CATOS-ACL-QOS-MIB

–CISCO-CAT6K-CROSSBAR-MIB

–CISCO-STP-EXTENSION-MIB

–CISCO-SWITCH-ENGINE-MIB

–CISCO-SYSTEM-MIB enhancement

Features for Supervisor Engine Software Release 6.2

These sections describe the features in software release 6.2:

•Software Release 6.2 Hardware Features

•Software Release 6.2 Software Features

---

Note Maximum switching performance is achieved when all switch components are fabric enabled. The presence of nonfabric-enabled switching modules might impact overall switching performance.

---

Software Release 6.2 Hardware Features

Software release 6.2 provides initial support for these modules:

•WS-C6513
Catalyst 13-slot chassis

---

Note The WS-C6513 chassis is supported with Supervisor Engine 2 only.

---

---

Note The WS-C6513 chassis has 64 MAC addresses. The MAC address reduction feature is enabled by default on this chassis.

---

•WS-X6500-SFM 2
Switch Fabric Module version 2

•WS-X6516-GE-TX
16-port 10/100/1000BASE-TX fabric-enabled Ethernet module

•WS-X6548-RJ-45
48-port 10/100BASE-TX fabric-enabled Ethernet module

•WS-X6548-RJ-21
48-port 10/100BASE-TX fabric-enabled Ethernet module

•WS-X6348-RJ21V
48-port 10/100BASE-TX Ethernet module with inline power

---

Note Software releases 6.1(1) and later do not support the same Flash PC card format as earlier software releases. To use a Flash PC card with software releases 6.1(1) and later, format the card with software releases 6.1(1) and later.

---

Software Release 6.2 Software Features

Software release 6.2 provides support for these software features:

•QoS minimum threshold for WRED

Allows you to configure the minimum threshold for WRED.

•QoS queuing for port type 1p1q0t/1p3q1t

Allows queuing on ports that support 1p1q0t/1p3q1t.

•Non-RPF MFD (Multicast Fast Drop)

Non-RPF multicast fast drop (MFD) rate limits packets that fail the RPF check (non-RPF packets) and drops the majority of the non-RPF packets in hardware.

•Multicast suppression for Gigabit Ethernet modules

Suppresses multicast traffic on Gigabit Ethernet ports to prevent the ports from being disrupted by a broadcast storm.

•QoS data export

The QoS statistics data export feature generates per port and per aggregate policer utilization information and forwards this information in UDP packets to traffic monitoring, planning, or accounting applications.

•VACL logging of access denied

Allows you to configure a log option on any VACL, so that packets or flows that are access denied by the VACL will be redirected to supervisor engine CPU to generate a report.

•Bidirectional VACLs for Private VLANs

Lets you create a policy that denies access in or out of a network.

•Per-port utilization of QoS statistics

Provides the input and output packet rate and input and output byte rate on a per-port basis.

•TCAM test on bootup

The system performs a TCAM test during bootup.

•Dynamic VLAN support with auxiliary VLANs.

Prior to software release 6.2(2), 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(2) 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)

•BPDU packet filtering

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

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

•BPDU skew detection

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

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

•Local command accounting

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

•MSFC Autostate Disable

Allows you to disable Autostate. The auto state feature shuts down (or brings up) Layer 3 interfaces/subinterfaces on the MSFC and the Multilayer Switch Module (MSM) when the port configuration changes occur on the switch.

•Redundancy enhancement

Enhanced redundancy provides more efficient system fault detection and recovery mechanisms.

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

•Support for the following MIBs:

–HC-RMON MIB enhancement

–Cisco STP-EXTENSIONS-MIB enhancements

–Cisco PRIVATE-VLAN-MIB

–Cisco ACL-QoS-MIB

–Cisco QoS-Policy-MIB

Features for Supervisor Engine Software Release 6.1

These sections describe the features in software release 6.1:

•Software Release 6.1 Hardware Features

•Software Release 6.1 Software Features

---

Note Maximum switching performance is achieved when all switch components are fabric enabled. The presence of nonfabric-enabled switching modules might impact overall switching performance.

---

Software Release 6.1 Hardware Features

Software release 6.1(2) provides initial support for these modules:

•2- and 4-port OC-12 POS Optical Services Modules

•8- and 16- port OC-3 POS Optical Services Modules

Software release 6.1 provides initial support for these modules:

•Supervisor Engine 2—Policy Feature Card 2 (PFC2; shipped only on Supervisor Engine 2)
WS-X6K-S2-MSFC2 or WS-X6K-S2-PFC2
Dual 1000BASE-X GBIC uplinks, fabric-enabled, Cisco Express Forwarding (CEF), enhanced QoS features, PFC2, and MSFC2

–The Cisco IOS unicast RPF feature is supported in hardware on the PFC2. For ACL-based RPF checks, traffic that matches the RPF ACL is forwarded to the MSFC2.

–Supervisor Engine 2 and PFC2 do not support ASLB.

•Switch Fabric Module
WS-C6500-SFM
Supports fabric-enabled modules.

---

Note The WS-C6500-SFM is not supported in the WS-C6513 chassis.

---

•Fabric-enabled 16-port Gigabit Ethernet GBIC switching module
WS-X6516-GBIC

•Intrusion Detection System Module
WS-X6381-IDS

---

Note Software releases 6.1(1) and later do not support the same Flash PC card format as earlier software releases. To use a Flash PC card with software releases 6.1(1) and later, format the card with software releases 6.1(1) and later.

---

Software Release 6.1 Software Features

Software release 6.1 provides support for these software features:

•CEF for PFC2—Supervisor Engine 2 and PFC2 provide IP and IPX unicast and IP multicast Layer 3 switching with Cisco Express Forwarding implemented on the PFC2.

•Jumbo frame feature enhancement—You can configure the jumbo frame feature on any Ethernet port and on EtherChannels and trunk ports.

---

Note With Cisco IOS Release 12.1(2)E or later, you can configure support for jumbo frames on MSFC2 VLAN interfaces.

---

•EtherChannel enhancements with PFC2—On a Supervisor Engine 2 with PFC2, you can configure the EtherChannel feature to distribute IP traffic based on Layer 4 port numbers in addition to Layer 3 addresses. With both Supervisor Engine 1 and 2, you can enter the show channel traffic command to display EtherChannel traffic.

•Globally disable EtherChannel—Enter the set port channel all mode off command to disable all EtherChannels on the switch.

•Globally disable trunking—Enter the set trunk all off command to disable all trunks on the switch.

•VMPS server—The Catalyst 6000 family switch can function as a VMPS server.

•4096 VLANs—Catalyst 6000 family switches support 4096 VLANs in accordance with the IEEE 802.1Q standard.

•Reduced MAC address usage—The MAC address reduction feature is used to enable extended-range VLAN identification. When MAC address reduction is enabled, it disables the pool of MAC addresses used for the VLAN spanning tree, leaving a single MAC address that identifies the switch.

---

Note The MAC address reduction feature is enabled by default on Cisco switches that have 64 MAC addresses (Cisco 7606, CISCO7603, WS-C6503, and WS-C6513).

---

•Multi-Instance Spanning Tree Protocol (MISTP)—MISTP allows you to group multiple VLANs under a single instance of spanning tree. MISTP combines the Layer 2 load-balancing benefits of PVST+ with the lower CPU load of IEEE 802.1Q.

•Spanning Tree Protocol 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.

•IEEE 802.1Q tunneling—802.1Q tunneling allows multiple VLANs in other VTP domains to be carried by a single VLAN on the Catalyst 6000 family switch without losing their unique VLAN IDs.

•Enhanced ACL configuration with private VLANs—ACLs can be applied as follows:

–VACLs can be mapped to secondary VLANs or primary VLANs.

–Cisco IOS ACLs that are mapped to a primary VLAN will get mapped to the associated secondary VLANs.

–Cisco IOS ACLs cannot be mapped to secondary VLANs.

–Dynamic ACEs cannot be mapped to a private VLAN.

–QoS ACLs can be mapped to secondary VLANs or primary VLANs.

•Secure Shell (SSH) encryption—The SSH feature provides security for Telnet sessions to the switch. SSH encryption supports 3DES encryption and can be used in conjunction with RADIUS and TACACS+ authentication (requires a "k9" image).

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

•Cisco IOS-like ping—The -s argument in the Cisco IOS-like 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 would produce a continuous ping.

•Layer 2 Traceroute—The Layer 2 Traceroute utility allows you to identify the physical path that a packet takes 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.

•write tech-support command—The write tech-support command allows you to generate a report with status information about your switch. You can upload this report to a TFTP server and send it to Cisco TAC.

•Search on More prompt—At the More prompt during a show command, enter a slash character ("/") followed by a text string to search for text.

•Clearing counters on a per-port basis—The clear counters command clears MAC and port counters.

•Enhanced support for scripting—The switch assumes a positive ("yes") answer to all the confirmation prompts when configured from a configuration file.

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

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

Features for Supervisor Engine Software Release 5.5

These sections describe the new features available in software release 5.5:

•Software Release 5.5 Hardware Features

•Software Release 5.5 Software Features

Software Release 5.5 Hardware Features

This section describes the new hardware component available in software release 5.5:

•24-port FXS analog interface module (WS-X6224-FXS)—Provides a standard RJ-21 Category 5 telco connector to connect directly to standard analog telephones or fax machines. The module interfaces supply ring voltage and dial tone. The module emulates the central office (CO) or private branch exchange (PBX) because it provides a service to an analog telephone or fax machine. The telephone or fax machine connected through the FXS module behaves as if it is connected to a normal CO or PBX line. The module requires an IP address, is registered with Cisco CallManager in its domain, and is managed by Cisco CallManager.

•8-port T1/E1 PSTN interface modules (WS-X6608-E1, WS-X6608-T1)—High-density, eight port, T1/E1 VoIP module that can support both digital T1/E1 connectivity to the PSTN or transcoding and conferencing. The module requires an IP address, is registered with Cisco CallManager in its domain, and is managed by Cisco CallManager.

Download the module software from a TFTP server. Depending upon which software you download, the ports can serve as T1/E1 interfaces or the ports will support transcoding and conferencing.

•Network Analysis Module (WS-X6380-NAM)—Monitors and analyzes network traffic for the Catalyst 6000 family switches using RMON, RMON2, and other MIBs. The RMON support that the NAM provides for Ethernet VLANs is an extension of the RMON support provided by the
Catalyst 6000 family supervisor engine. The switched port analyzer (SPAN) selects network traffic and directs it to the NAM. TrafficDirector, or any other IETF-compliant RMON application, can analyze link characteristics, packet layers for capacity planning or departmental accounting, differentiated service deployment and policies, and filter/capture packets for debugging.

•Catalyst 6000 Family Inline-Power Patch Panel (WS-PWR-PANEL)—Works with any Cisco 10/100 Mbps switching product capable of supporting IP telephones. The inline-power patch panel eliminates the need for external power sources; it is a standalone chassis that can be colocated with the Catalyst 6000 family switch to provide -48 VDC power directly to the telephone through existing Catalyst family 10/100BASE-TX switching modules. When used with an uninterruptible power supply (UPS), the inline-power patch panel can provide power to the telephone even in a power failure. The inline-power patch panel has 48 RJ-45 input ports and 48 RJ-45 output ports. There are two RJ-45 connectors per port for a total of 48 ports.

•Inline-power field-upgrade module (WS-F6K-VPWR)—Mounts on the 48-port 10/100BASE-TX RJ-45 module (WS-X6348-RJ-45) and provides -48 VDC inline power on all ports.

•2500W AC-input power supply (WS-CAC-2500W).

Software Release 5.5 Software Features

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

Numerous software features are introduced in this release to support configuring a voice-over-IP (VoIP) network using the Catalyst 6000 family voice-related hardware described in the previous section.

For detailed information on the Catalyst 6000 family VoIP software, refer to the "Configuring a Voice-over-IP Network" chapter of the Catalyst 6000 Family Software Configuration Guide publication.

Features for Supervisor Engine Software Release 5.4

These sections describe the new features available in software release 5.4:

•Software Release 5.4 Hardware Features

•Software Release 5.4 Software Features

Software Release 5.4 Hardware Features

This section describes the new hardware component available in software release 5.4.

•16-port Gigabit Ethernet module (WS-X6416-GBIC)—Provides 16 switched, full-duplex Gigabit Ethernet ports that you can configure with any combination of 1000BASE-SX, LX/LH, and ZX GBICs. Ports have SC-type connectors for MMF and SMF.

•FlexWAN module (WS-X6182-2PA)—Delivers flexible support for a wide range of Cisco 7200/7500 WAN port adapters. Two port adapters per FlexWAN module are supported, scaling from T1/E1 to OC-3 interfaces and including protocol support for Frame Relay, ATM, Packet over SONET, PPP, and HDLC. The FlexWAN module resides in a single slot of any Catalyst 6000 family switch and has no slot dependencies or limitations. The FlexWAN module works in conjunction with the Policy Feature Card (PFC) on the supervisor engine of the Catalyst 6000 family switch to deliver wire-speed security access control, distributed quality of service (QoS), and granular traffic management functionality.

---

Note To use the FlexWAN module, you must have a supervisor engine with an MSFC and PFC. You configure the FlexWAN module through the MSFC. For information regarding the FlexWan module, refer to the Catalyst 6000 Family FlexWAN Module Installation and Configuration Note.

---

•48-port 10/100BASE-TX RJ-45 Ethernet module (WS-X6348-RJ-45)—Provides 128K per-port packet buffers and accepts a field-upgradable voice daughter card in a future release to provide inline power to IP telephones.

•48-port 10/100 telco RJ-21 Ethernet module (WS-X6248A-TEL)—Provides 128K per-port packet buffers.

•8-port Gigabit Ethernet module (WS-X6408A-GBIC)—Provides enhanced QoS features.

•24-port 100FX multimode MT-RJ Ethernet module (WS-X6324-100FX-MT)—Provides 128K per-port packet buffers.

•16-port 1000BASE-TX RJ-45 Gigabit Ethernet module (WS-X6316-GE-TX)—Provides Gigabit connectivity using standard Category 5 UTP cabling.

•Catalyst Web Interface (CWI)—A browser-based tool that you can use to configure the Catalyst 6000, 5000, and 4000 family switches. It consists of a graphical user interface (GUI) that runs on the client (a Catalyst version of CiscoView 5.0) and a Hypertext Transfer Protocol (HTTP) server that runs on the switch. A GUI alternative to the CLI and SNMP interfaces, the CWI provides a real-time graphical representation of the switch and detailed information such as port status, module status, type of chassis, and modules. The CWI uses HTTP to download CiscoView from the server to the client.

---

Note For information on installing and using the CWI, refer to the Catalyst 6000, 5000, and 4000 Family Switches Web Interface Installation and Configuration Note publication.

---

Software Release 5.4 Software Features

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

•High availability—Provides improved switchover time from the active supervisor engine to the standby supervisor engine by synchronizing the standby supervisor engine with the active supervisor engine. In the event of a switchover, the standby can take over and continue exactly where the failed supervisor engine left off. The high-availability feature also provides a versioning option. High-availability versioning allows you to have two different but compatible images on the active and standby supervisor engines. The active supervisor engine exchanges image version information with the standby supervisor engine and determines whether the images are compatible for enabling high availability.

•UDLD enhancements—With supervisor engine software releases 5.4(3) and later, you can specify the message interval between UDLD messages. Previously, the message interval was fixed at 60 seconds. With a configurable message interval, UDLD reacts much faster to link failures.

Additionally, releases 5.4(3) and later have UDLD aggressive mode. UDLD aggressive mode is disabled by default and its use is recommended only for point-to-point links between Cisco switches running software release 5.4(3) or later. With aggressive mode enabled, when a port on a bidirectional link stops receiving UDLD packets, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is put into errdisable state.

In order to prevent spanning tree loops, normal UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to forwarding state (when default spanning tree parameters are used).

Enabling UDLD aggressive mode provides additional benefits in the following cases:

–One side of a link has a port stuck (both Tx and Rx)

–One side of a link remains up while the other side of the link has gone down

In these cases, UDLD aggressive mode errdisables one of the ports on the link and stops the blackholing of traffic. Even with aggressive mode disabled, there would have been no risk for a broadcast storm due to a spanning tree loop in this situation, as one port is unable to pass traffic in both directions.

For detailed information on configuring the message interval and UDLD aggressive mode, refer to the online version of the Catalyst 6000 Family Software Configuration Guide, Release 5.4.

•RADIUS authorization and accounting—Provides client-server authentication and accounting for users attempting to connect to the switch.

•TACACS+ authorization and accounting—Provides client-server authentication and accounting for access to network devices.

•Generic summertime—Allows you to configure non-US summertime.

•NTP enhancements—Trusted Key and Authorization supports the trusted key option where NTP time updates are only accepted from hosts with the correct key.

•Errdisable timeout—Allows you to automatically enable or reset a port minutes after a port is disabled by the software due to excessive errors.

•Case-sensitive password—Allows you to set case-sensitive passwords.

•IP permit list enhancements—Increases the number of IP entries allowed and provides you with the capability to configure separate permit lists for Telnet and SNMP traffic.

•Banner improvement—Increases the banner string to 3,070 characters long and includes a tab character.

•Scheduled reset—Allows you to reset the switch at a specified date and time.

•Permanent ARP entries—Allows you to save a static ARP entry in the NVRAM (or Flash) configuration file so a reset or power cycle does not clear the entry.

•Private VLANs—Sets of ports that have the features of normal VLANs and also provide some
Layer 2 isolation from other ports on the Catalyst 6000 family switch.

•Port security enhancements and single device per port:

–Increases the number of learned and configurable MAC addresses for port security to 1 MAC address per port and 1024 shared MAC addresses.

–Supports an option to automatically enable/reset the port N minutes after a port security violation lockdown.

–Provides an option to allow port security to automatically enable or reset the port on a link down instead of after a timeout. (NOT supported)

–Supports aging on the learned address to allow a new MAC address to use switch port after a configurable aging time in minutes.

•Kerberos Telnet—Provides support for encrypted Telnet sessions on the switch using Kerberos.

•DHCP client and rcp—Allows the switch to obtain its IP configuration from a DHCP server automatically and provides an alternative method for copying system software image files and configuration files over the network using remote copy (rcp).

•Command completion—Allows you to use the tab key to automatically complete unambiguous commands.

•Show configuration nondefault and default filename for the device configuration file—Allows you to specify nondefault values only in the show config command.

•Configure from Flash on startup—Allows the switch to use a configuration file on Flash instead of NVRAM.

•show tech-support command—Allows you to capture all of the information and statistics required by Cisco TAC for the entire device.

•set port host command—Essentially a CLI macro that executes these commands: set spantree portfast enable, set trunk off, and set port channel off. This new command will provide a quick and convenient way to configure host/access ports to a mode that allows the port to forward traffic in less than one second from link up.

•VLAN 1 disable on trunks—Allows you to disable VLAN 1 on any individual VLAN trunk link.

•PortFast guard—Provides a means to shut the port down when any received BPDUs are detected.

•RGMP support—Allows the switch to forward IP multicast traffic to only those multicast routers that are interested in receiving the traffic, thus offloading the multicast router from unnecessary packet processing and improving the network bandwidth.

---

Note The MSFC supports RGMP in Release 12.1(1)E or later.

---

•IGMP fast leave—Provides a mechanism to leave multicast sessions without any latency.

•Disable port startup option—Allows you to specify the default operation for all ports to be shut down, and once set, in the event of a complete configuration erase or a corrupted configuration, no traffic will be transmitted through the switch.

•Diagnostics options on bootup—Provides options to bypass all diagnostics completely, run a minimal set, or run the complete set.

•Capture capability with VACLs—Allows you to capture selective traffic and redirect it to one or multiple ports to which an Intrusion Detection appliance(s) can be connected.

•SNMPv3—Provides security and remote configuration capabilities of SNMPv3.

•Improved SNMP response time—Minimizes the response time for the SNMP subsystem in the Catalyst 6000 family switch.

•External LDA with the internal router—Supports the internal router as the default router.

•QoS ACL and VACL configuration from Flash memory—Configures and stores ACLs in Flash memory instead of NVRAM.

•System log messages for backplane traffic, low memory conditions, memory corruption, NVRAM conditions, inband communication errors, and TCP/UDP errors.

Features for Supervisor Engine Software Release 5.3

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

•UniDirectional Link Detection (UDLD)—Detects unidirectional connections on both copper and fiber-optic links.

•RADIUS authentication—Provides client-server authentication for users attempting to connect to the switch.

•Jumbo frame support for intra-VLAN traffic on Gigabit Ethernet links increases the MTU size to 9216 bytes (note that jumbo frames cannot be routed or fragmented for transmission through slower ports).

•Virtual Management Policy Server (VMPS) client support allows network administrators to define the VLAN membership policies for their network in a central database so that the switch automatically configures user ports to the correct VLAN.

•With the single-port OC-12 ATM Module (SMF or MMF):

–Reassembly of up to 255 buffers simultaneously (each buffer represents a packet)

–Support for up to 4096 virtual circuits

–Support for AAL 5

–ATM LANE 1.0, including LEC, LES, BUS, and LECS

–MPOA support

•On switches with a Policy Feature Card (PFC):

---

Note IPX VACLs, QoS ACLs, COPS-DS, and RSVP for Qualitative Service were introduced in software release 5.3(1a)CSX but were not fully tested; you were instructed not to use them. These features can be used in software releases 5.3(3)CSX or later as they have been fully tested.

---

–VLAN access control lists (VACLs) using IP, IPX, and MAC ACLs.

A VACL enhancement in software release 5.3(3)CSX is as follows:

A VACL redirect ACE allows a unicast flow to be specified.

–Common Open Policy Service (COPS) for Differentiated Services (DS) allows QoS to be configured from a central policy decision point server.

–Resource ReSerVation Protocol (RSVP) for Qualitative Service allows hosts to request QoS.

–Remote SPAN (RSPAN) supports source and destination SPAN ports on other compatible switches.

–Quality of service (QoS) supports classification, marking, and policing using IP, IPX, and MAC ACLs.

–Accelerated server load balancing (ASLB) support enables Catalyst 6000 family switches to cache Cisco LocalDirector load-balancing flows, accelerating the performance of the LocalDirector, which is a network appliance with a secure, real-time, embedded operating system that intelligently load balances IP traffic across multiple servers (refer to the Catalyst 6000 Family Accelerated Server Load Balancing Installation and Configuration Note).

ASLB enhancements in software release 5.3(3)CSX are as follows:

A TCP port can be a wildcard (0).

Up to 1024 virtual-IP addresses and TCP port pairs are supported.

---

Note Accelerated server load balancing was previously called LocalDirector Accelerator in these release notes.

---

•On switches with a Multilayer Switch Feature Card (MSFC):

–IP Multilayer Switching (MLS) provides high-performance hardware-based Layer 3 switching of IP unicast traffic, offloading processor-intensive IP packet routing from network routers.

–IP Multicast Multilayer Switching (IP MMLS) provides high-performance hardware-based Layer 3 switching of IP multicast traffic, offloading processor-intensive IP multicast packet routing from network routers.

–IPX MLS provides high-performance hardware-based Layer 3 switching of IPX unicast traffic, offloading processor-intensive IPX packet routing from network routers. Provides standard and extended Cisco IOS access control lists (ACLs) at wire rate.

–NetFlow Data Export (NDE) allows a summary of intersubnet Layer 3 traffic statistics for all expired flows to be periodically exported to a network management data collector.

---

Note Refer to the Release Notes for Catalyst 6000 Family Multilayer Switch Feature Card for more information.

---

Features for Supervisor Engine Software Release 5.2

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

•GARP VLAN Registration Protocol (GVRP; see IEEE 802.1p) provides 802.1Q-compliant VLAN pruning and dynamic VLAN creation on 802.1Q trunk ports.

•GARP Multicast Registration Protocol (GMRP; see IEEE 802.1p) maintains Layer 2 multicast groups that determine which switch ports need to participate in multicasts.

•EtherChannel frame distribution is configurable with Layer 2 Switching Feature Card II (WS-F6020A) and can use either Media Access Control (MAC) addresses or IP addresses and either source or destination or both source and destination addresses.

Enter a show module command for the supervisor engine to determine if EtherChannel frame distribution is configurable on your switch. If the display shows the "Sub-Type" to be "L2 Switching Engine I WS-F6020," then EtherChannel frame distribution is not configurable on your switch; it uses source and destination MAC addresses. EtherChannel frame distribution is configurable with any other switching engine and the default is to use source and destination IP addresses.

•The Spanning Tree Protocol can be enabled and disabled on a per-VLAN basis.

Features for Supervisor Engine Software Release 5.1

This section describes the features available in software release 5.1:

•Initial support for the Catalyst 6000 family switches

•Redundant supervisor engines (uplink ports are fully functional on a redundant supervisor engine in standby mode)

•IP supernetting, compatible with classless interdomain routing (CIDR)

•EtherChannel (maximum of eight ports) on all Ethernet ports on all modules, including those on a standby supervisor engine, with no requirement that ports be contiguous or on the same module

•Up to 1024 VLANs

•VLAN Trunk Protocol (VTP)

•Inter-Switch Link (ISL) and 802.1Q VLAN trunking on all Ethernet ports on all modules

•Per-VLAN Spanning Tree Protocol, STP PortFast, STP UplinkFast, and STP BackboneFast

•802.1Q-to-ISL VLAN mapping of up to eight 802.1Q VLANs numbered above 1005 to ISL VLANs

•Quality of Service (QoS)

•For transmitted traffic, up to four SPAN sessions; for received or both transmitted and received traffic, up to two SPAN sessions

•SNMP, SNMP v2C, SNMP traps, and Remote Monitoring (RMON)

•Switch TopN reports

•Cisco Discovery Protocol (CDP)

•System message logs

Usage Guidelines and Restrictions

These sections provide usage guidelines and restrictions for the Catalyst 6000 family switches:

•System and Supervisor Engine

•Modules and Switch Ports

•EtherChannel

•Quality of Service

•Multicast

•Spanning Tree

•Access Control

•High Availability

•Multilayer Switching

•MIBs

•VLANs, VTP, and VLAN Trunks

•Authentication, Authorization, and Accounting

•Auto-MDI/MDIX

•CiscoView Images

System and Supervisor Engine

This section contains usage guidelines, restrictions, and troubleshooting information that apply to the supervisor engine and to the switch at the system level:

•With software releases 6.4(11) and later, after a switchover, the newly active supervisor engine might display the following message:

Unable to message Standby Supervisor to Disable consistency checker

This problem is due to a shortage of memory for setting ROMMON variables.

Workaround: Either clear some of the ROMMON variables or reduce the boot string to only the essential images using the set boot system flash command. (CSCef42081)

•The WS-C6K-9SLOT-FAN2 fan tray is supported in all chassis (except for the 3-slot chassis) and all software releases. The minimum power supply requirement is 2500W. It is important that you determine the power requirements for your hardware configuration to ensure that your switch has adequate power for all modules. To determine power requirements, refer to the CCO power calculator at this URL: http://www.cisco.com/go/powercalculator.

•MAC addresses—Theoretical and recommended limits for PFC/PFC2: 128K theoretical maximum, 32K recommended.

•The standby use-bia option should not be used in an HSRP configuration. MLS entries are not created when you use the standby use-bia option. When the standby use-bia option is configured, if an HSRP active interface goes up and down, there will be no router CAM address for the standby VLAN interface. Without the router CAM entry, no shortcuts are created. This problem is independent of any MSFC Cisco IOS release. (CSCdz17169)

•In extremely rare conditions, the following configuration might cause the supervisor engine to reset when the MSFC2 is reloaded:

–Supervisor Engine 2 (with MSFC2) running supervisor engine software release 6.2(2) or 6.3(1)

–FlexWAN module with ATM port adapter

–Unicast RPF enabled on VLAN interfaces

The workaround is to disable unicast RPF on the VLAN interfaces. (CSCdv20407)

•In a redundant supervisor engine configuration, both supervisors must be running the same boot ROM version. For information on upgrading the boot ROM version, refer to the Catalyst 6000 Family Supervisor Engine 2 Boot ROM and Bootflash Device Upgrade Installation Note at this URL:

/en/US/docs/switches/lan/catalyst6500/hardware/Config_Notes/78_12667.html#xtocid41960

•For Supervisor Engine 1, the minimum boot ROM required for software release 5.4(1) and later releases is 5.3(1). For Supervisor Engine 2, the minimum boot ROM required for software release 6.2(2) and later releases is 6.1(3).

•IPX Layer-3 switched traffic with a SAP encapsulation type (Novell Ethernet 802.2) to non-SAP encapsulation type (Novell Ethertype's: Ethernet 802.3, Ethernet II, and Ethernet SNAP) and vice versa, follows the software forwarding path (via MSFC/MSFC2) on the PFC and PFC2 forwarding engines. This might cause high CPU utilization on the MSFC/MSFC2. The workaround is to avoid SAP to non-SAP and vice versa encapsulation changes when doing IPX Layer 3 switching.

•When a Supervisor Engine 2 is running in truncated mode with QoS enabled and policers configured, the traffic subject to policing that is received on a fabric-enabled switching module destined to a non-fabric-enabled switching module is overpoliced. The traffic is policed to half the value configured in the policer. (CSCds02280)

•When you reset the supervisor engine from a Telnet connection, the connection will not get dropped and will appear as though Telnet is frozen. To back out from the Telnet session, you need to manually disconnect the Telnet connection using the escape commands of the Telnet program. (CSCdp32220)

•If you perform a manual switchover or reset a switch while high-availability events are waiting in the queue of the standby supervisor engine, when the events will be completely processed is not known, and all configurations might not synchronize to the standby supervisor engine properly. (High availability events are the result of changing the configuration through the CLI.) We suggest that after changing the configuration, you allow additional time before resetting the switch to allow the supervisor engine to process all synchronized events. (CSCdp59261)

•With a PFC2, traffic that matches an egress reflexive ACL is handled by the MSFC2 as a partially switched flow. (CSCds09775)

•Changing the console port baud rate from 19,200 to 38,400 incorrectly sets the console port to 9600 baud. After a reset, the console port baud rate is 38,400. Changing the rate to 38,400 from any other setting works correctly. (CSCdk86876)

•In extremely rare conditions, if you enter the show module command, the status of the MSFC on the standby supervisor engine might be displayed as other. This has no impact on MSFC behavior and you should ignore this display. (CSCdp87997)

•With PFC or PFC2 and a standard network topology as shown below where you have multicast senders in the core and multicast receivers on the access layer:

		Layer 3 distribution No. 1
	/		\
Layer 2 access				Core
	\		/
		Layer 3 distribution No. 2

If both distribution switches have two supervisor engines and MSFCs and are configured to provide multicast functionality for the same access VLANs, then you will see high CPU utilization on the non-DR routers due to non-RPF traffic. (CSCdr74908)

•If you configure aging for UDP, it could slow down the removal of TCP entries belonging to a terminated connection. You might see entries no longer used in the NetFlow table being aged with the regular aging time of all the NetFlow entries, instead of the very fast LDA aging. The workaround is to enable the fast UDP aging only when really needed (for example, when load balancing UDP). (CSCdp79475)

•In a system with a Supervisor Engine 2 and WS-X6101 (ATM LANE) modules, ACLs configured from the CLI or COPS on the ATM LANE module ingress ports do not work. (CSCds09425)

•With Supervisor Engine 1 and PFC, online diagnostic failures are experienced on modules during boot up, online insertion, or module reset if you reconfigure the QoS default-action MAC ACL to include an aggregate policer with an action of drop. The system default does not include an aggregate policer in the default-action MAC ACL. The likelihood of the diagnostics failures increases as the amount of traffic being policed (dropped) by that aggregate policer increases. As the rate value specified in the policer decreases, the amount of traffic matching all ACLs specifying that aggregate policer increases. (CSCdp15471)

---

Note For switches with Supervisor Engine 2 and PFC2, CSCdp15471 is resolved in software release 6.1(1a).

---

Modules and Switch Ports

This section contains usage guidelines, restrictions, and troubleshooting information that apply to modules and switch ports:

•It is possible to power down a Switch Fabric Module from the CLI before it comes online but we do not support this action. Powering down a Switch Fabric Module while it is coming online can cause conflicting switching mode change operations to occur simultaneously which can result in delays in restoring the data path and unpredictable switch behavior. This Switch Fabric Module behavior is not going to be addressed by any hardware or software modifications. Rather, we are advising you to wait to power down a Switch Fabric Module until it comes online.

•At bootup some non-Ethernet modules (such as MSFC, WAN modules, and service modules) may fail to come online. This problem is seen especially in fully loaded chassis. The workaround is to manually reset each module that fails to come online at bootup. (CSCed24552)

•With software release 6.4(7), new CLI commands have been developed to deal with packet buffer memory errors that could occur with the WS-X6248-RJ-45, WS-X6348-RJ-45, and WS-X6348-RJ45V modules (these errors are documented in CSCec37610).

You are given two options to deal with these errors. The first option is to put the ports with this error condition in err-disable state. The second option is to power cycle the module. Putting the ports in the errdisable state is configured as the default. Additionally, there is a new err-disable-timeout cause: packet-buffer-error. The new CLI is as follows:

Console>(enable) set errordetection packet-buffer ?

errdisable

powercycle

Console>(enable) set errordetection packet-buffer errdisable 

Packet buffer error detection set to errdisable. 

Console>(enable) set errordetection packet-buffer powercycle 

Packet buffer error detection set to powercycle. 

Console>(enable)

Console> show errordetection 

Inband error detection: 	  disabled

Memory error detection:        disabled

Port counter error detection:  disabled

Packet buffer error detection: powercycle 

Console> show errdisable-timeout 

ErrDisable Reason           Timeout Status

----------------------      -------------------

bpdu-guard                  disable

channel-misconfig           disable

duplex-mismatch             disable

udld                        disable

crossbar-fallback           disable

packet-buffer-error         disable

other                       disable

Interval: 300 seconds

Port      ErrDisable Reason

-----      -----------------------

5/1         packet-buffer-error

5/2         packet-buffer-error

5/3         packet-buffer-error

5/4         packet-buffer-error

•The broadcast suppression counter undercounts packets that have a size evenly divisible by 16:

–A 64-byte packet should be counted as 4 but is counted as 3

–65- to 79-byte packets are correctly counted as 4

–An 80-byte packet should be counted as 5 but is counted as 4

–81- to 95-byte packets are correctly counted as 5

–A 96-byte packet should be counted as 6 but is counted as 5

This problem is seen on modules with the four-port Gigabit interface ASIC.

(CSCdr56784)

•A SPAN session with a 10/100 source port and a Gigabit destination port might result in duplicated packets on the destination port. (CSCea32926)

•The 8-port T1 PSTN interface module (WS-X6608-T1) voice ports will not retain their configuration across switch reboots if the switch is in text config mode. The workaround is to manually configure the T1 voice module after each switch reset. This problem only applies if the switch is in text config mode. (CSCdv04864)

•When the WS-X6548-RJ-45 is operating at 10Mb mode, pre-1994 NICs on ports 7, 15, 23, 31, and 39 may have connectivity problems. If these ports are having connectivity problems, as a workaround, enable auto-polarity detection in the NIC driver (where this is available) or use any of the other module ports. For additional information, refer to CSCdx15951.

•When you connect a Cisco IP Phone 7960 to a port on the 10/100 Ethernet switching module that supplies inline power, the phone might lose power after switching from wall power back to inline power. The link remains up but the phone is down. This problem only occurs at 10 Mbps. The workaround is to disconnect and then reconnect the cable between the switch port and the phone. (CSCdr37056)

•If a module fails to come online after a software upgrade, as a workaround, reset the module to bring it online. (CSCdu77125)

•When a module is reset due to a firmware download, the module may take 30 to 50 seconds (depending on the type of module) to come online and another 2 to 30 seconds (depending upon whether PortFast is configured or not) for spanning tree related events.

•The Distributed Forwarding Card (WS-F6K-DFC) and 16-port Gigabit Ethernet switching module (WS-X6816-GBIC) are not supported in systems running Catalyst software on the supervisor engine and Cisco IOS only on the MSFC. These items are supported on systems running
Cisco IOS Release 12.1(5c)EX or later on both the Supervisor Engine 2 and the MSFC2. For more information, refer to the Release Notes for 12.1(5c)EX on Cisco.com:

http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/ios121_e/78_12505.htm

•You cannot reset individual ports on WS-X6608-T1 or -E1 modules. To reset a port, reset the module. (CSCds19417)

•When you hot insert a module into a Catalyst 6000 or 6500 series chassis, be sure to use the ejector levers on the front of the module to seat the backplane pins properly. Inserting a module without using the ejector levers might cause the supervisor engine to display incorrect messages about the module.

If you see minor hardware failures or sync errors on bootup, reconfirm that the supervisor engine and all the switching modules are fully seated, the ejector levers are fully depressed, and the thumbscrews are fully tightened.

•There is a cabling issue with the 48-port 10/100BASE-TX switching module (WS-X6248-TEL). The WS-X6248-TEL module RJ-21 connectors do not support Category 3 RJ-21 telco connectors and cabling. Using Category 3 connectors and cabling causes carrier sense errors. The connectors are keyed for Category 5 telco connectors and cables. You must use Category 5 RJ-21 telco connectors and cables.

•24-port 100FX switching modules (WS-X6224-100FX-MT) with a hardware version of 1.1 or lower only support IEEE 802.1Q VLAN trunking; they do not support ISL trunking. Do not configure ISL trunks on 24-port 100FX switching modules (WS-X6224-100FX-MT) with a hardware version of 1.1 or lower. The restriction against ISL VLAN trunking is the only known problem with hardware version 1.1 or lower of these modules. If you do not require ISL VLAN trunking, these modules are fully functional. The ISL VLAN trunking problem has been corrected in hardware version 1.2 or later of these modules. If you wish to return a WS-X6224-100FX-MT module with a hardware version of 1.1 or lower, contact Cisco Systems.

You can identify WS-X6224-100FX-MT hardware versions using one of the following two methods:

–Command-line interface (CLI) method—Use the show version command to identify the hardware version of the WS-X6224-100FX-MT module as follows:

Console> show version

< ... output truncated ... >

Mod Port Model               Serial #    Versions

--- ---- ------------------- ----------- --------------------------------------

< ... output truncated ... >

5   24   WS-X6224-100FX-MT   SAD02470006 Hw : 1.1

< ... output truncated ... >

Console>

The example shows a WS-X6224-100FX-MT module with a hardware version of 1.1; this version does not support ISL VLAN trunking.

–Physical inspection method—Look for the part number that is printed on a label on the outer edge of the component side of the module. Versions 73-3245-04 or lower do not support ISL trunking.

•When multiple instances are configured over a LANE trunk and when the root for one of the instances is moved, the other instances stop receiving BPDUs. The fix for this problem will be available in an Cisco IOS release for the ATM LANE module later than Release 12.1(2)E1. (CSCdr88794)

•The show module command might show different versions for different modules in the chassis when upgraded with versioning enabled. (CSCdr55665)

•The following debounce timer command options have been added to increase the jitter tolerance on 10/100 UTP ports to make them interoperable with out-of-spec NICs:
set option debounce enable—Sets debounce to 3.1 seconds on 10/100 cards.
set option debounce disable—Sets debounce to 300 ms. The default is 300 ms debounce.
(CSCdp56343)

EtherChannel

This section contains usage guidelines, restrictions, and troubleshooting information that apply to EtherChannel:

•When you enable UplinkFast, the EtherChannel port path cost (set with the set channel cost command) for a 4-port 10/100 EtherChannel is less than the port path cost of a parallel Gigabit Ethernet link. This situation causes the slower 4-port EtherChannel to forward and the Gigabit Ethernet link to block. The workaround is to explicitly configure a higher cost for the EtherChannel after enabling UplinkFast. (CSCds22895)

•Catalyst switches running supervisor engine software releases 6.2(x) and later cannot form a channel with HP-Server NICs. TLV checking, which was added for PAgP packets in software release 6.2(1), uncovered a problem with HP-UX systems where the packet length was set incorrectly. HP has an updated driver available that can solve the problem; contact HP Technical Support for details. (CSCdu84575)

Quality of Service

This section contains usage guidelines, restrictions, and troubleshooting information that apply to QoS:

•The rate and burst parameters for microflow/aggregate policing are specified in terms of Kbps (kilo-bits-per-second) and Kb (kilo bits). However, the following should be noted:

–Rate specification—1 Kbps is equivalent to 1000 bits-per-second (as opposed to 1024 bits-per-second)

–Burst specification—1 Kb is equivalent to 1024 bits

•When you configure standard QoS receive-queue tail-drop thresholds, do not set the threshold 4 value less than 75 percent. Failure to do so might cause packets to be dropped on ports that are associated with the queue. (CSCdu75029)

•The set port qos mod/port {port-based | vlan-based} command configures all ports on switching modules with 1p1q0t/1p3q1t QoS port architecture.

•In extremely rare circumstances in a Catalyst 6000 family switch with two Supervisor Engine 2s, if you have more than 300 QoS ACLs and each is mapped to a different VLAN, the active supervisor engine might reset after clearing all the QoS ACLs and then committing the change. There is no workaround. (CSCdu85021)

•Microflow policing does not support policing of identical flows arriving on different interfaces simultaneously. Attempts to do so lead to incorrectly policed flows. (CSCdt72147)

•If there is an error in installing any COPS policy, a successful commit is sent to the PDP even if the policy was not correctly installed. In such situations, any modifications to the port's role combination does not install the correct policy on the port and might result in a switch reset. (CSCdp66572)

•If you create a security ACL with the redirect option and then replace the module that has the redirect port with another kind of module, the security ACL does not have the redirect port list anymore. The workaround is to manually modify the security ACL with the new redirect port information. (CSCdp74757)

•If you download a COPS ACL containing a policer to the switch and the switch cannot support the exact rate/burst supplied by the policer, no message informs you that the rate/burst was rounded off to the nearest value that the hardware could support. (CSCdr28715)

•Catalyst 6000 family switches do not support non-zero WRED minimum values. If a COPS QPM server sends down a COPS policy with a non-zero WRED minimum value, no error report is returned to the COPS server. As a result, there is no indication to the user that the WRED minimum specified in the COPS policy was not used. (CSCdr28819)

•COPS and RSVP are not supported in software release 6.2(2).

•On a Catalyst 6000 family switch, when the switch QoS policy source is COPS, no COPS roles are defined for a port, and the port policy source is COPS, the values that you set for the QoS configuration (such as queue mappings and sizes) are inappropriate. For example, all CoS values get mapped to the strict-priority queue on a 1P2Q2T or 1P1Q4T port type. This situation can lead to bandwidth starvation for other ports in the switch, especially, if these ports with a strict-priority queue are generating high rates of traffic. The workaround to avoid this problem is to either configure a COPS role on all ports in the switch or configure all ports without a COPS role to use local policy. (CSCdp44965)

•If a large number of QoS ACLs are defined on the system during switch boot up, some packets might get switched before the QoS ACLs are installed in hardware. This scenario would result in some packets getting an incorrect ToS or no policing applied. After the QoS ACLs are installed in hardware, the correct ToS and policers are applied. It is considered inappropriate to block traffic from flowing until all the QoS policy is installed. (CSCdp68608)

•After setting the QoS policy source to local, you might need to wait approximately 20 seconds before the QoS policy source can be set back to COPS. (CSCdp34367)

•The COPS policy fails to install on ports with a large number of QoS policers. The workaround is to unmap the local ACLs before installing the COPS policy. (CSCdp63138)

•Use the QoS strict-priority queues for your highest-priority traffic only. The strict-priority queues are designed to accommodate only a limited volume of traffic. If you overload the strict-priority queues, the supervisor engine cannot service the standard queues. (CSCdm90683)

•With QoS disabled, an EtherChannel can contain ports with both strict-priority queues and ports without strict-priority queues. With QoS enabled, an EtherChannel cannot contain both port types. If you enable QoS, ports drop out of any EtherChannels that contain both port types.

•When COPS is the QoS policy source, TFTP traffic and switching might be affected if a COPS policer is configured with a rate or burst value that the Catalyst 6000 family switch cannot support. (CSCds16976)

•Except for ports that support 1p1q0t/1p3q1t, the set port qos trust command and the trust-ipprec and trust-dscp port keywords are not supported on 10-, 10/100-, and 100-Mbps ports. Instead, configure ACLs with the trust-cos, trust-dscp, and trust-ipprec ACE keywords. Note that the trust-cos port keyword can be used on 10-, 10/100-, and 100-Mbps ports to enable receive-queue drop thresholds.

•To avoid the case where all traffic is out of profile, the burst size specified in a QoS policing rule must be at least as large as the maximum packet size permissible in the traffic to which the rule is applied.

•With heavy COPS protocol traffic between either the COPS-DS client or the COPS-RSVP client and the PDP, it is possible for a connection keep-alive timeout event to occur and for the COPS connection manager to miss a Client Close from the PDP. When this happens, the switch might have an exception later. (CSCdp64213)

Multicast

This section contains usage guidelines, restrictions, and troubleshooting information that apply to multicast protocols and traffic on the switch:

•A new command, set igmp ratelimit [disable | enable], has been added to the 6.x, 7.x, and 8.x software releases starting with the following releases:

–6.4(7)

–7.6(5)

–8.2(1)

IGMP rate limiting is disabled by default. In the 6.4(x) software release, rate-limit counters are supported only in text configuration mode. The set igmp ratelimit [disable | enable] command is supported in both text and binary configuration modes in all software release trains.

If IGMP rate limiting and multicast are enabled, multicast router ports might age out sporadically because the rate of the multicast control packets (such as PimV2-hellos or IGMP-General Queries) exceed the IGMP rate-limit watermarks that were configured. The default values for these watermarks is 100. The workaround (documented in CSCea44331) is to increase the PimV2-hellos rate limit; we recommend that you set the value to 3000 using the set igmp ratelimit pimv2 3000 command. You can also increase the IGMP-General Queries rate limit; we recommend that you set the value to 500 using the set igmp ratelimit general-query 500 command.

•If a host sends an IGMPv1 report during the max-query-response-interval (the default is 10 seconds) after another host sends an IGMPv2 report, the IGMPv1 report will be suppressed by the supervisor engine and connected routers will not see this report. This situation can result in connected routers not falling back to IGMPv1 compatibility mode. Later, if an IGMPv2 host sends an IGMP Leave, the routers will send IMGPv2 GS queries in response (which IGMPv1 hosts do not understand). If there are no other IGMPv2 hosts for this group on the VLAN, then the router removes this VLAN from its outgoing interface list. (CSCdu83776)

•The Cisco IOS last-member-query-interval command allows you to increase the time that the router waits for host responses to IGMP GS queries (group-specific queries). The switch implements this interval statically, as defined in RFC 2236 (the default is 1000 ms). If a router connected to the switch is configured with a "last-member-query-interval" that is greater than the default interval that is defined in RFC 2236, and IGMP snooping is enabled on the switch, then hosts connected to the switch might have packets discarded if these hosts are unable to respond to GS queries within the interval implemented on the switch. Currently, the supervisor engine software does not modify its behavior based on the last-member-query-interval configured on connected routers. Therefore, there is no benefit to modifying the last-member-query-interval on routers that are connected to the switch if IGMP snooping is enabled. The workaround is to disable IGMP snooping on the switch. (CSCdu72041)

•Bridged IP multicast traffic is not policed if an MSFC2 is installed and the VLAN interface defined on the MSFC2 is in shutdown mode. (CSCdu12731)

•With software releases 6.3(2) and later, the maximum number of Layer 2 multicast entries is 15488.

•If RGMP-enabled routers connected to an RGMP-enabled Catalyst 6000 family switch join many groups, the switch might run out of memory. Ensure that the total number of entries displayed by the show rgmp group count command is fewer than 800. The actual maximum number of entries will vary depending on the features enabled on the Catalyst 6000 family switch and the amount of memory installed.

•When a multicast goes to both bridged and routed addresses, the multicast packets going to the routed addresses are Layer 3 switched, and the multicast matches an ACL so that QoS rewrites the ToS byte in the multicast packet. QoS does not rewrite the ToS byte for the multicast packets that are bridged.

•We recommend that you do not use more than 1500 multicast groups with GMRP. This restriction does not apply to IGMP.

•The maximum number of supported multicast CAM entries is 124. After adding 124 permanent or static multicast CAM entries the switch produces the error "Failed to add CAM entry." After adding 124 static or permanent CAM entries, all attempts to add more static or permanent multicast entries fail. This is true for the same port/same VLAN, different port/same VLAN, and different port/different VLAN.

•In extremely rare conditions, multicast traffic might be blocked due to a mismatch between hardware and software entries. (CSCdp81324)

•Be aware of the following multicast traffic caveats specific to Supervisor Engine 2 (these caveats apply to all software releases supporting Supervisor Engine 2):

–If an outgoing IOS ACL is configured on an interface, Supervisor Engine 2 based systems will match/apply the IOS ACL in software. This results in all outgoing multicast flows for that interface being handled in software (based upon specific deny/permit all statements). MMLS is effectively disabled for the interface. Be aware that handling outgoing IOS ACLs in software increases CPU utilization.

–Outgoing VACLs are not applied to multicast traffic with Supervisor Engine 2.

Spanning Tree

This section contains usage guidelines, restrictions, and troubleshooting information that apply to Spanning Tree:

•If the forward delay, max age, and hello time Spanning Tree Protocol (STP) parameters are reduced in value, ensure that the number of instances of STP are also reduced proportionally to avoid STP loops in the network.

•Occasionally (less than once in every 100 attempts), the console process might lock when an STP mode changes from PVST+ to MISTP. The only workaround is to reset the switch. (CSCds20952)

•If you have a Catalyst switch in your network with MAC address reduction enabled, you should also enable MAC address reduction on all other Layer-2 connected switches to avoid undesirable root election and spanning tree topology issues.

When MAC address reduction is enabled, the root bridge priority becomes a multiple of 4096 plus the VLAN ID. With MAC address reduction enabled, a switch bridge ID (used by the spanning-tree algorithm to determine the identity of the root bridge, the lowest being preferred) can only be specified as a multiple of 4096. Only the following values are possible: 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, and 61440.

Therefore, if another bridge in the same spanning-tree domain does not run the MAC address reduction feature, it could claim and win root bridge ownership because of the finer granularity in the selection of its bridge ID.

---

Note The MAC address reduction feature is enabled by default on Cisco switches that have 64 MAC addresses (Cisco 7606, CISCO7603, WS-C6503, and WS-C6513).

---

Access Control

This section contains usage guidelines, restrictions, and troubleshooting information that apply to access control:

•The packets that are sent to the MSFC as a result of a bridge action from an ACL are not rate limited. Only those packets that are sent to the MSFC from a FIB hit are rate limited. (CSCdr99239)

•Note that VACLs provide access control for all traffic passing through a VLAN. This includes broadcast traffic and packets going to and from the router. Therefore, you must use care when defining a VACL.

For example, to allow traffic from a local IPX client (daf11511) to a remote server (daf00402), the following VACL is configured (remote server is learned through a routing protocol):

set security acl ipx jg_ipx_permit

 ---------------------------------------------------

 1. permit any DAF00402 DAF11511 

 2. permit any DAF11511 DAF00402 

 3. permit any DAF01023 DAF01023 

 4. permit any DAF11511 0 

 5. permit any 0 0 

 6. permit any DAF11511 DAF11511 

The VACL description is as follows:

–1, 2. Allow IPX between client and server.

–3. The router needs to see the RIP/SAP packets.

–4. If packets are dropped during a connection, the client tries to find another route to the server by sending out RIP requests to IPX network 0.ffff.ffff.ffff. Not doing this results in a lost connection after packet drop.

–5. Upon startup, a client sends its first packets to 0.ffff.ffff.ffff and uses 0.ffff.ffff.ffff as its one IPX address.

–6. When a server connection socket is timed out, the client reconnects by sending a request to its local network to find its server.

As the example shows, just 1 and 2 is not enough; you also have to define 3 through 6 to achieve the goal. (CSCdm55828)

•Make sure that the redirect port defined in a VACL is on the same VLAN as the "incoming" VLAN for the packet that is to be redirected. Otherwise, the redirected packet will be dropped.

For example, a redirect VACL is defined on VLAN 5 and the redirect destination port is also on VLAN 5. If an MLS entry is destined to VLAN 5, packets that are coming from VLAN 2 hit this MLS entry and also hit the VACL redirect ACE (both VLAN 2 and VLAN 5 ACLs will be checked) and are redirected in the incoming VLAN, VLAN 2. The redirect destination port will drop them on VLAN 5 rather than on VLAN 2.

High Availability

This section contains usage guidelines, restrictions, and troubleshooting information that apply to high availability:

•In software release 6.4(11) and later releases, improved supervisor engine failover rates with high availability enabled are as follows: In flow through, truncated, and compact modes, the Supervisor Engine 1 and Supervisor Engine 2 failover time is less than 500 ms.

•Prior to enabling Single Router Mode (SRM) on the MSFC, you must enable high availability on the supervisor engine. Currently, no syslog message is generated when SRM is enabled and high availability is disabled on the supervisor engine. In supervisor engine software releases 6.3(2) and later releases, if you enable SRM and high availability is disabled on the supervisor engine, a syslog message displays indicating that you must enable high availability before you enable SRM. Failure to do so could result in unexpected system behavior. (CSCdu78927)

•High availability does not support use of the Reset button. Pressing the Reset button to initiate a switchover results in a high-availability switchover failure. The workaround is to make the active supervisor engine the standby supervisor engine first, and then remove it from the chassis. (CSCdp76806)

•NVRAM synchronization and high-availability synchronization does not work between supervisor engine software release 6.3(1) and any later version. (CSCdv43206)

•In extremely rare conditions, when upgrading an image (image synchronization) from the active supervisor engine to the standby supervisor engine, the standby supervisor engine and possibly other modules might report "Minor hardware problem in Module X" to the console display. The workaround is to either reset the individual modules reporting this error or reset the switch. (CSCdv51172, CSCdv50525)

Multilayer Switching

This section contains usage guidelines, restrictions, and troubleshooting information that apply to MLS:

•If you have routed flows with MLS disabled (no shortcuts created), candidate entries age out rapidly to ensure that the forwarding table is used as much as possible by shortcut flows. A side effect of this rapid aging of candidate entries is that the microflow policer does not work accurately because its policing history is lost when the entries age out. When the same flow creates a new entry, it gets the entire traffic contract again even if it had exceeded the contract before the entry aged out. (CSCdp59086)

•Layer 3 switching on the Catalyst 6000 family switches does not support full or destination-source flows for IPX traffic. With Supervisor Engine 1 and PFC, when the MLS flow mask is destination-source or full-flow, the show mls entry ipx destination command that should select a specific destination displays all IPX Layer 3 entries rather than just those for a specific destination IPX address. (CSCdm46984)

MIBs

This section contains usage guidelines, restrictions, and troubleshooting information that apply to SNMP MIBs, RMON groups, and traps:

---

Note For information on MIBs, RMON groups, and traps, refer to the Cisco public MIB directory located at this URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

---

•You cannot use the tftpGrp MIB object to download Catalyst 6000 ATM software. (CSCdp16574)

VLANs, VTP, and VLAN Trunks

This section contains usage guidelines, restrictions, and troubleshooting information that apply to VTP, VLANs, and VLAN trunks:

•When a Catalyst 6000 family switch running supervisor engine software is connected to a switch running Cisco IOS software on the supervisor engine and both switches have VTP enabled, the Cisco IOS VTP might have a higher VTP configuration revision. In this event, the Cisco IOS switch tries to update the VTP on the switch running supervisor engine software. The switch running Cisco IOS has VLAN 1 translated to VLAN 1003 by default (Token Ring type VLAN), and the switch running supervisor engine software does not support this configuration resulting in an undefined VLAN configuration. If you try to configure the affected VLAN (VLAN 1 in this case), the system might reset with a watchdog timeout. This problem was corrected as follows in software releases 6.3(3) and later.

When the switch running supervisor engine software experiences the problem, it changes to VTP transparent mode and the following message is displayed:

VTP-4-UNSUPPORTEDCFGRCVD:Rcvd VTP advert with unsupported vlan config on trunk 3/24 - 
VTP mode changed to transparent

(CSCdu32627)

•When using a VLAN interface other than the VLAN 1 interface, a VLAN added on a Catalyst 3500XL running 120.5.1-XP does not appear in the Catalyst 6000 family switch database. As soon as management interfaces are put back in VLAN 1, a VLAN configured on the 3500XL is sent properly to the Catalyst 6000 family switch through VTP. Check the status of CSCdr80902 in your Cisco IOS release. (CSCdr66376)

•In a redundant configuration, if you modify the VLAN mapping on the active supervisor engine and a high-availability switchover occurs before the VLAN mapping is synchronized between the supervisor engines, you might experience a mapping inconsistency (VLANs claimed by two different instances) if you reenter the mapping command. The workaround is to recreate a new mapping on a different instance after the switchover. On the newly active supervisor engine, enter the set vlan vlan_num mistp none command and reenter the mapping. (CSCds27902)

Authentication, Authorization, and Accounting

This section contains usage guidelines, restrictions, and troubleshooting information that applies to authentication, authorization, and accounting (AAA):

•For login authentication, starting from software releases 5.5(15), 6.3(7), and 7.3(1), if you press the Enter key and then type in your password (<Enter> <password>) the ACS TACACS+ server will treat it as an indication that you are attempting to change your password. This behavior is related to CSCdx08395. Before the CSCdx08395 fix, the user privilege level was hard coded to 15 in the TACACS+ authentication request packet. With the CSCdx08395 fix, the user privilege level is set based on the privilege level that the user is authenticated as. For example, if the user is doing a login authentication, the privilege level would be 1. If the user is doing an enable authentication, the privilege level would be 15.

The Cisco ACS TACACS+ server acts differently for <Enter> <password>. For login authentication, if the user priv-lvl is hard coded to 15, <Enter> <password> is treated as a regular password attempt. If the user priv-lvl is set to 1 (CSCdx08395) during login authentication, then <Enter> <password> is treated as an indication of a changing password. The latter case is a behavior consistent with TACACS+ enable authentication and Cisco IOS software handling of <Enter> <password>. (CSCdy35129)

Auto-MDI/MDIX

With auto-MDI/MDIX you can use either a straight or crossover cable, and the module will automatically detect and adjust for the cable type. In this section when we say auto-MDI/MDIX works with the speed set to auto/1000 Mbps, but not with the speed set to 10Mbps or 100Mbps, this means that the link will come up with either a straight or crossover cable if the speed is set to auto/1000 using the set port speed mod/port auto command or the set port speed mod/port 1000 command. The link comes up even if the speed is autonegotiated at 10Mbps or 100Mbps in auto mode. However, if you enter the set port speed mod/port 10 command or the set port speed mod/port 100 command, the link fails to come up if the wrong cable is used.

Auto-MDI/MDIX has always been enabled on the following modules:

•WS-X6548-RJ-45, WS-X6548-RJ-21, WS-X6148-GE-TX, WS-X6548-GE-TX

Auto-MDI/MDIX works in 10-, 100-, and 1000-Mbps modes with autonegotiated and fixed speeds.

•WS-X6516-GE-TX

Auto-MDI/MDIX works with the speed set to auto/1000 Mbps, but not with the speed set to 10Mbps or 100Mbps.

•WS-X6316-GE-TX

With software release 8.2(1), auto-MDIX is also enabled on the following modules:

•WS-X6748-GE-TX, Supervisor Engine 720 port 2 (RJ-45)

Auto-MDI/MDIX works with the speed set to auto/1000, but not with the speed set to 10Mbps or 100Mbps

•WS-X6148X2-RJ-45, WS-X6148X2-RJ-45V

Auto-MDI/MDIX works with the speed set to auto, but not with the speed set to 10Mbps or 100Mbps.

---

Note Auto-MDI/MDIX is not supported on any other 10/100-Mbps Ethernet modules or GBIC, SFP, and XENPAK ports.

---

CiscoView Images

This section contains usage guidelines, restrictions, and troubleshooting information that applies to CiscoView (CV) images:

•The supported client platform/browser/plug-in versions to launch embedded CiscoView are as follows:

Client Platform	Web Browser	Java Plug-in
Solaris 2.6/2.7	Netscape Communicator 4.7	Java Plug-in 1.3.0 (JRE 1.3.0)
Windows NT 4.0 and Windows 2000	Internet Explorer 5.5 and Netscape Communicator 4.7	Java Plug-in 1.3.0-C (JRE 1.3.0)

---

Note Java Plug-in versions 1.3.0_01 and 1.3.0_02 do not work.

---

---

Note Java Plug-in versions 1.3.1 is not supported.

---

•The digital security certificate that is used to sign the Java classes in software release 6.2(2)CV image will be valid until May 19th, 2002. After the expiration date, if embedded CiscoView cannot be launched or an Access Control Error occurs, upgrade to the latest image or upgrade the plug-in/browser on the client machine.

•If CiscoView does not work after resizing the browser window on a Solaris client machine, download and use the Netscape Communicator 4.7 from Sun Microsystems instead of from Netscape.

•The new releases of the Java Plug-in 1.3 (1.3.0_01 and 1.3.0_02) available for download from Sun Microsystem's website do not work with CiscoView versions 5.5(4) and later on the Catalyst 4000 family, Catalyst 5000 family, Catalyst 6000 family, and Catalyst 2900/3500XL switches. The workaround is to install the previous release of the 1.3 Plug-in, 1.3.0-C.

To determine the version installed on your system, go to the "Start Menu" and select "Settings" then "Control Panel." There is a Java Icon in the Control Panel that displays the version. If it indicates "Java Plug-In" then it is the correct version. The incorrect versions have _01 or _02 next to the name. You can also double click on the Java Icon and then click on the "About" tab to display the version, which should be 1.3.0-C for CiscoView to work properly. (CSCdt96453)

•CiscoView images take approximately 12 minutes to download from a TFTP server to a PCMCIA Flash card. (CSCdr14437)

•You may be unable to delete a primary VLAN after unbinding the secondary VLAN. The workaround is to close and reopen the dialog and try to delete the primary VLAN again.

If you attempt to bind a secondary VLAN to the primary VLAN and delete the primary VLAN, the following incorrect error message appears:

Set failed due to snmpRspGenErr for vtpVlanEditRowStatus.1.199

The workaround is to close and reopen the dialog and the correct error message will display. (CSCdt65530)

•If you use QoS Device Management and select Policy Selection, Add/Edit Policies >Change, and then select a policy and click OK, selecting Cancel when the confirmation window displays will not cancel the operation. The policy is still added to the Policy Selection. The workaround is to delete the policy selection entry that was added. (CSCdu43690)

•If you use QoS Device Management to add or edit an IP/IPX/MAC ACL, no buttons are available to move ACE entries up and down. The workaround is to select the entry that needs to be moved and click on Edit and select OK. This entry is then moved to the bottom of the ACE list. (CSCdt64023)

•If you use QoS Device Management to create a policy name and try to delete the policy name, the following incorrect error message appears:

Unable to set row status

(CSCdu11333)

•If you use QoS Device Management to add an IP ACL, select the Add/Edit ACE option, select an entry and make some changes, and then either click Cancel or OK. The configuration fails due to misconfigurations when you select OK; the previously entered values will appear as defaults when you attempt to edit your configuration. The workaround is to overwrite the values in the fields if necessary. (CSCdu05678 and CSCdu15066)

•If you select Configure >Interface, all fields show either as N/A or with wrong values for the MultiChannel DS3 PA installed on a WS-X6182-PA module. (CSCdr39591)

•The Catalyst 6000 CiscoView (CV) images do not support the Carrier Alarm LED for WAN modules. (CSCdt52011)

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 6500 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)

•When a user upgrades from one release to a higher maintenance release, the NVRAM conversion routine does not occur and therefore the default summertime will not be changed to the new standard values.

Workaround: Use the set summertime command to manually configure the proper start date and end date for daylight savings time. After the summertime period for calendar year 2006 is over, one can for example configure:

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

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) 

Alternatively, you can upgrade the switch from any release to the current release which will bring the switch to the new standard values. For example, upgrade from 5.x to 6.4(23). You can also clear the configuration of the switch by using the clear config all command.

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

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

•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. (CSCsd35254)

Resolved Caveats in Software Release 6.4(22)

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

•When you initiate and abort a format of a flash card on any standby supervisor engine, and then attempt to view a directory listing, the standby supervisor engine's file system locks, the disk becomes inaccessible, and you see a "Try again later" message as shown in the example below:

Console> (enable) dir 1/disk0: 
File system in use (2). Try again later.

Workaround: Reset the supervisor.

This problem is resolved in software release 6.4(22). (CSCse35781)

•With PAgP mode set to "on," you might not be able to map a QoS ACL to a channel port when the port's status is "not connected." An example of the problem is as follows:

Console> (enable) set qos acl map test-qos 3/9 

Transient error. Port state in transition. Please retry command. Failed to map ACL

test-qos to port 3/9.

Console> (enable)

Workaround: Use one of the following workarounds:

–Map the QoS ACL to the port before configuring the channel.

–Change the PAgP mode to either auto or desirable.

–Map the QoS ACL only to ports with a status of "connected."

This problem is resolved in software release 6.4(22). (CSCdz89506)

•In rare circumstances, you might see the following behavior with the WS-X6324-100FX modules:

–Port counters indicate packets received and transmitted.

–No CDP neighbors are seen on the switch on ports of the affected module.

–No MAC addresses are learned on ports of the affected module.

–All incoming (receive) traffic on all ports is lost.

–Transmit traffic is working.

•Workaround: Reset the affected module. This problem is resolved in software release 6.4(22). (CSCeg60285)

•The switch might fail to forward multicast traffic. This problem is resolved in software release 6.4(22). (CSCsc75774)

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(21)

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

•After a high-availability switchover, you might experience a MISTP reconvergence on the newly active supervisor engine and the following message may display:

2005 Sep 09 16:00:49 JST +09:00 %SPANTREE-2-SWOVER_TOOLONG: switchover took too much 
time. All STP ports restarted. 

This problem is resolved in software release 6.4(21). (CSCej37841)

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(20)

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

•With redundant supervisor engines/MSFCs, MSFCs configured in DRM with both MSFCs using an administered MAC address on the VLAN interface, and MSFCs configured with HSRP and OSPF, there is no problem as long as both supervisor engines remain in the same chassis. If you remove the standby supervisor engine and install it in another chassis with a link between the two switches, you lose unicast communication between the MSFCs, as evidenced by the following problems:

–Cannot ping between the physical IP addresses

–OSPF does not come up

–Problems with HSRP

When you enter the show cam system command on the initial chassis, you can see that the MAC address configured on the removed MSFC still points to port 16/1. As soon as the administered MAC address is removed from the VLAN interfaces on the removed MSFC, communication returns. This problem is resolved in software release 6.4(20). (CSCed20984)

•You might experience a TLB exception when committing a VACL with approximately 278 or more lines. This problem is resolved in software release 6.4(20). (CSCej06637)

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

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(19)

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

•With an EtherChannel formed using ports on both the standby and active supervisor engines, the switchover time might take longer than normal. This problem is resolved in software release 6.4(19).

Workaround: Use the ports in a module other than the supervisor engine for the EtherChannel. (CSCef00617)

•In rare circumstances with a Supervisor Engine 2 and UDLD and high availability enabled, you might see a unidirectional link after a high-availability switchover. This problem is resolved in software release 6.4(19). (CSCei12152)

•Removing a private VLAN from a promiscuous port using the clear pvlan mapping primary-vlan secondary-vlan mod/port command breaks connectivity on that promiscuous port for all other mapped secondary VLANs. This problem has been seen with a Supervisor Engine 1A on switches running software release 7.6(11) and later releases with ports configured on the WS-X6148-GE-TX module.

Workaround: To restore connectivity, add back the VLAN mapping. This problem is resolved in software release 6.4(19). (CSCeh51722)

•When you are running software release 6.4(12) and later releases, the lbusDrops counter is incremented although no traffic is flowing. This is a cosmetic issue. This problem is resolved in software release 6.4(19). (CSCeh66404)

•With software release 6.4(17) and later releases, when the MSFC on the standby supervisor engine exceeds its minor temperature threshold, the module status is displayed as faulty. The module status should be displayed as temp-minor. This problem is resolved in software release 6.4(19). (CSCei55551)

•After a period of time, the Supervisor Engine 1A might drop multicast traffic. This problem is resolved in software release 6.4(19). (CSCsb55180)

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(18)

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

•The SNMP "snmpdm" process is sleeping after running for a long time. This problem is resolved in software release 6.4(18). (CSCeg64313)

•The WS-X6148-45AF module might reset due to excessive link changes and display the following error message:

2005 May 06 13:02:24 %SYS-5-MOD_NOSCPPINGRESPONSE:Module 9 not responding... resetting 
module 2005 May 06 13:02:24 %SYS-5-MOD_RESET:Module 9 reset from Software 2005 May 06 
13:04:07 %SYS-5-MOD_OK:Module 9(WS-X6148-45AF,SAL08175TMG) is online 

This reset is not related to faulty hardware and is caused when ports go up and down at an abnormally high rate.

Workaround: Check the linkChange counter in the output of the show counters mod/port command. A large number of link changes could cause the module to reset. This problem is resolved in software release 6.4(18). (CSCeh84332)

•When the set errordetection portcounters enable command is entered, you will see two SCP retries every 30 minutes.

Workaround: Enter the set errordetection portcounters disable command. This problem is resolved in software release 6.4(18). (CSCei08970)

•Netstat TCP displays negative values. This problem is resolved in software release 6.4(18). (CSCei21068)

•You might experience an exception when using CiscoWorks RME4.0 to pull information from the switch. This problem is resolved in software release 6.4(18). (CSCsb18681)

•With a Supervisor Engine 2/MSFC2, Unicast Reverse Path Forwarding (uRPF) may not work properly for multipath routes after RPF is disabled on a specific VLAN while other VLAN(s) still have RPF enabled.

Workaround: Disable all RPF-enabled VLANs and then enable them again. This problem is resolved in software release 6.4(18). (CSCei06016)

•With a Supervisor Engine 1 or Supervisor Engine 2, the configuration information for SPAN might be lost when the switch is reset after entering the clear config all command followed by the set span command. This problem has been seen with the following hardware/sofware:

–WS-X6K-SUP1A-2GE/software release 6.1(2)

–WS-X6K-SUP1A-2GE/software release 6.2(2)

–WS-X6K-SUP1A-2GE/software release 6.4(3)

–WS-X6K-SUP2-2GE/software release 6.1(3)

–WS-X6K-SUP2-2GE/software release 6.3(1)

–WS-X6K-SUP2-2GE/software release 6.3(10)

–WS-X6K-SUP2-2GE/software release 6.4(2)

–WS-X6K-SUP2-2GE/software release 6.4(17)

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

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(17)

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

•With a Supervisor Engine 1A/MSFC in single router mode redundancy, old MLS entries might not be purged when the active supervisor engine is removed from the switch. This problem is resolved in software release 6.4(17).

Workaround: Manually clear the old MLS entries. (CSCef29082)

•A switching module's port cost values might not synchronize correctly with the standby supervisor engine after the following configuration steps are performed on the switching module:

–UplinkFast is enabled.

–The module's configuration is cleared.

The problem is seen regardless of the spanning-tree mode. This problem is resolved in software release 6.4(17). (CSCeg78210)

•The switch might not return the values of the cseL2ForwardedLocalOctets MIB counter, although other counters in the cseL2StatsEntry tree are correctly returned. This problem is resolved in software release 6.4(17). (CSCeh16351)

•IEEE BPDUs may be sent from an 802.1Q trunk port even if the native VLAN is cleared from the trunk. When the native VLAN on a trunk is cleared, the IEEE untagged BPDUs should not be sent. If the trunk port reinitializes itself for any reason (such as disabling/enabling the trunk or doing a module or switch reset), the trunk port may start to send IEEE untagged BPDUs.

Workaround: Add the native VLAN and clear it again as follows:

set trunk mod/port NativeVlan_ID

clear trunk mod/port NativeVlan_ID

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

•On a Supervisor Engine 2/MSFC2 with PFC hardware version 2.0, you might see high CPU utilization after committing a large VACL that results in spanning tree recalculations. This problem is not seen with PFC hardware version 1.0 or 1.3. This problem is resolved in software release 6.4(17). (CSCeh37782)

•OSPF hello packets are not being forwarded from the switching module to the MSFC on the standby supervisor engine resulting in OSPF adjacencies going down on the MSFC. This problem is observed when the FPOE consistency checker is enabled.

Workaround: Disable the FPOE consistency checker. This problem is resolved in software release 6.4(17). (CSCeh74503)

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(16)

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

•You might experience a problem with an SSH login. The login prompt appears and you enter your login name and get a password login prompt. After entering the password, there is no reply; you see a blank line and pressing Enter again does nothing. If you try to enter a command, there is no echo on the screen but the output from the command is displayed on the screen. This problem is not affecting the ability of the switch to function correctly. Once the problem happens, it is continuous. Logging off and back on does not clear the problem. You must reboot the switch to clear the problem. If you attempt an SSH login on an affected switch and it fails, you can immediately do an SSH login to an unaffected switch from the same session without a problem. This problem is resolved in software release 6.4(16). (CSCef54438)

•An IEEE BPDU may be sent from an 802.1Q trunk port even if the native VLAN is cleared from the trunk. When the native VLAN on a trunk is cleared, the IEEE untagged BPDU should not be sent. If the trunk port reinitializes itself for any reason (such as disabling/enabling, module reset, and switch reset), the trunk port may start to send IEEE untagged BPDUs.

Workaround: Add the native VLAN and clear it again as follows:

1) set trunk mod/port NativeVlan_ID

2) clear trunk mod/port NativeVlan_ID

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

•After a supervisor engine switchover, if you add a VLAN to a trunk port, the VLAN is not displayed in the "Vlans in spanning tree forwarding state and not pruned" field of the show trunk command. This problem is resolved in software release 6.4(16). (CSCeg47658)

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

•Under certain conditions, such as bringing up the standby supervisor engine, the FPOE consistency checker might be disabled even though the active supervisor engine had consistency checking enabled before the switchover. This problem is resolved in software release 6.4(16). (CSCeg64212)

•The switch may not be able to communicate with a connected device on a secure port in a different VLAN. This problem does not impact the other traffic of the connected devices.

Workaround: Disable port security on desired ports using the set port security mod/port disable command. This problem is resolved in software release 6.4(16). (CSCeg71622)

•With a Supervisor Engine 2, packets with an unresolved destination MAC address may be dropped instead of being forwarded to the MSFC for the triggering of ARP requests.

Workarounds: 1) Ping the destination from the supervisor engine or the MSFC. 2) Add a static ARP entry on the MSFC. This problem is resolved in software release 6.4(16). (CSCeg73090)

•If you use the show trunk [mod[/port]] extended-range command, the system might display all the ports without releasing the CPU for other processes. During this period, BPDU processing might stop. This problem is resolved in software release 6.4(16). (CSCeg73646)

•With port security, when a port is shut down due to a security violation, the offending MAC address is not displayed in the syslog. This problem is resolved in software release 6.4(16). (CSCeg76020)

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

•If you upgrade your switch from any software release 7.x or earlier releases to software release 8.x and later releases with the boot mode set to "text" and spanning tree set to "PVST+," the spanning-tree mode changes to "Rapid PVST+."

Workaround: Change the boot mode to "binary" before performing the upgrade. This problem is resolved in software release 6.4(16). (CSCin75737)

•During a high availability switchover, the active supervisor engine may incorrectly detect a hardware mismatch during the synchronization process. Possible symptoms of this problem are as follows:

–Entering the show module command displays the standby supervisor engine status as "error"

–The active standby LED on the supervisor engine is red

–The show log command displays "Active and standby supervisors are of different card types"

Workaround: Reload the switch. This problem is resolved in software release 6.4(16). (CSCea16228)

•With a Supervisor Engine 2/MSFC2 in truncated mode with SRM configured on the MSFC2, the FPOE for hardware broadcasts is not set properly after resetting the designated MSFC2. When this problem occurs, traffic from fabric-enabled modules to nonfabric enabled modules is dropped.

Workaround: Change the switching mode to compact or use software release 6.4(13) or earlier releases. This problem is resolved in software release 6.4(16). (CSCeg84506)

•After uploading and downloading both default and nondefault configurations to and from a TFTP server, the "set mmls nonrpf timer 10" entry might mistakenly appear in the show config all command output as follows:

Console> (enable) show conf all

/snip/

#mmls nonrpf

set mmls nonrpf enable

set mmls nonrpf timer 60

set mmls nonrpf window 10

set mmls nonrpf timer 10   <--- should be interval

The second "set mmls nonrpf timer" entry should be "set mmls nonrpf interval." This problem is resolved in software release 6.4(16). (CSCeh20805)

•With redundant supervisor engines, the status and configuration of port 1/1 and port 2/1 is changed after a switchover. The first supervisor engine port on the newly active supervisor engine gets enabled even if the default is set to disable. This problem is only seen in text configuration mode.

Workaround: Use binary configuration mode. This problem is resolved in software release 6.4(16). (CSCsa42331)

•The show tech-support command might display configured passwords in text configuration mode. This problem is resolved in software release 6.4(16). (CSCeg17866)

•The Telnet access denied message includes "retry" timer information. The retry timer information has been removed in software release 6.4(16). (CSCeh18221)

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)

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

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(15)

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

•In a two-port EtherChannel, when the second port is added to the EtherChannel, the first port leaves and then rejoins the EtherChannel (this leaving and rejoining occurs twice).

Workaround: The problem does not occur if the EtherChannel mode is set to "on." This problem is resolved in software release 6.4(15). (CSCee76807)

•Out-Discard and Rcv-Octet counters increment on GBIC ports that are showing a "notconnect" status. This problem is resolved in software release 6.4(15). (CSCeg48512)

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)

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

•After a high-availability switchover, LTLs might not be set correctly for MSFC ports 15/1 and 16/1. (CSCee03884)

---

Note This problem was seen in earlier software releases but is not seen in the 6.4(14) and later software releases.

---

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(14)

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

•With a Supervisor Engine 1, you might see some Layer 3 table parity errors. These are non-fatal errors (packets are still forwarded in software). This problem is resolved in software release 6.4(14). (CSCdy41174)

•With the WS-X6502-10GE module, the set qos map command maps CoS values to the WRED thresholds only and not to the tail-drop thresholds. This problem is resolved in software release 6.4(14). (CSCdy79506)

•In text configuration mode, the SPAN sessions on the NAM, IDSM, and other service modules are not reconfigured after a reset.

Workaround: Manually configure the SPAN sessions on a service module each time that the switch is reset. This problem is resolved in software release 6.4(14). (CSCed65635)

•With PAgP, it might take an unusually long time for a trunk port to join an EtherChannel. This problem is resolved in software release 6.4(14). (CSCee95479)

•The switch does not respond properly when the logout timer is set to 3 (set logout 3) if you are accessing the switch through a Telnet session and the screen is either holding the display at the "More" prompt, the "Enter Password" prompt, or the "Username" prompt. The logout timer is ignored during these conditions, allowing the connection to remain open beyond the configured logout timer setting. This problem is resolved in software release 6.4(14). (CSCef15158)

•LTL indexes for configured multicast CAM entries that point to an EtherChannel that is configured in desirable mode are lost when the EtherChannel link goes up and down.

Workarounds: 1) Clear the configured CAM table entry and reenter it. 2) Configure the EtherChannel to "ON" mode. This problem is resolved in software release 6.4(14). (CSCef51905)

•If you configure a SPAN session on a module and then replace the module with a different type of module, the switch disables the SPAN session because a different type of module was inserted. This is normal behavior. The problem is that if you configure a new SPAN session on the newly installed module and then perform a high-availability switchover, the newly configured SPAN session is lost after the switchover.

Workaround: Reconfigure the SPAN session after the high-availability switchover. This problem is resolved in software release 6.4(14). (CSCef67073)

•The switch displays the following syslog message when the system is under a Denial of Service attack:

TCP-2-TCP_MAXESTABLISHED:Possible TCP ACK attack. . Maximum established connection 
limit 64 reached. Will drop unused connection

However, under some circumstances, the syslog might be generated when the system is not under attack. The system functionality is not affected. This problem is resolved in software release 6.4(14). (CSCef77162)

•The show tech-support command does not display "outband counters." This problem is resolved in software release 6.4(14). (CSCef81144)

•With IGMP snooping enabled, PIM hellos might not be going out of the ATM LANE modules.

Workaround: Disable and then reenable IGMP snooping. This problem is resolved in software release 6.4(14). (CSCef81723)

•The show tech command should not display password information because this could create a security vulnerability. This problem is resolved in software release 6.4(14). (CSCef86581)

•For a Supervisor Engine 2/MSFC2 with more than 255 VLANs assigned to the same HSRP group ID, the HSRP MAC address may be deleted mistakenly, resulting in Layer 3 packets being forwarded to the MSFC2 for software switching.

Workaround: Limit the number of VLANs with the same HSRP group ID to no more than 255. If necessary, use other HSRP group IDs. This problem is resolved in software release 6.4(14). (CSCef88220)

•The system passwords (both console and enable passwords) might not work after loading the passwords from a previously saved password configuration file. This problem is resolved in software release 6.4(14). (CSCeg05183)

•Manually configured MAC addresses on port security-enabled ports might age out. This problem is resolved in software release 6.4(14). (CSCin83482)

•With dual Supervisor Engine 2s and dual WS-6500-SFM modules running in truncated mode, the WS-X6516-GBIC module might fail to receive multicast traffic. The switch can send multicast traffic and there is no problem with unicast traffic on the problem port.

Workaround: Force the system to run in bus-only mode, or use a single supervisor engine in the chassis. This problem is resolved in software release 6.4(14). (CSCee13437)

•In rare circumstances, when versioning up or down to a different software release, the switch does not boot with the software that is configured to boot.

Workarounds: 1) Verify the bootstring and reset the system one more time. 2) After the reset, if the switch is booting with the wrong image, break the autoboot process and enter into the ROMMON mode by sending a Break. From ROMMON, execute the boot command to boot the switch with the correct image. This problem is resolved in software release 6.4(14). (CSCef43494)

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)

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

•After a high-availability switchover, LTLs might not be set correctly for MSFC ports 15/1 and 16/1. (CSCee03884)

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(13)

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

•If a port is moved from VLAN X to VLAN Y, permanent CAM entries might be lost. For example, if you have port group 1/1-8 with port 1/2 and port 1/7 in VLAN 10 and a permanent CAM entry configured on port 1/2, if port 1/7 is moved from VLAN 10 to VLAN 20, the permanent CAM entry on port 1/2 might be deleted.

Workaround: After moving a port to a different VLAN, reconfigure the permanent CAM entry. This problem is resolved in software release 6.4(13). (CSCef66696)

•When the EOBC out-of-band management bus fault detection code tries to repower a module that is in the "power-deny" state, the switch may crash. This problem is resolved in software release 6.4(13). (CSCee59418)

•With redundant Supervisor Engine 2s/MSFC2s and dual router mode (DRM) enabled, resetting the designated MSFC2 might cause loss of connectivity to/from the MSFC2 when it boots up again. The newly designated MSFC2 is not affected. This problem is seen in the following software releases:

–1) If the MLS rate limiter is not enabled, the problem is seen in software releases 7.6(5) through 7.6(8).

–2) If the MLS rate limiter is enabled, the problem is seen in software releases up to 6.4(12) in the 6.x software train.

Workaround: There are two ways to restore connectivity to the affected MSFC2: 1) Disable the MLS rate limiter by entering the set mls rate 0 command. Note that if the problem is seen in software releases 7.6(5) through 7.6(8), even if the MLS rate limiter is not enabled, entering the set mls rate 0 command restores connectivity. 2) Reset the affected MSFC2. This problem is resolved in software release 6.4(13). (CSCef32204)

•There is a vulnerability in the Transmission Control Protocol (TCP) specification (RFC 793). All Cisco products that contain TCP stack are susceptible to this vulnerability. This advisory is available at these URLs:

–http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-ios.shtml

This URL describes this vulnerability as it applies to Cisco products that run Cisco IOS software.

–http://www.cisco.com/warp/public/707/cisco-sa-20040420-tcp-nonios.shtml

This URL describes this vulnerability for products that do not run Cisco IOS software.

This problem is resolved in software release 6.4(13). (CSCed32349)

•The following syslog error message indicates an ASIC error with the WS-X6548-RJ-45 module and the recommended action is to replace the module:

SYS-6-SYS_LCPERR6:Module [dec]: Pentamak Ddr Sync Error

This message has a logging level of 6 but the severity of the error dictates that the logging level should be a 3. This problem is resolved in software release 6.4(13). (CSCef18763)

•If the system banner size is over approximately 3072 characters, the switch might crash when you enter the show banner command through a Telnet session. This problem is resolved in software release 6.4(13). (CSCef44617)

•Enabling and disabling the SPAN feature might generate control characters in your Telnet window during an open Telnet session to the switch. This problem is resolved in software release 6.4(13). (CSCeb62318)

•Gigabit fiber-based modules (and under some conditions, copper-based modules) might experience high latency on ports when a SPAN destination session is configured on the same module. If a SPAN destination port goes up and down, there is the possibilty that ports that are connected to the same port ASIC might experience latency (or possibly total lockup) in the receive direction. The latency, if present, is noticible when low amounts of traffic are being sent through the system and/or if the received packet size on ports adjacent to the SPAN port are small or of average size.

For complete details on this problem and a list of affected modules, refer to the online bug toolkit release notes at the following URL:

http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl

This problem is resolved in software release 6.4(13). (CSCef39614)

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)

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

•After a high-availability switchover, LTLs might not be set correctly for MSFC ports 15/1 and 16/1. (CSCee03884)

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(12)

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

•With a Supervisor Engine 2 or Supervisor Engine 720, traffic might be switched matching a policy map using the hardware CEF table instead of the next hop as set by the policy map. This problem has been observed only when you have a policy map with a large number of sequences and different next hops for each sequence. This problem is resolved in software release 6.4(12). (CSCef38462)

•With MISTP enabled and the EtherChannel mode set to "ON," if you configure more than one EtherChannel and trunk in a short period of time, all of the newly configured channels might not join the trunk. With this configuration scenario, the problem has also been seen after the switch is reset. This problem is resolved in software release 6.4(12). (CSCee95922)

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

•When running a K9 software image, the switch might crash when the SSH client tries to connect to the switch. This problem is resolved in software release 6.4(12). (CSCdz04272)

•In software release 6.4(12), to facilitate the troubleshooting of fabric-related problems, the FPOE mismatch count (error counter) has been added to the show fabric channel counters command. Additionally, a syslog has been added to indicate that this error counter is incrementing. (CSCef25518)

•If the switch is peering with a multicast router through an ATM interface (either LANE or RFC1483 with PVC binding), you might experience high CPU utilization with the multicast receive process.

Workaround: Disable IGMP or enable the multicast rate-limit feature and set the rate to a value that alleviates the problem. This problem is resolved in software release 6.4(12). (CSCef27349)

•The switch might reset (%SYS-5-MOD_NOSCPPINGRESPONSE) when getting CBL information through a PERL script. This problem is resolved in software release 6.4(12). (CSCee62021)

•A watchdog timeout might occur when you clear a large ACL (the problem was seen with an ACL that had 2000 ACEs). This problem is resolved in software release 6.4(12). (CSCee88608)

•After upgrading Catalyst software to a version that supports the set msfcautostate command from a software version that did not support the command, set msfcautostate disable is automatically configured even though the default option for this command is enabled. This problem is resolved in software release 6.4(12). (CSCee62169)

•A UNIX script might get stuck at the Telnet prompt.

Workaround: Press Enter when the script gets stuck to start the script again. This problem is resolved in software release 6.4(12). (CSCeb69513)

•The switch might drop all EtherChannels configured to "desirable" mode for approximately 10 minutes and depending on the topology, connectivity may be affected for the entire period of the outage.

Workaround: Configure EtherChannels to "ON" mode using the set port channel mod/port mode on command. This problem is resolved in software release 6.4(12). (CSCef02710)

•After experiencing a fabric sync error (%SYS-3-FAB_SYNCERR) some modules might have problems receiving control traffic such as UDLD packets (there is no problem with transmitting traffic).

Workaround: Reset the switch. This problem is resolved in software release 6.4(12). (CSCef06375)

•A problem is seen after an IP address is changed on a workstation or server; the address change can happen statically or due to DHCP after a reboot. The problem is that a drop adjacency is created for the IP address with a /32 mask on the switch. It is possible to ping the workstation from the switch but pings from a directly connected redundant switch fail (if Layer 3 CEF is traversed).

Workaround: A ping from the MSFC in the same chassis as the switch with the drop adjacency clears the drop adjacency. This problem is resolved in software release 6.4(12). (CSCec23277)

•The switch might crash with crashing function name po_ipu_get_adj_vlan_mac. This problem is resolved in software release 6.4(12). (CSCef00947)

•If port security is enabled on ports that have an auxiliary VLAN configured, no traffic switches on the auxiliary VLAN.

Workaround: Disable port security. This problem is resolved in software release 6.4(12). (CSCef14201)

•With a Supervisor Engine 1/MSFC, an input Cisco IOS ACL on the MSFC can cause Layer 2 traffic to be dropped in a VLAN. This problem is seen when no ip unreachables are configured and protocol filtering is enabled.

Workaround: Reset the switch to clear the problem. This problem is resolved in software release 6.4(12). (CSCee69960)

•The value of dot1dStpPortDesignatedPort is not correct when queried from SNMP. This problem is resolved in software release 6.4(12). (CSCee94422)

•With UplinkFast enabled, invalid dummy multicast packets might be sent out from the switch resulting in a communication failure.

Workaround: Clear the ARP cache. This problem is resolved in software release 6.4(12). (CSCee22626)

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)

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

•After a high-availability switchover, LTLs might not be set correctly for MSFC ports 15/1 and 16/1. (CSCee03884)

•The ToS byte remains unchanged in bridged multicast packets when you enable Multicast Multilayer Switching (MMLS). The system does not support multiple, different rewrites for a single packet. A Layer 3 rewrite is generated for multicast; there is no rewrite for the Layer 2 forwarding.

For example, you have a multicast source in VLAN 13, a receiver in the same VLAN, and a QoS IP ACL configured and mapped to the source's ingress port that matches the traffic flow and specifies DSCP 31. When you disable the MMLS feature, the IP packets that are captured on the receiver's port contain a ToS byte of x7C (the expected result). When you enable the MMLS feature and establish a Layer 3 flow, the captured packet's ToS byte is unchanged from the value that is sent by the source. A ToS rewrite occurs on the replicated packets in the outgoing VLANs (other than VLAN 13). No ToS rewrite occurs for the packets that are bridged in the same incoming VLAN. (CSCdm72364)

Resolved Caveats in Software Release 6.4(11)

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

•Spanning tree does not block ports looped with a Balun cable. If a port is looped through a Balun cable or a loop-back adapter, spanning tree will initially block the port. If a topology change occurs, the port is put into forwarding state. This problem is resolved in software release 6.4(11). (CSCed84323)

•IPX unicast packets may be dropped on the ingress MSFC interface when IP ACLs, VACLs, and no IP redirects are configured. The problem only occurs when you have the following three configuration components: An IP ACL configured on a VLAN interface, "no ip redirects" configured on the MSFC, and a VACL configured for the corresponding VLAN on the switch side. The problem is seen once the interface comes up. Only broadcast IPX traffic actually reaches the MSFC. If either the access group is removed or IP redirects are enabled on the VLAN interface on the MSFC, the problem is cleared immediately, but if the configuration is added back and the interface is brought down and then back up by entering the shutdown command followed by the no shutdown command, the problem returns.

Workaround: Remove one of the three components that causes the problem. This problem is resolved in software release 6.4(11). (CSCee51617)

•If a multicast entry is configured through the CLI by entering the set cam command, it does not get synchronized to the standby supervisor engine in the following cases:

–When the standby supervisor engine is reloaded after configuring the entry.

–When high availability is disabled and then reenabled after configuring the entry.

In general, whenever high availability global synchronization is involved in the presence of the entry, it is not synchronized to the standby supervisor engine. When a switchover is done, the new active supervisor engine is not aware of the multicast entry and it does not show the entry in the show cam command output.

Workaround: Ensure that high availability is enabled and "ON" by entering the show system highavailability command before creating any multicast entries using the set cam command. This problem is resolved in software release 6.4(11). (CSCee27955)

•Doing a minimal entry (entering only the first part of a command's syntax) on the following commands: set errdisable, set option, and show cdp port mod/port, results in either a missing key word or no error message. This problem is resolved in software release 6.4(11). (CSCed92864)

•The supervisor engine might fail to power down the SFM after a synchronization error or hardware failure.

Workaround: Remove the defective SFM. This problem is resolved in software release 6.4(11). (CSCee34175)

•When you enter the shutdown command followed by the no shutdown command on a loopback interface, and the same loopback interface address is also configured on two or more connected routers, the switch may crash with a FIB exception. This problem is resolved in software release 6.4(11). (CSCea50206)

•When resetting the designated MSFC, you might see "Incorrect_adj_ptr_fib" error messages. The frequency of these messages is proportional to the number of SVIs configured on the MSFC. Approximately two "Incorrect_adj_ptr_fib" messages are likely to be printed for every SVI configured on the MSFC. These messages can be ignored as they are not indications of actual SSRAM FIB errors. This problem is resolved in software release 6.4(11). (CSCed34657)

•When running the show flash or show tech-support commands, if you interrupt them by pressing Ctrl-C, the file system might lock for up to 30 minutes.

Workarounds: 1) After entering the show flash command, do not interrupt it. 2) When you run the show tech-support command, interrupt it only after all the show flash information is displayed. This problem is resolved in software release 6.4(11). (CSCeb17930)

•Due to alias counters not being cleared, the switch might unnecessarily go into multicast IGMP fall-back mode. If this occurs, you might see multicast packet loss for existing groups as the multicast router ports time out.

Workaround: Disable IGMP snooping. This problem is resolved in software release 6.4(11). (CSCea08633)

•With redundant Supervisor Engine 2s and high availability disabled, the switch can boot up normally. However, when a non-high availability switchover is performed, the new standby supervisor engine fails to synchronize in local test mode. Several critical failures are then reported and the module fails the boot process and ends up with an error on the console. This problem does not happen when the number of VLAN mappings for a security ACL are reduced to approximately 250 VLANs. This problem is resolved in software release 6.4(11). (CSCee43443)

•Trunking inconsistencies were seen when the following actions were taken on a switch: 1) An EtherChannel was configured using two modules. 2) One of the modules was removed from the switch. 3) An existing VLAN on the switch was added to trunks that were members of the EtherChannel. 4) The removed module was reinserted resulting in trunking inconsistencies. This problem is resolved in software release 6.4(11). (CSCed44129)

•With a Supervisor Engine 2/MSFC2 and port security enabled, the switch might display the following message: "Unable to add entry to earl on port 15/1, rc : -1." If the MSFC2 in slot 2 is active, the switch might display the following message: "Unable to add entry to earl on port 16/1, rc : -1." This problem is resolved in software release 6.4(11). (CSCeb86233)

•With a Supervisor Engine 1 or 1A, the switch might reload with the following log message:

ProcessStatusPing:Module 1 local SCP error detected... resetting module 

Workaround: Remove the faulty module. This problem is resolved in software release 6.4(11). (CSCea38268)

•Setting an existing entry in caqClassifierTable might cause a crash if there is an entry in caqIpAceTable in notInService state. The caqIpAceEntry must be linked to the entry in caqClassifierTable. This problem is resolved in software release 6.4(11). (CSCee27227)

•An SNMP query for cvbStpForwardingMap might return an invalid port state. This problem is not resolved by a power cycle, module reset, disabling and enabling the port, or swapping modules. This problem is resolved in software release 6.4(11). (CSCee58481)

•The MSFC might not be able to ping the sc0 interface on VLAN 1. This is a reoccurrence of the problem seen in CSCeb02380. This problem is resolved in software release 6.4(11). (CSCee66310)

•In rare circumstances, inserting a single-port OC-12 ATM module in a switch where all switching modules are fabric enabled causes the module diagnostics to fail on the ATM module. To put the ATM module into service, enter the reset slot_number command. This problem is resolved in software release 6.4(11). (CSCds12349)

•In a redundant system, after a reset or switchover, you might not be able to view the error log on the standby supervisor engine. Entering the show log command results in an error message. This problem is seen only when Network Time Protocol (NTP) is configured.

Workaround: Reset the switch or perform a supervisor engine failover. This problem is resolved in software release 6.4(11). (CSCee54278)

•IP phone traffic received on an untrusted port should match the configured QoS ACL but the DSCP based on the ACL is not rewritten. This problem is due to the wrong mask being used in the QoS ACL. The problem is caused by a CLI problem; the CLI asks for the IP mask but it should ask for a wild card. The problem is resolved by making the CLI consistent with the Cisco IOS CLI:

–Catalyst operating system CLI:

Console> (enable) set qos acl ip ipacl1 dscp 32 ip 10.1.3.0 ?

  <ip_addr>                  Source IP Mask

Console> (enable)

–Cisco IOS CLI:

msfc2(config)# access-list 199 permit ip 10.1.3.0 ?

  A.B.C.D  Source wildcard bits

This problem is resolved in software release 6.4(11). (CSCec68825)

•An MSFC trunk might not be added to the spanning tree after a switchover in DRM. This problem is resolved in software release 6.4(11). (CSCee20623)

•In extremely rare conditions, the standby supervisor engine might not come up after resetting the switch.

Workaround: Either reset the standby supervisor engine or delay the bootup of the standby supervisor engine. This problem is resolved in software release 6.4(11). (CSCee27392)

•With a Supervisor Engine 2, when a redirect error interrupt occurs, the Supervisor Engine 2 might crash. The Supervisor Engine 2 should recover from the interrupt without crashing. This problem is resolved in software release 6.4(11). (CSCee57837)

•With a Supervisor Engine 2, when ports are added to an EtherChannel one port at a time, the calculated value of a path cost may be incorrect. In some cases, the path cost value displayed with the show spantree mistp-instance command is correct, but the path cost value displayed with the show spantree statistics command may be incorrect. Miscalculated path cost values result in ports going into the blocked state and creates spanning tree topology discrepancies. This problem with the MISTP path cost feature is seen in all software releases up to and including release 6.4(10). This problem is resolved in software release 6.4(11). (CSCee82347)

•With the ip verify unicast reverse-path command configured on an MSFC interface, the interface fails to drop packets when there is a default route without a more specific route.

Workaround: Configure the MSFC interface using the ip verify unicast source reachable-via rx command. This problem is resolved in software release 6.4(11). (CSCec50151)

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)

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