Table Of Contents
Release Notes for the
Catalyst 3550 Multilayer Switch
Cisco IOS Release 12.1(8)EA1b
Contents
System Requirements
Hardware Supported
Software Compatibility
Recommended Platform Configuration for Web-Based Management
Operating System and Browser Support
Installing the Required Plug-In
Creating Clusters with Different Releases of IOS Software
Downloading Software
Determining the Software Version and Feature Set
Which Files to Use
Upgrading a Switch by Using CMS
Upgrading a Switch by Using the CLI
Recovering from Software Failure
Installation Notes
Setting Up the Catalyst 3550 Initial Configuration
Configuring Browsers and Accessing CMS
Configuring Netscape Communicator (All Versions)
Configuring Microsoft Internet Explorer (4.01)
Configuring Microsoft Internet Explorer (5.0)
Displaying the CMS Access Page
New Features in This Release
New Hardware Features
New Software Features
Limitations and Restrictions
Important Notes
Open Caveats
Open IOS Caveats
Open Cluster Caveats
Open Cluster Management Suite Caveats
Resolved Caveats
Resolved IOS Caveats
Resolved Cluster Caveats
Resolved Cluster Management Suite Caveats
Documentation Updates
Errors
Additions
Korean Regulatory Statement
Adding a VTP Client to a VTP Domain
Related Documentation
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
Release Notes for the
Catalyst 3550 Multilayer Switch
Cisco IOS Release 12.1(8)EA1b
February 11, 2002
Cisco IOS Release 12.1(8)EA1b runs on all Catalyst 3550 multilayer switches.
These release notes include important information about this IOS release and any limitations, restrictions, and caveats that apply to it. Verify that these are the correct release notes for your switch:
•
If you are installing a new switch, refer to the IOS release label on the rear panel of your switch.
•If your switch is on and running, you can use the show version privileged EXEC command. See the "Determining the Software Version and Feature Set" section.
•If you are upgrading to a new release, refer to the software upgrade filename for the IOS version.
For the complete list of Catalyst 3550 switch documentation, see the "Related Documentation" section.
This IOS release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future IOS releases become available, they will be posted to Cisco.com (previously Cisco Connection Online [CCO]) in the Cisco IOS software area.
Contents
This document has these sections:
•"System Requirements" section
•"Downloading Software" section
•"Installation Notes" section
•"New Features in This Release" section
•"Limitations and Restrictions" section
•"Important Notes" section
•"Open Caveats" section
•"Resolved Caveats" section
•"Documentation Updates" section
•"Related Documentation" section
•"Obtaining Documentation" section
•"Obtaining Technical Assistance" section
System Requirements
This section describes these system requirements for this IOS release:
•"Hardware Supported" section
•"Software Compatibility" section
Hardware Supported
Table 1 lists the hardware supported by this IOS release.
Table 1 Supported Hardware
Switch
|
Description
|
Catalyst 3550-12T
|
10 Gigabit Ethernet 10/100/1000BASE-T ports and 2 Gigabit Interface Converter (GBIC)-based Gigabit Ethernet slots
|
Catalyst 3550-12G
|
10 GBIC-based Gigabit Ethernet slots and 2 10/100/1000BASE-T ports
|
Catalyst 3550-24
|
24 autosensing 10/100 Ethernet ports and 2 GBIC-based Gigabit Ethernet slots
|
Catalyst 3550-48
|
48 autosensing 10/100 Ethernet ports and 2 GBIC-based Gigabit Ethernet slots
|
GBIC modules
|
•1000BASE-SX GBIC
•1000BASE-LX/LH GBIC
•1000BASE-ZX GBIC
•1000BASE-T GBIC
•GigaStack GBIC
|
Redundant power system
|
Cisco RPS 300 Redundant Power System
|
Software Compatibility
This section describes these software compatibility requirements for this IOS release:
•"Recommended Platform Configuration for Web-Based Management" section
•"Operating System and Browser Support" section
•"Installing the Required Plug-In" section
•"Creating Clusters with Different Releases of IOS Software" section
Recommended Platform Configuration for Web-Based Management
Table 2 lists the recommended platforms for Web-based management.
Table 2 Recommended Platform Configuration for Web-Based Management
OS
|
Processor Speed
|
DRAM
|
Number of Colors
|
Resolution
|
Font Size
|
Windows NT 4.01
|
Pentium 300 MHz
|
128 MB
|
65,536
|
1024 x 768
|
Small
|
Solaris 2.5.1
|
SPARC 333 MHz
|
128 MB
|
Most colors for applications
|
—
|
Small (3)
|
The minimum PC requirement is a Pentium processor running at 233 MHz with 64 MB of DRAM. The minimum UNIX workstation requirement is a Sun Ultra 1 running at 143 MHz with 64 MB of DRAM.
For information about supported operating systems, see the next section.
Operating System and Browser Support
You can access the web-based interfaces by using the operating systems and browsers listed in Table 3. The switch checks the browser version when starting a session to ensure that the browser is supported. If the browser is not supported, the switch displays an error message, and the session does not start.
Table 3 Supported Operating Systems and Browsers
Operating System
|
Minimum Service Pack or Patch
|
|
Microsoft Internet Explorer 2
|
Windows 95
|
Service Pack 1
|
4.61, 4.7x
|
4.01a, 5.0, 5.5
|
Windows 98
|
Second Edition
|
4.61, 4.7x
|
4.01a, 5.0, 5.5
|
Windows NT 4.0
|
Service Pack 3 or later
|
4.61, 4.7x
|
4.01a, 5.0, 5.5
|
Windows 2000
|
None
|
4.61, 4.7x
|
4.01a, 5.0, 5.5
|
Solaris 2.5.1 or later
|
Sun-recommended patch cluster for the OS and Motif library patch 103461-24
|
4.61, 4.7x
|
Not supported
|
Note If your browser is Internet Explorer and you receive an error message stating that the page might not display correctly because your security settings prohibit running activeX controls, this might mean that your security settings are set too high. To lower security settings, go to Tools > Internet Options, and select the Security tab. Select the indicated Zone, and move the Security Level for this Zone slider from High to Medium (the default).
Note In Cluster Management displays, Internet Explorer versions 4.01 and 5.0 might not display edge devices that are not connected to the command switch. Other functionality is similar to that of Netscape Communicator.
Installing the Required Plug-In
A Java plug-in is required for the browser to access the Java-based Cluster Management Suite (CMS). Download and install the plug-in before you start CMS. Each platform, Windows and Solaris, supports three plug-in versions. For information on the supported plug-ins, see the "Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Platforms" section and the "Solaris Platforms" section.
You can download the recommended plug-ins from this URL: http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note Uninstall older versions of the Java plug-ins before installing the Java plug-in.
If the Java applet does not initialize after you have installed the plug-in, open the Java Plug-in Control Panel (Start > Programs > Java Plug-in Control Panel), and verify these settings:
In the Proxies tab, verify that Use browser settings is checked and that no proxies are enabled.
Note If you are running an Internet virus checker on Windows 2000 and the plug-in takes a long time to load, you can speed up CMS operation by disabling the virus checker filter option or download option or both.
On McAfee VirusScan, from the Start menu, to disable the VirusScan Internet Filter option, the Download Scan option, or both, select Start > Programs > Network Associates > Virus Scan Console > Configure.
or
From the taskbar, right-click the Virus Shield icon and in the Quick Enable menu, disable the options by deselecting Internet Filter or Download Scan.
Windows 2000, Windows 95, Windows 98, and Windows NT 4.0 Platforms
These Java plug-ins are supported on the Windows platform:
•Java plug-in 1.3.1
•Java plug-in 1.3.0
•Java plug-in 1.2.2_05
You can download these plug-ins from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
Note If you start CMS without having installed the required Java plug-in, the browser automatically detects this. If you are using a supported Internet Explorer browser, it automatically downloads and installs the Java plug-in 1.3.0 (default). If you are using a supported Netscape browser, the browser displays a Cisco.com page that contains the Java plug-in and installation instructions. If you are using Windows 2000, Netscape Communicator might not detect the missing Java plug-in.
Solaris Platforms
These Java plug-ins are supported on the Solaris platform:
Caution To avoid performance and compatibility issues, do not use Java plug-ins later than Java plug-in 1.3.1.
•Java plug-in 1.2.2_07
•Java plug-in 1.3.0
•Java plug-in 1.3.1
You can download these plug-ins and instructions from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/java
To install the Java plug-in, follow the instructions in the README_FIRST.txt file.
Creating Clusters with Different Releases of IOS Software
When a cluster consists of a mixture of other Catalyst switches, we strongly recommend using only the Catalyst 3550 switches as the command and standby command switches. When the command switch is a Catalyst 3550 switch, all standby command switches must also be Catalyst 3550 switches. The Catalyst 3550 switch that has the latest software should be the command switch. If the command switch is a Catalyst 3550 Gigabit Ethernet switch and the standby command switch is a Catalyst 3550 Fast Ethernet switch, command switch port speeds are reduced if the standby command switch takes over.
If your cluster has Catalyst 2950, Catalyst 2900 XL, and Catalyst 3500 XL switches, the Catalyst 2950 switch (with the latest software release) should be the command switch. The Catalyst 2950 switch that has the latest software should be the command switch.
If your switch cluster has Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, and Catalyst 3500 XL switches, either the Catalyst 2900 XL or Catalyst 3500 XL (whichever has the latest software release) should be the command switch.
Table 4 lists the cluster capabilities and software versions for the switches.
Table 4 Switch Software and Cluster Capability
Switch
|
IOS Release
|
Cluster Capability
|
Catalyst 3550
|
Release 12.1(4)EA1 or later
|
Member or command switch
|
Catalyst 3500 XL
|
Release 12.0(5.1)XU or later
|
Member or command switch
|
Catalyst 2950
|
Release 12.0(5.2)WC(1) or later
|
Member or command switch
|
Catalyst 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 only
|
Catalyst 1900 and 2820
|
Release 9.00(-A or -EN) or later
|
Member switch only
|
Some versions of the Catalyst 2900 XL software do not support clustering and if you have a cluster with switches that are running different versions of IOS software, software features added on the latest release might not be reflected on switches running the older versions. For example, if you start Visual Switch Manager (VSM) on a Catalyst 2900 XL switch running Release 11.2(8)SA6, the windows and functionality can be different from a switch running Release 12.0(5)WC(1) or later.
Note The CMS is not forward-compatible, which means that if a member switch is running a software version that is newer than the release running on the command switch, the new features are not available on the member switch. If your member switch is a new device that is running a software release that is later than software release on the command switch or a new switch model released after the software release running on the command switch, the member switch is displayed as an unknown device in the Front Panel view. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to perform configuration and obtain reports for that member.
Downloading Software
This section describes these procedures for downloading software:
•"Determining the Software Version and Feature Set" section
•"Which Files to Use" section
•"Upgrading a Switch by Using CMS" section
•"Upgrading a Switch by Using the CLI" section
Note Before downloading software, read this section for important information.
Determining the Software Version and Feature Set
The IOS image is stored as a .bin file in a directory that is named with the IOS release. A subdirectory contains the HTML files needed for web management. The image is stored on the system board Flash device (flash:).
You can use the show version privileged 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. It shows the directory name in Flash memory where the image is stored. A couple of lines below the image name, you see Running Layer 2/3 Switching Image if you are running the enhanced multilayer software image, or Running Layer 2 Switching Image Only if you are running the standard multilayer software image.
Note Although the show version output always shows the software image running on the switch (Layer 2 or Layer 2/3), the model name shown at the end of this display is the factory configuration (SMI or EMI) and does not change if you upgrade the software image.
You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in Flash memory.
Which Files to Use
The upgrade procedures in these release notes describe how to perform the upgrade by using a combined .tar file. This file contains both the IOS image file and the HTML files (needed for the CMS). You must use the combined .tar file to upgrade the switch through the CMS.
The .tar file is an archive file from which you can extract files by using the tar command. You also use the .tar file to upgrade the system by using the archive download-sw privileged EXEC command.
Table 5 lists the software file names for this IOS release.
Table 5 Cisco IOS Software Files for Catalyst 3550 Switches
Filename
|
Description
|
c3550-i9q3l2-mz.121-0.210.EA1b.tar
|
IOS image file and HTML files
This image, the standard multilayer software image (SMI), has Layer 2+ features only.
|
c3550-i5q3l2-mz.121-0.210.EA1b.tar
|
IOS image file and HTML files
This image, the enhanced multilayer software image (EMI), has both Layer 2 and Layer 3 features.
|
Note All Catalyst 3550 Gigabit Ethernet switches ship with the enhanced multilayer software image (EMI) installed. This image is an orderable upgrade for Catalyst 3550 Fast Ethernet switches with the standard multilayer software image (SMI) pre-installed.
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
This procedure is for copying the combined .tar file to the Catalyst 3550 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.
To download software, and if necessary, the TFTP server application, follow these steps:
Step 1 Use Table 5 to identify the file that you want to download.
Step 2 Download the software image file.
If you have a SmartNet support contract, go to this URL and log in to download the appropriate files:
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
If you do not have a SmartNet contract, go to this URL and follow the instructions to register on Cisco.com and download the appropriate files:
http://www.cisco.com/public/sw-center/sw-lan.shtml
Step 3 Download the Cisco TFTP server from the URL link from Step 2, if necessary. The information on this page describes how to download and configure the TFTP server.
Step 4 Copy the image to the appropriate TFTP directory on the workstation, and make sure the TFTP server is properly configured.
For more information, refer to Appendix B in the Catalyst 3550 Multilayer Switch Software Configuration Guide.
Step 5 Log in to the switch through the console port or a Telnet session.
Step 6 Check your VLAN 1 configuration by using the show interfaces vlan 1 privileged EXEC command, and verify that VLAN 1 is part of the same network as the TFTP server. (Check the Internet address is line near the top of the display.)
Step 7 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.tar
The /overwrite option overwrites the software image in Flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not been 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 172.20.129.10 and to overwrite the image on the switch:
Switch# archive download-sw /overwrite tftp://172.20.129.10/c3550-i5q3l2-mz.121-8.EA1b.tar
Note You 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.
Recovering from Software Failure
In the software fails, you can reload the software. For detailed recovery procedures, refer to the "Troubleshooting" chapter in the Catalyst 3550 Multilayer Switch Software Configuration Guide.
Installation Notes
You can assign IP information to your switch by using the setup program, the Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration (refer to the Catalyst 3550 Multilayer Switch Software Configuration Guide), or by manually assigning an IP address (refer to the Catalyst 3550 Multilayer Switch Software Configuration Guide).
This section describes these installation procedures:
•"Setting Up the Catalyst 3550 Initial Configuration" section
•"Configuring Browsers and Accessing CMS" section
Setting Up the Catalyst 3550 Initial Configuration
The first time that you access the switch, it runs a setup program that prompts you for an IP address and other configuration information necessary for the switch to communicate with the local routers and the Internet. This information is also required if you plan to use the CMS to configure and manage the switch.
Note If the switch will be a cluster member managed through the IP address of the command switch, it is not necessary to assign IP information or a password. If you are configuring the switch as a standalone switch or as a command switch, you must assign IP information.
Follow these steps to create an initial configuration for the switch:
Step 1 Enter Yes at the first two prompts.
Would you like to enter the initial configuration dialog? [yes/no]: yes
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Basic management setup configures only enough connectivity
for management of the system, extended setup will ask you
to configure each interface on the system.
Would you like to enter basic management setup? [yes/no]: yes
Step 2 Enter a host name for the switch, and press Return.
On a command switch, the host name is limited to 28 characters; on a member switch to 31 characters. Do not use -n, where n is a number, as the last character in a host name for any switch.
Enter host name [Switch]: host_name
Step 3 Enter a secret password, and press Return.
The password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, allows spaces, but ignores leading spaces.
Enter enable secret: secret_password
Step 4 Enter an enable password, and press Return.
Enter enable password: enable_password
Step 5 Enter a virtual terminal (Telnet) password, and press Return.
The password can be from 1 to 25 alphanumeric characters, is case sensitive, allows spaces, but ignores leading spaces.
Enter virtual terminal password: terminal-password
Step 6 (Optional) Configure Simple Network Management Protocol (SNMP) by responding to the prompts.
Step 7 Enter the interface name (physical interface or VLAN name) of the interface that connects to the management network, and press Return. For this release, always use vlan 1 as that interface.
Enter interface name used to connect to the
management network from the above interface summary: vlan 1
Step 8 Configure the interface by entering the switch IP address and subnet mask and pressing Return:
Configuring interface vlan 1:
Configure IP on this interface? [yes]: yes
IP address for this interface: 10.4.120.106
Subnet mask for this interface [255.0.0.0]: 255.255.255.0
Step 9 Enter Y to configure the switch as the cluster command switch. Enter N to configure it as a member switch or as a standalone switch.
If you enter N, the switch appears as a candidate switch in the CMS. In this case, the message in Step 10 is not displayed.
Would you like to enable as a cluster command switch? [yes/no]: yes
Step 10 Assign a name to the cluster, and press Return.
Enter cluster name: cluster_name
The cluster name can be 1 to 31 alphanumeric characters, dashes, or underscores.
The initial configuration appears:
The following configuration command script was created:
enable secret 5 $1$LiBw$0Xc1wyT.PXPkuhFwqyhVi0
enable password enable-password
password terminal-password
snmp-server community public
ip address 10.4.120.106 255.255.255.0
interface GigabitEthernet0/1
interface GigabitEthernet0/2
interface GigabitEthernet0/12
cluster enable cluster-name
Step 11 These choices are displayed:
[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]:2
Make your selection, and press Return.
After you complete the setup program, the switch can run the created default configuration. If you want to change this configuration or want to perform other management tasks, use one of these tools:
•Command-line interface (CLI)
•Cluster Management Suite from your browser
Configuring Browsers and Accessing CMS
For the browser to use CMS, a Java plug-in is required, as described in the "Installing the Required Plug-In" section. After you have assigned an IP address to the switch and installed the plug-in, you can access the switch from your browser and use the CMS to configure other switches. To use the web-based tools, see the "Software Compatibility" section to set up the appropriate browser options.
This section describes these installation procedures:
•"Configuring Netscape Communicator (All Versions)" section
•"Configuring Microsoft Internet Explorer (4.01)" section
•"Configuring Microsoft Internet Explorer (5.0)" section
•"Displaying the CMS Access Page" section
Configuring Netscape Communicator (All Versions)
Follow these steps to configure Netscape Communicator:
Step 1 Start Netscape Communicator.
Step 2 From the menu bar, select Edit > Preferences.
Step 3 In the Preferences window, click Advanced.
Step 4 Check the Enable Java, Enable JavaScript, and Enable Style Sheets check boxes.
Step 5 From the menu bar, select Edit > Preferences.
Step 6 In the Preferences window, click Advanced Cache, and select Every time.
Step 7 Click OK to return to the browser Home page.
Configuring Microsoft Internet Explorer (4.01)
Follow these steps to configure Microsoft Internet Explorer 4.01:
Step 1 Start Internet Explorer.
Step 2 From the menu bar, select View > Internet Options.
Step 3 In the Internet Options window, click the Advanced tab.
a. Scroll through the list of options until you see Java VM. Check the Java logging enabled and Java JIT compiler enabled check boxes.
b. Click Apply.
Step 4 In the Internet Options window, click the General tab.
a. In the Temporary Internet Files section, click Settings.
b. In the Settings window, select Every visit to the page, and click OK.
Configuring Microsoft Internet Explorer (5.0)
Note During the installation of this browser, make sure to check the Install Minimal or Customize Your Browser check box. In the Component Options window in the Internet Explorer 5 section, make sure to check the Microsoft Virtual Machine check box to display applets written in Java.
Follow these steps to configure Microsoft Internet Explorer 5.0:
Step 1 Start Internet Explorer.
Step 2 From the menu bar, select Tools > Internet Options.
Step 3 In the Internet Options window, click the Advanced tab.
a. Scroll through the list of options until you see Java VM. Check the Java logging enabled and JIT compiler for virtual machine enabled check boxes.
b. Click Apply.
Step 4 In the Internet Options window, click the General tab.
a. In the Temporary Internet Files section, click Settings.
b. In the Settings window, select Every visit to the page, and click OK.
If you are using Microsoft Internet Explorer 5.0 to make configuration changes to the switch, note that this browser does not automatically reflect the latest configuration changes. Make sure that you click Refresh for every configuration change.
Displaying the CMS Access Page
After the browser is configured, display the CMS access page:
Step 1 Enter the switch IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer), and press Return.
Step 2 Enter your username and password when prompted. The password provides level 15 access. The Cisco Systems Access page appears. For more information on setting passwords and privilege levels, refer to the Catalyst 3550 Multilayer Switch Software Configuration Guide.
Step 3 Click Web Console to launch the CMS applet.
If you access CMS from a standalone or a cluster-member switch, Device Manager appears.
New Features in This Release
This section describes the new supported hardware and the new software features for the Catalyst 3550 switches that are provided in this release.
•"New Hardware Features" section
•"New Software Features" section
New Hardware Features
For a list of supported hardware, see the "Hardware Supported" section.
New Software Features
This software release contains these new features or enhancements:
•802.1X port-based authentication—prevents unauthorized devices (clients) from connecting to a LAN through publicly accessible ports. The authentication server authenticates each client connected to a switch port before making available any services offered by the switch or the LAN.
•Remote Authentication Dial-In User Service (RADIUS)—a distributed client/server system that secures networks against unauthorized access. RADIUS clients run on supported Cisco routers and switches (including Catalyst 3550 multilayer switches and Catalyst 2950 series switches) and send authentication requests to a central RADIUS server, which contains all user authentication and network service access information.
•MAC address notification traps—tracks users on a network by storing the MAC address activity on the switch. Whenever the switch learns or removes a MAC address, an SNMP notification can be generated and sent to the NMS. If you have many users coming and going from the network, you can set a trap interval time to bundle the notification traps and reduce network traffic.
•Port security—restricts input to an interface by limiting and identifying MAC addresses of the stations allowed to access the port. When you assign secure MAC addresses to a secure port, the port does not forward packets with source addresses outside the group of defined addresses. If you limit the number of secure MAC addresses to one and assign a single secure MAC address, the workstation attached to that port is assured the full bandwidth of the port.
•IGMP filtering—controls the set of multicast groups to which a switch port can belong by defining IP multicast profiles and associating them with individual switch ports. An IGMP profile can contain one or more multicast groups and specifies whether access to the group is permitted or denied. If an IGMP profile denying access to a multicast group is applied to a switch port, the IGMP join report requesting the stream of IP multicast traffic is dropped, and the port is not allowed to receive IP multicast traffic from that group.
•CMS software enhancements:
–Access modes—provide two levels of access to the configuration options: read-write and read-only. Read-write access requires privilege level 15. Read-only access requires privilege levels from 1 to 14. Privilege level 0 denies access to CMS.
–New and enhanced wizards:
Security wizard—filters certain traffic, such as HTTP traffic, to certain users or devices.
Priority data wizard—provides a higher priority to specific applications.
Enhanced Video wizard—optimizes multiple video servers for transmitting video traffic.
–System Messages—displays the most recent system messages (IOS messages and switch-specific messages) sent by the switch software.
–Front Panel view enhancements:
You can press the left mouse button and drag your mouse across ports that you want to select, or hold down the Ctrl and Shift keys for selecting. You can highlight ports and determine their VLAN membership modes. The cluster tree can display icons for Layer 2, Layer 3, and Long-Reach Ethernet (LRE) standby-command switches.
–Topology view enhancements:
You can press the left mouse button and drag your mouse across devices and links that you want to select. You have more options for controlling the type of information displayed in the Topology view. When you drag your mouse over a yellow or red device icon, a tool tip displays a status message. This view displays device icons for connected Cisco LRE customer premises equipment (CPE) devices, Cisco access points, Cisco IP phones, Cisco Discovery Protocol (CDP)-capable hubs, and routers. This view displays link icons for routed and LRE links.
–Dialog enhancements:
When you drag your mouse over a table heading, a tool tip displays the complete heading. On some table columns, you can sort information in ascending or descending order. Editable table cells are shown with a pencil icon. Links to the Internet are shown with a globe icon.
–Online help links—display configuration windows, related help topics, and related information from Cisco.com.
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.
•Before adding a VTP client to a VTP domain, always verify that its VTP configuration revision number is lower than the configuration revision number of the other switches in the VTP domain. If necessary, reset the switch configuration revision number to 0. See the "Adding a VTP Client to a VTP Domain" section for the procedure.
Caution Switches in a VTP domain always use the VLAN configuration of the switch with the highest VTP configuration revision number. If you add a switch that has a revision number higher than the revision number in the VTP domain, it can erase all VLAN information from the VTP server and VTP domain.
•Storm control or traffic suppression (configured by using the storm-control {broadcast | multicast | unicast} level level [.level] interface configuration command) is supported only on physical interfaces; it is not supported on EtherChannel port channels even though you can enter these commands through the CLI.
•The Cisco RPS 300 Redundant Power System supports the Catalyst 3550 multilayer switch and provides redundancy for up to six connected devices until one of these devices requires backup power. If a connected device has a power failure, the RPS immediately begins supplying power to that device and sends status information to other connected devices that it is no longer available as a backup power source. As described in the device documentation, when the RPS LED is amber, the RPS is connected but down. However, this might merely mean that the RPS is in standby mode. Press the Standby/Active button on the RPS to put it into active mode. You can view RPS status through the CLI by using the show rps privileged EXEC command. For more information, refer to the RPS 300 Hardware Installation Guide.
•You can connect the switch to a PC by using the switch console port and the supplied rollover cable and the DB-9 adapter. You need to provide a RJ-45-to-DB-25 female DTE adapter if you want to connect the switch console port to a terminal. You can order a kit (part number ACS-DSBUASYN=) with this RJ-45-to-DB-25 female DTE adapter from Cisco.
•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 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.
•Modifying a multicast boundary access list does not prevent packets from being forwarded by any multicast routes that were in existence before the access list was modified if the packets arriving on the input interface do not violate the boundary. However, no new multicast routes that violate the updated version of the multicast boundary access list are learned, and any multicast routes that are in violation of the updated access list are not relearned if they age out.
After updating a multicast boundary, the workaround is to use the clear ip mroute privileged EXEC command to delete any existing multicast routes that violate the updated boundary. (CSCdr79083)
•When an IP packet with a cyclic redundancy check (CRC) error is received, the per-packet per-DSCP counter (for DSCP 0) is incremented. Normal networks should not have packets with CRC errors. (CSCdr85898)
•The mac-address interface configuration command does not properly assign a MAC address to an interface. This command is not supported on Catalyst 3550 switches. (CSCds11328)
•When there is a transition from the cluster active command-switch to the standby command-switch, Catalyst 1900, Catalyst 2820, and Catalyst 2900 4-MB switches that are cluster members might lose their cluster configuration. You must manually add these switches back to the cluster.
(CSCds32517, CSCds44529, CSCds55711, CSCds55787, CSCdt70872)
•The show ip mroute count privileged EXEC command might display incorrect packet counts. In certain transient states (for example, when a multicast stream is forwarded only to the CPU during the route-learning process and the CPU is programming this route into the hardware), a multicast stream packet count might be counted twice. Do not trust the counter during this transient state. (CSCds61396)
•When changing the link speed of a Gigabit Ethernet port from 1000 Mbps to 100 Mbps, there is a slight chance that the port will stop transmitting packets. If this occurs, shut down the port, and re-enable it by using the shutdown and no shutdown interface configuration commands. (CSCds84279)
•In IP multicast routing and fallback bridging, certain hardware features are used to replicate packets for the different VLANs of an outgoing trunk port. If the incoming speed is line rate, the outgoing interface cannot duplicate that speed (because of the replication of the packets). As a result, certain replicated packets are dropped. (CSCdt06418)
•When a Catalyst 2900 XL or Catalyst 3500 XL cluster command-switch is connected to a Catalyst 3550 switch, the command switch does not find any cluster candidates beyond the Catalyst 3550 switch if it is not a member of the cluster. You must add the Catalyst 3550 switch to the cluster. You can then see any cluster candidates connected to it. (CSCdt09918)
•When you use the no interface port-channel global configuration command to remove an EtherChannel group, the ports in the port group change to the administratively down state.
When you remove an EtherChannel group, enter the no shutdown interface configuration command on the interfaces that belonged to the port group to bring them back on line. (CSCdt10825)
•In the output displayed after a show interface interface-id privileged EXEC command, the output buffer failures field shows the number of packets lost before replication, whereas the packets output field shows the successful transmitted packets after replication. To determine actual discarded frames, multiply the output buffer failures by the number of VLANs on which the multicast data is replicated. (CSCdt26928)
•Internet Group Management Protocol (IGMP) packets classified by quality of service (QoS) to map the Differentiated Service Code Point (DSCP) value and the class of service (CoS) value in a QoS policy map might only modify the DSCP property and leave the CoS value at zero. (CSCdt27705)
•If you assign both tail-drop threshold percentages to 100 percent by using the wrr-queue threshold interface configuration command and display QoS information for this interface by using the show mls qos interface statistics privileged command, the drop-count statistics are always zero even if the thresholds were exceeded. To display the total number of discarded packets, use the show controllers ethernet-controllers interface-id privileged EXEC command. In the display, the number of discarded frames includes the frames that were dropped when the tail-drop thresholds were exceeded. (CSCdt29703)
•Open Shortest Path First (OSPF) path costs and Interior Gateway Routing Protocol (IGRP) metrics are incorrect for switch virtual interface (SVI) ports. You can manually configure the bandwidth of the SVI by using the bandwidth interface configuration command. Changing the bandwidth of the interface changes the routing metric for the routes when the SVI is used as an outgoing interface. (CSCdt29806)
•On the Catalyst 3550, coldStart and warmStart traps are not consistently sent. (CSCdt33779)
•Remote Monitoring (RMON) collection functions on physical interfaces, but it is not supported on EtherChannels and SVIs. (CSCdt36101)
•When clustering is enabled, do not configure SNMP community strings of more than 59 bytes, or clustering SNMP might not work correctly. (CSCdt39616)
•If both the active command-switch and the standby command-switch fail at the same time, the cluster is not automatically recreated. Even if there is a third passive command-switch, it might not recreate all cluster members because it might not have all the latest cluster configuration information. You must manually recreate the cluster if both the active and standby command-switches simultaneously fail. (CSCdt43501)
•Multicast router information is displayed in the show ip igmp snooping mrouter privileged EXEC command when IGMP snooping is disabled. Multicast VLAN Registration (MVR) and IGMP snooping use the same commands to display multicast router information. In this case, MVR is enabled, and IGMP snooping is disabled. (CSCdt48002)
•The configurations for the tunnel keywords and commands related to IP multicasting and the track keyword related to the Hot Standby Router Protocol (HSRP) are not kept properly after rebooting the switch. If these configurations reference routed ports, the configuration is not applied after reboot. (CSCdt48614)
•When a VLAN interface has been disabled and restarted multiple times by using the shutdown and no shutdown interface configuration commands, the interface might not restart following a no shutdown command. To restart the interface, re-enter a shutdown and no shutdown command sequence. (CSCdt54435)
•When you configure the ip pim spt-threshold infinity interface configuration command, you want all sources for the specified group to use the shared tree and not use the source tree. However, the switch does not automatically start to use the shared tree. No connectivity problem occurs, but the switch continues to use the shortest path tree for multicast group entries already installed in the multicast routing table. You can enter the clear ip mroute * privileged EXEC command to force the change to the shared tree. (CSCdt60412)
•If the number of multicast routes configured on the switch is greater than the switch can support, it might run out of available memory, which can cause it to reboot. This is a limitation in the platform-independent code.
The workaround is to not configure the switch to operate with more than the maximum number of supported multicast routes. You can use the show sdm prefer and show sdm prefer routing privileged EXEC commands to view approximate maximum configuration guidelines for the current SDM template and the routing template. ((CSCdt63354))
•Configuring too many multicast groups might result in an extremely low memory condition and cause the software control data structure to go out of sync, causing unpredictable forwarding behavior. The memory resources can only be recovered by issuing the clear ip mroute privileged EXEC command. To prevent this situation, do not configure more than the recommended multicast routes on the switch. (CSCdt63480)
•The dec keyword is not supported in the bridge bridge-group protocol global configuration command. If two Catalyst 3550 switches are connected to each other through an interface that is configured for IP routing and fallback bridging, and the bridge group is configured with the bridge bridge-group protocol dec command, both switches act as if they were the spanning tree root. Therefore, spanning-tree loops might be undetected. (CSCdt63589)
•When you configure an EtherChannel between a Catalyst 3550 and a Catalyst 1900 switch, some of Catalyst 3550 links in the EtherChannel might go down, but one link in the channel remains up, and connectivity is maintained.
The workaround is to disable the Port Aggregation Protocol (PAgP) on both devices by using the channel-group channel-group-number mode on interface configuration command. PAgP negotiation between these two devices is not reliable. (CSCdt78727)
•The behavior of a software access control list (ACL) with QoS is different from a hardware ACL with QoS. On the Catalyst 3550 switch, when the QoS hardware rewrites the DSCP of a packet, the rewriting of this field happens before software running on the CPU examines the packet, and the CPU sees only the new value and not the original DSCP value.
When the security hardware ACL matches a packet on input, the match uses the original DSCP value. For output security ACLs, the security ACL hardware should match against the final, possibly changed, DSCP value as set by the QoS hardware. Under some circumstances, a match to a security ACL in hardware prevents the QoS hardware from rewriting the DSCP and causes the CPU to use the original DSCP.
If a security ACL is applied in software (because the ACL did not fit into hardware, and packets were sent to the CPU for examination), the match probably uses the new DSCP value as determined by the QoS hardware, regardless of whether the ACL is applied at the input or at the output. When packets are logged by the ACL, this problem can also affect whether or not a match is logged by the CPU even if the ACL fits into hardware and the permit or deny filtering was completed in hardware.
To avoid these issues, whenever the switch rewrites the DSCP of any packet to a value different from the original DSCP, security ACLs should not test against DSCP values in any of their access control elements (ACEs), regardless of whether the ACL is being applied to an IP access group or to a VLAN map. This restriction does not apply to ACLs used in QoS class maps.
If the switch is not configured to rewrite the DSCP value of any packet, it is safe to match against DSCP in ACLs used for IP access groups or for VLAN maps because the DSCP does not change as the packet is processed by the switch.
The DSCP field of an IP packet encompasses the two fields that were originally designated precedence and TOS (type of service). Statements relating to DSCP apply equally to either IP precedence or IP TOS. (CSCdt94355)
•Disabling autonegotiation on a GBIC interface by using the speed nonegotiate interface configuration command might cause the interface to show that the physical link is up, even when it is not connected. (CSCdv29722)
•On earlier versions of Catalyst 3550-24 switches, if a 10/100BASE-TX port on the switch is connected to a Catalyst 2820 or Catalyst 1900 switch through an ISL trunk at 100 Mbps, bidirectional communication cannot be established. The Catalyst 2820 or Catalyst 1900 switch identifies the Catalyst 3550-24 switch as a CDP neighbor, but the Catalyst 3550-24 switch does not recognize the Catalyst 2820 or Catalyst 1900 switch. On these switches, you should not use ISL trunks between the Catalyst 3550-24 and a Catalyst 2820 or Catalyst 1900 switch. Configure the link as an access link instead of a trunk link.
This problem has been fixed in hardware on Catalyst 3550-24 switches with motherboard assembly number 73-5700-08 or later. To determine the board level on your switch, enter the show version privileged EXEC. Motherboard information appears toward the end of the output display. (CSCdv68158)
•When IGMP filtering is enabled and you use the ip igmp profile global configuration command to create an IGMP filter, reserved multicast addresses cannot be filtered. Because IGMP filtering uses only Layer 3 addresses to filter IGMP reports and due to mapping between Layer 3 multicast addresses and Ethernet multicast addresses, reserved groups (224.0.0.x) are always allowed through the switch. In addition, aliased groups can leak through the switch. For example, if a user is allowed to receive reports from group 225.1.2.3, but not from group 230.1.2.3, aliasing will cause the user to receive reports from 230.1.2.3. Aliasing of reserved addresses means that all groups of the form y.0.0.x are allowed through. (CSCdv73626)
If you use the ip igmp max-groups interface configuration command to set the maximum number of IGMP groups for an interface to 0, the port still receives group reports from reserved multicast groups (224.0.0.x) and their Layer 2 aliases (y.0.0.x). (CSCdv79832)
Important Notes
This section describes important information related to this IOS release.
•Beginning with IOS release 12.1(8)EA1, to configure traffic suppression (previously configured by using the switchport broadcast, switchport multicast, and switchport unicast interface configuration commands), you use the storm-control {broadcast | multicast | unicast} level level [.level] interface configuration commands. For more information about these commands, refer to the Catalyst 3550 Multilayer Switch Command Reference.
•When you are configuring a cascaded stack of Catalyst 3550 switches by using the GigaStack GBIC and want to include more than one VLAN in the stack, be sure to configure all the GigaStack GBIC interfaces as trunk ports by using the switchport mode trunk interface configuration command and to use the same encapsulation method by using the switchport encapsulation {isl | dot1q} interface configuration command. For more information about these commands, refer to the Catalyst 3550 Multilayer Switch Command Reference.
•If the 1000BASE-T GBIC (WS-G5482) is not securely inserted, the switch might fail to recognize it or might display an incorrect media type following a show interface privileged EXEC command entry. If this happens, remove and reinsert the GBIC.
•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.
•CMS does not display QoS classes that are created through the CLI if these classes have multiple match statements. When using CMS, you cannot create classes that match more than one match statement. CMS does not display policies that have such classes.
•If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.add.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch CMS.
•Within an ACL, you can change the sequence of ACEs that have the host keyword. However, because such ACEs are independent of each other, the change has no effect on the way the ACL filters traffic.
•If you use the Netscape browser to view the CMS GUI and you resize the browser window while CMS is initializing, CMS does not resize to fit the window.
Resize the browser window again when CMS is not busy.
•CMS does not start if the temporary directory on your computer runs out of memory. This problem can occur because of a bug in the 1.2.2 version of the Java plug-in. The plug-in creates temporary files in the directory whenever it runs CMS, and the directory eventually runs out of plug-in space.
The workaround is to remove all the jar_cache*.tmp files from the temporary directory. The path to the directory is different for different operating systems:
Solaris: /var/tmp
Windows NT and Windows 2000: \TEMP
Windows 95 and 98: \Windows\Temp
Open Caveats
This section describes these open caveats with possible unexpected activity in this IOS release:
•"Open IOS Caveats" section
•"Open Cluster Caveats" section
•"Open Cluster Management Suite Caveats" section
Open IOS Caveats
This section describes the severity 3 IOS configuration caveats:
•CSCds55220
If you configure the DHCP server to allocate addresses from a pool to the switch, two devices on the network might have the same IP address. Pooled addresses are temporarily allocated to a device and are returned to the pool when not in use. If you save the configuration file after the switch receives such an address, the pooled address is saved, and the switch does not attempt to access the DHCP server after a reboot to receive a new IP address. As a result, two devices might have the same IP address.
The workaround is to make sure that you configure the DHCP server with reserved leases that are bound to each switch by the switch hardware address.
•CSCdt51254
If you try to configure an ACL that uses the log keyword, an error is displayed, and a match none statement is added to the show class-map class-map-name display. Not only does the match none statement make the ACL useless, but any previously entered match commands for the same class map are not retained.
The workaround is to re-enter the old ACL without the log keyword.
•CSCdt79172
When the switch is operating with equal-cost routes and it is required to learn more unicast routes than it can support, the CPU might run out of memory, and the switch might fail.
The workaround is to remain within the documented recommended and supported limits.
•CSCdu87797
If Catalyst 3550 GBIC ports containing GigaStack GBICs are configured as routed ports with EtherChannel group assignments, they might not correctly join the channel group.
GigaStack GBICs are not supported as EtherChannel group members on the Catalyst 3550 switch. The workaround is to not configure channel-group settings on interfaces containing GigaStack GBICs.
•CSCdv10257
You cannot set the vmVlanType object in CISCO-VLAN-MEMBERSHIP-MIB, which means that you cannot convert a port from static to dynamic access using SNMP.
The workaround is to use the switchport access vlan dynamic interface configuration command to to change an access port from static to dynamic.
•CSCdv10276
The switch does not generate the vmVmpsChange trap in CISCO-VLAN-MEMBERSHIP-MIB, so there is no way to monitor VMPS change event by using SNMP.
There is no workaround.
•CSCdv15832
If a routed interface is configured with a multicast boundary by using the ip multicast boundary interface configuration command, and there are ACLs configured, if the ACLs are modified or the multicast boundary is removed, this might not affect the existing multicast routes.
The workaround is to delete the multicast routing table by using the clear ip mroute * privileged EXEC command.
•CSCdv46715
If you configure a trunk port for Dynamic Trunking Protocol (DTP) nonegotiate mode and change the encapsulation type from ISL to 802.1Q by using the switchport trunk encapsulation interface configuration command, the port becomes an access port and is no longer trunking.
There is no workaround.
•CSCdv47319
The switch might fail while deleting 7000 multicast routes with the maximum number of SVIs supported by the SDM access template.
There is no workaround.
•CSCdv59364
If you use the setup program for initial configuration and set an IP address for a specific port (making it a router port and not a switch port), the setup program does not write the no switchport interface configuration command to the configuration file, making the port unusable without manual reconfiguration.
The workaround is to not use the setup program for configuring routed ports. Always enter no when prompted with the Configure IP on this interface? message.
•CSCdv66568
After you change connections between GigaStack ports, the link might not be established, and LEDs on the GigaStack GBIC might continue to blink for more than 2 minutes. (It is normal for the LEDs to blink for a short time.)
The workaround is to disconnect and reconnect one of the links connected to the GigaStack GBIC with the continuous blinking LEDs.
•CSCdv70296
If a port is put into self-looped state, Spanning Tree Protocol (STP) remains in the blocking state after the self-looped condition is removed.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown interface configuration command on the port in the blocking state.
•CSCdv79737
If a stack contains both Catalyst 3550 switches and Catalyst 3500 XL or Catalyst 2900 XL switches, cross-stack UplinkFast does not function if the management VLAN on the Catalyst 3500 XL or Catalyst 2900 XL switches is changed to other than VLAN 1 (the default).
The workaround is to make sure that the management VLAN of all Catalyst 3500 XL or 2900 XL switches in the stack is set to VLAN 1.
•CSCdw07801
After you have changed the system maximum transmission unit (MTU) size by using the system mtu global configuration command, the new MTU value is applied to all interfaces on the switch. However, the show interfaces privileged EXEC command still displays the default MTU size (1500 bytes), which could mislead you about the maximum MTU size on the interface.
The workaround is to use the show system mtu privileged EXEC command to verify the setting of the system MTU.
•CSCdw17713
When you configure a switch port to block flooded traffic by using the switchport block interface configuration command, and then configure the port as a SPAN destination port by using the monitor session session_number destination interface interface_id global configuration command, the block settings might remain enabled during the SPAN session, causing traffic sent to unknown addresses to be blocked instead of forwarded to the destination port.
The workaround is to disable any switchport block settings on the port by using the no switchport block interface command before using the monitor session command to configure the port as a destination port.
•CSCdw27053
When y
