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

Hierarchical Navigation

Cisco Catalyst 3750-E Series Switches

Release Notes for Catalyst 3750-E and Catalyst 3560-E Switches, Cisco IOS Release 12.2(37)SE and Later

Downloads

Table Of Contents

Release Notes for Catalyst 3750-E
and Catalyst 3560-E Switches, Cisco IOS Release 12.2(37)SE and Later

Contents

System Requirements

Hardware Supported

Device Manager System Requirements

Hardware Requirements

Software Requirements

Cluster Compatibility

CNA Compatibility

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch by Using the Device Manager or Network Assistant

Upgrading a Switch by Using the CLI

Recovering from a Software Failure

Installation Notes

New Features

New Hardware Features

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Cisco IOS Limitations

Access Control List

Cisco Redundant Power System 2300

Cisco X2 Transceiver Modules and SFP Modules

Configuration

EtherChannel

IEEE 802.1x Authentication

Multicasting

PoE

QoS

Routing

SPAN and RSPAN

Stacking (only Catalyst 3750-E Switch Stack)

Device Manager Limitations

Important Notes

Switch Stack Notes

Cisco IOS Notes

Device Manager Notes

Open Caveats

Resolved Caveats

Caveats Resolved in Cisco IOS Release 12.2(37)SE1

Caveats Resolved in Cisco IOS Release 12.2(37)SE

Documentation Updates

Updates for the Catalyst 3750-E and 3560-E Switch Software Configuration Guides

Web Authentication with Automatic MAC Check

Updates to the Catalyst 3750-E and 3560-E Switch Command Reference

ip arp inspection validate

ip arp inspection vlan logging

show ip arp inspection

Updates for the Catalyst 3750-E and 3560-E Switch Getting Started Guides

Updates for the Regulatory Compliance and Safety Information for
Catalyst 3750-E and 3560-E Switches

Regulatory Standards Compliance

Cautions and Regulatory Compliance Statements for NEBS

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Catalyst 3750-E
and Catalyst 3560-E Switches, Cisco IOS Release 12.2(37)SE and Later

Revised August 8, 2007

Cisco IOS Release 12.2(37)SE runs on all Catalyst 3750-E and Catalyst 3560-E switches.

The Catalyst 3750-E switches support stacking through Cisco StackWise Plus technology. The Catalyst 3560-E switches do not support switch stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.

These release notes include important information about Cisco IOS Release 12.2(37)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:

•If you are installing a new switch, see 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, see the software upgrade filename for the software version. See the "Deciding Which Files to Use" section.

You can download the switch software from this site (registered Cisco.com users with a login password):

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

This software release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.

For the complete list of Catalyst 3750-E and Catalyst 3560-E switch documentation, see the "Related Documentation" section.

Contents

This information is in the release notes:

•"System Requirements" section

•"Upgrading the Switch Software" section

•"Installation Notes" section

•"New Features" section

•"Minimum Cisco IOS Release for Major Features" section

•"Limitations and Restrictions" section

•"Important Notes" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Documentation Updates" section

•"Related Documentation" section

•"Obtaining Documentation, Obtaining Support, and Security Guidelines" section

System Requirements

The system requirements are described in these sections:

•"Hardware Supported" section

•"Device Manager System Requirements" section

•"Cluster Compatibility" section

•"CNA Compatibility" section

Hardware Supported

Table 1 lists the hardware supported on this release.

Table 1 Catalyst 3750-E and Catalyst 3560-E Switches Supported Hardware 

Switch Hardware
Description
Supported by Minimum Cisco IOS Release

Cisco Catalyst 3750E-24TD

24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3750E-48TD

48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3750E-24PD

24 10/100/1000 PoE1 ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3750E-48PD

48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3750E-48PD
Full Power

48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3560E-24TD

24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3560E-48TD

48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3560E-24PD

24 10/100/1000 PoE ports, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3560E-48PD

48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco Catalyst 3560E-48PD
Full Power

48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(35)SE2

Cisco X2 transceiver modules

