Release Notes for the Catalyst 4500 Series Switch, Cisco IOS, 12.2(46)SG1
Available Languages
Table Of Contents
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.2(46)SG1
Cisco IOS Software Packaging for the Cisco Catalyst 4500 Series
Catalyst 4500 Series Switch Cisco IOS Release Strategy
Cisco IOS Software Migration Guide
Supported Hardware on Catalyst 4500 Series Switch
Supported Hardware on Catalyst 4500 E-Series Switch
Supported Features on the Catalyst 4500 Series Switch
New Hardware Features in Release 12.2(46)SG1
New Software Features in Release 12.2(46)SG1
Guidelines for Upgrading the ROMMON
Upgrading the Supervisor Engine ROMMON from the Console
Upgrading the Supervisor Engine ROMMON Remotely Using Telnet
Upgrading the Cisco IOS Software
For Features on the LAN Base Image
Open Caveats in Cisco IOS Release 12.2(46)SG1
Resolved Caveats in Cisco IOS Release 12.2(46)SG1
Open Caveats in Cisco IOS Release 12.2(46)SG
Resolved Caveats in Cisco IOS Release 12.2(46)SG
Troubleshooting at the System Level
Obtaining Documentation and Submitting a Service Request
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.2(46)SG1
Current Release
12.2(46)SG1—Sept 15, 2008Previous Releases
12.2(46)SGThese 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 Cisco IOS Release 12.2(46)SG1.
The most current software release is Cisco IOS Release 12.2(46)SG1. The most current release notes for this release is available on Cisco.com at this URL:
http://www.cisco.com/en/US/products/hw/switches/ps4324/prod_release_note09186a00801f5b1e.html
Note
Although their Release Notes are unique, the 3 platforms (Catalyst 4500, Catalyst 4900 and Catalyst 4900M), use the same Software Configuration Guide, Command Reference Guide, and System Message Guide. Refer to this location:
http://www.cisco.com/go/cat4500/docs
Contents
This publication consists of these sections:
•
•
•
•
Cisco IOS Software Packaging for the Cisco Catalyst 4500 Series
A new Cisco IOS Software package for Cisco Catalyst 4500 Series Switches was introduced in Cisco IOS Software Release 12.2(25)SG . It is a new foundation for features and functionality and provides consistency across all Cisco Catalyst switches. The new Cisco IOS Software release train is designated as 12.2SG.
Cisco IOS Release 12.2(46)SG1 introduces a new LAN Base Software image and an IP upgrade image. These will complement the existing IP Base and Enterprise Services images. The LAN base image is supported on the Supervisor II-Plus-10GE only. It is primarily focused on customers Layer 2 requirements and therefore many of the IP Base features have been removed. If at a later date some of the features are required, the IP upgrade image is available.
The LAN Base image will not support the following features currently offered in the IP Base image ,10Gig Uplinks, FHRP(HSRP/VRRP), GLBP, WCCP, L2PT & QinQ, Netflow, Auto QoS,EIGRP Stub, PIM SM/DM, MLD Snooping, Flex Link, PVST+, RPVST+, EPoE/PoE+, EEM, TDR, SSO,ISSU, CTS and Smartports (Role based Macros).
Orderable Product Numbers:
•
•
•
•
•
•
•
•
Catalyst 4500 Series Switch Cisco IOS Release Strategy
Note
Cisco IOS Release 12.2SG train offers the latest features for the Catalyst 4500 Series supervisor engines. Customers with Catalyst 4500 Series supervisor engines who need the latest hardware support and software features should migrate to Cisco IOS Release 12.2(46)SG.
Note
Catalyst 4500 Series has two maintenance trains. The Cisco IOS Release 12.2(25)EW train is the most stable train but only has features found in the Cisco IOS Release 12.2(25)EW. The
Cisco IOS Release 12.2(31)SG train has more recent features including support for the WS-X4013+10GE supervisor engine. Currently, the Cisco IOS Release 12.2(31)SGA7 is the recommended release for customers desiring a release with a maintenance train.For more information on the Catalyst 4500 series switches, visit the following URL:
www.cisco.com/univercd/cc/td/doc/product/lan/cat4000/index.htmCisco IOS Software Migration Guide
Note
Figure 1 displays the Cisco IOS Software Release 12.2(46)SG plan relative to the 12.2S release train and identifies the recommended migration path. Note that 12.2(44)SG will not be the base release for a new maintenance train. Currently, the Cisco Catalyst 4500 platform has two active maintenance trains: 12.2(25)EWA and 12.2(31)SGA.
Figure 1 Software Release Strategy for the Catalyst 4500 Series Switch
Summary of Migration Plan
Note
•
•
•
System Requirements
This section describes the system requirements:
•
•
Supported Hardware on Catalyst 4500 Series Switch
Note
Table 1 lists the hardware supported on the Catalyst 4500 Series Switch.
Table 1 Supported Hardware
WS-X4013+10GE
Catalyst 4500 series switch Supervisor Engine II-Plus-10GE
12.2(25)SG
WS-X4302-GB
2-port 1000BASE-X (GBIC) Gigabit Ethernet module
12.1(19)EW
WS-X4306-GB
6-port 1000BASE-X (GBIC) Gigabit Ethernet switching module
12.1(8a)EW
WS-X4418-GB
18-port 1000BASE-X (GBIC) Gigabit Ethernet server switching module
12.1(8a)EW
WS-X4412-2GB-T
12-port 1000BASE-T Gigabit Ethernet and 2-GBIC ports switching module
12.1(8a)EW
WS-X4424-GB-RJ45
24-port 10/100/1000BASE-T Gigabit Ethernet RJ-45 switching module
12.1(8a)EW
WS-X4448-GB-LX
48-port 1000BASE-LX (small form-factor pluggable) Gigabit Ethernet fiber optic interface switching module
12.1(8a)EW
WS-X4448-GB-RJ45
48-port 10/100/1000BASE-T Gigabit Ethernet switching module
12.1(8a)EW
WS-X4448-GB-SFP
48-port 1000BASE-X (small form-factor pluggable) module
12.2(20)EW
WS-X4506-GB-T
6-port Alternately-Wired 10/100/1000BASE-T Catalyst 4500 series Power over Ethernet (PoE) 802.3af or 1000BASE-X SFP
12.2(20)EWA
WS-X4524-GB-RJ45V
24-port 10/100/1000BASE-T RJ-45 Catalyst 4500 series PoE 802.3af
12.2(18)EW
WS-X4548-GB-RJ45
48-port 10/100/1000BASE-T Gigabit Ethernet module
12.1(19)EW
WS-X4548-GB-RJ45V
48-port 10/100/1000BASE-T RJ-45 Catalyst 4500 series PoE 802.3af
12.2(18)EW
WS-X4124-FX-MT
24-port 100BASE-FX Fast Ethernet MT-RJ multimode fiber switching module
12.1(8a)EW
WS-X4148-FX-MT
48-port 100BASE-FX Fast Ethernet MT-RJ multimode fiber switching module
12.1(8a)EW
WS-X4148-FE-LX-MT
48-port 100BASE-LX10 Fast Ethernet MT-RJ single-mode fiber switching module
12.1(13)EW
WS-X4148-FE-BD-LC
48-port 100BASE-BX10-D module
12.2(18)EW
WS-X4248-FE-SFP
48-port 100BASE-X SFP switching module
12.2(25)SG
WS-U4504-FX-MT
4-port 100BASE-FX (MT-RF) uplink daughter card
12.1(8a)EW
WS-X4124-RJ45
24-port 10/100 RJ-45 module
12.2(20)EW
WS-X4148-RJ
48-port 10/100 RJ-45 switching module
12.1(8a)EW
WS-X4148-RJ21
48-port 10/100 4xRJ-21 (telco connector) switching module
12.1(8a)EW
WS-X4148-RJ45V
48-port Pre-standard PoE 10/100BASE-T switching module
12.1(8a)EW for data support
12.1(11b)EW for data and inline power support
WS-X4224-RJ45V
24-port 10/100BASE-TX RJ-45 Cisco Catalyst 4500 series PoE 802.3af
12.2(20)EW
WS-X4232-GB-RJ
32-port 10/100 Fast Ethernet RJ-45, plus 2-port 1000BASE-X (GBIC) Gigabit Ethernet switching module
12.1(8a)EW
WS-X4248-RJ45V
48-port 10/100BASE-T RJ-45 Cisco Catalyst 4500 series PoE 802.3af
12.2(18)EW
WS-X4248-RJ21V
48-port 10/100 Fast Ethernet RJ-21 Cisco Catalyst 4500 series PoE 802.3af telco
12.2(18)EW
WS-X4232-RJ-XX
32-port 10/100 Fast Ethernet RJ-45 modular uplink switching module
12.1(8a)EW
GLC-FE-100FX
100BASE-FX, 1310 nm wavelength, 2 km over MMF
12.2(25)SG
GLC-FE-100LX
100BASE-LX, 1310 nm wavelength, 10 km over SMF
12.2(25)SG
GLC-FE-100BX-D
100BASE-BX10-D, 1550 nm TX/1310 nm RX wavelength
12.2(25)SG
GLC-FE-100BX-U
100BASE-BX10-U, 1310 nm TX/1550 nm RX wavelength
12.2(25)SG
GLC-BX-D
1000BASE-BX10-D small form-factor pluggable module
For DOM support, see Table 5.12.2(20)EWA
GLC-BX-U
1000BASE-BX10-U small form-factor pluggable module
For DOM support, see Table 5.bv12.2(20)EWA
GLC-SX-MM
1000BASE-SX small form-factor pluggable module
12.2(20)EW
GLC-LH-SM
1000BASE-LX/LH small form-factor pluggable module
12.2(20)EW
GLC-ZX-SM
1000BASE-ZX small form-factor pluggable module
12.2(20)EW
GLC-T
1000BASE-T small form-factor pluggable module
12.2(20)EW
CWDM-SFP-xxxx
CWDM small form-factor pluggable module (See Table 2 for a list of supported wavelengths.)
For DOM support, see Table 5.12.2(20)EW
X2-10GB-LR
10GBASE-LR X2 transceiver module for SMF, 1310-nm wavelength, SC duplex connector
12.2(25)EW
X2-10GB-ER
10GBASE-ER X2 transceiver module for SMF, 1550-nm wavelength, SC duplex connector
12.2(25)EWA
X2-10GB-CX4
10GBASE-CX4 X2 transceiver module for CX4 cable, copper, Infiniband 4X connector
12.2(25)EWA
X2-10GB-LX4
10GBASE-LX4 X2 transceiver module for MMF, 1310-nm wavelength, SC duplex connector
12.2(25)EWA
X2-10GB-LRM
10GBASE-LRM X2 transceiver module for MMF, 1310-nm wavelength, SC duplex connector
12.2(31)SGA
X2-10GB-SR
10GBASE-SR X2 transceiver module for MMF, 850-nm wavelength, SC duplex connector
12.2(25)EWA
WS-G5483=
1000BASE-T GBIC
12.1(13)EW
WS-G5484
1000BASE-SX short wavelength GBIC (multimode only)
12.1(8a)EW
WS-G5486
1000BASE-LX/LH long-haul GBIC (single mode or multimode)
12.1(8a)EW
WS-G5487
1000BASE-ZX extended reach GBIC (single-handed)
12.1(8a)EW
CWDM-GBIC-xxxx
CWDM gigabit interface converter (See Table 2 for a list of supported wavelengths.)
12.1(12c)EW
DWDM-GBIC-xx.yy
Dense Wavelength-Division Multiplexing ITU 100-Ghz grid 15xx.yy nm GBIC.
For DOM support, see Table 5.12.1(19)EW
WDM-GBIC-REC
Receive-only 1000BASE-WDM GBIC
12.1(19)EW
MEM-C4K-FLD64M
Catalyst 4500 series switch CompactFlash, 64 MB Option
12.1(8a)EW
MEM-C4K-FLD128M
Catalyst 4500 series switch CompactFlash, 128 MB Option
12.1(8a)EW
WS-X4590=
Catalyst 4500 series switch Fabric Redundancy Modules
12.2(18)EW
PWR-C45-1000AC
Catalyst 4500 series switch 1000 Watt AC power supply for chassis 4503, 4506, and 4507R (data only)
12.1(12c)EW
PWR-C45-1400DC
Catalyst 4500 series switch 1400 Watt DC triple input power supply (data-only)
12.2(25)EW
PWR-C45-1400DC-P
Catalyst 4500 series switch 1400 Watt DC power supply with integrated PEM
12.1(19)EW
PWR-C45-1400AC
Catalyst 4500 series switch 1400 Watt AC power supply (data-only)
12.1(12c)EW
PWR-C45-1300ACV
Catalyst 4500 series switch 1300 Watt AC power supply with integrated voice for chassis 4503, 4506, and 4507R
12.1(12c)EW
PWR-C45-2800ACV
Catalyst 4500 series switch 2800 Watt AC power supply with integrated voice (data and PoE) for chassis 4503, 4506, and 4507R
12.1(12c)EW
PWR-C45-4200ACV
Catalyst 4500 series switch 4200 Watt AC dual input power supply with integrated voice (data and PoE)
12.2(25)EWA5
WS-P4502-1PSU
Catalyst 4500 series switch auxiliary power shelf (25-slot), including one PWR-4502
12.1(19)EW
PWR-4502
Catalyst 4500 series switch auxiliary power shelf redundant power supply
12.1(19)EW
Table 2 briefly describes the supported wavelengths in the Catalyst 4500 Classic Series Switch.
Table 3 briefly describes the seven chassis in the Catalyst 4500 Series Switch. For the chassis listed in the table, refer to Table 4 for software release information.
Table 4 lists the software release information for the Catalyst 4500 Series Switch supervisor engines.
Note
Table 5 DOM Support on the Catalyst 4500 Series Switch
GLC-BX-D
12.2(20)EWA
GLC-BX-U
12.2(20)EWA
DWDM GBIC
12.1(19)EW
CWDM SFP
12.2(20)EWA
Supported Hardware on Catalyst 4500 E-Series Switch
Note
For the chassis listed in the table, refer to Table 6 for software release information.
Supported Features on the Catalyst 4500 Series Switch
Except for the features listed in Table 7, the LAN Base image supports all the features supported on the IP Base image. For details on those features, see the
Catalyst 4500 Series Switch Software Configuration Guide, Cisco IOS Release 12.2(46).
Unsupported Features
The following features are not supported in Cisco IOS Release 12.2(46)SG1 for the Catalyst 4500 series switches:
•
–
–
–
–
•
•
•
•
–
•
•
•
•
•
•
•
•
•
•
•
•
•
•
New and Changed Information
These sections describe the new and changed information for the Catalyst 4500 series switch running Cisco IOS software:
•
•
New Hardware Features in Release 12.2(46)SG1
Release 12.2(46)SG1 provides the following new hardware for the Catalyst 4500 series switch:
•
New Software Features in Release 12.2(46)SG1
Cisco IOS Release 12.2(46)SG1 introduces the LAN Base and IP upgrade images:
•
•
•
•
•
•
•
•
Cisco IOS Release 12.2(46)SG1 is a rebuild of Release 12.2(46)SG.
Upgrading the System Software
In most cases, upgrading the switch to a newer release of Cisco IOS software does not require a ROMMON upgrade. However, if you are running an early release of Cisco IOS software and plan to upgrade, refer to the following tables for the minimum Cisco IOS image and the recommended ROMMON release, respectively.
Caution
The following sections describe how to upgrade your switch software:
•
•
•
•
Guidelines for Upgrading the ROMMON
Caution
Upgrading the Supervisor Engine ROMMON from the Console
Caution
Note
Follow this procedure to upgrade your supervisor engine ROMMON:
Step 1
Note
Step 2
The cat4000-ios-promupgrade-121_20r_EW1 programs are available on Cisco.com at the same location from which you download Catalyst 4000 system images.
Step 3
squeeze bootflash: command to reclaim the space.If you are using a CompactFlash card, replace bootflash: with slot0:.
Step 4
The following example shows how to download the PROM upgrade image cat4000-ios-promupgrade-121_20r_EW1 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-ios-promupgrade-121_20r_EW1]? Destination filename [cat4000-ios-promupgrade-121_20r_EW1]? Accessing tftp://172.20.58.78/cat4000-ios-promupgrade-121_20r_EW1... Loading cat4000-ios-promupgrade-121_20r_EW1 from 172.20.58.78 (viaFastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 455620 bytes]455620 bytes copied in 2.644 secs (172322 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-X4515 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Rom Monitor Program Version 12.1(12r)EW..(output truncated).Established physical link 100MB Half DuplexNetwork layer connectivity may take a few secondsrommon 1 >Step 6
boot bootflash:cat4000-ios-promupgrade-121_20r_EW1
Caution
The following example shows the output from a successful upgrade, followed by a system reset:
rommon 2 > boot bootflash:cat4000-ios-promupgrade-121_20r_EW1*********************************************************** ** Rom Monitor Upgrade Utility For WS-X4515 System ** This upgrades flash Rom Monitor image to the latest ** ** Copyright (c) 2002, 2003 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Image size = 314.236 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 (0x4e8ec 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 15Step 7
Step 8
The following example shows how to delete the cat4000-ios-promupgrade-121_20r_EW1 image from bootflash and reclaim unused space:
Switch# delete bootflash:cat4000-ios-promupgrade-121_20r_EW1Switch# squeeze bootflash:All deleted files will be removed, proceed (y/n) [n]? ySqueeze operation may take some time, proceed (y/n) [n]? ySwitch#Step 9
Switch#show versionCisco Internetwork Operating System SoftwareIOS (tm) Catalyst 4500 L3 Switch Software (cat4500-I9S-M), Version 12.1(20)EW, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 1986-2003 by cisco Systems, Inc.Compiled Wed 22-Oct-03 23:42 by kellmillImage text-base: 0x00000000, data-base: 0x00F56DDCROM: 12.1(20r)EW1Dagobah Revision 86, Swamp Revision 28Switch uptime is 0 day, 0 hour, 5 minutesSystem returned to ROM by reloadSystem image file is "bootflash:cat4500-i9s-mz.121-20.EW1"cisco WS-C4503 (XPC8245) processor (revision 7) with 524288K bytes of memory.Processor board ID FOX06460YD8Last reset from Reload3 Ethernet/IEEE 802.3 interface(s)51 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)403K bytes of non-volatile configuration memory.Configuration register is 0x2102Switch#
The ROMMON has now been upgraded.
See the "Upgrading the Cisco IOS Software" section for instructions on how to upgrade the Cisco IOS software on your switch.
Upgrading the Supervisor Engine ROMMON Remotely Using Telnet
Caution
Follow this procedure to upgrade your supervisor engine ROMMON to Release 12.1(20r)EW1. This procedure can be used when console access is not available and when the ROMMON upgrade must be performed remotely.
Note
Step 1
Note
Step 2
The cat4000-ios-promupgrade-121_20r_EW1 programs are available on Cisco.com at the same location from which you download Catalyst 4500 system images.
Step 3
squeeze bootflash: command to reclaim the space.If you are using a CompactFlash card, replace bootflash: with slot0:.
Step 4
copy tftp command.The following example shows how to download the PROM upgrade image cat4000-ios-promupgrade-121_20r_EW1 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-ios-promupgrade-121_20r_EW1]? Destination filename [cat4000-ios-promupgrade-121_20r_EW1]? Accessing tftp://172.20.58.78/cat4000-ios-promupgrade-121_20r_EW1... Loading cat4000-ios-promupgrade-121_20r_EW1 from 172.20.58.78 (viaFastEthernet2/1):!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! [OK - 455620 bytes]455620 bytes copied in 2.644 secs (172322 bytes/sec) Switch#Step 5
Switch# configure terminalSwitch(config)# no boot system flash bootflash:cat4000-i5s-mz.121-19.EW1.binSwitch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Use the boot system flash bootflash:file_name command to set the BOOT variable. You will use two BOOT commands: one to upgrade the ROMMON and a second to load the Cisco IOS software image after the ROMMON upgrade is complete. Notice the order of the BOOT variables in the example below. At bootup the first BOOT variable command upgrades the ROMMON. When the upgrade is complete the supervisor engine will autoboot, and the second BOOT variable command will load the Cisco IOS software image specified by the second BOOT command.
Note
In this example, we assume that the console port baud rate is set to 9600 bps and that the config-register is set to 0x0102.Use the config-register command to autoboot using image(s) specified by the BOOT variable. Configure the BOOT variable to upgrade the ROMMON and then autoboot the IOS image after the ROMMON upgrade is complete. In this example, we are upgrading the ROMMON to version 12.1(20r)EW1. After the ROMMON upgrade is complete, the supervisor engine will boot Cisco IOS software Release 12.1(20)EW1.config-register to 0x0102.Switch# configure terminalSwitch(config)# boot system flash bootflash:cat4000-ios-promupgrade-121_20r_EW1Switch(config)# boot system flash bootflash:cat4000-i9s-mz.121-20.EW1Switch(config)# config-register 0x0102Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Step 6
Switch#sh bootvarBOOT variable = bootflash:cat4000-ios-promupgrade-121_20r_EW1,1;bootflash:cat4000-i9s-mz.121-20.EW1,1CONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x2102Step 7
Caution
The following example shows the console port output from a successful ROMMON upgrade followed by a system reset. Your Telnet session is disconnected during the ROMMON upgrade, so you will not see this output. This step could take 2-3 minutes to complete. You will need to reconnect your Telnet session after 2-3 minutes when the Cisco IOS software image and the interfaces are loaded.
Switch#reloadProceed with reload? [confirm]1d05h: %SYS-5-RELOAD: Reload requested*********************************************************** ** Welcome to Rom Monitor for WS-X4515 System. ** Copyright (c) 2002 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Rom Monitor Program Version 12.1(12r)EWBoard type 2, Board revision 7Swamp FPGA revision 28, Dagobah FPGA revision 86***** The system will autoboot in 5 seconds *****Type control-C to prevent autobooting.. . . . .Established physical link 100MB Full DuplexNetwork layer connectivity may take a few seconds******** The system will autoboot now ********config-register = 0x0102Autobooting using BOOT variable specified file.....Current BOOT file is --- bootflash:cat4000-ios-promupgrade-121_20r_EW1*********************************************************** ** Rom Monitor Upgrade Utility For WS-X4515 System ** This upgrades flash Rom Monitor image to the latest ** ** Copyright (c) 2002, 2003 by Cisco Systems, Inc. ** All rights reserved. ** ***********************************************************Image size = 314.236 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 (0x4e8ec 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..(output truncated).******** The system will autoboot now ********config-register = 0x0102Autobooting using BOOT variable specified file.....Current BOOT file is --- bootflash:cat4000-i9s-mz.121-20.EW1Rommon reg: 0x56000380Running IOS...Decompressing the image#################################################################################################################################################################################################################################################################################################################################################################################################################################################################################### [OK]Step 8
Switch# configure terminalSwitch(config)# no boot system flash bootflash:cat4000-ios-promupgrade-121_20r_EW1Switch(config)# exitSwitch# writeBuilding configuration...Compressed configuration from 3641 to 1244 bytes [OK]Switch#Step 9
Switch#show versionCisco Internetwork Operating System SoftwareIOS (tm) Catalyst 4000 L3 Switch Software (cat4000-I9S-M), Version 12.1(20)EW, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)TAC Support: http://www.cisco.com/tacCopyright (c) 1986-2003 by cisco Systems, Inc.Compiled Wed 22-Oct-03 23:42 by kellmillImage text-base: 0x00000000, data-base: 0x00F56DDCROM: 12.1(20r)EW1Dagobah Revision 86, Swamp Revision 28Switch uptime is 0 day, 0 hour, 5 minutesSystem returned to ROM by reloadSystem image file is "bootflash:cat4000-i9s-mz.121-20.EW1"cisco WS-C4503 (XPC8245) processor (revision 7) with 524288K bytes of memory.Processor board ID FOX06460YD8Last reset from Reload3 Ethernet/IEEE 802.3 interface(s)51 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)403K bytes of non-volatile configuration memory.Configuration register is 0x0102Switch#Step 10
The following example shows how to delete the cat4000-ios-promupgrade-121_20r_EW1 image from bootflash and reclaim unused space:
Switch# delete bootflash:cat4000-ios-promupgrade-121_20r_EW1Switch# squeeze bootflash:All deleted files will be removed, proceed (y/n) [n]? ySqueeze operation may take some time, proceed (y/n) [n]? ySwitch#Step 11
Switch#sh bootvarBOOT variable = bootflash:cat4000-i9s-mz.121-20.EW1,1CONFIG_FILE variable does not existBOOTLDR variable does not existConfiguration register is 0x0102
The ROMMON has now been upgraded.
See the "Upgrading the Cisco IOS Software" section for instructions on how to upgrade the Cisco IOS software on your switch.
Upgrading the Cisco IOS Software
Caution
Before you proceed, observe the following rules for hostname:
•
Uppercase and lowercase characters look the same to many internet software applications. It may seem appropriate to capitalize a name the same way you might do in English, but conventions dictate that computer names appear all lowercase. For more information, refer to RFC 1178, Choosing a Name for Your Computer.
•
•
•
•
To upgrade the Cisco IOS software on your Catalyst 4500 series switch, use this procedure:
Step 1
Step 2
If you are using a CompactFlash card, use slot0: instead of bootflash.
Step 3
The following example shows how to download the Cisco IOS software image cat4000-is-mz.121-12c.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-is-mz121_12c.EW]?Destination filename [cat4000-is-mz.121-12c.EW]?Accessing tftp://172.20.58.78/cat4000-is-mz.121-12c.EW...Loading cat4000-is-mz.121-12c.EW 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 flash bootflash:cat4000-is-mz.121-8a.EWSwitch(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-12c.EW image to the BOOT variable:
Switch# configure terminalSwitch(config)# boot system flash bootflash:cat4000-is-mz.121-12c.EWSwitch(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)# config-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# reloadRommon 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 software on the Catalyst 4500 series switch:
•
–
–
–
•
–
–
–
–
•
–
–
–
•
–
–
–
–
•
–
–
–
•
–
–
–
•
•
spanning-tree link-type point-to-point.•
Workaround: None
•
•
•
•
•
•
•
•
For example, if the active supervisor engine is in slot 1, and you have configured interface Gig 1/1, the supervisor engine in slot 2 becomes active if you remove the active supervisor engine from the chassis. In addition, while the startup configuration file is being parsed, you will receive an error message indicating that interface GE1/1 is no longer present. This behavior is correct. When the formerly active supervisor engine is reinserted into slot 1, there is no configuration for interface Gig 1/1.
This situation will not occur when both supervisor engines are physically in the chassis.
Workaround: Copy the startup configuration file into the running configuration:
Switch# copy startup-config running-config•
Workaround: Because the problem is caused by mismatched MTUs, the solution is to change the MTU on either router to match the other's MTU.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Workaround: Remove and reinsert the standby supervisor after the active supervisor boots. (CSCsa66509)
•
•
switchport private-vlan mapping trunk command above is 500. For example, one thousand secondary VLANs could map to one primary VLAN, or one thousand secondary VLANs could map one to one to one thousand primary VLANs.•
PoE switching modules:
–
–
–
–
–
–
PoE enabled power supplies:
–
–
–
–
–
•
•
•
•
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, verify that the switch is connected to the ACS. You should also ensure that the switch has been properly configured as an AAA client on the ACS.
•
•
Workaround: Disable idle timeouts. (CSCec30214)
•
Workarounds:
1. Disable inline power on the switch ports using the power inline never command.
2. Configure the media converter to autonegotiate the speed and duplex instead of running them at 100 Mbps and full duplex. (CSCee62109)
•
–
–
•
•
•
•
•
•
–
–
•
–
–
–
–
•
•
Because CPP implementation is tightly integrated between IOS and platform code, an error message will always appear during boot-up and CPP will not be applied when you downgrade IOS software from a version where this caveat is integrated to a previous release (where this fix is not present):
%Invalid control plane policy-map; Please unconfigure policy-map attached to control-plane, and associated class-maps, and execute config command "macro global apply system-cpp" error: failed to install policy map system-cpp-policyWorkaround:
1. Backup your configuration when downgrading software.
2. Remove all CPP entries manually from the configuration and then re-apply the
macro global apply system-cpp command.This caveat should not affect your system while you upgrade between releases (CSCsh45714).
•
–
–
–
–
To maximize the 10/100/1000 port density of 7- and 10-slot chassis when using redundant Supervisor engine 6-E, install WS-X4548-GB-RJ45 linecards instead of WS-X4448-GB-RJ45 line cards. If WS-X4448-GB-RJ45 line cards are required, two options are available:
Option 1
Only four linecard slots can be used on the Catalyst 4507R and six line card slots on the
Catalyst 4510R chassis.Option 2
When all slots are required, only one model WS-X4448-GB-RJ45 line card can be used.
To maximize the 100-BASE-FX port density of 7 and 10 slot chassis when using Supervisor engine 6-E install WS-4248-FE-SFP line cards with FX optics instead of WS-X4148-FX-MT line cards. If WS-X4148-FX-MT line cards are required two options are available.
Option 1
Only 4 linecard slots can be used on the Cat4507R and 6 line card slots on the Cat4510R chassis.
Option 2
When all slots are required only one WS-X4448-GB-RJ45 line card can be used.
•
% Hardware MTU table exhaustedIn such a scenario, the ipv6 MTU value programmed in hardware is different from the ipv6 interface MTU value. This will happen if there is no room in the hardware MTU table to store additional values.
You must make room in the table by unconfiguring some unused MTU values and subsequently disable/re-enable ipv6 on the interface or reappling the MTU configuration.
•
Switch(config-if)# no ip verify sourceSwitch(config-if)# no ip device tracking max"To enable IPSG with static hosts on a port, enter the following commands:
Switch(config)# ip device tracking ****enable IP device tracking globallySwitch(config)# ip device tracking max <n> ***set an IP device tracking maximum on intSwitch(config-if)# ip verify source tracking [port-security] ****activate IPSG on port
Caution
Note
•
•
For Features on the LAN Base Image
Caveats
Note
Caveats describe unexpected behavior in Cisco IOS releases. Caveats listed as open in a prior release are carried forward to the next release as either open or resolved.
Note
http://www.cisco.com/univercd/cc/td/doc/product/software/ios124/124relnt/124cavs/124mcavs.htm
Note
http://www.cisco.com/en/US/products/products_security_advisories_listing.html
Open Caveats in Cisco IOS Release 12.2(46)SG1
This section lists the open caveats in Cisco IOS Release 12.2(46)SG1:
•
Resolved Caveats in Cisco IOS Release 12.2(46)SG1
This section lists the open caveats in Cisco IOS Release 12.2(46)SG1:
•
Open Caveats in Cisco IOS Release 12.2(46)SG
This section lists the open caveats in Cisco IOS Release 12.2(46)SG:
•
000099: Jul 9 01:22:36.478 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000100: Jul 9 01:22:46.534 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000101: Jul 9 01:22:56.566 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000102: Jul 9 01:23:06.598 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000103: Jul 9 01:23:16.642 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000104: Jul 9 01:23:26.682 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000105: Jul 9 01:23:36.721 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000106: Jul 9 01:23:46.777 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standby000107: Jul 9 01:23:56.793 PDT: %HA_CONFIG_SYNC-3-LBL_CFGSYNC: Unable to sync config-changed command to standbyWorkaround: When using the access-list N permit host hostname command, specify the IP address of the host rather than the hostname (CSCef67489)
•
show policy-map interface fa6/1 do not show the packets being matched:clearwater# show policy-map intFastEthernet3/2Service-policy output: p1Class-map: c1 (match-all)0 packets <--------It stays at '0' despite of traffic being receivedMatch: access-group name fnacl21police: Per-interfaceConform: 9426560 bytes Exceed: 16573440 bytesWorkaround: Verify that the MAC addresses being transmitted through the system are learned.
(CSCef01798)
•
Workaround: None. (CSCeg48586)
•
–
–
On a switch that support redundancy, the generation of the self-signed certificate is performed independently on the active and the standby supervisor engines. So, the certificates differ. After switchover, the HTTP client that holds the old certificate can not connect to the HTTPS server.
Workaround: Re-connect. (CSCsb11964)
•
This only affects a switch that has any of the following queues are configured as SPAN source in releases prior to 12.2(31)SG and saved to startup-config. The SPAN destination would not get the same traffic after upgrading to 12.2(31)SG.
Workaround: After upgrading to 12.2(31)SG and later releases, remove the old SPAN source configuration and reconfigure with the new queue names/IDs. For example:
Switch(config)# no monitor session n source cpu queue all rxSwitch(config)# monitor session n source cpu queue <new_Queue_Name>(CSCsc94802)
•
Workaround: None. (CSCsc11726)
•
This could occur for these reasons:
–
–
Workarounds:
–
–
•
qos account layer2 encapsulation.Workaround: None. (CSCsg58526)
•
This does not affect performance.
Workaround: Enter the no shutdown command. (CSCsg27395)
•
Workaround: Upgrade to Cisco IOS Release 12.2(31)SG or later and resize the TCAM with the
access-list hardware region balance command to support the ACL Verify TCAM utilization with the show platform hardware acl statistics utilization brief command. (CSCse50565)•
Workaround: Remove the transceiver from the new port and place it in the old port. After the SFP is recognized in the old port, remove it slowly and insert it in the new port. (CSCse34693).
•
Workaround: None. (CSCsj83688)
•
Problem is not observed if the phone is a stand alone device.
Workarounds: Powercycle the Cisco IP phone. (CSCsk81297)
•
Workaround: Enter the shutdoown, then no shutdown commands on the interface after changing the access VLAN on the port. (CSCsk45969)
•
Workaround: None. (CSCsm30320)
•
Workaround: Intentionally fail the link between two switches by physically pulling the cable or shutting down the interface. Then, return the links to a normal condition. This is followed by delayed preemption, which you might have already configured. (CSCsm91997)
•
Workaround: Authenticate the phone before plugging a PC behind the phone. (CSCsq92724)
•
Workaround: None. (CSCso50659)
•
Workarounds: Do one of the following:
–
–
–
(CSCsq63051)
•
Workarounds: Do one of the following:
–
–
(CSCsq90598)
•
%PM-4-PORT_INCONSISTENT: STANDBY:Port is inconsistent:Workaround: When the port channel starts to flap, enter shut and no shut on the port channel. After the first switchover and after deleting the portchannel, create a new channel. (CSCsr00333)
Not supported on Supervisor Engine 6-E
•
Workaround: None. (CSCso93282)
•
Workaround: None. (CSCsq72572)
•
Workaround: None. (CSCsq63572)
Supervisor Engine 6-E Specific
•
Workaround: None.
The support to handle .1Q packets for software QoS lookup unavailable in the Cisco IOS Release 12.2(40)SG release. (CSCsk66449)
•
speed 10/100/1000 command, the applied policer or shape or bandwidth value might not correspond to the new forced speed.Service policy has to be configured with percentage police or shape or share values and the link speed is forced to a specific values. For example
Policy-map p1class-map c1police rate percent 10Workaround: Either use the speed auto 10/100/1000 command or the absolute policer, shape or shape values rather than percentage values. For example,
Policy-map p1class-map c1police rate 10 mbps(CSCsk56877
•
When an output service-policy is attached to an interface and if the policy is configured to apply DBL on a queue, the flows that are enqueued to the queue are subjected to the DBL algorithm. If one or more flows are classified as belligerent (flows do not back-off in response to drops because of congestion in the queue), those flows continue to be classified as belligerent even when DBL is disabled on that queue.
For this condition to persist, the transmit queues in question must remain congested for a long period of time and that congestion must be caused by flows that remain belligerent.
Workaround: Provided the queue in question is non-default (queuing actions are not configured in the class-default class of the policy-map), detach and re-attach the service-policy.
If this happens on the default queue, modifying and resetting some queuing parameters like bandwidth/shape fixes the issue. (CSCsk62457
•
Workarounds: Use the show log command to determine the cause of the power-down.
–
–
(CSCsk48632)
•
Workaround: None. (CSCsh99124)
•
On a switch running Cisco IOS Release 12.2(40)SG, all MTU values configured on a line card are set to default when the module is reset. Furthermore, MTU values are not retained for modules that are physically moved.
Workaround: None. (CSCsk52542)
•
Cisco IOS Release 12.2(40)SG, you will observe CRC errors after a reload or power cycle when you insert the card or the X2.Workaround: Reinsert the X2. (CSCsk43618)
•
Workaround: None. CSCsk67395)
•
When a packet is sent to the CPU it may get sent out on some other interface. If so, the original COS value for a .1X packet cannot be matched by software QoS (as per CSCsk66449). The packet is transmitted with whatever COS value it was generated with (7, for the MLDv1 packets described here).
Workaround: None.
Part of the root cause of this problem is captured through CSCsk66449, which indicates that the software QoS cannot match against a .1X packet. (CSCsk72544)
•
Workaround: None. You cannot explicitly check the trusted boundary state. However, you can indirectly determine this state:
The trusted boundary feature ensures whether the packet's COS/DSCP value will b e trusted or not. When the interface is not in a trusted state, the COS/DSCP fields are forced to zero on a received packet.
A QoS policy exists on that interface that uses that COS/DSCP value for classification. Therefore, if the packet classification is based on the packet value, you can infer that the interface is in a trusted state. (CSCsh72408)
•
Workaround: Enter the show policy-map interface command to find the actual burst value programmed. (CSCsi71036)
•
Workaround: Remove the configuration line by line without entering the default interface command. (CSCsj23103)
•
Workaround: None. However, if you enter the show policy-map name, the unconditional marking actions appear. (CSCsi94144)
•
Workaround: None. (CSCsl72868)
•
Workaround: Do one of the following:
–
–
(CSCsm45156)
•
Workaround: To ensure that the DBL action operates on the default queue, use the queue-limit command to specify an explicit queue size. The size range is dictated by the queue-limit command. (CSCso06422)
•
Configuring an inbound routemap on RTR3 to override the nexthop advertised by RTR2 does not avoid this problem because the BGP update message is ignored.
Workaround: Configure a n outbound routemap on RTR2 to explicitly set the IPv4 nexthop rather than allow the protocol to derive it implicitly. (CSCsk65139)
•
ipv6 bandwidth-percent eigrp as-number percent command, the supervisor engine reloads. If you enable redundancy, the STANDBY supervisor engine changes to ACTIVE, and the reloaded supervisor engine is set to STANDBY.Workaround: None. (CSCso30051)
•
This behavior occurs in a redundant switch when the ACTIVE supervisor engine is running IOS, the STANDBY supervisor engine is in rommon, and the STANDBY's rommon is upgraded from version 0.34 or to a later version. The upgrade process will cause the uplinks on the STANDBY supervisor engine to go down but the ACTIVE supervisor engine is unaware of this.
Workarounds: To resume normal operation, do one of the following:
–
–
There is no workaround for the link flap issue. (CSCsm81875)
•
The message may appear when a linecard boots, depending on how the hardware has powered-up.
Workaround: Reset the linecard. (CSCsq21215)
•
This problem can happen when pause frames are sent to the switchport and the flow control receive configuration is toggled on 10G port.
Workaround: Change the flow control receive configuration when no traffic exists. (CSCso71647)
•
Workaround: Disable IGMP snooping on all the relevant VLANs before disabling it globally.
(CSCsq71546)
•
Workaround: Enter shut followed by no shut on the interface to which the prefix list has been added. (CSCsq69116)
•
Workarounds:
a.
b.
(CSCsq62342)
•
Workaround: Remove and re-apply the service-policy on the interface.
(CSCsq79073)
•
The issue is observed only for packets that are logically switched through the switch but are internally controlled such that on egress the system generated by the switch itself. This can happen for certain snooping features like DAI, IGMP snooping, and DHCP snooping. This can also happen for IPv4/v6 packets with IP options/ extension headers that need processing in software.
Workaround: None.
(CSCso96660)
•
Example:
Policy-map p1class-map c1police rate percent 10Workaround: Use either the speed auto 10/100/1000 command or the absolute policer or shape values instead of percentage values.
Example:
Policy-map p1class-map c1police rate 10 mbps(CSCsk56877)
•
Layer 2 to Layer 3 or Layer 3 to Layer 2.Workaround: None. (CSCso54096)
•
03:50:00: %SM-4-BADEVENT: STANDBY:Event 'bundle_sync' is invalid for the current state 'COLLECTING_DISTRIBUTING': lacp_mux Gi7/7 - mux-Traceback= 10B97B80 10B98294 10189F78 1038FE0C 103944FC 1055E420 1055C4B8 10A2C28C 10A2AE88 10A2A4B0 10A27A18 10A225E8 1059E824 10595AACWorkaround: None. CSCso23786)
•
Workaround: Unconfigure all generic QOS policies from the system. (CSCsq84853)
•
Workaround: Unconfigure any generic QOS policies from the system. The QoS policies with the match any attribute cause IPv6 entries to become active. If the switch is a pure Layer 2 device, remove the generic protocol family attributes and narrow it to the protocol family.
(CSCsq84796)
•
Workaround: Enter shut, then no-shut on any REP port (of the same segment in which VLB is configured) in the topology. (CSCsq75342)
•
Workaround: Ping the global and link local addresses of the neighbor to ascertain and reinstate reachability. (CSCsq77181)
•
Workaround: Unconfigure the port channel and the associated physical port, and reconfigure them.
(CSCsq74229)
•
IFM CC Status as Inactive. Then, you allocate the VLAN, the CC-status remains Inactive.You only see this symptom if you did not allocate a VLAN before you configure the IFM, then at a later time allocate the same VLAN.
Workaround: Unconfigure, then reconfigure the IFM on the port.
•
This behavior is only seen when VLAN is allocated after the IFM is configured.
Workaround: Unconfigure with the no ethernet cfm mep level mpid vlan command, then reconfigure the IFM with the ethernet cfm mep level mpid vlan command on the port after the VLAN is allocated. Verify that the C-Status of the IFM is Active with the
show ethernet cfm maintenance-points local command. (CSCsm85460)Resolved Caveats in Cisco IOS Release 12.2(46)SG
This section lists the resolved caveats in Release 12.2(46)SG:
•
00:10:34: %BGP-5-DAMPENING_HIGH_MAX_PENALTY: Maximum penalty (32473) is more than allowed maximum (20000). Dampening is OFF00:10:06: %BGP-5-DAMPENING_HIGH_MAX_PENALTY: Maximum penalty (32473) is more than allowed maximum 000). Dampening is OFFAt this point, if you revert back to the bgp dampening command on the active supervisor engine, the new command is not synchronized with the standby supervisor engine.
Workaround: Enter the no bgp dampening command, then the bgp dampening command. (CSCse12485)
•
Workaround: Ensure that the REP Admin VLAN and the RSPAN destination VLAN differ. (CSCso12495)
•
Workaround: None. (CSCsm61748)
•
%C4K_HWACLMAN-4-ACLHWLABELERR: Path (in :50, 1006) label allocation failure: SignatureInconsistent - packets will be handled in software, QoS is disabled.One feature combination that can trigger this problem is the attempt to combine a QoS policy that matches on cos bits with IPv6 ACL configuration that matches on IPv6 source addresses that partially mask in the lower 48 bits of the address. (IPv6 subnets in the /81 to /127 range will also trigger this behavior if IPv6 multicast routing is enabled.)
Workaround: Do not configure feature combinations that conflict. Currently the above conflict between QoS policies matching on COS bits and IPv6 configuration with partial masking of the lower 48 bits of the source address is the only known conflicting feature combination. If matching on COS bits is required by the QoS policy, architect the IPv6 network using /80 subnets or larger. (CSCsk79791)
•
The first problem occurs on a dual Layer 3 interface where both IPv4 and IPv6 address are configured. The second problem occurs when all Layer 3 interfaces in a switch are configured with IPv6 address only.
Workarounds: Avoid using a dual Layer 3 interface with both IPv6 and IPv4 address configured.
Avoid using a switch as a purely IPv6 Layer 3 interface-only router. Ensure that it has at least one Layer 3 interface per SVI with IPv4 address configured. (CSCsk77234)
•
Workaround: Before switching a Layer 3 interface from a router port to a switch port, unconfigure the IPv6 ACL on the router interface. This ensures that the IPv6 ACL is cleaned up properly both in the IOS running configuration as well as in the TCAM hardware. (CSCsk60775)
•
This occurs on all E-series line cards that report critical or shutdown temperature alarms. The actual temperatures and the alarm states are visible in the output of show environment temperature command.
Workarounds: None for LED colors. However, when an alarm is raised or cleared, console log messages and SNMP traps are entered. Also, the current status of any temperature alarms are visible in the output of the show environment temperature command. (CSCsk57143)
•
Cisco IOS Release 12.2(31)SGA to 12.2(40)SG, the duplex settings on FastEthernet settings are lost. The interface reverts to its default duplex setting, and the duplex setting no longer appears in the output of the show running command.Workaround: If non-default duplex settings are in the running config, note them prior to upgrading, and reapply them after the upgrade completes. (CSCsk83670)
•
Workaround: Re-apply the policy-map. (CSCsk75793
•
Workaround: Enter the show policy-map interface command to find the actual exceed burst value programmed. (CSCsj44237)
•
The QoS configuration is present in the running configuration but is not honored on the interface.
Workaround: Reapply the QoS configuration to the interface. (CSCsm58839)
•
Workarounds: Before configuring IPv6 MTU on an interface you must enable IPv6 on the interface. To enable IPv6, use the ipv6 enable command.
If you encounter this issue, use the following commands to recover your switch:
1.
2.
3.
4.
5.
6.
7.
8.
9.
•
Workaround: Shut down supervisor uplink ports prior to reload. (CSCsl34390)
Troubleshooting
These sections provide troubleshooting guidelines for the Catalyst 4000 family running IOS supervisor engines:
•
Netbooting from the ROMMON
Netbooting using a boot loader image is not supported. Instead, use one of the following options to boot an image:
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 engine Ethernet port with an IP address 172.16.1.5 and IP mask 255.255.255.0, enter the following command:
rommon 2> set interface fa1 172.16.1.5 255.255.255.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 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 4500 series switches, refer to the Catalyst 4000 MIB Support List located at ftp://ftp.cisco.com/pub/mibs/supportlists/cat4000/cat4000-supportlist.html.
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
•
http://www.cisco.com/go/cat4900/docs
•
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
Notices
The following notices pertain to this software license.
OpenSSL/Open SSL Project
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com).
This product includes software written by Tim Hudson (tjh@cryptsoft.com).
License Issues
The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License:
Copyright © 1998-2007 The OpenSSL Project. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
4.
5.
6.
"This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/)".
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT "AS IS"' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
Original SSLeay License:
Copyright © 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved.
This package is an SSL implementation written by Eric Young (eay@cryptsoft.com).
The implementation was written so as to conform with Netscapes SSL.
This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com).
Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.
2.
3.
"This product includes cryptographic software written by Eric Young (eay@cryptsoft.com)".
The word `cryptographic' can be left out if the routines from the library being used are not cryptography-related.
4.
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license [including the GNU Public License].
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
Release Notes for the Catalyst 4500 Series Switch, Cisco IOS Release 12.2(46)SG1
Copyright © 1999-2008, Cisco Systems, Inc. All rights reserved.
FeedbackContact Cisco
- Open a Support Case
- (Requires a Cisco Service Contract)