Guest

Cisco Catalyst 3550 Series Switches

Release Notes for the Catalyst 3550 Multilayer Switch, Cisco IOS Release 12.1(22)EA1a

  • Viewing Options

  • PDF (668.0 KB)
  • Feedback
Release Notes for the Catalyst 3550 Multilayer Switch Cisco IOS Release 12.1(22)EA1a

Table Of Contents

Release Notes for the
Catalyst 3550 Multilayer Switch
Cisco IOS Release 12.1(22)EA1a

Contents

System Requirements

Hardware Supported

Software Compatibility

Windows

Solaris

Cluster Compatibility

Downloading Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Upgrading a Switch by Using CMS

Upgrading a Switch by Using the CLI

Upgrading with a Nondefault System MTU Setting

Recovering from Software Failure

Installation Notes

New Features

New Hardware Features

New Software Features

Limitations and Restrictions

Cisco IOS Limitations and Restrictions

Cluster Limitations and Restrictions

CMS Limitations and Restrictions

Important Notes

Cisco IOS Notes

Cluster Notes

CMS Notes

Open Caveats

Open Cisco IOS Caveats

Open CMS Caveats

Resolved Caveats

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1a

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(20)EA2

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

CMS Caveats Resolved in Cisco IOS Release 12.1(20)EA2

Documentation Updates

Changes to the Catalyst 3550 Multilayer Switch Software Configuration Guide

Configuring Storm Control

Troubleshooting Power over Ethernet Switch Ports

Changes to the Catalyst 3550 Multilayer Switch Command Reference

duplex

power inline

show interfaces

show storm-control

speed

storm-control

Corrections to the Catalyst 3550 Multilayer Switch Software Configuration Guide

Chapter 3, Getting Started with CMS

Chapter 29, Configuring QoS

Changes to the Catalyst 3550 Multilayer Switch System Message Guide

Related Documentation

Obtaining Documentation

Cisco.com

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for the
Catalyst 3550 Multilayer Switch
Cisco IOS Release 12.1(22)EA1a


Revised April 2005

Cisco IOS Release 12.1(22)EA1a runs on all Catalyst 3550 multilayer switches.

These release notes include important information about this Cisco 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 Cisco IOS release label on the rear panel of your switch.

If your switch is on, use the show version privileged EXEC command. See the "Finding 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. See the "Deciding Which Files to Use" section.

For the complete list of Catalyst 3550 switch documentation, see the "Related Documentation" section.

You can download the switch software from these sites:

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

Contents

This information is in the release notes:

"System Requirements" section

"Downloading Software" section

"Installation Notes" section

"New Features" section

"Limitations and Restrictions" section

"Important Notes" section

"Open Caveats" section

"Resolved Caveats" section

"Documentation Updates" section

"Related Documentation" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

System Requirements

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

"Hardware Supported" section

"Software Compatibility" section

"Cluster Compatibility" section

Hardware Supported

Table 1 lists the hardware supported by this Cisco IOS release.

Table 1 Supported Hardware 

Switch
Description

Catalyst 3550-12G

10 GBIC-based Gigabit Ethernet slots and 2 Gigabit Ethernet 10/100/1000BASE-T ports

Catalyst 3550-12T

10 Gigabit Ethernet 10/100/1000BASE-T ports and 2 GBIC1 -based Gigabit Ethernet slots

Catalyst 3550-24

24 autosensing 10/100 Ethernet ports and 2 GBIC-based Gigabit Ethernet slots

Catalyst 3550-24-DC

24 autosensing 10/100 Ethernet ports, 2 GBIC-based Gigabit Ethernet slots, and an on-board DC power converter

Catalyst 3550-24-FX

24 100BASE-FX ports and 2 GBIC-based Gigabit Ethernet slots

Catalyst 3550-24PWR

24 autosensing 10/100 Ethernet ports, 2 GBIC-based Gigabit Ethernet slots, ability to provide power for Cisco IP Phones and Cisco Aironet Access Points from all 10/100 Ethernet ports, auto-detection and control of inline power on a per-port basis on all 10/100 ports

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

CWDM2 fiber-optic GBIC

DWDM3 fiber-optic GBIC

Redundant power system

Cisco RPS 300 Redundant Power System4

Cisco RPS 675 Redundant Power System5

1 GBIC = Gigabit Interface Converter

2 CWDM = coarse wavelength-division multiplexing

3 DWDM = dense wavelength-division multiplexing

4 The Cisco RPS 300 does not support the Catalyst 3550-24-DC or 3550-24PWR switch.

5 The Cisco RPS 675 does not support the Catalyst 3550-24-DC switch.


Software Compatibility

For information about the recommended platforms for web-based management, operating systems and browser support, the CMS plug-in guidelines, 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) to run CMS. You can download the latest CMS plug-in for Windows from this URL:

http://www.cisco.com/pcgi-bin/Support/ClusterMgmtSuite/cms_plugin_redirect.cgi?platform=
windows&version=1.1

Solaris

This release uses a CMS plug-in (Solaris only) that replaces the Java plug-in. You must download the CMS plug-in to run CMS. You can download the latest CMS plug-in for Solaris from this URL:

http://www.cisco.com/pcgi-bin/Support/ClusterMgmtSuite/cms_plugin_redirect.cgi?platform=
solaris&version=1.1

Cluster Compatibility

This section describes how to choose command and standby command switches when a cluster consists of a mixture of Catalyst switches. When creating a switch cluster or adding a switch to a cluster, follow these guidelines:

When you create a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch. Table 2 lists the cluster capabilities and Cisco IOS releases for the switches. The switches are listed from highest- to lowest-end switch.

If you are managing the cluster through CMS, the switch that has the latest software should be the command switch, unless your command switch is running Cisco IOS Release 12.1(19)EA1 or later.

The standby command switch must be the same type as the command switch. For example, if the command switch is a Catalyst 3750 switch, all standby command switches must be Catalyst 3750 switches.

Table 2 Switch Software and Cluster Capability 

Switch
Cisco IOS Release
Cluster Capability

Catalyst 3750

12.1(11)AX or later

Member or command switch

Catalyst 3560

12.1(19)EA1b

Member or command switch

Catalyst 3550

12.1(4)EA1 or later

Member or command switch

Catalyst 2970

12.1(11)AX or later

Member or command switch

Catalyst 2955

12.1(12c)EA1 or later

Member or command switch

Catalyst 2950

12.0(5.2)WC(1) or later

Member or command switch

Catalyst 2950 LRE

12.1(11)JY or later

Member or command switch

Catalyst 2940

12.1(13)AY or later

Member or command switch

Catalyst 3500 XL

12.0(5.1)XU or later

Member or command switch

Catalyst 2900 XL (8-MB switches)

12.0(5.1)XU or later

Member or command switch

Catalyst 2900 XL (4-MB switches)

11.2(8.5)SA6 (recommended)

Member switch only1

Catalyst 1900 and 2820

9.00(-A or -EN) or later

Member switch only

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


CMS is not forward-compatible on command switches running Cisco IOS 12.1(14)EA1 and earlier. This means that if a member switch is running a release that is earlier 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 running a release that is later than the release on the command switch, the command switch cannot recognize the member switch, and the Front Panel view displays it as an unknown device. You cannot configure any parameters or generate a report through CMS for that member; instead, you must launch the Device Manager application to configure and to obtain reports for that member.

Some versions of the Catalyst 2900 XL software do not support clustering, and if you have a cluster with switches that are running different versions of Cisco IOS software, software features added on the latest release might not be reflected on switches running the older releases. For example, if you start CMS 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.

Downloading Software

Before downloading software, read this section for important information. These are the procedures for downloading software:

"Finding the Software Version and Feature Set" section

"Deciding 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


Caution A bootloader upgrade occurs if you are upgrading the switch from a noncryptographic image to cryptographic image, regardless of the current noncryptographic Cisco IOS Release that is running on the switch. The bootloader can take up to 30 seconds to upgrade. Do not power cycle the switch while you are copying this image to the switch. If a power failure occurs when you are copying this image to the switch, call Cisco Systems immediately.

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.

Finding the Software Version and Feature Set

The Cisco IOS image is stored as a bin file in a directory that is named with the Cisco IOS release. A subdirectory contains the files needed for web management. The image is stored on the system board flash device (flash:).

You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line displays C3550-I5Q3L2 for the enhanced multilayer software image (EMI) or C3550-I9Q3L2 for the standard multilayer software image (SMI).