X2-10GB-SR V02 or later
X2-10GB-LR V03 or later
X2-10GB-ER V02 or later
X2-10GB-CX4 V03 or later
X2-10GB-LX4 V03 or later

Cisco IOS Release 12.2(35)SE2

Cisco TwinGig Converter Module

Dual SFP2 X2 converter module to allow the switch to support SFP Gigabit Ethernet modules

Cisco IOS Release 12.2(35)SE2

SFP modules

1000BASE-LX/LH
1000BASE-SX
1000BASE-ZX
1000BASE-BX10-D
1000BASE-BX10-U
1000BASE-T
100BASE-FX
CWDM3

Cisco IOS Release 12.2(35)SE2

SFP module patch cable4

CAB-SFP-50CM

Cisco IOS Release 12.2(35)SE2

C3K-PWR-1150WAC

1150-W AC power supply module for PoE-capable switches

Supported on all software releases

C3K-PWR-750WAC

750-W AC power supply module for PoE-capable switches

Supported on all software releases

C3K-PWR-265WAC

265-W AC power supply module for nonPoE-capable switches

Supported on all software releases

C3K-PWR-265WDC

265-W DC power supply module for nonPoE-capable switches

Supported on all software releases

C3K-BLWR-60CFM

Fan module

Supported on all software releases

Redundant power system (RPS)

Cisco RPS 2300 RPS

Supported on all software releases

1 PoE = Power over Ethernet.

2 SFP = small form-factor pluggable

3 CWDM = coarse wavelength-division multiplexer

4 Only Catalyst 3560-E switches. The SFP module patch cable is a 0.5-meter, copper, passive cable with SFP module connectors at each end. The patch cable can connect two Catalyst 3560-E switches in a cascaded configuration.


Device Manager System Requirements

These sections describe the hardware and software requirements for using the device manager:

•"Hardware Requirements" section

•"Software Requirements" section

Hardware Requirements

Table 2 lists the minimum hardware requirements for running the device manager.

Table 2 Minimum Hardware Requirements 

Processor Speed
DRAM
Number of Colors
Resolution
Font Size

Intel Pentium II1

64 MB2

256

1024 x 768

Small

1 We recommend Intel Pentium 4.

2 We recommend 256-MB DRAM.


Software Requirements

Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.

Note The device manager does not require a plug-in.

Table 3 Supported Operating Systems and Browsers 

Operating System
Minimum Service Pack or Patch
Microsoft Internet Explorer1
Netscape Navigator

Windows 2000

None

5.5 or 6.0

7.1

Windows XP

None

5.5 or 6.0

7.1

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


Cluster Compatibility

You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.

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.

•If you are managing the cluster through Network Assistant, the switch with the latest software should be the command switch.

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

For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.

CNA Compatibility

Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Network Assistant from this URL:

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

For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.

Upgrading the Switch Software

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

•Finding the Software Version and Feature Set

•Deciding Which Files to Use

•Upgrading a Switch by Using the Device Manager or Network Assistant

•Upgrading a Switch by Using the CLI

•Recovering from a Software Failure

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 of the display shows the version.

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

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 the Cisco IOS image file and the files needed for the embedded device manager. You must use the combined tar file to upgrade the switch through the device manager. To upgrade the switch through the command-line interface (CLI), use the tar file and the archive download-sw privileged EXEC command.

Table 4 lists the filenames for this software release.

Note For IPv6 routing and IPv6 ACL capability on the Catalyst 3750-E or 3560-E switch, you must get the advanced IP services software license from Cisco.

Table 4 Cisco IOS Software Image Files 

Filename

Description

c3750e-universal-tar.122-37.SE.tar

Catalyst 3750-E universal image and device manager files. This image has all the supported features that are enabled by the software license installed on the switch.

c3750e-universalk9-tar.122-37.SE.tar

Catalyst 3750-E universal cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, and SNMPv3 in addition to the features supported in the universal image.

c3560e-universal-tar.122-37.SE.tar

Catalyst 3560-E universal image and device manager files. This image has all the supported features that are enabled by the software license installed on the switch.

