Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco Catalyst 2950 Series Switches

Release Notes for the Catalyst 2950 and Catalyst 2955 Switches, Release 12.1(13)EA1c

Downloads

Table Of Contents

Release Notes for the Catalyst 2950 and Catalyst 2955 Switches
Cisco IOS Release 12.1(13)EA1c

Contents

System Requirements

Hardware Supported

Hardware Not Supported

Software Compatibility

Recommended Platform Configuration for Web-Based Management

Operating System and Browser Support

Guidelines for Installing and Enabling the Java Plug-In

Installing the Required Plug-In

Creating Clusters with Different Releases of Cisco IOS Software

Downloading Software

Guidelines for Downloading Switch Software

Determining the Software Version and Feature Set

Which Files to Use

Upgrading a Switch by Using CMS

Upgrading a Switch by Using the CLI

Downloading the Software and TFTP Server Application

Copying the Current Startup Configuration from the Switch to a PC or Server

Using the CLI to Upgrade a Catalyst 2950 or Catalyst 2955 Switch

Upgrading Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches

Upgrading Catalyst 1900 or Catalyst 2820 Member Switches

Recovering from Software Failure

Installation Notes

Setting Up the Catalyst 2950 or Catalyst 2955 Initial Configuration

Accessing CMS

Configuring the HTTP Server

Displaying CMS

New Features

New Hardware Features

New Software Features

Limitations and Restrictions

Cisco IOS Limitations

Crypto Software Image Guidelines

Immediate-Leave Limitation

RSPAN Limitation

ACL Limitations

CMS Limitations and Restrictions

Hardware and Software Compatibility Matrixes

Port Configuration Conflicts

SPAN Limitation

Important Notes

Cisco IOS Notes

CMS Notes

Read-Only Mode in CMS

Configuring CMS

VLAN Notes

IGMP Filtering

Open Caveats

Open Cisco IOS Caveats

Open Cluster Configuration Caveat

Open CMS Caveats

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.1(13)EA1c

Caveats Resolved in Cisco IOS Release 12.1(13)EA1b

Caveats Resolved in Cisco IOS Release 12.1(13)EA1

CMS Caveats Resolved in Cisco IOS Release 12.1(13)EA1

Documentation Updates

Corrections to the Catalyst 2950 Desktop Switch Hardware Installation Guide

Corrections to the Catalyst 2955 Hardware Installation Guide

Switch and Alarm Circuit Warning

DC Circuit Power Warning

Switch Operating Range Warning

Relay Wires Warning

Substitution of Components Warning

"Open Type" Equipment Warning

Switch Functional Ground Lug Warning

Switch Operation Warning

Ambient Temperature of 140°F Warning

Suitable Enclosure Warning

Twisted-Pair Supply Wires Warning

Pollution Degree 2 Warning

Class I, Division 2 Warning

Power to the Switch Warning

Related Documentation

Obtaining Documentation

Cisco.com

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Cisco TAC Website

Cisco TAC Escalation Center

Obtaining Additional Publications and Information


Release Notes for the Catalyst 2950 and Catalyst 2955 Switches
Cisco IOS Release 12.1(13)EA1c

June 2003

The Cisco IOS Release 12.1(13)EA1c runs on Catalyst 2950 and Catalyst 2955 switches.

These release notes include important information about this Cisco IOS release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:

•If you are installing a new switch, refer to the Cisco IOS release label on the rear panel of your switch.

•If your switch is running, you can use the show version user EXEC command. See the "Determining the Software Version and Feature Set" section.

•If you are upgrading to a new release, refer to the software upgrade filename for the Cisco IOS version.

For the complete list of Catalyst 2950 and Catalyst 2955 switch documentation, see the "Related Documentation" section.

You can download the switch software from these sites:

•http://www.cisco.com/public/sw-center/sw-lan.shtml

(for registered Cisco.com users with a login password)

•http://www.cisco.com/public/sw-center/sw-lan.shtml

(for nonregistered Cisco.com users)

This software 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 Cisco IOS releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.

Note This software release does not support the Catalyst 2950 LRE switches. For information about these switches, refer to the Catalyst 2950 LRE release notes.

Contents

This information is in the release notes:

•"System Requirements" section

•"Downloading Software" section

•"Installation Notes" section

•"New Features" section

•"Limitations and Restrictions" section

•"Important Notes" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Documentation Updates" section

•"Related Documentation" section

•"Obtaining Documentation" section

•"Obtaining Technical Assistance" section

System Requirements

The system requirements for this Cisco IOS release are described in these sections:

•"Hardware Supported" section

•"Hardware Not Supported" section

•"Software Compatibility" section

Hardware Supported

The Catalyst 2950 switch is supported by either the standard software image (SI) or the enhanced software image (EI). The Catalyst 2955 switch is supported by the EI only.

The EI provides a richer set of features, including access control lists (ACLs), enhanced quality of service (QoS) features, extended-range VLANs, the IEEE 802.1W Rapid Spanning Tree Protocol (RSTP), and the IEEE 802.1S Multiple STP (MSTP). The enhanced crypto software image supports the Secure Shell (SSH) protocol.

For information about the software releases that support the switches listed in Table 1, see the "Limitations and Restrictions" section.

Each Catalyst 2950 switch has one fan. The Catalyst 2955 switches do not have fans.

Table 1 lists the hardware supported by this release:

Table 1 Hardware Supported 

Hardware
Software Image
Description

Catalyst 2950-12

SI

12 fixed autosensing 10/100 Ethernet ports

Catalyst 2950-24

SI

24 fixed autosensing 10/100 Ethernet ports

Catalyst 2950C-24

EI

24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports

Catalyst 2950G-12-EI

EI

12 fixed autosensing 10/100 Ethernet ports and 2 GBIC1 module slots

Catalyst 2950G-24-EI 

EI

24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots

Catalyst 2950G-24-EI-DC

EI

24 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots with DC-input power

Catalyst 2950G-48-EI

EI

48 fixed autosensing 10/100 Ethernet ports and 2 GBIC module slots

Catalyst 2950SX-24

SI

24 fixed autosensing 10/100 Ethernet ports and 2 1000BASE-SX ports

Catalyst 2950T-24

EI

24 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports2

Catalyst 2955C-12

EI

12 fixed autosensing 10/100 ports and 2 multimode (MM) 100BASE-FX ports

Catalyst 2955S-12

EI

12 fixed autosensing 10/100 ports and 2 single-mode (SM) 100BASE-LX ports

Catalyst 2955T-12

EI

12 fixed autosensing 10/100 ports and 2 10/100/1000 Ethernet ports3

GBIC Modules

—

•1000BASE-SX GBIC

•1000BASE-LX/LH GBIC

•1000BASE-ZX GBIC

•1000BASE-T GBIC (model WS-5483)

•CWDM4 fiber-optic GBIC5

•GigaStack GBIC

Redundant power system

—

•Cisco RPS 300 Redundant Power System

•Cisco RPS 675 Redundant Power System

1 GBIC = Gigabit Interface Converter

2 The 10/100/1000 ports on the Catalyst 2950 switch operate only in full-duplex mode.

3 The 10/100/1000 ports on the Catalyst 2955T-12 switch operate at 10 or 100 Mbps in either full- or half- duplex mode and at 1000 Mbps only in full-duplex mode.

4 CDWM = Coarse Wave Division Multiplexer

5 This feature is only supported when your switch is running the EI.

5 The Catalyst 2955 switch is designed to operate with one or two power supplies. Each power supply input has an associated LED that shows the power supply status. If you use the Catalyst 2955 switch with a single power supply, the LED for the empty secondary power supply input is red.

If you prefer that the LED for the empty power supply input not be red, connect jumper wires from the primary power supply input connections to the empty input connections for the secondary power supply. After making those connections, the secondary power supply status LED will also show primary power supply status.


Hardware Not Supported

Table 2 lists the hardware that is not supported by this release:

Table 2 Hardware Not Supported

Hardware
Description

GBIC module

1000BASE-T GBIC (model WS-G4582)

Redundant power system

Cisco RPS 600 Redundant Power System


Software Compatibility

These are the software compatibility requirements for this Cisco IOS release:

•"Recommended Platform Configuration for Web-Based Management" section

•"Operating System and Browser Support" section