Note Although the show version output always shows the software image running on the switch (Layer 2 only or Layer 2 and Layer 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.

Deciding 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 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 3 lists the software filenames for this Cisco IOS release.

Table 3 Cisco IOS Software Files for Catalyst 3550 Switches 

Filename

Description

c3550-i9q3l2-tar.121-22.EA1a.tar

Cisco IOS SMI image file and the CMS files.
This image has Layer 2+ and basic Layer 3 routing features.

c3550-i5q3l2-tar.121-22.EA1a.tar

Cisco IOS EMI image file and the CMS files.
This image has Layer 2+ and full Layer 3 features.

c3550-i9k2l2q3-tar.121-22.EA1a.tar

Cisco IOS SMI cryptographic image file and the CMS files. This image has the Kerberos, Secure Shell (SSH), Layer 2+, and basic Layer 3 routing features.

c3550-i5k2l2q3-tar.121-22.EA1a.tar

Cisco IOS EMI cryptographic image file and the CMS files. This image has the Kerberos, SSH, Layer 2, and full Layer 3 features.


The Catalyst 3550 switch is supported by either the SMI, which provides Layer 2+ features and basic Layer 3 routing, or the EMI, which provides Layer 2+ features, full Layer 3 routing, and advanced services. All Catalyst 3550 Gigabit Ethernet switches are shipped with the EMI installed. Catalyst 3550 Fast Ethernet switches are shipped with either the SMI or the EMI installed. After initial deployment, you can order the Enhanced Multilayer Software Image Upgrade kit to upgrade the Catalyst 3550 Fast Ethernet switches from the SMI to the EMI.

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.


Caution A bootloader upgrade occurs if you are upgrading the switch from a noncryptographic image to cryptographic image, regardless of the current noncryptographic Cisco IOS release that is running on the switch. The bootloader can take up to 30 seconds to upgrade. Do not power cycle the switch while you are copying this image to the switch. If a power failure occurs when you are copying this image to the switch, call Cisco Systems immediately.

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. This procedure requires a configured TFTP server.


Caution A bootloader upgrade occurs if you are upgrading the switch from a noncryptographic image to a cryptographic image, regardless of the current noncryptographic Cisco IOS release that is running on the switch. The bootloader can take up to 30 seconds to upgrade. Do not power cycle the switch while you are copying this image to the switch. If a power failure occurs when you are copying this image to the switch, call Cisco Systems immediately.

To download software, follow these steps:


Step 1 Use Table 3 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

To download the SMI and EMI files, select Catalyst 3550 software.

To obtain authorization and to download the cryptographic software files, select Catalyst 3550 3DES Cryptographic Software.

Step 3 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.

For more information, refer to Appendix B in the Catalyst 3550 Multilayer Switch Software Configuration Guide.

Step 4 Log in to the switch through the console port or a Telnet session.

Step 5 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 6 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 198.30.20.19 and to overwrite the image on the switch:

Switch# archive download-sw /overwrite tftp://198.30.20.19/c3550-i5q3l2-tar.121-22.EA1.tar

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.

Upgrading with a Nondefault System MTU Setting

If the switch was running Cisco IOS Release 12.1(8)EA1c or earlier and you had used the system mtu global configuration command to configure a nondefault system maximum transmission unit (MTU) size on your switch, follow these steps to upgrade your switch to Cisco IOS Release 12.1(11)EA1 or later:


Step 1 Upgrade the Cisco IOS software to Cisco IOS Release 12.1(11)EA1 or later.

Step 2 If a system MTU size of greater than 2000 is configured on the Catalyst 3550-12T or Catalyst 3550-12G, use the system mtu global configuration command to set it to the maximum supported MTU size.


Note The maximum allowable system MTU for Catalyst 3550 Gigabit Ethernet switches
is 2000 bytes; the maximum system MTU for Fast Ethernet switches is 1546 bytes.


Step 3 Save the running configuration by entering the copy running-config startup-config privileged EXEC command.

Step 4 Reload the switch by using the new Cisco IOS software.

Step 5 When the switch comes back up with Cisco IOS Release 12.1(11)EA1 or later, reload the switch a second time by using the reload privileged EXEC command so that the system mtu command takes effect.


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.

Installation Notes

You can assign IP information to your switch by using these methods:

The Express Setup program described in the hardware installation guide.

The CLI-based setup program described in the hardware installation guide.

The Dynamic Host Configuration Protocol (DHCP)-based autoconfiguration described in the software configuration guide.

Manually assigning an IP address described in the software configuration guide.

New Features

These are the new supported hardware and the new software features provided in this release.

New Hardware Features

For a list of supported hardware, see the "Hardware Supported" section.

New Software Features

This release contains these new Catalyst 3550 switch enhancements:

Configure storm control by using the rate at which packets are received on input interfaces.

Configure the duplex setting when the speed is set to auto.

Specify the speed at which a switch port autonegotiates.

Verify the speed and duplex settings and inline power status on a port by entering the show interfaces transceiver properties privileged EXEC command.

For more information about these feature enhancements, see the "Documentation Updates" section.

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.

These are the limitations and restrictions:

"Cisco IOS Limitations and Restrictions" section

"Cluster Limitations and Restrictions" section

"CMS Limitations and Restrictions" section

Cisco IOS Limitations and Restrictions

These limitations apply to Cisco IOS configuration:

The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.

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-Differentiated Service Code Point (DSCP) counter (for DSCP 0) is incremented. Normal networks should not have packets with CRC errors. (CSCdr85898)

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. (CSCds55220)

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 forwarding 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 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 show interface interface-id privileged EXEC command output, 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 QoS to map the 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)

Remote Monitoring (RMON) collection functions on physical interfaces, but it is not supported on EtherChannels and SVIs. (CSCdt36101)

Multicast router information is displayed in the show ip igmp snooping mrouter privileged EXEC command output 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)

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 use 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)

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 entering 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)

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)

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)

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. (CSCdt79172)

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 type of service (TOS). Statements relating to DSCP apply equally to either IP precedence or IP TOS. (CSCdt94355)

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 Inter-Switch Link (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 a switch stack contains both Catalyst 3550 switches and Catalyst 2900 XL or Catalyst 3500 XL switches, Cross-Stack UplinkFast (CSUF) is not enabled if the management VLAN on the Catalyst 2900 XL or 3500 XL switches is changed to a VLAN other than VLAN 1 (the default).

The workaround is to make sure that the management VLAN of all Catalyst 2900 XL or 3500 XL switches in the stack is set to VLAN 1. (CSCdv79737)

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)

Multicast traffic can be temporarily lost when a link comes up in a redundant network and causes the reverse path forwarding (RPF) to change. This only occurs when there are multiple paths between the rendezvous point (RP) and the multicast source. (CSCdw27519)

The switch might reload when it is executing the no snmp-server host global configuration command. This is a rare condition that can happen if SNMP traps or informs are enabled and the SNMP agent attempts to send a trap to the host just as it is being removed from the configuration and if the IP address of the host (or the gateway to reach the host) has not been resolved by Address Resolution Protocol (ARP).

The workaround is to ensure that the target host or the next-hop gateway to that host is in the ARP cache (for example, by using a ping command) before removing it from the SNMP configuration. Alternatively, disable all SNMP traps and informs before removing any hosts from the SNMP configuration. (CSCdw44266)

When you access CISCO-STACK-MIB portTable, the mapping might be off by one from the mapping given by the switch. The objects in this table are indexed by two numbers: portModuleIndex and portIndex. The allowable values for portModuleIndex are 1 through 16. Because 0 is not an allowable value, the value 1 represents module 0.

The workaround is to use the value 1 to represent module 0. (CSCdw71848)

If a port on the Catalyst 3550 switch that is running the Multiple Spanning Tree Protocol (MSTP) is connected to another switch that belongs to a different multiple spanning tree (MST) region, the Catalyst 3550 port is not recognized as a boundary port when you start the protocol migration process by using the clear spanning-tree detected-protocols interface interface-id privileged EXEC command. This problem occurs only on the root bridge, and when the root bridge is cleared, the boundary ports are not shown because the designated ports do not receive any bridge protocol data units (BPDUs) unless a topology change occurs. This is the intended behavior.

The workaround is to configure the Catalyst 3550 switch for Per-VLAN spanning-tree plus (PVST+) by using the spanning-tree mode pvst global configuration command bridge, and then change it to MSTP by using the spanning-tree mode mst global configuration command. (CSCdx10808)

When a large number of VLANs and a large number of trunk ports with allowed VLAN lists are configured on the switch, if you enter the no switchport trunk allowed vlan interface-range command to remove the allowed list for all the trunk ports, the SYS-3-CPUHOG system message might appear.

The workaround is to use the no switchport trunk allowed vlan interface configuration command on each trunk port to remove the allowed list for all the trunk ports. (CSCdx17189)

When 1000 VLANs and more than 40 trunk ports are configured, and the spanning-tree mode changes from MSTP to PVST+ or vice versa, this message appears on the console:

%ETHCNTR-3-RA_ALLOC_ERROR: RAM Access write pool I/O memory allocation failure

There is no workaround. However, we recommend that you reload the switch by using the reload privileged EXEC command. To avoid this problem, configure the system with fewer VLANs and fewer trunk ports, or use the switchport trunk allowed vlan interface configuration command to reduce the number of active VLANs on each trunk port. (CSCdx20106)

Ternary content addressable memory (TCAM) generation might fail when there are multiple ACLs in a policy-map. If you add an entry that checks TCP flags to an access list that is used for QoS classification, the system might report that a hardware limitation has been reached for the policy map. This can occur when the policy map already contains several other access list entries that check different TCP flags, or that check TCP or User Datagram Protocol (UDP) port numbers using an operation different from equal (eq), such as not equal (ne), less than (lt), greater than (gt), or range. When the hardware limitation is reached, the service-policy input policy-map-name interface configuration command is removed from the running configuration of the interface.

Checking for TCP flags and TCP/UDP port numbers using operators other than eq share some of the same hardware resources. The switch supports no more than six checks within a single policy map. An identical check repeated in multiple entries in the same policy map counts as a single instance. If this limit is reached during a TCP or UDP port number check, the software can often work around the problem by allocating extra entries in the TCAM. There is no workaround if the limit is reached during a check against the TCP flags in the packet. Similar checks in a port ACL applied to the same physical interface as the policy map also count toward the limit.

Because these resources are allocated on a first-come, first-serve basis, rearranging the order of ACLs within a policy map or the order of entries within a single ACL, placing the TCP flags checks as early as possible, might enable the policy map to be loaded into the hardware.

Similar limits apply for any combination of input VLAN maps, input router ACLs, output VLAN maps, and output router ACLs that share the same VLAN label. The switch supports eight checks for all features on the same VLAN label. When the limit is reached, the system might forward packets by using the CPU rather than through hardware, greatly reducing system performance. To determine the VLAN label assigned to a VLAN or interface on input or output, use the show fm vlan or show fm interface privileged EXEC commands. Then use the show fm vlan-label privileged EXEC command to determine which set of features (input VLAN map, input router ACL, output VLAN map, or output router ACL) share this label.

These are the workarounds:

Re-arrange the order of classes within the policy map and the order of entries within the individual access lists in the policy map or within any IP port ACL applied to the interface so that checks for TCP flags are made as early as possible within the policy map. You can also re-arrange the order of the individual ACLs within a VLAN map and the order of the individual entries in a security ACL.

Add an extra entry to the front of an ACL that checks for the same TCP flags that are checked later on in the ACL. If the first entry of the ACL already matches only the TCP protocol, you can duplicate the entry and add a check for the appropriate TCP flags.

Reduce the number of different combinations of TCP flags being tested.