c3560e-universalk9-tar.122-37.SE.tar

Catalyst 3560-E universal cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, and SNMPv3 in addition to the features supported in the universal image.


The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set. For information about software activation, see the Cisco Software Activation and Compatibility Document on Cisco.com:

http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html

Archiving Software Images

Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.

Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:

http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html

You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.

Note Although you can copy any file on the flash memory to the TFTP server, it is time-consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.

You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the "Basic File Transfer Services Commands" section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2, at this URL:

http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_book09186a00800811e0.html

Upgrading a Switch by Using the Device Manager or Network Assistant

You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.

Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.

Upgrading a Switch by Using the CLI

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

To download software, follow these steps:

Step 1 Use Table 4 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/public/sw-center/sw-lan.shtml

To download the universal software image files for a Catalyst 3750-E switch, click Catalyst 3750-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750-E 3DES Cryptographic Software.

To download the universal software image files for a Catalyst 3560-E switch, click Catalyst 3560-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560-E 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, see Appendix B in the software configuration guide for this release.

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

Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command: 

Switch# ping tftp-server-address

For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.

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 entering this privileged EXEC command: 

Switch# 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 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/c3750e-universal-tar.122-35.SE2.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.

Recovering from a Software Failure

For additional recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.

Installation Notes

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

•The Express Setup program, as described in the switch getting started guide.

•The CLI-based setup program, as described in the switch hardware installation guide.

•The DHCP-based autoconfiguration, as described in the switch software configuration guide.

•Manually assigning an IP address, as described in the switch software configuration guide.

New Features

These sections describe the new supported hardware and the new and updated software features provided in this release:

•"New Hardware Features" section

•"New Software Features" section

New Hardware Features

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

New Software Features

These are the new software features for this release:

•DHCP Snooping Statistics show and clear commands to display and remove DHCP snooping statistics in summary or detail form

•IP phone detection enhancement to detect and recognize a Cisco IP phone

•IP unicast reverse path forwarding (unicast RPF) for confirming source packet IP addresses

•Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED) for interoperability with third-party IP phones

•PIM stub routing to reduce resource usage by moving routed traffic closer to the end user

•Port security on a PVLAN host to limit the number of MAC addresses learned on a port, or to define which MAC addresses can be learned on a port

•VLAN aware port security option to shut down the VLAN on the port when a violation occurs, instead of shutting down the entire port

•Support for auto-rendezvous point (auto-RP) for multicast, which uses IP multicast to automate the distribution of group-to-RP mappings to all Cisco routers and multilayer switches in a PIM network

•VLAN Flex Link Load Balancing to provide Layer 2 redundancy without requiring Spanning Tree Protocol (STP). A pair of interfaces configured as primary and backup links can load balance traffic based on VLAN

•Web Cache Communication Protocol (WCCP) for redirecting traffic to wide-area application engines, for enabling content requests to be fulfilled locally, and for localizing web-traffic patterns in the network (requires the IP services image)

•SNMP support for the Port Error Disable MIB

•Support for the Time Domain Reflectometry MIB

Minimum Cisco IOS Release for Major Features

Table 5 lists the minimum software release (after the first release) required to support the major features of the Catalyst 3750-E and Catalyst 3560-E switches. Features not listed are supported in all releases.

Table 5 Features Introduced After the First Release and the Minimum Cisco IOS Release Required 

Feature
Minimum Cisco IOS Release Required
Catalyst Switch Support

DHCP Snooping Statistics show and clear commands

12.2(37)SE

3750-E, 3560-E

IP phone detection enhancement

12.2(37)SE

3750-E, 3560-E

IP unicast reverse path forwarding (unicast RPF)

12.2(37)SE

3750-E, 3560-E

Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED)

12.2(37)SE

3750-E, 3560-E

PIM stub routing in the IP base image

12.2(37)SE

3750-E, 3560-E

Port security on a PVLAN host

12.2(37)SE

3750-E, 3560-E

VLAN aware port security option

12.2(37)SE

3750-E, 3560-E

Support for auto-rendezvous point (auto-RP) for IP multicast

