Release Notes for the Catalyst 4500 Series Switch, Cisco IOS, 12.1(19)E
Available Languages
Table Of Contents
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.1(19)E
New Hardware Features in Release 12.1(19)E
New Software Features in Release 12.1(19)E
New Hardware Features in Release 12.1(14)E1
New Software Features in Release 12.1(14)E1
New Hardware Features in Release 12.1(12c)EW
New Software Features in Release 12.1(12c)EW
New Hardware Features in Release 12.1(11b)EW
New Software Features in Release 12.1(11b)EW
New Hardware Features in Release 12.1(8a)EW
New Software Features in Release 12.1(8a)EW
Upgrading the Supervisor Engine ROMMON and the Cisco IOS Software
Upgrading the Supervisor Engine ROMMON
Upgrading the Cisco IOS Software
Open Caveats in Software Release 12.1(19)E
Resolved Caveats in Software Release 12.1(19)E
Open Caveats in Software Release 12.1(14)E1
Resolved Caveats in Software Release 12.1(14)E1
Open Caveats in Software Release 12.1(12c)EW1
Resolved Caveats in Software Release 12.1(12c)EW1
Open Caveats in Software Release 12.1(12c)EW
Resolved Caveats in Software Release 12.1(12c)EW
Open Caveats in Software Release 12.1(11b)EW1
Resolved Caveats in Software Release 12.1(11b)EW1
Open Caveats in Software Release 12.1(11b)EW
Resolved Caveats in Software Release 12.1(11b)EW
Open Caveats in Software Release 12.1(8a)EW1
Resolved Caveats in Software Release 12.1(8a)EW1
Open Caveats in Software Release 12.1(8a)EW
Resolved Caveats in Software Release 12.1(8a)EW
Recovering from Loss of the Boot Loader Image
Troubleshooting at the System Level
Documentation Updates for Release 12.1(19)E
Documentation Updates for Release 12.1(14)E1
Documentation Updates for Release 12.1(12c)EW
Cisco IOS System Message Guide for the Catalyst Family Switch
Cisco IOS Command Reference for the Catalyst 4000 Family Switch
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
Cisco IOS System Message Guide for the Catalyst Family Switch
Cisco IOS Command Reference for the Catalyst 4000 Family Switch
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
Cisco IOS System Message Guide for the Catalyst Family Switch
Cisco IOS Command Reference for the Catalyst 4000 Family Switch
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
Obtaining Documentation and Submitting a Service Request
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.1(19)E
Current Release
12.1(19)E—May 27, 2003Previous Releases
12.1(14)E1, 12.1(12c)EW1, 12.1(12c)EW, 12.1(11b)EW1, 12.1(11b)EW, 12.1(8a)EW1, 12.1(8a)EWProduct Numbers:
•
S4KL3-12119E—Cisco IOS for the Catalyst 4000 Family Supervisor Engine III and IV, basic Layer 3 software image (RIP, Static Routes, AppleTalk and IPX), Release 12.1(19)E
•
•
•
•
•
•
•
•
•
These release notes describe the features, modifications, and caveats for the Cisco IOS software on the Catalyst 4500 series switch. The most current software release is version 12.1(19)E.
Note
As of May 2003, 12.1(13)EW is the latest 12.1EW IOS release for the Catalyst 4500. Software features such as PBR, DBL, Port Security, Jumbo Frames, as well as support for the Catalyst 4500 NetFlow Services Card, 1000BASE-T GBIC and the AGM module are contained in this release. The Catalyst 4500 12.1EW IOS release train will continue to be the vehicle to offer the latest hardware and software features.
Contents
This publication consists of these sections:
•
•
•
•
System Requirements
This section describes the system requirements:
Memory Requirements
These are the minimum required memory configurations for Cisco IOS on the Catalyst 4500 series switch:
•
•
Supported Hardware
Supported Features
Table 1 lists the software features for the Catalyst 4500 series switch.
Table 1 Feature Set for the Catalyst 4500 Series Switch
10/100/1000BASE-TX half duplex and full duplex
1000BASE-SX,-LX, and long haul (-LX/LH, -ZX) full duplex
Longwave laser single mode GBICs1
Layer 2 transparent bridging2
Layer 2 MAC3 learning, aging, and switching by software
Layer 2 hardware forwarding at 48 Mpps
Layer 2 switch ports and VLAN trunks
Spanning-Tree Protocol (IEEE 802.1D) per VLAN
802.1s and 802.1w
Per-VLAN spanning tree (PVST) and PVST+
Spanning-tree root guard
Spanning-tree Loop guard and PortFast BPDU Filtering
Support for 1600 byte frames
Private VLANs
ISL4 -based VLAN encapsulation (excluding blocking ports on WS-X4418-GB and WS-X4412-2GB-T)5
IEEE 802.1Q-based VLAN encapsulation
Multiple VLAN access port
VLAN Trunking Protocol (VTP) and VTP domains
Support for 4096 VLANs per switch
Unidirectional link detection (UDLD) and aggressive UDLD
IP and IP multicast routing and switching between Ethernet ports
Static IP routing
QoS-based forwarding based on IP precedence
CEF6 load balancing
Hardware-based IP CEF routing at 48Mpps
Up to 128,000 IP routes
Up to 32,000 IP host entries (Layer 3 adjacencies)
Up to 12,000 IP multicast route entries
Multicast flooding suppression for STP changes
Software routing of IPX and AppleTalk
IGMP v1, v2, and v3
DTP7
RIP8 and RIP II
IGRP9
EIGRP10
OSPF11
BGP412
MBGP13
MSDP14
ICMP15 Router Discovery Protocol
PIM16 —sparse and dense mode
Static routes
Classless interdomain routing (CIDR)
DVMRP17
SSM
Cisco EtherChannel, Fast EtherChannel, and Gigabit EtherChannel technology across line cards
Load balancing for routed traffic, based on source and destination IP addresses
Load sharing for bridged traffic based on MAC addresses
ISL on the Fast EtherChannel and Gigabit EtherChannel
IEEE 802.1Q on the Fast EtherChannel and Gigabit EtherChannel
Bundling of up to eight Fast Ethernet ports
Bundling of up to eight Gigabit Ethernet ports
Up to 64 active Fast Ethernet port channels
Up to 64 active Gigabit Ethernet port channels
Secondary addressing
Bootstrap protocol (BOOTP)
Authentication using TACACS+ and RADIUS protocol
Cisco Discovery Protocol (CDP)
Cisco Group Management Protocol (CGMP) server support
HSRP18 over 10/100 Ethernet, Gigabit Ethernet, Fast EtherChannel, and Gigabit EtherChannel
IGMP19 snooping v1 and v2
IGMP filtering
Port Aggregation Protocol (PagP)
SNMP20 v1 and v2
DHCP server and relay-agent
DHCP snooping
802.1x port-based authentication
Router standard and extended ACLs 21 on all ports with no performance penalty
VLAN Access Control Lists
Local Proxy ARP
Per-port QoS22 rate-limiting and shaping
Inline power support for Cisco IP phones
Power redundancy
RPR23
1 GBICs = 1470, 1490, 1510, 1530, 1550, 1570, 1590, and 1610 nm
2 This is hardware-based transparent bridging within a VLAN.
3 MAC = Media Access Control
4 ISL = Inter-Switch Link
5 Ports 3 thru 18 on the WS-X4418-GB and ports 1 thru 12 on the WS-X4412-2GB
6 CEF = Cisco Express Forwarding
7 DTP = Dynamic Trunking Protocol
8 RIP = Routing Information Protocol
9 IGRP = Interior Gateway Routing Protocol
10 EIGRP = Enhanced Interior Gateway Routing Protocol
11 OSPF = Open Shortest Path First
12 BGP4 = Border Gateway Protocol 4
13 MBGP = Multicast Border Gateway Protocol
14 MSDP = Multicast Source Discovery Protocol
15 ICMP = Internet Control Message Protocol
16 PIM = Protocol Independent Multicast
17 DVMRP = Distance Vector Multicast Routing Protocol
18 HSRP = Hot Standby Router Protocol
19 IGMP = Internet Group Management Protocol
20 SNMP = Simple Network Management Protocol
21 ACLs = Access Control Lists
22 QoS = Quality of Service
23 RPR = Supervisor redundancy
Unsupported Features
These are some of the features that are not supported in Cisco IOS Release 12.1(19)E for the Catalyst 4500 series switch:
•
•
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
New and Changed Information
These sections describe the new and changed information for the Catalyst 4500 series switch running Cisco IOS:
•
•
•
•
•
•
•
•
•
•
New Hardware Features in Release 12.1(19)E
None. This is an E train release.
New Software Features in Release 12.1(19)E
None. This is an E train release.
New Hardware Features in Release 12.1(14)E1
None. This is an E train release.
New Software Features in Release 12.1(14)E1
None. This is an E train release.
New Hardware Features in Release 12.1(12c)EW
Release 12.1(12c)EW provides the following new hardware for the Catalyst 4000 family switch:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
New Software Features in Release 12.1(12c)EW
Release 12.1(12c)EW provides the following Cisco IOS features for the Catalyst 4000 family switch.
•
Note
–
–
–
–
–
–
–
–
–
•
–
•
•
New Hardware Features in Release 12.1(11b)EW
Release 12.1(11b)EW provides initial support of the Cisco IOS software for the Catalyst 4006 switch with Supervisor Engine III and the following modules:
•
•
•
•
New Software Features in Release 12.1(11b)EW
Release 12.1(11b)EW provides initial support of the Cisco IOS for the Catalyst 4006 switch with Supervisor Engine III. Release 12.1(11b)EW provides these features:
•
•
•
•
•
New Hardware Features in Release 12.1(8a)EW
Release 12.1(8a)EW provides initial support of the Cisco IOS software for the Catalyst 4006 switch with Supervisor Engine III and the following modules:
•
•
•
•
•
•
•
•
•
•
•
•
•
New Software Features in Release 12.1(8a)EW
Release 12.1(8a)EW provides initial support of the Cisco IOS for the Catalyst 4006 switch with Supervisor Engine III. Release 12.1(8a)EW provides these features:
•
–
–
–
–
–
–
–
•
•
•
•
•
•
•
–
Static IP routing
IP routing protocols
IP multicast routing protocols–
Internet Group Management Protocol (IGMP) v1 and v2
Cisco Group Membership Protocol (CGMP) server support
Full Internet Control Message Protocol (ICMP) support
ICMP Router Discovery Protocol (IRDP)
Multicast Source Discovery Protocol (MSDP)
Multicast Border Gateway Protocol (MBGP)•
•
•
•
Upgrading the System Software
If you have a Catalyst 4500 series switch running Cisco IOS 12.1(11b)EW1 or earlier, and you want to upgrade your switch to Cisco IOS 12.1(19)E, you must upgrade the Supervisor Engine III or IV ROMMON version to at least 12.1(12r)EW in addition to upgrading the Cisco IOS software.
The following sections describe how to upgrade your switch software:
•
•
•
Upgrading the Supervisor Engine ROMMON and the Cisco IOS Software
This section describes how to upgrade the ROMMON software and the Cisco IOS software on your switch in a single procedure. If this process fails, upgrade your ROMMON software as described in "Upgrading the Supervisor Engine ROMMON" section and then upgrade your Cisco IOS software as described in "Upgrading the Cisco IOS Software" section.
Caution
To upgrade the ROMMON software and Cisco IOS software on your switch follow this procedure:
Step 1
The cat4000-sup3-promupgrade-121_12r_EW programs are available at the same location on Cisco.com where you download Catalyst 4500 system images.
Step 2
Step 3
If you are using a Compact Flash card, use slot0: instead of bootflash:.
Step 4
The following example shows how to download the promupgrade image cat4000-sup3-promupgrade-121_12r_EW from the remote host 172.20.58.78 to bootflash:
Switch# copy tftp: bootflash:Address or name of remote host [172.20.58.78]?Source filename [/home/rommon/4014rommon]? cat4000-sup3-promupgrade-121_12r_EWDestination filename [cat4000-sup3-promupgrade-121_12r_EW]?Accessing tftp://172.20.58.78/ cat4000-sup3-promupgrade-121_12r_EW...Loading cat4000-sup3-promupgrade-121_12r_EW from 172.20.58.78 (via FastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 2006316/4012032 bytes]2006316 bytes copied in 20.936 secs (100315 bytes/sec)Switch#Step 5
The following example shows how to download the Cisco IOS software image cat4000-is-mz.121-14.E1 from the remote host 172.20.58.78 to bootflash:
Switch# copy tftp: bootflash:Address or name of remote host [172.20.58.78]?Source filename [cat4000-is-mz.121-14.E1]?Destination filename [cat4000-is-mz.121-14.E1]?Accessing tftp://172.20.58.78/cat4000-is-mz.121-14.E1...Loading cat4000-is-mz.121-14.E1 from 172.20.58.78 (via FastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 6923388/13846528 bytes]6923388 bytes copied in 72.200 secs (96158 bytes/sec)Switch#Step 6
The following example shows how to display the contents of the BOOT variable.
Switch# show bootvarBOOT variable = bootflash:cat4000-is-mz.121-8a.EWCONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x2100Switch#Step 7
The following example shows how to clear the cat4000-is-mz.121-8a.EW file and save the BOOT variable.
Switch# configure terminalSwitch(config)# no boot system flash bootflash:cat4000-is-mz.121-8a.EWSwitch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Step 8
The following example shows an empty the BOOT variable.
Switch# show bootvarBOOT variable does not existCONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x2100Switch#Step 9
The following example shows how to add the cat4000-sup3-promupgrade-121_12r_EW program and the cat4000-is-mz.121-14.E1 image to the BOOT variable.
Switch# configure terminalSwitch(config)# boot system flash bootflash:cat4000-sup3-promupgrade-121_12r_EWSwitch(config)# boot system flash bootflash:cat4000-is-mz.121-14.E1Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3723 to 1312 bytes [OK]Switch#Step 10
The following example shows that the cat4000-sup3-promupgrade-121_12r_EW program and the cat4000-is-mz.121-14.E1 image are in the BOOT variable and that the configuration register is set to 0x21020.
Switch# show bootvarBOOT variable = bootflash:cat4000-sup3-promupgrade-121_12r_EW,1;cat4000-is-mz.121-14.E1,1CONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x2102Switch#Step 11
The following example show how to set the second least significant bit in the configuration register.
Switch# configure terminalSwitch(config)# configure-register 0x2102Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3723 to 1312 bytes [OK]Switch#Step 12
Caution
The following example shows the output from the upgrade and reboot.
Switch# reloadProceed with reload? [confirm]00:02:53:%SYS-5-RELOAD:Reload requested**************************************************** ** Welcome to Rom Monitor for WS-X4014 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ****************************************************Rom Monitor Program Version 12.1(8r)EWBoard type 1, Board revision 6Swamp FPGA revision 16, Dagobah FPGA revision 43............***** The system will autoboot in 5 seconds *****Type control-C to prevent autobooting.. .Established physical link 100MB Half DuplexNetwork layer connectivity may take a few seconds. . .******** The system will autoboot now ********config-register = 0x2102Autobooting using BOOT variable specified file.....Current BOOT file is --- bootflash:cat4000-sup3-promupgrade-121_12r_EW......************************************************************** ** Rom Monitor Upgrade Utility For WS-X4014 System ** This upgrades flash Rom Monitor image to the latest ** ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** **********************************************************......Success! The prom has been upgraded successfully.System will reset itself and reboot in about 15 seconds.0********************************************************* ** Welcome to Rom Monitor for WS-X4014 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** *********************************************************Rom Monitor Program Version 12.1(12r)EWBoard type 1, Board revision 6Swamp FPGA revision 16, Dagobah FPGA revision 48......***** The system will autoboot in 5 seconds *****Type control-C to prevent autobooting.. .Established physical link 100MB Half DuplexNetwork layer connectivity may take a few seconds. . .******** The system will autoboot now ********config-register = 0x2102Autobooting using BOOT variable specified file.....Current BOOT file is --- bootflash:cat4000-is-mz.121-14.E1Rommon reg:0x300041A8Running diags...Decompressing the image#######################################################################################################################[OK]k2diags version 1.6prod:WS-X4014 part:73-6854-06 serial:JAB05450C57Power-on-self-test for Module 1: WS-X4014Status:(. = Pass, F = Fail)....Module 1 PassedExiting to ios...Rommon reg:0x300001A8Running IOS...Decompressing the image###################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################[OK]Restricted Rights LegendUse, duplication, or disclosure by the Government issubject to restrictions as set forth in subparagraph(c) of the Commercial Computer Software - RestrictedRights clause at FAR sec. 52.227-19 and subparagraph(c) (1) (ii) of the Rights in Technical Data and ComputerSoftware clause at DFARS sec. 252.227-7013.cisco Systems, Inc.170 West Tasman DriveSan Jose, California 95134-1706Cisco Internetwork Operating System SoftwareIOS (tm) Catalyst 4000 L3 Switch Software (cat4000-IS-M), Version......Uncompressed configuration from 1033 bytes to 3204 bytesPress RETURN to get started!.....Cisco Internetwork Operating System SoftwareIOS (tm) Catalyst 4000 L3 Switch Software (cat4000-IS-M), Version......Switch#Step 13
In the following example, the ROMMON level is 12.1(12r)EW, and the Cisco IOS version 12.1(19)E.
Switch# show versionCisco Internetwork Operating System SoftwareIOS (tm) Catalyst 4000 L3 Switch Software (cat4000-IS-M), Version12.1(19)E, RELEASE SOFTWARE (fc1)TAC Support:http://www.cisco.com/tacCopyright (c) 1986-2002 by cisco Systems, Inc.Compiled Tue 30-Apr-02 17:34 by ccaiImage text-base:0x00000000, data-base:0x00AA2B8CROM:12.1(12r)EWSwitch uptime is 6 minutesSystem returned to ROM by reloadSystem image file is "slot0:fcsboot"cisco WS-C4006 (MPC8245) processor (revision 6) with 262144K bytes of memory.Processor board IDLast reset from Reload48 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)467K bytes of non-volatile configuration memory.Configuration register is 0x2102Switch#Step 14
The following example shows how to delete the cat4000-sup3-promupgrade-121_12r_EW image from bootflash: and reclaim unused space.
Switch# delete bootflash:cat4000-sup3-promupgrade-121_12r_EWSwitch# squeeze bootflash:All deleted files will be removed, proceed (y/n) [n]? ySqueeze operation may take some time, proceed (y/n) [n]? ySwitch#Step 15
The following example shows how to delete the cat4000-sup3-promupgrade-121_12r_EW image from the BOOT variable.
Switch# configure terminalSwitch(config)# no boot system flash cat4000-sup3-promupgrade-121_12r_EWSwitch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3620 to 1236 bytes [OK]Switch#Step 16
The following example shows that the BOOT variable contains only the Cisco IOS image cat4000-is-mz.121-14.E1.
Switch# show bootvarBOOT variable = bootflash:cat4000-is-mz.121-14.E1,1CONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x2102Switch#Upgrading the Supervisor Engine ROMMON
Caution
If you have a Catalyst 4500 series switch running Cisco IOS 12.1(11b)EW1 or earlier, and you want to upgrade your switch to Cisco IOS 12.1(19)E, you must upgrade the Supervisor Engine ROMMON version to at least 12.1(12r)EW. When you upgrade and boot the Cisco IOS software to 12.1(19)E, the field programmable gate array (FPGA) is automatically upgraded.
Follow this procedure to upgrade your Supervisor Engine ROMMON to 12.1(12r)EW:
Step 1
Note
Step 2
The cat4000-sup3-promupgrade-121_12r_EW programs are available at the same location on Cisco.com where you download Catalyst 4500 system images.
Step 3
If you are using a Compact Flash card, use slot0: instead of bootflash:.
Step 4
The following example shows how to download the promupgrade image cat4000-sup3-promupgrade-121_12r_EW from the remote host 172.20.58.78 to bootflash:
Switch# copy tftp: bootflash:Address or name of remote host [172.20.58.78]?Source filename [cat4000-sup3-promupgrade-121_12r_EW]?Destination filename [cat4000-sup3-promupgrade-121_12r_EW]?Accessing tftp://172.20.58.78/ cat4000-sup3-promupgrade-121_12r_EW...Loading cat4000-sup3-promupgrade-121_12r_EW from 172.20.58.78 (viaFastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 2006316/4012032 bytes]2006316 bytes copied in 20.936 secs (100315 bytes/sec)Switch#Step 5
The following example shows the output after a reset into ROMMON.
Switch# reloadProceed with reload? [confirm]03:57:16:%SYS-5-RELOAD:Reload requested*********************************************************** ** Welcome to Rom Monitor for WS-X4014 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ************************************************************Rom Monitor Program Version 12.1(8r)EW..(output truncated).Established physical link 100MB Half DuplexNetwork layer connectivity may take a few secondsrommon 1 >Step 6
Caution
The following example shows the output from a successful upgrade followed by a system reset.
rommon 2 > boot bootflash:cat4000-sup3-promupgrade-121_12r_EWRommon reg:0x300001A8Decompressing the image############################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################################## [OK]Restricted Rights Legend************************************************************ ** Rom Monitor Upgrade Utility For WS-X4014 System ** This upgrades flash Rom Monitor image to the latest ** ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ************************************************************Image size = 431.476 KBytesMaximum allowed size = 511.75 KBytesUpgrading your PROM... DO NOT RESET the systemunless instructed or upgrade of PROM will fail !!!Beginning erase of 0x80000 bytes at offset 0x3f80000... Done!Beginning write of prom (0x6bddc bytes at offset 0x3f80000)...This could take as little as 30 seconds or up to 2 minutes.Please DO NOT RESET!Success! The prom has been upgraded successfully.System will reset itself and reboot in about 15 seconds.0Step 7
Step 8
The following example shows how to delete the cat4000-sup3-promupgrade-121_12r_EW image from bootflash and reclaim unused space.
Switch# delete bootflash:cat4000-sup3-promupgrade-121_12r_EWSwitch# squeeze bootflash:All deleted files will be removed, proceed (y/n) [n]? ySqueeze operation may take some time, proceed (y/n) [n]? ySwitch#
The ROMMON is now upgraded.
See the "Upgrading the Cisco IOS Software" section for instructions on upgrading the Cisco IOS software on your switch.
Upgrading the Cisco IOS Software
You can upgrade the Cisco IOS software on your Catalyst 4500 series switch using the following procedure.
If you have Cisco IOS software release 12.1(8a)EW loaded on your switch, you must upgrade the ROMMON before upgrading your switch software. For more information, see the "Upgrading the Supervisor Engine ROMMON" section.
Caution
Step 1
Step 2
If you are using a Compact Flash card, use slot0: instead of bootflash:.
Step 3
The following example shows how to download the Cisco IOS software image cat4000-is-mz.121-14.E1 from the remote host 172.20.58.78 to bootflash:
Switch# copy tftp: bootflash:Address or name of remote host [172.20.58.78]?Source filename [cat4000-is-mz121_14.E1]?Destination filename [cat4000-is-mz.121-14.E1]?Accessing tftp://172.20.58.78/cat4000-is-mz.121-14.E1Loading cat4000-is-mz.121-14.E1 from 172.20.58.78 (viaFastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 6923388/13846528 bytes]6923388 bytes copied in 72.200 secs (96158 bytes/sec)Switch#Step 4
The following example shows how to clear the BOOT variable.
Switch# configure terminalSwitch(config)# no boot system flashSwitch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Step 5
The following example shows how to add the cat4000-is-mz.121-14.E1 image to the BOOT variable.
Switch# configure terminalSwitch(config)# boot system flash bootflash:cat4000-is-mz.121-14.E1Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Step 6
The following example show how to set the second least significant bit in the configuration register.
Switch# configure terminalSwitch(config)# configure-register 0x2102Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3723 to 1312 bytes [OK]Switch#Step 7
Caution
The following example shows the output from a successful upgrade followed by a system reset.
Switch# resetRommon reg: 0x2B004180Upgrading FPGA...Decompressing the image############## [OK]******************************************************** ** WS-X4014 FPGA Upgrade Utility For WS-X4014 Machines ** ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Image size = 483.944 KBytesMaximum allowed size = 1023.75 KBytesUpgrading your FPGA image... DO NOT RESET the systemunless instructed or upgrade of FPGA will fail !!!Beginning erase of 0x100000 bytes at offset 0x3d00000... Done!Beginning write of fpga image (0x78fb0 bytes at offset 0x3d00000)...This could take as little as 30 seconds or up to 2 minutes.Please DO NOT RESET!Success! FPGA image has been upgraded successfully.System will reset itself and reboot in about 15 seconds.0*********************************************************** ** Welcome to Rom Monitor for WS-X4014 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Rom Monitor Program Version 12.1(12r)EWBoard type 1, Board revision 5Swamp FPGA revision 16, Dagobah FPGA revision 47MAC Address : 00-30-85-XX-XX-XXIP Address : 10.10.10.91Netmask : 255.255.255.0Gateway : 10.10.10.1TftpServer : Not set.Main Memory : 256 MBytes***** The system will autoboot in 5 seconds *****Type control-C to prevent autobooting.Switch#Step 8
Limitations and Restrictions
These sections list the limitations and restrictions for the current release of Cisco IOS on the Catalyst 4500 series switch:
•
–
–
•
–
–
•
Workaround: Display the configuration with the show standby command and remove the CLI. Here is a sample output of the
[no standby group# name] show standby GigabitEthernet1/1 command:GigabitEthernet1/1 - Group 0Local state is Active, priority 105, may preemptHellotime 1 sec, holdtime 3 secNext hello sent in 0.642Virtual IP address is 131.241.2.6 configuredSecondary virtual IP address 131.241.2.7Active router is localStandby router is 131.241.2.2 expires in 2.872Virtual mac address is 0000.0c07.ac002 state changes, last state change 00:00:41IP redundancy name is "hsrp-Gi1/1-0" (default) <====== this line should be removedPriority tracking 1 interface, 1 up:Interface Decrement StateGigabitEthernet1/2 10 Up•
Workaround: Since the problem is caused by mismatched MTUs, the solution is to change either router's MTU to match the neighbor's MTU.
•
Workaround: Contact your technical support representative for a replacement.
•
•
1q in 1q encapsulation is not supported with any Catalyst 4500 Supervisor Engine.•
•
•
•
•
•
•
•
•
•
•
Caveats
Caveats describe unexpected behavior in Cisco IOS software releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Open Caveats in Software Release 12.1(19)E
This section lists open caveats in release 12.1(19)E:
•
Workaround: Configure fewer switch virtual interfaces (SVIs) in the startup configuration file. (CSCdx91258)
•
2d07h: %SYS-3-CPUHOG: Task ran for 8692 msec (0/0), process = Exec, PC = 128790.
2d07h: %C4K_EBM-4-HOSTFLAPPING: Host 00:10:0B:10:B9:20 in vlan 200 is flapping between port Po2 and port Po1
Workaround: None. (CSCdy21031)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
•
Workaround: None. (CSCdz60995)
•
Error Message %C4K_CHASSIS-2-INSUFFICIENTFANSDETECTED: Too few working fans, the chassis will overheatWorkaround: None. Do not leave chassis operational without fan tray for more than 5 minutes. (CSCdz50817)
•
Workaround: None. (CSCdz55274)
•
Workaround: None. (CSCea89330)
•
For example, you may want to set a boot variable to point to the cat4000-is-mz.121-12c.EW image, but you mistakenly type the first letter as upper case C instead of as lowercase c (for example,
boot system flash bootflash: Cat4000-is-mz.121-12c.EW). When you try to reload the switch it will not boot, because the boot variable is pointing to a nonexistent image.You will not be able to add the correct boot variable, because the software perceives that it already exists and will not add it to the configuration.
Workaround: Remove the invalid boot variable and add the correct one. (CSCeb05517)
•
Workaround: Disable or enable the port. (CSCeb06811)
Resolved Caveats in Software Release 12.1(19)E
This section lists resolved caveats in release 12.1(19)E:
•
Workaround: Cisco has made software available, free of charge, to correct the problem. (CSCdz71127, CSCea02355)
•
Workaround: Use the spanning-tree bpduguard enable interface command to enable BPDU Guard, which will detect any BPDUs received on private VLAN trunk ports. (CSCdx62226)
•
Workaround: Do not use the VLAN configuration shutdown and no shutdown commands to disable the VLAN. To disable the VLANs, delete and recreate the secondary VLAN with the proper VLAN type and association configuration. (CSCdy22082)
•
Workaround: If IP packets can be fragmented in your network, program ACLs in the VLAN map without any Layer 4 information. (CSCdx84696)
•
Workaround: None. (CSCdz89143)
•
Workaround: Wait at least 5 seconds, and then delete an existing user-configured VLAN and enter the no shut command on the Layer 3 physical interface.(CSCdz56613)
•
Workaround: None. (CSCdz49171)
•
Workaround: None. (CSCdz89123)
•
Workaround: None. (CSCdy80025)
Open Caveats in Software Release 12.1(14)E1
This section lists open caveats in release 12.1(14)E1.
•
Workaround: Configure fewer switch virtual interfaces (SVIs) in the startup configuration file. (CSCdx91258)
•
2d07h: %SYS-3-CPUHOG: Task ran for 8692 msec (0/0), process = Exec, PC = 128790.
2d07h: %C4K_EBM-4-HOSTFLAPPING: Host 00:10:0B:10:B9:20 in vlan 200 is flapping between port Po2 and port Po1
Workaround: None. (CSCdy21031)
•
Workaround: Use the spanning-tree bpduguard enable interface command to enable BPDU Guard, which will detect any BPDUs received on private VLAN trunk ports. (CSCdx62226)
•
Workaround: Do not use the shutdown and no shutdown VLAN configuration command to disable the VLAN. To disable the VLANs, delete and recreate the secondary VLAN with the proper VLAN type and association configuration. (CSCdy22082)
•
Workaround: If IP packets can be fragmented in your network, program ACLs in the VLAN map, without any Layer 4 information. (CSCdx84696)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
•
Workaround: None. (CSCdy80025)
•
Workaround: None. (CSCdz89143)
•
Workaround: Wait at least 5 seconds, and then delete an existing user-configured VLAN and enter the no shut command on the Layer 3 physical interface.(CSCdz56613)
•
Workaround: None. (CSCdz60995)
•
Error Message %C4K_CHASSIS-2-INSUFFICIENTFANSDETECTED: Too few working fans, the chassis will overheatWorkaround: None. Do not leave chassis operational without fan tray for more than 5 minutes. (CSCdz50817)
•
Workaround: None. (CSCdz55274)
•
Workaround: None. (CSCdz49171)
•
Workaround: None. (CSCdz89123)
Resolved Caveats in Software Release 12.1(14)E1
This section lists resolved caveats in release 12.1(14)E1.
•
Workaround: To ensure that the ports operate as normal trunks, enter the shutdown, and no shutdown commands after configuring the ports as normal trunks. (CSCdy40311)
•
C4K_REDUNDANCY-4-CONFIGSYNCFAIL: Persistent-config Sync to Standby Supervisor failed
The following messages are displayed on the standby supervisor engine:
C4k_REDUNDANCY-6-SWITCHOVER: Switchover activity detected, changing role from STANDBY to ACTIVE
C4K_REDUNDANCY-6-INIT: Initializing as ACTIVE supervisor
Workaround: Keep your startup-config file reasonably small. (CSCdy02031)
•
Workaround: Do not configure 802.1x on PVLAN ports. (CSCdy23098)
•
Workaround: None. (CSCdz37046)
•
Workaround: To add the VLAN interface to the routing table, either enter the clear ip route command or the shutdown and the noshutdown command on the VLAN interface. (CSCdz46944)
•
Workaround: None. (CSCdz24084)
•
Workaround: None. (CSCdz56298)
•
Workaround: Enter the shutdown and the shutdown commands on the port. (CSCdy17476)
•
Workaround: Ensure that some VLANs are available when you enable routed port channels. (CSCdz39541)
•
Error Message Nov 15 14:33:22 EST: %C4K_EBM-4-HOSTFLAPPING: Host 00:09:11:3D:7F:FC in vlan 204 is flapping between port Fa5/18 and port Gi1/1Error Message Nov 15 14:33:36 EST: %SPANTREE-2-RECV_PVID_ERR: Received BPDU with inconsistent peer vlan id 204 on FastEthernet5/18 VLAN4.Error Message Nov 15 14:33:36 EST: %SPANTREE-2-BLOCK_PVID_PEER: Blocking FastEthernet5/18 on VLAN204. Inconsistent peer vlan.Error Message Nov 15 14:33:36 EST: %SPANTREE-2-BLOCK_PVID_LOCAL: Blocking FastEthernet5/18 on VLAN4. Inconsistent local vlan.Workaround: Apply external power to the phone. (CSCdz34648)
Open Caveats in Software Release 12.1(12c)EW1
This section lists open caveats in release 12.1(12c)EW1.
•
Workaround: To ensure that the ports operate as normal trunks, issue shutdown/no shutdown commands after configuring the ports as normal trunks. (CSCdy40311)
•
C4K_REDUNDANCY-4-CONFIGSYNCFAIL: Persistent-config Sync to Standby Supervisor failed
and the following messages display on the standby supervisor:
C4k_REDUNDANCY-6-SWITCHOVER: Switchover activity detected, changing role from STANDBY to ACTIVE
C4K_REDUNDANCY-6-INIT: Initializing as ACTIVE supervisor
Workaround: Keep your startup-config file reasonably small. (CSCdy02031)
•
Workaround: Don't configure 802.1x on PVLAN ports. (CSCdy23098)
•
Workaround: Configure fewer SVIs in the startup config file. (CSCdx91258)
•
2d07h: %SYS-3-CPUHOG: Task ran for 8692 msec (0/0), process = Exec, PC = 128790.
2d07h: %C4K_EBM-4-HOSTFLAPPING: Host 00:10:0B:10:B9:20 in vlan 200 is flapping between port Po2 and port Po1
Workaround: None. (CSCdy21031)
•
Workaround: Use the spanning-tree bpduguard enable interface command to enable BPDU Guard to detect any BPDUs received on private VLAN trunk ports. (CSCdx62226)
•
Workaround: Do not use the shutdown and no shutdown VLAN configuration command to disable the VLAN. Instead, delete and recreate the secondary VLAN with the proper VLAN type and association configuration. (CSCdy22082)
•
Workaround: If IP packets can be fragmented in your network, program ACLs in the VLAN Map, without any Layer 4 information. (CSCdx84696)
•
Workaround: Don't configure 802.1x on PVLAN ports. (CSCdy23098)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
Resolved Caveats in Software Release 12.1(12c)EW1
•
%Error: Opening vlan.dat on STANDBY
Workaround: After the switch boots, verify that the standby supervisor has a valid cat4000_flash:vlan.dat file. If you suspect the file is invalid, copy the valid file using the following command on the active supervisor:
copy cat4000_flash:vlan.dat slavecat4000_flash:vlan.dat
(CSCdy26890)
•
Workaround:.Review the output of the show power command to check the status of power supplies. This is the only way to be notified of a supply failure. (CSCdy33518)
•
Workaround: Either not enable all these features at the same time, or upgrade the switch to the latest maintenance release image that contains the fix for this problem.
•
Workaround: Issue a shutdown/ no shutdown command at the associated interface to bring up the link.
When you force the speed, the switch port does not auto-detect crossover/straight through cables. In these situations, you must use the correct cable.
–
–
•
Workaround: None. (CSCdy47753)
•
Workaround: Apply an input router ACL to filter out those broadcast DHCP packets before they can be relayed by the Agent. (CSCdy50604)
•
Workaround: Either enable the DHCP snooping feature, or use a VACL instead of a router ACL to filter the DHCP packets. (CSCdy62123)
•
Workaround: First, change the duplex to half, then reconfigure to full. (CSCdy67241)
•
*Sep 19 21:53:17.947: %C4K_HWACLMAN-4-ACLHWPROGERR: <Feature using ACLs>- hardware TCAM limit, ...
*Sep 19 21:53:17.975: %C4K_HWACLMAN-4-ACLHWPROGERRREASON: <Feature using ACLs>- out of software acl programming resources.
Workaround: Re-apply the ACLs to the appropriate security ACL or QoS policy-map. (CSCdy68681)
•
Workaround: Avoid configuring ACLs that trigger L4 operator expansion. (CSCdy70646)
Open Caveats in Software Release 12.1(12c)EW
This section lists open caveats in release 12.1(12c)EW.
•
Workaround: To ensure that the ports operate as normal trunks, issue shutdown/no shutdown commands after configuring the ports as normal trunks. (CSCdy40311)
•
Workaround: Configure fewer SVIs in the startup config. (CSCdx91258)
•
2d07h: %SYS-3-CPUHOG: Task ran for 8692 msec (0/0), process = Exec, PC = 128790.
2d07h: %C4K_EBM-4-HOSTFLAPPING: Host 00:10:0B:10:B9:20 in vlan 200 is flapping between port Po2 and port Po1
Workaround: None. (CSCdy21031)
•
Workaround: Use the spanning-tree bpduguard enable interface command to enable BPDU Guard to detect any BPDUs received on private VLAN trunk ports. (CSCdx62226)
•
Workaround: If possible, do not use the shutdown and no shutdown VLAN configuration command to disable the VLAN. Instead, delete and recreate the secondary VLAN with the proper VLAN type and association configuration. (CSCdy22082)
•
Workaround: If IP packets can be fragmented in your network, program ACLs in the VLAN Map, without any Layer 4 information. (CSCdx84696)
•
C4K_REDUNDANCY-4-CONFIGSYNCFAIL: Persistent-config Sync to Standby Supervisor failed
and the following messages display on the standby supervisor
C4k_REDUNDANCY-6-SWITCHOVER: Switchover activity detected, changing role from STANDBY to ACTIVE
C4K_REDUNDANCY-6-INIT: Initializing as ACTIVE supervisor
Workaround: Keep your startup-config reasonably small. (CSCdy02031)
•
Workaround: Don't configure 802.1x on PVLAN ports. (CSCdy23098)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
Resolved Caveats in Software Release 12.1(12c)EW
This section lists resolved caveats in release 12.1(12c)EW.
•
show platform software etherchannel port-channel channel-no
This command was introduced in software release 12.1(11b)EW. Software release 12.1(8a)EW is not affected by this caveat.
Workaround: Don't use the above command for a port channel in a shutdown state. (CSCdx47694)
•
•
Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)
•
3d03h: %FIB-4-FIBIDB: Missing cef idb for GigabitEthernet2/6 during address chWhen this happens, traffic to or from that interface will not be received or forwarded correctly.
Workaround: Functionality can be restored by bringing the interface administratively down and up, or by disabling and re-enabling IP routing. (CSCdx37609)
•
Workarounds: Determine whether the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txtDetermine whether the router is running a Cisco IOS image that has the correction for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).
Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)
•
Open Caveats in Software Release 12.1(11b)EW1
•
•
show platform software etherchannel port-channel channel-no
This command was introduced in software release 12.1(11b)EW. Software release 12.1(8b)EW is not affected by this caveat.
Workaround: Don't use the above command for a port channel in a shutdown state. (CSCdx47694)
•
•
Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)
•
3d03h: %FIB-4-FIBIDB: Missing cef idb for GigabitEthernet2/6 during address chWhen this happens, traffic to or from that interface will not be received or forwarded correctly.
Workaround: Functionality might be restored by bringing the interface administratively down and up, or by disabling and re-enabling IP routing. (CSCdx37609)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
Resolved Caveats in Software Release 12.1(11b)EW1
•
When the switch enters this state, the NoPacketBuffAvailOrCdmFifoOverruns counter will increment on all ports that have received incoming data traffic. You can display the contents of the NoPacketBuffAvailOrCdmFifoOverruns counter by entering the show platform software interface statistics command.
Workaround: This condition is temporary and can be resolved by resetting the switch. (CSCdx66345)
•
Open Caveats in Software Release 12.1(11b)EW
•
When the switch enters this state, the NoPacketBuffAvailOrCdmFifoOverruns counter will increment on all ports that have received incoming data traffic. You can display the contents of the NoPacketBuffAvailOrCdmFifoOverruns counter by entering the show platform software interface statistics command.
Workaround: This condition is temporary and can be resolved by resetting the switch. (CSCdx66345)
•
•
show platform software etherchannel port-channel channel-no
This command was introduced in software release 12.1(11b)EW. Software release 12.1(8b)EW is not affected by this caveat.
Workaround: Don't use the above command for a port channel in a shutdown state. (CSCdx47694)
•
•
Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)
•
3d03h: %FIB-4-FIBIDB: Missing cef idb for GigabitEthernet2/6 during address chWhen this happens, traffic to or from that interface will not be received or forwarded correctly.
Workaround: Functionality might be restored by bringing the interface administratively down and up, or by disabling and re-enabling IP routing. (CSCdx37609)
•
Workarounds: Determine whether the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txtDetermine whether the router is running a Cisco IOS image that has the correction for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).
Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)
•
Workaround: Detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
Resolved Caveats in Software Release 12.1(11b)EW
•
•
Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)
•
•
•
Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)
•
•
Workaround: Replace the permit ip any any fragment command with the following commands:
permit 1 any any fragmentpermit 2 any any fragmentpermit 255 any any fragment(CSCdw39872)
•
Open Caveats in Software Release 12.1(8a)EW1
•
•
Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)
•
Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)
•
Workarounds: Determine if the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txtDetermine if the router is running a Cisco IOS image that has the fix for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).
Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)
•
•
Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)
•
Workaround: Replace the permit ip any any fragment command with the following commands:
permit 1 any any fragmentpermit 2 any any fragmentpermit 255 any any fragment(CSCdw39872)
•
•
Workaround: detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
•
Resolved Caveats in Software Release 12.1(8a)EW1
•
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
(CSCdw65903)
Open Caveats in Software Release 12.1(8a)EW
•
When the switch enters this state, the NoPacketBuffAvailOrCdmFifoOverruns counter will increment on all ports that have received incoming data traffic. You can display the contents of the NoPacketBuffAvailOrCdmFifoOverruns counter by entering the show platform software interface statistics command.
Workaround: This condition is temporary and can be resolved by resetting the switch. (CSCdx66345)
•
•
•
Workaround: Do not clear the groups all at once. Instead, clear each IGMP group cache entry separately. (CSCdw46417)
•
Workaround: Use extended named ACLs. Named ACLs specified in the ACL config mode do not exhibit this behavior. (CSCdw20032)
•
Workarounds: Determine if the routers have the SA filters configured properly by reviewing the MSDP SA filter recommendations posted at the following URL:
ftp://ftpeng.cisco.com/ipmulticast/config-notes/msdp-sa-filter.txtDetermine if the router is running a Cisco IOS image that has the fix for CSCdr93446 (MSDP: Reducing SA storms and session resets (MSDP rearchitect)).
Review the output of the show ip msdp sa-cache EXEC command to see if some of the SAs can be filtered based on the source address, the Rendezvous point (RP) address, or the autonomous system (AS) number. (CSCdw35003)
•
Workaround: Don not create associations between VLANs if the SVI of the primary VLAN has been deleted.(CSCdw50014)
•
Workaround: detach the ACL from one interface at a time (without deleting the ACL), and then reattach the ACL to that interface. (CSCdw28603)
•
Workaround: Replace the permit ip any any fragment command with the following commands:
permit 1 any any fragmentpermit 2 any any fragmentpermit 255 any any fragment(CSCdw39872)
•
•
Resolved Caveats in Software Release 12.1(8a)EW
There are no resolved caveats in software release 12.1(8a)EW.
Troubleshooting
These sections provide troubleshooting guidelines for the Catalyst 4006 with Supervisor Engine III:
•
•
•
Recovering from Loss of the Boot Loader Image
If you lose the boot loader image, you can recover by using one of the following methods:
1.
rommon 1> boot slot0:<bootable_image>2.
The ROMMON TFTP boot is very similar to the BOOTLDR TFTP boot, except that:
–
–
To boot from ROMMON, perform the following tasks while in ROMMON mode:
a.
b.
c.
For example, to set the supervisor Ethernet port with an IP address 172.16.1.5 and IP mask 255.255.255.0.0, enter the following command:
rommon 2> set interface fa1 172.16.1.5 255.255.0.0d.
e.
f.
For example, to boot the image name cat4000-is-mz.160 located on the TFTP server 172.16.1.8, enter the following command:
rommon 3> boot tftp://172.16.1.8/tftpboot/cat4000-is-mzTroubleshooting at the System Level
This section contains troubleshooting guidelines for system-level problems:
•
•
Troubleshooting Modules
This section contains troubleshooting guidelines for modules:
•
•
Troubleshooting VLANs
Although DTP is a point-to-point protocol, some internetworking devices might forward DTP frames. To avoid connectivity problems that might be caused by a switch acting on these forwarded DTP frames, do the following:
•
•
Troubleshooting Spanning Tree
The Spanning Tree Protocol (STP) blocks certain ports to prevent physical loops in a redundant topology. On a blocked port, switches periodically receive spanning tree bridge protocol data units (BPDUs) from neighboring switches. You can configure the frequency with which BPDUs are received by entering the spanning-tree VLAN vlan_ID hello-time command. By default, the frequency is set to 2 seconds. If a switch does not receive a BPDU in the time period defined by the spanning-tree VLAN vlan_ID max-age command (20 seconds by default), the blocked port transitions to the listening state, the learning state, and to the forwarding state. As it transitions, the switch waits for the time period specified by the spanning-tree VLAN vlan_ID forward-time command (15 seconds by default) in each of these intermediate states. Therefore, a blocked spanning tree interface moves into the forwarding state if it does not receive BPDUs from its neighbor within approximately 50 seconds.
Note
Use these guidelines to debug STP problems:
•
–
The show spanning-tree summary totals command displays the number of logical interfaces in the STP Active column.
•
•
•
•
•
Troubleshooting MIBs
For general information on MIBs, RMON groups, and traps, refer to the Cisco public MIB directory (http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml). For information on the specific MIBs supported by the Catalyst 4000 family switches, refer to the Catalyst 4000 MIB Support List located at ftp://ftp.cisco.com/pub/mibs/supportlists/cat4000/cat4000-supportlist.html.
Documentation Updates for Release 12.1(19)E
None. This is an E train release.
Documentation Updates for Release 12.1(14)E1
None. This is an E train release.
Documentation Updates for Release 12.1(12c)EW
This section describes updates to the Catalyst 4000 family switch documentation. These updates will be included in the next iteration of the documentation.
Changes
This section describes last-minute changes to the Catalyst 4000 family switch documentation.
Cisco IOS System Message Guide for the Catalyst Family Switch
Error Message C4K_REDUNDANCY-5-CONFIGSYNC:The [char] has been successfully synchronized to the standby supervisorExplanation The configuration has been successfully synchronized to the standby supervisor. [char] can be either private configuration or startup configuration.
Recommended Action This is an informational message. No action is required.
Cisco IOS Command Reference for the Catalyst 4000 Family Switch
•
Examples
This example shows how to display the DHCP snooping binding entries for a switch:
Switch# show ip dhcp snooping bindingMacAddress IP Address Lease (seconds) Type VLAN Interface ----------- ----------- ---------------- ----- ----- ------------ 0000.0100.0201 10.0.0.1 1600 dynamic 100 FastEthernet3/1Switch#This example shows how to display a DHCP snooping binding entries IP address:
Switch# show ip dhcp snooping binding 172.100.101.102MacAddress IP Address Lease (seconds) Type VLAN Interface ----------- ----------- ---------------- ----- ----- ------------ 0000.0100.0201 172.100.101.102 1600 dynamic 100 FastEthernet3/1Switch#This example shows how to display the DHCP snooping binding entries MAC address:
Switch# show ip dhcp snooping binding 55.5.5.2 0002.b33f.3d5fMacAddress IpAddress Lease(sec) Type VLAN Interface------------------ --------------- ---------- ------- ---- --------------------00:02:B3:3F:3D:5F 55.5.5.2 492 dynamic 99 FastEthernet6/36Switch#This example shows how to display the DHCP snooping binding entries MAC address for a specific VLAN:
Switch# show ip dhcp snooping binding 55.5.5.2 0002.b33f.3d5f vlan 99MacAddress IpAddress Lease(sec) Type VLAN Interface------------------ --------------- ---------- ------- ---- --------------------00:02:B3:3F:3D:5F 55.5.5.2 479 dynamic 99 FastEthernet6/36Switch#This example shows how to display dynamic DHCP snooping binding entries:
Switch# show ip dhcp snooping binding dynamicMacAddress IP Address Lease (seconds) Type VLAN Interface ----------- ----------- ---------------- ----- ----- ------------ 0000.0100.0201 10.0.0.1 1600 dynamic 100 FastEthernet3/1Switch#This example shows how to display DHCP snooping binding entries on VLAN 100:
Switch# show ip dhcp snooping binding vlan 100'MacAddress IP Address Lease (seconds) Type VLAN Interface ----------- ----------- ---------------- ----- ----- ------------ 0000.0100.0201 10.0.0.1 1600 dynamic 100 FastEthernet3/1Switch#This example shows how to display DHCP snooping binding entries on Ethernet interface 0/1:
Switch# show ip dhcp snooping binding interface FastEthernet3/1MacAddress IP Address Lease (seconds) Type VLAN Interface ----------- ----------- ---------------- ----- ----- ------------ 0000.0100.0201 10.0.0.1 1600 dynamic 100 FastEthernet3/1Switch#•
Arp-Non-Ipv4; 0x0806 and protocol header of Arp is other than 0x0800
•
Support for this command was introduced on the Catalyst 4000 family switch. (4500 Series only:4503, 4506, and 4507)
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
•
UplinkFast increases the bridge priority to 49,152 and adds 3000 to the spanning tree port cost of all interfaces on the switch, making it unlikely that the switch will become the root switch. The max_update_rate value represents the number of multicast packets transmitted per second (the default is 150 packets per second [pps]).
•
Switch# show ip dhcp snoopingSwitch DHCP snooping is enabled.DHCP Snooping is configured on the following VLANs:10 30-40 100 200-220Insertion of option 82 information is enabled.Interface Trusted Rate limit (pps)--------- ------- ----------------FastEthernet2/1 yes 10FastEthernet3/1 yes noneGigabitEthernet1/1 no 20Switch#Additions
This section lists last-minute additions to the Catalyst 4000 family switch documentation.
Cisco IOS System Message Guide for the Catalyst Family Switch
Error Message C4K_IOSMODPORTMAN-2-INLINEPOWEROFF:Inline power to the switch has been turned offExplanation Software has detected that the passthrough current is disabled. This will cause all phones drawing inline power from the switch to be powered off.
Error Message C4K_IOSMODPORTMAN-4-INLINEPOWERRESTORED:Resuming normal phone operation since inline power has been restoredExplanation The inline power supply to the switch has been restored and normal phone operation will resume.
Error Message C4K_IOSSYSMAN-3-OUTOFPACKETHEADERS:Cannot allocate buffer for a packet headerExplanation The system cannot allocate a buffer for the packet header.
Recommended Action Call Cisco TAC and be ready to provide the configuration information for the switch.
Error Message C4K_SUPERVISOR-2-MUXBUFFERNOTPRESENT:Mux buffer (WS-X4K-MUX) [dec] is not presentExplanation The WS-X4K-MUX line card is either not connected to the backplane properly or is not present. If the line card present in this slot cannot be identified, its SEEPROM cannot be read and it will be unusable.
Recommended Action Return the backplane to Cisco for repair.
Error Message C4K_SUPERVISOR-3-RETIMERDISABLEFAILED:Failed to disable the retimer of the active supervisor's uplink.Explanation The retimer on the active supervisor could not be initialized. In a redundant system, you might see packets transmitted out the active supervisor's non-active uplink. To prevent this, disconnect the second uplink on the active supervisor.
Error Message C4K_SUPERVISOR-3-RETIMERINITFAILED:Failed to initialize the retimer of the active supervisor's uplink.Explanation The retimer on the active supervisor could not be initialized. In a redundant system, you might see packets transmitted out the active supervisor's non-active uplink. To prevent this, disconnect the second uplink on the active supervisor.
Error Message C4K_IOSMODPORTMAN-4-POWERSUPPLYINSERTED:Power Supply [dec] has been insertedExplanation This informational message indicates that the power supply has been inserted. No action is required.
Error Message C4K_IOSMODPORTMAN-4-POWERSUPPLYREMOVED:Power Supply [dec] has been removedExplanation This informational message indicates that the power supply has been removed. No action is required.
Error Message C4K_REDUNDANCY-5-CONFIGSYNC_RATELIMIT:The [char] has been successfully synchronized to the standby supervisorExplanation The configuration has been successfully synchronized to the standby supervisor. This is a rate limited message. These messages are logged at 1 minute intervals, rather than continuously as with many other messages.
Recommended Action This is an informational message. No action is required.
Error Message C4K_SUPERVISOR-4-OTHERSUPERVISORACTIVEDEBOUNCE:Other supervisor is still holding hardware lockExplanation This condition is detected when the redundancy register incorrectly indicates that the other supervisor is holding a lock, and is probably caused by hardware signal latency. Unless there is a real hardware failure, the switch will automatically recover from this state. If there is a persistent hardware failure this message will appear four times.
Error Message C4K_COMMONHWACLMAN-4-FAILEDTOSWITCHPORTTAGS:Failed to switch port tags, old tag: [object-info] new tag: [object-info]. Software paths: [dec] Hardware paths: [dec]Explanation Software failed to switch tags. This could be a transient error. The ACL that we were trying to configure will not become active.
Recommended Action Detaching and attaching ACLs (and policies) again might solve the problem.
Error Message C4K_COMMONHWACLMAN-4-FAILEDTOSWITCHVLANTAGS:Failed to switch vlan tags, old tag: [object-info] new tag: [object-info]. Software paths: [dec] Hardware paths: [dec]Explanation Software failed to switch tags. This could be a transient error. The ACL that you were trying to configure will not become active.
Recommended Action Detaching and attaching ACLs (and policies) might solve the problem.
Cisco IOS Command Reference for the Catalyst 4000 Family Switch
•
–
–
–
–
–
•
–
–
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
•
Note: VLAN maps do not filter IPv4 ARP packets.
•
This example shows how to create and display an access list named mac1, denying only EtherType DECnet Phase IV traffic, but permitting all other types of traffic.
Switch(config)# mac access-list extended mac1Switch(config-ext-macl)# deny any any decnet-iv (old) protocol-family decnet (new)Switch(config-ext-macl)# permit any anySwitch(config-ext-macl)# endSwitch # show access-listsExtended MAC access list mac1deny any any decnet-iv (old) protocol-family decnet (new)permit any anyDeletions
This section describes last-minute deletions to the Catalyst 4000 family switch documentation.
Cisco IOS System Message Guide for the Catalyst Family Switch
Error Message C4K_IOSSYSMAN-3-OUTOFPRIVATEPOOLPACKETS:Cannot allocate Gsg packet buffer (probably packet leak)Cisco IOS Command Reference for the Catalyst 4000 Family Switch
•
ArpIpv4 - 0x0806 and protocol header of Arp is 0x0800(Ipv4)
Cisco IOS Software Configuration Guide for the Catalyst 4000 Family Switch
•
–
–
Related Documentation
Although their Release Notes are unique, the 4 platforms (Catalyst 4500, Catalyst 4900, Catalyst ME 4900, and Catalyst 4900M) use the same Software Configuration Guide, Command Reference Guide, and System Message Guide. Refer to the following home pages for additional information:
•
http://www.cisco.com/go/cat4500/docs
•
m
•
http://www.cisco.com/en/US/products/ps7009/tsd_products_support_series_home.html
Hardware Documents
Installation guides and notes including specifications and relevant safety information are available at the following URLs:
•
•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_installation_guides_list.html
•
http://www.cisco.com/en/US/products/ps6021/prod_installation_guides_list.html
•
http://www.cisco.com/en/US/products/ps7009/prod_installation_guides_list.html
Software Documentation
Software release notes, configuration guides, command references, and system message guides are available at the following URLs:
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_release_notes_list.html
•
http://www.cisco.com/en/US/products/ps6021/prod_release_notes_list.html
•
http://www.cisco.com/en/US/docs/switches/lan/catalyst4500/release/note/OL_11511.html
Software documents for the Catalyst 4500 Classic, Catalyst 4500 E-Series, Catalyst 4900, and
Cisco ME 4900 Series Ethernet Switches are available at the following URLs:•
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_command_reference_list.html
•
http://www.cisco.com/en/US/products/hw/switches/ps4324/products_system_message_guides_list.html
Cisco IOS Documentation
Platform-independent Cisco IOS documentation may also apply to the Catalyst 4500 and 4900 switches. These documents are available at the following URLs:
•
http://www.cisco.com/en/US/products/ps6350/products_installation_and_configuration_guides_list.html
•
http://www.cisco.com/en/US/products/ps6350/prod_command_reference_list.html
You can also use the Command Lookup Tool at:
http://tools.cisco.com/Support/CLILookup/cltSearchAction.do
•
http://www.cisco.com/en/US/products/ps6350/products_system_message_guides_list.html
You can also use the Error Message Decoder tool at:
http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi
•
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.1(19)E
Copyright © 1999-2003, Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)
This Document Applies to These Products
- Collaboration Endpoints - Retired Products
- Conferencing - Retired Products
- Contact Center - Retired Products
- Optical Networking - Retired Products
- Routers - Retired Products
- Security - Retired Products
- Servers - Unified Computing (UCS) Retired Products
- Storage Networking Retired Products
- Switches - Retired Products
- Video - Retired Products
- Wireless - Retired Products