If the other workarounds fail, avoid combining any check against the TCP flags with gt, lt, ne, or range checks within the policy map and port ACL configured on the interface or within the VLAN maps and router ACLs that share the same VLAN label. (CSCdx24363)

If you apply an ACL to an interface that has a QoS policy map attached and the ACL is configured so that the packet should be forwarded by the CPU or if the configured ACL cannot fit into the ternary content addressable memory (TCAM), all packets received from this interface are forwarded to the CPU. Because traffic forwarded to the CPU cannot be policed by the policer configured on the interface, this traffic is not accurately rate-limited to the configured police rate.

The workaround, when QoS rate limiting is configured on an interface, is to configure applied ACLs so that packets are not forwarded by the CPU or reduce the number of ACEs in the ACL so that it can fit into the TCAM. (CSCdx30485)

When you reboot a Catalyst 3550-24-FX switch, it might loop back packets received on a 100BASE-FX port to its link partner. This can occur before the Cisco IOS software takes control of the system and lasts for about 200 milliseconds.

As a result, the link partner might shut down the port when it detects loopback packets, or MAC addresses might be learned on the wrong ports on upstream switches. The network might be unable to deliver packets to a few devices for up to 5 minutes after rebooting the Catalyst 3550-24-FX switch when:

The Catalyst 3550-24-FX switch is connected to one or more switches in the network.

Spanning tree is disabled in the network or the Port Fast feature is enabled on the ports connected to the Catalyst 3550-24-FX switch.

The Catalyst 3550-24-FX switch is powered cycled or reloaded from CLI.

One or more devices in the network transmit a broadcast or multicast packet during the 200-millisecond timing window while the Catalyst 3550-24-FX switch is booting.

This problem corrects itself after five minutes or when these devices transmit a broadcast or multicast packet, whichever comes first.

The workaround is to enable spanning tree in the network and to make sure that the Port Fast feature is disabled on all ports connected to the Catalyst 3550-24-FX switch. (CSCdx45558)

If the switch fails for any reason while you are exiting VLAN configuration mode (accessed by entering the vlan database privileged EXEC command), there is a slight chance that the VLAN database might get corrupted. After resetting from the switch, you might see these messages on the console:

%SW_VLAN-4-VTP_INVALID_DATABASE_DATA: VLAN manager received bad data of type device 
type: value 0 from vtp database 

$SW_VLAN-3-VTP_PROTOCOL_ERROR: VTP protocol code internal error 

The workaround is to use the delete flash:vlan.dat privileged EXEC command to delete the corrupted VLAN database. Then reload the switch by using the reload privileged EXEC command. (CSCdx19540)

If you apply a large ACL and it fills the entire TCAM, the MVR IP multicast data packets are sent to the switch CPU and are not forwarded to the MVR receiver ports. (CSCdx80751)

When a Cisco RPS 300 Redundant Power System provides power to a switch, after the switch power supply is restored, the RPS 300 continues to provide power until the RPS mode button is pressed. At this point, some switches restart, depending on how quickly the switch internal power supply resumes operation. (CSCdx81023)

If you create a policy map by using the policy-map policy-map-name global configuration command, enter the class class-map-name policy-map configuration command, and then immediately exit from the policy-map class configuration mode, the policy map does not show its class-map association.

The workaround is to enter another command (such as the police, trust, or set policy-map class configuration command) after entering the class class-map-name policy-map configuration command. (CSCdx81650)

When you insert a GigaStack GBIC in a GBIC module slot, the CPU utilization increases by six percent. This increase occurs for each GigaStack GBIC added to the switch. Other types of GBICs do not cause additional CPU utilization. (CSCdx90515)

An RSPAN source session does not forward monitored traffic to the RSPAN destination session if there is an egress SPAN source port in the session with port security or 802.1x enabled. (CSCdy21035)

Not all traffic is properly mirrored by RSPAN when a port is monitored for egress traffic and the RSPAN VLAN is carried through a Layer 2 Protocol Tunnel to the RSPAN destination switch.

This happens because the MAC addresses for the original packets as well as the mirrored RSPAN packets are all learned on the tunnel VLAN, so the RSPAN traffic is no longer properly segregated on the tunneling switches.

The workaround is to not include any RSPAN VLANs in any Layer 2 Protocol tunnels unless the tunnel is dedicated to a single RSPAN VLAN. (CSCdy37188)

Ingress forwarding on a SPAN destination port does not work if there is an egress SPAN source port in the session with port security or 802.1x enabled. (CSCdy44646)

When the switch receives multicast traffic and IGMP join for requests a multicast group at the same time and it begins to forward the multicast packets, some of the packets might be dropped. (CSCdy80326)

If a Catalyst 3550 switch is connected to two routers (Router 1 and Router 2) in this topology:

The link between Router 1 and the switch is a BVI (bridge virtual interface) that belongs to two VLANs (VLAN 100 and VLAN 110) and uses one IP address. The IP subnet for the BVI is the same for both VLANs. The ports in both VLANs operate as Layer 2 interfaces. An SVI with an IP address is configured only on VLAN 100.

The link between Router 2 and the switch is an IP interface that only belongs to VLAN 110.

IP connectivity then exists between Router 1 and the switch. There is no IP connectivity between Router 2 and the switch.

The workaround is to configure another SVI with an IP address on the Catalyst 3550 switch that would be reachable from Router 2. (CSCdy82042)

The 5 minute input rate and 5 minutes output rate fields in the output of the show interfaces privileged EXEC command show both rates as 0 bits/sec. If you enter the show interfaces command more than once, these fields might show values greater than 0 bits/sec. (CSCdz06305)

When the link between a device with an AC power supply and a Catalyst 3550-24PWR switch is 10 Mbps and half duplex, and the AC power supply is turned off, the switch is in the error-disabled state.

The workaround is remove the AC power supply, disconnect the Ethernet cable, and then reconnect the Ethernet cable. This ensures that the switch uses inline power. (CSCdz16265)

When you perform a ping from a VLAN to another VLAN on the same switch, the VLAN counter does not change. (CSCdz17863)

The Catalyst 3550 switch does not adjust the power allocation based on IEEE class of the power device. When an IEEE powered-compliant device is connected to a switch, it allocates 15 W (the default) to the port. (CSCdz37516)

When an 802.1x-authenticated client is disconnected from an IP phone, hub, or switch and does not send an EAPOL-Logoff message, the switch interface does not transition to the unauthorized state. If this happens, it can take up to 60 minutes for the interface to transition to the unauthorized state when the re-authentication time is the default value (3600 seconds).

The workaround is to change the number of seconds between re-authentication attempts by using the dot1x timeout re-authperiod seconds global configuration command. (CSCdz38483)

When the link between two switches is a Ethernet cable to an E3 converter, if MST is enabled on an 802.1Q trunk, traffic is not forwarded or sent for 60 seconds after the shutdown and no shutdown interface configuration commands are entered. (CSCdz45037)

When a switch receives a bridge STP bridge protocol data unit (BPDU) from an access port and the egress port is a trunk port, the switch assigns the BPDU a CoS value of 0 instead of 7.

There is no workaround. (CSCdz54043)

If a switch configuration contains a large ACL and a per-port per-VLAN policy map that both are attached to two interfaces, when you are copying it to the running configuration, this process might fail because the switch runs out of memory. (CSCdz54115)

These are the workarounds:

Copy the new configuration file to the config.txt file, and reboot the switch.

Save the configuration file as two files: one containing only the ACL configuration and one containing the rest of the configuration (including the QoS and interface configuration). Add the first configuration file to the running-configuration file, and then add the second file to the running-configuration file.

After the no interface tunnel0 global configuration command is entered to remove the tunnel interface, the output from the show running-config privileged EXEC command still shows the tunnel interface that was removed. (CSCdz66450)

This can occur if HSRP interface tracking is configured on another interface to track a tunnel interface, if the no interface command was entered before the HSRP tracking configuration was removed, or if the no standby tunnel0 global configuration command was entered on the other interface to disable tracking.

These are the workarounds:

Before removing the tunnel interface from the configuration, remove the HSRP interface tracking commands in the configuration that specify the tunnel interface.

Use the no standby track global configuration command without specifying an interface to disable HSRP tracking.

After a MAC address is relearned on a new interface, traffic might not be immediately forwarded to the MAC addresses. (CSCdz75459)

The Catalyst 3550 switch only supports the read operation in the sysClearPortTime MIB object (.1.3.6.1.4.1.9.5.1.1.13) in the CISCO-STACK-MIB. Use the clear counters privileged EXEC command to clear the counters. (CSCdz87897)

When a Catalyst 3550 switch is connected to a 3-port Gigabit Ethernet module in a Cisco 12000 Gigabit Switch Router (GSR) that is configured for Ethernet over Multiprotocol Label Switching (EoMPLS), the switch does not reliably send frames to the GSR.

The workaround is to configure the Catalyst 3550 Gigabit Ethernet interface with the spanning-tree portfast interface configuration command. (CSCea04746)

On a switch running Cisco IOS Release 12.1(12c)EA1 or later, if the switch MTU value is set to a value greater than 1500 and the authentication server and the intermediate devices are not configured with a compatible MTU value, 802.1x authentication with EAP-Transparent LAN Services (TLS) might fail.

The workaround is to reset the switch MTU value to the default value or to configure the same MTU value on the switch, the authentication server, and the intermediate devices. (CSCea05682)

If a cable on an ingress interface is disconnected, an Alteon A184 cannot detect when a 1000BASE-X link between two Catalyst 3550 switches is down.

There is no workaround. (CSCea09786)

Performing an extended ping from one interface to another interface on the same switch can cause high CPU utilization. This can occur when a large number of ping packets are sent and received and is the expected behavior.

The workaround is to not perform a ping from one interface to another on the same switch. (CSCea19301)

The switch does not create an adjacency table entry when the ARP timeout value is 15 seconds and the ARP request times out.

The workaround is to not set an ARP timeout value lower than 120 seconds. (CSCea21674)

If the output from the show tcam inacl 1 statistics privileged EXEC command shows that the TCAM is not full and you are applying an ACL, this system message might appear:

%FM-3-UNLOADING: Unloading input vlan label 1 feature from all TCAMs

There is no workaround. (CSCea25658)

When three or more Catalyst 3550-24PWR switches are connected through GigaStack GBICs, you can access all the VLANs on the uplink switch, but you can only access VLAN 1 on the other switches.

The workaround is to enter the switchport mode trunk interface configuration command on all of the GigaStack interfaces and do one of these:

Use the shutdown and then the no shutdown interface configuration commands on the ports.

Save the switch configuration by using the copy running-config startup-config privileged EXEC command, and reload all the switches. (CSCec86258)

The switch uses the same MAC address for all VLAN interfaces. If the destination MAC address in a packet is the same as the MAC address of the VLAN interface, and the VLAN interface for that VLAN is shut down or does not exist, the switch drops the packet.

There is no workaround. (CSCed12004)

When the switch has many routes that use loadsharing among multiple next hops, some of the routes might not loadshare but instead pick only one of the next hops for forwarding all packets on that route. This happens when the portion of the adjacency RAM that has been allotted for multipath routes has been used up.

There is no workaround. (CSCed22152)

The DHCP option-82 format on the Catalyst 3550 switch is inconsistent with other Cisco switches. When the Catalyst 3550 switch is used as the relay agent with DHCP snooping and the option-82 feature using the VLAN-module-port (vlan-mod-port) format, the switch does not assign the correct value to the port identifier (circuit ID suboption). The value is offset by 1 from the actual interface module- and port-number values. Also, the circuitID/port-identifier for Fast Ethernet and Gigabit Ethernet interfaces have the same module-number but different port-number values. For example, on a Catalyst 3550-24 switch, fastethernet0/1 is reported as module 0/port 0 and gigabitethernet0/1 is reported as module 0/port 24.

There is no workaround. (CSCed29525)

Storm control or traffic suppression (configured by using the storm-control {broadcast | multicast | unicast} 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.

When connected to some third-party devices that send early preambles, a Catalyst 3550 switch port operating at 100 Mbps full duplex or 100 Mbps half duplex might bounce the line protocol up and down. The problem is observed only when the Catalyst 3550 switch is receiving frames.

The workaround is to configure the port for 10 Mbps and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)

Packets received from media types that require SNAP encapsulation of IPv4 packets require the switch to forward SNAP-encapsulated packets. Layer 2 forwarding of IPv4 in SNAP encapsulation ordinarily takes place in hardware (unless a VLAN map or port ACL contains an IP ACL). However, on the Catalyst 3550 switch, Layer 3 forwarding of IPv4 in SNAP can only be done in software. SNAP-encapsulated IPv4 packets that are directed to the router MAC address or the HSRP group MAC address (if this device is the active router in the HSRP group) are forwarded to the switch CPU, potentially causing high CPU utilization levels.

This is a hardware limitation, and there is no workaround. (CSCed59864)

The undersize error counter is incrementing when no undersize packets are present. This condition occurs on 802.1Q tunnel ports connected to a Nortel or Alteon Load Balancer.

There is no known workaround. (CSCed73388)

When multi-VRF-CE is enabled on the switch, the switch does not support the ip directed-broadcast interface configuration command used to enable forwarding of IP-directed broadcasts on an interface.

There is no workaround. (CSCee05670)

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 documentation.

The switch might ignore the configured dot1x max-req value.

There is no workaround. (CSCee80587)

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.

Catalyst 3550 switches do not take into account the Preamble and Inter Frame Gap (IFG) when rate limiting traffic, which could result in a slightly inaccurate policing rate on a long burst of small-sized frames, where the ratio of the Preamble and IFG to frame size is more significant. This should not be an issue in an environment where the frames are a mix of different sizes.

Certain combinations of features and switches create conflicts with the port security feature. In Table 4, No means that port security cannot be enabled on a port on the referenced switch if the referenced feature is also running on the same port. Yes means that both port security and the referenced feature can be enabled on the same port at the same time. A dash means not applicable.

Table 4 Port Security Incompatibility with Other Switch Features 

 
Catalyst 2940
Catalyst 2950 and Catalyst 2955
Catalyst 2970
Catalyst 3550
Catalyst 3560 and Catalyst 3750

DTP1 port2

No

No

No

No

No

Trunk port

No

No

Yes

Yes

Yes

Dynamic-access port3

No

No

No

No

No

Routed port

No

No

SPAN source port

Yes

Yes

Yes

Yes

Yes

SPAN destination port

No

No

No

No

No

EtherChannel

No

No

No

No

No

Tunneling port

Yes

Protected port

Yes

Yes

Yes

Yes

Yes

802.1x port

Yes4

Yes

Yes

Yes

Voice VLAN port5

Yes

Yes

Yes

Yes

Yes

Private VLAN port

No6

IP source guard

Yes6

Dynamic ARP7 inspection

Yes6

Flex Links

Yes

Yes

1 DTP = Dynamic Trunking Protocol

2 A port configured with the switchport mode dynamic interface configuration command.

3 A VLAN Query Protocol (VQP) port configured with the switchport access vlan dynamic interface configuration command.

4 The switch must be running the enhanced software image (EI).

5 You must set the maximum allowed secure addresses on the port to two plus the maximum number of secure addresses allowed on the access VLAN.

6 The switch must be running the enhanced multilayer image (EMI).

7 ARP = Address Resolution Protocol


Cluster Limitations and Restrictions

These limitations apply to cluster configuration:

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, CSCds55711)

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)

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)

When the active switch fails in a switch cluster that uses Hot Standby Routing Protocol (HSRP) redundancy, the new active switch might not contain a full cluster member list.

The workaround is to ensure that the ports on the standby cluster members are not in the STP blocking state. Refer to the "Configuring STP" chapter in the software configuration guide for more information about verifying port status. (CSCec31495)

CMS Limitations and Restrictions

These limitations apply to CMS configuration:

CMS performance degrades if the Topology View is open for several hours on a Solaris machine. The cause might be a memory leak.The workaround is to close the browser, reopen it, and launch CMS again. (CSCds29230)

If you are printing a Topology View or Front Panel View that contains many devices and are running Solaris 2.6 with JDK1.2.2, you might get an Out of Memory error message. The workaround is to close the browser, re-open it, and launch CMS again. Before you perform any other task, open the view that you want to print, and click Print in the CMS menu. (CSCds80920)

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. (CSCdv82352)

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. 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. (CSCdw87550)

If you open a window in which you can enter text, open another window, and return to the first window, right-clicking in the text field might make the cursor in this field disappear. You can still enter text in the field. (CSCdy44189)

CMS fails when a switch is running the cryptographic software image and the vty lines have been configured to use only SSH using the transport input ssh and line vty 0 15 global configuration commands. The workaround is to allow SSH and Telnet access through the vty lines by using the transport input ssh telnet and line vty 0 15 global configuration command. (CSCdz01037)

When you add a new member with a username and password that is different from the existing cluster member usernames and passwords, CMS produces an exception error because of an authentication failure. The workaround is to add the new member without any username and password. When the new member is added to the cluster, remove the existing username and password from the Username and Password fields, enter a new username and password, and then apply it to all cluster members. (CSCdz07957)

When the Link Graphs application has run for hours displaying packet drop and error information, sometimes the X-axis crosses the Y-axis at a negative y value instead of at y = 0. This condition occurs with all supported operating systems, browsers, and Java plug-ins. There is no workaround. (CSCdz32584)

After you click Apply or Refresh in the Simple Network Management Protocol (SNMP) window, the window size changes. (CSCdz75666, CSCdz84255)

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 browser when you are using Netscape version 6.xx on Solaris and Linux. This is a Netscape browser problem. There is no workaround. (CSCea01179)

CMS sometimes halts after you click Apply when using Netscape 4.7 on the Japanese version of Windows 98 or Windows ME. The workaround is to use Microsoft Internet Explorer or Netscape 6.0 or later. (CSCea27408)

Changing the password or current authentication while CMS is running causes HTTP requests to fail. The workaround is to close all browser sessions and then relaunch CMS. (CSCeb33995)

The CMS plug-in is not supported in Netscape 4.7x. The workaround is to use a supported browser, such as Netscape 7.1 or Internet Explorer 5.5 or 6.0. (CSCed21655)

When TACACS authentication is only enabled on a command switch, member switches cannot be configured. The workaround is to enable TACACS authentication on the member switches. (CSCed27723)

If an ACL is deleted from a device, all QoS classes that use this ACL for traffic classification become unusable (only on Catalyst 2970 and 3750 switches). The modification of these classes to use any other traffic classification (match statement) fails. The workaround is to delete the QoS class that uses the undefined ACL and then recreate it with the intended traffic classification (match statement). (CSCed40866)

When an Open Shortest Path First (OSPF) summary address is added for a 10.x.x.x network, a Windows exception error sometimes occurs.

The workaround is to add the address by using the router ospf <process-id>, area <area-id>, and range <address> <mask> configuration commands. (CSCed87031)

The Telnet link on the TOOLS page (select TOOLS from the switch home page) does not work on Solaris systems.

There is no workaround. (CSCee11710)

A Java exception error occurs when CMS is in read-only mode and you launch the Port Settings dialog. This only occurs on Catalyst 2900 XL, 3500 XL, and 2950 LRE switches.

The workaround is to open the Port Settings dialog with CMS in read-write mode. (CSCee25870)

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.