12.2(37)SE

3750-E, 3560-E

VLAN Flex Link Load Balancing

12.2(37)SE

3750-E, 3560-E

Web Cache Communication Protocol (WCCP)

12.2(37)SE

3750-E, 3560-E

SNMP support for the Port Error Disable MIB

12.2(37)SE

3750-E, 3560-E

Support for the Time Domain Reflectometry MIB

12.2(37)SE

3750-E, 3560-E


Limitations and Restrictions

You should review this section before you begin working with the switch. 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.

This section contains these limitations:

•"Cisco IOS Limitations" section

•"Device Manager Limitations" section

Cisco IOS Limitations

Unless otherwise noted, these limitations apply to the Catalyst 3750-E and 3560-E switches:

•"Access Control List" section

•"Cisco Redundant Power System 2300" section

•"Cisco X2 Transceiver Modules and SFP Modules" section

•"Configuration" section

•"EtherChannel" section

•"IEEE 802.1x Authentication" section

•"Multicasting" section

•"PoE" section

•"QoS" section

•"Routing" section

•"SPAN and RSPAN" section

•"Stacking (only Catalyst 3750-E Switch Stack)" section

Access Control List

These are the access control list (ACL) limitations:

•The Catalyst 3750-E and Catalyst 3560-E switches have 964 TCAM entries available for ACLs in the default and routing SDM templates instead of the 1024 entries that are available on the Catalyst 3560 and Catalyst 3750 switches.

There is no workaround. (CSCse33114)

•When a MAC access list is used to block packets from a specific source MAC address, that MAC address is entered in the switch MAC-address table.

The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)

Cisco Redundant Power System 2300

This is the Cisco Redundant Power System (RPS) 2300 limitation:

•When connecting the RPS cable between the RPS 2300 and the Catalyst 3750-E or 3560-E switch or other supported network devices, this communication error might appear:

%PLATFORM_ENV-1-RPS_ACCESS: RPS is not responding

No workaround is required because the problem corrects itself. (CSCsf15170)

Cisco X2 Transceiver Modules and SFP Modules

These are the Cisco X2 transceiver module and SFP module limitations:

•Cisco X2-10GB-LR transceiver modules with a version identification number lower than V03 might show intermittent frame check sequence (FCS) errors or be ejected from the switch during periods of operational shock greater than 50g. There is no workaround. (CSCse14048)

•Cisco X2-10GB-CX4 transceiver modules with a version identification number lower than V03 might be difficult to insert because of a dimensional tolerance discrepancy. The workaround is to use modules with a version identification number of V03 or later. (CSCsg28558)

•Switches with the Cisco X2-10GB-LX4 transceiver modules with a version identification number prior to V03 might intermittently fail. The workaround is to use Cisco X2-10GB-LX4 transceiver modules with a version identification number of V03 or later. (CSCsh60076)

•Cisco GLC-GE-100FX SFP modules with a serial number between OPC0926xxxx and OPC0945xxxx might show intermittent module not valid, data, status, link-flapping, and FCS errors. The workaround is to use modules with serial numbers that are not in the specified range. (CSCsh59585)

•When switches are installed closely together and the uplink ports of adjacent switches are in use, you might have problems accessing the SFP module bale-clasp latch to remove the SFP module or the SFP cable (Ethernet or fiber). Use one of these workarounds:

–Allow space between the switches when installing them.

–In a switch stack, plan the SFP module and cable installation so that uplinks in adjacent stack members are not all in use.

–Use long, small screwdriver to access the latch then remove the SFP module and cable. (CSCsd57938)

•When a Cisco X2-10GB-CX4 transceiver module is in the X2 transceiver module port and you enter the show controllers ethernet-controller tengigabitethernet privileged EXEC command, the command displays some fields as unspecified. This is the expected behavior based IEEE 802.3ae. (CSCsd47344)

Configuration

These are the configuration limitations:

•When an excessive number (more than 100 packets per second) of Address Resolution Protocol (ARP) packets are sent to a Network Admission Control (NAC) Layer 2 IP-configured member port, a switch might display a message similar to this:

%PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323

-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8

No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)

•When there is a VLAN with protected ports configured in fallback bridge group, packets might not be forwarded between the protected ports.

The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)

EtherChannel

These are the EtherChannel limitations:

•In an EtherChannel running Link Aggregation Control Protocol (LACP), the ports might be put in the suspended or error-disabled state after a stack partitions or a member switch reloads. This occurs when

–The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.

–The switch stack partitions because a member reloads. The EtherChannel is divided between the two partitioned stacks, each with a stack master.

The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:

–Enable the switch to recover from the error-disabled state.

–Enter the shutdown and the no shutdown interface configuration commands to enable the port.

The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.

After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)

•When a switch stack is configured with a cross-stack EtherChannel, it might transmit duplicate packets across the EtherChannel when a physical port in the EtherChannel has a link-up or link-down event. This can occur for a few milliseconds while the switch stack adjusts the EtherChannel for the new set of active physical ports and can happen when the cross-stack EtherChannel is configured with either mode ON or LACP. This problem might not occur with all link-up or link-down events.

No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)

IEEE 802.1x Authentication

These are the IEEE 802.1x authentication limitations:

•If a supplicant using a Marvel Yukon network interface card (NIC) is connected an IEEE 802.1x-authorized port in multihost mode, the extra MAC address of 0c00.0000.0000 appears in the MAC address table.

Use one of these workarounds (CSCsd90495):

–Configure the port for single-host mode to prevent the extra MAC address from appearing in the MAC address table.

–Replace the NIC card with a new card.

•When MAC authentication bypass is configured to use Extensible Authentication Protocol (EAP) for authorization and critical authentication is configured to assign a critical port to an access VLAN:

–If the connected device is supposed to be unauthorized, the connected device might be authorized on the VLAN that is assigned to the critical port instead of to a guest VLAN.

–If the device is supposed to be authorized, it is authorized on the VLAN that is assigned to the critical port.

Use one of these workarounds (CSCse04534):

–Configure MAC authentication bypass to not use EAP.

–Define your network access profiles to not use MAC authentication bypass. For more information, see the Cisco Access Control Server (ACS) documentation.

•When IEEE 802.1x authentication with VLAN assignment is enabled, a CPUHOG message might appear if the switch is authenticating supplicants in a switch stack.

The workaround is not use the VLAN assignment option. (CSCse22791)

Multicasting

These are the multicasting limitations:

•Multicast packets with a time-to-live (TTL) value of 0 or 1 are flooded in the incoming VLAN when all of these conditions are met:

–Multicast routing is enabled in the VLAN.

–The source IP address of the packet belongs to the directly connected network.

–The TTL value is either 0 or 1.

The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)

•Multicast packets denied by the multicast boundary access list are flooded in the incoming VLAN when all of these conditions are met:

–Multicast routing is enabled in the VLAN.

–The source IP address of the multicast packet belongs to a directly connected network.

–The packet is denied by the IP multicast boundary access-list configured on the VLAN.

There is no workaround. (CSCei08359)

•Reverse path forwarding (RPF) failed multicast traffic might cause a flood of Protocol Independent Multicast (PIM) messages in the VLAN when a packet source IP address is not reachable.

The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)

•If the clear ip mroute privileged EXEC command is used when multicast packets are present, it might cause temporary flooding of incoming multicast traffic in the VLAN.

There is no workaround. (CSCsd45753)

•When you configure the ip igmp max-groups number and ip igmp max-groups action replace interface configuration commands and the number of reports exceed the configured max-groups value, the number of groups might temporarily exceed the configured max-groups value. No workaround is necessary because the problem corrects itself when the rate or number of IGMP reports are reduced. (CSCse27757)

•When you configure the IGMP snooping throttle limit by using the ip igmp max-groups number interface configuration on a port-channel interface, the groups learned on the port-channel might exceed the configured throttle limit number, when all of these conditions are true:

–The port-channel is configured with member ports across different switches in the stack.

–When one of the member switches reloads.

