Table Of Contents
Release Notes for the
Catalyst 2900 Series XL and 3500 Series XL Cisco IOS Release 12.0(5)XW
Contents
System Requirements
Hardware Supported
Software Compatibility
Browser Support
Creating Clusters with Different Releases of IOS Software
Creating Clusters with Catalyst 1900 and 2820 Switches
Minimum IOS Release for Major Features
Upgrading to a New Software Release
Upgrading a Switch by Using the VSM or Cluster Manager
Using VSM to Upgrade a Switch
Recovering from an Incomplete VSM Software Upgrade
Upgrading a Switch by Using the CLI
Which Files to Use
Downloading the New Software
Upgrading Catalyst 3500 Series XL Switches
Upgrading 8-MB Catalyst 2900 Series XL Switches
Installing the Required Plug-In
Windows 95, Windows 98, and Windows NT 4.0 Users
Solaris Users
New Features in This Release
New Hardware Features in Release 12.0(5)XW
New Software Features in Release 12.0(5)XW
Limitations and Restrictions
Important Notes
Caveats
Open Caveats
Resolved Caveats
Documentation Updates
Documentation Notes
Setting Up the Catalyst 2900 XL Initial Configuration
Configuring Voice Ports to Carry Voice and Data Traffic on Different VLANs
Understanding Cross-Stack UplinkFast
How CSUF Works
Events that Cause Fast Convergence
Limitations
Connecting the Stack Ports
Configuring Cross-Stack UplinkFast
Understanding DHCP-Based Autoconfiguration
DHCP Client Request Process
Configuring the DHCP Server
Configuring the TFTP Server
Configuring the DNS
Configuring the Relay Device
Obtaining Configuration Files
Example Configuration
New and Changed Commands
show interface
show spanning-tree
spanning-tree stack-port
Syslog Error Messages
Related Documentation
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Contacting TAC by Using the Cisco TAC Website
Contacting TAC by Telephone
Release Notes for the
Catalyst 2900 Series XL and 3500 Series XL Cisco IOS Release 12.0(5)XW
December 18, 2000 (Document revised April, 2001)
Cisco IOS Release 12.0(5)XW runs on Catalyst 3500 series XL switches and Catalyst 2900 series XL 8-MB CPU DRAM switches. Catalyst 2900 series XL 4-MB CPU DRAM switches are not supported.
These release notes include important information about this IOS release and any limitations, restrictions, and caveats that apply to it. See the "Related Documentation" section for the complete list of Catalyst 2900 and 3500 XL switch documentation.
Note 
Before upgrading your switch to Release 12.0(5)XW, read the "Upgrading to a New Software Release" section for important information.
This IOS release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future IOS releases become available, they will be posted to CCO in the Cisco IOS software area.
Contents
This document has the following sections:
•"System Requirements" section
•"Upgrading to a New Software Release" section
•"New Features in This Release" section
•"Limitations and Restrictions" section
•"Important Notes" section
•"Caveats" section
•"Documentation Updates" section
•"Related Documentation" section
•"Obtaining Documentation" section
•"Obtaining Technical Assistance" section
System Requirements
This section describes these system requirements for Release 12.0(5)XW:
•"Hardware Supported" section
•"Software Compatibility" section
•"Minimum IOS Release for Major Features" section
Hardware Supported
Table 1 lists the supported Catalyst 3500 XL switches, and Table 2 lists the supported 8-MB Catalyst 2900 XL switches.
Catalyst 2900 series XL 4-MB switches run original edition software and are not supported. These switches can be updated only to Release 11.2(8.6)SA6.
Table 1 Catalyst 3500 Series XL Switches
Switch
|
Description
|
Catalyst 3508G XL
|
8 Gigabit module slots
|
Catalyst 3512 XL
|
12 autosensing 10/100 ports and 2 Gigabit module slots
|
Catalyst 3524 XL
|
24 autosensing 10/100 ports and 2 Gigabit module slots
|
Catalyst 3524-PWR XL
|
24 autosensing 10/100 inline-power ports and 2 Gigabit module slots
|
Catalyst 3548 XL
|
48 autosensing 10/100 ports and 2 Gigabit module slots
|
Table 2 8-MB Catalyst 2900 Series XL Switches
Switch
|
Description
|
Catalyst 2912MF XL
|
12 100BaseFX ports and 2 high-speed expansion slots
|
Catalyst 2912 XL
|
12 autosensing 10/100 ports
|
Catalyst 2924M XL
|
24 autosensing 10/100 ports and 2 high-speed expansion slots
|
Catalyst 2924M DC XL
|
24 autosensing 10/100 ports and 2 high-speed expansion slots (DC power)
|
Catalyst 2924 XL
|
24 autosensing 10/100 ports
|
Catalyst 2924C XL
|
22 autosensing 10/100 ports and 2 100BaseFX ports
|
Software Compatibility
This section describes these software compatibility requirements for Release 12.0(5)XW:
•"Browser Support" section
•"Creating Clusters with Different Releases of IOS Software" section
•"Creating Clusters with Catalyst 1900 and 2820 Switches" section
Browser Support
You can access the web-based interfaces through the browsers listed in Table 3. The switch checks the browser version when starting a session to ensure that the browser is supported. If the browser is not supported, the switch displays an error message, and the session does not start.
Table 3 Browser Support
Operating System
|
Minimum Operating System Requirements
|
Netscape Communicator
|
Microsoft Internet Explorer
|
Windows 95
|
Service Pack 1
|
4.61, 4.7
|
4.01a or 5.0
|
Windows 98
|
Second Edition
|
4.61, 4.7
|
4.01a or 5.0
|
Windows NT 4.0
|
Service Pack 3 or later
|
4.61, 4.7
|
4.01a or 5.0
|
Solaris 2.5.1 or higher
|
SUN-recommended patch cluster for the OS and Motif library patch 103461-24
|
4.61, 4.7
|
Not supported
|
Netscape Communicator version 4.60 is not supported.
Note If your browser is Internet Explorer and you receive an error message stating that the page might not display correctly because your security settings prohibit running activeX controls, this might indicate that your security settings are set too high. To lower security settings, go to Tools > Internet Options and select the Security tab. Select the indicated Zone, and move the Security Level for this Zone slider from High to Medium (the default).
To use the Cluster Management Suite (CMS), complete the browser-configuration instructions described in the Cisco IOS Desktop Switching Software Configuration Guide.
Creating Clusters with Different Releases of IOS Software
Some versions of the Catalyst 2900 and 3500 XL software do not support clustering, and other versions do not support some of the features in this release. To ensure that all cluster switches are operating with the same level of software, we recommend that you upgrade all cluster switches to Release 12.0(5)XP or later. Table 4 lists the available versions of clustering software and their capabilities.
If you have a cluster with switches that are running different versions of IOS software, changes on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)XU or later.
Table 4 Cluster Software Caveats
IOS Release
|
Cluster Status
|
Caveats
|
Release 12.0(5)XU
|
Member or commander switch
|
Features introduced with Release 12.0(5)XW, such as cross-stack UplinkFast and the 1000BaseT Gigabit Interface Converter (GBIC), are not supported.
|
Release 12.0(5)XP and earlier
|
Member switch
|
Features introduced with Release 12.0(5)XU, such as Virtual Local Area Network (VLAN) Trunk Protocol (VTP) pruning, appear as read-only.
|
Release 12.0(5)XP and earlier
|
Command switch
|
A 1000BaseT module installed in a switch running Release 12.0(5)XU does not display in Cluster Manager or VSM.
|
Release 11.2(8)SA6
|
Member switch
|
Features introduced with Release 12.0(5)XU, such as VTP pruning, appear as read-only.
|
Release 11.2(8)SA5 and earlier
|
Edge device
|
No clustering capabilities.
|
Creating Clusters with Catalyst 1900 and 2820 Switches
Catalyst 1900 and 2820 switches are always member switches, not command switches. However, a cluster with a command switch that is running Release 11.2(8)SA6 cannot communicate with a Catalyst 1900 or 2820. This means that if the command switch is running Release 11.2(8)SA6, the CMS does not support a Catalyst 1900 or 2820 switch in these CMS features:
•Visual Switch Manager
•Device report
•Link graph
•Bandwidth graph
Minimum IOS Release for Major Features
Table 5 lists the minimum IOS release required to support the major features of the Catalyst 2900 and 3500 XL switches.
Table 5 Catalyst 2900 and 3500 Series XL Features and the Minimum IOS Release Required
Feature
|
Minimum Release Required
|
Cross-stack UplinkFast
|
Release 12.0(5)XW
|
Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration
|
Release 12.0(5)XW
|
Support for the single-port 1000BaseT Gigabit Ethernet GBIC (WS-G5482)
|
Release 12.0(5)XW
|
WS-C3524-PWR XL switch with 10/100 inline-power ports
|
Release 12.0(5)XU
|
WS-C2924M-XL-EN-DC switch with DC power connector
|
Release 12.0(5)XU
|
Hot Standby Router Protocol (HSRP) for clustering
|
Release 12.0(5)XU
|
Extended discovery of cluster candidates up to 7 hops from the command switch
|
Release 12.0(5)XU
|
Support for up to 16 switches in a cluster
|
Release 12.0(5)XU
|
VTP pruning
|
Release 12.0(5)XU
|
Change management VLAN for a cluster
|
Release 12.0(5)XU
|
Private VLAN edge support
|
Release 12.0(5)XU
|
UniDirectional Link Detection (UDLD) for detecting unidirectional links
|
Release 12.0(5)XU
|
Extended cluster member functionality for Catalyst 1900 and 2820 switches
|
Release 12.0(5)XP
|
Remote monitoring (RMON) support through the command-line interface (CLI) or Simple Network Management Protocol (SNMP)
|
Release 12.0(5)XP
|
Change management VLAN
|
Release 12.0(5)XP
|
Quality of service (QoS) based on IEEE 802.1p class of service (CoS) values
|
Release 12.0(5)XP
|
Catalyst 3500 series XL switches (except 3548 XL)
|
Release 11.2(8)SA6
|
Catalyst 3548 XL switch
|
Release 12.0(5)XP
|
Cluster management
|
Release 11.2(8)SA6
|
Terminal Access Control Access Server+ (TACACS+)
|
Release 11.2(8)SA6 (Enterprise Edition Software)
|
Network Time Protocol (NTP)
|
Release 11.2(8)SA6
|
Spanning Tree Protocol (STP) UplinkFast
|
Release 11.2(8)SA6
(Enterprise Edition Software)
|
250 VLANs (some models: see the "Limitations and Restrictions" section)
|
Release 11.2(8)SA6
|
Catalyst 2900 series XL 1000BaseX modules
|
Release 11.2(8)SA5
|
Catalyst 2900 series XL ATM modules
|
Release 11.2(8)SA5
|
VLAN Membership Policy Server (VMPS)
|
Release 11.2(8)SA4 (Enterprise Edition Software)
|
8192 media access control (MAC) addresses on modular switches
|
Release 11.2(8)SA4
|
Inter-Switch Link (ISL) trunking
|
Release 11.2(8)SA4
(Enterprise Edition Software)
|
IEEE 802.1Q trunking
|
Release 11.2(8)SA5
(Enterprise Edition Software)
|
Switch Network View stack management
|
Release 11.2(8)SA3
|
Web-based switch management
|
Release 11.2(8)SA
|
Fast EtherChannel port groups
|
Release 11.2(8)SA
|
Upgrading to a New Software Release
This section describes these procedures for upgrading your switch software:
•"Upgrading a Switch by Using the VSM or Cluster Manager" section
•"Upgrading a Switch by Using the CLI" section
•"Upgrading Catalyst 3500 Series XL Switches" section
•"Upgrading 8-MB Catalyst 2900 Series XL Switches" section
•"Installing the Required Plug-In" section
Caution The 4-MB Catalyst 2900 series XL switches do not have sufficient memory to be upgraded to this release.
Note Before upgrading your switch to Release 12.0(5)XW, read this section for important information.
Upgrading a Switch by Using the VSM or Cluster Manager
If your switch is running Release 11.2(8)SA3, SA4, or SA5, we recommend that you upgrade the switch software by using the web-based VSM. If you are upgrading a switch running Release 11.2(8)SA6 or later to this release, we recommend that you use Cluster Manager.
If you are using VSM to upgrade a switch running Release 11.2(8)SA6 or later, follow the procedure in the "Using VSM to Upgrade a Switch" section.
General instructions for upgrading switch software are included in the Cisco IOS Desktop Switching Software Configuration Guide; detailed instructions are provided in the online help files.
Note You cannot use the web-based interface to upgrade a switch running Release 11.2(8)SA2 or previous releases. Use the CLI to perform the upgrade in such cases.
Using VSM to Upgrade a Switch
Note If you use VSM to upgrade your switch from a release prior to Release 11.2(8)SA6 to this release, you must rename the image file to ensure that you can reload the software. You can rename the image file by accessing the CLI through Telnet or by connecting to the switch console port.
Tips If your switch is not configured for Telnet, follow the procedure described in the "Configuring the Switch for Telnet" section in the Cisco IOS Desktop Switching Software Configuration Guide.
Note You do not need to perform this procedure if you are using Cluster Manager or VSM to upgrade from Release 11.2(8)SA6 or later. This issue also does not apply to the current release of IOS.
Follow these steps to rename the image file by using the CLI, and then use VSM to upgrade the software:
Step 1 Access the CLI by starting a Telnet session or by connecting to the switch console port through the RS-232 connector.
To start a Telnet session on your PC or workstation, enter the following command:
server% telnet switch_ip_address
Enter the Telnet password if you are prompted to do so.
Step 2 Enter privileged EXEC mode:
Enter the password if you are prompted to do so.
Step 3 Display the files in Flash memory:
2 -rwx 4484 Mar 05 1993 00:31:09 vlan.dat
3 -rwx 110 Mar 01 1993 19:50:50 info
92 -rwx 877 Mar 06 1993 18:39:38 placement.txt
5 -rwx 1644050 Mar 01 1993 19:36:14 c2900XL-c3h2s-mz-112.8.SA6.bin
6 drwx 6720 Mar 01 1993 00:18:36 html
86 -rwx 110 Mar 01 1993 19:37:00 info.ver
116 -rwx 3686 Mar 01 1993 19:55:33 config.text
89 -rwx 25 Mar 01 1993 00:26:30 snmpengineid
7 -rwx 313 Mar 01 1993 19:34:57 env_vars
Step 4 Rename the image file to boot.bin:
switch# rename flash:c2900XL-c3h2s-mz-112.8.SA6.bin flash:boot.bin
Ensure that there are no other image files in Flash memory.
Step 5 Start VSM as usual and display the System Configuration page by selecting
System > System Configuration from the menu bar.
Step 6 In the Cisco IOS Image File field, enter boot.bin.
Step 7 Check the Retain Current IOS Image File Name check box.
Step 8 Complete the other fields on the page as described in the "Reloading and Upgrading the Switch Software" section of the Cisco IOS Desktop Switching Software Configuration Guide.
Step 9 Click Upgrade IOS Software and Visual Switch Manager.
Step 10 Verify the upgrade by displaying the contents of Flash memory. The file boot.bin should be present:
2 -rwx 4484 Mar 05 1993 00:31:09 vlan.dat
4 -rwx 110 Mar 01 1993 19:50:50 info
92 -rwx 877 Mar 06 1993 18:39:38 placement.txt
5 -rwx 1644050 Mar 01 1993 19:36:14 boot.bin
6 drwx 6720 Mar 01 1993 00:18:36 html
86 -rwx 110 Mar 01 1993 19:37:00 info.ver
116 -rwx 3686 Mar 01 1993 19:55:33 config.text
89 -rwx 25 Mar 01 1993 00:26:30 snmpengineid
7 -rwx 313 Mar 01 1993 19:34:57 env_vars
3612672 bytes total (840704 bytes free)
Step 11 Verify that the switch reloads correctly by displaying the boot variable (BOOT path-list), which should also be boot.bin.
BOOT path-list: flash:boot.bin
Config file: flash:config.text
Recovering from an Incomplete VSM Software Upgrade
If you do not follow the procedure described in "Using VSM to Upgrade a Switch," an upgrade can fail due to insufficient space because of multiple software images or other files in Flash memory. When the upgrade fails, the image file is copied to Flash memory, but there is insufficient space for the HTML files, and you lose access to VSM.
In the event of a failure, ensure that the image file in Flash memory has the same name as the contents of the boot variable. You can compare these two names by following the last two steps in the procedure described in the "Using VSM to Upgrade a Switch" section.
If the contents of the boot variable and the image file name are the same, the switch can reset successfully. If they are different, rename the image file, or reset the boot variable by entering the system boot name global configuration command. The boot variable and the image file name should be the same.
To recover from the incomplete download of the HTML files, log in to the switch, and upgrade the software as described in the "Upgrading a Switch by Using the CLI" section.
Upgrading a Switch by Using the CLI
The CLI upgrade procedure consists of these major steps:
1. Downloading the combined .tar file from CCO, as described in the "Downloading the New Software" section. This file contains the IOS image and the HTML files. The tar command extracts the IOS image and the HTML files from the combined .tar file during the TFTP copy to the switch.
2. Downloading the TFTP server application to copy the switch software from your PC to the switch, if necessary.
3. Using the CLI to upgrade your switch or cluster to the new software.
Which Files to Use
Table 6 describes the file extensions and what they mean for the upgrade procedure. It is easier to upgrade the switch software by using a combined .tar file that contains the HTML files and the IOS image. The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file, and you must use a combined .tar file to upgrade a switch through the CMS.
Table 7 and Table 8 list the software files for this IOS release.
Table 6 Possible Extensions for IOS Software Files
Extension
|
Description
|
.tar
|
A compacted file from which you can extract files by using the tar command. There are two types of .tar files:
•A combined .tar file that contains both the IOS image file and the HTML files.
•An HTML .tar file that has the letters HTML in its name and contains just the HTML files for the IOS release. From the CLI, you can upgrade the switch software with this HTML file and the IOS image file.
|
.bin
|
The IOS image file that you can copy to the switch through TFTP.
|
Table 7 Catalyst 2900 Series XL Cisco IOS Software Files
Filename
|
Description
|
c2900XL-c3h2s-mz-120.5-XW.bin
|
IOS image-only file
|
c2900XL-c3h2s-mz-120.5-XW.tar
|
IOS image and HTML files
|
c2900XL-html-plus.120.5-XW.tar
|
HTML files
|
Table 8 Catalyst 3500 Series XL Cisco IOS Software Files
Filename
|
Description
|
c3500XL-c3h2s-mz-120.5-XW.bin
|
IOS image file
|
c3500XL-c3h2s-mz-120.5-XW.tar
|
IOS image file and HTML files
|
c3500XL-html-plus.120.5-XW.tar
|
HTML files
|
Downloading the New Software
Follow these steps to download the new software and, if necessary, the TFTP server application.
Step 1 Use Table 6 to Table 8 to identify the files that you want to download.
Note We recommend that you download the combined .tar file that contains the image file and the HTML files. The procedures in these release notes are for upgrading a switch by using the combined .tar file, and the VSM and Cluster Manager are designed to upgrade a switch by using this combined file.
Step 2 Download the files from the following location:
If you have a SmartNet support contract, log in to one of the following URLs and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
If you do not have a SmartNet contract, download the appropriate files from one of the following URLs:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
Step 3 Download the TFTP server from the URL listed in Step 2, if necessary. The readme.txt file describes how to download the TFTP server.
After you have downloaded the correct files to your PC or workstation, you can use the CLI to perform a TFTP transfer of the file or files to the switch.
Upgrading Catalyst 3500 Series XL Switches
This procedure is only for upgrading Catalyst 3500 XL switches by copying the combined .tar file to the switch. You copy the files to the switch from a TFTP server and extract the files by entering the tar command.
Follow these steps to upgrade the switch software by using a TFTP transfer:
Step 1 If your PC or workstation cannot act as a TFTP server, copy the file to a TFTP server to which you have access.
Step 2 Access the CLI by starting a Telnet session or by connecting to the switch console port through the RS-232 connector.
To start a Telnet session on your PC or workstation, enter the following command:
server% telnet switch_ip_address
Enter the Telnet password if you are prompted to do so.
Step 3 Enter privileged EXEC mode:
Enter the password if you are prompted to do so.
Step 4 Display the name of the running (default) image file (BOOT path-list). The following example shows the name in italic:
switch# show boot
BOOT path-list: flash:current_image
Config file: flash:config.text
Enable Break: 1
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
Step 5 If there is no file defined in the BOOT path-list, enter dir flash: to display the contents of Flash memory.
Step 6 Using the exact, case-sensitive name of the combined .tar file that you downloaded, rename the running image file to that name, and replace the .tar extension with .bin. The image filename is then the same as the downloaded filename but with a .bin extension. This step does not affect the operation of the switch.
switch# rename flash:current_image flash:new_image
Source filename [current_image]?
Destination filename [new_image]?
For example:
switch# rename flash:c3500XL-c3h2-mz-112.8.2-SA6.bin flash:c3500XL-c3h2s-mz-120.5-XW.bin
Step 7 Display the contents of Flash memory to verify the renaming of the file:
switch# dir flash:
Directory of flash:/
2 ---x 1644045 Apr 04 1993 15:17:15 c3500XL-c3h2s-mz-120.5-XW.bin
3 -rwx 415 Jun 13 1993 05:15:37 placement.txt
4 d--x 6848 May 03 2000 10:47:58 html
70 -rwx 20 Mar 21 1993 09:17:03 prefs.text
6 ---x 106 Mar 01 1993 21:56:52 info
228 ---x 106 Apr 04 1993 15:17:54 info.ver
69 -rwx 2188 Mar 13 1993 03:38:28 config.text
230 -rwx 744 Mar 25 1993 19:16:46 vlan.dat
115 -rwx 354 Mar 13 1993 04:17:15 env_vars
3612672 bytes total (936960 bytes free)
Step 8 Enter global configuration mode:
switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 9 Disable access to the switch HTML pages:
switch(config)# no IP http server
Step 10 If you entered the boot command with the name of the image file, enter this command to change it to the new name:
switch(config)# boot system flash:new_image
For example:
switch(config)# boot system flash:c3500XL-c3h2s-mz-120.5-XW.bin
Note If the show boot command entered in Step 4 displays no image name, you do not need to enter this command; the switch automatically finds the correct file to use when it resets.
Step 11 Return to privileged EXEC mode:
Step 12 Remove the HTML files:
switch# delete flash:html/*
Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Caution In the following step, the tar command copies the combined.tar file that contains both the image and the HTML files. You do not need to copy an HTML.tar file in this procedure.
Step 13 Enter the following command to copy the new image and HTML files to the switch Flash memory:
switch# tar /x tftp://server_ip_address//path/filename.tar flash:
Loading /path/filename.tar from server_ip_address (via VLAN1):!)
extracting info (110 bytes)
extracting c3500XL-c3h2s-mz-120.5-XW.bin (1271095 bytes)!!!!!!!!!!!!!!!!!!!!
extracting html/Detective.html.gz (1139 bytes)!
extracting html/ieGraph.html.gz (553 bytes)
extracting html/DrawGraph.html.gz (787 bytes)
extracting html/GraphFrame.html.gz (802 bytes)!
Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the tar command.
Step 14 Enter global configuration mode:
switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 15 Re-enable access to the switch HTTP pages:
switch(config)# IP http server
Step 16 Return to privileged EXEC mode:
Step 17 Reload the new software with the following command:
switch# reload
System configuration has been modified. Save? [yes/no]:y
Proceed with reload? [confirm]
Step 18 Press Return to confirm the reload.
Your Telnet session ends when the switch resets.
Step 19 After the switch reboots, use Telnet to return to the switch, and enter the privileged EXEC mode show version command to verify the upgrade procedure. If you have a previously-opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest HTML files.
Upgrading 8-MB Catalyst 2900 Series XL Switches
This procedure is for upgrading Catalyst 2900 XL switches with 8 MB of DRAM. You upgrade a switch by extracting the IOS image file and the HTML files from a combined.tar file. You copy the files to the switch from a TFTP server and extract the files by entering the tar command.
Note If you want to copy the IOS image file or HTML files separately to the switch, refer to the Catalyst 2900 series XL release notes for Release 11.2(8)SA4 on CCO.
If you are unsure whether your switch has 4 MB or 8 MB of memory, you can verify memory capacity at Step 4.
Follow these steps to upgrade the switch software by using the tar command to start a TFTP transfer:
Step 1 If your PC or workstation cannot act as a TFTP server, copy the file to a TFTP server to which you have access.
Step 2 Access the CLI by starting a Telnet session or by connecting to the switch console port through the RS-232 connector.
To start a Telnet session on your PC or workstation, enter the following command:
server% telnet switch_ip_address
Enter the Telnet password if you are prompted to do so.
Step 3 Enter privileged EXEC mode:
Enter a password if you are prompted to do so.
Step 4 Confirm that you have an 8-MB switch:
Cisco Internetwork Operating System Software IOS (tm)
C2900XL Software (C2900XL-HS-M), Version 11.2(8.2)SA6, RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Mon 23-Nov-98 20:59 by paulines
Image text-base: 0x00003000, data-base: 0x00202144
ROM: Bootstrap program is C2900XL boot loader
2900XL-EN-84.3 uptime is 1 day, 22 hours, 23 minutes
System restarted by power-on
cisco WS-C2924-XL (PowerPC403GA) processor (revision 0x11)
with 8192K/1024K bytes of memory.
Processor board ID 0x0E, with hardware revision 0x01
Processor is running Enterprise Edition Software
24 Ethernet/IEEE 802.3 interface(s)
32K bytes of flash-simulated non-volatile configuration memory.
Base ethernet MAC Address: 00:50:80:39:EC:40
Motherboard assembly number: 73-3382-04
Power supply part number: 34-0834-01
Motherboard serial number: FAA02499G7X
Model number: WS-C2924-XL-EN
System serial number: FAA0250U03P
Configuration register is 0xF
Step 5 Display the name of the running (default) image file (BOOT path-list). The following example shows the name in italic:
switch# show boot
BOOT path-list: flash:current_image
Config file: flash:config.text
Enable Break: 1
Manual Boot: no
HELPER path-list:
NVRAM/Config file
buffer size: 32768
Step 6 If there is no file defined in the BOOT path-list, enter dir flash: to display the contents of Flash memory. The file named c2900XL-h2-mz-112.8.2.11-SA6.bin is your image file. c2900XL-h2-mz-112.8.2.11-SA6.bin
2 ---x 1644046 Apr 04 1993 15:22:13 c2900XL-c3h2s-mz-120.5-XU.bin
4 d--x 6848 Apr 04 1993 15:23:11 html
6 -rwx 79 Apr 04 1993 15:20:34 env_vars
5 ---x 106 Apr 04 1993 15:20:36 info
68 -rwx 1399 May 16 2000 14:43:42 config.text
259 ---x 106 Apr 04 1993 15:23:12 info.ver
3612672 bytes total (940032 bytes free)
Step 7 Using the exact, case-sensitive name of the combined .tar file that you downloaded, rename the running image file to that name, and replace the .tar extension with a .bin extension. The image file name is then the same as the downloaded file name but with a .bin extension. This step does not affect the operation of the switch.
switch# rename flash:current_image flash:new_image
Source filename [current_image]?
Destination filename [new_image]?
For example:
switch# rename flash:c2900XL-h2-mz-112.8.2-SA6.bin flash:c2900XL--c3h2s-mz-120.5-XW.bin
Source filename [c2900XL-h2-mz-112.8.2-SA6.bin]?
Destination filename [c2900XL-c3h2s-mz-120.5-XW.bin]?
Step 8 Enter global configuration mode:
switch# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 9 Disable access to the switch HTML pages:
switch(config)# no IP http server
Step 10 If you entered the boot command with the name of the image file, enter this command to change it to the new name.
switch(config)# boot system flash:new_image
For example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120.5-XW.bin
Note If the show boot command entered in Step 5 displays no image name, you do not need to enter this command; the switch automatically finds the correct file to use when it resets
Step 11 Return to privileged EXEC mode:
Step 12 Remove the HTML files:
switch# delete flash:html/*
Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 13 If upgrading from Release 11.2(8)SA5 or earlier, remove the files in the Snmp directory:
switch# delete flash:html/Snmp/*
Make sure the S in Snmp is uppercase.
Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Caution In the following step, the
tar command copies the combined .tar file that contains both the image and the HTML files. You do not need to copy an HTML.tar file in this procedure.
Step 14 Enter the following command to copy the new image and HTML files to the switch Flash memory:
switch# tar /x tftp://server_ip_address//path/filename.tar flash:
Loading /path/filename.tar from server_ip_address (via VLAN1):!)
extracting info (111 bytes)
extracting c2900XL-c3h2s-mz-120.5-XW.bin (1557286 bytes)!!!!!!!!!!!!!!!!!!!!
extracting html/Detective.html.gz (1139 bytes)!
extracting html/ieGraph.html.gz (553 bytes)
extracting html/DrawGraph.html.gz (787 bytes)!
Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the tar command.
Step 15 Enter global configuration mode:
switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 16 Re-enable access to the switch HTTP pages:
switch(config)# IP http server
Step 17 Return to privileged EXEC mode:
Step 18 Reload the new software with the following command:
switch# reload
System configuration has been modified. Save? [yes/no]:y
Proceed with reload? [confirm]
Step 19 Press Return to confirm the reload.
Your Telnet session ends when the switch resets.
Step 20 After the switch reboots, use Telnet to return to the switch, and enter the privileged EXEC mode show version command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest HTML files.
Installing the Required Plug-In
A browser Java plug-in is required to access the HTML-based CMS. Download and install the plug-in before you start CMS.
If the Java applet does not initialize after you have installed the plug-in, open the Java Plug-in Control Panel (Start > Programs > Java Plug-in Control Panel), and verify the following setting:
In the Proxies tab, verify that Use browser settings is checked and that no proxies are enabled.
Windows 95, Windows 98, and Windows NT 4.0 Users
If you have a SmartNet support contract, log in to one of the following URLs and download the plug-in:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
If you do not have a SmartNet contract, download the plug-in from one of the following URLs:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
If you start CMS without having installed the required Java plug-in, the switch automatically detects the lack of the plug-in. If you are using a supported Netscape browser, the browser displays a Cisco Connection Online (CCO) page that contains the Java plug-in and instructions to install it. If you are using a supported Internet Explorer browser, it automatically downloads and installs the browser.
Solaris Users
Solaris users need to download the Java plug-in and the JRE 1.2.2_05.
Download the Java plug-in for Solaris from the following URL:
http://www.sun.com/software/solaris/netscape/ipis/
Install the plug-in by following the instructions that are posted on the URL.
Install the JRE 1.2.2_05 from the following URL:
http://www.sun.com/software/solaris/java/download.html
Follow the links in the section titled J2SE: Java[tm] 2 SDK, Standard Edition (1.2.2_05) to download and install the JRE.
New Features in This Release
This section describes the new supported hardware and the new software features for the Catalyst 2900 series XL and Catalyst 3500 series XL switches that are provided in this release.
•"New Hardware Features in Release 12.0(5)XW" section
•"New Software Features in Release 12.0(5)XW" section
Note New major software features, more detailed descriptions, as well as procedures for implementation, are in the "Documentation Updates" section. This information will be incorporated into the next version of the software documentation.
New Hardware Features in Release 12.0(5)XW
This release supports the single-port 1000BaseT GBIC (WS-G5482). Switches running earlier software versions do not recognize and automatically enable this GBIC.
Note If the GBIC is not securely inserted, the switch might fail to recognize it or might display an incorrect media type following a show interface command entry. If this happens, remove and reinsert the GBIC.
New Software Features in Release 12.0(5)XW
This release contains the following new software features:
•Cross-stack UplinkFast
Cross-stack UplinkFast provides a fast spanning-tree transition (fast convergence in less than 2 seconds under normal network conditions) across a stack of switches that use the GigaStack GBICs connected in a shared cascaded configuration (multidrop backbone). During the fast transition, an alternate redundant link on the stack of switches is placed into the forwarding state without causing temporary loops or loss of connectivity to the backbone. With this feature, you can have a redundant and resilient network. For more information, see the "Understanding Cross-Stack UplinkFast" section.
•DHCP-based autoconfiguration
The DHCP provides configuration information to Internet hosts and internetworking devices. With DHCP-based autoconfiguration, your switch (DHCP client) can be automatically configured during bootup with IP address information and a configuration file that it receives during DHCP-based autoconfiguration. DHCP replaces BOOTP for autoconfiguration to ensure retrieval of configuration files by unicast TFTP messages. For more information, see the "Understanding DHCP-Based Autoconfiguration" section.
•The following new features were added to CMS:
–Port Search window: From the main menu, select Port > Port Search. In this window, you can search for ports by their description. After a search is complete, you can select one of the ports and click View Details to display its run-time status.
–Port Statistics window: From the main menu, select Port > Port Statistics. In this window, you can monitor the data traffic on the ports of a given device in three tabbed panels (Overview, Transmit Details, and Receive Details). You can also refresh the display or reset the statistics counters.
–In Cluster Manager, a new port status LED indication has been added. You can now distinguish between ports that are disabled and have no links (LED shows brown) and ports that are disabled and have links (LED shows amber).
–In Cluster Manager, a Describe button was added to the Port Configuration window. When you select a single (or multiple) row and click Describe, the Basic Port Description window opens. In this window, you can specify the port description.
–Enhancements to the online help, which provide an index, a glossary, Back and Forward buttons for quick navigation within a set of topics, and a link to an online feedback form.
Limitations and Restrictions
You should review this section before you begin working with the switches. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
•Regardless of the switch model, only 64 possible instances of STP are supported.
•When connecting to the Catalyst 3524-PWR XL 10/100 inline-power ports, observe the following caution:
Caution It takes a Catalyst 3524-PWR XL 10/100 port up to 10 seconds to initially detect, power, and link to a Cisco IP Phone. If you disconnect the Cisco IP Phone before link has been established, you must wait 10 seconds before connecting another network device (other than another Cisco IP phone) to that switch port. Failure to do so can result in damage to that network device.
•The Cisco 600W Redundant Power System (RPS) supports all Catalyst 2900 and 3500 XL switches other than the Catalyst 3524-PWR XL switch to provide a quasi-redundant power source for four external devices that use up to 150W DC each. You can use a one-to-one cable (one connector at each end) to connect four external devices to the four DC output power modules. The power source is quasi-redundant because there are two AC input power modules for the Cisco RPS and one DC output power module for each external device. The AC input to the Cisco RPS is fully redundant, but the DC output to the external devices is not.
•The Cisco RPS 300 Redundant Power System supports the Catalyst 3524-PWR XL switch and provides redundancy for up to six connected devices until one of these devices requires backup power. If a connected device has a power failure, the RPS immediately begins supplying power to that device and sends status information to other connected devices that it is no longer available as a backup power source. As described in device documentation, when the RPS LED is amber, the RPS is connected but down. However, this might merely indicate that the RPS is in standby mode. Press the Standby/Active button on the RPS to put it into active mode. Refer to the RPS 300 Hardware Installation Guide for more information.
You can view RPS status through the CLI by using the show rps privileged EXEC command.
•You can connect the switch to a PC by using the switch console port and the supplied rollover cable and the DB-9 adapter. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) with this RJ-45-to-DB-25 female DTE adapter from Cisco.
•Certain combinations of port features create configuration conflicts. Refer to the section on "Managing Configuration Conflicts" in the Cisco IOS Desktop Switching Software Configuration Guide for a table that defines these conflicts.
•Host names and Domain Name System (DNS) server names that contain commas on a cluster command switch, member switch, or candidate switch can cause CMS to behave unexpectedly. You can avoid this instability in the interface by not using commas in host names or DNS names. Do not enter commas when also entering multiple DNS names in the IP Configuration tab of the IP Management window in CMS.
•The range of seconds for the span-tree max-age global configuration command is now 6 to 200 seconds. If you used this command in a release before 11.2(8)SA6 to set a value greater than this new range and then upgrade your software to Release 11.2(8.1)SA6 or later, the switch sets this value to the default: 20 seconds for IEEE STP and 10 seconds for IBM STP.
•When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is 50 percent oversubscribed for a sustained period of time, it will probably become congested. One or more of the ports being monitored might also experience a slowdown.
•When using the Software Image Management (SWIM) application in the Resource Manager Essentials (RME) suite of the CiscoWorks2000 product family to perform automated system software and boot loader upgrades, you should note the following:
–Catalyst 2900 series XL switches require Release 11.2(8)SA4 or later and RME version 2.1
or 2.2.
–Catalyst 3500 series XL switches require Release 11.2(8.1)SA6 or later and RME version 2.2.
•All Catalyst 3500 series XL and most Catalyst 2900 series XL switches support 250 VLANs. However, the Catalyst 2912 XL, Catalyst 2924 XL, and Catalyst 2924C XL support only 64 VLANs.
Important Notes
This section describes important information related to Release 12.0(5)XW.
•When you are configuring a cascaded stack of Catalyst 3500 XL switches using the GigaStack GBIC and want to include more than one VLAN in the stack, be sure to configure all of the GigaStack GBIC interfaces as trunk ports by using the switchport mode trunk interface configuration command and to use the same encapsulation method by using the switchport encapsulation {isl | dot1q} interface configuration command. For more information about these commands, refer to the command reference publication for your switch.
•Before upgrading your switch, read the "Documentation Updates" section for important information.
Caveats
Open Caveats
This section describes possible unexpected activity by Release 12.0(5)XW.
•If no spanning-tree [vlan stp-list] is specified in the configuration file, when the switch is reloaded, vlan stp-list is pruned even if there is an active link on the VLAN.
There is no workaround. (CSCds40442)
•The UniDirectional Link Detection (UDLD) protocol does not always detect a unidirectional link when there is a loop between the TX and RX strands on the same port (TX/RX loop condition).
This is an intermittent problem, and there is no workaround. (CSCds68177)
•When UDLD is enabled on a port group and a unidirectional link is detected on one port in the group, UDLD shuts down all members of the group instead of only the port experiencing the unidirectional link.
There is no workaround. (CSCds87929)
•If you select a switch in the tree by using Cluster Management and choose Console Baud Rate, the baud rate dialog appears with the selected switch in the Selected Device List. If you then click cancel and select Console Baud Rate again, two identical items for the same switch is listed.
There is no workaround. (CSCds86420)
•If multiple devices have the same host name, selecting one of these devices using the tree view in Cluster Manager selects all the devices with the same host name.
The workaround is to not use the same host name for multiple switches in the cluster. (CSCdr86448)
•If you connect two Catalyst 2924M XL switches through GBIC interfaces and then remove the cable, the GBIC LED remains green for up to 1 minute, even though the switches are not connected.
The workaround, if you need to reconnect the switches through their GBIC ports, is to wait until the green LED turns off, and then reconnect the switches. (CSCds89780)
•When two switches are connected by GigaStack GBICs and duplex mode is manually set to full duplex or to autonegotiate on both ends, the link sometimes will not stabilize.
If this occurs, the workaround is to remove and reinsert one of the GBICs. (CSCds84479)
•If you use Cluster Manager to choose Stack Area or Stack Bar graph types, the graph displays the data incorrectly.
The workaround is to use the graph types Line (default) or Bar to view the data. (CSCds54709)
•The c2900InfoRedundantPowerSupplyInfo MIB object returns the wrong values for some RPS-to-switch conditions for the RPS 300. When the RPS is connected and in Standby mode, the expected status is "connectedNotFunctional;" the status returned is "functionalPrimaryFailed." When the RPS is in the Active state and no connected switch is being backed up, the expected status is "connectedFunctional;" the status returned is "connectedNotFunctional."
There is no workaround. (CSCds82026)
•When you enter a show interface [interface-id] status privileged EXEC command for a WS-X2932-XL or GigaStack GBIC interface, the display shows Unknown in the interface Type field.
There is no workaround. This will be fixed in a future release. (CSCds82043)
•The DHCP server should contain reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool. If the switch gets configured from the dynamic IP pool, a duplicate or different IP address might be assigned. (CSCds58369)
•Cluster Management Suite requires a Java plug-in from Sun Microsystems. If you are using Internet Explorer and you disable Java plug-ins by using the Java Plug-In Control Panel, the initial Splash screen shows that the plug-in and Java are enabled, but Internet Explorer crashes.
The workaround is to not disable Java plug-ins on the Java Plug-In Control Panel. (CSCdp67822)
•If you right-click a device that is near the edge of the browser window, the second-level menu of the device pop-up menu might not display.
The workaround is to right-click again on the device until the pop-up menu displays correctly. (CSCdp61365)
•The Cluster Manager System Time Management window supports the configuration of the Network Time Protocol (NTP) and system time. When you make changes on this window from a command switch, Java propagates the changes to all cluster members. A conflict can arise if you configure NTP and also use the Set Daylight Saving Time and Set Current Time tabs.
To avoid a possible conflict, either set the system time for the entire cluster on the command switch, or configure NTP on the command switch to use an NTP server to provide time to the cluster. Do not use both methods at the same time. (CSCdp82224)
•You can use Cluster Manager to configure an Hot Standby Router Protocol (HSRP) standby group and bind it to a cluster. However, you cannot use Cluster Manager to configure more than one standby group. If you want to configure more than one standby group, use the CLI. (CSCdp82354)
•The serial port shares the same status bit for hardware flow control and for ready.
The workaround is to not use flow control on the console port. (CSCdm24487)
•When changing the management VLAN on a cluster with command-switch redundancy enabled, the cluster can break if HSRP is configured on any of the cluster members in the new management VLAN.
The workaround is to not change the management VLAN to a VLAN where a member is configured as part of a standby group. (CSCdp70389)
•Root guard is inconsistent when configured on a port that is in the STP blocked state at the time of configuration. (CSCdp85954)
•HSRP does not support entering a virtual MAC address or a built-in address (BIA) for a cluster. (CSCdp49419).
•All members of an HSRP standby group must be cluster members. (CSCdp97517)
• If a non-private VLAN edge port is configured to monitor a private VLAN edge port (to use SPAN), the SPAN port captures monitored traffic from the private VLAN edge port to other private VLAN edge ports. This happens even though the monitored private VLAN edge port is not forwarding traffic to other private VLAN edge ports. In effect, the SPAN port captures incorrect traffic.
The workaround is to not monitor private VLAN edge ports. (CSCdp84267)
•If the storm control filter is enabled for unicast, multicast, or broadcast traffic and the rising threshold is reached, all traffic on the port is filtered. No unicast, multicast, or broadcast traffic is forwarded from the port. (CSCdp30543)
•Cisco IOS does perform some checks on entered IP addresses. For example, it does not allow the broadcast address to be entered. However, it does not check for the broadcast address on the same subnet as the HSRP VIP or the management VLAN IP address. This means that you could configure HSRP with a virtual IP address that is the same as the network broadcast address.
There is no workaround. (CSCdp87748)
•If you use the command switch DNS server name to start CMS for a member that is running an earlier software release, CMS might not display the switch image, or it might display the command switch image. This can also occur when a standby group is configured for a cluster and you access CMS by entering the command-switch IP address and not the virtual IP address.
The workaround is to always use the command-switch IP address to access CMS. If a standby group is configured for a cluster, always use the virtual IP address to access CMS. (CSCdp75220)
•CMS can behave unexpectedly if host names or DNS server names that it processes contain commas. This means that host names or DNS server names on a cluster command switch, member, or neighbor can cause instability in the HTML interface.
The workaround is to not include commas in host names or DNS server names in CMS. (CSCdp85928)
•If you click the list of switches in CMS and press the Page Down key on the keyboard, the entire list moves to the bottom of the window. This only happens with Windows NT.
The workaround is to collapse the list into a single icon, which returns the list to the top of the window. (CSCdp62807)
•In VSM, you cannot see the individual menu items when you right-click the chassis image to display the device pop-up menu.
The workaround is to right-click another part of the chassis image to display the device pop-up menu. (CSCdp89945)
•When STP Port Fast or STP root guard are configured on a module port, the configuration is not saved after the module is removed and reinserted. These features need to be reconfigured on the module ports after the module is reinserted. (CSCdr04281)
Resolved Caveats
•You are no longer prompted twice for the enable password if you use the DNS name instead of the IP address to access a cluster. (CSCdp69639)
•After you enter the write erase privileged EXEC command on a Catalyst 2900 XL switch, the flash:config.text file is erased. Previously, the flash:config.text file was emptied but not erased, which prevented the switch from entering configuration mode when starting up. (CSCdr65397)
•You can use the mouse to correctly select ports with Cluster Manager. (CSCdr72702)
•Catalyst 2900 XL and 3500 XL switches no longer reload due to improper signaling on the console port. (CSCdr76698)
•IOS context-sensitive help no longer incorrectly lists