•"Installing the Required Plug-In" section

•"Creating Clusters with Different Releases of Cisco IOS Software" section

Recommended Platform Configuration for Web-Based Management

Table 3 lists the recommended platforms for web-based management.

Table 3 Recommended Platform Configuration for Web-Based Management

OS
Processor Speed
DRAM
Number of Colors
Resolution
Font Size

Windows NT 4.01

Pentium 300 MHz

128 MB

65,536

1024 x 768

Small

Solaris 2.5.1 or higher

SPARC 333 MHz

128 MB

Most colors for applications

—

Small (3)

1 Service Pack 3 or higher is required.


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.

For information about supported operating systems, see the next section.

Operating System and Browser Support

You can access the web-based interfaces by using the operating systems and browsers listed in Table 4. 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 4 Supported Operating Systems and Browsers

Operating System
Minimum Service Pack or Patch
Netscape Communicator1
Microsoft Internet Explorer2

Windows 98

Second Edition

4.75, 6.22, or 6.23

5.5 or 6.0

Windows NT 4.0

Service Pack 3 or later

4.75, 6.22, or 6.23

5.5 or 6.0

Windows 2000

None

4.75, 6.22, or 6.23

5.5 or 6.0

Windows XP

None

4.75, 6.22, or 6.23

5.5 or 6.0

Solaris 2.5.1 or later

Sun-recommended patch cluster for the OS and Motif library patch 103461-24

4.75, 6.22, or 6.23

Not supported

1 Netscape Communicator version 6.0 is not supported.

2 Service Pack 1 or higher is required for Internet Explorer 5.5.


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 mean 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).

Note In Cluster Management displays, Internet Explorer versions 4.01 and 5.0 might not display edge devices that are not connected to the command switch. Other functionality is similar to that of Netscape Communicator.

Guidelines for Installing and Enabling the Java Plug-In

If CMS does not launch automatically, you might not have a supported Java plug-in installed or the Java plug-in might not be enabled. CMS does not automatically detect if a supported Java plug-in is installed. If you start CMS without the required Java plug-in installed, the CMS splash screen remains open, and CMS will not launch.

To make sure that a supported Java plug-in is correctly installed and enabled, follow these guidelines:

•If you are using a supported browser and are connected to the Internet, click the Java plug-in link to download and install a supported Java plug-in.

•If you have installed the Java plug-in but CMS still does not launch, make sure that the plug-in is enabled by clicking Start > Settings > Control Panel > Java Plug-in. Click the Basic tab, select Enable Java Plug-In, and click Apply.

•To verify that a supported version of the Java plug-in is installed, click Start > Settings > Control Panel. The Java plug-in is listed with the version number in the Control Panel menu.

Installing the Required Plug-In