–The member switch that is reloading has a high rate of IP IGMP joins arriving on the port-channel member port.

The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)

PoE

These are the power-over-Ethernet (PoE) limitations:

•When a loopback cable is connected to a switch PoE port, the show interface status privileged EXEC command shows not connected, and the link remains down. When the same loopback cable is connected to a non-PoE port, the link becomes active and then transitions to the error-disabled state when the keepalive feature is enabled. There is no workaround. (CSCsd60647)

•The Cisco 7905 IP Phone is error-disabled when the phone is connected to an external power source.

The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)

•The pethPsePortShortCounter MIB object appears as short even though the powered device is powered on after it is connected to the PoE port.

There is no workaround. (CSCsg20629)

QoS

These are the quality of service (QoS) limitations:

•When QoS is enabled and the egress port receives pause frames at the line rate, the port cannot send packets.

There is no workaround. (CSCeh18677)

•Egress shaped round robin (SRR) sharing weights do not work properly with system jumbo MTU frames.

There is no workaround. (CSCsc63334)

•In a hierarchical policy map, if the VLAN-level policy map is attached to a VLAN interface and the name of the interface-level policy map is the same as that for another VLAN-level policy map, the switch rejects the configuration, and the VLAN-level policy map is removed from the interface.

The workaround is to use a different name for the interface-level policy map. (CSCsd84001)

•If the ingress queue has low buffer settings and the switch sends multiple data streams of system jumbo MTU frames at the same time at the line rate, the frames are dropped at the ingress.

There is no workaround. (CSCsd72001)

•When you use the srr-queue bandwidth limit interface configuration command to limit port bandwidth, packets that are less than 256 bytes can cause inaccurate port bandwidth readings. The accuracy is improved when the packet size is greater than 512 bytes. There is no workaround. (CSCsg79627)

Routing

These are the routing limitations:

•The switch stack might reload if the switch runs with this configuration for several hours, depleting the switch memory and causing the switch to fail:

–The switch has 400 Open Shortest Path First (OSPF) neighbors.

–The switch has thousands of OSPF routes.

The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)

•When the PBR is enabled and QoS is enabled with DSCP settings, the CPU utilization might be high if traffic is sent to unknown destinations.

The workaround is to not send traffic to unknown destinations. (CSCse97660)

SPAN and RSPAN

This is the SPAN and Remote SPAN (RSPAN) limitation.

•When egress SPAN is running on a 10-Gigabit Ethernet port, only about 12 percent of the egress traffic is monitored.

There is no workaround. This is a hardware limitation. (CSCei10129)

Stacking (only Catalyst 3750-E Switch Stack)

These are the Catalyst 3750-E switch stack limitations:

•Where there is a mixed hardware stack with Catalyst 3750-E and 3750 switches as stack members, when you change the configuration and enter the write memory privileged EXEC command, the unable to read config message appears.

The workaround is to wait a few seconds and then to reenter the write memory privileged EXEC command. (CSCsd66272)

•When using the logging console global configuration command, low-level messages appear on both the stack master and the stack member consoles.

The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)

•In a mixed stack which consists of Catalyst 3750 switches along with Catalyst 3750-E switches, when the stack ring is congested with approximately 40 Gb/s of traffic, some of the local traffic from one port to another on a Catalyst 3750-E member might be dropped.

The workaround is to avoid traffic congestion on the stack ring. (CSCsd87538)

•If a new member switch joins a switch stack within 30 seconds of a command to copy the switch configuration to the running configuration of the stack master, the new member might not get the latest running configuration and might not operate properly.

The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)

•When the flash memory of a stack member is almost full, it might take longer to start up than other member switches. This might cause that switch to miss the stack-master election window. As a result, the switch might fail to become the stack master even though it has the highest priority.

The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)

Device Manager Limitations

This is the device manager limitation:

•When you are prompted to accept the security certificate and you click No, you only see a blank screen, and the device manager does not launch.

The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)

Important Notes

These sections describe the important notes related to this software release for the Catalyst 3750-E and 3560-E switches:

•"Switch Stack Notes" section