Access control entries (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.

Important Notes

These are the important notes related to this Cisco IOS release:

"Cisco IOS Notes" section

"Cluster Notes" section

"CMS Notes" section

Cisco IOS Notes

These notes apply to Cisco IOS configuration:

In Cisco IOS Release 12.1(19)EA1, the implementation for the Option-82 Subscriber Identification changed from the previous release. The new option-82 format uses a different circuit ID and remote ID suboption, vlan-mod-port. The previous version uses the snmp-ifindex circuit ID and remote ID suboption.

If you have option-82 configured on the switch and you upgrade to Cisco IOS Release 12.1(19)EA1 or later, the option-82 configuration is not affected. However, when you globally enable DHCP snooping on the switch by using the ip dhcp snooping global configuration command, the previous option-82 configuration is suspended, and the new option-82 format is applied. When you globally disable DHCP snooping on the switch, the previous option-82 configuration is re-enabled.

To provide for backward compatibility, you can select the previous option-82 format by using the ip dhcp snooping information option format snmp-ifindex global configuration command when you enable DHCP snooping. When DHCP snooping is globally enabled, option-82 information (in the selected format) is only inserted on snooped VLANs.

For more information about using the previous version of option-82 without enabling DHCP snooping, see the software configuration guide for this release.

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 address of the IP 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.

If you configure a port ACL on a physical interface on a switch that has VLAN maps or input router ACLs configured, or if you configure a VLAN map or input router ACL on a switch that has port ACLs configured, a CONFLICT message is generated but the configuration is accepted. The port ACL action has priority on that port over actions in a router ACL or VLAN map applied to the VLAN to which the port belongs.

The result is that packets received on that physical port will be permitted or denied based on the port ACL action without regard to any permit or deny statements in any router ACL or VLAN map, while packets received on other physical ports in the VLAN will still be permitted or denied based on any router ACLs or VLAN maps applied to the VLAN. If the port ACL is applied to a trunk port, it overrides any other input ACLs applied to all VLANs on the trunk port.

The default system MTU for traffic on the Catalyst 3550 switch is 1500 bytes. The 802.1Q tunneling feature increases the frame size by 4 bytes. Therefore, when you configure 802.1Q tunneling, you must configure all switches in the 802.1Q network to be able to process maximum frames by increasing the switch system MTU size to at least 1504 bytes. You configure the system MTU size by using the system mtu global configuration command.

Beginning with Cisco 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 command reference.

When you are configuring a cascaded stack of Catalyst 3550 switches by using the GigaStack GBIC module 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 command reference.

If the 1000BASE-T GBIC (WS-G5482) module 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 module.

Beginning with Cisco IOS Release 12.1(11)EA1, the mac address-table aging-time command replaces the mac-address-table aging-time command (with the hyphen). The mac-address-table aging-time command (with the hyphen) will become obsolete in a future release.

Beginning with Cisco IOS Release 12.1(11)EA1, the vtp privileged EXEC command keywords are available in the vtp global configuration command. The vtp privileged EXEC command will become obsolete in a future release.

Beginning with Cisco IOS Release 12.1(12c)EA1, the ip igmp query-interval seconds interface configuration command range is 1 to 18000 seconds. If your existing configuration includes a value larger than 18000, the command has no effect, and the switch returns a warning message the first time you restart the switch with the upgraded software. Enter a new value by using the ip igmp query-interval seconds interface configuration command, and then save your configuration.

If the switch has insufficient Layer 4 resources, this message might appear when configuring port ACLs:

%Error: cannot create VMR data structures.
%FM-2-NOVMR: Cannot create VMR data structures for access list 131

If this message appears, the switch did not apply the ACL to the port. (CSCdx42414)

Beginning with Cisco IOS Release 12.1(12c)EA1, you can set the CoS value of incoming traffic in a policy map that includes the trust dscp policy-map class configuration command. To do this, follow the steps described in the "Classifying, Policing, and Marking Traffic by Using Policy Maps" section in the "Configuring QoS" chapter of the software configuration guide for this release. (CSCdy45670)

When you configure a dynamic switchport by using the switchport access vlan dynamic interface configuration command, the port might allow unauthorized users to access network resources if the interface changes from access mode to trunk mode through Dynamic Trunking Protocol (DTP) negotiation.

The workaround is to configure the port as a static access port. (CSCdz32330)

If a spanning-tree loop occurs, this message might appear:

MALLOCFAIL, alignment 0. -Process=Syslog Traps -Traceback= 1A3740

This message appears because the switch has run out of I/O memory and is unable to allocate a packet buffer to report the error. You can also verify if the switch runs out of I/O memory by using the show memory privileged EXEC command.

The workaround is to reconfigure the spanning tree to remove the loop. (CSCdz51522)

Beginning in Cisco IOS Release 12.1(13)EA1, these are the default settings for a IP Phone connected to a switch (CSCdz76948):

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.

Catalyst 3550-24-FX switches support both full- and half-duplex mode, and the default duplex mode is half duplex. Autonegotiation of the duplex mode is not supported.

On a Catalyst 3550-24-FX switch, when you upgrade to Cisco IOS Release 12.1(13)EA1 or later, all ports are reset to half-duplex mode. This will cause a duplex setting mismatch if the switch is connected to another device operating in full-duplex mode. After upgrading to Cisco IOS Release 12.1(13)EA1 or later, you should configure the Catalyst 3550-24-FX switch to operate in full-duplex mode, if necessary. (CSCdz29482)

Cluster Notes

The cluster setup privileged EXEC command and the standby mac-address interface configuration command have been removed from the CLI and the documentation because they did not function correctly.

CMS Notes

These notes apply to 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.

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.cisco.com), 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 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.

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.

The workaround is to resize the browser window again when CMS is not busy.

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 with possible unexpected activity in this Cisco IOS release:

"Open Cisco IOS Caveats" section

"Open CMS Caveats" section

Open Cisco IOS Caveats

These are the severity 3 Cisco IOS configuration caveats:

CSCdx95501

When a community string is assigned by the cluster command switch, you cannot get any dot1dBridge MIB objects by 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.

Mbr3(config)#snmp community public@es3@1 RO
Mbr3(config)#snmp community public@es3@2 RO
Mbr3(config)#snmp community public@es3@3 RO

CSCec27355

If a policy map with more than 75 class statements and class maps is configured on an interface and you add a class map to this policy map, the switch might reload.

The workaround is to:

End all Telnet sessions other than the one that you are using.

Remove the policy map from the interface, add the class map, and re-attach the policy map to the interface.

CSCec46594

If you are configuring a policy map on an interface by using named ACLs and the policy map has 13 named ACLs that include deny statements, these messages might appear when you add an ACL:

QoS: Programming TCAM failed: Unsuccessful ACL merge
 Service Policy attachment failed
 Service Policy xxxx not attached
QM-4-HARDWARE_NOT_SUPPORTED: Hardware limitation has reached for policymap xxxx

Use one of these workarounds:

Use numbered ACLs.

Do not use deny statements because the end of an ACL has an implicit deny statement.

CSCed02730

When policy-based routing (PBR) is enabled on an ingress Layer 3 interface that receives routed packets, the default gateway might not send IP Control Message Protocol (ICMP) redirect messages to a host. This might occur when:

The default gateway is defined but does not generate an ICMP redirect message. This occurs when the routing table has a packet route that specifies a host on another subnet instead of the next hop specified by PBR.

The default gateway sends an ICMP redirect message, but the local router specified in the ICMP redirect message is the next hop in the routing table instead of the next hop specified by PBR.

The workaround is use the no ip redirects interface configuration command to not send ICMP redirect messages to the interface on which PBR is enabled. Using this command disables all ICMP redirect messages sent to or from the interface.

There is no workaround. However, when a valid link partner is connected to the inline power port, it operates normally and without user intervention.

CSCed87243

If the VTP password is configured but the VTP domain name is not configured, and if the switch reloads twice, the switch does not retain the VLAN information.

Use of these workarounds:

Delete the vlan.dat file, which deletes the VTP password.

Delete the VTP password by using the no vtp password global configuration command.

Assign a VTP domain name.

CSCee17595

MAC address-table notifications are not sent when addresses are removed from the address table. Notifications are sent only when MAC addresses are added to the address table.

There is no workaround.

CSCee19574

When one Fast Ethernet port on a switch (Switch A) is connected to a packet generator, and another Fast Ethernet port on the switch is connected to a Gigabit Ethernet interface on another switch (Switch B), multicast traffic sent from Switch A to Switch B is incorrectly counted. The output from the show mls qos interface interface-id statistics command for the Gigabit Ethernet interface is incorrect.

There is no workaround.

CSCee37213

When modifications are made to access-list entries associated with a route map, the modifications have no effect. The problem occurs when the access-list entries are modified after the route map is created.

The workaround is to remove the route map by using the no route-map map-tag global configuration command and remove the access list associated with it by using the no access-list access-list-number global configuration command. Then recreate the access list and then the route map.

CSCee87655

The switch prompts the 802.1x client to authenticate twice.

There is no workaround.

Open CMS Caveats

These are the open severity 3 CMS configuration caveats:

CSCed39693

When there are Catalyst 2950 and 2955 devices in a cluster, if you launch the QoS Queue Window to configure the devices and then try to view the settings for other devices by using the device selection menu, CMS halts after 20 to 30 selections.

The workaround is to close and then restart CMS.

CSCed88494

When you change the Spanning Tree Protocol (STP) mode from Rapid PVST+ to PVST+, a Java OutOfBoundsException error sometimes appears.

There is no workaround. The new STP mode is still configured even if the error message appears.

CSCee06206

When a Catalyst 3750 stack member leaves or joins the switch stack, the entire stack disappears from the Topology View. Only the stack member that has left the stack should disappear from the Topology view.

There is no workaround.

CSCee06244

When you select a remote device from the VLAN menu, the displayed table sometimes does not show all the connected links between the device selected in the Host Name and the Remote Device lists. This can also occur when you add a new device to a cluster and then open VLAN menu.

This is the workaround:

1. Click Refresh on the CMS toolbar two or three times, or select View > Refresh two or three times.

2. Click Refresh in VLAN Window.

CSCee15761

The Device Manager Launch button does not work for Catalyst 1900 and 2820 switches.

The workaround is to launch Device Manager for these devices outside of CMS by opening a new browser and manually entering the URL for the switch.

CSCee26671

When you click Refresh in the Stack Settings dialog, the latest information switch cluster does not appear.

The workaround is to close and then to reopen the Stack Settings dialog.

Resolved Caveats

These are the caveats that have been resolved in this release.

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1a" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(20)EA2" section

"CMS Caveats Resolved in Cisco IOS Release 12.1(22)EA1" section

"CMS Caveats Resolved in Cisco IOS Release 12.1(20)EA2" section

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1a