A Java plug-in is required for the browser to access and run the Java-based Cluster Management Suite (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 XP, Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Plug-Ins" section and the "Solaris Plug-Ins" section.

You can download the recommended plug-ins from this URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java

Note Uninstall any older versions of the Java plug-ins before installing the new Java plug-in.

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 If you are running an Internet virus checker on Windows 2000 and the plug-in takes a long time to load, you can speed up CMS operation by disabling the virus checker filter option or download option or both.

On McAfee VirusScan, from the Start menu, to disable the VirusScan Internet Filter option, the Download Scan option, or both, select 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 XP, Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Plug-Ins

These Java plug-ins are supported in the Windows environments:

•Java plug-in 1.4

•Java plug-in 1.3.1

You can download these plug-ins from this URL:

http://www.cisco.com/pcgi-bin/tablebuild.pl/java

Solaris Plug-Ins

These Java plug-ins are supported on the Solaris platform:

•Java plug-in 1.4

•Java plug-in 1.3.1

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.

Creating Clusters with Different Releases of Cisco IOS Software

When a cluster consists of Catalyst 3550 switches and a mixture of other Catalyst switches, we strongly recommend using only the Catalyst 3550 switches as the command and standby command switches. When the command switch is a Catalyst 3550 switch, all standby command switches must also be Catalyst 3550 switches. The Catalyst 3550 switch that has the latest software should be the command switch.

If your cluster has Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, and Catalyst 3500 XL switches, the Catalyst 2950 or Catalyst 2955 switch should be the command switch. The Catalyst 2950 or Catalyst 2955 switch that has the latest software should be the command switch.

If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL should be the command switch. The Catalyst 2900 or 3500 XL switch that has the latest software should be the command switch.

Table 5 lists the cluster capabilities and software versions for the switches.

Table 5 Switch Software and Cluster Capability 

Switch
Cisco IOS Release
Cluster Capability

Catalyst 3550

Cisco IOS Release 12.1(4)EA1 or later

Member or command switch

Catalyst 3500 XL

Cisco IOS Release 12.0(5.1)XU or later

Member or command switch

Catalyst 2950

Cisco IOS Release 12.0(5.2)WC(1) or later

Member or command switch

Catalyst 2955

Cisco IOS Release 12.1(12c)EA1 or later

Member or command switch

Catalyst 2900 XL (8-MB switches)

Cisco IOS Release 12.0(5.1)XU or later

Member or command switch

Catalyst 2900 XL (4-MB switches)

Cisco IOS Release 11.2(8.5)SA6 (recommended)

Member switch only1

Catalyst 1900 and 2820

Cisco IOS Release 9.00(-A or -EN)

Member switch only

1 Catalyst 2900 XL (4-MB) switches appear in the front-panel and topology views of CMS. However, CMS does not support configuration or monitoring of these switches.


Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of Cisco IOS software, software features added 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 Catalyst 2900 XL switch running Cisco IOS Release 11.2(8)SA6, the windows and functionality can be different from a switch running Cisco IOS Release 12.0(5)WC(1) or later.

Note The CMS is not forward-compatible, which means that if a member switch is running a software version that is newer than the release running on the command switch, the new features are not available on the member switch. If the member switch is a new device supported by a software release that is later than the software release on the command switch, the command switch cannot recognize the member switch and it is displayed as an unknown device in the Front Panel view. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to perform configuration and obtain reports for that member.

Downloading Software

This section describes these procedures for downloading software:

•"Guidelines for Downloading Switch Software" section

•"Determining the Software Version and Feature Set" section

•"Which Files to Use" section

•"Upgrading a Switch by Using the CLI" section

•"Recovering from Software Failure" section

For information about the software releases that support the Catalyst 2950 switches, see the "Limitations and Restrictions" section.

Note Before downloading software, read this section for important information.

Note The Catalyst 2950-12 and Catalyst 2950-24 switches cannot be upgraded to Cisco IOS Release 12.1(6)EA2, Cisco IOS Release 12.1(6)EA2a, or Cisco IOS Release 12.1(6)EA2b. They can be upgraded to Cisco IOS Release 12.1(6)EA2c or later.

Guidelines for Downloading Switch Software

When using CMS to upgrade multiple switches from the Cisco TFTP server, the Cisco TFTP server application can process multiple requests and sessions. When using CMS to upgrade multiple switches from the Cisco TFTP server, you must first disable the TFTP Show File Transfer Progress and the Enable Logging options to avoid TFTP server failures. If you are performing multiple-switch upgrades with a different TFTP server, it must be capable of managing multiple requests and sessions at the same time.

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. If a failure occurs during the copy process, you can still reboot your switch by using the old image. If Flash memory does not have enough space for two images, the new image is copied over the existing one. Features provided by the new software are not available until you reload the switch.

If a failure occurs while copying a new image to the switch, and the old image has already been deleted, refer to the "Recovering from Corrupted Software" section in the "Troubleshooting" chapter of the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide.

Note If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.

Caution Do not power cycle the switch while you are copying an image to the switch. If a power failure occurs while you are copying the software image to the switch, call Cisco Systems immediately.

Determining the Software Version and Feature Set

The Cisco IOS image is stored as a .bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the 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. In the display, check the line that begins with System image file is. This line shows the directory name in Flash memory where the image is stored. A couple of lines below the image name, you see Running Enhanced Image if you are running the EI or Running Standard Image if you are running the SI.

Note Although the show version output always shows the software image running on the switch (SI or EI), the model name shown at the end of this display is the factory configuration and does not change if you upgrade the software image.

You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in Flash memory.

Which Files to Use

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file. This file contains both the Cisco IOS image file and the files needed for the CMS. You must use the combined .tar file to upgrade the switch through the CMS.

The .tar file is an archive file from which you can extract files by using the archive tar command.

Note If you are upgrading from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command.

Table 6 lists the software filenames for this Cisco IOS release.

Table 6 Catalyst 2950 and Catalyst 2955 Cisco IOS Software Files

Filename
Description

c2950-i6k2l2q4-tar.121-13.EA1c.tar

Catalyst 2950 SI1 and EI files. This includes the enhanced Cisco IOS image, standard Cisco IOS image, crypto image, and CMS files.

c2950-i6q4l2-tar.121-13.EA1c.tar

Catalyst 2950 SI1 and EI files. This includes the CMS files.

c2955-i6k2l2q4-tar.121-13.EA1.tar

Catalyst 2955 SI1 and EI files. This includes the enhanced Cisco IOS image, standard Cisco IOS image, crypto image, and CMS files.

c2955-i6q4l2-tar.121-13.EA1.tar

Catalyst 2955 SI1 and EI files. This includes the CMS files.

1 Switches that support only the SI cannot run the crypto image. For more information, see the SI-only switches listed in Table 1 and the "Crypto Software Image Guidelines" section.


Upgrading a Switch by Using CMS

You can upgrade switch software by using CMS. From the menu bar, select Administration > Software Upgrade. For detailed instructions, click Help.

If you are using Cluster Manager to upgrade a switch cluster, you can use the Software Upgrade feature to upgrade all or some of the switches in a cluster at once. Consider these conditions when doing an upgrade:

•You cannot upgrade Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, and Catalyst 3500 XL switches at the same time. However, you can group together and upgrade Catalyst 1900 and Catalyst 2820 switches at the same time.

•Upgrade Catalyst 1900 and Catalyst 2820 switches last. To function efficiently, these switches need to be rebooted shortly after the upgrade occurs. If you do not click Reboot Cluster in 30 seconds after the upgrade, the Catalyst 1900 and Catalyst 2820 switches automatically reboot.

•For Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, and Catalyst 3500 XL switches, enter the image_name.tar filename in the New File Name field. The .tar file contains both the Cisco IOS image and the web-management code.

•For Catalyst 1900 and Catalyst 2820 switches, enter the image_name.bin filename in the New File Name field. The .bin file contains the software image and the web-management code.

Follow these steps to use Cluster Manager to upgrade software. Refer to the online help for more details.

Step 1 In Cluster Manager, select Administration > Software Upgrade to display the Software Upgrade window.

Step 2 Enter the .tar filename (for Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, and Catalyst 3500 XL switches) or the .bin filename (for Catalyst 1900 and Catalyst 2820 switches) that contains the switch software image and the web-management code.

You can enter just the filename or a pathname into the New Image File Name 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 If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.

Caution Do not power cycle the switch while you are copying an image to the switch. If a power failure occurs when you are copying the software image to the switch, call Cisco Systems immediately.

Note You can also use Device Manager to upgrade a single switch by following the same software upgrade procedure.

Step 3 Close your browser after the upgrade process is complete.

Upgrading a Switch by Using the CLI

To download switch software by using the CLI, follow these procedures in this order:

•Decide which software files to download from Cisco.com (see the "Determining the Software Version and Feature Set" section).

•Download the .tar file from Cisco.com (see the "Downloading the Software and TFTP Server Application" section).

Use the archive tar command to extract the Cisco IOS image and the CMS files from the .tar file during the TFTP copy to the switch. If you are upgrading from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command.

•Copy the current startup configuration file (see the "Copying the Current Startup Configuration from the Switch to a PC or Server" section).

If the upgrade to the new software fails or if the new startup configuration fails, you can reinstall the previous version of the switch software and use the copy of the startup configuration file to start the switch. If a failure occurs while copying a new image to the switch, and the old image has already been deleted, see the "Guidelines for Downloading Switch Software" section.

•If you are using the CLI to upgrade a Catalyst 2950 or Catalyst 2955 switch, see the "Using the CLI to Upgrade a Catalyst 2950 or Catalyst 2955 Switch" section.

•If you are using the CLI to upgrade a member switch in a switch cluster, follow one of these procedures:

–If you are upgrading Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, and Catalyst 3500 XL member switches, see the "Upgrading Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches" section.

–If you are upgrading Catalyst 1900 or Catalyst 2820 member switches, see the "Upgrading Catalyst 1900 or Catalyst 2820 Member Switches" section.

If you are upgrading a member switch in a switch cluster, because a member switch might not be assigned an IP address, command-line software upgrades through TFTP are managed through the command switch.

Note If you are upgrading from a Cisco IOS release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command as described in the "Using the CLI to Upgrade a Catalyst 2950 or Catalyst 2955 Switch" section, the "Upgrading Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches" section, and the "Upgrading Catalyst 1900 or Catalyst 2820 Member Switches" section.

Downloading the Software and TFTP Server Application

This procedure is for copying the combined .tar file to the Catalyst 2950 or Catalyst 2955 switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.

Note For information about downloading a TFTP server, refer to the URLs in Step 2.

Follow these steps to download the software and, if necessary, the TFTP server application, from Cisco.com to your management station:

Step 1 Use Table 6 to identify the files that you want to download.

Step 2 Download the files from one of these locations:

•If you have a SmartNet support contract, go to this URL, and log in to download the appropriate files:

http://www.cisco.com/public/sw-center/sw-lan.shtml

•If you do not have a SmartNet contract, go to this URL, follow the instructions to register on Cisco.com, and download the appropriate files:

http://www.cisco.com/public/sw-center/sw-lan.shtml

To download the files, select Catalyst 2950 Software for a Catalyst 2950 switch or Catalyst 2955 Software for a Catalyst 2955 switch.

To obtain authorization and download the enhanced crypto software files, elect Catalyst 2950 Strong Cryptographic (3DES) Software for a Catalyst 2950 switch or Catalyst 2955 Strong Cryptographic (3DES) Software for a Catalyst 2955 switch.

Step 3 Use the CLI or web-based interface to perform a TFTP transfer of the file or files to the switch after you have downloaded them to your PC or workstation.

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.

This 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 Copy the file in Flash memory to the root directory of the TFTP server: 

switch# copy flash:config.text tftp

Step 2 Enter the IP address of the device where the TFTP server resides: 

Address or name of remote host []? ip_address

Step 3 Enter the name of the destination file (for example, config.text): 

Destination filename [config.text]? yes/no

Step 4 Verify the copy by displaying the contents of the root directory on the PC or server.

Using the CLI to Upgrade a Catalyst 2950 or Catalyst 2955 Switch

Use this procedure for upgrading Catalyst 2950 or Catalyst 2955 switches by copying the .tar file to the switch. You copy the files to the switch from a TFTP server and extract the files by entering the archive tar command, with these results:

•Changes the name of the current image file to the name of the new file that you are copying and replaces the old image file with the new one. Perform this step only if you have space available on your switch.

•Disables access to the CMS pages and deletes the existing CMS files before the software upgrade to avoid a conflict if users access the web pages during the software upgrade.

•Reenables access to the CMS pages after the upgrade is complete.

Note If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.

Caution Do not power cycle the switch while you are copying an image to the switch. If a power failure occurs when you are copying the software image to the switch, call Cisco Systems immediately.

Note The image names in this section are for a Catalyst 2950 switch. Follow the same steps to upgrade a Catalyst 2955 switch. See Table 6 for the Catalyst 2955 image names.

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 this command: 

server% telnet switch_ip_address

Enter the Telnet password if you are prompted to do so.

Step 3 Enter privileged EXEC mode: 

switch> enable 
switch#

Enter the password if you are prompted to do so.

Step 4 Remove the CMS files: 

switch# delete flash:html/*

Press Enter to confirm the deletion of each file. Do not press any other keys during this process.

Step 5 Enter this command to copy the new image and CMS files to Flash memory:

Caution In this step, the archive tar command copies the .tar file that contains both the image and the CMS files. If you are upgrading from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command. 
switch# archive 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 c2950-i6q4l2-mz.121-13.EA1c.bin (2239579 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 archive tar command.

Step 6 Display the name of the running (default) image file (BOOT path-list). This 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 7 Enter global configuration mode: 

switch# configure terminal 
Enter configuration commands, one per line. End with CNTL/Z.

Step 8 Enter the boot command with the name of the new image filename: 

switch(config)# boot system flash:new_image

For example: 

switch(config)# boot system flash:c2950-i6q4l2-mz.121-13.EA1c.bin

Note If the show boot command entered in Step 6 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 9 Return to privileged EXEC mode: 

switch(config)# end

Step 10 Reload the new software with this command: 

switch# reload 
System configuration has been modified. Save? [yes/no]:y 
Proceed with reload? [confirm]

Step 11 Press Return to confirm the reload.

Your Telnet session ends when the switch resets.

After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC 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 CMS files.

Upgrading Catalyst 2950, Catalyst 2955, Catalyst 2900 XL, or Catalyst 3500 XL Member Switches

Note If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.

Caution Do not power cycle the switch while you are copying an image to the switch. If a power failure occurs when you are copying the image to the switch, call Cisco Systems immediately.

Note The image names in this section are for a Catalyst 2950 switch. Follow the same steps to upgrade a Catalyst 2955. See Table 6 for the Catalyst 2955 image names.

Follow these steps to upgrade the software on a member switch:

Step 1 In privileged EXEC mode on the command switch, display information about the cluster members: 

switch# show cluster members

From the output, 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 Log in to the member switch (for example, member number 1): 

switch# rcommand 1

Step 3 Enter privileged EXEC mode: 

switch> enable 
switch#

Enter the password if you are prompted to do so.

Step 4 Display the name of the running (default) image file (BOOT path-list). This example shows the name in italic: 

switch# show boot 
BOOT path-list:       flash:current_image

Config file:          flash:config.text

Private Config file:  flash:private-config.text

Enable Break:         no

Manual Boot:          no

HELPER path-list:

NVRAM/Config file

      buffer size:    32768

Step 5 If there is no software image defined in the BOOT path-list, enter dir flash: to display the contents of Flash memory.

Step 6 Enter global configuration mode: 

switch# configure terminal 
Enter configuration commands, one per line. End with CNTL/Z.

Step 7 Enter the boot command with the name of the new image filename: 

switch(config)# boot system flash:new_image

For example: 

switch(config)# boot system flash:c2950-i6q4l2-mz.121-131.EA1c.bin

Note If the show boot command entered in Step 6 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 8 Return to privileged EXEC mode: 

switch(config)# end

Step 9 Remove the CMS files: 

switch# delete flash:html/*

Press Enter to confirm the deletion of each file. Do not press any other keys during this process.

Step 10 Start the TFTP copy function as if you were initiating it from the command switch.

Caution In this step, the archive tar command copies the .tar file that contains both the image and the CMS files. If you are upgrading from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command. 
switch-1# archive 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 11 Reload the new software with this command: 

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 command, refer to the Catalyst 2950 and Catalyst 2955 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 In privileged EXEC mode on the command switch, display information about the cluster members: 

switch# show cluster members

From 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 Log in to the member switch (for example, member number 1): 

switch# rcommand 1

Step 3 For switches running the standard edition software, enter the password (if prompted), access the Firmware Configuration menu from the menu console, and perform the upgrade. Follow the instructions in the installation and configuration guide that shipped with your switch. When the download is complete, the switch resets and begins using the new software.

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 For switches running Enterprise Edition Software, start the TFTP copy as if you were initiating it from the member switch: 

switch-1# copy tftp://host/src_file opcode

For example, copy tftp://spaniel/op.bin opcode downloads new system operational code op.bin from the host spaniel.

You should see the TFTP successfully downloaded operational code message. When the download is complete, the switch resets and begins using the new software. If this message does not appear, refer to the installation and configuration guide that shipped with your switch for more information.

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.

Recovering from Software Failure

If the software fails, you can reload the software. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide.

Installation Notes

You can assign IP information to your switch by using the setup program, the Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration (refer to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide), or by manually assigning an IP address (refer to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide).

This section describes these installation procedures:

•"Setting Up the Catalyst 2950 or Catalyst 2955 Initial Configuration" section

•"Accessing CMS" section

Setting Up the Catalyst 2950 or Catalyst 2955 Initial Configuration

The first time that you access the switch, it runs a setup program that prompts you for an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also required if you plan to use the CMS to configure and manage the switch.

Note If the switch will be a cluster member managed through the IP address of the command switch, it is not necessary to assign IP information or a password. If you are configuring the switch as a standalone switch or as a command switch, you must assign IP information.

Follow these steps to create an initial configuration for the switch:

Step 1 Enter Yes at the first two prompts. 

Would you like to enter the initial configuration dialog? [yes/no]: yes


At any point you may enter a question mark '?' for help.

Use ctrl-c to abort configuration dialog at any prompt.

Default settings are in square brackets '[]'.


Basic management setup configures only enough connectivity

for management of the system, extended setup will ask you

to configure each interface on the system.


Would you like to enter basic management setup? [yes/no]: yes

Step 2 Enter a host name for the switch, and press Return.

On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch. 

Enter host name [Switch]: host_name

Step 3 Enter a secret password, and press Return.

The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces. 

Enter enable secret: secret_password

Step 4 Enter an enable password, and press Return. 

Enter enable password: enable_password

Step 5 Enter a virtual terminal (Telnet) password, and press Return.

The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces. 

Enter virtual terminal password: terminal-password

Step 6 (Optional) Configure the Simple Network Management Protocol (SNMP) by responding to the prompts.

Step 7 Enter the interface name (physical interface or VLAN name) of the interface that connects to the management network, and press Return. For this release, always use vlan 1 as that interface. 

Enter interface name used to connect to the

management network from the above interface summary: vlan 1

Step 8 Configure the interface by entering the switch IP address and subnet mask and pressing Return: 

Configuring interface vlan1:

Configure IP on this interface? [yes]: yes 

IP address for this interface: 10.4.120.106

Subnet mask for this interface [255.0.0.0]: 255.255.255.0

Step 9 Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.

If you enter N, the switch appears as a candidate switch in the CMS. In this case, the message in Step 10 does not appear. 

Would you like to enable as a cluster command switch? [yes/no]: yes

Step 10 Assign a name to the cluster, and press Return. 

Enter cluster name: cluster_name

The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores.

The initial configuration appears: 

The following configuration command script was created:


hostname host_name

enable secret 5 $1$Max7$Qgr9eXBhtcBJw3KK7bc850

enable password my

line vty 0 15

password my_password

snmp-server community public

!

no ip routing

!

interface Vlan1

no shutdown

ip address 172.20.139.145 255.255.255.224

!

interface Vlan2

shutdown

no ip address

!

interface FastEthernet0/1

!

interface FastEthernet0/2

!

...<output abbreviated)