•"Cisco IOS Notes" section

•"Device Manager Notes" section

Switch Stack Notes

These notes apply to switch stacks:

•Always power off a switch before adding or removing it from a switch stack.

•The Catalyst 3560-E switches do not support switch stacking. However, the show processes privileged EXEC command still lists stack-related processes. This occurs because these switches share common code with other switches that do support stacking.

•Catalyst 3750-E switches running Cisco IOS Release 12.2(35)SE2 are compatible with Catalyst 3750 switches and Cisco EtherSwitch service modules running Cisco IOS Release 12.2(35)SE. Catalyst 3750-E switches, Catalyst 3750 switches, and Cisco EtherSwitch service modules can be in the same switch stack. In this switch stack, we recommend that the Catalyst 3750-E switch be the stack master.

Cisco IOS Notes

This note applies to Cisco IOS software:

•If the switch requests information from the Cisco Secure Access Control Server (ACS) and the message exchange times out because the server does not respond, a message similar to this appears: 

00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not 
responding.

If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.

Device Manager Notes

These notes apply to the device manager:

•You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the CLI or Cisco Network Assistant.

•When the switch is running a localized version of the device manager, the switch displays settings and status only in English letters. Input entries on the switch can only be in English letters.

•For device manager session on Internet Explorer, popup messages in Japanese or in simplified Chinese can appear as garbled text. These messages appear properly if your operating system is in Japanese or Chinese.

•We recommend this browser setting to speed up the time needed to display the device manager from Microsoft Internet Explorer.

From Microsoft Internet Explorer:

1. Choose Tools > Internet Options.

2. Click Settings in the "Temporary Internet files" area.

3. From the Settings window, choose Automatically.

4. Click OK.

5. Click OK to exit the Internet Options window.

•The HTTP server interface must be enabled to display the device manager. By default, the HTTP server is enabled on the switch. Use the show running-config privileged EXEC command to see if the HTTP server is enabled or disabled.

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

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

ip http authentication {aaa | enable | local}

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

•aaa—Enable the authentication, authorization, and accounting feature. You must enter the aaa new-model interface configuration command for the aaa keyword to appear.

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

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

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show running-config

Verify your entries.

•The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.

If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.

If you are not using the default method of authentication (the enable password), you need to configure the HTTP server interface with the method of authentication used on the switch.

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

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

ip http authentication {enable | local | tacacs}

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

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

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

•tacacs—TACACS server is used.

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show running-config

Verify your entries.

•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:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch the device manager.

Open Caveats

This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the Catalyst 3750-E and 3560-E switches:

•CSCsb85001

If traffic is passing through VMPS ports and you perform a shut operation, a dynamic VLAN is not assigned, and a VLAN with a null ID appears.

The workaround is to clear the MAC address table. This forces the VMPS server to correctly reassign the VLAN.

•CSCse06827

The switch might place a port in an error-disabled state due to an Address Resolution Protocol (ARP) rate limit exception even when the ARP traffic on the port is not exceeding the configured limit. This could happen when the burst interval setting is 1 second, the default.

The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.

•CSCse51203

When the dynamic ARP inspection trust setting is removed from a large number of ports across multiple members of a stack, a %PLATFORM_RPC-3-MSG_THROTTLED message might appear.

The workaround is to remove the trust settings on a small number of ports, one switch at a time. If the problem still occurs, continue to reduce the number of ports.

•CSCse88619

The error message %HPSECURE-6-ADDR_REMOVED might appear in a switch stack under these conditions:

–Port security is enabled on at least one port.

–Some secure addresses exist in the switch state.

–A new member joins a switch stack.

There is no workaround.

•CSCsf32504

When there are more than five switches in a stack or when four or more switches join a stack, there might be a long delay between the time the Ready prompt appears and a switch that is starting up begins carrying traffic. This delay can last several minutes.

There is no workaround. However, this condition only causes a delay during switch startup, and no data is lost.

•CSCsf98557

