Table Of Contents
Release Notes for the Catalyst 2900 XL and Catalyst 3500 XL Switches, Cisco IOS Release 12.0(5)WC5a
Browser and Java Plug-In Requirements
Cluster Requirements and Guidelines
Catalyst 2900 XL and Catalyst 3500 XL Switches
Catalyst 1900 and Catalyst 2820 Switches
Minimum Cisco IOS Release for Major Features
Port Security MAC Address Aging
Resolved IOS Caveats in Release 12.0(5)WC5a
Resolved IOS Caveats in Release 12.0(5)WC5
Resolved Cluster Configuration Caveat in Release 12.0(5)WC5
Installing the Required Plug-In
Displaying the CMS Access Page
Guidelines for Upgrading Switch Software
Overview of the Switch Upgrade Process
Determining the Switch Software Version
Which Software Files to Download from Cisco.com
Downloading the New Software and TFTP Server Application to Your Management Station
Copying the Current Startup Configuration from the Switch to a PC or Server
Using CMS to Upgrade One or More Switches
Recovering from an Incomplete CMS Software Upgrade
Using the CLI to Upgrade an 8-MB Catalyst 2900 XL Switch
Using the CLI to Upgrade a Catalyst 3500 XL Switch
Using the CLI to Upgrade Member Switches
Upgrading Catalyst 2900 XL or Catalyst 3500 XL Member Switches
Upgrading Catalyst 1900 or Catalyst 2820 Member Switches
Obtaining Technical Assistance
Release Notes for the Catalyst 2900 XL and Catalyst 3500 XL Switches, Cisco IOS Release 12.0(5)WC5a
August 2002
Cisco IOS Release 12.0(5)WC5a runs on the Catalyst 2900 series XL and Catalyst 3500 series XL switches with 8-MB CPU DRAM.
Note
This release is not for the Catalyst 2900 LRE XL switches. Do not install this release on the Long-Reach Ethernet (LRE) switches. For information about these switches, refer to Cisco IOS Release 12.0(5)WC4.
Note
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
•
•
You can download the switch software from these sites:
•
(for registered Cisco.com users with a login password)•
(for nonregistered Cisco.com users)This 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 releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This document has the following sections:
•
•
•
•
•
•
•
•
•
•
•
•
Hardware Requirements
This release supports the 8-MB Catalyst 2900 XL switches (see Table 1) and Catalyst 3500 XL switches (see Table 2).
Note
Note
Software Requirements
This section describes the requirements for the system and for the Cluster Management Suite (CMS) software.
System Requirements
These operating systems are supported for CMS management:
•
•
•
•
•
The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM. Table 3 lists the recommended platforms for using CMS.
Table 3 Recommended Minimum Platform Configuration for Web-Based Management
Windows NT 4.01
Pentium 300 MHz
128 MB
65,536
1024 x 768
Small
Solaris 2.5.1
SPARC 333 MHz
128 MB
Most colors for applications
-
Small (3)
1 Service Pack 3 or higher required
Browser and Java Plug-In Requirements
When starting a CMS session, the switch verifies the browser version to ensure that the browser is supported. If the browser is not supported, an error message appears, and the session does not start. Table 4 lists the browsers supported by CMS.
CMS requires the Java plug-ins described in the "Installing the Required Plug-In" section.
Table 4 Browser Requirements
Windows 95
4.61, 4.7
5.0, or 5.5
Windows 98
-2
5.0, or 5.5
Windows NT 4.0
4.61, 4.7
5.0, or 5.5
Windows 2000
4.61, 4.7
5.0, or 5.5
Solaris 2.5.1 or higher
4.61, 4.7
-3
1 Netscape Communicator version 4.60 and 6.0 are not supported. (CSCdx34982)
2 CMS is not supported on machines running Windows 98 and Netscape Navigator. The workaround is to use Microsoft Internet Explorer if your operating system is Windows 98. (CSCdx4997)
3 Microsoft Internet Explorer is not supported on Solaris 2.5.1 or higher.
Note
To access CMS, follow the procedures in the "Initial Switch Configuration" section.
Cluster Requirements and Guidelines
This section describes the hardware and software requirements for clustering Catalyst desktop switches.
Catalyst 2900 XL and Catalyst 3500 XL Switches
Some versions of switch 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 using the same software level, we recommend that you upgrade all cluster switches to the software release that supports the features that you want.
If you have a cluster with switches that are running different versions of switch 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 5 describes the Catalyst 2900 XL and Catalyst 3500 XL switches supported by this release and shows which switches can be command switches. All switches can function as standalone devices.
All Catalyst 2900 XL and Catalyst 3500 XL switches running Release 12.0(5.3)WC(1) and later are cluster-capable. All Catalyst 2900 XL modules are supported in cluster configurations.
We recommend that either the command switch has the latest software version installed if there switches in the cluster with older software versions or that all switches in the same platform be upgraded to the latest software version.
Note
Note
Table 5 Catalyst 2900 XL and Catalyst 3500 XL Switches as Cluster Members
Catalyst 2900 XL (4 MB of DRAM)1
No
No
Yes
Catalyst 2900 XL (8 MB of DRAM)
Yes
Yes
Yes
Catalyst 2900 LRE XL (16 MB of DRAM)
Yes
Yes
Yes
Catalyst 3500 XL
Yes
Yes
Yes
1 These switches can act as cluster members if they are running Release 11.2(8.x)SA6 original edition software. They can interoperate with this software release, but they cannot be upgraded to it.
Catalyst 3550 Switches
Catalyst 3550 switches running Release 12.0(4)EA1 or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 3550 switches.
Note
Catalyst 2950 Switches
Catalyst 2950 switches running Release 12.0(5)WC(1) or higher can be command and member switches. For more information, refer to the documentation for the Catalyst 2950 switches.
Note
Catalyst 1900 and Catalyst 2820 Switches
Table 6 lists the Catalyst 1900 and Catalyst 2820 switches and the minimum software release that they require to be cluster members. All Catalyst 2820 modules are supported in cluster configurations. For more information, refer to the documentation for the Catalyst 1900 and Catalyst 2820 switches.
Note
Table 6 Catalyst 1900 and Catalyst 2820 Switches as Cluster Members
Catalyst 1900
Yes
Yes
No
Catalyst 2820
Yes
Yes
No
Minimum Cisco IOS Release for Major Features
Table 7 lists the minimum software release required to support the major features of the Catalyst 2900 XL and Catalyst 3500 XL switches.
Table 7 Catalyst 2900 XL (including 2900 LRE XL) and Catalyst 3500 XL Features and the Minimum Cisco IOS Release Required
Port security MAC address aging
Release 12.0(5)WC5
Bridge protocol data unit (BPDU) guard
Release 12.0(5)WC5
Remote Authentication Dial-In User Service (RADIUS)
Release 12.0(5)WC5
UniDirectional Link Detection (UDLD) recovery
Release 12.0(5)WC5
Support for the Cisco Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules
Release 12.0(5)WC5
Enhanced web-based switch management (CMS)
Release 12.0(5)WC3
MAC address notification
Release 12.0(5)WC3
Internet Group Management Protocol (IGMP) filtering
Release 12.0(5)WC3
Extended cluster member compatibility with the Catalyst 2950 and Catalyst 3550 switches
Release 12.0(5)WC(1)
Multicast VLAN Registration (MVR)
Release 12.0(5)WC(1)
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 1000BASE-T GBIC module (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
WS-X2932-XL Catalyst 2900 XL 1-port 1000BASE-T module
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
VLAN Trunking Protocol (VTP) pruning
Release 12.0(5)XU
Change management Virtual LAN (VLAN) for a cluster
Release 12.0(5)XU
Private VLAN edge support
Release 12.0(5)XU
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
WS-C3548-XL switch with 48 10/100 ports
Release 12.0(5)XP
WS-X2931-XL Catalyst GigaStack GBIC module
Release 12.0(5)XP
Catalyst 3500 series XL switches (except WS-C3548-XL)
Release 11.2(8)SA6
Cluster management
Release 11.2(8)SA6
Terminal Access Control Access System Plus (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 1000BASE-X modules
Release 11.2(8)SA5
Catalyst 2900 series XL asynchronous transmission mode (ATM) modules
Release 11.2(8)SA5
IEEE 802.1Q trunking
Release 11.2(8)SA5
(Enterprise Edition Software)Inter-Switch Link (ISL) trunking
Release 11.2(8)SA4
(Enterprise Edition Software)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
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
New Features in this Release
This section describes the new features in this release.
New Hardware Support
Release 12.0(5)WC5 supports the Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules.
New Software Support
This section describes the new software features in this release.
Port Security MAC Address Aging
You can use port security aging to configure dynamic source MAC addresses that the switch learns and then drops when they are not in use. The aging time parameter defines how long the switch retains unseen addresses in the MAC address table.
BPDU Guard
The bridge protocol data unit (BPDU) guard feature shuts down Port Fast-enabled interfaces that receive BPDUs rather than putting the interfaces into the blocking state. The BPDU guard feature provides a secure response to invalid configurations because you must manually put the interface back in service.
RADIUS Authentication Support
Remote Authentication Dial-In User Service (RADIUS) secures networks against unauthorized access. RADIUS clients run on supported Cisco routers and switches and send authentication requests to a central RADIUS server, which contains all user authentication and network service access information.
UDLD Errdisable Enhancement
You can use the UniDirectional Link Detection (UDLD) Errdisable Enhancement to configure a timeout period for error-disabled ports, after which the ports are re-enabled automatically. This eliminates the need to manually re-enable all the ports. This errdisable and re-enable cycle continues until the error condition is gone.
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.
•
•
•
Caution
•
•
•
Caution
Beginning in user EXEC mode, follow these steps to verify and reset the VTP configuration revision number on a switch before adding it to a VTP domain.
After resetting the configuration revision number, add the switch to the VTP domain.
Note
•
•
•
•
–
–
Open Caveats
These are the open caveats in this release:
Open IOS Caveats
These are the severity 3 IOS configuration caveats:
•
A switch that is running cross-stack UplinkFast cannot undergo a fast transition and must use the usual slow spanning tree transition stages.
There is no workaround.
•
When you are using a terminal program to Telnet from a PC into the console port of a switch, and TACACS+ is running on that PC, the switch fails, and you lose your Telnet connection when you enter switch commands from the PC.
The workaround is to run TACACS+ on a terminal server instead of on the PC.
•
A switch that is running Release 12.0(5)WC3b and is configured as a cluster commander does not display correct SNMP port information about cluster members.
The workaround is to downgrade the cluster commander to Release 12.0(5)WC3. Other switches in the cluster can continue running Release 12.0(5)WC3b.
Open CMS Caveats
These are the severity 3 CMS configuration caveats:
•
CMS does not work reliably on machines running Windows 98 and Netscape Navigator.
The workaround is to use Microsoft Internet Explorer.
•
If a switch is running CMS for 2 to 3 days, and the switch is low on memory, the switch fails with an out of memory error.
The workaround is to close the browser and relaunch CMS.
•
CMS does not support Netscape Navigator 6.0.
The workaround is to use a supported version of Netscape Navigator.
Resolved Caveats
These caveats were resolved in these releases:
•
•
•
Resolved IOS Caveats in Release 12.0(5)WC5a
These IOS caveats were resolved in Release 12.0(5)WC5a:
•
The Network Time Protocol (NTP) handling is improved.
•
The authentication, authorization, and accounting (AAA) authentication process has been corrected.
•
You can use CiscoWorks to upgrade Catalyst 2900 XL and 3500 XL switches to Release 12.0(5)WC5a. (The internal files for Release 12.0(5)WC5 did not follow Cisco file-naming conventions.)
•
A switch no longer unexpectedly reboots when Cisco Group Management Protocol (CGMP) join requests and spanning tree protocol (STP) topology change notices (TCNs) are processed at the same time.
•
A switch no longer fails when you use the mac-address-table static global configuration command to configure a static multicast entry.
•
When a switch that has inline power devices connected to it is restarted, those devices now power up correctly.
•
MAC address flapping no longer occurs between Fast EtherChannel ports on a switch.
•
When a 1000BASE-T Gigabit Interface Converter (GBIC) is inserted into a port that has been administratively shut down, the switch correctly recognizes the GBIC as a 1000BASE-T GBIC.
•
Memory allocation errors no longer occur on switches that have a large number of VLANS or SNMP community strings configured.
•
A link-up trap is now generated for a VLAN interface.
•
The media-type interface command has been removed.
•
The exception dump global configuration command has been removed.
•
When CGMP Leave is enabled on a switch, the management VLAN on that switch no longer responds to ping requests from outside VLANs.
•
The show cdp neighbors privileged EXEC command now displays device names that are longer than 17 characters in the Device ID field.
•
The %CDP-4-DUPLEX_MISMATCH: duplex mismatch error message is no longer displayed when ISL trunking connects a Catalyst 3524-PWR XL to a Cisco router or another Catalyst switch.
•
When you move a Cisco IP phone from one switch port to another, multiple Cisco Discovery Protocol (CDP) entries for that IP phone are no longer displayed.
Resolved IOS Caveats in Release 12.0(5)WC5
These IOS caveats were resolved Release 12.0(5)WC5:
•
When a GigaStack GBIC module is inserted into the GBIC slot of a switch, the switch no longer displays a value of 1, which is the value for not specified.
•
After disconnecting and reconnecting the console rollover cable, the console session no longer freezes.
•
You can now set the Spanning Tree Protocol (STP) priority to 32768 when cross-stack UplinkFast is enabled.
•
When a switch is configured as a cluster commander and it does not have the address for an outgoing packet in its MAC address table, it now sends the packet out the default gateway instead of sending an ARP request for a nonlocal address.
•
When there are two uplinks to a switch and the root port and nonroot port are sequentially brought down, the other uplink that is in the blocking state no longer takes more than 10 seconds to go into the learning state.
•
When you are connected through a Telnet session and enter a show USER exec command that causes many pages of output to display, holding the space bar down does not halt the session.
•
When you shut down one Fast EtherChannel (FEC) port, the other ports also shut down.
•
Recovery when power cycling a root switch when running cross-stack UplinkFast is not going to go through faster convergence.
•
It is no longer necessary to disable SNMP in order to receive a ping response from the switch.
•
It is no longer necessary to enable STP to return the correct MAC address in the dot1dBaseBridgeAddress MIB variable.
•
Release 12.0(5)WC5 supports the Coarse Wave Division Multiplexing (CWDM) Gigabit Interface Converter (GBIC) modules.
•
You can use the UniDirectional Link Detection (UDLD) errdisable enhancement to configure a timeout period for error-disabled ports. After the timeout period, the ports are automatically re-enabled.
•
When you have multiple VLANs configured, you no longer need to reload a switch to reconnect the first VLAN in the list.
•
A switch no longer fails when trying to collect or send authentication, authorization, and accounting (AAA) data.
•
Entering this sequence no longer causes a switch to reload:
switch(config)#aaa new-modelswitch(config)#aaa group server tacacs+ test1switch(config-sg-tacacs+)#exitswitch(config)#aaa group server radius test2switch(config)#aaa group server radius test1•
A switch no longer fails when an extended ping operation is used with the loose and strict options enabled.
Resolved Cluster Configuration Caveat in Release 12.0(5)WC5
This cluster caveat was resolved in Release 12.0(5)WC5:
•
Switch cluster members now provide reliable SNMP information from Cisco Building Broadband Service Manager (BBSM) products.
Important Notes
This section describes important information related to this release.
•
•
•
Documentation Notes
•
–
–
–
•
When you start the switch, the switch automatically requests configuration information from a DHCP server only if a configuration file is not present on the switch.
DHCP autoconfiguration does not occur under these conditions:
–
–
•
•
•
•
Japan
This is a Class A product based on the standard of the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). If this equipment is used in a domestic environment, radio disturbance may arise. When such trouble occurs, the user may be required to take corrective actions.
Korea
Hungary
This equipment is a Class A product and should be used and installed properly according to the Hungarian EMC Class A requirements (MSZEN55022). Class A equipment is designed for typical commercial establishments for which special conditions of installation and protection distance are used.
Figyelmeztetés a felhasználói kézikönyv számára:
Ez a berendezés "A" osztályú termék, felhasználására és üzembe helyezésére a magyar EMC "A" osztályú követelményeknek (MSZ EN 55022) megfeleloen kerülhet sor, illetve ezen "A" osztályú berendezések csak megfelelo kereskedelmi forrásból származhatnak, amelyek biztosítják a megfelelo speciális üzembe helyezési körülményeket és biztonságos üzemelési távolságok alkalmazását.Initial Switch Configuration
This section provides these procedures:
•
•
•
This section assumes that you have already installed the switch and connected devices to it, as described in the switch hardware installation guide.
Using the Setup Program
You can use an automatic setup program to assign switch IP information, host and cluster names, and passwords and to create a default configuration for continued operation. Later, you can use CMS or the command-line interface (CLI) to customize your configuration. To run the setup program, access the switch from the PC terminal that you connected to the console port. For information about connecting a PC or terminal to the switch console port, refer to the switch hardware installation guide.
Note
The first time that you access the switch, it runs a setup program that prompts you for IP and other configuration information necessary for the switch to communicate with local routers and the Internet. This information is also required if you plan to use CMS to configure and manage the switch.
You will need the following information from your system administrator:
Use this procedure to create an initial configuration for the switch:
Note
At any point you can enter a question mark for help. Use Ctrl-C to stop the configuration dialog at any prompt. The default settings are in square brackets.
Step 1
Continue with configuration dialog? [yes/no]: yStep 2
Enter IP address: ip_addressStep 3
Enter IP netmask: ip_netmaskStep 4
Would you like to enter a default gateway address? [yes]: yStep 5
IP address of the default gateway: ip_address
Note
Note
Step 6
Note
Enter enable secret: secret_passwordStep 7
Would you like to configure a Telnet password? [yes] y
Note
Step 8
Enter Telnet password: telnet_passwordStep 9
Note
Would you like to enable as a cluster command switch? yStep 10
Enter cluster name: cls_name
Note
Step 11
The following configuration command script was created: ip subnet-zero interface VLAN1 ip address 172.20.153.36 255.255.255.0 ip default-gateway 172.20.153.01 hostname host_name enable secret 5 $1$M3pS$cXtAlkyR3/6Cn8/ line vty 0 15 password telnet_password snmp community private rw snmp community public ro cluster enable cls_name endStep 12
•
•
Use this configuration? [yes/no]: yAfter you complete the setup program, the switch can use the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•
•
The switch software configuration guide provides more information about how to set a password to protect the switch against unauthorized Telnet access and how to access the switch if you forget the password.
Installing the Required Plug-In
A Java plug-in is required for the browser to access CMS. Download and install the plug-in before you start CMS. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the "Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users" section and the "Solaris Platforms" section.
You can download the recommended plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
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 these settings:
In the Proxies tab, verify that the Use browser settings is checked and that no proxies are enabled.
Note
From the Start menu, disable the options by selecting Start > Programs > Network Associates > Virus Scan Console > Configure.
or
From the taskbar, right-click the Virus Shield icon, and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan.
Windows 95, Windows 98, and Windows NT 4.0, and Windows 2000 Users
These Java plug-ins are supported on the Windows platform:
•
•
•
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Solaris Platforms
These Java plug-ins are supported on the Solaris platform:
Caution
•
•
•
If you have a SmartNet contract, you can download these plug-ins and instructions from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
To install the Java plug-in, follow the instructions in the README_FIRST.txt file.
If you do not have a SmartNet contract, download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1
http://10.1.126.45:184/level/14/where 10.1.126.45 is the switch IP address, 184 is the HTTP port, and level/14 is the privilege level. You do not need to enter the HTTP port if the switch is using HTTP port 80 (the default) or enter the privilege level if you have read-write access to the switch (privilege level is 15).
For information about the HTTP port and privilege levels, refer to the switch software configuration guide.
Step 2
If you configure a local username and password, make sure you enable it by using the ip http authentication global configuration command. Enter your username and password when prompted.
Step 3
If you access CMS from a standalone or member switch, Device Manager appears. If you access CMS from a command switch, you can display the Front Panel and Topology views.
For complete information about CMS, refer to the switch software configuration guide.
Upgrading the Switch Software
This section provides topics about upgrading the switch software:
•
•
•
•
•
•
•
•
•
•
Note
Guidelines for Upgrading Switch Software
Note
When upgrading the switch software, follow these rules:
•
•
•
–
–
•
•
•
Overview of the Switch Upgrade Process
The software upgrade procedure has these major steps:
•
•
The tar command extracts the IOS image and the HTML files from the .tar file during the TFTP copy to the switch.
•
When you upgrade a switch, the switch continues to operate while the new software is copied to Flash memory. If Flash memory has enough space, the new image is copied to the selected switch but does not replace the running image until you reboot the switch.
Note
If Flash memory does not have enough space for two images, your new image is copied over the existing one.
Note
•
–
–
Features provided by the new software are not available until you reload the switch.
Determining the Switch Software Version
The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the HTML files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version user EXEC command to see the software version that is running on your switch. For example:
3500-239-34> show versionCisco Internetwork Operating System SoftwareIOS (tm) C3500xl Software (C3500xl-C3H2S-M), Version 12.0(0.0.2)WC5, RELEASE SOFT)
Copyright (c) 1986-2002 by cisco Systems, Inc.Compiled Tue 14-May-02 12:57 by antoninoImage text-base: 0x00003000, data-base: 0x0034A3B8You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that might be stored in Flash memory.
Note
Which Software Files to Download from Cisco.com
New software releases are posted on Cisco.com and are also available through authorized resellers. From Cisco.com, you can also download a TFTP server application to copy the switch software from your PC to the switch.
Table 8 describes the file extensions and what they mean for the upgrade procedure. Table 9 and Table 10 list the software files that you need from Cisco.com.
Downloading the New Software and TFTP Server Application to Your Management Station
Follow these steps to download the new software and, if necessary, the TFTP server application, from Cisco.com to your management station:
Step 1
Step 2
If you have a SmartNet support contract, go to one of these 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, go to one of these URLs, and download the appropriate files:
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat2900XL
http://www.cisco.com/pcgi-bin/tablebuild.pl/cat3500XL
Step 3
The readme.txt file describes how to download the TFTP server application. New features provided by the software are not available until you reload the software.
Copying the Current Startup Configuration from the Switch to a PC or Server
When you make changes to a switch configuration, your changes become part of the running configuration. When you enter the command to save those changes to the startup configuration, the switch copies the configuration to the config.text file in Flash memory. To ensure that you can recreate the configuration if a switch fails, you might want to copy the config.text file from the switch to a PC or server.
The following procedure requires a configured TFTP server such as the Cisco TFTP server available on Cisco.com.
Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the PC or server that has the TFTP server application:
Step 1
switch# copy flash:config.text tftpStep 2
Address or name of remote host []? ip_addressStep 3
Destination filename [config.text]? yes/noStep 4
Using CMS to Upgrade One or More Switches
You can use the Software Upgrade window in Cluster Manager to upgrade all or some of the switches in a cluster at once. Consider these conditions when doing an upgrade:
•
–
–
•
Follow these steps to use CMS to upgrade switch software. Refer to the online help for more details.
Step 1
Step 2
You can enter just the filename or a pathname into the New Image File Names field. You do not need to enter a pathname if the image file is in the directory that you have defined as the TFTP root directory.
Note
Note
On the Catalyst 2900 XL and Catalyst 3500 XL switches, new images are copied to Flash memory and do not affect operation. The switch checks Flash memory to ensure that there is sufficient space before the upgrade takes place. If there is enough space, the new image is copied to the switch without replacing the old image, and after the new image is completely downloaded, the old one is erased. In this case, you can still reboot your switch by using the old image if a failure occurs during the copy process.
If there is not enough space in Flash memory for the new and old images, the old image is deleted, and the new image is downloaded.
On the Catalyst 1900 and Catalyst 2820 switches, the new image overwrites the current image during the upgrade.
Note
Recovering from an Incomplete CMS Software Upgrade
An upgrade failure can create multiple copies of IOS images and other files in Flash memory. This would not leave enough space for the HTML files to also be copied to Flash memory; thus, you will not be able to access the switch through CMS.
If a failure occurs, ensure that the image file in Flash memory has the same name as the contents of the boot variable:
•
•
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 "Using the CLI to Upgrade Member Switches" section.
Using the CLI to Upgrade an 8-MB Catalyst 2900 XL Switch
Caution
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 privileged EXEC command with these results:
•
•
•
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 privileged EXEC command to start a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter a password if you are prompted to do so.
Step 4
switch# show versionCisco 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 paulinesImage text-base: 0x00003000, data-base: 0x00202144ROM: Bootstrap program is C2900XL boot loader2900XL-EN-84.3 uptime is 1 day, 22 hours, 23 minutesSystem restarted by power-onRunning default softwarecisco WS-C2924-XL (PowerPC403GA) processor (revision 0x11)Processor board ID 0x0E, with hardware revision 0x01Last reset from power-onProcessor is running Enterprise Edition Software24 Ethernet/IEEE 802.3 interface(s)32K bytes of flash-simulated non-volatile configuration memory.Base ethernet MAC Address: 00:50:80:39:EC:40Motherboard assembly number: 73-3382-04Power supply part number: 34-0834-01Motherboard serial number: FAA02499G7XModel number: WS-C2924-XL-ENSystem serial number: FAA0250U03PConfiguration register is 0xFStep 5
switch# show bootIf there is no file defined in the BOOT path-list, enter the dir flash: privileged EXEC command to display the contents of Flash memory. For example, the file named c2900XL-c3h2-mz-120-5.3.WC.1.bin is the image file.
c2900XL-c3h2-mz-120-5.3.WC.1.binswitch# dir flash:Directory of flash:/4 d--x 6848 Apr 04 1993 15:23:11 html6 -rwx 79 Apr 04 1993 15:20:34 env_vars5 ---x 106 Apr 04 1993 15:20:36 info68 -rwx 1399 May 16 2000 14:43:42 config.text259 ---x 106 Apr 04 1993 15:23:12 info.ver3612672 bytes total (940032 bytes free)Step 6
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.3.WC.1.bin Source filename [c2900XL-h2-mz-112.8.2-SA6.bin]? Destination filename [c2900XL-c3h2s-mz-120-5.3.WC.1.bin]?Step 7
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 8
switch(config)# no IP http serverStep 9
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c2900XL-c3h2s-mz-120-5.3.WC.1.bin
Note
Step 10
switch(config)# endStep 11
switch# delete flash:html/*Step 12
Step 13
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
Step 14
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.3.WC.1.bin (1557286 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)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 privileged command.
Step 15
switch# configure terminal Enter configuration commands, one per line. End with CNTL/Z.Step 16
switch(config)# IP http serverStep 17
switch(config)# endStep 18
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 19
Your Telnet session ends when the switch resets.
Step 20
Using the CLI to Upgrade a Catalyst 3500 XL Switch
This procedure is 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 privileged EXEC command, with these results:
•
•
•
Follow these steps to upgrade the switch software by using a TFTP transfer:
Step 1
Step 2
To start a Telnet session on your PC or workstation, enter this command:
server% telnet switch_ip_addressEnter the Telnet password if you are prompted to do so.
Step 3
switch> enable switch#Enter the password if you are prompted to do so.
Step 4
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
Step 6
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.3.WC.1.binStep 7
switch# dir flash: Directory of flash:/3 -rwx 415 Jun 13 1993 05:15:37 placement.txt4 d--x 6848 May 03 2000 10:47:58 html70 -rwx 20 Mar 21 1993 09:17:03 prefs.text6 ---x 106 Mar 01 1993 21:56:52 info228 ---x 106 Apr 04 1993 15:17:54 info.ver69 -rwx 2188 Mar 13 1993 03:38:28 config.text230 -rwx 744 Mar 25 1993 19:16:46 vlan.dat115 -rwx 354 Mar 13 1993 04:17:15 env_vars3612672 bytes total (936960 bytes free)Step 8
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 9
switch(config)# no IP http serverStep 10
switch(config)# boot system flash:new_imageFor example:
switch(config)# boot system flash:c3500XL-c3h2s-mz-120-5.3.WC.1.bin
Note
Step 11
switch(config)# endStep 12
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Caution
Step 13
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.3.WC.1.bin (1271095 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)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 privileged EXEC command.
Step 14
switch# config terminal Enter configuration commands, one per line. End with CNTL/Z.Step 15
switch(config)# IP http serverStep 16
switch(config)# endStep 17
switch# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Step 18
Your Telnet session ends when the switch resets.
Step 19
Using the CLI to Upgrade Member Switches
Because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch.
This section provides these procedures:
•
•
Upgrading Catalyst 2900 XL or Catalyst 3500 XL Member Switches
Follow these steps to upgrade the software on a Catalyst 2900 XL or Catalyst 3500 XL member switch:
Step 1
switch# show cluster membersFrom the display, select the number of the member switch that you want to upgrade. The member number is in the SN column of the display. You need this member number for Step 2.
Step 2
switch# rcommand 1Step 3
switch-1# tar /x tftp://server_ip_address/path/filename.tar flash:Source IP address or hostname [server_ip_address]? Source filename [path/filename]? Destination filename [flash:new_image]? Loading /path/filename.bin from server_ip_address (via!) [OK - 843975 bytes]Step 4
switch-1# reload System configuration has been modified. Save? [yes/no]:y Proceed with reload? [confirm]Press Enter to start the download.
You lose contact with the switch while it reloads the software. For more information on the rcommand privileged EXEC command, refer to the switch command reference.
Upgrading Catalyst 1900 or Catalyst 2820 Member Switches
Follow these steps to upgrade the software on a Catalyst 1900 or Catalyst 2820 member switch:
Step 1
switch# show cluster membersFrom the display, select the number of the member switch that you want to upgrade. The member number is in the SN column of the display. You need this member number for Step 2.
Step 2
switch# rcommand 1Step 3
The Telnet session accesses the menu console (the menu-driven interface) if the command switch password is privilege level 15. If the command switch password is privilege level 1, you are prompted for the password.
You lose contact with the switch while it reloads the software.
Step 4
switch-1# copy tftp://host/src_file opcodeFor example, copy tftp://spaniel/op.bin opcode downloads new system operational code op.bin from the host spaniel.
When the download is complete, the TFTP successfully downloaded operational code message appears, and the switch resets and begins using the new software.
You can also upgrade the switch software through the Firmware Configuration menu from the menu console. For more information, refer to the installation and configuration guide that shipped with your switch.
You lose contact with the switch while it reloads the software.
Related Documentation
You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Ordering Documentation" section.
These publications provide more information about the switches and the switch software:
•
•
•
•
•
•
•
•
•
•
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•
http://www.cisco.com/public/ordsum.html
•
http://www.cisco.com/go/subscription
•
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or Email option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•
•
•
•
•
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•
•
•
•
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, Internet Quotient, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0206R)
Copyright © 1998-2002, Cisco Systems, Inc.
All rights reserved.
Guest
