Table Of Contents
Release Notes for the Catalyst 2950 and Catalyst 2955 Switches, Release 12.1(13)EA1
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 IOS Software
Guidelines for Downloading Switch Software
Determining the Software Version and Feature Set
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
Setting Up the Catalyst 2950 or Catalyst 2955 Initial Configuration
Crypto Software Image Guidelines
CMS Limitations and Restrictions
Hardware and Software Compatibility Matrixes
Open Cluster Configuration Caveat
Caveats Resolved in Release 12.1(13)EA1
CMS Caveats Resolved in Release 12.1(13)EA1
Corrections to the Catalyst 2950 Desktop Switch Hardware Installation Guide
Corrections to the Catalyst 2955 Hardware Installation Guide
Switch and Alarm Circuit Warning
Switch Operating Range Warning
Substitution of Components Warning
Switch Functional Ground Lug Warning
Ambient Temperature of 140°F Warning
Twisted-Pair Supply Wires Warning
Obtaining Technical Assistance
Obtaining Additional Publications and Information
Release Notes for the Catalyst 2950 and Catalyst 2955 Switches, Release 12.1(13)EA1
March 2003
The Cisco IOS Release 12.1(13)EA1 runs on Catalyst 2950 and Catalyst 2955 switches.
These release notes include important information about this 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 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 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 IOS release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future IOS releases become available, they will be posted to 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
•
"Limitations and Restrictions" section
•
"Documentation Updates" section
•
"Related Documentation" section
•
"Obtaining Documentation" section
•
"Obtaining Technical Assistance" section
System Requirements
The system requirements for this IOS release are described in these sections:
•
"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 DescriptionCatalyst 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)
•
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 DescriptionGBIC 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 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 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 SizeWindows 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 Explorer2Windows 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 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 IOS Release Cluster CapabilityCatalyst 3550
Release 12.1(4)EA1 or later
Member or command switch
Catalyst 3500 XL
Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2950
Release 12.0(5.2)WC(1) or later
Member or command switch
Catalyst 2955
Release 12.1(12c)EA1 or later
Member or command switch
Catalyst 2900 XL (8-MB switches)
Release 12.0(5.1)XU or later
Member or command switch
Catalyst 2900 XL (4-MB switches)
Release 11.2(8.5)SA6 (recommended)
Member switch only1
Catalyst 1900 and 2820
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 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 Release 11.2(8)SA6, the windows and functionality can be different from a switch running 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
•
"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 Release 12.1(6)EA2, Release 12.1(6)EA2a, or Release 12.1(6)EA2b. They can be upgraded to 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 Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
CautionDo 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 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. 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 IOS image file and the HTML 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 Release 12.1(6)EA2, use the tar command instead of the archive tar command.
Table 6 lists the software filenames for this IOS release.
Table 6 Catalyst 2950 and Catalyst 2955 IOS Software Files
Filename Descriptionc2950-i6k2l2q4-tar.121-13.EA1.tar
Catalyst 2950 SI1 and EI files. This includes the enhanced IOS image, standard IOS image, crypto image, and CMS files.
c2950-i6q4l2-tar.121-13.EA1.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 IOS image, standard 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 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 Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
CautionDo 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 IOS image and the HTML files from the .tar file during the TFTP copy to the switch. If you are upgrading from a release earlier than 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 an IOS release earlier than 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 tftpStep 2
Enter the IP address of the device where the TFTP server resides:
Address or name of remote host []? ip_addressStep 3
Enter the name of the destination file (for example, config.text):
Destination filename [config.text]? yes/noStep 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 HTML pages and deletes the existing HTML files before the software upgrade to avoid a conflict if users access the web pages during the software upgrade.
•
Reenables access to the HTML pages after the upgrade is complete.
Note
If you are upgrading a switch that is running a release earlier than Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
CautionDo 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_addressEnter 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 HTML files:
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 5
Enter this command to copy the new image and HTML files to Flash memory:
CautionIn this step, the archive tar command copies the .tar file that contains both the image and the HTML files. If you are upgrading from a release earlier than 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.EA1.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: 32768Step 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_imageFor example:
switch(config)# boot system flash:c2950-i6q4l2-mz.121-13.EA1.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)# endStep 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 HTML 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 Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
CautionDo 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 membersFrom 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 1Step 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_imageConfig file: flash:config.textPrivate Config file: flash:private-config.textEnable Break: noManual Boot: noHELPER path-list:NVRAM/Config filebuffer size: 32768Step 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_imageFor example:
switch(config)# boot system flash:c2950-i6q4l2-mz.121-131.EA1.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)# endStep 9
Remove the HTML files:
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 10
Start the TFTP copy function as if you were initiating it from the command switch.
CautionIn this step, the archive tar command copies the .tar file that contains both the image and the HTML files. If you are upgrading from a release earlier than 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 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
Log in to the member switch (for example, member number 1):
switch# rcommand 1Step 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 opcodeFor 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
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]: yesAt 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 connectivityfor management of the system, extended setup will ask youto configure each interface on the system.Would you like to enter basic management setup? [yes/no]: yesStep 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_nameStep 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_passwordStep 4
Enter an enable password, and press Return.
Enter enable password: enable_passwordStep 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-passwordStep 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 themanagement network from the above interface summary: vlan 1Step 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]: yesIP address for this interface: 10.4.120.106Subnet mask for this interface [255.0.0.0]: 255.255.255.0Step 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]: yesStep 10
Assign a name to the cluster, and press Return.
Enter cluster name: cluster_nameThe 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_nameenable secret 5 $1$Max7$Qgr9eXBhtcBJw3KK7bc850enable password myline vty 0 15password my_passwordsnmp-server community public!no ip routing!interface Vlan1no shutdownip address 172.20.139.145 255.255.255.224!interface Vlan2shutdownno ip address!interface FastEthernet0/1!interface FastEthernet0/2!...<output abbreviated)!!!interface GigabitEthernet0/1!interface GigabitEthernet0/2!endStep 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:
After you have configured the HTTP server interface, display the CMS access page as described in "Displaying CMS" section.
Displaying CMS
To display the CMS access page, follow these steps:
Step 1
Enter the switch IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer), and press Return.
Step 2
Enter your username and password when prompted.
The Cisco Systems Access page appears. For more information on setting passwords and privilege levels, refer to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide.
Step 3
Click Web Console to launch the CMS applet.
When you access CMS from a standalone or a cluster-member switch, Device Manager appears.
New Features
These are the new supported hardware and the new software features provided in Release 12.1(13)EA1.
New Hardware Features
There is no new hardware offered with this release. For a list of supported hardware, see the "Hardware Supported" section.
New Software Features
Cisco IOS Release 12.1(13)EA1 has these new features or enhancements:
•
Per-VLAN Rapid Spanning Tree Plus (PVRST+) for balancing load across VLANs by providing convergence of spanning-tree instances (available only with the EI)
Note
PVRST+ is referred to as PVRST in the software documentation.
•
SPAN support of Intrusion Detection Systems (IDSs) to monitor, repel, and report network security violations
•
Support for the CISCO-PORT-SECURITY-MIB with these limitations:
–
The cpsGlobalPortSecurityEnable object can only be implemented as a read object. By default this object is set to TRUE.
–
The cpsIfPortSecurityStatus object has three values (secureup, securedown, and shutdown). Only the secureup and securedown values are supported in this release.
–
The cpsIfClearSecureAddresses object is not supported. (CSCea06807)
•
Facilities for processing alarms related to temperature, power-supply conditions, and the status of the Ethernet ports (Catalyst 2955 switch only)
•
CMS support for these features:
–
Cisco Redundant Power System (RPS) 675—Monitor status of switches that are using the RPS 675.
–
Alarms Dialog—Display and configure the settings for device alarms, interface alarms, and alarm profiles (Catalyst 2955 switch only).
–
Alarm Status Dialog—Display the status of outstanding alarms (Catalyst 2955 switch only).
Limitations and Restrictions
You should review this section before you begin working with the switches. These are known limitations that will not be fixed, and there is not always a workaround. Some features might not work as documented, and some features could be affected by recent changes to the switch hardware or software.
Note
These limitations and restrictions apply to all Catalyst 2950 and Catalyst 2955 switches unless otherwise noted.
These are the limitations and restrictions:
•
"Crypto Software Image Guidelines" section
•
"Immediate-Leave Limitation" section
•
"Hardware and Software Compatibility Matrixes" section
•
"Hardware and Software Compatibility Matrixes" section
•
"Port Configuration Conflicts" section
IOS Limitations
•
Root guard is inconsistent when configured on a port that is in the STP blocked state at the time of configuration.
There is no workaround. (CSCdp85954)
•
Aging of dynamic addresses does not always occur exactly after the specified aging time elapses. It might take up to three times this time period before the entries are removed from the table.
There is no workaround. (CSCdr96565)
•
If the switch gets configured from the dynamic IP pool, a duplicate or different IP address might be assigned.
The workaround is to make sure that the DHCP server contains reserved addresses that are bound to each switch by the switch hardware address so that the switch does not obtain its IP address from the dynamic pool. (CSCds58369)
•
Internal loopback in half-duplex mode causes input errors. We recommend that you configure the PHY to operate in full duplex before setting the internal loopback.
There is no workaround. (CSCds20365)
•
A source-based distribution port group does not share the broadcast with all the group members. When the destination of the packets is a broadcast or unknown unicast or multicast, the packets are forwarded only on one port member of a port group, instead of being shared among all members of the port group.
There is no workaround. (CSCdt24814, formerly CSCdt2481)
•
When you enter the show controllers ethernet-controller interface-id or show interfaces interface-id counters privileged EXEC command, if a large number of erroneous frames are received on an interface, the receive-error counts might be smaller than the actual values, and the receive-unicast frame count might be larger than the actual frame count.
There is no workaround. (CSCdt27223)
•
Two problems occur when the Catalyst 2950 switch is in transparent mode:
–
If the switch is a leaf switch, any new VLANs added to it are not propagated upstream through VTP messages. As a result, the switch does not receive flooded traffic for that VLAN.
–
If the switch is connected to two VTP servers, it forwards their pruning messages. If the switch has a port on a VLAN that is not requested by other servers through their pruning messages, it does not receive flooded traffic for that VLAN.
There is no workaround. (CSCdt48011)
•
The receive count output for the show controllers ethernet-controller interface-id privileged EXEC command shows the incoming packets count before the ASIC makes a decision of whether to drop the packet or not. Therefore, for ports in the STP blocking states, even though the receive count shows incoming frames, the packet is not forwarded to the other port.
There is no workaround. (CSCdu83640)
•
In some network topologies, when UplinkFast is enabled on all Catalyst 2950 or Catalyst 2955 switches and BackboneFast is not enabled on all switches, a temporary loop might be caused when the STP root switch is changed.
The workaround is to enable BackboneFast on all switches. (CSCdv02941)
•
At times, the Window XP pop-up window might not appear while authenticating a client (supplicant) because the user information is already stored in Windows XP. However, the Extensible Authentication Protocol over LAN (EAPOL) response to the switch (authenticator) might have an empty user ID that causes the 802.1X port to be de-authenticated.
The workaround is to manually re-initiate authentication by either logging off or detaching the link and then re-connecting it. (CSCdv19671)
•
If two Catalyst 2950 switches are used in a network and if access ports are used to connect two different VLANs whose VLAN IDs are separated by the correct multiple of 64, it is possible to create a situation where the two switches use the same bridge ID in the same spanning-tree instances. This might cause a loss of connectivity in the VLAN as the spanning tree blocks the ports that should be forwarding.
The workaround is to not cross-connect VLANs. For example, do not use an access port to connect VLAN 1 to VLAN 65 on either the same switch or from one switch to another switch. (CSCdv27247)
•
A command switch might not show the Catalyst 1900, Catalyst 2820, and Catalyst 2900 XL 4-MB (models C2908-XL, C2916M-XL, C2924C-XL, and C2924-XL) switches as candidates even though their management VLAN is the same as the command switch. This occurs only when their management VLAN is not VLAN 1.
There is no workaround. (CSCdv34505)
•
You can configure up to 256 Multicast VLAN Registration (MVR) groups by using the mvr vlan group interface configuration command, but only 255 groups are supported on a Catalyst 2950 switch at one time. If you statically add a 256th group, and 255 groups are already configured on the switch, it continues trying (and failing) to add the new group.
The workaround is to set the mode to dynamic for Catalyst 2950 switches that are connected to IGMP-capable devices. The new group can join the multicast stream if another stream is dynamically removed from the group. (CSCdv45190)
•
A Catalyst 2950 command switch can discover only the first Catalyst 3550 switch if the link between the Catalyst 3550 switches is an 802.1Q trunk and the native VLAN is not the same as the management VLAN of the Catalyst 2950 switch or if the link between the Catalyst 3550 switches is an ISL trunk and the management VLAN is not VLAN 1.
The workaround is to connect Catalyst 3550 switches by using the access link on the command switches management VLAN or to configure an 802.1Q trunk with a native VLAN that is the same as the management VLAN of the command switch. (CSCdv49871)
•
There might be a link on the Fast Ethernet port of the Catalyst 2950 switch when it is forced to 10 Mbps and full-duplex mode and its link partner is forced to 100 Mbps and forced duplex mode. The LED on the Catalyst 2950 switch might display the link, and the error counters might increment.
The workaround is to configure both sides of a link to the same speed or use auto-negotiation. (CSCdv62271)
•
The ip http authentication enable global configuration command is not saved to the configuration file because this is the default configuration. Therefore, this configuration is lost after a reboot.
The workaround is to manually enter the command again after a reboot. (CSCdv67047)
•
If a stack that has Catalyst 2950 or Catalyst 2955 switches also has Catalyst 2900 XL or Catalyst 3500 XL switches, cross-stack UplinkFast (CSUF) does not function if the management VLAN on the Catalyst 2900 XL or Catalyst 3500 XL switches is changed to a VLAN other than VLAN 1 (the default).
The workaround is to make sure that the management VLANs of all Catalyst 2900 XL or 3500 XL switches in the stack are set to VLAN 1. (CSCdv82224)
If a port is configured as a secure port with the violation mode as restrict, the secure ports might process packets even after maximum limit of MAC addresses is reached, but those packets are not forwarded to other ports.
There is no workaround. (CSCdw02638)
•
The discarded frames count of the show controllers ethernet-controller privileged EXEC command output and the ignored count of the show controller ethernet privileged EXEC command output can increment for these reasons:
–
The source and destination ports are the same.
–
The spanning-tree state of the ingress port is not in the forwarding state.
–
Traffic is filtered because of unicast or multicast storms are on the port.
–
Traffic is dropped because a VLAN has not been assigned by VLAN Query Protocol (VQP).
Note
This error occurs only on switches that can run Release 12.1(6)EA2 or earlier.
There is no workaround. (CSCdw48441)
•
A switch does not use the default gateway address in the DHCP offer packet from the server during automatic-install process.
The workaround is to manually assign an IP address to the switch. (CSCdy08716)
•
If you assign a nonexistent VLAN ID to a static-access EtherChannel by setting the ciscoVlanMembershipMIB:vmVlan object, the switch does not create the VLAN in the VLAN database.
There is no workaround. (CSCdy65850)
•
When you configure a dynamic switch port by using the switchport access vlan dynamic interface configuration command, the port might allow unauthorized users to access network resources if the interface changes from access mode to trunk mode through Dynamic Trunking Protocol (DTP) negotiation.
The workaround is to configure the port as a static access port. (CSCdz32556)
•
The output from the show stack privileged EXEC command might show a large number of false interrupts.
There is no workaround. The number of interrupts does not affect the switch functionality. (CSCdz34545)
•
In Release 12.1(13)EA1, these are the default settings for a IP Phone connected to a switch:
–
The port trust state is to not trust the priority of frames arriving on the IP Phone port from connected devices.
–
The CoS value of incoming traffic is overwritten and set to zero. (CSCdz76915)
•
When you enable Port Fast on a static-access port and then change the port to dynamic, Port Fast remains enabled. However, if you change the port back to static, Port Fast is disabled.
The workaround is to configure Port Fast globally by using the spanning-tree portfast global configuration command. (CSCea24969)
Crypto Software Image Guidelines
The SSH feature uses a large amount of switch memory, which limits the number of VLANs, trunk ports, and cluster members that you can configure on the switch. Before you download the crypto software image, your switch configuration must meet these conditions:
•
The number of trunk ports multiplied by the number of VLANs on the switch must be less than or equal to 128. These are examples of switch configurations that meet this condition:
–
If the switch has 2 trunk ports, it can have up to 64 VLANs.
–
If the switch has 32 VLANs, it can have up to 4 trunk ports.
•
If your switch is a cluster command switch, it can only support up to eight cluster members.
Note
A switch that runs the SI cannot run the crypto image. If a crypto image is loaded on an SI-only switch, the switch will perform a forced reload.
If your switch has a saved configuration that does not meet the previous conditions and you upgrade the switch software to the crypto software image, the switch might run out of memory. If this happens, the switch does not operate properly. For example, it might continuously reload.
If the switch runs out of memory, this message appears:
%SYS-2-MALLOCFAIL: Memory allocation of (number_of_bytes) bytes failed ...The workaround is to check your switch configuration and ensure that it meets the previous conditions. (CSCdw66805)
Immediate-Leave Limitation
When the Internet Group Management Protocol (IGMP) Immediate-Leave is configured, new ports are added to the group membership each time a join message is received, and ports are pruned (removed) each time a leave message is received.
If the join and leave messages arrive at high rate, the CPU can become busy processing these messages. For example, the CPU usage is approximately 50 percent when 50 pairs of join and leave messages are received each second. Depending on the rate at which join and leave messages are received, the CPU usage can go very high, even up to 100 percent, as the switch continues processing these messages.
The workaround is to only use the Immediate-Leave processing feature on VLANs where a single host is connected to each port. (CSCdx95638)
RSPAN Limitation
In a Remote Switched Port Analyzer (RSPAN) session, if at least one switch is used as an intermediate or destination switch and if traffic for a port is monitored in both directions, traffic does not reach the destination switch. (CSCdy38476)
These are the workarounds:
•
Use a Catalyst 3550 or Catalyst 6000 switch as an intermediate or destination switch.
•
Monitor traffic in only one direction if a Catalyst 2950 switch is used as an intermediate or destination switch.
ACL Limitations
Follow these guidelines for applying access control lists (ACLs) to interfaces:
•
From IOS version 12.1(9)EA1d and later, you can create ACLs with access control entries (ACEs) that have different masks. However, these ACLs can only be applied to a management VLAN or to any traffic that is going directly to the CPU, such as SNMP, Telnet, or web traffic. (CSCdz06177)
•
When you apply an ACL to a physical interface, some keywords are not supported, and certain mask restrictions apply to the ACLs. For information on creating ACLs for physical interfaces, refer to the "Creating a Numbered Standard ACL" section and the "Creating a Numbered Extended ACL" section of the software configuration guide for Release 12.1(9)EA1 or later. (CSCdw56650)
•
You can apply ACLs to a management VLAN or to any traffic that is going directly to the CPU, such as SNMP, Telnet, or web traffic. For information on creating ACLs for these interfaces, refer to the "Configuring IP Services" section of the Cisco IOS IP and IP Routing Configuration Guide and the Command Reference for IOS Release 12.1.
CMS Limitations and Restrictions
These limitations apply to CMS configuration:
•
If you are printing a Topology View or Front Panel View that contains many devices and are running Solaris 2.6 with JDK1.2.2, you might get an Out of Memory error message.
The workaround is to close the browser, re-open it, and launch CMS again. Before you perform any other task, bring up the view that you want to print, and click Print in the CMS menu. (CSCds80920)
•
CMS performance degrades if the Topology View is open for several hours on a Solaris machine. The cause might be a memory leak.
The workaround is to close the browser, re-open it, and launch CMS again. (CSCds29230)
•
If a PC running CMS has low memory and CMS is running continuously for 2 to 3 days, the PC runs out of memory.
The workaround is to relaunch CMS. (CSCdv88724)
•
When a VLAN or a range of VLANs is already configured and you specify VLAN filter for a SPAN session, the current configuration for that session is overwritten with the new entry. Although the CLI appends new entries after the existing ones, CMS recreates the whole session, overwrites the current entry, and provides only a single VLAN filter per entry.
The workaround is to use the CLI. It is the only method for specifying multiple VLANs for filtering in a SPAN session. (CSCdw93904)
•
If you launch CMS by using Netscape 4.75 and Java Runtime Environment (JRE) 1.3.1 or 1.4.0 on Windows 98 or by using Netscape 6.2 and JRE 1.3.1 on Windows 98, CMS stops running while it determines the network information.
The workaround is to click once outside of the CMS window. (CSCea25913)
•
On the Japanese versions of Windows 98 and Windows ME, if you launch CMS by using the Netscape 4.7 browser, CMS might stop running after you click the Apply button.
The workaround is to use Netscape 6.0 or later or use Internet Explorer to launch CMS on Windows 98 and Windows ME. (CSCea27408)
•
Host names and Domain Name System (DNS) server names that contain commas on a cluster command switch, member switch, or candidate switch can cause CMS to behave unexpectedly. You can avoid this instability in the interface by not using commas in host names or DNS names. Do not enter commas when also entering multiple DNS names in the IP Configuration tab of the IP Management window in CMS.
•
ACEs that contain the host keyword precede all other access control entries (ACEs) in standard ACLs. You can reposition the ACEs in a standard ACL with one restriction: No ACE with the any keyword or a wildcard mask can precede an ACE with the host keyword.
Hardware and Software Compatibility Matrixes
Some switches are not supported by certain software releases. In Table 7 and Table 8, Yes means that the switch is supported by the software release; No means that the switch is not supported by the release.
Table 7 lists the Catalyst 2950-12, 2950-24, 2950C-24, and 2950T-24 switches and the software releases supporting them. The serial numbers are on the switch rear panel.
Table 8 lists the Catalyst 2950G-12-EI, 2950G-24-EI, 2950G-24-EI-DC, 2950G-48-EI, and 2950SX-24 switches and the software releases supporting them. The serial numbers are on the switch rear panel.
Note
The Catalyst 2955 switch is supported by Release 12.1(12c)EA1 or later.
Port Configuration Conflicts
Certain combinations of port features create configuration conflicts (see Table 9). If you try to enable incompatible features, CMS issues a warning message, and you cannot make the change. Reload the page to refresh CMS.
In Table 9, No means that the two referenced features are incompatible, and both should not be enabled; Yes means that both can be enabled at the same time and do not cause an incompatibility conflict. A dash means not applicable.
Table 9 Conflicting Features
Port Group Port Security SPAN Source Port SPAN Destination Port Connect to Cluster? Protected Port 802.1X Port Port Group-
No
Yes
No
Yes
Yes
No
Port SecurityNo
-
Yes
No
Yes
Yes
Yes1
SPAN Source PortYes
Yes
-
No
Yes
Yes
Yes
SPAN Destination PortNo
No
No
-
Yes
Yes
No
Connect to ClusterYes
Yes
Yes
Yes
-
Yes
-
Protected PortYes
Yes
Yes
Yes
Yes
-
-
802.1X PortNo
Yes1
Yes
No
-
-
-
1 The switch must be running the EI.
SPAN Limitation
When using the SPAN feature, the monitoring port receives copies of sent and received traffic for all monitored ports. If the monitoring port is oversubscribed, it will probably become congested. This might also affect how one or more of the monitored ports forwards traffic.
Important Notes
This section describes important information related to this IOS release. These sections are included:
IOS Notes
These notes applies to IOS configuration:
•
When an 802.1X-authenticated client is disconnected from an IP phone, hub, or switch and does not send an EAPOL-Logoff message, the switch interface does not transition to the unauthorized state. If this happens, it can take up to 60 minutes for the interface to transition to the unauthorized state when the re-authentication time is the default value (3600 seconds).
The workaround is to change the number of seconds between re-authentication attempts by using the dot1x timeout re-authperiod seconds global configuration command. (CSCdz38483)
•
When you configure a dynamic switchport by using the switchport access VLAN dynamic interface configuration command, the port might allow unauthorized users to access network resources if the interface changes from access mode to trunk mode through Dynamic Trunking Protocol (DTP) negotiation.
The workaround is to configure the port as a static access port. (CSCdz32556)
CMS Notes
This section describe this information:
Read-Only Mode in CMS
CMS provides two levels of access to the configuration options. If your privilege level is 15, you have read-write access to CMS. If your switch privilege level is from 1 to 14, you have read-only access to CMS. In the read-only mode, some data is not displayed, and an error message appears when these switches are running these software releases:
•
Catalyst 2900 XL or Catalyst 3500 XL member switches running Release 12.0(5)WC2 or earlier
•
Catalyst 2950 member switches running Release 12.0(5)WC2 or earlier
•
Catalyst 3550 member switches running Release 12.1(6)EA1 or earlier
In the Front Panel view or Topology view, CMS does not display error messages. In the Front Panel view, if the switch is running one of the software releases listed previously, the device LEDs do not appear. In Topology view, if the member is a Long-Reach Ethernet (LRE) switch, the customer premises equipment (CPE) devices that are connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.
To view switch information, you need to upgrade the member switch software. For information about upgrading switch software, see the "Downloading Software" section.
Configuring CMS
These notes apply to the CMS configuration:
•
If you use CMS on Windows 2000, it might not apply configuration changes if the enable password is changed from the CLI during your CMS session. You have to restart CMS and enter the new password when prompted. Platforms other than Windows 2000 prompt you for the new enable password when it is changed.
•
If you have a proxy server configured on your web browser, CMS can run slowly and take 2 to 3 minutes to process each command that is entered.
The workaround, if you do not want to disable the proxy server settings on the browser, is to download a browser from a different vendor and use it without the proxy server settings configured to access the CMS.
•
CMS does not display QoS classes that are created through the CLI if these classes have multiple match statements. When using CMS, you cannot create classes that match more than one match statement. CMS does not display policies that have such classes.
•
If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.add.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch CMS.
•
Within an ACL, you can change the sequence of ACEs that have the host keyword. However, because such ACEs are independent of each other, the change has no effect on the way the ACL filters traffic.
VLAN Notes
These notes apply to VLAN configuration:
•
The management interface configuration command is not supported in Release 12.1(6)EA2 or later. To shut down the current management VLAN interface and to enable the new management VLAN interface, use the shutdown and no shutdown interface configuration commands. Refer to the Catalyst 2950 and Catalyst 2955 Switch Command Reference for information about using the shutdown interface configuration command.
•
If VLAN 1 or VLANs 1002 to 1005 are removed from a trunk port, the switch no longer receives CDP or VTP frames. VLAN minimization is not supported on the Catalyst 2950 switch. You cannot remove VLAN 1 or VLANs 1002 to 1005 from the allowed VLAN list. (CSCdz22629)
IGMP Filtering
IGMP filtering controls only group specific query and membership reports, including join and leave reports. It does not control general IGMP queries.
Open Caveats
Open caveats in this release are described in these sections:
•
"Open Cluster Configuration Caveat" section
Note
All open caveats listed in these sections apply to both the Catalyst 2950 and Catalyst 2955 switches unless otherwise noted.
Open IOS Caveats
These are the severity 3 IOS configuration caveats:
•
CSCdx47532
A switch can log this error message:
Apr 30 18:26:20 AEST: %SCHED-3-STUCKMTMR: Sleep with expired managed timer 80D9F 210, time 0x4F29560 (00:00:00 ago).
-Process= "L2MM", ipl= 7, pid= 39
-Traceback= 801C5B14 801C5E78 803F50C0 801B1A8C 801B1A78
There is no workaround. This does not affect switch functionality.
•
CSCdx75308
When you use the policy-map global configuration command to create a policy map, and you do not specify any action for a class map, the association between that class map and policy map is not saved when you exit policy-map configuration mode.
The workaround is to specify an action in the policy map.
•
CSCdy65883
On Gigabit Ethernet interfaces, if the pagpEthcOperationMode object value is set to pagpOn, the running configuration on the CLI incorrectly shows that the PAgP mode is set to auto. The PAgP mode should be desirable.
There is no workaround.
•
CSCdy68250
Regardless of the power mode (single or dual) that is being used on a Catalyst 2955 switch, the power status LED is red if an associated power supply is not present.
These are the workarounds:
–
Use the default single-power mode and ignore the red LED for the empty secondary power supply inputs.
–
Connect jumper wires from the primary power supply inputs to the empty power supply inputs so that both power status LEDs show status for the primary power supply.
•
CSCdy75471
After a switch reloads, if a multicast dynamic MAC address is manually configured on a trunk port, traffic to this multicast address is sent to the incorrect native VLAN.
The workaround is to remove the multicast dynamic MAC address that was manually configured and then configure the multicast address as a static MAC address.
•
CSCdy87390
When IGMP snooping is enabled on a switch, if it receives an IGMP report from a client port and sends the packet to a router port, the switch adds a 4-byte frame check sequence (FCS) to the end of the frame, which changes the length of the frame from 64 bytes to 68 bytes.
There is no workaround.
•
CSCdz00065
When a link is down, this message might not appear:
Interface changed state to downThere is no workaround.
•
CSCdz07948
When a switch is connected through redundant EtherChannels to another switch, and that switch is the SpanningTree Protocol (STP) root switch, a loop can occur when that root switch is rebooted.
The workaround is to shut down the EtherChannel. If this does not correct the problem, remove the redundant physical connection between the switches.
•
CSCdz12991
If the system board test fails during the power-on self-test (POST), the polling c2900InfoSelfTestFailed object value is 0x80, which means the test failed, but the output from the show post privileged EXEC command shows that the system board test passed.
There is no workaround.
•
CSCdz45149
A switch might reboot when an EtherChannel line state changes to up.
There is no workaround.
•
CSCdz45204
When you use the system mtu global configuration command to set the maximum packet size to 1530 bytes, large frames are still counted as Giants and Input errors in the output of the show interfaces counters privileged EXEC command.
There is no workaround.
•
CSCdz45660
When a Catalyst switch is used as a Layer 2 switch with IGMP snooping enabled, the switch sends IGMP leave packets with a source IP address of 0.0.0.0. Some third-party switches erroneously reject IGMP leave message with a source address of 0.0.0.0.
The workaround is to only use devices that accept IGMPv2 messages with a source address of 0.0.0.0.
•
CSCdz61363
When a host leaves a multicast group by sending an Internet Group Management Protocol (IGMP) leave or does not send an IGMP report in response to a General Query within the maximum IGMP response-time window (10 seconds by default), the IGMP snooping code removes the port. If this is the last receiver in the group, the switch generates a leave to the router to prune the multicast router quickly.
There is no workaround.
•
CSCdz64196
If a Catalyst 2950 or Catalyst 2955 switch is connected to a Catalyst 3500 XL switch through a Gigastack GBIC module and the cable is disconnected and then reconnected, the link might flap continuously, fail to negotiate the duplex mode, and the LED on both ends of the link could blink amber.
The workarounds are to restart both switches simultaneously to disable autonegotiation on the Catalyst 3500 XL switch, or to use the shutdown and no shutdown interface configuration command on the interface.
•
CSCdz74685
If you configure a static secure MAC address on an interface before enabling port security on the interface, the same MAC address is allowed on multiple interfaces. If the same MAC address is added on multiple ports before enabling port security and port security is later enabled on those ports, only the first MAC address can be added to the hardware database. If port security is first enabled on the interface, the same static MAC address is not allowed on multiple interfaces.
There is no workaround.
•
CSCdz75555
When some Network Interface Cards (NICs) are set to autonegotiate and the switch interface is manually configured to operate at 100 Mbps in half- or full-duplex mode, the link between the NIC and the switch interface might be down.
The workaround is to configure the NIC and switch interface to autonegotiate the speed and duplex settings.
•
CSCdz89699
The copper uplink 10/100/1000 Ethernet interfaces operate only in full-duplex mode on a Catalyst 2955T-12 switch.
There is no workaround.
•
CSCea00546
When a Catalyst 2950 or Catalyst 2955 switch is a middle stack member through Gigastack GBIC connections, the switch returns a traceback message and the response time is high when you use Telnet to connect from one switch to another switch in the stack.
There is no workaround.
•
CSCea05146
When using an SNMP query on ciscoFLASHPartitionTable some attributes defined by the MIB are not displayed. For example, Size, FreeSpace, and FileCount are defined by the MIB but are not shown in the query result.
There is no workaround.
•
CSCea05157
These variables in c2900PortTable MIB return a value of zero:
–
c2900PortStatus
–
c2900PortViolationAction
–
c2900PortMayLearnAddress
–
c2900PortMayForwardFrames
–
c2900PortBufferCongestionControl
There is no workaround
•
CSCea12888
If you press and hold the spacebar while the output of any show user EXEC command is being displayed, the Telnet session is stopped, and you can no longer communicate with the management VLAN.
These are the workarounds:
–
Enter the show commands from privileged EXEC mode, and use this command to set the terminal length to zero:
switch# terminal length 0
–
Telnet directly from a PC or workstation to the switch.
–
Do not hold down the spacebar while scrolling through the output of a show user EXEC command. Instead, slowly press and release the spacebar.
•
CSCea23138
When you connect a switch to another switch through a trunk port and the number of VLANs on the first switch is lower than the number on the connected switch, interface errors are received on the management VLAN of the first switch.
The workaround is to match the configured VLANs on each side of the trunk port.
•
CSCea29670
For traffic sent by the switch, such as an Open Shortest Path First (OSPF) database description packet (not including the OSPF hello packet) and extended ping packets that have a type of service (TOS) value of 6, the switch overrides the CoS value and sets it to 0.
•
CSCea34287
On switches running Release 12.1(12c)EA1 or later, if you change the access VLAN ID of a port channel by using the switchport access vlan interface configuration command, the changes are propagated to the port-channel members but are not added to the running configuration of the member switches. After the switch reloads, the VLAN IDs of the port channel and its candidate member ports do not match, and the candidate ports cannot join the port channel.
The workaround is to manually change the access VLAN ID on each of the port-channel members when you change the access VLAN ID of the port channel.
•
CSCin26670
On Catalyst 2950 and Catalyst 2955 switches, the vtpVlanApplyStatus MIB object is not returning value 2, which appears when the apply operation is successful after creating or deleting a VLAN.
There is no workaround.
Open Cluster Configuration Caveat
This is the severity 3 cluster caveat:
•
CSCdz88305
When a cluster of switches have NTP (Network Time Protocol) configured, the command switch is not synchronized with the rest of the switches.
There is no workaround.
Open CMS Caveats
These are the severity 3 CMS configuration caveats:
•
CSCdv56582
In the CMS topology view, icons for the fiber-optic, ATM, and FDDI links are not visible.
There is no workaround.
•
CSCdv82352
A red border appears around the text-entering area of some CMS dialogs. The color of the border changes to green when text is entered. This is only a cosmetic error. The colored border does not prevent you from entering text.
There is no workaround.
Note
This error only occurs with Java plug-in 1.4.0.
•
CSCdw87550
You cannot switch modes (for example, from Guide Mode to Expert Mode) for an open CMS window.
The workaround is to close the open window, select the mode that you want, and then reopen the CMS window.
Note
For the mode change to take effect on any other CMS window that is open, you need to close that window and then reopen it after you select the new mode.
•
CSCdx73168
Log scaling does not appear in a link graph until the first data values appear in the graph. This happens when you are using any of the supported operating systems, browsers, or java plug-ins.
There is no workaround.
•
CSCdx88994
In read-only mode, time ranges are not displayed unless you are logged in with read-write access (privilege level 15). See the "CMS Notes" section for more information about CMS modes.
There is no workaround.
•
CSCdy30416
Community Strings tab shows community strings that are created for trap managers.
There is no workaround.
•
CSCdz04048
When a switch is using a Cisco Redundant Power System (RPS) 300, the icon for that switch might appear yellow instead of green.
There is no workaround.
•
CSCdz07672
When one of two switches in a link is down, the link might appear green. This could happen when you are using any of the supported operating systems, browsers, or java plug-ins.
There is no workaround.
•
CSCdz23548
When you use Visual Switch Manager (VSM) to configure Catalyst 2900 XL and Catalyst 3500 XL switches, the configuration is not saved if you save it in VSM.
The workaround is to save the configuration by using the CLI.
•
CSCdz38000
CMS does not work when a switch is running the crypto software image and the vty lines are configured to use only secure shell (SSH) by using the transport input ssh line vty 0 15 interface configuration command.
The workaround is to allow SSH and Telnet access through the vty lines by using the transport input ssh telnet interface configuration command.
•
CSCdz71493
In the Trap Manager tab of the SNMP window, CMS does not show the VLAN Create/Delete traps option as enabled. This occurs after you create a trap manager, select the Create VLAN and Delete VLAN traps with other trap types, apply all the traps, and then select a new trap manager entry in the Current Managers list.
There is no workaround.
•
CSCdz75666
After you click Apply or Refresh in the SNMP window, the window size changes.
There is no workaround.
•
CSCdz79838
A Windows exception error sometimes occurs when you move a device that is displayed in the tree view.
There is no workaround.
•
CSCea09132
In the Trust Settings window of the QoS window, if you select Modify and try to change the trust settings, an error message appears, and you cannot change the trust settings.
The workaround is to change the trust values in the table in the Trust Settings window.
•
CSCea25787
If a port does not meets these conditions, it cannot join the port group of an EtherChannel:
–
Port group members must belong to the same VLANs and must all be static-access, multi-VLAN, or trunk ports.
–
The native VLAN ID, allowed VLANs, and pruning-eligible VLANs must be same for the trunk ports.
–
SPAN, port security, and 802.1X must not be enabled on port.
The workaround is to ensure that the port meets these conditions.
Note
Dynamic-access ports cannot belong to a channel group.
•
CSCea27601
The CMS files that are downloaded from the switch to your PC or terminal are not cached on the PC or terminal. The files are then downloaded again when CMS is relaunched.
There is no workaround.
•
CSCea27662
On a voice VLAN, if you configure the IP Phone to use priority tagging and VLAN 0 (the native VLAN) and if 802.1X is enabled on the interface, a switch running Release 12.1(12c)EA1 or later does not forward voice traffic correctly.
The workaround is to disable 802.1X on the interface or change the ID of the voice VLAN to a VLAN ID other than the port VLAN ID (PVID).
Resolved Caveats
These are the caveats that were resolved in this release:
•
"Caveats Resolved in Release 12.1(13)EA1" section
•
"CMS Caveats Resolved in Release 12.1(13)EA1" section
Note
The Catalyst 2955 switches are not supported by software releases earlier than 12.1(12c)EA1. The resolved caveats in these sections apply only to the Catalyst 2950 switches
Caveats Resolved in Release 12.1(13)EA1
These IOS caveats were resolved in Release 12.1(13)EA1:
•
CSCdy72613
This message is no longer displayed before and after a switch reloads:
Bootstrap Emulator called with code 45
•
CSCdy72718
A port now correctly sends and receives packets when it is configured at 100 Mbps.
•
CSCdy80581
The dot3StatsTable in the ETHERLIKE-MIB no longer incorrectly shows high values.
•
CSCdz00380
If you reconfigure a dynamic access port as a static access port and manually assign the same VLAN that was allocated by the VLAN Membership Policy Server (VMPS) server, the port now begins to learn new addresses and now behaves as dynamic access port.
•
CSCdz13456
If you change a management VLAN so that it is no longer the default VLAN, you can ping the VLAN Membership Policy Server (VMPS) server that is directly connected to it.
•
CSCdz13900
A SPAN destination port now forwards all traffic correctly.
•
CSCdz14682
Time-based DSCP quality of service (QoS) filters that have inactive access control lists (ACLs) are no longer in effect after the timerange has expired.
•
CSCdz16774
A VLAN no longer halts when an interface is added.
•
CSCdz22925
When you attach four access control lists (ACLs) that each have different masks to different interfaces, and then try to attach a policy to one of those interfaces, a no free mask error no longer appears.
•
CSCdz24645
On Gigabit Ethernet interfaces, you can now remove static MAC addresses by using the dot1dStaticStatus object in SNMP.
•
CSCdz25366
When there are multiple VLANs in the system with IP addresses configured on them, an interface can be added to any VLAN without halting the VLAN.
•
CSCdz31076
When configuring 802.1X with dynamic VLAN assignment on a switch, the Tunnel-Private-Group-ID field in the RADIUS server can now be configured with a VLAN number or a VLAN name.
•
CSCdz37442
A switch no longer reloads when Internet Group Management Protocol (IGMP) packets are received on an EtherChannel.
•
CSCdz51307
When sticky- or static port-security is configured on an interface that is also configured with a voice VLAN and an active Cisco IP Phone, the interface no longer learns voice traffic as sticky secure but as dynamic secure. When the switch is reloaded, any secure addresses present on the voice VLAN are not retained and are relearned as dynamic secure addresses.
CSCdz61209
When two switches are connected by redundant trunk ports, and the native VLAN on one of the switches is changed, the switch ports are no longer put into a port VLAN ID (PVID) inconsistent state.
•
CSCdz71152
Remote SPAN (RSPAN) can monitor a port channel when it is configured as a source interface.
•
CSCdz78970
A Port Fast-enabled port on a switch no longer generates a topology change (TC) when the interface for that port is up and then down.
•
CSCdz82994
When the aaa new-model and some vlans options are configured on a switch, this message no longer appears:
%AAAA-3-INVALIDLIST
CMS Caveats Resolved in Release 12.1(13)EA1
These CMS caveats were resolved in Release 12.1(13)EA1:
•
CSCdx76634
The data that is displayed when you click on the data point areas of a Stack Bar or Stack Area link graph is now correct.
•
CSCdy47214
You can now add a class to a new policy when you launch Device > QoS > Policies in Guide Mode.
•
CSCdy74927
You can create or modify ports in an EtherChannel.
•
CSCdz05782
The Add Class to QoS Policy window now appears when you click Create to create a quality of service (QoS) policy, enter a policy name that already exists, and then click Add Class.
•
CSCdz11352
When you select multiple interfaces from the quality of service (QoS) window, you can now override the class of service (CoS) settings for these interfaces.
•
CSCdz17299
If you delete an access control list (ACL) that is associated with a QoS and then open the Modify QoS Trust Settings window, the correct ACL is now shown to be associated with the QoS.
•
CSCdz21201
You can now create time-range entries that are active only on specific days.
•
CSCdz21478
When you select and delete multiple time ranges from the access control list (ACL) window, all of those time ranges are deleted.
•
CSCdz26503
You can use CMS to disable port security on cluster members.
•
CSCdz26631
When you run a link graph report on a connected port selected from the Front Panel view, the graph displays data for the first connected port, regardless of the port you select.
The workaround is to select a port from the Link Graph window instead of the Front Panel view.
•
CSCdz26886
When you select Device > STP and click the UpLinkFast tab, the Max. Update Rate now correctly appears.
Documentation Updates
You can access all Catalyst 2950 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
Corrections to the Catalyst 2950 Desktop Switch Hardware Installation Guide
These are corrections for the Catalyst 2950 Desktop Switch Hardware Installation Guide:
•
The Catalyst 2950 Desktop Switch Hardware Installation Guide shows an incorrect RPS cover. Figure 1 shows the correct RPS cover.
Figure 1 RPS Cover
•
The Catalyst 2950 Desktop Switch Hardware Installation Guide states incorrect maximum cable lengths for 100BASE-FX and 1000BASE-SX ports in full-duplex mode. These are the correct maximum cable lengths:
–
In full-duplex mode, the cable length from the 100BASE-FX port on a switch to an attached device cannot exceed 6562 feet (2 kilometers).
–
In full-duplex mode, the cable length from the 1000BASE-SX port on a switch to an attached device cannot exceed 1804 feet (550 meters).
Corrections to the Catalyst 2955 Hardware Installation Guide
These warnings have been updated for 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
These documents provide complete information about the switch and are available from this Cisco.com site:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
The software documents are not shipped with the product, but you can access them under the appropriate IOS software release on Cisco.com. 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 "Obtaining Documentation" section.
These publications provide more information about the switches:
For hardware information for the Catalyst 2950 and Catalyst 2955 switches, refer to these documents:
•
Catalyst 2950 Desktop Switch Hardware Installation Guide (order number DOC-7811157=)
•
Catalyst 2955 Hardware Installation Guide (order number DOC-7814944=)
For software information about Release 12.1(13)EA1 or later for the Catalyst 2950 and Catalyst 2955 switches, refer to these documents:
•
Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide (order number DOC-7811380=)
•
Catalyst 2950 and Catalyst 2955 Switch Command Reference (order number DOC-7811381=)
•
Catalyst 2950 and Catalyst 2955 Switch System Message Guide (order number DOC-7814233=)
For software information about Release 12.1(12c)EA1 for the Catalyst 2950 and Catalyst 2955 switches, refer to these documents:
•
Catalyst 2950 and Catalyst 2955 Software Configuration Guide (order number DOC-7815303=)
•
Catalyst 2950 and Catalyst 2955 Switch Command Reference (order number DOC-7815304=)
•
Catalyst 2950 and Catalyst 2955 Switch System Message Guide (order number DOC-7815306=)
Note
The Catalyst 2955 switches are not supported by software releases earlier than Release 12.1(12c)EA1.
For other information about related products, refer to these documents:
•
Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide (order number DOC-786460=)
•
Cluster Management Suite (CMS) online help (available only from the switch CMS software)
•
CWDM Passive Optical System Installation Note (not orderable but is available on Cisco.com)
•
1000BASE-T Gigabit Interface Converter Installation Notes (not orderable but is available on Cisco.com)
Obtaining Documentation
Cisco provides several ways to obtain documentation, technical assistance, and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
International Cisco web sites can be accessed from this 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 may have 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.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•
Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•
Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
•
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•
Streamline business processes and improve productivity
•
Resolve technical issues with online support
•
Download and test software packages
•
Order Cisco learning materials and merchandise
•
Register for online skill assessment, training, and certification programs
To obtain customized information and service, you can self-register on Cisco.com at this URL:
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•
Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Cisco TAC Website
You can use the Cisco TAC website 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 website, go to this URL:
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require 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 this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. 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 automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this 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). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•
Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
•
Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•
iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•
Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•
Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
This document is to be used in conjunction with the documentation listed in the "Related Documentation" section.
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, 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, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, TransPath, 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. (0303R)
Copyright ©2001- 2003, Cisco Systems, Inc.
All rights reserved.

















