When the domain is authorized in the guest VLAN on a member switch port without link loss and an Extensible Authentication Protocol over LAN (EAPOL) is sent to an IEEE 802.1x supplicant to authenticate, the authentication fails. This problem happens intermittently with certain stacking configurations and only occurs on the member switches.

The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status.

•CSCsg21537

When MAC addresses are learned on an EtherChannel port, the addresses are incorrectly deleted from the MAC address table even when the MAC address table aging timeout value is configured to be longer than the ARP timeout value. This causes intermittent unicast packet flooding in the network.

The MAC address is automatically relearned after the ARP refresh. The workaround is to enter the ping ip address privileged EXEC command from the switch to the next hop router to avoid the intermittent flooding.

•CSCsg58889

If IEEE 802.1Q tunneling and Layer 2 protocol tunneling are configured first on physical ports, and the ports are then added to an unconfigured port channel, the port channel might stop forwarding traffic if one or more physical ports in the EtherChannel are shut down.

These are the workarounds:

–Remove and reapply the Layer 2 protocol tunneling configuration on the port channel.

–Configure the port channel first, next configure the physical ports, and then add them to the port channel.

•CSCsg62919

Clearing secure addresses by entering the clear port-security global configuration command in a stack member might cause traffic to be dropped from the switch. Some secure addresses learned on the stack master might not be learned on a stack member. Packets with a secure source address might also be dropped.

These are the workarounds. You only need to do one of these:

–Enter the clear port-security global configuration command to stop the traffic.

–Enter the shut and no shut interface configuration commands on the port where the traffic is being dropped.

•CSCsg67684

When a cross-stack LACP EtherChannel has a maximum configuration, such as eight active and eight hot-standby ports, and there are multiple rapid sequential master failovers and stack rejoins that cause extreme stress, it is possible that the port channel will not function as expected. Some ports might not join the EtherChannel, and traffic might be lost. You can detect the condition by using the remote command all show etherchannel summary privileged EXEC command.

There is no workaround. The out-of-sync switches must be reloaded.

•CSCsg70039

When both an authorized data domain and an authorized voice domain is present on a port, and you change the VLAN configuration on the port to equal the assigned VLAN, a traceback error appears. This problem only occurs on the ports of a member switch.

The workaround is to change the voice VLAN to a value that does not match the assigned VLAN or VLAN feature (such as a guest VLAN).

•CSCsg77818

When a switch interface is configured with trust boundary and Cisco Discovery Protocol (CDP) or the CDP table is repeatedly disabled, enabled, or cleared, the switch might reload.

The workaround is to avoid repeatedly disabling, enabling, or clearing CDP or the CDP table when trust boundary is configured on an interface. Or, disable trust boundary first before repeatedly disabling, enabling, or clearing CDP or the CDP table.

•CSCsg79506

When a RADIUS server is unstable, the switch memory might be depleted when the switch repeatedly reauthenticates supplicants.

The workaround is to stabilize the RADIUS server.

•CSCsg81185

When a device is attached to a multidomain authentication (MDA)- enabled port that has IEEE 802.1x guest VLAN configured but not MAC authentication bypass (MAB), if the switch gets its MAC address from that port, the device is authenticated in the guest VLAN but appears as an IEEE 802.1x-authenticated device.

The workaround is to enable MAB by entering the dot1x mac-auth-bypass interface configuration command, or to enter the dot1x timeout tx-period 1 to set the IEEE 802.1x timeout period to 1 second.

•CSCsh04301

When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in one direction until the port traffic is stopped and then restarted. You can detect the condition by using the show controller ethernet-controller or the show interfaces privileged EXEC commands.

The workaround is to stop the traffic in the direction in which it is not being forwarded, and then restart it after 2 seconds. You can also use the shutdown interface configuration command followed by the no shutdown command on the interface.

•CSCsh12472

The switch might display tracebacks similar to this example when an EtherChannel interface port-channel type changes from Layer 2 to Layer 3 or the reverse:

15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58

There is no workaround.

•CSCsh70377

When a secondary VLAN is disassociated from the primary VLAN, duplicate MAC addresses on the primary VLAN remain in the MAC address table.

The workaround is to