Table Of Contents
Release Notes for Catalyst 6500 Series Software Release 7.x
Release 7.x DRAM Memory Requirements
Boot ROM (ROMMON) Requirements
Redundant Supervisor Engine Configurations
Product and Software Version Matrix
Software Image Version Compatibility
Features for Supervisor Engine Software Release 7.6
Software Release 7.6 Hardware Features
Software Release 7.6 Software Features
Features for Supervisor Engine Software Release 7.5
Software Release 7.5 Hardware Features
Software Release 7.5 Software Features
Features for Supervisor Engine Software Release 7.4
Software Release 7.4 Hardware Features
Software Release 7.4 Software Features
Features for Supervisor Engine Software Release 7.3
Software Release 7.3 Hardware Features
Software Release 7.3 Software Features
Features for Supervisor Engine Software Release 7.2
Software Release 7.2 Hardware Features
Software Release 7.2 Software Features
Features for Supervisor Engine Software Release 7.1
Software Release 7.1 Hardware Features
Software Release 7.1 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 Releases 5.1 Through 5.5
Usage Guidelines and Restrictions
Automatic Quality of Service with Cisco IP Phones
Authentication, Authorization, and Accounting
Binary and Text File Configuration Modes
Open and Resolved Caveats in Software Release 7.6(24)
Open Caveats in Software Release 7.6(24)
Resolved Caveats in Software Release 7.6(24)
Open and Resolved Caveats in Software Release 7.6(23)
Open Caveats in Software Release 7.6(23)
Resolved Caveats in Software Release 7.6(23)
Open and Resolved Caveats in Software Release 7.6(22)
Open Caveats in Software Release 7.6(22)
Resolved Caveats in Software Release 7.6(22)
Open and Resolved Caveats in Software Release 7.6(21)
Open Caveats in Software Release 7.6(21)
Resolved Caveats in Software Release 7.6(21)
Open and Resolved Caveats in Software Release 7.6(20)
Open Caveats in Software Release 7.6(20)
Resolved Caveats in Software Release 7.6(20)
Open and Resolved Caveats in Software Release 7.6(19)
Open Caveats in Software Release 7.6(19)
Resolved Caveats in Software Release 7.6(19)
Open and Resolved Caveats in Software Release 7.6(18)
Open Caveats in Software Release 7.6(18)
Resolved Caveats in Software Release 7.6(18)
Open and Resolved Caveats in Software Release 7.6(17)
Open Caveats in Software Release 7.6(17)
Resolved Caveats in Software Release 7.6(17)
Open and Resolved Caveats in Software Release 7.6(16)
Open Caveats in Software Release 7.6(16)
Resolved Caveats in Software Release 7.6(16)
Open and Resolved Caveats in Software Release 7.6(15)
Open Caveats in Software Release 7.6(15)
Resolved Caveats in Software Release 7.6(15)
Open and Resolved Caveats in Software Release 7.6(14)
Open Caveats in Software Release 7.6(14)
Resolved Caveats in Software Release 7.6(14)
Open and Resolved Caveats in Software Release 7.6(13)
Open Caveats in Software Release 7.6(13)
Resolved Caveats in Software Release 7.6(13)
Open and Resolved Caveats in Software Release 7.6(12)
Open Caveats in Software Release 7.6(12)
Resolved Caveats in Software Release 7.6(12)
Open and Resolved Caveats in Software Release 7.6(11)
Open Caveats in Software Release 7.6(11)
Resolved Caveats in Software Release 7.6(11)
Open and Resolved Caveats in Software Release 7.6(10)
Open Caveats in Software Release 7.6(10)
Resolved Caveats in Software Release 7.6(10)
Open and Resolved Caveats in Software Release 7.6(9)
Open Caveats in Software Release 7.6(9)
Resolved Caveats in Software Release 7.6(9)
Open and Resolved Caveats in Software Release 7.6(8)
Open Caveats in Software Release 7.6(8)
Resolved Caveats in Software Release 7.6(8)
Open and Resolved Caveats in Software Release 7.6(7)
Open Caveats in Software Release 7.6(7)
Resolved Caveats in Software Release 7.6(7)
Open and Resolved Caveats in Software Release 7.6(6)
Open Caveats in Software Release 7.6(6)
Resolved Caveats in Software Release 7.6(6)
Open and Resolved Caveats in Software Release 7.6(5)
Open Caveats in Software Release 7.6(5)
Resolved Caveats in Software Release 7.6(5)
Open and Resolved Caveats in Software Release 7.6(4)
Open Caveats in Software Release 7.6(4)
Resolved Caveats in Software Release 7.6(4)
Open and Resolved Caveats in Software Release 7.6(3a)
Open Caveats in Software Release 7.6(3a)
Resolved Caveats in Software Release 7.6(3a)
Open and Resolved Caveats in Software Release 7.6(3)
Open Caveats in Software Release 7.6(3)
Resolved Caveats in Software Release 7.6(3)
Open and Resolved Caveats in Software Release 7.6(2a)
Open Caveats in Software Release 7.6(2a)
Resolved Caveats in Software Release 7.6(2a)
Open and Resolved Caveats in Software Release 7.6(2)
Open Caveats in Software Release 7.6(2)
Resolved Caveats in Software Release 7.6(2)
Open and Resolved Caveats in Software Release 7.6(1)
Open Caveats in Software Release 7.6(1)
Resolved Caveats in Software Release 7.6(1)
Open and Resolved Caveats in Software Release 7.5(1)
Open Caveats in Software Release 7.5(1)
Resolved Caveats in Software Release 7.5(1)
Open and Resolved Caveats in Software Release 7.4(3)
Open Caveats in Software Release 7.4(3)
Resolved Caveats in Software Release 7.4(3)
Open and Resolved Caveats in Software Release 7.4(2)
Open Caveats in Software Release 7.4(2)
Resolved Caveats in Software Release 7.4(2)
Open and Resolved Caveats in Software Release 7.3(2)
Open Caveats in Software Release 7.3(2)
Resolved Caveats in Software Release 7.3(2)
Open and Resolved Caveats in Software Release 7.3(1)
Open Caveats in Software Release 7.3(1)
Resolved Caveats in Software Release 7.3(1)
Open and Resolved Caveats in Software Release 7.2(2)
Open Caveats in Software Release 7.2(2)
Resolved Caveats in Software Release 7.2(2)
Open and Resolved Caveats in Software Release 7.1(2)
Open Caveats in Software Release 7.1(2)
Resolved Caveats in Software Release 7.1(2)
Open and Resolved Caveats in Software Release 7.1(1a)
Open Caveats in Software Release 7.1(1a)
Resolved Caveats in Software Release 7.1(1a)
Open and Resolved Caveats in Software Release 7.1(1)
Open Caveats in Software Release 7.1(1)
Resolved Caveats in Software Release 7.1(1)
Catalyst Software Image Upgrade Procedure
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Catalyst 6500 Series Software Release 7.x
Revised: April 02, 2008, OL-1982-29Current Release
7.6(24)—February 26, 2008
Previous Releases: 7.6(23), 7.6(22), 7.6(21),7.6(20), 7.6(19), 7.6(18), 7.6(17), 7.6(16), 7.6(15), 7.6(14), 7.6(13), 7.6(12)-GD release, 7.6(11), 7.6(10), 7.6(9), 7.6(8), 7.6(7), 7.6(6), 7.6(5), 7.6(4)-Supervisor Engine 2 images deferred, 7.6(3a)-Supervisor Engine 2 images deferred, 7.6(3)-Supervisor Engine 2 images deferred, 7.6(2a)-Supervisor Engine 2 images deferred, 7.6(2)-Supervisor Engine 2 images deferred, 7.6(1)-Supervisor Engine 2 images deferred, 7.5(1), 7.4(3), 7.4(2), 7.3(2), 7.3(1), 7.2(2), 7.1(2), 7.1(1a), 7.1(1)
CautionThe Supervisor Engines 1 and 1A are not supported in Catalyst software release 7.6(18) and above. 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
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/index.htm
Note
Contents
This document consists of these sections:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Release 7.x DRAM Memory Requirements
Supervisor Engine 2: The Catalyst 6500 series Supervisor Engine 2 ships with 128-MB DRAM, which fully supports software release 7.x.
Supervisor Engine 1: Early versions of the Catalyst 6500 series Supervisor Engine 1 shipped with 64-MB DRAM (currently, new Supervisor Engine 1 modules ship with 128-MB DRAM). Depending on the software release you are running, be aware of these DRAM memory requirements:
•
•
Supervisor Engine 1 upgrade options: With the exception of WS-X6K-SUP1A-MSFC, all other Supervisor Engine 1 modules can upgrade to 128-MB DRAM using the MEM-S1-128MB= upgrade kit. For detailed information on the MEM-S1-128MB= upgrade, refer to the Catalyst 6500 Series Switch Supervisor Engine 1A DRAM Upgrade Installation Note at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/78_14357.htmTo upgrade to 128-MB DRAM on the WS-X6K-SUP1A-MSFC, use the MEM-S1-128MB-UPG= upgrade kit which also includes an MSFC2 upgrade.
Caution
Boot ROM (ROMMON) 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 7.x(x) is 5.2(1). The default (shipping) image for software releases 6.x(x) and 7.x(x) 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
Upgrading the Boot ROM
Follow these guidelines to upgrade the boot ROM (ROMMON) on Supervisor Engine 1 or 1A:
Note
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_13488.htm•
•
•
Note
•
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/cfgnotes/78_10142.htmFlash PC Card Support
The following Flash PC cards are supported on Catalyst 6500 series switches:
•
•
•
•
Prior to software release 7.5(1), Supervisor Engine 1 and Supervisor Engine 2 supported the following Flash PC cards:
•
•
With software releases 7.5(1) and later, additional Flash PC card support was added as follows:
•
•
Note
Note
Note
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 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, the MSFC2 bootloader and Cisco IOS image can be put 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, your switch can have the following configurations:
•
Slot 2—Supervisor Engine 2, PFC2, MSFC2•
Slot 2—Supervisor Engine 2, PFC2•
Slot 2—Supervisor Engine 1, PFC, MSFC2•
Slot 2—Supervisor Engine 1, PFC, MSFC1•
Slot 2—Supervisor Engine 1, PFC•
Slot 2—Supervisor Engine 1These configuration requirements apply to all Catalyst 6500 series 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 supervisor engine software version for Catalyst 6500 series modules and chassis.
Note
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 6500 Series Switch Software Configuration Guide:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/sw_7_1/index.htm
Note
Table 1 Minimum and Recommended Supervisor Engine Software Versions
"=" for spares
Software Version
Supervisor Engine
Software VersionWS-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/1p2q2t6.1(1d)
6.4(21)
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/1p2q2t6.1(1d)
6.4(21)
WS-X6K-S2-PFC2
Supervisor Engine 2, dual 1000BASE-X GBIC uplinks, fabric-enabled, and PFC2
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t6.1(1d)
6.4(21)
WS-X6K-S1A-MSFC2
Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, PFC, and MSFC2
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.4(3)
6.4(21)
WS-X6K-SUP1A-MSFC
Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, PFC, and MSFC
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.3(1a)CSX
6.4(21)
WS-X6K-SUP1A-PFC
Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks, and PFC
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.3(1a)CSX
6.4(21)
WS-X6K-SUP1A-2GE
Supervisor Engine 1A, dual 1000BASE-X GBIC uplinks
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.3(1a)CSX
6.4(21)
WS-X6K-SUP1-2GE
Supervisor Engine 1, dual 1000BASE-X GBIC uplinks
QoS port architecture (Rx/Tx): 1q4t/2q2t5.1(1)CSX
6.4(21)
WS-C6500-SFM
Switch Fabric Module to support fabric-enabled modules
6.1(1d)
6.4(21)
WS-X6500-SFM2
Switch Fabric Module version 2
6.2(2)
6.4(21)
WS-X6501-10GEX4
1-port 10GBASE-EX4 Metro 10-Gigabit Ethernet, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q8t/1p2q1t7.1(1)
7.6(9)
WS-X6502-10GE
1-port 10GBASE-E Serial 10-Gigabit Ethernet, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q8t/1p2q1tNote: The WS-X6502-10GE module does not support ISL encapsulation.
7.1(1)
7.6(9)
WS-G6483
10GBASE-ER Serial 1550-nm extended-reach Optical Interface Module (OIM)
7.2(2)
7.6(9)
WS-G6488
10GBASE-LR Serial 1310-nm long-haul OIM
7.1(1)
7.6(9)
WS-X6148-GE-TX
WS-X6148V-GE-TX48-port 10/100/1000BASE-TX switching module (WS-X6148V-GE-TX provides inline power to IP telephones)
QoS port architecture (Rx/Tx): 1q2t/1p2q2t7.6(1)
7.6(9)
WS-X6548-GE-TX
WS-X6548V-GE-TX48-port 10/100/1000BASE-TX switching module, fabric-enabled (WS-X6548V-GE-TX provides inline power to IP telephones)
QoS port architecture (Rx/Tx): 1q2t/1p2q2t7.6(1)
7.6(9)
WS-X6148-GE-TX
WS-X6148V-GE-TX48-port 10/100/1000BASE-TX switching module (WS-X6148V-GE-TX provides inline power to IP telephones)
QoS port architecture (Rx/Tx): 1q2t/1p2q2t7.6(1)
7.6(9)
WS-X6548-GE-TX
WS-X6548V-GE-TX48-port 10/100/1000BASE-TX switching module, fabric-enabled (WS-X6548V-GE-TX provides inline power to IP telephones)
QoS port architecture (Rx/Tx): 1q2t/1p2q2t7.6(1)
7.6(9)
WS-X6516A-GBIC
16-port Gigabit Ethernet GBIC switching module, fabric-enabled, 1-MB per-port packet buffers
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t7.5(1)
7.6(9)
WS-X6516-GBIC
16-port Gigabit Ethernet GBIC switching module, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t6.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/1p2q2t6.2(2)
6.4(11)
WS-X6416-GBIC
16-port Gigabit Ethernet GBIC switching module
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.4(2)
6.4(11)
WS-X6416-GE-MT
16-port Gigabit Ethernet MT-RJ
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.3(5a)CSX
6.4(11)
WS-X6316-GE-TX
16-port 1000BASE-TX RJ-45 Gigabit Ethernet
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.4(2)
6.4(11)
WS-X6408A-GBIC
8-port Gigabit Ethernet GBIC
QoS port architecture (Rx/Tx): 1p1q4t/1p2q2t5.3(1a)CSX
6.4(11)
WS-X6408-GBIC
8-port Gigabit Ethernet GBIC
QoS port architecture (Rx/Tx): 1q4t/2q2t5.1(1)CSX
6.4(11)
WS-X6524-100FX-MM
24-port 100FX Ethernet multimode, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q0t/1p3q1t7.1(1)
7.6(9)
WS-X6324-100FX-SM
WS-X6324-100FX-MM24-port 100FX single mode or multimode MT-RJ with 128K per-port packet buffers
QoS port architecture (Rx/Tx): 1q4t/2q2t5.4(2)
6.4(11)
WS-X6224-100FX-MT
24-port 100FX Multimode MT-RJ
QoS port architecture (Rx/Tx): 1q4t/2q2t5.1(1)CSX
6.4(11)
WS-X6548-RJ-21
48-port 10/100BASE-TX RJ-21, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q0t/1p3q1t6.2(2)
6.4(11)
WS-X6548-RJ-45
48-port 10/100BASE-TX RJ-45, fabric-enabled
QoS port architecture (Rx/Tx): 1p1q0t/1p3q1t6.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/2q2t6.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/2q2tWithout
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-X6148-RJ-45
WS-X6148-RJ-45V48-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/2q2tFor software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
WS-X6148-RJ21
WS-X6148-RJ21V48-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/2q2tFor software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
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/2q2t5.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/2q2t5.3(2)CSX
6.4(11)
WS-X6248-TEL
48-port 10/100BASE-TX RJ-21
QoS port architecture (Rx/Tx): 1q4t/2q2t5.2(1)CSX
6.4(11)
WS-X6024-10FL-MT
24-port 10BASE-FL MT-RJ
QoS port architecture (Rx/Tx): 1q4t/2q2t5.3(3)CSX
6.4(11)
Power Over Ethernet Daughter Cards
IEEE 802.3af PoE daughter card for:
WS-X6148X2-45AF
8.2(1)
8.3(3)
WS-X6196-21AF
8.4(1)
8.4(1)
IEEE 802.3af PoE daughter card for:
WS-X6148A-GE-45AF
8.4(1)
8.4(1)
WS-X6148V-GE-TX
7.6(1)
7.6(9)
WS-X6148-GE-45AF
8.2(1)
8.3(3)
WS-X6548V-GE-TX
7.6(1)
7.6(9)
WS-X6548-GE-45AF
8.2(1)
8.3(3)
IEEE 802.3af PoE daughter card for:
WS-X6148A-45AF
8.4(1)
8.4(1)
WS-X6148-RJ-45V
For software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
WS-X6148-RJ21V
For software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
IEEE 802.3af PoE daughter card for:
WS-X6548V-GE-TX
7.6(1)
7.6(9)
WS-X6148V-GE-TX
7.6(1)
7.6(9)
IEEE 802.3af PoE daughter card for:
WS-X6348-RJ-45V
5.5(1)
6.4(11)
WS-X6348-RJ21V
6.2(2)
6.4(11)
WS-X6148-RJ-45V
For software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
WS-X6148-RJ21V
For software releases 6.x: 6.4(1)
For software releases 7.x: 7.2(2)
For software releases 6.x: 6.4(11)
For software releases 7.x: 7.6(9)
WS-SVC-CMM
Communication Media Module
7.6(12)
8.3(3)
WS-SVC-CMM-6E
16-port E1 interface port adapter
7.6(12)
8.3(3)
WS-SVC-CMM-6T1
6-port T1 interface port adapter
7.6(12)
8.3(3)
WS-SVC-CMM-24FXS
24-port FXS interface port adapter
7.6(12)
8.3(3)
WS-SVC-CMM-ACT
Ad-hoc conferencing and transcoding port adapter
7.6(12)
8.3(3)
WS-X6624-FXS
24-port FXS analog interface module
5.5(1)
6.4(11)
WS-X6608-T1
WS-X6608-E18-port T1/E1 PSTN interface modules
5.5(1)
6.4(11)
WS-X6182-2PA
FlexWAN Module
5.4(2)
6.4(11)
WS-X6381-IDS
Intrusion Detection System Module
6.1(1d)
6.4(11)
WS-SVC-IDSM2-BUN-K9
Intrusion Detection System Module 2
7.5(1)
7.6(9)
WS-X6380-NAM
Network Analysis Module, 256-MB RAM
5.5(1)
6.4(11)
WS-SVC-NAM-1
Network Analysis Module, 512-MB RAM, fabric-enabled
7.3(1)
7.6(9)
WS-SVC-NAM-2
Network Analysis Module, 1-GB RAM, fabric enabled, accelerator daughter card
7.3(1)
7.6(9)
Firewall Services Module7
WS-SVC-FWM-1-K9
Firewall Services Module
7.5(1)
7.6(9)
SSL Services Module8
WS-SVC-SSL-1
SSL Services Module
7.5(1)
7.6(9)
Content Switching Module (CSM)9
WS-X6066-SLB-APC
Content Switching Module
7.5(1)
7.6(9)
Content Services Gateway (CSG)10
WS-SVC-CSG-1
Content Services Gateway
7.6(1)
7.6(9)
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)
WS-X6302-MSM
Multilayer Switch Module
5.2(1)CSX
6.4(11)
OSM-4GE-WAN-GBIC
4-port Gigabit Ethernet Optical Services Module
6.1(2)
6.4(11)
OC-12 Packet over SONET15
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-LR16 , 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)
OC-12 Packet over SONET15
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 SONET14
OSM-4OC3-POS-SI
4-port OC-3c/STM-1c POS Optical Services Module, SM-IR, with 4 Gigabit Ethernet ports
7.1(1)
7.6(9)
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 SONET14
OSM-1OC48-POS-SS
1-port OC-48c/STM-16c POS Optical Services
Module, SM-SR, with 4 Gigabit Ethernet ports6.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 ports6.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 ports6.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-3000W
3000W AC power supply
7.5(1)
7.6(9)
WS-CAC-4000W
4000W AC power supply
6.1(3)
6.4(11)
PWR-4000-DC17
4000W DC power supply
6.1(3)
8.3(3)
PWR-950-AC18
950W AC power supply
7.5(1)
7.6(9)
PWR-950-DC18
950W DC power supply
7.5(1)
7.6(9)
PWR-1900-AC/619
1900W AC power supply
7.2(2)
7.6(9)
PWR-1900-DC18
1900W DC power supply
7.2(2)
7.6(9)
WS-C6513
Catalyst 6513 chassis:
•
•
•
6.2(2)
6.4(11)
WS-C6509
Catalyst 6509 chassis:
•
•
5.1(1)CSX
6.4(11)
WS-C6509-NEB
Catalyst 6509-NEB chassis:
•
•
5.4(2)
6.4(11)
WS-C650320
Catalyst 6503 chassis:
•
•
•
7.4(2)
7.6(9)
WS-C6009
Catalyst 6009 chassis:
•
•
5.1(1)CSX
6.4(11)
WS-C6506
Catalyst 6506 chassis:
•
•
5.2(1)CSX
6.4(11)
WS-C6006
Catalyst 6006 chassis:
•
•
5.2(1)CSX
6.4(11)
OSR-7609-AC, -DC
Cisco 7609 router chassis:
•
•
•
6.1(1b)
6.4(11)
CISCO7603
Cisco 7603 router chassis:
•
•
•
7.1(1)
7.6(9)
CISCO7606
Cisco 7606 router chassis:
•
•
•
7.2(2)
7.6(9)
CISCO7613
Cisco 7613 router chassis:
•
•
•
7.6(1)
7.6(9)
1 Not supported in the WS-C6513 chassis.
2 Not supported in software release 7.6(18). 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.html3 Refer to the Catalyst 6500 Series Switch FlexWAN Module Installation and Configuration Note.
4 Refer to the Catalyst 6500 Series Switch Intrusion Detection System Module Installation and Configuration Note.
5 Refer to the Network Analysis Module Installation and Configuration Note.
6 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.
7 Refer to the Catalyst 6500 Series Switch and 7600 Series Firewall Services Module Installation and Configuration Note.
8 Refer to the Catalyst 6500 Series Switch SSL Services Module Installation and Configuration Note.
9 Refer to the Cisco Content Switching Module Installation and Configuration Guide.
10 Refer to the Cisco Content Services Gateway Installation and Configuration Guide.
11 Refer to the ATM Configuration Guide and Command Reference.
12 Refer to the Multilayer Switch Module Release Notes.
13 Refer to the Optical Services Module Installation and Configuration Note.
14 Channelized OSMs are not supported on Catalyst 6500 series switches; they are supported only on the Cisco 7600 series router platform.
15 Also has four Layer 2 Gigabit Ethernet ports.
16 Single-mode, long reach.
17 The full 4000W is only available with software release 8.1(1) and later releases. With software release 6.1(3) and later 6.x and 7.x releases, the maximum wattage is 2506.56W.
18 Supported only on the WS-C6503 and CISCO7603 chassis.
19 Supported only on the CISCO7606 chassis.
20 The CiscoView 7.4(2) image for the Catalyst 6500 series switch does not support the WS-C6503 chassis. Support for this chassis will be included in the next CiscoView release.
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 6500 series supervisor engine software.
Caution
Note
Note
Note
Note
Note
Note
Note
Note
Table 2 Orderable Software Images
7.6(24) Flash image
cat6000-sup2k8.7-6-24.bin
SC6K-SUP2K8-7.6
7.6(24) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-24.bin
SC6K-SUP2CVK8-7.6
7.6(24) Flash image (Secure Shell)
cat6000-sup2k9.7-6-24.bin
SC6K-SUP2K9-7.6
7.6(24) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-24.bin
SC6K-SUP2CVK9-7.6
7.6(23) Flash image
cat6000-sup2k8.7-6-23.bin
SC6K-SUP2K8-7.6
7.6(23) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-23.bin
SC6K-SUP2CVK8-7.6
7.6(23) Flash image (Secure Shell)
cat6000-sup2k9.7-6-23.bin
SC6K-SUP2K9-7.6
7.6(23) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-23.bin
SC6K-SUP2CVK9-7.6
7.6(22) Flash image
cat6000-sup2k8.7-6-22.bin
SC6K-SUP2K8-7.6
7.6(22) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-22.bin
SC6K-SUP2CVK8-7.6
7.6(22) Flash image (Secure Shell)
cat6000-sup2k9.7-6-22.bin
SC6K-SUP2K9-7.6
7.6(22) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-22.bin
SC6K-SUP2CVK9-7.6
7.6(21) Flash image
cat6000-sup2k8.7-6-21.bin
SC6K-SUP2K8-7.6
7.6(21) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-21.bin
SC6K-SUP2CVK8-7.6
7.6(21) Flash image (Secure Shell)
cat6000-sup2k9.7-6-21.bin
SC6K-SUP2K9-7.6
7.6(21) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-21.bin
SC6K-SUP2CVK9-7.6
7.6(20) Flash image
cat6000-sup2k8.7-6-20.bin
SC6K-SUP2K8-7.6
7.6(20) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-20.bin
SC6K-SUP2CVK8-7.6
7.6(20) Flash image (Secure Shell)
cat6000-sup2k9.7-6-20.bin
SC6K-SUP2K9-7.6
7.6(20) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-20.bin
SC6K-SUP2CVK9-7.6
7.6(19) Flash image
cat6000-sup2k8.7-6-19.bin
SC6K-SUP2K8-7.6
7.6(19) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-19.bin
SC6K-SUP2CVK8-7.6
7.6(19) Flash image (Secure Shell)
cat6000-sup2k9.7-6-19.bin
SC6K-SUP2K9-7.6
7.6(19) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-19.bin
SC6K-SUP2CVK9-7.6
7.6(18) Flash image
cat6000-sup2k8.7-6-18.bin
SC6K-SUP2K8-7.6
7.6(18) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-18.bin
SC6K-SUP2CVK8-7.6
7.6(18) Flash image (Secure Shell)
cat6000-sup2k9.7-6-18.bin
SC6K-SUP2K9-7.6
7.6(18) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-18.bin
SC6K-SUP2CVK9-7.6
7.6(17) Flash image
cat6000-sup2k8.7-6-17.bin
SC6K-SUP2K8-7.6
7.6(17) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-17.bin
SC6K-SUP2CVK8-7.6
7.6(17) Flash image (Secure Shell)
cat6000-sup2k9.7-6-17.bin
SC6K-SUP2K9-7.6
7.6(17) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-17.bin
SC6K-SUP2CVK9-7.6
7.6(16) Flash image
cat6000-sup2k8.7-6-16.bin
SC6K-SUP2K8-7.6
7.6(16) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-16.bin
SC6K-SUP2CVK8-7.6
7.6(16) Flash image (Secure Shell)
cat6000-sup2k9.7-6-16.bin
SC6K-SUP2K9-7.6
7.6(16) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-16.bin
SC6K-SUP2CVK9-7.6
7.6(15) Flash image
cat6000-sup2k8.7-6-15.bin
SC6K-SUP2K8-7.6
7.6(15) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-15.bin
SC6K-SUP2CVK8-7.6
7.6(15) Flash image (Secure Shell)
cat6000-sup2k9.7-6-15.bin
SC6K-SUP2K9-7.6
7.6(15) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-15.bin
SC6K-SUP2CVK9-7.6
7.6(14) Flash image
cat6000-sup2k8.7-6-14.bin
SC6K-SUP2K8-7.6
7.6(14) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-14.bin
SC6K-SUP2CVK8-7.6
7.6(14) Flash image (Secure Shell)
cat6000-sup2k9.7-6-14.bin
SC6K-SUP2K9-7.6
7.6(14) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-14.bin
SC6K-SUP2CVK9-7.6
7.6(13) Flash image
cat6000-sup2k8.7-6-13.bin
SC6K-SUP2K8-7.6
7.6(13) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-13.bin
SC6K-SUP2CVK8-7.6
7.6(13) Flash image (Secure Shell)
cat6000-sup2k9.7-6-13.bin
SC6K-SUP2K9-7.6
7.6(13) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-13.bin
SC6K-SUP2CVK9-7.6
7.6(12) Flash image
cat6000-sup2k8.7-6-12.bin
SC6K-SUP2K8-7.6
7.6(12) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-12.bin
SC6K-SUP2CVK8-7.6
7.6(12) Flash image (Secure Shell)
cat6000-sup2k9.7-6-12.bin
SC6K-SUP2K9-7.6
7.6(12) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-12.bin
SC6K-SUP2CVK9-7.6
7.6(11) Flash image
cat6000-sup2k8.7-6-11.bin
SC6K-SUP2K8-7.6
7.6(11) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-11.bin
SC6K-SUP2CVK8-7.6
7.6(11) Flash image (Secure Shell)
cat6000-sup2k9.7-6-11.bin
SC6K-SUP2K9-7.6
7.6(11) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-11.bin
SC6K-SUP2CVK9-7.6
7.6(10) Flash image
cat6000-sup2k8.7-6-10.bin
SC6K-SUP2K8-7.6
7.6(10) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-10.bin
SC6K-SUP2CVK8-7.6
7.6(10) Flash image (Secure Shell)
cat6000-sup2k9.7-6-10.bin
SC6K-SUP2K9-7.6
7.6(10) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-10.bin
SC6K-SUP2CVK9-7.6
7.6(9) Flash image
cat6000-sup2k8.7-6-9.bin
SC6K-SUP2K8-7.6
7.6(9) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-9.bin
SC6K-SUP2CVK8-7.6
7.6(9) Flash image (Secure Shell)
cat6000-sup2k9.7-6-9.bin
SC6K-SUP2K9-7.6
7.6(9) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-9.bin
SC6K-SUP2CVK9-7.6
7.6(8) Flash image
cat6000-sup2k8.7-6-8.bin
SC6K-SUP2K8-7.6
7.6(8) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-8.bin
SC6K-SUP2CVK8-7.6
7.6(8) Flash image (Secure Shell)
cat6000-sup2k9.7-6-8.bin
SC6K-SUP2K9-7.6
7.6(8) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-8.bin
SC6K-SUP2CVK9-7.6
7.6(7) Flash image
cat6000-sup2k8.7-6-7.bin
SC6K-SUP2K8-7.6
7.6(7) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-7.bin
SC6K-SUP2CVK8-7.6
7.6(7) Flash image (Secure Shell)
cat6000-sup2k9.7-6-7.bin
SC6K-SUP2K9-7.6
7.6(7) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-7.bin
SC6K-SUP2CVK9-7.6
7.6(6) Flash image
cat6000-sup2k8.7-6-6.bin
SC6K-SUP2K8-7.6
7.6(6) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-6.bin
SC6K-SUP2CVK8-7.6
7.6(6) Flash image (Secure Shell)
cat6000-sup2k9.7-6-6.bin
SC6K-SUP2K9-7.6
7.6(6) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-6.bin
SC6K-SUP2CVK9-7.6
7.6(5) Flash image
cat6000-sup2k8.7-6-5.bin
SC6K-SUP2K8-7.6
7.6(5) Flash image (CiscoView)
cat6000-sup2cvk8.7-6-5.bin
SC6K-SUP2CVK8-7.6
7.6(5) Flash image (Secure Shell)
cat6000-sup2k9.7-6-5.bin
SC6K-SUP2K9-7.6
7.6(5) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-6-5.bin
SC6K-SUP2CVK9-7.6
7.5(1) Flash image
cat6000-sup2k8.7-5-1.bin
SC6K-SUP2K8-7.5.1
7.5(1) Flash image (CiscoView)
cat6000-sup2cvk8.7-5-1.bin
SC6K-SUP2CVK8-7.5.1
7.5(1) Flash image (Secure Shell)
cat6000-sup2k9.7-5-1.bin
SC6K-SUP2K9-7.5.1
7.5(1) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-5-1.bin
SC6K-SUP2CVK9-7.5.1
7.4(3) Flash image
cat6000-sup2k8.7-4-3.bin
SC6K-SUP2K8-7.4.3
7.4(3) Flash image (CiscoView)
cat6000-sup2cvk8.7-4-3.bin
SC6K-SUP2CVK8-7.4.3
7.4(3) Flash image (Secure Shell)
cat6000-sup2k9.7-4-3.bin
SC6K-SUP2K9-7.4.3
7.4(3) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-4-3.bin
SC6K-SUP2CVK9-7.4.3
7.4(2) Flash image
cat6000-sup2k8.7-4-2.bin
SC6K-SUP2K8-7.4.2
7.4(2) Flash image (CiscoView)
cat6000-sup2cvk8.7-4-2.bin
SC6K-SUP2CVK8-7.4.2
7.4(2) Flash image (Secure Shell)
cat6000-sup2k9.7-4-2.bin
SC6K-SUP2K9-7.4.2
7.4(2) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-4-2.bin
SC6K-SUP2CVK9-7.4.2
7.3(2) Flash image
cat6000-sup2k8.7-3-2.bin
SC6K-SUP2K8-7.3.2
7.3(2) Flash image (CiscoView)
cat6000-sup2cvk8.7-3-2.bin
SC6K-SUP2CVK8-7.3.2
7.3(2) Flash image (Secure Shell)
cat6000-sup2k9.7-3-2.bin
SC6K-SUP2K9-7.3.2
7.3(2) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-3-2.bin
SC6K-SUP2CVK9-7.3.2
7.3(1) Flash image
cat6000-sup2k8.7-3-1.bin
SC6K-SUP2K8-7.3.1
7.3(1) Flash image (CiscoView)
cat6000-sup2cvk8.7-3-1.bin
SC6K-SUP2CVK8-7.3.1
7.3(1) Flash image (Secure Shell)
cat6000-sup2k9.7-3-1.bin
SC6K-SUP2K9-7.3.1
7.3(1) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-3-1.bin
SC6K-SUP2CVK9-7.3.1
7.2(2) Flash image
cat6000-sup2k8.7-2-2.bin
SC6K-SUP2K8-7.2.2
7.2(2) Flash image (CiscoView)
cat6000-sup2cvk8.7-2-2.bin
SC6K-SUP2CVK8-7.2.2
7.2(2) Flash image (Secure Shell)
cat6000-sup2k9.7-2-2.bin
SC6K-SUP2K9-7.2.2
7.2(2) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-2-2.bin
SC6K-SUP2CVK9-7.2.2
7.1(2) Flash image
cat6000-sup2k8.7-1-2.bin
SC6K-SUP2K8-7.1.2
7.1(2) Flash image (CiscoView)
cat6000-sup2cvk8.7-1-2.bin
SC6K-SUP2CVK8-7.1.2
7.1(2) Flash image (Secure Shell)
cat6000-sup2k9.7-1-2.bin
SC6K-SUP2K9-7.1.2
7.1(2) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-1-2.bin
SC6K-SUP2CVK9-7.1.2
7.1(1a) Flash image
cat6000-sup2k8.7-1-1a.bin
SC6K-SUP2K8-7.1.1a
7.1(1a) Flash image (CiscoView)
cat6000-sup2cvk8.7-1-1a.bin
SC6K-SUP2CVK8-7.1.1a
7.1(1a) Flash image (Secure Shell)
cat6000-sup2k9.7-1-1a.bin
SC6K-SUP2K9-7.1.1a
7.1(1a) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-1-1a.bin
SC6K-SUP2CVK9-7.1.1a
7.1(1) Flash image
cat6000-sup2k8.7-1-1.bin
SC6K-SUP2K8-7.1.1
7.1(1) Flash image (CiscoView)
cat6000-sup2cvk8.7-1-1.bin
SC6K-SUP2CVK8-7.1.1
7.1(1) Flash image (Secure Shell)
cat6000-sup2k9.7-1-1.bin
SC6K-SUP2K9-7.1.1
7.1(1) Flash image (Secure Shell and CiscoView)
cat6000-sup2cvk9.7-1-1.bin
SC6K-SUP2CVK9-7.1.1
7.6(17) Flash image
cat6000-supk8.7-6-17.bin
SC6K-SUPK8-7.6
7.6(17) Flash image (CiscoView)
cat6000-supcvk8.7-6-17.bin
SC6K-SUPCVK8-7.6
7.6(17) Flash image (Secure Shell)
cat6000-supk9.7-6-17.bin
SC6K-SUPK9-7.6
7.6(17) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-17.bin
SC6K-SUPCVK9-7.6
7.6(16) Flash image
cat6000-supk8.7-6-16.bin
SC6K-SUPK8-7.6
7.6(16) Flash image (CiscoView)
cat6000-supcvk8.7-6-16.bin
SC6K-SUPCVK8-7.6
7.6(16) Flash image (Secure Shell)
cat6000-supk9.7-6-16.bin
SC6K-SUPK9-7.6
7.6(16) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-16.bin
SC6K-SUPCVK9-7.6
7.6(15) Flash image
cat6000-supk8.7-6-15.bin
SC6K-SUPK8-7.6
7.6(15) Flash image (CiscoView)
cat6000-supcvk8.7-6-15.bin
SC6K-SUPCVK8-7.6
7.6(15) Flash image (Secure Shell)
cat6000-supk9.7-6-15.bin
SC6K-SUPK9-7.6
7.6(15) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-15.bin
SC6K-SUPCVK9-7.6
7.6(14) Flash image
cat6000-supk8.7-6-14.bin
SC6K-SUPK8-7.6
7.6(14) Flash image (CiscoView)
cat6000-supcvk8.7-6-14.bin
SC6K-SUPCVK8-7.6
7.6(14) Flash image (Secure Shell)
cat6000-supk9.7-6-14.bin
SC6K-SUPK9-7.6
7.6(14) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-14.bin
SC6K-SUPCVK9-7.6
7.6(13) Flash image
cat6000-supk8.7-6-13.bin
SC6K-SUPK8-7.6
7.6(13) Flash image (CiscoView)
cat6000-supcvk8.7-6-13.bin
SC6K-SUPCVK8-7.6
7.6(13) Flash image (Secure Shell)
cat6000-supk9.7-6-13.bin
SC6K-SUPK9-7.6
7.6(13) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-13.bin
SC6K-SUPCVK9-7.6
7.6(12) Flash image
cat6000-supk8.7-6-12.bin
SC6K-SUPK8-7.6
7.6(12) Flash image (CiscoView)
cat6000-supcvk8.7-6-12.bin
SC6K-SUPCVK8-7.6
7.6(12) Flash image (Secure Shell)
cat6000-supk9.7-6-12.bin
SC6K-SUPK9-7.6
7.6(12) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-12.bin
SC6K-SUPCVK9-7.6
7.6(11) Flash image
cat6000-supk8.7-6-11.bin
SC6K-SUPK8-7.6
7.6(11) Flash image (CiscoView)
cat6000-supcvk8.7-6-11.bin
SC6K-SUPCVK8-7.6
7.6(11) Flash image (Secure Shell)
cat6000-supk9.7-6-11.bin
SC6K-SUPK9-7.6
7.6(11) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-11.bin
SC6K-SUPCVK9-7.6
7.6(10) Flash image
cat6000-supk8.7-6-10.bin
SC6K-SUPK8-7.6
7.6(10) Flash image (CiscoView)
cat6000-supcvk8.7-6-10.bin
SC6K-SUPCVK8-7.6
7.6(10) Flash image (Secure Shell)
cat6000-supk9.7-6-10.bin
SC6K-SUPK9-7.6
7.6(10) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-10.bin
SC6K-SUPCVK9-7.6
7.6(9) Flash image
cat6000-supk8.7-6-9.bin
SC6K-SUPK8-7.6
7.6(9) Flash image (CiscoView)
cat6000-supcvk8.7-6-9.bin
SC6K-SUPCVK8-7.6
7.6(9) Flash image (Secure Shell)
cat6000-supk9.7-6-9.bin
SC6K-SUPK9-7.6
7.6(9) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-9.bin
SC6K-SUPCVK9-7.6
7.6(8) Flash image
cat6000-supk8.7-6-8.bin
SC6K-SUPK8-7.6
7.6(8) Flash image (CiscoView)
cat6000-supcvk8.7-6-8.bin
SC6K-SUPCVK8-7.6
7.6(8) Flash image (Secure Shell)
cat6000-supk9.7-6-8.bin
SC6K-SUPK9-7.6
7.6(8) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-8.bin
SC6K-SUPCVK9-7.6
7.6(7) Flash image
cat6000-supk8.7-6-7.bin
SC6K-SUPK8-7.6
7.6(7) Flash image (CiscoView)
cat6000-supcvk8.7-6-7.bin
SC6K-SUPCVK8-7.6
7.6(7) Flash image (Secure Shell)
cat6000-supk9.7-6-7.bin
SC6K-SUPK9-7.6
7.6(7) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-7.bin
SC6K-SUPCVK9-7.6
7.6(6) Flash image
cat6000-supk8.7-6-6.bin
SC6K-SUPK8-7.6
7.6(6) Flash image (CiscoView)
cat6000-supcvk8.7-6-6.bin
SC6K-SUPCVK8-7.6
7.6(6) Flash image (Secure Shell)
cat6000-supk9.7-6-6.bin
SC6K-SUPK9-7.6
7.6(6) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-6.bin
SC6K-SUPCVK9-7.6
7.6(5) Flash image
cat6000-supk8.7-6-5.bin
SC6K-SUPK8-7.6
7.6(5) Flash image (CiscoView)
cat6000-supcvk8.7-6-5.bin
SC6K-SUPCVK8-7.6
7.6(5) Flash image (Secure Shell)
cat6000-supk9.7-6-5.bin
SC6K-SUPK9-7.6
7.6(5) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-5.bin
SC6K-SUPCVK9-7.6
7.6(4) Flash image
cat6000-supk8.7-6-4.bin
SC6K-SUPK8-7.6
7.6(4) Flash image (CiscoView)
cat6000-supcvk8.7-6-4.bin
SC6K-SUPCVK8-7.6
7.6(4) Flash image (Secure Shell)
cat6000-supk9.7-6-4.bin
SC6K-SUPK9-7.6
7.6(4) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-4.bin
SC6K-SUPCVK9-7.6
7.6(3a) Flash image
cat6000-supk8.7-6-3a.bin
SC6K-SUPK8-7.6
7.6(3a) Flash image (CiscoView)
cat6000-supcvk8.7-6-3a.bin
SC6K-SUPCVK8-7.6
7.6(3a) Flash image (Secure Shell)
cat6000-supk9.7-6-3a.bin
SC6K-SUPK9-7.6
7.6(3a) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-3a.bin
SC6K-SUPCVK9-7.6
7.6(3) Flash image
cat6000-supk8.7-6-3.bin
SC6K-SUPK8-7.6
7.6(3) Flash image (CiscoView)
cat6000-supcvk8.7-6-3.bin
SC6K-SUPCVK8-7.6
7.6(3) Flash image (Secure Shell)
cat6000-supk9.7-6-3.bin
SC6K-SUPK9-7.6
7.6(3) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-3.bin
SC6K-SUPCVK9-7.6
7.6(2a) Flash image
cat6000-supk8.7-6-2a.bin
SC6K-SUPK8-7.6.2a
7.6(2a) Flash image (Secure Shell)
cat6000-supk9.7-6-2a.bin
SC6K-SUPK9-7.6.2a
7.6(2) Flash image
cat6000-supk8.7-6-2.bin
SC6K-SUPK8-7.6.2
7.6(2) Flash image (CiscoView)
cat6000-supcvk8.7-6-2.bin
SC6K-SUPCVK8-7.6.2
7.6(2) Flash image (Secure Shell)
cat6000-supk9.7-6-2.bin
SC6K-SUPK9-7.6.2
7.6(2) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-2.bin
SC6K-SUPCVK9-7.6.2
7.6(1) Flash image
cat6000-supk8.7-6-1.bin
SC6K-SUPK8-7.6.1
7.6(1) Flash image (CiscoView)
cat6000-supcvk8.7-6-1.bin
SC6K-SUPCVK8-7.6.1
7.6(1) Flash image (Secure Shell)
cat6000-supk9.7-6-1.bin
SC6K-SUPK9-7.6.1
7.6(1) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-6-1.bin
SC6K-SUPCVK9-7.6.1
7.5(1) Flash image
cat6000-supk8.7-5-1.bin
SC6K-SUPK8-7.5.1
7.5(1) Flash image (CiscoView)
cat6000-supcvk8.7-5-1.bin
SC6K-SUPCVK8-7.5.1
7.5(1) Flash image (Secure Shell)
cat6000-supk9.7-5-1.bin
SC6K-SUPK9-7.5.1
7.5(1) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-5-1.bin
SC6K-SUPCVK9-7.5.1
7.4(3) Flash image
cat6000-supk8.7-4-3.bin
SC6K-SUPK8-7.4.3
7.4(3) Flash image (CiscoView)
cat6000-supcvk8.7-4-3.bin
SC6K-SUPCVK8-7.4.3
7.4(3) Flash image (Secure Shell)
cat6000-supk9.7-4-3.bin
SC6K-SUPK9-7.4.3
7.4(3) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-4-3.bin
SC6K-SUPCVK9-7.4.3
7.4(2) Flash image
cat6000-supk8.7-4-2.bin
SC6K-SUPK8-7.4.2
7.4(2) Flash image (CiscoView)
cat6000-supcvk8.7-4-2.bin
SC6K-SUPCVK8-7.4.2
7.4(2) Flash image (Secure Shell)
cat6000-supk9.7-4-2.bin
SC6K-SUPK9-7.4.2
7.4(2) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-4-2.bin
SC6K-SUPCVK9-7.4.2
7.3(2) Flash image
cat6000-supk8.7-3-2.bin
SC6K-SUPK8-7.3.2
7.3(2) Flash image (CiscoView)
cat6000-supcvk8.7-3-2.bin
SC6K-SUPCVK8-7.3.2
7.3(2) Flash image (Secure Shell)
cat6000-supk9.7-3-2.bin
SC6K-SUPK9-7.3.2
7.3(2) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-3-2.bin
SC6K-SUPCVK9-7.3.2
7.3(1) Flash image
cat6000-supk8.7-3-1.bin
SC6K-SUPK8-7.3.1
7.3(1) Flash image (CiscoView)
cat6000-supcvk8.7-3-1.bin
SC6K-SUPCVK8-7.3.1
7.3(1) Flash image (Secure Shell)
cat6000-supk9.7-3-1.bin
SC6K-SUPK9-7.3.1
7.3(1) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-3-1.bin
SC6K-SUPCVK9-7.3.1
7.2(2) Flash image
cat6000-supk8.7-2-2.bin
SC6K-SUPK8-7.2.2
7.2(2) Flash image (CiscoView)
cat6000-supcvk8.7-2-2.bin
SC6K-SUPCVK8-7.2.2
7.2(2) Flash image (Secure Shell)
cat6000-supk9.7-2-2.bin
SC6K-SUPK9-7.2.2
7.2(2) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-2-2.bin
SC6K-SUPCVK9-7.2.2
7.1(2) Flash image
cat6000-supk8.7-1-2.bin
SC6K-SUPK8-7.1.2
7.1(2) Flash image (CiscoView)
cat6000-supcvk8.7-1-2.bin
SC6K-SUPCVK8-7.1.2
7.1(2) Flash image (Secure Shell)
cat6000-supk9.7-1-2.bin
SC6K-SUPK9-7.1.2
7.1(2) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-1-2.bin
SC6K-SUPCVK9-7.1.2
7.1(1a) Flash image
cat6000-supk8.7-1-1a.bin
SC6K-SUPK8-7.1.1a
7.1(1a) Flash image (CiscoView)
cat6000-supcvk8.7-1-1a.bin
SC6K-SUPCVK8-7.1.1a
7.1(1a) Flash image (Secure Shell)
cat6000-supk9.7-1-1a.bin
SC6K-SUPK9-7.1.1a
7.1(1) Flash image
cat6000-supk8.7-1-1.bin
SC6K-SUPK8-7.1.1
7.1(1) Flash image (CiscoView)
cat6000-supcvk8.7-1-1.bin
SC6K-SUPCVK8-7.1.1
7.1(1) Flash image (Secure Shell)
cat6000-supk9.7-1-1.bin
SC6K-SUPK9-7.1.1
7.1(1) Flash image (Secure Shell and CiscoView)
cat6000-supcvk9.7-1-1.bin
SC6K-SUPCVK9-7.1.1
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:
•
–
–
–
–
–
–
•
–
–
–
Images that are compatible with all modules except Gigabit Ethernet switching modules are as follows:
•
–
–
–
Images that are compatible with Gigabit Ethernet switching modules but not compatible with 10/100BASE-T modules are as follows:
•
–
Images that are compatible with all modules except the SFM/SFM2 and fabric-enabled modules are as follows:
•
–
–
Note
Catalyst 6500 Series Features
Note
These sections describe the Catalyst 6500 series features:
•
•
•
•
•
•
•
•
•
•
Features for Supervisor Engine Software Release 7.6
These sections describe the features in software release 7.6, 17 April 2003:
•
•
Note
Software Release 7.6 Hardware Features
Software release 7.6 provides initial support for these modules and chassis:
•
The Content Services Gateway (CSG) provides the capability to examine the mobile wireless and wireline IP datastream beyond the IP and TCP/UDP headers to enable billing that is based on the content being provided to the end user.
•
•
The WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6148-GE-TX, and WS-X6148V-GE-TX modules do not support the following:
–
–
–
–
–
–
–
•
Software Release 7.6 Software Features
Software release 7.6 provides support for these software features:
•
•
•
•
•
Note
•
•
•
•
–
–
–
–
Features for Supervisor Engine Software Release 7.5
These sections describe the features in software release 7.5, 27 December 2002:
•
•
Note
Software Release 7.5 Hardware Features
Software release 7.5 provides initial support for these modules and chassis:
•
Connections between the inside, outside, and DMZ networks are controlled by the Firewall Services Module through the firewall using a network-modeled protection scheme that is based upon a configuration and security policy. By implementing a security policy, you can ensure that all traffic from the protected networks only passes through the firewall to the unprotected network. You also can control who accesses the networks and with which services. Features on the module allow you to control how your security policy is used.
•
The SSL Services Module is a Layer 4-through-Layer 7 service module. The module terminates secure sockets layer (SSL) transactions and accelerates the encryption and decryption of data used in SSL sessions.
The module operates either in a standalone configuration or with the Content Switching Module (CSM). In a standalone configuration, secure traffic is directed to the module using policy-based routing (PBR). When used with the CSM, only encrypted client traffic is forwarded to the module, while clear text traffic is forwarded to the real servers.
•
The CSM provides high-performance server load balancing (SLB) among groups of servers, firewalls, caches, VPN termination devices, and other network devices, based on Layer 3 as well as Layer 4 through Layer 7 packet information. Server farms are groups of load-balanced devices.
•
The IDSM2 is an integrated services module that detects unauthorized activity traversing the network by analyzing traffic in real-time, helping enable you to quickly respond to security breaches.
•
Fabric-enabled with 1-MB per-port packet buffers.
Software Release 7.5 Software Features
Software release 7.5 provides support for these software features:
•
–
802.1X authentication is compatible with the port security feature. If you enable port security for only one MAC address on a specific port, only that MAC address will authenticate through a RADIUS server. Users connected through all other MAC addresses are denied access. If you enable port security for multiple MAC addresses, each address needs to authenticate through the 802.1X RADIUS server.
–
The guest VLAN feature allows non-802.1X capable hosts to be able to access networks that use 802.1X authentication.
–
You can enable 802.1X on a Multiple VLAN Access Port (MVAP), and you can enable an auxiliary VLAN ID on an 802.1X port.
•
Automatic QoS consists of a macro that simplifies QoS configuration on the Catalyst 6500 series switches. The automatic QoS macro covers all the QoS configuration tasks that are required for implementing the recommended Architecture for Voice, Video, and Integrated Data (AVVID) settings for a voice port.
•
Automatic voice configuration consists of two macros that simplify voice configuration on the Catalyst 6500 series switches. The automatic voice configuration macros cover all the voice configuration tasks that are required for implementing the recommended AVVID settings for a voice port.
•
–
–
The switch synchronizes runtime 802.1X and port security information between the active and standby supervisor engines.
•
The ARP inspection feature allows you to configure a set of order-dependent rules within the security ACL (VACL) framework to prevent ARP table attacks.
•
The dot1q-all-tagged feature command prior to software release 7.5(1) was a global command. It configured a switch to forward all frames from 802.1Q trunks with 802.1Q tagging, including traffic in the native VLAN (default VLAN), and admit only 802.1Q tagged frames on 802.1Q trunks, dropping any untagged traffic, including untagged traffic in the native VLAN.
In software releases 7.5(1) and later, the dot1q-all-tagged feature can be enabled or disabled on a per-port basis.
•
IGMP version 3 snooping uses source-based filtering and is the industry-designated standard protocol for hosts to signal channel subscriptions in Source Specific Multicast (SSM). Source-based filtering enables hosts and routers to specify which source addresses should be allowed or blocked for a specific multicast group.
Note
•
Local user authentication uses local user accounts and passwords that you create to validate the login attempts of local users rather than requiring a network authentication protocol such as RADIUS or TACACS+.
•
NBAR is a classification engine that recognizes a wide variety of applications, including web-based and other difficult-to-classify protocols that utilize dynamic TCP/UDP port assignments. When an application is recognized and classified by NBAR, a network can invoke services for that specific application. NBAR ensures that network bandwidth is used efficiently by classifying packets and then applying QoS to the classified traffic.
For NBAR configuration information, refer to this URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/dtnbarad.htm#
•
This feature enables background polling of the hardware CAM table so that the software can recognize when new MAC addresses are learned by the switch and generate an SNMP trap. To prevent overloading the network with traps, multiple addresses that are learned during one polling interval generate only one trap (see the set cam notification command description in the Catalyst 6500 Series Switch Command Reference publication).
•
This feature allows you to enable notification when a MAC address change occurs to the CAM table, enable notification when the CAM table utilization exceeds a predefined threshold, and also allows you to set the time between notifications (see the set cam notification command description in the Catalyst 6500 Series Switch Command Reference publication).
•
The enhancements added to the PBF feature simplify the process of setting and committing the security ACLs and adjacency information.
•
You can enable unicast flood blocking on any Ethernet port on a per-port basis. Unicast flood blocking provides you the option to drop unicast flood packets on an Ethernet port that has only one host connected to the port. All Ethernet ports on a switch are configured to allow unicast flooding; unicast flood blocking allows you to drop the unicast flood packets before they reach the port.
•
Rapid PVST+ is the same as PVST+, although rapid PVST+ utilizes a rapid STP that is based on IEEE 802.1w instead of 802.1D. Rapid PVST+ uses the same configuration as PVST+ and you only need minimal extra configuration.
•
The rate-limiting feature for Cisco IOS ACL logging limits the number of packets that are sent to the MSFC CPU for bridged ACEs. An ACE is bridged when the result for the Cisco IOS ACL is a deny or permit with the log option specified. The bridge action can result in Cisco IOS ACL logging overloading the MSFC CPU. When you configure rate limiting for Cisco IOS ACL logging, the bridged ACEs are redirected to the MSFC with rate limiting.
•
–
–
•
The framed-ip-address is now sent in the RADIUS authentication access-request packet.
•
The NVRAM monitoring feature is a background process that allows the system to recover when data in NVRAM is corrupted.
•
You can configure the maximum number of QoS ACLs that the hardware supports. The new limit allows 512 IP QoS ACLs, 512 IPX QoS ACLs, and 512 MAC QoS ACLs on up to 512 different interfaces. Previous to this software release, only 512 QoS ACLs in combination (IP, IPX, and MAC) were supported on 512 different interfaces.
•
•
Prior to software release 7.5(1), Supervisor Engine 1 and Supervisor Engine 2 supported the following Flash PC cards:
–
–
With software releases 7.5(1) and later, additional Flash PC card support is added as follows:
–
–
•
On switches with Catalyst software installed on the Supervisor Engine 2 and Cisco IOS software installed on the MSFC2, the supervisor engine will accept 512-MB DRAM, but works only up to 256 MB. This situation allows you to upgrade your DRAM to 512 MB in the event you change your operating system to Cisco IOS software on both the Supervisor Engine 2 and the MSFC2. In software releases prior to release 7.5(1), with 512-MB DRAM installed on a Supervisor Engine 2 running Catalyst software on the supervisor engine and Cisco IOS software on the MSFC, boot messages and the show version command only showed 256 MB. This problem is resolved in software release 7.5(1). (CSCdw84513)
•
A configurable inband sc1 IP management interface is added. If you configure two inband interfaces, sc0 and sc1, the switch is directly accessible from two different VLANs at the same time.
•
•
•
–
–
–
–
–
•
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Features for Supervisor Engine Software Release 7.4
These sections describe the features in software release 7.4, 27 September 2002:
•
•
Note
Software Release 7.4 Hardware Features
Software release 7.4 provides initial support for these modules and chassis:
•
Note
Software Release 7.4 Software Features
Software release 7.4 does not provide any new software features.
Features for Supervisor Engine Software Release 7.3
These sections describe the features in software release 7.3:
•
•
Note
Software Release 7.3 Hardware Features
Software release 7.3 provides initial support for these modules and chassis:
•
•
Software Release 7.3 Software Features
Software release 7.3 does not provide any new software features. Software release 7.3 does provide the following software enhancement:
•
•
•
•
Features for Supervisor Engine Software Release 7.2
These sections describe the features in software release 7.2:
•
•
Note
Software Release 7.2 Hardware Features
Software release 7.2 provides initial support for these modules and chassis:
•
•
•
•
–
–
–
–
–
–
–
–
•
Note
Software Release 7.2 Software Features
Software release 7.2 provides support for these software features:
•
You can set the authentication login lockout (delay) time to a maximum of 43200 seconds (in previous releases, the maximum was 600 seconds).
•
You can set bridged flow statistics reporting per VLAN. Bridged flows are exported through NetFlow Data Export (NDE) when you enable bridged flow statistics.
•
When broadcast, multicast, or unicast suppression occurs, you can configure ports to either drop packets or go into the errdisable state.
•
Provides more flexibility for traffic flows and their rate limits.
•
Before supervisor engine software release 7.2(2), if a port went into errdisable state, it was reenabled automatically after a selected time interval. With software releases 7.2(2) and later, the timeout enhancement allows you to manually prevent a port from being enabled by setting the errdisable timeout for that port to disabled.
•
You can use this feature to prevent security problems if users disconnect their PCs from networked Cisco IP Phones and plug them directly into the switch port to take advantage of the QoS trust-cos switch port settings.
•
Before supervisor engine software release 7.2(2), IP-directed broadcast traffic was handled by enabling IP directed broadcasts using the ip directed-broadcast command on the MSFC which handled the traffic at the process level causing high CPU utilization.
With software releases 7.2(2) and later, you can configure the MSFC2 to handle the IP-directed broadcasts in hardware using the PFC2. This example shows how to enable IP-directed broadcasts:
Router(config-if)# mls ip directed-broadcast ?exclude-router exclude router from recipient list for directed broadcastinclude-router include router in recipient list for directed broadcastThe exclude-router option forwards the IP-directed broadcast packet in hardware to all hosts in the VLAN except the router.
The include-router option forwards the IP-directed broadcast packet in hardware to all hosts in the VLAN including the router. With this option, the router does not forward the IP-directed broadcast packet again.
Note
•
Jumbo frames are passed through the sc0 interface as a nonconfigurable default; no CLI configuration is necessary.
•
Layer 2 protocol tunneling allows protocol data units (PDUs) (CDP, STP, and VTP) to be tunneled through a network.
•
Before supervisor engine software release 7.2(2), when using the set ip default next-hop ipaddr MSFC2 command (as part of the route-map for PBR), the router packets getting forwarded were software switched by the MSFC2. With supervisor engine software releases 7.2(2) and later, packets that need to be forwarded as a result of the set ip default next-hop ipaddr command, are hardware switched by the PFC2.
Note
•
Before supervisor engine software release 7.2(2), once the 802.1X client was authenticated, it joined an NVRAM-configured VLAN. With software releases 7.2(2) and later, after authentication, an 802.1X client can receive its VLAN assignment from the RADIUS server.
•
The SNMP community string for the NAM is synchronized between the supervisor engine and the NAM allowing greater integration of network management functions.
•
–
–
–
–
–
–
–
–
–
–
–
Features for Supervisor Engine Software Release 7.1
These sections describe the features in software release 7.1:
•
•
Note
Software Release 7.1 Hardware Features
Software release 7.1 provides initial support for these modules and chassis:
•
•
•
•
•
Note
Note
Software Release 7.1 Software Features
Software release 7.1 provides support for these software features:
•
The MST feature is an IEEE standard. 802.1s for MST is an amendment to 802.1Q. MST extends the 802.1w Rapid Spanning Tree (RST) algorithm to multiple spanning trees. This extension provides rapid convergence and load balancing in a VLAN environment. The MST protocol is currently in development and the MST feature for this release is based on a draft version of the IEEE standard. The protocol as implemented in this release is backward compatible with 802.1D STP, 802.1w (the Rapid Spanning Tree Protocol [RSTP]), and the Cisco PVST+ architecture.
•
Provides rapid reconvergence of the spanning tree after the failure of any link in a bridged environment.
•
Allows Cisco switches to manage Ethernet channeling with devices that conform to the 802.3ad (LACP) specification. Prior to software release 7.1(1), Port Aggregation Control Protocol (PAgP) was available. PAgP is a Cisco-proprietary protocol that can be run only on Cisco switches and those switches released by licensed vendors.
•
Significantly reduces the number of ACEs after a merge. In addition, with the new algorithm, you can do the following:
–
–
•
Allows you to avoid transmitting BPDUs on a PortFast-enabled port connected to an end system. This feature is on a per-switch basis; after BPDU filtering is enabled, it applies to all PortFast-enabled ports. The PortFast BPDU filter allows access ports to move directly to the forwarding state as soon as end hosts are connected.
•
Enables IGMP snooping within a VLAN where Protocol Independent Multicast (PIM) and IGMP are not configured because the multicast traffic does not need to be routed.
•
In the VTP off mode, switches behave the same as in VTP transparent mode with the exception that VTP advertisements are not forwarded.
•
Allows PortFast to be configured for trunk and channel ports. On linkup, the port immediately transitions into spanning tree forwarding mode, bypassing the listening and learning states, and bypassing the DTP, PAgP, and IEEE 802.3ad protocols. This feature would normally be used for direct connections to routers or servers and is not intended for connection to other switches because spanning tree loops could occur.
•
Displays individual port MAC addresses when you enter the mac-address keyword to the show port command. Before this feature, the only way you could find the port's MAC address was to enter the show module command to display the module's MAC address range and then calculate each port's MAC address.
•
Increases the valid range of the "Port Security Age Time" and "Shutdown Timeout" to 1 through 1440 minutes (previously, the range was 10 through 1440 minutes).
•
Allows you to monitor and troubleshoot the Catalyst 6500 series switches by polling selected error counters on all ports and logging the system error messages.
•
Provides improved convergence times and less disruption of multicast traffic during MSFC2 switchovers when you enable SRM redundancy. The MSFC2 is protected from being overloaded with multicast traffic during the switchover. The switch caches flows from the MSFC2 that went down and uses the cached flows to forward traffic until the newly activated MSFC2 learns the routes. Only a few flows at a time are provided to the MSFC2 to prevent it from being overwhelmed.
Note
Note
Note
•
Provides support for IGMP snooping with private VLANs.
•
Provides support for Layer 2 and Layer 3 hardware switching for multicast traffic in private VLANs when you use a Supervisor Engine 2 only (PFC2/MSFC2). Layer 2 isolation for hosts is provided from traffic sourced by other receivers (hosts) in the same private VLAN, only if the private VLAN is an isolated private VLAN. For community private VLANs, there is no isolation for hosts from traffic sourced within the same community private VLAN. For community private VLANs, Layer 2 isolation for hosts is provided from traffic sourced by other hosts in a different private VLAN.
Note
•
–
–
–
–
–
–
–
–
–
–
–
–
Features for Supervisor Engine Software Release 6.3
These sections describe the features in software release 6.3:
•
•
Note
Software Release 6.3 Hardware Features
There is no new hardware being introduced in software release 6.3.
Note
Software Release 6.3 Software Features
Software release 6.3 provides support for these software features:
•
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 6500 Series Switch Software Configuration Guide, Release 6.3, for detailed configuration procedures.
•
The sc0 management interface can be assigned to a private VLAN.
•
An EtherChannel is preserved even if it contains only one port. In software releases prior to 6.3(1), if you had a 2-port channel and one link was removed, the remaining link was removed and added back to spanning tree. This situation caused a loss of connection on the channel until the link was forwarding again.
•
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.
•
•
–
–
–
•
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.
•
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.
•
Use the CLI to display SNMPv3 counters for various MIBs.
•
A VLAN interface will not transition to the up state until at least one port in the VLAN is forwarding traffic.
•
The SNMPv3 implementation in software releases prior to 6.3(1) supported RFC 2271 through
RFC 2275. RFC 2271 through RFC 2275 were replaced with RFC 2571 through RFC 2576. The SNMPv3 enhancement in 6.3(1) implements RFC 2571 through RFC 2576.•
–
–
–
–
–
–
Features for Supervisor Engine Software Release 6.2
These sections describe the features in software release 6.2:
•
•
Note
Software Release 6.2 Hardware Features
Software release 6.2 provides initial support for these modules:
•
Note
Note
•
•
•
•
•
Note
Software Release 6.2 Software Features
Software release 6.2 provides support for these software features:
•
Allows you to configure the minimum threshold for WRED.
•
Allows queuing on ports that support 1p1q0t/1p3q1t
•
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.
•
Suppresses multicast traffic on Gigabit Ethernet ports to prevent the ports from being disrupted by a broadcast storm.
•
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.
•
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.
•
Lets you create a policy that denies access in or out of a network.
•
Provides the input and output packet rate and input and output byte rate on a per-port basis.
•
The system performs a TCAM test during bootup.
•
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:
–
–
•
BPDU packet filtering turns off BPDU transmission on PortFast-enabled ports and nontrunking ports.
•
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 allows you to troubleshoot slow network convergence caused by skewing.
•
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 records the last 100 commands that the user entered into the system.
•
Allows you to disable Autostate. Autostate 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.
•
Enhanced redundancy provides more efficient system fault detection and recovery mechanisms.
•
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.
•
–
–
–
–
–
Features for Supervisor Engine Software Release 6.1
These sections describe the features in software release 6.1:
•
•
Note
Software Release 6.1 Hardware Features
Software release 6.1(2) provides initial support for these modules:
•
•
Software release 6.1 provides initial support for these modules:
•
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–
–
•
WS-C6500-SFM
Supports fabric-enabled modules.
Note
•
WS-X6516-GBIC•
WS-X6381-IDS
Note
Software Release 6.1 Software Features
Software release 6.1 provides support for these software features:
•
•
Note
•
•
•
•
•
•
Note
•
•
•
•
–
–
–
–
–
•
•
•
•
•
•
•
•
•
•
•
Features for Supervisor Engine Software Releases 5.1 Through 5.5
For a complete list of hardware and software features for software releases 5.1 through 5.5, refer to the Release Notes for Catalyst 6500 Series Switch Software Release 6.x at
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/relnotes/78_11235.htmUsage Guidelines and Restrictions
These sections provide usage guidelines and restrictions for the Catalyst 6500 series switches:
•
•
•
•
•
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:
•
Workaround: Enter any command on the switch after reaching the end of summertime to come of out of summertime immediately. (CSCsh77991)
•
Workaround: Save the configuration to Flash memory, and restore the configuration after the move. (CSCdy83320)
•
•
•
–
–
–
–
–
–
–
•
•
•
•
Workaround: Either reset the individual modules reporting this error, or reset the switch. (CSCdv51172)
•
•
•
/en/US/docs/switches/lan/catalyst6500/hardware/Config_Notes/78_12667.html#xtocid41960
•
release 6.2(2) and later releases is 6.1(3).•
Workaround: Avoid SAP to non-SAP and vice versa encapsulation changes when doing IPX Layer 3 switching.
•
•
•
•
•
•
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)
•
Workaround: Enable the fast UDP aging only when it is really needed (for example, when load balancing UDP). (CSCdp79475)
•
•
Note
•
Workaround: Set the diagnostic mode to minimal or complete. (CSCdw09563)
•
Modules and Switch Ports
This section contains usage guidelines, restrictions, and troubleshooting information that apply to modules and switch ports:
•
•
•
–
–
–
–
–
(CSCdr56784)
•
•
Workaround: Manually configure the T1 voice module after each switch reset. This problem only applies if the switch is in text config mode. (CSCdv04864)
•
•
Workaround: Power cycle the module (set module power up/down mod_num). (CSCdw04861)
•
Workaround: Disconnect and then reconnect the cable between the switch port and the phone. (CSCdr37056)
•
Workaround: Reset the module to bring it online. (CSCdu77125)
•
•
•
Cisco IOS Release 12.1(8a)E or later on both the Supervisor Engine 2 and the MSFC2. For more information, refer to the Release Notes for 12.1(8a)E on Cisco.com:http://www.cisco.com/univercd/cc/td/doc/product/lan/cat6000/12_1e/ol_2310.htm
•
•
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.
•
•
You can identify WS-X6224-100FX-MT hardware versions using one of the following two methods:
–
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.
–
•
•
•
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)•
Workaround: Remove at least two of the 1000BASE-TX GBICs before removing the module. (CSCdw25775)
•
Workaround: Remove at least two of the 1000BASE-TX GBICs before removing the module above the WS-X6516-GBIC module. (CSCdx19538)
EtherChannel
This section contains usage guidelines, restrictions, and troubleshooting information that apply to EtherChannel:
•
•
Note
–
–
–
Note
•
Quality of Service
This section contains usage guidelines, restrictions, and troubleshooting information that apply to QoS:
•
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 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 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)
•
–
–
•
•
•
•
•
Workaround: Manually modify the security ACL with the new redirect port information. (CSCdp74757)
•
•
•
•
Workaround: Either configure a COPS role on all ports in the switch or configure all ports without a COPS role to use local policy. (CSCdp44965)
•
•
•
Workaround: Unmap the local ACLs before installing the COPS policy. (CSCdp63138)
•
•
•
•
•
•
Automatic Quality of Service with Cisco IP Phones
This section contains usage guidelines, restrictions, and troubleshooting information that apply to configuring automatic QoS with Cisco IP Phones:
•
Workaround: Use custom QoS ACLs instead of automatic QoS on the switch. For this problem, caveat CSCdy62735 has been logged against the Cisco IP phone.
•
Workaround: Use custom QoS ACLs instead of automatic QoS on the switch.
•
Workaround: Use custom QoS ACLs instead of automatic QoS on the switch. For this problem, caveat CSCdy60186 has been logged against Cisco SoftPhone.
•
•
Multicast
This section contains usage guidelines, restrictions, and troubleshooting information that apply to multicast protocols and traffic on the switch:
•
•
•
•
Caveat CSCdx51216 was opened to address the issue of preventing IGMP version 3 reports from flooding in VLANs. IGMP version 3 reports are supported with both PFC2 and PFC3A and that support is described as follows:
–
–
•
•
•
Workaround: Disable IGMP snooping on the switch. (CSCdu72041)
•
•
•
–
–
–
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.
Workaround: 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.
•
•
Workaround: Increase the rate limit value using the set igmp ratelimit pimv2 command. (CSCea44331)
•
•
•
•
•
•
•
•
–
–
Spanning Tree
This section contains usage guidelines, restrictions, and troubleshooting information that apply to Spanning Tree:
•
•
•
Workaround: Reset the switch. (CSCds20952)
•
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
Access Control
This section contains usage guidelines, restrictions, and troubleshooting information that apply to security:
•
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 DAF115112. permit any DAF11511 DAF004023. permit any DAF01023 DAF010234. permit any DAF11511 05. permit any 0 06. permit any DAF11511 DAF11511The VACL description is as follows:
–
–
–
–
–
As the example shows, just 1 and 2 is not enough; you also have to define 3 through 6 to achieve the goal. (CSCdm55828)
•
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:
•
•
•
•
•
•
Workaround: Make the active supervisor engine the standby supervisor engine first, and then remove it from the chassis. (CSCdp76806)
•
Multilayer Switching
This section contains usage guidelines, restrictions, and troubleshooting information that apply to MLS:
•
•
MIBs
This section contains usage guidelines, restrictions, and troubleshooting information that apply to SNMP MIBs, RMON groups, and traps:
Note
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml•
VLANs, VTP, and VLAN Trunks
This section contains usage guidelines, restrictions, and troubleshooting information that apply to VTP, VLANs, and VLAN trunks:
•
•
The Cat6k-A configuration is as follows:
–
–
–
–
–
The Cat6k-B configuration is as follows:
–
–
–
–
–
–
In this configuration, assume that Server 1 is interacting with the router and there is no traffic between Server 2 and the router. If Server 2 suddenly starts interacting with the router, the traffic between Server 1 and the router might stop. This happens when the Cat6k-A 3/1 port is on the WS-X6101-OC12-MMF ATM module.
In summary, do not have a configuration with a promiscuous port on switch A and secondary ports on switch B connected through an ATM trunk on the WS-X6101-OC12-MMF module. (CSCdy03515)
•
•
Workaround: 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 apply to authentication, authorization, and accounting (AAA):
•
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)
SPAN and RSPAN
This section contains usage guidelines, restrictions, and troubleshooting information that apply to Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN):
•
•
TDR
This section contains usage guidelines, restrictions, and troubleshooting information that applies to the time domain reflectometer (TDR) feature:
•
•
•
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. Auto-MDI/MDIX works with the speed set to auto/1000 Mbps, but not with the speed set to 10 Mbps or 100 Mbps. 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 10 Mbps or 100 Mbps 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:
•
Auto-MDI/MDIX works in 10-, 100-, and 1000-Mbps modes with autonegotiated and fixed speeds.
•
Auto-MDI/MDIX works with the speed set to auto/1000 Mbps, but not with the speed set to 10 Mbps or 100 Mbps.
•
With software release 8.2(1), auto-MDIX is also enabled on the following modules:
•
Auto-MDI/MDIX works with the speed set to auto/1000, but not with the speed set to 10 Mbps or 100 Mbps.
•
Auto-MDI/MDIX works with the speed set to auto, but not with the speed set to 10 Mbps or 100 Mbps.
Note
Binary and Text File Configuration Modes
The main purpose of storing configuration information in NVRAM blocks is to restore the system configuration when the switch boots up after a reset. The supervisor engine boot process includes reading the NVRAM blocks and using the configuration information in the blocks to configure the system. Before restoring the configuration from an NVRAM block, a new checksum is generated on the data in the block, and the new checksum is compared with the checksum stored in the block itself. If both of the checksums match, the data is determined to be valid and the data in the block is used to restore the configuration. If the checksum matching fails, the NVRAM block is deallocated, and the default configuration is used.
There are two modes for storing the configuration file, binary configuration mode and text file configuration mode. These modes are described in the following sections.
Binary Configuration Mode
In binary configuration mode, the NVRAM configuration model uses binary data structures to save information. The NVRAM is allocated in blocks, and each data structure is stored as an NVRAM block as follows:
•
•
•
When you enter a command to configure a feature, the information is stored immediately in one of the NVRAM blocks. Some blocks are allocated at startup, such as the global block, the SNMP block, and the VTP block. Other blocks are allocated as needed. For example, a module block is allocated only when a nondefault setting is configured for the module or configured for a port on the module. Some NVRAM blocks also grow dynamically. The VTP block, by default, allows for 256 VLANs to be configured. If more than 256 VLANs are configured, the VTP block expands to allow 256 additional VLANs. Binary configuration mode provides an easy way to store the configuration immediately without the need for a write memory command to commit the configuration to NVRAM.
Binary storage of data is also space efficient. For example, remembering if a feature is enabled or not requires a single bit of NVRAM.
Text File Configuration Mode
A disadvantage of the binary configuration mode is that although configured features can be stored efficiently, a large amount of NVRAM space can be wasted by features that are not configured by the user. For example, the global block currently requires approximately 150 KB, but users may have configured only a few features. Similarly, a 48-port module consumes approximately 25 KB of NVRAM space (about 0.5 KB per port) even if only a single port on the module has been configured with a nondefault setting.
With software release 6.3(1) and later releases, the text file configuration mode was introduced to support the new 13-slot chassis and all the configurable options on the switch. With text file configuration mode, you can store the configuration as a text file in Flash memory or NVRAM. In text file configuration mode, the binary NVRAM data structures are deleted from NVRAM. The only blocks not deleted from NVRAM are those that contain information not stored in the configuration file. These blocks include the following:
•
•
•
•
•
•
•
•
•
The NVRAM blocks are copied to DRAM before being deleted. Except for some isolated code associated with the copying of the NVRAM blocks into DRAM, this change is transparent to the rest of the software. The data structures are manipulated and accessed as before; the only difference is that they are now stored in the DRAM instead of the NVRAM memory region.
A new B_GENERAL NVRAM block is also created when operating in text configuration mode. This block contains any configuration from a deleted block that must still be saved in NVRAM. For example, there are time zone and encryption-related fields in the global block that must be stored in NVRAM. These fields are moved to the new B_GENERAL block whenever text configuration mode is selected. The B_GENERAL block is deleted when moving back to binary configuration mode.
When operating in text file configuration mode, most user settings are no longer saved immediately to NVRAM. Instead, configuration changes are written to the DRAM only. You must enter the write memory command to store the configuration in non-volatile storage. The non-volatile storage may be either the Flash file system or NVRAM. Because the text file configuration file in most cases requires less space than the binary data structures, NVRAM is an appropriate place for the configuration file. Alternatively, you may specify a file in the Flash file system.
Note
CiscoView
This section contains usage guidelines, restrictions, and troubleshooting information that apply to CiscoView:
•
•
Note
Note
Note
•
On Windows NT machines with Java Plug-in 1.3.0 installed and Netscape running, the CiscoView chassis scrollbar does not appear, even after resizing it. To correct the problem, upgrade to Java Plug-in 1.3.1. (CSCdw58407)
•
To correct the problem, perform these steps:
Step 1
Step 2
http://www.cisco.com/pcgi-bin/tablebuild.pl/cview-plugin
Step 3
Step 4
Step 5
Step 6
Step 7
Step 8
Step 9
Step 10
Step 11
•
To correct the problem, download Java Plug-in 1.3.0 or later from the following location: http://www.cisco.com/pcgi-bin/tablebuild.pl/cview-plugin
•
–
1) Select Start > Settings > Control Panel > Java Plug-in 1.3.1.
2) Click the Cache tab.
3) Click Clear JAR Cache.
–
1) Select Start > Settings > Control Panel > Java Plug-in.
2) Click the Basic tab.
3) Make sure the "Cache JARs In Memory" checkbox is not selected.
4) Click Apply.
•
http://www.hp.com/workstations/products/unix/software/netscape/index.html
(CSCdw59617)•
•
Workaround: Close and reopen the dialog box and then delete the primary VLAN.
After binding a secondary VLAN to the primary VLAN, delete the primary VLAN and the following error message is displayed: "Set failed due to snmpRspGenErr for vtpVlanEditRowStatus.1.199."
Workaround: Close and then reopen the dialog box. You should now see the correct error message: "The Primary is bounded ..." (CSCdt65530)
•
•
•
•
•
Unable to set row status(CSCdu11333)
•
Workaround: Overwrite the values in the fields if necessary. (CSCdu05678 and CSCdu15066)
•
Workaround: 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)
•
Workaround: Delete the policy selection entry that was added. (CSCdu43690)
•
•
•
•
•
•
•
•
Workaround: Because the problem is intermittent, the workaround is to close the dialog and try launching the application again. (CSCin41067)
•
–
–
–
–
–
–
–
–
–
–
You might see the problem with Windows NT, Windows 2000, and Solaris platforms. The problem is not seen with other features.
Workaround: Because the problem is intermittent, the workaround is to close the dialog and try launching the application again. (CSCin42718)
•
–
–
FWM Card->Firewall Service Blade Setup Wizard
FWM Card->Assign VLANs To Firewall Blade
FWM Card->Configure Firewall Interface(s)
FWM Card->Configure Static Route
FWM Card->Configure HTTP Service on Firewall Interface(s)
FWM Card->Configure HTTP Server
CSM Card->CSM Details
After the progress dialog displays, press the Cancel button. This action displays the following message: "Failed to retrieve category: Assign VLANs to Firewall Blade.java.lang.NullPointerException:."
This problem is intermittent and the cancel operation is successful for VLAN flows dialogs.
Workaround: The workaround for problem 1 is to close the exception and try to launch the dialog again.
–
–
Workaround: The workaround for problem 2 is to close the session and try to launch the dialog again. Instead of using the close (X) button, press the Cancel button to close the dialog. (CSCin43633)
•
Open and Resolved Caveats in Software Release 7.6(24)
These sections describe open and resolved caveats in supervisor engine software release 7.6(24).
•
•
Open Caveats in Software Release 7.6(24)
There are no open caveats in software release 7.6.(24).
Resolved Caveats in Software Release 7.6(24)
•
Workaround: Disabling the spanning tree loop guard will prevent the VLAN from going into a loop-inconsistent state. When both bridges' spanning tree protocol are set to Rapid-PVST+, the loop guard can be enabled again.
This problem is resolved in software release 7.6(24). (CSCsl34983)
•
Workaround: Configure PAgP and LACP to on mode.
This problem is resolved in software release 7.6(24). (CSCsh33078)
Open and Resolved Caveats in Software Release 7.6(23)
These sections describe open and resolved caveats in supervisor engine software release 7.6(23).
•
•
Open Caveats in Software Release 7.6(23)
There are no open caveats in software release 7.6.(23)
Resolved Caveats in Software Release 7.6(23)
•
Workaround: Configure FPOE in engineering mode manually and then switchover.
This problem is resolved in software release 7.6(23).(CSCsk34156)
•
Workaround: Disable bpdu-guard and bpdu-filter spanning tree features for MSFC ports.
This problem is resolved in software release 7.6(23).(CSCsk15951)
•
Workaround: None.
This problem is resolved in software release 8.6(1). (CSCse44785)
•
Workaround: Disable the newRoot trap.
This problem is resolved in software release 8.6(3). (CSCsi40326)
Open and Resolved Caveats in Software Release 7.6(22)
These sections describe open and resolved caveats in supervisor engine software release 7.6(21):
•
•
Open Caveats in Software Release 7.6(22)
There are no open caveats in supervisor engine software release 7.6(19).
Resolved Caveats in Software Release 7.6(22)
•
Workaround: None
This problem is resolved in software release 7.6(22). (CSCsi86485)
•
Workaround: None.
This problem is resolved in software release 7.6(22). (CSCsi89867)
•
This problem is resolved in software release 7.6(22). (CSCsi92247)
•
Forwarding loops are introduced across the channel links, and eventually are errdisabled due to channel misconfiguration.
Workaround: Use the native VLAN as 1 or set the trunk mode to on.
This problem is resolved in software release 7.6(22). (CSCsj26890)
Open and Resolved Caveats in Software Release 7.6(21)
These sections describe open and resolved caveats in supervisor engine software release 7.6(21):
•
•
Open Caveats in Software Release 7.6(21)
This section describes open caveats in supervisor engine software release 7.6(21):
•
Workaround: None. (CSCsi86485)
•
Workaround: None. (CSCsi89867)
•
Workaround: To configure more than one PVLAN, you must configure them one at a time. (CSCsi92247)
Resolved Caveats in Software Release 7.6(21)
This section describes resolved caveats in supervisor engine software release 7.6(21):
•
–
–
CatOS 7.1(1) and 7.6(3) or later experiences the same behavior.
Workaround: None.
This problem is resolved in software release 8.6(1). (CSCed52709)
•
This problem is resolved in software release 7.6(21). (CSCin51922)
•
Workaround: Set editing disable.
This problem is resolved in software release 7.6(21). (CSCse29446)
•
Workaround: None.
This problem is resolved in software release 7.6(21). (CSCsh86516)
•
This problem is resolved in software release 7.6(21). (CSCsi00968)
Open and Resolved Caveats in Software Release 7.6(20)
These sections describe open and resolved caveats in supervisor engine software release 7.6(18):
•
•
Open Caveats in Software Release 7.6(20)
There are no open caveats in supervisor engine software release 7.6(20).
Resolved Caveats in Software Release 7.6(20)
This section describes resolved caveats in supervisor engine software release 7.6(20):
•
Workaround: To set diaglebel to bypass mode using command set test diaglevel bypass.
This problem is resolved in software release 7.6(20).(CSCsd89614)
•
This problem is resolved in software release 7.6(20). (CSCec42270)
•
Workaround: Enable BPDU guard on the access port.
This problem is resolved in software release 7.6(20). (CSCsd94558)
•
Workaround: Reset the switch to clear the MAC address.
This problem is resolved in software release 7.6(20). (CSCei27809)
•
Workaround: Disable loopguard on the designated side of the link.
This problem is resolved in software release 7.6(20). (CSCsd61118)
•
Workaround: To clear the parser error, perform one of the following tasks:
1.
2.
3.
This problem is resolved in software release 7.6(20). (CSCse47765)
•
Workaround: Reset the switch to clear the MAC address.
This problem is resolved in software release 7.6(20). (CSCei27809)
•
Workaround: Perform one of the following tasks:
–
–
–
This problem is resolved in software release 7.6(20). (CSCse47765)
•
***** Available only on Earl5 supervisors *****.Upon entering a clear counter supervisor command, the supervisor engine will then failover if in a redundant configuration or reload.
Workaround: Do not enter the clear count supervisor command on a supervisor engine without a PFC installed.
This problem is resolved in software release 7.6(20). (CSCsg68051)
•
This problem is resolved in software release 7.6(20). (CSCec42270)
•
Workaround: Disable loopguard on the designated side of the link.
This problem is resolved in software release 7.6(20). (CSCsd61118)
•
Workaround: Enable BPDU guard on the access port.
This problem is resolved in software release 7.6(20). (CSCsd94558)
•
Workaround: None.
This problem is resolved in software release 7.6(20). (CSCse44785)
•
Workaround: To clear the parser error, perform one of the following tasks:
–
–
–
This problem is resolved in software release 7.6(20). (CSCse47765)
•
This problem is resolved in software release 7.6(20). (CSCsg80406)
•
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 PDTSummertime is enabled and set to 'PDT'Start : Sun Mar 11 2007, 02:00:00End : Sun Nov 4 2007, 02:00:00Offset: 60 minutesRecurring: 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 60Summertime is enabled and set to 'PDT'Start : Sun Mar 11 2007, 02:00:00End : Sun Nov 4 2007, 02:00:00Offset: 60 minutesRecurring: yes, starting at 02:00am of second Sunday of March and ending on 0.Console> (enable)
Note
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 7.6(20). (CSCse79110)
•
This problem is resolved in software release 7.6(20). (CSCse79110)
Open and Resolved Caveats in Software Release 7.6(19)
These sections describe open and resolved caveats in supervisor engine software release 7.6(18):
•
•
Open Caveats in Software Release 7.6(19)
There are no open caveats in supervisor engine software release 7.6(19).
Resolved Caveats in Software Release 7.6(19)
This section describes resolved caveats in supervisor engine software release 7.6(19):
•
Workaround: Reset the module to correct this issue. (CSCse81638)•
Workaround: None. (CSCsb91548)•
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)
Open and Resolved Caveats in Software Release 7.6(18)
These sections describe open and resolved caveats in supervisor engine software release 7.6(18):
•
•
Open Caveats in Software Release 7.6(18)
This section describes open caveats in supervisor engine software release 7.6(18):
•
Resolved Caveats in Software Release 7.6(18)
This section describes resolved caveats in supervisor engine software release 7.6(18):
•
Console> (enable) set qos acl map test-qos 3/9Transient error. Port state in transition. Please retry command. Failed to map ACLtest-qos to port 3/9.Console> (enable)Workaround: Use one of the following workarounds:
–
–
–
This problem is resolved in software release 7.6(18). (CSCdz89506)
•
–
–
–
–
–
Workaround: Reset the affected module. This problem is resolved in software release 7.6(18). (CSCeg60285)
•
•
•
•
Workaround 1: Run PVST+ instead of Rapid PVST+.
Workaround 2: Disable high availability using the set system highavailability disable command. This problem is resolved in software release 7.6(18). (CSCsd69668)
•
Last Exception occurred on [date] ...Software version = 6.4(18)Error Msg:PID = 35 cdpdtimerEPC: 806F1670The supervisor engine appears to be operating normally when this problem occurs. This problem is resolved in software release 7.6(18). (CSCsd35254)
•
Open and Resolved Caveats in Software Release 7.6(17)
These sections describe open and resolved caveats in supervisor engine software release 7.6(17):
•
•
Open Caveats in Software Release 7.6(17)
This section describes open caveats in supervisor engine software release 7.6(17):
•
Resolved Caveats in Software Release 7.6(17)
This section describes resolved caveats in supervisor engine software release 7.6(17):
•
Workaround: When one of the ports in the channel goes down, disable and enable all the ports in the channel. This problem is resolved in software release 7.6(17). (CSCsc34494)
•
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 7.6(17). (CSCej37841)
•
•
1) On the active (slot 1) supervisor engine, configure two default routes.
2) On the active (slot 1) supervisor engine, enter the switch supervisor command.
3) On the newly active (slot 2) supervisor engine, enter the clear config all command.
4) On the active (slot 2) supervisor engine, add a route to an external network to ping the network.
4) On the active (slot 2) supervisor engine, enter the switch supervisor command.
5) On the newly active (slot 1) supervisor engine, the default IP route is still there.
Workaround: Manually clear the default IP route on the slot 1 supervisor engine. This problem is resolved in software release 7.6(17). (CSCei04333)
•
Workaround: Disable high availability. This problem is resolved in software release 7.6(17). (CSCsc37456)
•
Workaround: Enable the Layer 3 cache or set the diagnostic level to minimal or bypass instead of complete. This problem is resolved in software release 7.6(17). (CSCsc91179)
•
•
•
%DTP-5-TRUNKPORTON:Port 4/1 has become dot1q trunk %SYS-3-MOD_PORTINTFINSYNC:Port Interface in sync for Module 4 %ETHC-5-PORTTOSTP:Port 4/1 joined bridge port 4/1-6 %DTP-5-TRUNKPORTON:Port 4/2 has become dot1q trunk %DTP-5-TRUNKPORTON:Port 4/3 has become dot1q trunk %DTP-5-TRUNKPORTON:Port 4/4 has become dot1q trunk %DTP-5-TRUNKPORTON:Port 4/5 has become dot1q trunk %ETHC-3-ONMODEFAIL:Port 4/5 errdisabled, ON mode attributes mismatch %DTP-5-TRUNKPORTON:Port 4/6 has become dot1q trunk %ETHC-3-ONMODEFAIL:Port 4/6 errdisabled, ON mode attributes mismatch %ETHC-5-PORTTOSTP:Port 4/2 joined bridge port 4/1-6 %ETHC-5-PORTTOSTP:Port 4/3 joined bridge port 4/1-6 %ETHC-5-PORTTOSTP:Port 4/4 joined bridge port 4/1-6 %DTP-5-NONTRUNKPORTON:Port 4/5 has become non-trunk %DTP-5-NONTRUNKPORTON:Port 4/6 has become non-trunkWorkaround: Manually add/delete the VLANs to the individual ports. This problem is resolved in software release 7.6(17). (CSCsd15946)
•
Open and Resolved Caveats in Software Release 7.6(16)
These sections describe open and resolved caveats in supervisor engine software release 7.6(16):
•
•
Open Caveats in Software Release 7.6(16)
This section describes open caveats in supervisor engine software release 7.6(16):
•
Workaround: When one of the ports in the channel goes down, disable and enable all the ports in the channel. (CSCsc34494)
•
Resolved Caveats in Software Release 7.6(16)
This section describes resolved caveats in supervisor engine software release 7.6(16):
•
–
–
–
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 7.6(16). (CSCed20984)
•
•
•
Open and Resolved Caveats in Software Release 7.6(15)
These sections describe open and resolved caveats in supervisor engine software release 7.6(15):
•
•
Open Caveats in Software Release 7.6(15)
This section describes open caveats in supervisor engine software release 7.6(15):
•
Guest