This Cisco IOS caveat was resolved in Cisco IOS Release 12.1(22)EA1a:

CSCef25135

If a policy map has multiple classes and actions such as, trust dscp and set cos, and you modify it by adding or removing a class map and then remove the policy map, the Catalyst 3550 switch no longer fails.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(22)EA1

These Cisco IOS caveats were resolved in Cisco IOS Release 12.1(22)EA1:

CSCec84254

These Catalyst 3550 switches with 10/100BASE-T interfaces now link up with some media converters running at 100 Mbps:

WS-C3550-24-DC-SMI, WS-C3550-24-SMI/EMI, WS-C3550-48-SMI/EMI

This problem has been resolved when the listed switch is running one of these Cisco IOS Releases:

12.1(13)EA1, 12.1(13)EA1a, or 12.1(13)EA1c

12.1(14)EA1 or 12.1(14)EA1a

12.1(19)EA1, 12.1(19)EA1a, or 12.1(19)EA1c

CSCec89120

When the switch is the cluster command switch, it now discovers candidates greater than one routed hop beyond its routed ports.

CSCed15006

When a Type-1 Token Ring patch cable is connected to an inline power port on a Catalyst 3550-24PWR switch, the switch detects an error and now places the port into an err-disabled state.

CSCed18377

If the switchport nonegotiate interface configuration command is entered on an interface that is connected to a Catalyst 3550 switch, UniDirectional Link Detection (UDLD) now runs properly when the link goes down and then comes up quickly or when a neighbor port restarts.

CSCed53766

If a switch is running CDP Version 1, CDP Version 2 information is also advertised. The Catalyst 3550-24PWR switch now provides the proper power on its inline-power ports.

CSCed65285

Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server in combination with Terminal Access Controller Access Control System Plus (TACACS+) as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In User Service (RADIUS) is not affected by these vulnerabilities.

Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)

This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml

CSCed65778

Certain release trains of Cisco Internetwork Operating System (IOS), when configured to use the Cisco IOS Secure Shell (SSH) server in combination with Terminal Access Controller Access Control System Plus (TACACS+) as a means to perform remote management tasks on Cisco IOS devices, may contain two vulnerabilities that can potentially cause Cisco IOS devices to exhaust resources and reload. Repeated exploitation of these vulnerabilities can result in a Denial of Service (DoS) condition. Use of SSH with Remote Authentication Dial In UserService (RADIUS) is not affected by these vulnerabilities.

Cisco has made free software available to address these vulnerabilities for all affected customers. There are workarounds available to mitigate the effects of the vulnerability (see the "Workarounds" section of the full advisory for details.)

This advisory will be posted at http://www.cisco.com/warp/public/707/cisco-sa-20050406-ssh.shtml

CSCed65818

When the switch is running Rapid STP (MSTP or Rapid PVST+), it no longer causes a temporary spanning-tree loop when the root bridge changes and the switch must change forwarding paths.

CSCed82426

If you make a change to an access list that is applied to an interface, the switch no longer fails to deny a packet on another interface that has an access list applied to it.

CSCee11565, CSCee11587

These CISCO-STACK-MIB objects now return valid values:

vlanPortSwitchLevel

vlanPortIslAdminStatus

vlanPortIslOperStatus

vlanPortAdminStatus

CSCef04275

The switch no longer reloads when it receives an SNMP community string longer than 129 characters. This problem occurred only in Cisco IOS Release 12.1(20)EA2.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.1(20)EA2

These Cisco IOS caveats were resolved in Cisco IOS Release 12.1(20)EA2:

CSCeb83424

If you use the no network router configuration command to remove a network from an EIGRP configuration, the switch now correctly removes all of the subnetworks that are related to the specified network from the running EIGRP routing process.

CSCec43569, CSCec69647, CSCec77810

When a GigaStack GBIC module port is connected to an interface on another device and the switch reloads, the GBIC interface now behaves correctly:

If more than two switches are connected in a GigaStack loop, the loop is now detected, preventing broadcast storms.

The output from the show interfaces privileged EXEC command no longer shows the port status as down.

The GigaStack GBIC interface can now receive and forward traffic.

CSCec86385

When you enter the radius-server attribute nas-port format format global configuration command, the configured format takes effect.

CSCed01591

You can now obtain VLAN statistics information from clustered switches.

CSCed02043

After all the static MAC addresses for a VLAN are removed from the MAC address table, the output from the show mac address-table vlan privileged EXEC command might no longer show the CPU static addresses for the VLAN if the MAC address table parameters for the VLAN have changed from the default values.

CSCed05042

In the output from the debug mac-manager privileged EXEC command, the messages are now preceded by a time stamp.

CSCed10401

On a Catalyst 3550 switch, these MIB entries no longer contain invalid characters:

entPhysicalHardwareRev
entPhysicalSerialNum

The switch can now be added to the CiscoWorks Resource Manager Essentials (RME) database.

CSCed16439

Service Assurance Agent (SAA) now runs properly when 100 or more probes are configured that continuously send packets at 1-second intervals.

CSCed25122

The output from the show interfaces interface-id privileged EXEC command now shows the correct media types for the SFP modules.

CSCed54175

The switch now accepts duplicate remark statements in named ACLs.

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

These CMS caveats were resolved in Cisco IOS Release 12.1(22)EA1:

CSCee26637

When you open the Port Settings dialog for a Power-over-Ethernet (PoE) switch that is a member of a switch stack and the stack master is not a PoE switch, a Java exception error no longer occurs.

CSCec61919

When a switch cluster has only one member switch and that member switch is down, CMS now displays the Remove From Cluster option.

CMS Caveats Resolved in Cisco IOS Release 12.1(20)EA2

These CMS caveats were resolved in Cisco IOS Release 12.1(20)EA2:

CSCec18805

In the IP Multicast Wizard, multicast-enabled member devices are now correctly listed in the Enabled Multicast list box instead of in the Current Candidate list box.

CSCed34582

The Front Panel View now correctly displays the port LEDs.

Documentation Updates

This section provides updates to the product documentation. These changes will be included in the next revision of the documentation.


Note You can access all Catalyst 3550 documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/index.htm


These are the updates to the product documentation:

"Changes to the Catalyst 3550 Multilayer Switch Software Configuration Guide" section

"Changes to the Catalyst 3550 Multilayer Switch Command Reference" section

"Corrections to the Catalyst 3550 Multilayer Switch Software Configuration Guide" section

"Changes to the Catalyst 3550 Multilayer Switch System Message Guide" section

Changes to the Catalyst 3550 Multilayer Switch Software Configuration Guide

This section includes changes for these chapters:

"Configuring Port-Based Traffic Control" (see the "Configuring Storm Control" section)

"Troubleshooting" (see the "Troubleshooting Power over Ethernet Switch Ports" section)

Configuring Storm Control

The "Configuring Port-Based Traffic Control" chapter was changed to describe packet-based storm control.


Note This information replaces the information in the software configuration guide for Cisco IOS Release 12.1(20)EA2.


These sections include storm control configuration information and procedures:

Understanding Storm Control

Default Storm Control Configuration

Configuring Storm Control and Threshold Levels

Understanding Storm Control

Storm control prevents traffic on a LAN from being disrupted by a broadcast, a multicast, or a unicast storm on one of the physical interfaces. A LAN storm occurs when packets flood the LAN, creating excessive traffic and degrading network performance. Errors in the protocol-stack implementation or in the network configuration can cause a storm.

Storm control (or traffic suppression) monitors packets passing from an interface to the switching bus and determines if the packet is unicast, multicast, or broadcast. The switch counts the number of packets of a specified type received within the 1-second time interval and compares the measurement with a predefined suppression-level threshold.

Storm control uses one of these methods to measure traffic activity:

Bandwidth as a percentage of the total available bandwidth of the port that can be used by the broadcast, multicast, or unicast traffic

Traffic rate in packets per second at which broadcast, multicast, or unicast packets are received (Cisco IOS Release 12.1(22)EA1 or later)

With either method, the port blocks traffic when the rising threshold is reached. The port remains blocked until the traffic rate drops below the falling threshold (if one is specified) and then resumes normal forwarding. If the falling suppression level is not specified, the switch blocks all traffic until the traffic rate drops below the rising suppression level. In general, the higher the level, the less effective the protection against broadcast storms.


Note When the rate of multicast traffic exceeds a set threshold, all incoming traffic (broadcast, multicast, and unicast) is dropped until the level drops below the threshold level. Only spanning-tree packets are forwarded. When broadcast and unicast thresholds are exceeded, traffic is blocked for only the type of traffic that exceeded the threshold.


You use the storm-control interface configuration commands to set the threshold value for each traffic type.


Note Before Cisco IOS Release 12.1(8)EA1, you set up storm control threshold values by using the switchport broadcast, switchport multicast, and switchport unicast interface configuration commands. These commands are now obsolete, replaced by the storm-control interface configuration commands.


Default Storm Control Configuration

By default, unicast, broadcast, and multicast storm control is disabled on the switch: that is, the suppression level is 100 percent (no limit is placed on the traffic).

Configuring Storm Control and Threshold Levels

You configure storm control on a port and enter the threshold level that you want to be used by a particular type of traffic.

However, because of hardware limitations and the way in which packets of different sizes are counted, threshold percentages are approximations. Depending on the sizes of the packets making up the incoming traffic, the actual enforced threshold might differ from the configured level by several percentage points.


Note Storm control is supported only on physical interfaces; it is not supported on EtherChannel port channels even though the command is available in the CLI.


Beginning in privileged EXEC mode, follow these steps to configure storm control and threshold levels:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

interface interface-id

Specify the physical interface to configure and enter interface configuration mode.

Step 3 

storm-control {broadcast | multicast | unicast} level {level [level-low] | pps pps pps-low}

Configure broadcast, multicast, or unicast storm control. By default, storm control is disabled.

The keywords have these meanings:

For level, specify the rising threshold level for broadcast, multicast, or unicast traffic as a percentage (up to two decimal places) of the bandwidth. The port blocks traffic when the rising threshold is reached. The range is 0 to 100.

