Table Of Contents
Release Notes for Catalyst 4000 Family Software Release 6.x
Release 6.x Memory Requirements
Product and Software Version Support Matrix
Release 6.x Orderable Software Images
New Features for Supervisor Engine Software Release 6.4
New Features for Supervisor Engine Software Release 6.3
New Features for Supervisor Engine Software Release 6.2
New Features for Supervisor Engine Software Release 6.1
Open and Resolved Caveats in Software Release 6.4(21)
Open Caveats in Software Release 6.4(21)
Resolved Caveats in Software Release 6.4(21)
Open and Resolved Caveats in Software Release 6.4(20)
Open Caveats in Software Release 6.4(20)
Resolved Caveats in Software Release 6.4(20)
Open and Resolved Caveats in Software Release 6.4(19)
Open Caveats in Software Release 6.4(19)
Resolved Caveats in Software Release 6.4(19)
Open and Resolved Caveats in Software Release 6.4(18)
Open Caveats in Software Release 6.4(18)
Resolved Caveats in Software Release 6.4(18)
Open and Resolved Caveats in Software Release 6.4(17)
Open Caveats in Software Release 6.4(17)
Resolved Caveats in Software Release 6.4(17)
Open and Resolved Caveats in Software Release 6.4(16)
Open Caveats in Software Release 6.4(16)
Resolved Caveats in Software Release 6.4(16)
Open and Resolved Caveats in Software Release 6.4(15)
Open Caveats in Software Release 6.4(15)
Resolved Caveats in Software Release 6.4(15)
Open and Resolved Caveats in Software Release 6.4(14)
Open Caveats in Software Release 6.4(14)
Resolved Caveats in Software Release 6.4(14)
Open and Resolved Caveats in Software Release 6.4(13)
Open Caveats in Software Release 6.4(13)
Resolved Caveats in Software Release 6.4(13)
Open and Resolved Caveats in Software Release 6.4(12)
Open Caveats in Software Release 6.4(12)
Resolved Caveats in Software Release 6.4(12)
Open and Resolved Caveats in Software Release 6.4(11)
Open Caveats in Software Release 6.4(11)
Resolved Caveats in Software Release 6.4(11)
Open and Resolved Caveats in Software Release 6.4(10)
Open Caveats in Software Release 6.4(10)
Resolved Caveats in Software Release 6.4(10)
Open and Resolved Caveats in Software Release 6.4(9)
Open Caveats in Software Release 6.4(9)
Resolved Caveats in Software Release 6.4(9)
Open and Resolved Caveats in Software Release 6.4(8)
Open Caveats in Software Release 6.4(8)
Resolved Caveats in Software Release 6.4(8)
Open and Resolved Caveats in Software Release 6.4(7)
Open Caveats in Software Release 6.4(7)
Resolved Caveats in Software Release 6.4(7)
Open and Resolved Caveats in Software Release 6.4(6)
Open Caveats in Software Release 6.4(6)
Resolved Caveats in Software Release 6.4(6)
Open and Resolved Caveats in Software Release 6.4(5)
Open Caveats in Software Release 6.4(5)
Resolved Caveats in Software Release 6.4(5)
Open and Resolved Caveats in Software Release 6.4(4)
Open Caveats in Software Release 6.4(4)
Resolved Caveats in Software Release 6.4(4)
Open and Resolved Caveats in Software Release 6.4(3)
Open Caveats in Software Release 6.4(3)
Resolved Caveats in Software Release 6.4(3)
Open and Resolved Caveats in Software Release 6.4(2)
Open Caveats in Software Release 6.4(2)
Resolved Caveats in Software Release 6.4(2)
Open and Resolved Caveats in Software Release 6.4(1)
Open Caveats in Software Release 6.4(1)
Resolved Caveats in Software Release 6.4(1)
Open and Resolved Caveats in Software Release 6.3(10)
Open Caveats in Software Release 6.3(10)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(10)
Open and Resolved Caveats in Software Release 6.3(9)
Open Caveats in Software Release 6.3(9)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(9)
Open and Resolved Caveats in Software Release 6.3(8)
Open Caveats in Software Release 6.3(8)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(8)
Open and Resolved Caveats in Software Release 6.3(7)
Open Caveats in Software Release 6.3(7)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(7)
Open and Resolved Caveats in Software Release 6.3(6)
Open Caveats in Software Release 6.3(6)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(6)
Open and Resolved Caveats in Software Release 6.3(5)
Open Caveats in Software Release 6.3(5)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(5)
Open and Resolved Caveats in Software Release 6.3(4a)
Open Caveats in Software Release 6.3(4a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(4a)
Open and Resolved Caveats in Software Release 6.3(4)
Open Caveats in Software Release 6.3(4)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(4)
Open and Resolved Caveats in Software Release 6.3(3a)
Open Caveats in Software Release 6.3(3a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(3a)
Open and Resolved Caveats in Software Release 6.3(3)
Open Caveats in Software Release 6.3(3)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(3)
Open and Resolved Caveats in Software Release 6.3(2a)
Open Caveats in Software Release 6.3(2a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(2a)
Open and Resolved Caveats in Software Release 6.3(2)
Open Caveats in Software Release 6.3(2)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(2)
Open and Resolved Caveats in Software Release 6.3(1a)
Open Caveats in Software Release 6.3(1a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(1a)
Open and Resolved Caveats in Software Release 6.3(1)
Open Caveats in Software Release 6.3(1)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.3(1)
Open and Resolved Caveats in Software Release 6.2(3a)
Open Caveats in Software Release 6.2(3a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.2(3a)
Open and Resolved Caveats in Software Release 6.2(3)
Open Caveats in Software Release 6.2(3)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.2(3)
Open and Resolved Caveats in Software Release 6.2(2a)
Open Caveats in Software Release 6.2(2a)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.2(2a)
Open and Resolved Caveats in Software Release 6.2(2)
Open Caveats in Software Release 6.2(2)
Open Caveats in Nonembedded CiscoView
Resolved Caveats in Software Release 6.2(2)
Resolved Caveats for Nonembedded CiscoView
Open and Resolved Caveats in Software Release 6.2(1a)
Open Caveats in Software Release 6.2(1a)
Resolved Caveats in Software Release 6.2(1a)
Open and Resolved Caveats in Software Release 6.2(1)
Open Caveats in Software Release 6.2(1)
Resolved Caveats in Software Release 6.2(1)
Open and Resolved Caveats in Software Release 6.1(4b)
Open Caveats in Software Release 6.1(4b)
Resolved Caveats in Software Release 6.1(4b)
Open and Resolved Caveats in Software Release 6.1(3a)
Open Caveats in Software Release 6.1(3a)
Resolved Caveats in Software Release 6.1(3a)
Open and Resolved Caveats in Software Release 6.1(3)
Open Caveats in Software Release 6.1(3)
Resolved Caveats in Software Release 6.1(3)
Open and Resolved Caveats in Software Release 6.1(2a)
Open Caveats in Software Release 6.1(2a)
Resolved Caveats in Software Release 6.1(2a)
Open and Resolved Caveats in Software Release 6.1(2)
Open Caveats in Software Release 6.1(2)
Resolved Caveats in Software Release 6.1(2)
Open and Resolved Caveats in Software Release 6.1(1e)
Open Caveats in Software Release 6.1(1e)
Resolved Caveats in Software Release 6.1(1e)
Open and Resolved Caveats in Software Release 6.1(1c)
Open Caveats in Software Release 6.1(1c)
Resolved Caveats in Software Release 6.1(1c)
Open and Resolved Caveats in Software Release 6.1(1)
Open Caveats in Software Release 6.1(1)
Resolved Caveats in Software Release 6.1(1)
Usage Guidelines, Restrictions, and Troubleshooting
Authentication, Authorization, and Accounting
Software Documentation Updates for Release 6.1
Obtaining Technical Assistance
Cisco Technical Support Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Catalyst 4000 Family Software Release 6.x
Current Release:
6.4(21)—February 20, 2005
Previous Releases:
6.4(20), 6.4(19), 6.4(18), 6.4(17), 6.4(16), 6.4(15), 6.4(14), 6.4(13), 6.4(12), 6.4(11), 6.4(10), 6.4(9), 6.4(8), 6.4(7), 6.4(6), 6.4(5), 6.4(4), 6.4(3), 6.4(2), 6.4(1) 6.3(10), 6.3(9), 6.3(8), 6.3(7), 6.3(6), 6.3(5), 6.3(4a), 6.3(4), 6.3(3a), 6.3(3), 6.3(2a), 6.3(2), 6.3(1a), 6.3(1), 6.2(3a), 6.2(3), 6.2(2a), 6.2(2), 6.1(4b), 6.1(3a), 6.1(3), 6.2(1a), 6.2(1), 6.1(2a), 6.1(2), 6.1(1e), 6.1(1c), 6.1(1)These release notes describe the features, modifications, and caveats for Catalyst 4000 series supervisor engine software release 6.x and all 6.x maintenance releases. The most current 6.x release is supervisor engine software release 6.4(21). These release notes apply to Catalyst 4000 series switches as well as to Catalyst 2948G and 2980 switches running Catalyst 4000 series supervisor engine software.
Note
For the latest information on the open caveats, see the most current version of these release notes at the following URL: http://www.cisco.com/en/US/products/hw/switches/ps663/prod_release_note09186a008029aa83.html
CautionWe strongly recommend that you read these release notes before using your switch or upgrading your switch software.
Note
Although the software image in a new Catalyst 4000 family switch operates correctly, later software images containing the latest upgrades and modifications are released regularly to provide you with the most optimized software available. We strongly recommend that you check for the latest released software images at the World Wide Web location listed in the "Cisco.com" section.
Note
Release notes for earlier Catalyst 4000 family software releases were accurate at the time of release. However, for information on the latest caveats and updates to previously released Catalyst 4000 family software releases, refer to the release notes for the latest maintenance release in your software release train. You can access all Catalyst 4000 series release notes at the World Wide Web location listed in the "Cisco.com" section.
CautionAlways back up the switch configuration file before upgrading or downgrading the switch software to avoid losing all or part of the configuration stored in nonvolatile RAM (NVRAM). A software downgrade will always cause the configuration to be lost. Use the copy config tftp command to back up your configuration to a Trivial File Transfer Protocol (TFTP) server. Use the copy config flash command to back up the configuration to a Flash device.
Contents
This document consists of these sections:
•
Product and Software Version Support Matrix
•
Release 6.x Orderable Software Images
•
New Features for Supervisor Engine Software Release 6.4
•
New Features for Supervisor Engine Software Release 6.3
•
New Features for Supervisor Engine Software Release 6.2
•
New Features for Supervisor Engine Software Release 6.1
•
Open and Resolved Caveats in Software Release 6.4(21)
•
Open and Resolved Caveats in Software Release 6.4(20)
•
Open and Resolved Caveats in Software Release 6.4(19)
•
Open and Resolved Caveats in Software Release 6.4(18)
•
Open and Resolved Caveats in Software Release 6.4(17)
•
Open and Resolved Caveats in Software Release 6.4(16)
•
Open and Resolved Caveats in Software Release 6.4(15)
•
Open and Resolved Caveats in Software Release 6.4(14)
•
Open and Resolved Caveats in Software Release 6.4(13)
•
Open and Resolved Caveats in Software Release 6.4(12)
•
Open and Resolved Caveats in Software Release 6.4(11)
•
Open and Resolved Caveats in Software Release 6.4(10)
•
Open and Resolved Caveats in Software Release 6.4(9)
•
Open and Resolved Caveats in Software Release 6.4(8)
•
Open and Resolved Caveats in Software Release 6.4(7)
•
Open and Resolved Caveats in Software Release 6.4(6)
•
Open and Resolved Caveats in Software Release 6.4(5)
•
Open and Resolved Caveats in Software Release 6.4(4)
•
Open and Resolved Caveats in Software Release 6.4(3)
•
Open and Resolved Caveats in Software Release 6.4(2)
•
Open and Resolved Caveats in Software Release 6.4(1)
•
Open and Resolved Caveats in Software Release 6.3(10)
•
Open and Resolved Caveats in Software Release 6.3(9)
•
Open and Resolved Caveats in Software Release 6.3(8)
•
Open and Resolved Caveats in Software Release 6.3(7)
•
Open and Resolved Caveats in Software Release 6.3(6)
•
Open and Resolved Caveats in Software Release 6.3(5)
•
Open and Resolved Caveats in Software Release 6.3(4a)
•
Open and Resolved Caveats in Software Release 6.3(4)
•
Open and Resolved Caveats in Software Release 6.3(3a)
•
Open and Resolved Caveats in Software Release 6.3(3)
•
Open and Resolved Caveats in Software Release 6.3(2a)
•
Open and Resolved Caveats in Software Release 6.3(2)
•
Open and Resolved Caveats in Software Release 6.3(1a)
•
Open and Resolved Caveats in Software Release 6.3(1)
•
Open and Resolved Caveats in Software Release 6.2(3a)
•
Open and Resolved Caveats in Software Release 6.2(3)
•
Open and Resolved Caveats in Software Release 6.2(2a)
•
Open and Resolved Caveats in Software Release 6.2(2)
•
Open and Resolved Caveats in Software Release 6.2(1a)
•
Open and Resolved Caveats in Software Release 6.2(1)
•
Open and Resolved Caveats in Software Release 6.1(4b)
•
Open and Resolved Caveats in Software Release 6.1(3a)
•
Open and Resolved Caveats in Software Release 6.1(3)
•
Open and Resolved Caveats in Software Release 6.1(2a)
•
Open and Resolved Caveats in Software Release 6.1(2)
•
Open and Resolved Caveats in Software Release 6.1(1e)
•
Open and Resolved Caveats in Software Release 6.1(1c)
•
Open and Resolved Caveats in Software Release 6.1(1)
•
Usage Guidelines, Restrictions, and Troubleshooting
•
Software Documentation Updates for Release 6.1
System Requirements
This section describes the system requirements for the Catalyst 4000 family switches and contains the following sections:
•
Release 6.x Memory Requirements
Power Supply Requirements
The Catalyst 4006 switch requires dual power supplies.
Release 6.x Memory Requirements
The Catalyst 4000 series supervisor engine software release 6.x requires a minimum of 64-MB DRAM installed on your supervisor engine.
If your supervisor engine has less than 64-MB DRAM, you can add more memory by ordering the 32-MB DRAM upgrade (Cisco product number MEM-C4K-32-RAM=) for the Catalyst 4000 family Supervisor Engine I.
ROMMON Requirements
If the Boot ROM (ROMMON) loaded onto your switch is version 4.5(1) or earlier, you need to upgrade to a ROMMON version of 5.4(1) or greater in order to run software release 6.3(2) or a later release.
Upgrading the ROMMON
Follow these guidelines to upgrade the ROMMON on your switch:
CautionTo avoid actions that might make your system unbootable, read this entire section before starting the upgrade.
You can do this procedure entirely over a Telnet connection. If something fails, you will need to have access to the console serial port. If done improperly, the system can become unbootable. You will then have to return it to Cisco for repair.
This section describes an upgrade to ROMMON version 6.1(4). The same procedure applies to other ROMMON versions, but you will have to substitute appropriate version numbers in the upgrade image names.
Step 1
Download the promupgrade program from Cisco.com and place it on a TFTP server in a directory that is accessible from the switch to be upgraded.
The promupgrade programs are available at the same location on Cisco.com where you download Catalyst 4000 system images.
To upgrade to ROMMON version 6.1(4), download the cat4000-promupgrade.6-1-4.bin file.
Step 2
In privileged mode on your switch, use the show version command to verify the ROMMON version loaded on the switch.
The ROMMON version number is listed as the System Bootstrap Version. For example, the system is running ROMMON version 6.1(2):
Console> (enable) show versionWS-C4003 Software, Version NmpSW:5.5(8)Copyright (c) 1995-2001 by Cisco Systems, Inc.NMP S/W compiled on May 24 2001, 21:12:09GSP S/W compiled on May 24 2001, 18:39:50System Bootstrap Version:6.1(2)Hardware Version:1.0 Model:WS-C4003 Serial #:xxxxxxxxx.
Console> (enable)Step 3
Use the dir bootflash: command to ensure that there is sufficient space in Flash memory to store the promupgrade image. If there is insufficient space, delete one or more images and then enter the squeeze bootflash: command to reclaim the space.
Step 4
Download the promupgrade image into Flash memory using the copy tftp command.
This example shows how to download the promupgrade image cat4000-promupgrade.6-1-4.bin from the remote host Lab_Server to bootflash:
Console> (enable) copy tftp flashIP address or name of remote host []? Lab_ServerName of file to copy from []? /cat4000-promupgrade.6-1-4.binFlash device []? bootflashName of file to copy to []? cat4000-promupgrade.6-1-4.bin9205592 bytes available on device bootflash, proceed (y/n) [n]? yCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCFile has been copied successfully.Console > (enable)Step 5
Ensure that the last line in the output of the show boot command is boot:image specified by the boot system commands.
•
If the last line in the output of the show boot command is not boot:image specified by the boot system commands, go to Step 6.
•
If the last line in the output of the show boot command is boot:image specified by the boot system commands, go to Step 7.
This example shows the autoboot configuration:
Console> (enable) show bootBOOT variable = bootflash:cat4000.5-5-8.bin,1;CONFIG_FILE variable = bootflash:switch.cfgConfiguration register is 0x102ignore-config:disabledauto-config:non-recurringconsole baud:9600boot:image specified by the boot system commands
Console > (enable)Step 6
If the last line in the output of the show boot command is not boot:image specified by the boot system commands, use the set boot config-register command to set the boot configuration.
This example shows how to set the boot configuration:
Console > (enable) set boot config-register boot systemConfiguration register is 0x102ignore-config:disabledauto-config:non-recurringconsole baud:9600boot:image specified by the boot system commandsConsole > (enable)Step 7
Use the set boot system flash command to prepend the promupgrade image to the boot string:
Note
Make sure that you use the prepend keyword with the set boot system flash command. The switch always boots the first image in the boot string, and you want the promupgrade image to boot first.
This example shows how to prepend the promupgrade image to the boot string:
Console> (enable) set boot system flash bootflash:cat4000-promupgrade.6-1-4.bin prependBOOT variable = bootflash:cat4000-promupgrade.6-1-4.bin,1;bootflash:cat4000.5-5-8.bin,1;Step 8
Reset the switch to boot the promupgrade program.
CautionNo intervention is necessary to complete the upgrade. Do not interrupt the boot process by performing a reset, power cycle, or OIR of the supervisor engine for at least 5 minutes! If the process is not allowed to complete, you may damage the switch and have to return it to Cisco for repair.
Upgrading the ROMMON may require up to 5 minutes because the switch boots the promupgrade image. This special program erases the current ROMMON from Flash memory and installs the new one. After installing the new ROMMON, the system resets again and boots the next image in the BOOT string. If the BOOT string was configured as described in Step 7, the next image is the software image that the switch was originally configured to boot.
Note
A Telnet session is disconnected when you reset the switch; you will lose connectivity to the switch for some time.
If you connect to the console serial port, similar output displays when you reset the switch:
0:00.530901:ig0:00:10:7b:aa:d3:fe is 172.20.59.2030:00.531660:netmask:255.255.255.00:00.532030:broadcast:172.20.59.2550:00.532390:gateway:172.20.59.1WS-X4012 bootrom version 6.1(2), built on 2000.04.03 15:20:09H/W Revisions:Meteor:2 Comet:8 Board:1Supervisor MAC addresses:00:10:7b:aa:d0:00 through 00:10:7b:aa:d3:ff (1024 addresses)Installed memory:64 MBTesting LEDs.... done!The system will autoboot in 5 seconds.Type control-C to prevent autobooting.rommon 1 >The system will now begin autobooting.Autobooting image:"bootflash:cat4000-promupgrade.6-1-4.bin"CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC#############################Replacing ROM version 6.1(2) with version 6.1(4)Upgrading your PROM... DO NOT RESET the systemunless instructed or it may NOT be bootable!!!Beginning erase of 524288 bytes at offset 0x0... Done!Beginning write of system prom (467456 bytes at offset 0x0)...This could take as little as 10 seconds or up to 2 minutes.Please DO NOT RESET!*******************************************Success!System will reset in 2 seconds...[ ... ]The switch reboots back into the online software:
0:00.530856:ig0:00:10:7b:aa:d3:fe is 172.20.59.2030:00.531616:netmask:255.255.255.00:00.531967:broadcast:172.20.59.2550:00.532342:gateway:172.20.59.1WS-X4012 bootrom version 6.1(4), built on 2000.04.03 15:20:09H/W Revisions:Meteor:2 Comet:8 Board:1Supervisor MAC addresses:00:10:7b:aa:d0:00 through 00:10:7b:aa:d3:ff (1024 addresses)Installed memory:64 MBTesting LEDs.... done!The system will autoboot in 5 seconds.Type control-C to prevent autobooting.rommon 1 >The system will now begin autobooting.Autobooting image:"bootflash:cat4000.5-5-8.bin"CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCC#####################################Step 9
In privileged mode, use the show version command to verify that the new ROMMON version is running on the switch.
The ROMMON version number is listed as the System Bootstrap Version. For example, this system is running ROMMON version 6.1(4):
Console> (enable) show versionWS-C4003 Software, Version NmpSW:5.5(8)Copyright (c) 1995-2001 by Cisco Systems, Inc.NMP S/W compiled on May 24 2001, 21:12:09GSP S/W compiled on May 24 2001, 18:39:50System Bootstrap Version:6.1(4)Hardware Version:1.0 Model:WS-C4003 Serial #:xxxxxxxxx...Console > (enable)
CautionWhen entering the clear boot system flash cat.4000-promupgrade.6-1-4.bin command, be sure to type the correct promupgrade image in the command syntax. If you enter only clear boot system flash, all images in the autoboot string are cleared, and the switch will not know which image to boot.
Step 10
Use the clear boot system flash promupgrade_image command to remove the promupgrade program from the autoboot string.
This example shows how to remove the promupgrade image cat.4000-promupgrade.6-1-4.bin from the boot sequence. Notice that the response message shows the system image for software release 5.5(8) in the autoboot string.
Console> (enable) clear boot system flash bootflash:cat4000-promupgrade.6-1-4.binBOOT variable = bootflash:cat4000.5-5-8.bin,1;Step 11
Use the del command to delete the promupgrade program from Flash memory and squeeze the Flash memory to reclaim unused space.
This example shows how to delete the promupgrade image cat.4000-promupgrade.6-1-4.bin from Flash memory and reclaim unused space:
Console> (enable) del bootflash:cat4000-promupgrade.6-1-4.binConsole> (enable) squeeze bootflash:All deleted files will be removed, proceed (y/n) [n]? ySqueeze operation may take some time, proceed (y/n) [n]? yConsole> (enable)Step 12
After removing the promupgrade image from the BOOT string, use the show boot command to verify that the BOOT string is set correctly.
Product and Software Version Support Matrix
This section contains the configuration matrixes to help you order Catalyst 4000 family products. Table 1 lists the minimum supervisor engine software version and the current recommended supervisor engine software version for Catalyst 4000 family modules and chassis.
Release 6.x Orderable Software Images
Table 2 lists the software versions and applicable ordering information for Catalyst 4000 family supervisor engine software release 6.x.
Table 2 Release 6.x Orderable Software Image Matrix
Software Release Filename Orderable Product NumberFlash on System Orderable Product NumberSpare Upgrade (Floppy Media) Supervisor Engine I and II6.1(1)
cat4000.6-1-1.bin
SC4K-SUP-6.1.1
SC4K-SUP-6.1.1=
6.1(1) Cisco View1
cat4000-cv.6-1-1.bin
SC4K-SUPCV-6.1.1
SC4K-SUPCV-6.1.1=
6.1(1) Secure Shell
cat4000-k9.6-1-1.bin
SC4K-SUPK9-6.1.1
SC4K-SUPK9-6.1.1=
6.1(1e)
cat4000.6-1-1e.bin
SC4K-SUP-6.1.1e
SC4K-SUP-6.1.1e=
6.1(2)
cat4000.6-1-2.bin
SC4K-SUP-6.1.2
SC4K-SUP-6.1.2=
6.1(2) Cisco View1
cat4000-cv.6-1-2.bin
SC4K-SUPCV-6.1.2
SC4K-SUPCV-6.1.2=
6.1(2) Secure Shell
cat4000-k9.6-1-2.bin
SC4K-SUPK9-6.1.2
SC4K-SUPK9-6.1.2=
6.1(2a)
cat4000.6-1-2a.bin
SC4K-SUP-6.1.2a
SC4K-SUP-6.1.2a=
6.1(3)
cat4000.6-1-3.bin
SC4K-SUP-6.1.3
SC4K-SUP-6.1.3=
6.1(3) Cisco View1
cat4000-cv.6-1-3.bin
SC4K-SUPCV-6.1.3
SC4K-SUPCV-6.1.3=
6.1(3) Secure Shell
cat4000-k9.6-1-3.bin
SC4K-SUPK9-6.1.3
SC4K-SUPK9-6.1.3=
6.1(3a)
cat4000.6-1-3a.bin
SC4K-SUP-6.1.3a
SC4K-SUP-6.1.3a=
6.1(4b)
cat4000.6-1-4b.bin
SC4K-SUP-6.1-4b
SC4K-SUP-6.1-4b=
6.2(1)1
cat4000.6-2-1.bin
SC4K-SUP-6.2-1
SC4K-SUP-6.2-1=
6.2(1) Cisco View1
cat4000-cv.6-2-1.bin
SC4K-SUPCV-6.2-1
SC4K-SUPCV-6.2-1=
6.2(1) Secure Shell
cat4000-k9.6-2-1.bin
SC4K-SUPK9-6.2-1
SC4K-SUPK9-6.2-1=
6.2(1a)
cat4000.6-2-1a.bin
SC4K-SUP-6.2-1a
SC4K-SUP-6.2-1a=
6.2(2)
cat4000.6-2-2.bin
SC4K-SUP-6.2-2
SC4K-SUP-6.2-2=
6.2(2) Cisco View1
cat4000-cv.6-2-2.bin
SC4K-SUPCV-6.2-2
SC4K-SUPCV-6.2-2=
6.2(2) Secure Shell
cat4000-k9.6-2-2.bin
SC4K-SUPK9-6.2-2
SC4K-SUPK9-6.2-2=
6.2(2a)
cat4000.6-2-2a.bin
SC4K-SUP-6.2-2a
SC4K-SUP-6.2-2a=
6.2(3)
cat4000.6-2-3.bin
SC4K-SUP-6.2-3
SC4K-SUP-6.2-3=
6.2(3) Cisco View1
cat4000-cv.6-2-3.bin
SC4K-SUPCV-6.2-3
SC4K-SUPCV-6.2-3=
6.2(3) Secure Shell
cat4000-k9.6-2-3.bin
SC4K-SUPK9-6.2-3
SC4K-SUPK9-6.2-3=
6.3(1)
cat4000.6-3-1.bin
SC4K-SUP-6.3-1
SC4K-SUP-6.3-1=
6.3(1) Secure Shell
cat4000-k9.6-3-1.bin
SC4K-SUPK9-6.3-1
SC4K-SUPK9-6.3-1=
6.3(1a)
cat4000.6-3-1a.bin
SC4K-SUP-6.3-1a
SC4K-SUP-6.3-1a=
6.3(2)
cat4000.6-3-2.bin
SC4K-SUP-6.3-2
SC4K-SUP-6.3-2=
6.3(2) Secure Shell
cat4000-k9.6-3-2.bin
SC4K-SUPK9-6.3-2
SC4K-SUPK9-6.3-2=
6.3(2) Cisco View1
cat4000-cv.6-3-2.bin
SC4K-SUPCV-6.3-2
SC4K-SUPCV-6.3-2=
6.3(2a)
cat4000.6-3-2a.bin
SC4K-SUP-6.3-2a
SC4K-SUP-6.3-2a=
6.3(3)
cat4000.6-3-3.bin
SC4K-SUP-6.3-3
SC4K-SUP-6.3-3=
6.3(3) Secure Shell
cat4000-k9.6-3-3.bin
SC4K-SUPK9-6.3-3
SC4K-SUPK9-6.3-3=
6.3(3) Cisco View1
cat4000-cv.6-3-3.bin
SC4K-SUPCV-6.3-3
SC4K-SUPCV-6.3-3=
6.3(3a)
cat4000.6-3-3a.bin
SC4K-SUP-6.3-3a
SC4K-SUP-6.3-3a=
6.3(4)
cat4000.6-3-4.bin
SC4K-SUP-6.3-4
SC4K-SUP-6.3-4=
6.3(4a)
cat4000.6-3-4a.bin
SC4K-SUP-6.3a-4
SC4K-SUP-6.3-4a=
6.3(5)
cat4000.6-3-5.bin
SC4K-SUP-6.3-5
SC4K-SUP-6.3-5=
6.3(5) Secure Shell
cat4000-k9.6-3-5.bin
SC4K-SUPK9-6.3-5
SC4K-SUPK9-6.3-5=
6.3(6)
cat4000.6-3-6.bin
SC4K-SUP-6.3-6
SC4K-SUP-6.3-6=
6.3(6) Secure Shell
cat4000-k9.6-3-6.bin
SC4K-SUPK9-6.3-6
SC4K-SUPK9-6.3-6=
6.3(7)
cat4000.6-3-7.bin
SC4K-SUP-6.3-7
SC4K-SUP-6.3-7=
6.3(7) Secure Shell
cat4000-k9.6-3-7.bin
SC4K-SUPK9-6.3-7
SC4K-SUPK9-6.3-7=
6.3(8)
cat4000.6-3-8.bin
SC4K-SUP-6.3-8
SC4K-SUP-6.3-8=
6.3(8) Secure Shell
cat4000-k9.6-3-8.bin
SC4K-SUPK9-6.3-8
SC4K-SUPK9-6.3-8=
6.3(9)
cat4000.6-3-9.bin
SC4K-SUP-6.3-9
SC4K-SUP-6.3-9=
6.3(9) Secure Shell
cat4000-k9.6-3-9.bin
SC4K-SUPK9-6.3-9
SC4K-SUPK9-6.3-9=
6.3(10)
cat4000.6-3-10.bin
SC4K-SUP-6.3-10
SC4K-SUP-6.3-10=
6.3(10) Secure Shell
cat4000-k9.6-3-10.bin
SC4K-SUPK9-6.3-10
SC4K-SUPK9-6.3-10=
6.4(1)
cat4000.6-4-1.bin
SC4K-SUP-6.4-1
SC4K-SUP-6.4-1=
6.4(1) Secure Shell
cat4000-k9.6-4-1.bin
SC4K-SUPK9-6.4-1
SC4K-SUPK9-6.4-1=
6.4(2)
cat4000.6-4-2.bin
SC4K-SUP-6.4-2
SC4K-SUP-6.4-2=
6.4(2) Secure Shell
cat4000-k9.6-4-2.bin
SC4K-SUPK9-6.4-2
SC4K-SUPK9-6.4-2=
6.4(3)
cat4000.6-4-3.bin
SC4K-SUP-6.4-3
SC4K-SUP-6.4-3=
6.4(3) Secure Shell
cat4000-k9.6-4-3.bin
SC4K-SUPK9-6.4-3
SC4K-SUPK9-6.4-3=
6.4(4)
cat4000.6-4-4.bin
SC4K-SUP-6.4-4
SC4K-SUP-6.4-4=
6.4(4) Secure Shell
cat4000-k9.6-4-4.bin
SC4K-SUPK9-6.4-4
SC4K-SUPK9-6.4-4=
6.4(5)
cat4000.6-4-5.bin
SC4K-SUP-6.4-5
SC4K-SUP-6.4-5=
6.4(5) Secure Shell
cat4000-k9.6-4-5.bin
SC4K-SUPK9-6.4-5
SC4K-SUPK9-6.4-5=
6.4(6)
cat4000.6-4-6.bin
SC4K-SUP-6.4-6
SC4K-SUP-6.4-6=
6.4(6) Secure Shell
cat4000-k9.6-4-6.bin
SC4K-SUPK9-6.4-6
SC4K-SUPK9-6.4-6=
6.4(7)
cat4000.6-4-7.bin
SC4K-SUP-6.4-7
SC4K-SUP-6.4-7=
6.4(7) Secure Shell
cat4000-k9.6-4-7.bin
SC4K-SUPK9-6.4-7
SC4K-SUPK9-6.4-7=
6.4(8)
cat4000.6-4-8.bin
SC4K-SUP-6.4-8
SC4K-SUP-6.4-8=
6.4(8) Secure Shell
cat4000-k9.6-4-8.bin
SC4K-SUPK9-6.4-8
SC4K-SUPK9-6.4-8=
6.4(8a)
cat4000.6-4-8a.bin
SC4K-SUP-6.4-8a
SC4K-SUP-6.4-8a=
6.4(9)
cat4000.6-4-9.bin
SC4K-SUP-6.4-9
SC4K-SUP-6.4-9=
6.4(9) Secure Shell
cat4000-k9.6-4-9.bin
SC4K-SUPK9-6.4-9
SC4K-SUPK9-6.4-9=
6.4(10)
cat4000.6-4-10.bin
SC4K-SUP-6.4-10
SC4K-SUP-6.4-10=
6.4(10) Secure Shell
cat4000-k9.6-4-10.bin
SC4K-SUPK9-6.4-10
SC4K-SUPK9-6.4-10=
6.4(11)
cat4000.6-4-11.bin
SC4K-SUP-6.4-11
SC4K-SUP-6.4-11=
6.4(11) Secure Shell
cat4000-k9.6-4-11.bin
SC4K-SUPK9-6.4-11
SC4K-SUPK9-6.4-11=
6.4(12)
cat4000.6-4-12.bin
SC4K-SUP-6.4-12
SC4K-SUP-6.4-12=
6.4(12) Secure Shell
cat4000-k9.6-4-12.bin
SC4K-SUPK9-6.4-12
SC4K-SUPK9-6.4-12=
6.4(13)
cat4000.6-4-13.bin
SC4K-SUP-6.4-13
SC4K-SUP-6.4-13=
6.4(13) Secure Shell
cat4000-k9.6-4-13.bin
SC4K-SUPK9-6.4-13
SC4K-SUPK9-6.4-13=
6.4(14)
cat4000.6-4-14.bin
SC4K-SUP-6.4-14
SC4K-SUP-6.4-14=
6.4(14) Secure Shell
cat4000-k9.6-4-14.bin
SC4K-SUPK9-6.4-14
SC4K-SUPK9-6.4-14=
6.4(15)
cat4000.6-4-15.bin
SC4K-SUP-6.4-15
SC4K-SUP-6.4-15=
6.4(15) Secure Shell
cat4000-k9.6-4-15.bin
SC4K-SUPK9-6.4-15
SC4K-SUPK9-6.4-15=
6.4(16)
cat4000.6-4-16.bin
SC4K-SUP-6.4-16
SC4K-SUP-6.4-16=
6.4(16) Secure Shell
cat4000-k9.6-4-16.bin
SC4K-SUPK9-6.4-16
SC4K-SUPK9-6.4-16=
6.4(17)
cat4000.6-4-17.bin
SC4K-SUP-6.4-17
SC4K-SUP-6.4-17=
6.4(17) Secure Shell
cat4000-k9.6-4-17.bin
SC4K-SUPK9-6.4-17
SC4K-SUPK9-6.4-17=
6.4(18)
cat4000.6-4-18.bin
SC4K-SUP-6.4-18
SC4K-SUP-6.4-18=
6.4(18) Secure Shell
cat4000-k9.6-4-18.bin
SC4K-SUPK9-6.4-18
SC4K-SUPK9-6.4-18=
6.4(19)
cat4000.6-4-19.bin
SC4K-SUP-6.4-19
SC4K-SUP-6.4-19=
6.4(19) Secure Shell
cat4000-k9.6-4-19.bin
SC4K-SUPK9-6.4-19
SC4K-SUPK9-6.4-19=
6.4(20)
cat4000.6-4-20.bin
SC4K-SUP-6.4-20
SC4K-SUP-6.4-20=
6.4(20) Secure Shell
cat4000-k9.6-4-20.bin
SC4K-SUPK9-6.4-20
SC4K-SUPK9-6.4-20=
6.4(21)
cat4000.6-4-21.bin
SC4K-SUP-6.4-21
SC4K-SUP-6.4-21=
6.4(21) Secure Shell
cat4000-k9.6-4-21.bin
SC4K-SUPK9-6.4-21
SC4K-SUPK9-6.4-21=
1 The 6.x CiscoView releases require JPI (Java Plug-in) 1.3.0 in the browser. This version is incompatible with the 5.5(3) CiscoView and earlier releases, which require JPI 1.2.2. Software releases 5.5(4) CiscoView and later work with JPI 1.3.0. Java Plug-in versions released after 1.3.0 (1.3.0_01 and above) do not work with software releases 5.5(4) CiscoView and 6.x CiscoView.
New Features for Supervisor Engine Software Release 6.4
This section describes the new hardware and software features available in software release 6.4.
Hardware Features
There are no hardware features that are new to software release 6.4.
Software Features
There are no software features that are new to software release 6.4.
New Features for Supervisor Engine Software Release 6.3
This section describes the new hardware and software features available in software release 6.3.
Hardware Features
The following hardware features are new to software release 6.3:
•
48-port Gigabit Ethernet switching module (WS-X4448-GB-LX)
Software Features
The following software features are new to software release 6.3:
•
EtherChannel Enhancement
An EtherChannel is preserved even if it contains only one port. In software releases prior to 6.3(1), if you have a 2-port channel and one link is removed, the remaining link is removed and added back to spanning tree, which causes a loss of connection on the channel until the link is forwarding again.
•
Power Management Enhancement
The power management feature provides 1+1 power redundancy for the Catalyst 4000 series switches but is designed to optimized a Catalyst 4006 chassis consisting of a WS-X4013 supervisor engine and four WS-X4148-RJ or WS-X4148-RJ21 modules.
•
CDPv2 Enhancements
–
Addition of TLVs such as sysName, sysObjectID, management address, and physical location
–
Support of a new device ID format called the mac-address format in addition to the "old-style" format (as in the device hardware serial number)
–
Display changes corresponding to some parameters such as device ID for the show cdp command
•
Private VLAN on sc0
The management interface, sc0, can be assigned to a private VLAN as well as regular VLANs.
•
Remote SPAN
Source and destination SPAN ports can be on different compatible switches.
•
Display SNMPv3 counters using the CLI
You can now use the CLI to display SNMP counters for various MIBs.
•
SNMPv3 enhancements
The SNMPv3 implementation in software releases prior to 6.3(1) support RFC 2271 through RFC 2275. RFC 2271 through RFC 2275 were replaced with RFC 2571-RFC 2576. The SNMPv3 enhancement in 6.3(1) implements RFC 2571 through RFC 2576.
•
Text Config Mode
When you use text file configuration mode, the system stores its configuration as a text file in nonvolatile storage, either in NVRAM or Flash memory. This text file consists of commands entered by you to configure various features.
•
Support for the following MIBs:
–
CISCO-AAA-CLIENT-MIB
–
CISCO-ENTITY-FRU-CONTROL-MIB
–
CISCO-RMON-CONFIG-MIB Enhancement
–
CISCO-STP-EXTENSION-MIB
–
CISCO-SYSTEM-MIB Enhancement
New Features for Supervisor Engine Software Release 6.2
This section describes the new hardware and software features available in software release 6.2.
Hardware Features
The following hardware features are new to software release 6.2:
•
48-port 100BASE-FX Fast Ethernet switching module (WS-X4148-FX-MT)
•
24-port 10/100/1000BASE-T Gigabit Ethernet switching module (WS-X4424-GB-RJ45)
Software Features
The following software features are new to software release 6.2:
•
Dynamic VLAN support for VVID
Prior to software release 6.2(1), dynamic ports could only belong to one VLAN. You could not enable the dynamic port VLAN feature on ports that carried a native VLAN and an auxiliary VLAN. With software release 6.2(1) and later releases, the dynamic ports can belong to two VLANs. The switch port configured for connecting an IP phone can have separate VLANs that are configured for carrying the following traffic:
–
Voice traffic to and from the IP phone (auxiliary VLAN)
–
Data traffic to and from the PC that is connected to the switch through the access port of the IP phone (native VLAN)
•
BPDU packet filtering
BPDU packet filtering turns off BPDU transmission on PortFast-enabled ports and nontrunking ports.
•
BPDU skew detection and syslog
BPDU skew detection allows you to troubleshoot slow network convergence that is caused by skewing.
•
IEEE 802.1x
IEEE 802.1x is a client-server-based access control and authentication protocol that restricts unauthorized devices from connecting to a LAN through publicly accessible ports.
•
Local command accounting
Local command accounting records the last 100 commands that the user entered into the system.
•
Loop guard



boot:image specified by the boot system commands