Table Of Contents
Determining the Software Version and Feature Set
Determining Which Files to Use
Upgrading a Switch by Using CMS
Upgrading a Switch by Using the CLI
Copying the Current Startup Configuration from the Switch to a PC or Server
Using the CLI to Upgrade a Catalyst 2940 or Catalyst 2950 LRE Switch
Using the CLI to Upgrade a Catalyst 2955 Switch or Non-LRE Catalyst 2950 Switch
Recovering from Software Failure
Cisco IOS Limitations and Restrictions
LRE Limitations and Restrictions
CMS Limitations and Restrictions
Cluster Limitations And Restrictions
Catalyst 2950 Hardware and Software Compatibility Matrixes
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
Cisco IOS Caveats Resolved in Release 12.1(19)EA1 (Catalyst 2940 Switches Only)
LRE Caveats Resolved in Cisco IOS Release 12.1(19)EA1
CMS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
CMS Caveat Resolved in Cisco IOS Release 12.1(19)EA1 (Catalyst 2940 Switches Only)
Corrections to the Catalyst 2940 Switch Software Configuration Guide
Corrections to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide
Correction to the Catalyst 2940 Switch Hardware Installation Guide
Correction to the Catalyst 2950 Switch Hardware Installation Guide
Corrections to the Catalyst 2955 Switch Hardware Installation Guide
Setting Up the Initial Configuration by Using the CLI-Based Setup Program
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 2940, Catalyst 2950, and Catalyst 2955 Switches, Cisco IOS Release 12.1(19)EA1
October 2003
Cisco IOS Release 12.1(19)EA1 runs on Catalyst 2940, Catalyst 2950, and Catalyst 2955 switches.
Review the new software features, open caveats, and resolved caveats sections for information specific to your switch. The information in this document refers to all the switches, unless noted otherwise.
These release notes include important information about this release and any limitations, restrictions, and caveats that apply to it. To verify that these are the correct release notes for your switch:
•
If you are installing a new switch, refer to the Cisco IOS release label on the rear panel of your switch.
•
If your switch is running, you can use the show version user EXEC command. See the "Determining the Software Version and Feature Set" section.
•
If you are upgrading to a new release, refer to the software upgrade filename for the Cisco IOS version.
For the complete list of Catalyst 2940, 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 release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.
Note
If you are upgrading a switch running Cisco IOS Release 12.1(13)EA1 or earlier that uses the 802.1X feature, or your switch has not run Cisco IOS Release 12.1(14)EA1, you must re-enable 802.1X after upgrading the software. For more information, see the "Cisco IOS Notes" section.
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 release are described in these sections:
•
"Hardware Not Supported" section
Hardware Supported
The Catalyst 2950 switch is supported by either the standard software image (SI) or the enhanced software image (EI). The Catalyst 2950 Long-Reach Ethernet (LRE) and Catalyst 2955 switches are supported only by the EI. The Catalyst 2940 switch supports some of the features supported by a Catalyst 2950 switch running the SI.
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 (SSHv2) protocol.
For information about the software releases that support the switches listed in Table 1, see the "Catalyst 2950 Hardware and Software Compatibility Matrixes" section.
Table 1 and Table 2 list the hardware supported by this release:
Table 1 Catalyst 2940, Catalyst 2950, and Catalyst 2955 Hardware Supported
Hardware Software Image DescriptionCatalyst 2940-8TT-S
—1
8 10/100 Ethernet ports and 1 10/100/1000 Ethernet port
Catalyst 2940-8TF-S
—1
8 10/100 Ethernet ports, 1 small form-factor pluggable (SFP) module slot, and 1 100BASE-FX port
Catalyst 2950-12
SI
12 fixed autosensing 10/100 Ethernet ports
Catalyst 2950-24
SI
24 fixed autosensing 10/100 Ethernet ports
Catalyst 2950C-24
EI
24 fixed autosensing 10/100 Ethernet ports and 2 100BASE-FX ports
Catalyst 2950G-12-EI
EI
12 fixed autosensing 10/100 Ethernet ports and 2 GBIC2 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 2950ST-8 LRE
EI
8 LRE ports, 2 10/100/1000 Ethernet ports3 , and 2 SFP4 module slots
Catalyst 2950ST-24 LRE
EI
24 LRE ports, 2 10/100/1000 Ethernet ports3, and 2 SFP module slots
Catalyst 2950ST-24 LRE 997
EI
24 LRE ports, 2 10/100/1000 Ethernet ports3, and 2 SFP module slots with DC-input power
Catalyst 2950SX-24
SI
24 fixed autosensing 10/100 Ethernet ports and 2 1000BASE-SX ports
Catalyst 2950SX-48-SI
SI
48 fixed autosensing10/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 ports5
Catalyst 2950T-48-SI
SI
48 fixed autosensing 10/100 Ethernet ports and 2 10/100/1000 Ethernet ports
Catalyst 2955C-12
EI
12 fixed autosensing 10/100 ports and 2 multimode6 100BASE-FX ports
Catalyst 2955S-12
EI
12 fixed autosensing 10/100 ports and 2 single-mode7 100BASE-LX ports
Catalyst 2955T-12
EI
12 fixed autosensing 10/100 ports and 2 10/100/1000 Ethernet ports3
1 The Catalyst 2940 switch supports some of the features supported by a Catalyst 2950 switch running the SI.
2 GBIC = Gigabit Interface Converter
3 The 10/100/1000 ports on a Catalyst 2950 LRE or 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 SFP = small form-factor pluggable
5 The 10/100/1000 interfaces on the Catalyst 2950T-24 switch do not support the half keyword in the duplex command.
6 MM = multimode
7 SM = single mode
Table 2 Other Hardware Supported
Hardware Software Image DescriptionCisco 575 LRE CPE1
—
1 fixed 10/100 port
Cisco 576 LRE CPE 997
—
1 fixed 10/100 port
Cisco 585 LRE CPE
—
4 fixed 10/100 ports
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
SFP devices
—
•
1000BASE-SX SFP module
•
1000BASE-LX\LH SFP module
•
1000BASE-ZX SFP module
•
1000BASE-T SFP module
•
CWDM2
1 CPE = customer premises equipment
2 CDWM = Coarse Wave Division Multiplexer
3 This feature is only supported when your switch is running the EI.
Hardware Not Supported
Table 3 lists the hardware that is not supported by this release.
Table 3 Hardware Not Supported
Hardware DescriptionGBIC module
1000BASE-T GBIC (model WS-G4582)
Redundant power system
Cisco RPS 600 Redundant Power System
Software Compatibility
For information about the recommended platforms for web-based management, operating systems and browser support, and installation procedures, refer to the "Getting Started with CMS" chapter of the software configuration guide.
Windows
This release uses a CMS plug-in (Windows only) that replaces the Java plug-in. You can download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/CMS-Plug-In-Win-1-0
Note
You must download the CMS plug-in to run CMS for this release.
Solaris
Java plug-in 1.4.1_02 is required to run CMS. You can download the Java plug-in and installation instructions from this URL:
http://www.cisco.com/public/sw-center/lan/java/1.4.1-02.html
Cluster Capability
When creating a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch.
A Catalyst 2940, Catalyst 2950, or Catalyst 2955 switch can be a command switch or a member of a switch cluster.
If your cluster has Catalyst 2950, Catalyst 2955, Catalyst 2940, 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.
Table 4 lists the cluster capabilities and minimum software versions for the switches. The switches are listed from highest to lowest. A lower-end switch cannot be the command switch of a switch listed above it in the table (for example, a Catalyst 2940 switch cannot be the command switch of a cluster that has Catalyst 2950 or Catalyst 3550 switches.)
Table 4 Switch Software and Cluster Capability
Switch Cisco IOS Release Cluster CapabilityCatalyst 3750
Release 12.1(11)AX or later
Member or command switch
Catalyst 3550
Release 12.1(4)EA1 or later
Member or command switch
Catalyst 2970
Release 12.1(11)AX later
Member or command switch
Catalyst 2955
Release 12.1(12c)EA1 or later
Member or command switch
Catalyst 2950
Release 12.0(5.2)WC(1) or later
Member or command switch
Catalyst 2950 LRE
Release 12.1(11)JY or later
Member or command switch
Catalyst 2940
Release 12.1(13)AY or later
Member or command switch
Catalyst 3500 XL
Release 12.0(5.1)XU 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 software, software features added in the latest release might not be reflected on switches running the older versions. For example, if you start CMS on a Catalyst 2900 XL switch running Cisco IOS Release 11.2(8)SA6, the windows and functionality can be different from a switch running Cisco IOS Release 12.0(5)WC(1) or later.
Note
The Cluster Management Suite (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.
For more information about clustering and CMS, including system requirements for running CMS, refer to the software configuration guide.
Downloading Software
This section describes these procedures for downloading software:
•
"Determining the Software Version and Feature Set" section
•
"Determining Which Files to Use" section
•
"Upgrading a Switch by Using CMS" section
•
"Upgrading a Switch by Using the CLI" section
•
"Recovering from Software Failure" section
For information about the software releases that support the switches, see the "Limitations and Restrictions" section.
Note
Before downloading software, read this section for important information.
Note
The Catalyst 2950-12 and Catalyst 2950-24 switches cannot be upgraded to Cisco IOS Release 12.1(6)EA2, Cisco IOS Release 12.1(6)EA2a, or Cisco IOS Release 12.1(6)EA2b. They can be upgraded to Cisco IOS Release 12.1(6)EA2c or later.
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 software configuration guide for this release.
For information about upgrading the LRE switch firmware, refer to the "Upgrading LRE Switch Firmware" section in the software configuration guide for this release.
Note
If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
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, and there are no other images on the switch, refer to the "Troubleshooting" chapter in the software configuration guide for detailed recovery procedures.
Determining the Software Version and Feature Set
The image is stored as a .bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version user EXEC command to see the software version that is running on your switch. In the display, check the line that begins with System image file is. This line shows the directory name in Flash memory where the image is stored. A couple of lines below the image name, you see Running Enhanced Image if you are running the EI or Running Standard Image if you are running the SI.
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.
Determining Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file. This file contains both the Cisco IOS image file and the CMS files. 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 non-LRE Catalyst 2950 switch from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command.
Table 5 lists the software filenames for this Cisco IOS release.
Table 5 Catalyst 2950 and Catalyst 2955 Cisco IOS Software Files
Filename Descriptionc2940-i6q4l2-tar.121-19.EA1.tar
Catalyst 2940 files. This includes the Cisco IOS image and CMS files.
c2950-i6k2l2q4-tar.121-19.EA1.tar
Catalyst 2950 SI1 and EI files. This includes the cryptographic Cisco IOS image and CMS files.
c2950-i6q4l2-tar.121-19.EA1.tar
Catalyst 2950 SI and EI files. This includes the Cisco IOS image and CMS files.
c2950lre-i6k2l2q4-tar.121-19.EA1.tar
Catalyst 2950 LRE EI files. This includes the cryptographic Cisco IOS image and CMS files.
c2950lre-i6l2q4-tar.121-19.EA1.tar
Catalyst 2950 LRE EI files. This includes the Cisco IOS image and CMS files.
c2955-i6k2l2q4-tar.121-19.EA1.tar
Catalyst 2955 EI files. This includes the cryptographic Cisco IOS image and CMS files.
c2955-i6q4l2-tar.121-19.EA1.tar
Catalyst 2955 EI files. This includes the Cisco IOS image and 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 "Cisco IOS Limitations and Restrictions" 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.
Upgrading a Switch by Using the CLI
To upgrade the switch software by using the CLI, see Table 5 to decide which software files that you need, and then follow these procedures in this order:
1.
Download the .tar files from Cisco.com, as described in the "Downloading the Software" section.
2.
Copy the current startup configuration file, as described in the "Copying the Current Startup Configuration from the Switch to a PC or Server" section.
3.
Use the CLI to extract the image and CMS files from the .tar file:
–
If your switch is a Catalyst 2940 or Catalyst 2950 LRE switch, see the "Using the CLI to Upgrade a Catalyst 2940 or Catalyst 2950 LRE Switch" section
–
If your switch is a Catalyst 2955 or non-LRE Catalyst 2950, switch, see the "Using the CLI to Upgrade a Catalyst 2955 Switch or Non-LRE Catalyst 2950 Switch" section.
Downloading the Software
This procedure is for copying the combined .tar file to a 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
If you do not have access to a TFTP server, download it before downloading the software.
Follow these steps to download the software from Cisco.com to your management station:
Step 1
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, click the link for your switch platform, and then follow the links on the page to select the correct. tar image file.
Step 2
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.
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 TFTP server.
Beginning in privileged EXEC mode, follow these steps to copy a switch configuration file to the TFTP server.
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 TFTP server.
Using the CLI to Upgrade a Catalyst 2940 or Catalyst 2950 LRE Switch
Use this procedure for upgrading your Catalyst 2940 or Catalyst 2950 LRE switch by using the archive download-sw privileged EXEC command to automatically extract and download the Cisco IOS image and CMS files to the switch. The archive download-sw command automatically deletes the old version and copies the new version to Flash memory if the Flash memory does not have space to store the old and new versions simultaneously. The archive download-sw command initiates this process:
•
It verifies adequate space on the Flash memory before downloading the new set of images.
•
If there is insufficient space on the Flash memory to hold both the old and the new images, it deletes the old set of images. The images are always stored in a subdirectory on the Flash memory. The subdirectory name is the same as the image release name, for example, flash:/c2940-i6q412-tar.121.19.EA1/
•
It replaces the old set of images with the new set of images. The set includes the Cisco IOS image and CMS files and, on Catalyst 2950 LRE switches, the LRE firmware files. You do not have to manually delete the CMS directory from Flash memory.
•
After the new set of files is downloaded, it automatically sets the BOOT environment variable.
•
If you enter the command with the /reload or the /force-reload option, it automatically reloads the switch after the upgrade.
For further information on this command, see the command reference for this release.
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
Log into the switch 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
Ensure that you have IP connectivity to the TFTP server by using this privileged EXEC command:
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, refer to the software configuration guide for this release.
Step 5
Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by using this privileged EXEC command:
archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /overwrite option overwrites the software image in Flash memory with the downloaded one.
Note
You must use the /overwrite option when upgrading a Catalyst 2940 switch.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For //location, specify the IP address of the TFTP server.
For /directory/image-name.tar, specify the directory (optional) and the image to download. Directory and image names are case-sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://198.30.20.19/c2940-i612-tar.121-19.EA1.tarYou can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
Your Telnet session ends when the switch reloads.
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.
Using the CLI to Upgrade a Catalyst 2955 Switch or Non-LRE Catalyst 2950 Switch
Use this procedure for upgrading your Catalyst 2955 or non-LRE Catalyst 2950 switch by copying the .tar file to the switch. You copy the Cisco IOS image and CMS files to the switch from a TFTP server and then extract the files by entering the archive tar command, with these results:
•
Changes the name of the current image file to the name of the new file that you are copying and replaces the old image file with the new one. Perform this step only if you have space available on your switch.
•
Disables access to the CMS pages and deletes the existing CMS files before the software upgrade to avoid a conflict if users access the web pages during the software upgrade.
•
Reenables access to the CMS pages after the upgrade is complete.
Note
If you are upgrading a switch that is running a release earlier than Cisco IOS Release 12.1(11)EA1, this release includes a bootloader upgrade. The bootloader can take up to 30 seconds to upgrade.
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
Log into the switch 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 CMS files:
switch# delete flash:html/*Press Enter to confirm the deletion of each file. Do not press any other keys during this process.
Step 5
Enter this command to copy the new image and CMS files to Flash memory:
CautionIn this step, the archive tar command copies the .tar file that contains both the image and the CMS files. If you are upgrading from a release earlier than Cisco IOS Release 12.1(6)EA2, use the tar command instead of the archive tar command.
switch# archive tar /x tftp://server_ip_address/path/filename.tar flash: Loading /path/filename.tar from server_ip_address (via VLAN1):!) extracting info (110 bytes)extracting c2950-i6q4l2-mz.121-13.EA1c.bin (2239579 bytes)!!!!!!!!!!!!!!!!!!!!html/ (directory)extracting html/Detective.html.gz (1139 bytes)!extracting html/ieGraph.html.gz (553 bytes)extracting html/DrawGraph.html.gz (787 bytes)extracting html/GraphFrame.html.gz (802 bytes)!...Depending on the TFTP server being used, you might need to enter only one slash (/) after the server_ip_address in the archive tar command.
Step 6
Display the name of the running (default) image file (BOOT path-list). This example shows the name in italic:
switch# show boot BOOT path-list: flash:current_image Config file: flash:config.text Enable Break: 1 Manual Boot: no HELPER path-list: NVRAM/Config file buffer size: 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.EA1c.bin
Note
If the show boot command entered in Step 6 displays no image name, you do not need to enter this command; the switch automatically finds the correct file to use when it resets.
Step 9
Return to privileged EXEC mode:
switch(config)# 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 reloads.
After the switch reboots, use Telnet to return to the switch, and enter the show version user EXEC command to verify the upgrade procedure. If you have a previously opened browser session to the upgraded switch, close the browser, and start it again to ensure that you are using the latest CMS files.
Recovering from Software Failure
If the software fails, you can reload the software. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the software configuration guide for your switch.
Installation Notes
You can assign IP information to your switch by using one of these methods:
•
The Express Setup program on Catalyst 2940 and Catalyst 2950 switches (including Catalyst 2950 LRE switches.) The Express Setup program is not supported on Catalyst 2955 switches.
Refer to the "Quick Setup" chapter in the Catalyst 2940 and Catalyst 2950 hardware installation guides for more information about Express Setup.
•
The CLI-based setup program.
This procedure is described in the Catalyst 2940 and Catalyst 2950 hardware installation guides and in the "Documentation Updates" section for the Catalyst 2955 switches.
•
The Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration. Refer to the software configuration guide for your switch.
•
Manually assigning an IP address. Refer to the software configuration guide for your switch.
Note
If you are upgrading a switch that uses the 802.1X security feature, you must re-enable 802.1X after upgrading the software. For more information, see the "In Cisco IOS Release 12.1(14)EA1, the implementation for 802.1X changed from the previous release. Some global configuration commands became interface configuration commands, and new commands were added." section.
New Features
These are the new supported hardware and the new software features provided in Cisco IOS Release 12.1(19)EA1.
New Hardware Features
There is no new hardware supported by this release. For a complete list of supported hardware, see the "Hardware Supported" section.
New Software Features
These features are supported by the Catalyst 2940, Catalyst 2950, and Catalyst 2955 switches:
•
Internet Group Management Protocol (IGMP) snooping for IGMP version 3 to limit the flooding of multicast traffic
•
IGMP throttling for configuring the action when the maximum number of entries is in the IGMP forwarding table
•
IGMP report suppression for sending only one IGMP report per multicast router query to the multicast devices (supported only for IGMPv1 or IGMPv2 queries)
Note
In the software documentation, IP refers to IP version 4 (IPv4). Layer 3 IP version 6 (IPv6) packets are treated as non-IP packets
•
CMS support for these new features:
–
The option to install CMS to your computer rather than to download it from the cluster every time you start a CMS session.
Note
CMS is downloaded to your browser each time you launch CMS. You can increase the speed at which CMS loads by permanently installing CMS on your PC or workstation. Select CMS > Installation and Distributions, and click Install. CMS will be installed locally and load faster the next time that you launch it.
–
A feature bar, which offers networking features to configure and reports, graphs, and statistics to display. These options were previously on the menu bar, which is now dedicated to CMS service options. You can choose features from menus on the Features tab or search for them on the Search tab.
–
Device-specific online help. You now see help topics below labels that name the devices to which the information applies. You see topics only for the networking features in the cluster.
Note
This release uses a CMS plug-in (Windows only) that replaces the Java plug-in.You must download the CMS plug-in to run CMS for this release. You can download the plug-in from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/CMS-Plug-In-Win-1-0
The CMS plug-in includes a console window that you can use for troubleshooting. For more information, see the "Documentation Updates" sectionFor more information about new CMS features, click Help > What's New from the online help.
These features only apply to Catalyst 2950 and Catalyst 2955 switches:
•
Unicast MAC filtering to drop packets with specific source or destination MAC addresses (available only on the Catalyst 2950 running the EI, the Catalyst 2950 LRE, and the Catalyst 2955.)
•
Support for the SSHv2 server application (available only in the cryptographic Catalyst 2950 EI, the Catalyst 2950 LRE, and Catalyst 2955 crytopgraphic software images.)
•
Port blocking on forwarding unknown unicast and multicast traffic (available only on the Catalyst 2950G-12-EI, 2950G-24-EI, 2950G-24-EI-DC, and 2950G-48-EI, Catalyst 2950 LRE, and Catalyst 2955 switches.)
This feature only applies to Catalyst 2955 switches:
•
DHCP server for automatic assignment of IP addresses and other DHCP options to IP hosts (available only on the Catalyst 2955 switch.)
This feature only applies to Catalyst 2950 LRE switches:
•
Express Setup for quickly configuring a Catalyst 2950 switch for the first time with basic IP information, contact information, switch and Telnet passwords, and Simple Network Management Protocol (SNMP) information through a browser-based program.
For more information, refer to the "Quick Setup" chapter of the hardware installation guide.
•
DHCP snooping to filter untrusted DHCP messages between untrusted hosts and DHCP servers (available only with the EI.)
This feature only applies to Catalyst 2940 switches:
•
Automatic medium-dependent interface crossover (Auto-MDIX) capability on 10/100 and 10/100/1000 Mbps interfaces that enables the interface to automatically detect the required cable connection type (straight-through or crossover) and to configure the connection appropriately.
Note
Auto-MDIX is not supported on SFP module interfaces.
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 2940, Catalyst 2950, and Catalyst 2955 switches unless otherwise noted.
These are the limitations and restrictions:
•
"Cisco IOS Limitations and Restrictions" section
•
"LRE Limitations and Restrictions" section
•
"CMS Limitations and Restrictions" section
•
"Cluster Limitations And Restrictions" section
•
"Catalyst 2950 Hardware and Software Compatibility Matrixes" section
Cisco IOS Limitations and Restrictions
These limitations and restrictions apply to the Cisco IOS configuration:
•
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)
•
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 a 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 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 autonegotiation. (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 2940, 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 Cisco IOS Release 12.0(5)WC2b or earlier.
There is no workaround. (CSCdw48441)
•
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 for Cisco IOS Release 12.1 and the Cisco IOS IP and IP Routing Command Reference for Cisco IOS Release 12.1.
•
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)
•
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)
•
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)
•
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. (CSCdz74685)
•
In Cisco IOS Release 12.1(13)EA1 or later, 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)
•
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. (CSCea12888)
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.
•
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. (CSCea23138)
•
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)
•
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.
•
When a 10/100 switch port is connected to a 10/00 port on a hub and another 10/100 port on the hub is connected to a 10/100 port on another switch, when one of the switches restarts, the link state might transition from down to up, and these messages might appear:
%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to down%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state to upThen the switch that restarted does not forward traffic until the spanning-tree state enters the forwarding state. This can occur on a switch running Cisco IOS Release 12.1(13)EA1 or later.
There is no workaround. (CSCea47230)
LRE Limitations and Restrictions
These LRE limitations that only apply to Catalyst 2950 LRE switches:
•
VLAN-tagged packets from multiple VLANs with the same source MAC address that are received on different Cisco 585 LRE CPE Ethernet ports create a single MAC address entry (ingress port entry). Any network designed with the assumption that MAC addresses are maintained per VLAN does not work.
There is no workaround. The Ethernet port on the Cisco 585 LRE CPE does not support VLANs. All the ports are assumed to be in the same VLAN. (CSCdx03708)
•
Maximum-sized ISL frames (frames between 1537 and 1544 bytes) are discarded by the CPE device on ingress. Some chips and switches on the CPE device support a maximum frame size of 1536 bytes, which causes any maximum-sized ISL frames coming into the CPE from an end device or from an LRE switch to be discarded.
There is no workaround. You must ensure that the network does not send ISL tagged frames of sizes between 1537 and 1544 bytes to an LRE switch. (CSCdx25940)
•
The system runs out of memory and fails after too many RMON buckets are requested.
There is no workaround; only 1000 buckets per interface are supported. (CSCdy38390)
•
The flow control autonegotiation settles in the incorrect outcome if you use a Cisco-made 1000BASE-T GBIC with any switch not listed in the Table 1 of the 1000BASE-T GBIC Switch Compatibility Matrix:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c2900xl/1000gbic/1000comp.htm.
The workaround is to use the Cisco 1000BASE-T GBIC only with compatible switches. (CSCdy53369)
•
The Flash memory write operation is slower on LRE switches than on non-LRE switches.
There is no workaround. (CSCdy55897)
•
The Cisco 585 LRE CPE has four Fast Ethernet ports. When the CPE is connected to an LRE switch, the default value for the maximum number of secure MAC addresses is 1. You can use the show port-security command to display the current maximum value.
The workaround is to use the switchport port-security maximum value interface configuration command to change the default value. For interfaces connected to Cisco 575 LRE and Cisco 576 LRE 997 CPEs, the default value can be 1. For interfaces connected to Cisco 585 LRE CPEs, the value can be 5 because the CPE has four Fast Ethernet ports and one additional MAC address. (CSCdy73748)
•
The Cisco 575 LRE or the Cisco 576 LRE 997 CPE does not support all of the Fast Ethernet statistics displayed by the show controllers ethernet-controller longreachethernet 0/4 cpe command. The Cisco 585 LRE CPE supports all the LRE and CPE Fast Ethernet statistics.
There is no workaround. These CPE Fast Ethernet statistics are supported by the Cisco 575 LRE CPE (CSCdy89348):
–
1 Transmit receive 0 bytes
–
0 Bytes
–
0 Unicast frames
–
0 Broadcast frames
–
0 Pause frames
–
0 Alignment errors
–
0 One collision frames
–
0 Multiple collisions
–
0 Undersize frames
–
0 Late collisions
–
0 Oversize frames
–
0 Excess collisions
–
0 FCS errors
–
0 Deferred frames
•
When the entPhysicalTable object is retrieved, the copper physical entry is not included.
There is no workaround. (CSCdz06748)
•
When a 802.1X Protocol-enabled client attempts to connect to a Catalyst 2950 LRE switch through a Cisco 585 LRE CPE with 802.1X configured on a port, the client cannot be authenticated. This problem does not affect the Cisco 575 LRE CPE. The show dot1x interface interface configuration command displays the port state as unauthorized.
There is no workaround. (CSCdz22965)
•
When a Fast Ethernet port on a Cisco 585 LRE CPE is in half-duplex mode and the rate at which the port receives packets is higher than rate at which it can forward packets, the Pause Frames counter for the CPE port increments.
There is no workaround. (CSCea41362)
•
On a Catalyst 2950 LRE switch running Cisco IOS Release 12.1(11)YJ4 or later, a Cisco 575 LRE CPE or a Cisco 576 LRE 997 CPE that does not have an LRE link but is connected to a remote device through the Ethernet link might see repeated flaps on the Ethernet link. This does not occur on a Cisco 585 LRE CPE.
There is no workaround. (CSCeb01097)
•
When a Cisco Catalyst 2950 LRE running Cisco IOS 12.1(14)EA1 or Cisco IOS 12.1(11)YJ is connected to Cisco 575 LRE CPE, the Fast Ethernet link on the CPE port fails to activate if you change the CPE speed setting from 10 to 100 while the CPE duplex mode is set to half or full.
The workaround is to reset the CPE port by using the cpe shutdown followed by the no cpe shutdown interface configuration command. This activates the FastEthernet link on the CPE port. (CSCeb35007)
CMS Limitations and Restrictions
These limitations apply to CMS configuration:
•
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. (CSCdv82352)
Note
This error only occurs with Java plug-in 1.4.0.
•
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. (CSCdw87550)
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.
•
After you click Apply or Refresh in the SNMP window, the window size changes.
There is no workaround. (CSCdz75666)
•
When you enable log scaling for Link Graphs, the Y-axis scale becomes illegible.
There is no workaround. (CSCdz81086)
•
The CMS window does not return to full size after resizing the NE or IE when using Netscape version 6.xx on Solaris and Linux. This is a Netscape browser problem.
There is no workaround. (CSCea01179)
•
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. (CSCea27601)
•
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)
•
The icons on the tool bar are blank when you unlock the PC while CMS is running or you interrupt the screen saver on your PC.
The workaround is to resize the CMS window so that the window is refreshed correctly. (CSCea80753)
•
If you change the password or start the authentication process while CMS is running, HTTP requests sent by the switch fail.
The workaround is to close all browser sessions and then relaunch CMS. (CSCeb33995)
•
Running pop-up blocking software with a browser prevents CMS from loading.
The workaround is to disable the pop-up blocking software before launching CMS. (CSCec24615)4
•
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.
•
Certain combinations of port features create configuration conflicts (see Table 6 for the port configuration conflicts). If you try to enable incompatible features, a warning message appears in CMS, and you cannot make the change. Reload the page to refresh CMS.
In Table 6, 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 6 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.
Cluster Limitations And Restrictions
This limitation and restriction applies to the cluster configuration:
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. (CSCdz88305)
Catalyst 2950 Hardware and Software Compatibility Matrixes
Some Catalyst 2950 switches are not supported by certain software releases.
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. In this table, Yes means that the switch is supported by the software release; No means that the switch is not supported by the release.
The Catalyst 2950G-12-EI, 2950G-24-EI, 2950G-24-EI-DC, and 2950G-48-EI switches are supported by Cisco IOS Release 12.1(6)EA2 or later.
The Catalyst 2950SX-24 switches are supported by Cisco IOS Release 12.1(9)EA1d or later.
The Catalyst 2955 switches are supported by Cisco IOS Release 12.1(12c)EA1 or later.
The Catalyst 2950ST-8 LRE and 2950ST-24 LRE switches are supported by Cisco IOS Release 12.1(11)YJ or later.
The Catalyst 2950ST-24 LRE 997 switches are supported by Cisco IOS Release 12.1(11)YJ4 or later.
The Cisco LRE CPE devices are not supported by certain Catalyst 2950 LRE switches. In Table 8, Yes means that the CPE is supported by the switch; No means that the CPE is not supported by the switch.
Important Notes
Note
These important notes apply to all Catalyst 2940, Catalyst 2950, and Catalyst 2955 switches unless otherwise noted.
This section describes important information related to this release. These sections are included:
Cisco IOS Notes
These notes applies to Cisco IOS configuration:
•
In Cisco IOS Release 12.1(14)EA1, the implementation for 802.1X changed from the previous release. Some global configuration commands became interface configuration commands, and new commands were added.
If you have 802.1X configured on the switch and you upgrade to Cisco IOS Release 12.1(14)EA1 or later, the configuration file will not contain the new commands, and 802.1X will not operate. After the upgrade is complete, make sure to globally enable 802.1X by using the dot1x system-auth-control global configuration command. For more information, refer to the software configuration guide for this release.
•
When you enable port security on an interface that is also configured with a voice VLAN, you must set the maximum allowed secure addresses on the port to 2 plus the maximum number of secure addresses allowed on the access VLAN. When the port is connected to a Cisco IP phone, the IP phone requires up to two MAC addresses. The IP address of the phone is learned on the voice VLAN, and it might or might not be learned on the access VLAN. Connecting a PC to the IP phone requires additional MAC addresses.
•
IGMP filtering controls only group specific query and membership reports, including join and leave reports. It does not control general IGMP queries.
•
The management interface configuration command is not supported in Cisco IOS 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.
•
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)
•
The Guest VLAN might not assign a DHCP address to some clients. This is a problem with the 802.1X client, not with the switch.
The workaround is to either release and renew the IP address or to change the default timers. The following examples shows typical interface timer changes:
dot1x timeout quiet-period 3
dot1x timeout tx-period 5
CMS Notes
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 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.cisco.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 from each other, the change has no effect on the way the ACL filters traffic.
•
In the Front Panel view or Topology view, CMS does not display error messages in read-only mode for these switches:
–
Catalyst 2900 XL or Catalyst 3500 XL member switches running Cisco IOS Release 12.0(5)WC2 or earlier
–
Catalyst 2950 member switches running Cisco IOS Release 12.0(5)WC2 or earlier
–
Catalyst 3550 member switches running Cisco IOS Release 12.1(6)EA1 or earlier
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 an LRE switch, the CPE devices that are connected to the switch do not appear. The Bandwidth and Link graphs also do not appear in these views.
Open Caveats
These are the open caveats in this release:
•
"Open Cisco IOS Caveats" section
Note
All open caveats listed in these sections apply to all the Catalyst 2940, Catalyst 2950, and Catalyst 2955 switches unless otherwise noted.
Open Cisco IOS Caveats
These are the open Cisco IOS configuration caveats:
•
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.
•
CSCdx95501
When a community string is assigned by the cluster command switch, you cannot get any dot1dBridge MIB objects using a community string with a VLAN entity from a cluster member switch.
The workaround is to manually add the cluster community string with the VLAN entity on the member switches for all active VLANs shown in the show spanning-tree summary display. This is an example of such a change, where cluster member 3 has spanning-tree on vlan 1-3 and the cluster commander community string is public@es3.
Switch(config)#snmp community public@es3@1 ROSwitch(config)#snmp community public@es3@2 ROSwitch(config)#snmp community public@es3@3 RO•
CSCea69056
When 10/100 Mbps ports are connected to one another through media converters and 100BASE-FX media, the link fails to activate.
There is no workaround.
•
CSCea87794
When MAC addresses are learned and deleted at high rates on a switch, addresses on Dynamic Access Ports might need to be authenticated from the VLAN Membership Policy Server (VMPS) again, causing traffic to drop until authentication is complete.
The workaround is to reduce the MAC address learning and MAC address movement activity.
•
CSCeb36925
A FastEthernet port that has been configured at 10 Mbps might stay linked up or link flap after the device to which is have been linked to has been shut down.
The workaround is to enter the shutdown and then the no shutdown interface configuration commands on the interface.
•
CSCeb55987
When UplinkFast is configured on a Catalyst 2950 or Catalyst 3550 switch, the MAC address of the switch is not forwarded to the uplink switch through the new link. This temporarily interrupts communication with the management VLAN and delays convergence of UplinkFast.
There is no workaround.
•
CSCec13986
After a topology change in Spanning Tree Protocol (STP) occurs, some terminals connected to the management VLAN can transfer data because the affected switch ports start forwarding before they move to the forwarding state.
Note
If the terminal does not belong to Management VLAN, this failure does not occur.
The workaround is to place the ports in static access mode for a single VLAN, if possible in the topology.
Open CMS Caveats
These are the open CMS configuration caveats:
•
CSCdz01037
CMS does not work when a switch is running the crypto software image and the vty lines are configured to use only 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.
•
CSCeb11990
On a switch running Cisco IOS Release 12.1 or later, the Bridge Parameter tab in the STP window incorrectly shows IBM as a STP bridge protocol option. This option is no longer supported on the switch.
There is no workaround.
•
CSCeb23334
On a switch running Cisco IOS Release 12.1 or later, CMS does not validate STP port-priority configuration values before they are added to the switch configuration. When these invalid values are added to the switch configuration, an error message does not appear.
There is no workaround.
•
CSCeb23416
On a switch running Cisco IOS Release 12.1 or later, CMS does not validate STP port-path-cost configuration values before they are added to the switch configuration. When these invalid values are added to the switch configuration, an error message does not appear.
There is no workaround.
•
CSCeb23592
CMS does not validate STP bridge parameter values before they are added to the switch. When invalid values are applied, the attempt fails without a warning message. This applies to all switches running Cisco IOS 12.1 or later.
There is no workaround. Make sure the input configuration values are valid before applying them to the switch.
•
CSCeb38967
When CMS is in read-only mode, an error message appears if the online help is launched from the QoS Graph window.
There is no workaround.
•
CSCeb40625
Shaped bandwidth weights are invalid if the sum of their reciprocals is greater than 1 and the weight of a queue is zero. CMS does not configure these invalid bandwidth weights.
There is no workaround.
•
CSCeb05183
On the Catalyst 2820 and Catalyst 1900 switches, the Port Settings table might show incorrect information in the interface description and duplex columns.
There is no workaround.
•
CSCec03397
The settings on the Catalyst 2950 LRE switch ports cannot be modified by using the Port Settings window.
There is no workaround.
•
CSCec08618
When you change the Spanning Tree Protocol (STP) port priority on a switch that is running Cisco IOS Release 12.1(19)EA1 or later, the value must be in the range of 0 to 240 and in increments of16. If you enter a value that is not an increment of 16, the configuration fails, and no error message appears.
The workaround is to enter values from 0 to 240 that are in increments of 16.
•
CSCec08662
If UplinkFast is enabled and you enter a value in the Path Cost field in the STP Modify Port Parameters window, 3000 is automatically added to the configured-STP cost value. For example, if the path cost is 10, the actual value becomes 3010. If you disable UplinkFast, the path- cost value changes to its originally configured value of 10.
•
CSCec09433
You cannot attach or remove an access control list (ACL) to or from an interface when you are in guide mode.
The workaround is to use expert mode to attach or remove an ACL to or from an interface.
•
CSCec16057
CMS does not recognize the Coarse Wave Division Multiplexer (CWDM) small form-factor pluggable (SFP) module on Catalyst 2940 switches, even though the CWDM SPF is supported by the switches.
There is no workaround
•
CSCec18805
When you launch the IP Multicast wizard, multicast-enabled devices do not appear in the list of multicast-enabled devices.
There is no workaround. The wizard does not display multicast-enabled devices.
•
CSCec24473
When you right-click on a Catalyst 3750 switch in the Front Panel view, these pop-up menu options do not appear:
–
The delete-cluster menu option if the Catalyst 3750 switch is a command switch.
–
The remove-from cluster option if the Catalyst 3750 switch is a member switch.
The workarounds are to select these menu options from the feature bar:
–
Select Cluster > Delete Cluster to delete a cluster from a command switch.
–
Select Cluster > Remove from Cluster to remove a member switch.
•
CSCec34831
When you click the Highlight VLAN Port Membership Modes button in the VLAN window of a switch, and that switch front panel is not displayed in Front Panel View, CMS brings the Front Panel View to the foreground. However, the front panel view of the switch is not displayed and you cannot see the highlighted ports.
These are the workarounds:
–
From the Front Panel View device diagram, check the switch box so that the front panel appears in the Front Panel View, then click the Highlight VLAN Port Membership Modes button in the VLAN window. The front panel is displayed, and you can see the highlighted ports.
–
After you click the Highlight VLAN Port Membership Modes button in the VLAN window, you should check the box for the switch in the Front Panel View device diagram. The front panel appears, and you can see the highlighted ports.
•
CSCec45975
When you click Previous instead of Finish in the Save Configuration window, the configuration for the interfaces is not applied to the member devices.
The workaround is to click the Finish button to apply the configuration to member devices. If you need to modify the configuration, you need to launch the configuration wizard again.
•
CSCec47247
The IGMP Report Window does not list all the entries in the table.
There is no workaround.
•
CSCec47247
The IGMP Report Window does not list all the entries in the table.
There is no workaround.
Resolved Caveats
These are the caveats that were resolved in this release:
•
"Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(19)EA1" section
•
"Cisco IOS Caveats Resolved in Release 12.1(19)EA1 (Catalyst 2940 Switches Only)" section
•
"LRE Caveats Resolved in Cisco IOS Release 12.1(19)EA1" section
•
"CMS Caveats Resolved in Cisco IOS Release 12.1(19)EA1" section
Note
All open caveats listed in these sections apply to both the Catalyst 2950 and Catalyst 2955 switches unless otherwise noted.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
These Cisco IOS caveats were resolved in this release:
•
CSCdz23548
When you use Visual Switch Manager (VSM) to configure a switch, the configuration is now saved if you save it in VSM.
•
CSCea63436
The source port Multicast VLAN Registration (MVR) membership on a switch no longer flaps when the switch is in MVR dynamic mode.
•
CSCeb05733
When an LACP channel group with hot standby ports is restarted by using the shutdown and no shutdown interface configuration commands, this error message no longer appears:
%SM-4-BADEVENT: Event 'link_down' is invalid for the current state 'link_down':•
CSCeb33988
When a switch powers on and many traps are enabled, the switch no longer fails to generate the coldStart trap.
•
CSCeb47201
An ICMP echo_request is now sent from one port channel to another port when the MAC address table is cleared on a Catalyst 2950G-48 switch.
•
CSCeb49033
Configuring mac-address-table notification under these conditions no longer causes the switch to run out of memory and fail:
–
Large number of MAC addresses flapping.
With the wrong setup, a single host with multiple network interface cards (NICs) can be connected to the switch by using the same MAC address in the same VLAN. As the result, the MAC address flaps from port to port, generating many adds and drops from the MAC address table.
–
MAC address flooding attack
With a MAC address flooding attack, a single NIC host sends out many packets with different source MAC addresses, which also generates many adds for the MAC address table.
•
CSCeb61370
If a Cisco Catalyst WS-2950G-48-EI switch that is running the cryptographic image has the maximum number of supported 128 virtual ports (number of trunk ports multiplied by the number of VLANs) and is also the switch master, the show running-configuration privileged EXEC commands no longer fail, and memory fragmentation error messages no longer appear.
•
CSCeb62247
With light Layer 2 multicast traffic (about 10 Mbps line rate), IP IGMP query messages no longer fail to reach the Catalyst 2950, which had caused the IP IGMP snooping feature to fail.
Cisco IOS Caveats Resolved in Release 12.1(19)EA1 (Catalyst 2940 Switches Only)
These Cisco IOS caveats were resolved in this release. They only apply to Catalyst 2940 switches:
•
CSCdx47532
When a switch logs 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
the switch functionality is no longer affected.
•
CSCdz07948
When a switch is connected through redundant EtherChannels to another switch and that switch is the Spanning Tree Protocol (STP) root switch, a loop no longer occurs when that root switch is rebooted.
•
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 no longer generates a leave message to the router to quickly prune the multicast router.
•
CSCea05146
When using an SNMP query on the ciscoFLASHPartitionTable, some attributes defined by the MIB now appear. For example, Size, FreeSpace, and FileCount are defined by the MIB and are shown in the query result.
•
CSCea05157
These variables in c2900PortTable MIB no longer return a value of zero:
–
c2900PortStatus
–
c2900PortViolationAction
–
c2900PortMayLearnAddress
–
c2900PortMayForwardFrames
–
c2900PortBufferCongestionControl
•
CSCea34287
On switches running Cisco IOS 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 now 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 now match, and the candidate ports can join the port channel.
•
CSCin26670
The vtpVlanApplyStatus MIB object now returns value 2, which appears when the apply operation successfully creates or deletes a VLAN.
LRE Caveats Resolved in Cisco IOS Release 12.1(19)EA1
These LRE caveats were resolved in this release. They apply only to Catalyst 2950 LRE switches.
•
CSCea04914
If a sequence is configured when an LRE interface is shut down, the sequence can now be used for determining the profile. The switch no longer attempts to re-establish the link through the default LRE-10 profile.
•
CSCea55990
You can now disable CPE toggle on a link from a Cisco 585 LRE CPE to a remote Ethernet device (such as PC). For more information, refer to the software configuration guide for this release.
CMS Caveats Resolved in Cisco IOS Release 12.1(19)EA1
These CMS caveats were resolved in this release:
•
CSCdz15119
If only one management VLAN interface is configured on a switch, you can now change the management VLAN interface to another management VLAN interface by using CMS.
•
CSCeb05183
On the Catalyst 2820 and Catalyst 1900 switches, The Port Settings table no longer shows incorrect information in the interface description and duplex columns for Catalyst 1900 and 2830 switches.
CMS Caveat Resolved in Cisco IOS Release 12.1(19)EA1 (Catalyst 2940 Switches Only)
This CMS caveat was resolved in this release. It applies only to Catalyst 2940 switches:
•
CSCdz71493
In the Trap Manager tab of the SNMP window, CMS now shows the VLAN Create/Delete traps option as enabled 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.
Documentation Updates
You can access all Catalyst 2940 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2940/index.htm
You can access all Catalyst 2950 and Catalyst 2955 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/cat2950/index.htm
This section provides these updates to the product documentation:
•
"Corrections to the Catalyst 2940 Switch Software Configuration Guide" section
•
"Corrections to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide" section
•
"Correction to the Catalyst 2940 Switch Hardware Installation Guide" section
•
"Correction to the Catalyst 2950 Switch Hardware Installation Guide" section
•
"Corrections to the Catalyst 2955 Switch Hardware Installation Guide" section
These changes will be included in the next version of the documentation.
Corrections to the Catalyst 2940 Switch Software Configuration Guide
These are corrections for the "Getting Started with CMS" chapter:
•
The CMS plug-in includes a console window that you can use to troubleshoot CMS or to view the CLI commands from CMS.
When CMS is running, press F2 to display or to hide the CMS console. Press F3 to display or to hide the CLI commands that CMS is sending.
•
The chapter incorrectly states that Java plug-in 1.4.1 is required for Solaris. Java plug-in 1.4.1_02 is required to run CMS on Solaris. You can download it from this URL:
http://www.cisco.com/public/sw-center/lan/java/1.4.1-02.html
Corrections to the Catalyst 2950 and Catalyst 2955 Switch Software Configuration Guide
These are corrections for the "Getting Started with CMS" chapter:
•
The CMS plug-in includes a console window that you can use to troubleshoot CMS or to view the CLI commands from CMS.
When CMS is running, press F2 to display or to hide the CMS console. Press F3 to display or to hide the CLI commands that CMS is sending.
•
The chapter incorrectly states that Java plug-in 1.4.1 is required for Solaris. Java plug-in 1.4.1_02 is required to run CMS on Solaris. You can download it from this URL:
http://www.cisco.com/public/sw-center/lan/java/1.4.1-02.html
Correction to the Catalyst 2940 Switch Hardware Installation Guide
The CMS requirements described in the "Managing the Switch by Using the Cluster Management Suite" chapter are no longer correct. Refer to the "Getting Started with CMS" chapter of the software configuration guide for the latest CMS requirements.
Correction to the Catalyst 2950 Switch Hardware Installation Guide
The "Quick Setup" chapter states that the Express Setup program is supported on Catalyst 2950 LRE switches running Cisco IOS Release 12.1(14)EA1 or later. Express Setup is only supported on Catalyst 2950 LRE switches running Cisco IOS Release 12.1(19)EA1 or later.
Corrections to the Catalyst 2955 Switch Hardware Installation Guide
This section provides This section provides these updates to the Catalyst 2955 Hardware Installation Guide:
•
Figure B-9 in the "Connectors and Cables" appendix is incorrect. Figure 1 shows the correct schematics of four twisted-pair crossover cables for 10/100 ports.
Figure 1 Four Twisted-Pair Crossover Cable Schematic for 10/100 Ports
•
The information in Table A-3 in the "Technical Specifications" appendix of the Catalyst 2955 Hardware Installation Guide is incorrect. Table 9 lists the correct information:
Table 9 Fiber-Optic Port Specifications for the Catalyst 2955S-12 Switch
Fiber-Port Power Levels Catalyst 2955S-12 (100BASE-LX SM1 )Optical transmitter wavelength
1300 nm2
Optical receiver sensitivity for 9/125-micron SM cabling
-38 to -31 dBm3
Optical transmitter power for 9/125-micron cabling
-15 to -8 dBm
1 SM = single-mode fiber
2 nm = nanometer
3 dBm = decibel milliwatt
•
This information was omitted from the Catalyst 2955 Hardware Installation Guide:
–
The Catalyst 2955 switches do not have fans.
–
The Catalyst 2955 switch can operate with one or two power supplies. Each power supply input has an associated LED that shows the power supply status.
If the switch is in single power mode and only power supply A is present and functioning, the LED for power supply B is always green, and the LED for power supply A shows the true status.
If the switch is in single power mode and only power supply B is present and functioning, the LED for power supply A is always green, and the LED for power supply B shows the true status.
•
The CLI-based setup program is not included in the Catalyst 2955 Hardware Installation Guide. To assign an IP address to a new switch, follow the steps in this procedure:
Setting Up the Initial Configuration by Using the CLI-Based Setup Program
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 the command-line interface (CLI) or CMS (from your browser).
•
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
The software documents are not shipped with the product, but you can access them under the appropriate Cisco 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 Catalyst 2940 switches:
•
Catalyst 2940 Switch Software Configuration Guide (order number DOC-7815507=)
•
Catalyst 2940 Switch Command Reference (order number DOC-7815505=)
•
Catalyst 2940 Switch System Message Guide (order number DOC-7815524=)
•
Cluster Management Suite (CMS) online help (available only from the switch CMS software)
•
Catalyst 2940 Switch Hardware Installation Guide (order number DOC-7815435=)
These publications provide more information about the Catalyst 2950 and Catalyst 2955 switches:
•
Catalyst 2950 Desktop Switch Hardware Installation Guide (order number DOC-7811157=)
•
Catalyst 2955 Hardware Installation Guide (order number DOC-7814944=)
•
Catalyst 2950 and Catalyst 2955 Desktop Switch Software Configuration Guide (order number DOC-7811380=)
•
Catalyst 2950 and Catalyst 2955 Desktop Switch Command Reference (order number DOC-7811381=)
•
Catalyst 2950 and Catalyst 2955 Desktop Switch System Message Guide (order number DOC-7814233=)
For information about the Catalyst 2950 LRE switches running software releases earlier than Release 12.1(19)EA1, refer to these documents:
•
Catalyst 2950 Desktop Switch Software Configuration Guide (order number DOC-7814982=)
•
Catalyst 2950 Desktop Switch Command Reference (order number DOC-7814984=)
•
Catalyst 2950 Desktop Switch System Message Guide (order number DOC-7814981=)
•
Release Notes for the Catalyst 2950 LRE Switch (not orderable but available on Cisco.com)
For other information about related products, refer to these documents:
•
1000BASE-T Gigabit Interface Converter Installation Notes (not orderable but is available on Cisco.com)
•
Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide (order number DOC-786460=)
•
Cisco LRE CPE Hardware Installation Guide (order number DOC-7811469=)
•
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)
•
Installation Notes for the Catalyst Family Small-Form-Factor Pluggable Modules (order number DOC-7815160=)
•
Installation and Warranty Notes for the Cisco LRE 48 POTS Splitter (order number DOC-7812250=)
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 websites 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 regularly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual or quarterly subscription.
Registered Cisco.com users can order a single Documentation CD-ROM (product number DOC-CONDOCCD=) through the Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/ordering_place_order_ordering_tool_launch.html
All users can order annual or quarterly subscriptions 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
•
Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) 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 send your comments in e-mail to bug-doc@cisco.com.
You can submit comments by using the response card (if present) 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
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, the Cisco Technical Assistance Center (TAC) provides 24-hour, award-winning technical support services, online and over the phone. Cisco.com features the Cisco TAC website as an online starting point for technical assistance.
Cisco TAC Website
The Cisco TAC website (http://www.cisco.com/tac) provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The Cisco TAC website is available 24 hours a day, 365 days a year.
Accessing all the tools on the Cisco TAC website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a login ID or password, register at this URL:
http://tools.cisco.com/RPF/register/register.do
Opening a TAC Case
The online TAC Case Open Tool (http://www.cisco.com/tac/caseopen) is the fastest way to open P3 and P4 cases. (Your network is minimally impaired or you require product information). After you describe your situation, the TAC Case Open Tool automatically recommends resources for an immediate solution. If your issue is not resolved using these recommendations, your case will be assigned to a Cisco TAC engineer.
For P1 or P2 cases (your production network is down or severely degraded) or if you do not have Internet access, contact Cisco TAC by telephone. Cisco TAC engineers are assigned immediately to P1 and P2 cases to help keep your business operations running smoothly.
To open a case by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete listing of Cisco TAC contacts, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
TAC Case Priority Definitions
To ensure that all cases are reported in a standard format, Cisco has established case priority definitions.
Priority 1 (P1)—Your network is "down" or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Priority 2 (P2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Priority 3 (P3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Priority 4 (P4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
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 quarterly publication that provides the latest networking trends, technology breakthroughs, and Cisco products and solutions to help industry professionals get the most from their networking investment. Included are networking deployment and troubleshooting tips, configuration examples, customer case studies, tutorials and training, certification information, and links to numerous in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/go/packet
•
iQ Magazine is the Cisco bimonthly publication that delivers the latest information about Internet business strategies for executives. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•
Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating 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. Current offerings in network training are listed at this URL:
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documentation listed in the "Related Documentation" section.
This product includes code licensed from RSA Security, Inc. Some portions licensed from IBM are available at
http://oss.software.ibm.com/icu4j/
Copyright ©2001-2003 Cisco Systems Inc. All rights reserved


















