(Optional) For level-low, specify the falling threshold level as a percentage (up to two decimal places) of the bandwidth. This value must be less than or equal to the rising suppression value. The port forwards traffic when traffic drops below this level. If you do not configure a falling suppression level, it is set to the rising suppression level. The range is 0 to 100.

For pps pps, specify the rising threshold level for broadcast, multicast, or unicast traffic in packets per second. The port blocks traffic when the rising threshold is reached. The range is 0 to 4294967295.

For pps-low, specify the falling threshold level in packets per second. It can be less than or equal to the rising threshold level. The port forwards traffic when traffic drops below this level. The range is 0 to 4294967295.

Note If you set the threshold to the maximum value (100 percent or 4294967295), no limit is placed on the traffic. If you set the threshold to 0 0, all broadcast, multicast, and unicast traffic on that port is blocked.

Step 4 

end

Return to privileged EXEC mode.

Step 5 

show storm-control [interface-id] [broadcast | multicast | unicast]

Verify the storm control suppression levels set on the interface for the specified traffic type. If you do not enter a traffic type, broadcast storm control settings appear.

Step 6 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

To disable storm control, use the no storm-control {broadcast | multicast | unicast} level interface configuration command.

This example shows how to enable unicast storm control on a port with an 87-percent rising suppression level and a 65-percent falling suppression level:

Switch# configure terminal
Switch(config)# interface fastethernet0/1
Switch(config-if)# storm-control unicast level 87 65

Troubleshooting Power over Ethernet Switch Ports

The "Troubleshooting" chapter was changed to describe troubleshooting Power over Ethernet (PoE) switch ports.

This information was added:

"Disabled Port Caused by Power Loss" section

"Disabled Port Caused by False Link-Up" section

Disabled Port Caused by Power Loss

If a powered device (such as a Cisco IP Phone 7910) that is connected to a PoE switch port and is powered by an AC power source loses power from the AC power source, the device might enter an error-disabled state. To recover from an error-disabled state, enter the shutdown interface configuration command, and then enter the no shutdown interface command. You can also configure automatic recovery on the switch to recover from the error-disabled state. The errdisable recovery cause loopback and the errdisable recovery interval seconds global configuration commands automatically take the interface out of the error-disabled state after the specified period of time.

Use these commands, described in the command reference for this release, to monitor the PoE port status:

show controllers power inline privileged EXEC command

show power inline privileged EXEC command

debug ilpower privileged EXEC command

Disabled Port Caused by False Link-Up

If a Cisco powered device is connected to a port and you configure the port by using the power inline never interface configuration command, a false link-up can occur on the port, placing it into an error-disabled state. To take the port out of the error-disabled state, enter the shutdown and the no shutdown interface configuration commands.

You should not connect a Cisco powered device to a port that has been configured with the power inline never command.

Changes to the Catalyst 3550 Multilayer Switch Command Reference

These commands were changed in this release:

duplex interface configuration command was changed to support the duplex setting configuration when the speed is set to auto. See the "duplex" section.

power inline interface configuration command was changed to support duplex and speed interactions. See the "power inline" section.

show interfaces privileged EXEC command was changed to display speed, duplex, and inline power settings. See the "show interfaces" section.

show storm-control user EXEC command display was changed for packet-based storm-control settings. See the "show storm-control" section.

speed interface configuration command was changed to support using the 10, 100, and 1000 keywords with the auto keyword. See the "speed" section.

storm-control interface configuration command was changed for packet-based storm control. See the "storm-control" section.

duplex


Note This usage guideline is added to the ones in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


Beginning with Cisco IOS Release 12.1(22)EA1, you can configure the duplex setting when the speed is set to auto.

power inline


Note This usage guideline is added to the ones in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