!!!

interface GigabitEthernet0/1

!

interface GigabitEthernet0/2

!

end

Step 11 These choices appear: 

[0] Go to the IOS command prompt without saving this config.


[1] Return back to the setup without saving this config.


[2] Save this configuration to nvram and exit.


Enter your selection [2]:

Make your selection, and press Return.

After you complete the setup program, the switch can run the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:

•Command-line interface (CLI)

•CMS from your browser

Accessing CMS

Before using the web-based CMS tools, see the "Software Compatibility" section and the "Installing the Required Plug-In" section to set up the appropriate browser options. After you have assigned an IP address to the switch and installed the plug-in, you can access the switch from your browser and use the CMS to configure other switches.

Note If you have downloaded a new version of the CMS, you must clear your browser cache before launching the new CMS version.

The browser prompts for a username and password when you access CMS:

•If no username is configured on your switch (the default), you only need to enter the enable password in the appropriate field. For more information, see the "Displaying CMS" section.

•If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch. For more information, see the "Configuring the HTTP Server" section.

Configuring the HTTP Server

Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

ip http authentication {aaa | enable | local | tacacs}

Configure the HTTP server interface for the type of authentication you want to use.

•aaa—Authentication, authorization, and accounting (AAA) facility is used for authentication.

•enable—Enable password, which is the default method of HTTP server user authentication, is being used.

•local— Local user database as defined on the Cisco router or access server is used for authentication.

•tacacs—TACACS server is used for authentication.

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show running-config

Verify your entries.

After you have configured the HTTP server interface, display the CMS access page as described in