When you configure a port by using the power inline auto interface configuration command, the port autonegotiates by using the configured speed and duplex settings to determine the power requirements of the connected device (whether or not it is a powered device. After the power requirements are determined, the switch hardcodes the interface by using the configured speed and duplex settings without resetting the interface.

When you configure a port by using the power inline never command, the command disables the detection and power for the inline-power-capable port, the port reverts to the configured speed and duplex settings.

show interfaces


Note The information in this section is added to the show interfaces command in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


Use the show interfaces privileged EXEC command to display the administrative and operational status of all interfaces or a specified interface.

show interfaces [interface-id | vlan vlan-id] [accounting | capabilities [module {module-number}] description | etherchannel | flowcontrol | pruning | stats | status [err-disabled] | switchport | trunk] | [transceiver properties] | [ | {begin | exclude | include} expression]

Syntax Description

transceiver properties

(Optional) Display speed, duplex, and inline power settings of an interface.


Command History

Release
Modification

12.1(4)EA1

This command was introduced.

12.1(12c)EA1

The capabilities keyword was added.

12.1(22)EA1

The transceiver and properties keywords were added.


Examples

This is an example of output from the show interfaces transceiver properties command. If you do not specify an interface, the output of the command shows the status on all switch ports:

Switch# show interfaces transceiver properties
Name : Fa0/1
Administrative Speed: auto 10 100
Administrative Duplex: auto
Administrative Auto-MDIX: N/A 
Administrative Power Inline: enable
Operational Speed: 100
Operational Duplex: full
Operational Auto-MDIX: N/A 

Name : Fa0/2
Administrative Speed: auto 10 
Administrative Duplex: auto
Administrative Auto-MDIX: N/A 
Administrative Power Inline: enable
Operational Speed: auto
Operational Duplex: auto
Operational Auto-MDIX: N/A 

Name : Fa0/3
Administrative Speed: auto
Administrative Duplex: auto
Administrative Auto-MDIX: N/A 
Administrative Power Inline: enable
Operational Speed: 100
Operational Duplex: auto
Operational Auto-MDIX: auto
<output truncated> 

This is an example of output from the show interfaces module number transceiver properties command for a specific interface:

Switch# show interfaces fastethernet0/1 transceiver properties
Name : Fa0/1
Administrative Speed: auto
Administrative Duplex: auto
Administrative Auto-MDIX: N/A
Administrative Power Inline: disable
Operational Speed: 100
Operational Duplex: full

Operational Auto-MDIX: N/A

show storm-control


Note These examples replace the ones in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


Examples

This is an example of output from the show storm-control command. Because no traffic type keyword was entered, the broadcast storm control settings appear.

Switch> show storm-control
Interface  Filter State   Upper       Lower      Current
---------  -------------  ----------  ---------  ---------
Fa0/1      Forwarding     20 pps      10 pps     5 pps
Fa0/2      Forwarding     50.00%      40.00%     0.00%
<output truncated>

This is an example of output from the show storm-control command for a specified interface. Because no traffic type keyword was entered, the broadcast storm control settings appear.

Switch> show storm-control fastethernet0/1
Interface  Filter State   Upper       Lower      Current
---------  -------------  ----------  ---------  ---------
Fa0/1      Forwarding     20 pps      10 pps     5 pps

This is an example of output from the show storm-control command for a specified interface and traffic type when no storm control threshold has been set for that traffic type on the specified interface:

Switch> show storm-control fastethernet0/1 multicast
Interface  Filter State   Upper       Lower      Current
---------  -------------  ----------  ---------  ---------
Fa0/1      inactive       100.00%     100.00%    N/A

speed


Note This command replaces the one in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


Use the speed interface configuration command to specify the speed of a 10/100 Mbps or 10/100/1000 Mbps port. Use the no or default form of this command to return the port to its default value.

speed {10 | 100 | 1000 | auto [10 | 100 | 1000] | nonegotiate}

no speed


Note You cannot configure speed or duplex mode on Gigabit Interface Converter (GBIC) ports, but for certain types of GBICs, you can configure speed to not negotiate (nonegotiate) if they are connected to a device that does not support autonegotiation.


Syntax Description

10

Port runs at 10 Mbps.

100

Port runs at 100 Mbps.

1000

Port runs at 1000 Mbps. This option is valid and visible only on Gigabit Ethernet (Tx) ports.

auto

Port automatically detects the speed it should run at based on the port at the other end of the link. If you use the 10, 100, or 1000 keywords with the auto keyword, the port only autonegotiates at the specified speeds.

nonegotiate

Autonegotiation is disabled and the port runs at 1000 Mbps. This option is valid and visible only on 1000BASE-SX, -LX, and -ZX GBIC ports. Gigastack GBICs and 1000BASE-T GBICs do not support disabling of autonegotiation.


Defaults

The default is auto.

Command Modes

Interface configuration

Command History

Release
Modification

12.1(4)EA1

This command was introduced.

12.1(6)EA1

The 1000 and nonegotiate keywords were added.

12.1(22)EA1

Support for the 10, 100, and 1000 keywords with the auto keyword was added.


Usage Guidelines

You can configure Fast Ethernet port speed to either 10 or 100 Mbps. You can configure Gigabit Ethernet port speed to 10, 100, or 1000 Mbps. You cannot configure speed on Gigabit Interface Converter (GBIC) interfaces, but for 1000BASE-SX, -LX, or -ZX GBICs, you can configure speed to not negotiate (nonegotiate) if connected to a device that does not support autonegotiation.

If the speed is set to auto, the switch negotiates with the device at the other end of the link for the speed setting and then forces the speed setting to the negotiated value. The duplex setting remains as configured on each end of the link, which could result in a duplex setting mismatch.

If the speed is set to auto and the 10, 100, or 1000 keywords are also used, the port only autonegotiates at the specified speeds.

If both ends of the line support autonegotiation, we highly recommend the default autonegotiation settings. If one interface supports autonegotiation and the other end does not, configure duplex and speed on both interfaces; do use the auto setting on the supported side.

If both the speed and duplex are set to specific values, autonegotiation is disabled.


Caution Changing the interface speed and duplex mode configuration might shut down and re-enable the interface during the reconfiguration.


Note For guidelines on setting the switch speed and duplex parameters, refer to the software configuration guide for this release.


Examples

This example shows how to set the specified interface to 100 Mbps:

Switch(config)# interface fastethernet0/1
Switch(config-if)# speed 100

This example shows how to set a port to autonegotiate at only 10 Mbps:

Switch(config)# interface fastethernet0/1
Switch(config-if)# speed auto 10

This example shows how to set a port to autonegotiate at only 10 or 100 Mbps:

Switch(config)# interface fastethernet0/1
Switch(config-if)# speed auto 10 100

You can verify your settings by entering the show interfaces transceiver properties or the show running-config privileged EXEC command.


You can verify your settings by entering the show interfaces privileged EXEC command.

Related Commands

Command
Description

duplex

Specifies the duplex mode of operation for Fast Ethernet and Gigabit Ethernet ports.

show interfaces

Displays the statistical information specific to all interfaces or to a specific interface



storm-control


Note This command replaces the one in the Catalyst 3550 Multilayer Switch Command Reference, Cisco IOS Release 12.1(20)EA2.


Use the storm-control interface configuration command to configure broadcast, multicast, or unicast storm control with a specific suppression-level threshold on an interface. Use the no form of this command to return to the default setting.

storm-control {broadcast | multicast | unicast} level {level [level-low] | pps pps pps-low}

no storm-control {broadcast | multicast | unicast} level

Syntax Description

broadcast

Enable broadcast storm control on the interface.

multicast

Enable multicast storm control on the interface.

unicast

Enable unicast storm control on the interface.

level level [level-low]

Specify the rising and falling suppression levels as a percentage of total bandwidth of the port.

level—Rising suppression level, up to two decimal places. The range is 0 to 100 percent. Block the flooding of storm packets when the value specified for level is reached.

level-low—(Optional) Falling suppression level, up to two decimal places. The range is 0 to 100. This value must be less than or equal to the rising suppression value. If you do not configure a falling suppression level, it is set to the rising suppression level.

level pps pps pps-low

Specify the rising and falling suppression levels as a rate in packets per second at which traffic is received on the port.

pps—Rising suppression level in packets per second. The range is 0 to 4294967295. Block the flooding of storm packets when the value specified for pps is reached.

pps-low—Falling suppression level in packets per second. The range is 0 to 4294967295. This value must be equal to or less than the rising suppression value.


Defaults

Broadcast, multicast, and unicast storm control are disabled.

Command Modes

Interface configuration

Command History

Release
Modification

12.1(8)EA1

This command was introduced. It replaces the switchport broadcast, switchport multicast, and switchport unicast interface configuration commands.

12.1(22)EA1

The level level [.level] option was replaced with the level level [level-low] option. The pps pps pps-low options were added.


Usage Guidelines

Storm control is supported only on physical interfaces; it is not supported on EtherChannel port channels, even though it is available in the CLI.

The storm-control suppression level can be entered as a percentage of total bandwidth or as a rate in packets per second at which traffic is received.

When specified as a percentage of total bandwidth, a suppression value of 100 percent means that no limit is placed on the specified traffic type. A value of level 0 0 means that all broadcast, multicast, or unicast traffic on that port is blocked. Storm control is enabled only when the rising suppression level is less than 100 percent.

When specified in packets per second, a suppression value of 4294967295 packets per second means that no limit is placed on the specified traffic type. This feature is enabled only when the rising suppression level is less than 4294967295 packets per second.

If the falling suppression level is not specified, the port blocks all traffic until the traffic rate drops below the rising suppression level. If the falling suppression level is specified, the port blocks traffic until the traffic rate drops below this level.


Note If a multicast storm control suppression level is exceeded on a switch, all traffic (multicast, unicast, and broadcast) is blocked until the multicast traffic rate drops below the threshold. Only spanning-tree packets are passed. If the broadcast or the unicast storm control suppression level is exceeded, only that type of traffic is blocked until the rate drops below the threshold.


For more information about storm-control suppression levels, refer to the software configuration guide for this release.

Examples

This example shows how to enable broadcast storm control with a 75.5-percent rising suppression level:

Switch(config-if)# storm-control broadcast level 75.5

This example shows how to enable unicast storm control on a port with a 87 percent rising suppression level and a 65-percent falling suppression level:

Switch(config-if)# storm-control unicast level 87 65

This example shows how to enable multicast storm control on a port with a 2000-packets-per-second rising suppression level and a 1000-packets-per-second falling suppression level:

Switch(config-if)# storm-control multicast level pps 2000 1000

You can verify your settings by entering the show storm-control privileged EXEC command.

Related Commands

Command
Description

show storm-control

Displays broadcast, multicast, or unicast storm-control settings on all interfaces or on a specified interface.


Corrections to the Catalyst 3550 Multilayer Switch Software Configuration Guide

These corrections apply to printed copies of the software configuration guide in the indicated chapters.

Chapter 3, Getting Started with CMS

The URL listed in the "Privilege Levels" section is incorrect.

The section lists this URL:

http://ip_address/level/13

This is the correct URL (the closing "/" is required):

http://ip_address/level/13/

Chapter 29, Configuring QoS

In the "Classifying Traffic by Using ACLs" section, this information in Step 3 to create a Layer 2 MAC ACL is incorrect:

For src-MAC-addr, enter the MAC address of the host from which the packet is being sent. You specify this by using the hexadecimal format (H.H.H), by using the any keyword as an abbreviation for source 0.0.0, source-wildcard 255.255.255, or by using the host keyword for source 0.0.0.

For dst-MAC-addr, enter the MAC address of the host to which the packet is being sent. You specify this by using the hexadecimal format (H.H.H), by using the any keyword as an abbreviation for source 0.0.0, source-wildcard 255.255.255, or by using the host keyword for source 0.0.0.

This is the correct information:

For src-MAC-addr, enter the MAC address of the host from which the packet is being sent. You specify this by using the hexadecimal format (H.H.H), by using the any keyword as an abbreviation for source 0.0.0, source-wildcard ffff.ffff.ffff, or by using the host keyword for source 0.0.0.

For dst-MAC-addr, enter the MAC address of the host to which the packet is being sent. You specify this by using the hexadecimal format (H.H.H), by using the any keyword as an abbreviation for source 0.0.0, source-wildcard ffff.ffff.ffff, or by using the host keyword for source 0.0.0.

Changes to the Catalyst 3550 Multilayer Switch System Message Guide

These messages were added to Cisco IOS Release 12.1(22)EA1:

Error Message    DTP-5-DOMAINMISMATCH: Unable to perform trunk negotiation on port 
[chars] because of VTP domain mismatch. 

Explanation    This message means that the two ports involved in trunk negotiation belong to different VTP domains. Trunking is possible only when the ports involved belong to the same VTP domain. [chars] is the name of the interface.

Recommended Action    Ensure that the two ports that are involved in trunk negotiation belong to the same VTP domain.

Error Message    ETHCNTR-3-HALF_DUX_COLISION_EXCEED_THRESHOLD: Collision at [chars] 
exceed threshold. Consider as loop-back.

Explanation    This message means that the collision at a half-duplex port exceeded the threshold, and the port is considered to be in the loop-back state. On switches that support Power over Ethernet (PoE), this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded.

Recommended Action    On switches that support PoE, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands. No action is required on non-PoE switches. The port goes into error-disabled mode until the problem is resolved.

Error Message    ETHCNTR-3-LOOP_BACK_DETECTED:, Loop-back detected on [chars]. The port 
is forced to linkdown.

Explanation    This message means that a loopback condition might be the result of a balun cable incorrectly connected into a port. On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port.

Recommended Action    On non-PoE switches, check the cables. If a balun cable is connected and the loopback condition is desired, no action is required. Otherwise, connect the correct cable, and then enable the port up by entering the no shutdown interface configuration command. On PoE switches, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands.

Error Message    PM-4-ERR_DISABLE: [chars] error detected on [chars], putting [chars] 
in err-disable state.

Explanation    This message means that the port manager detected a misconfiguration or misbehavior and placed the interface in an error-disabled state. A recovery is attempted after the configured retry time (the default is 5 minutes). On PoE switches, this message might appear when a device that can be powered by either a PoE switch port or by AC power is not being powered by an external AC power source and is connected to a port that has been configured with the power inline never interface configuration command. [chars] is the port where the threshold was exceeded. The first [chars] is the error, and the second and third [chars] are the affected interfaces.

Recommended Action    On non-PoE switches, copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Enter the show tech-support user EXEC command to gather data that might help identify the nature of the error. Use the Bug Toolkit to look for similar reported problems. On PoE switches, remove the device or configure the port by entering the power inline auto, the shutdown, and the no shutdown interface configuration commands. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about the online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in Chapter 1 of the system message guide.

Error Message    SW_VLAN-4-VTP_SEM_BUSY: VTP semaphore is unavailable for function 
[chars]. Semaphore locked by [chars].

Explanation    This message means that the VTP database is currently locked by another task and is not available. Retry the operation later. [chars] is the name of the function that has locked the VTP database.

Recommended Action    Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section in Chapter 1 of the Catalyst 3550 Multilayer Switch System Message Guide.

Related Documentation

These documents provide complete information about the switch and are available from this Cisco.com site:

http://www.cisco.com/univercd/cc/td/doc/product/lan/c3550/index.htm

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.

Catalyst 3550 Multilayer Switch Software Configuration Guide (order number DOC-7811194=)

Catalyst 3550 Multilayer Switch Command Reference (order number DOC-7811195=)

Catalyst 3550 Multilayer Switch System Message Guide (order number DOC-7811196=)

Cluster Management Suite (CMS) online help (available only from the switch CMS software)

Catalyst 3550 Multilayer Switch Hardware Installation Guide (order number DOC-7811358=)

1000BASE-T Gigabit Interface Converter Installation Note (not orderable but is available on Cisco.com)

Catalyst GigaStack Gigabit Interface Converter Hardware Installation Guide (order number DOC-786460=)

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain 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 at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

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 Ordering tool:

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 send comments about technical documentation 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-9883

We appreciate your comments.

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool automatically provides recommended solutions. If your issue is not resolved using the recommended resources, your service request will be assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request 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 2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—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.

Severity 2 (S2)—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.

Severity 3 (S3)—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.

Severity 4 (S4)—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.

Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

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://cisco.com/univercd/cc/td/doc/pcat/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. 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/ipj

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html