Guest

Cisco Catalyst 3750-E Series Switches

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

  • Viewing Options

  • PDF (472.0 KB)
  • Feedback
Release Notes for Catalyst 3750-E and Catalyst 3560-E Switches, Cisco IOS Release 12.2(44)SE and Later

Table Of Contents

Release Notes for Catalyst 3750-E
and Catalyst 3560-E Switches, Cisco IOS Release 12.2(44)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

Address Resolution Protocol

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

VLANs

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

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750-E Switches Only)

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE

Documentation Updates

Updates to the Software Configuration Guide

Understanding Embedded Event Manager

Event Detectors

Embedded Event Manager Actions

Embedded Event Manager Policies

Embedded Event Manager Environment Variables

Configuring Embedded Event Manager

Registering and Defining an Embedded Event Manager Applet

Registering and Defining an Embedded Event Manager TCL Script

Displaying Embedded Event Manager Information

Updates to the Command Reference

power inline

Updates to the System Message Guide

Updates to the Getting Started Guides

Updates to the Hardware Installation Guide

Updates to the Regulatory Compliance and Safety Information

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(44)SE and Later


Revised September 9, 2009

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


Note Cisco IOS Release 12.2(44)SE4 only runs on the Catalyst 3750-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(44)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://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches

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" sectionOL-14629-07

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 Catalyst 3560E-12D

12 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(40)EX

Cisco Catalyst 3560E-12SD

12 SFP2 module slots, 2 10-Gigabit Ethernet X2 module slots

Cisco IOS Release 12.2(44)SE

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

X2-10GB-LRM

Cisco IOS Release 12.2(35)SE2





Cisco IOS Release 12.2(40)SE

Cisco TwinGig Converter Module

Dual SFP 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

233 MHz minimum1

512 MB2

256

1024 x 768

Small

1 We recommend 1 GHz.

2 We recommend 1 GB 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 Explorer 1
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" section

"Deciding Which Files to Use" section

"Upgrading a Switch by Using the Device Manager or Network Assistant" section

"Upgrading a Switch by Using the CLI" section

"Recovering from a Software Failure" section

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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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/kobayashi/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-44.SE.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-based autoconfiguration and image update to download a specified configuration and image to a large number of switches

Configurable small-frame arrival threshold to prevent storm control when small frames (64 bytes or less) arrive on an interface at a specified rate (the threshold)

Digital optical monitoring (DOM) to check the status of X2 small form-factor pluggable (SFP) modules

Source Specific Multicast (SSM) mapping for multicast applications to provide a mapping of source IGMPv2 clients to utilize SSM, allowing listeners to connect to multicast sources dynamically and reducing dependencies on the application

Support for the *, ip-address, interface interface-id, and vlan vlan-id keywords with the clear ip dhcp snooping command

HTTP and HTTP(s) support over IPv6, which eliminates the need to run dual stack on the switch

Simple Network and Management Protocol (SNMP) configuration over IPv6 transport so that an IPv6 host can send SNMP queries and receive SNMP notifications from a device running IPv6

IPv6 support for stateless autoconfiguration to manage link, subnet, and site addressing changes, such as management of host and mobile IP addresses

Flex Link Multicast Fast Convergence to reduces the multicast traffic convergence time after a Flex Link failure

IEEE 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802.1x on the switch

Flow-based Switch Port Analyzer (FSPAN) to define filters for capturing traffic for analysis

Support for /31 bit masks for multicast traffic

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-based autoconfiguration and image update

12.2(44)SE

3750-E, 3560-E

Configurable small-frame arrival threshold

12.2(44)SE

3750-E, 3560-E

Digital optical monitoring (DOM)

12.2(44)SE

3750-E, 3560-E

Embedded event manager (EEM) for device and system management
(IP service image only)

12.2(40)SE

3750-E, 3560-E

Source Specific Multicast (SSM) mapping

12.2(44)SE

3750-E, 3560-E

HTTP and HTTP(s) support over IPV6

12.2(44)SE

3750-E, 3560-E

Simple Network and Management Protocol (SNMP) configuration over IPv6 transport

12.2(44)SE

3750-E, 3560-E

IPv6 support for stateless autoconfiguration

12.2(44)SE

3750-E, 3560-E

Flex Link Multicast Fast Convergence

12.2(44)SE

3750-E, 3560-E

IEEE 802.1x readiness check

12.2(44)SE

3750-E, 3560-E

/31 bit mask support for multicast traffic

12.2(44)SE

3750-E, 3560-E

Flow-based Switch Port Analyzer (FSPAN)

12.2(44)SE

3750-E, 3560-E

Automatic quality of service (QoS) Voice over IP (VoIP) enhancement

12.2(40)SE

3750-E, 3560-E

Configuration replacement and rollback

12.2(40)SE

3750-E, 3560-E

Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA)

12.2(40)SE

3750-E, 3560-E

Internet Group Management Protocol (IGMP) Helper

12.2(40)SE

3750-E, 3560-E

IP Service Level Agreements (IP SLAs)

12.2(40)SE

3750-E, 3560-E

IP SLAs EOT

12.2(40)SE

3750-E, 3560-E

Multicast virtual routing and forwarding (VRF) Lite

12.2(40)SE

3750-E, 3560-E

SSM PIM protocol

12.2(40)SE

3750-E, 3560-E

Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6

12.2(40)SE

3750-E, 3560-E

Support for VRF-aware services

12.2(40)SE

3750-E, 3560-E

Support for the Link Layer Discovery Protocol Media Extensions (LLDP-MED) location TLV

12.2(40)SE

3750-E, 3560-E

Support for the CISCO-MAC-NOTIFICATION-MIB

12.2(40)SE

3750-E, 3560-E

Support for the CISCO-POWER-ETHERNET-EXT-MIB

12.2(40)SE

3750-E, 3560-E

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

"Address Resolution Protocol" 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)

Address Resolution Protocol

This is an Address Resolution Protocol limitation:

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

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

The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module. The workaround is to configure aggressive UDLD. (CSCsh70244).

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)

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

When line rate traffic is passing through a dynamic port, and you enter the switchport access vlan dynamic interface configuration command for a range of ports, the VLANs might not be assigned correctly. One or more VLANs with a null ID appears in the MAC address table instead.

The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)

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)

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

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)

When you enter an all 0s route with an all 1s mask in the routing table and the next hop is entered as an interface, a traceback message appears.

The workaround is to use an IP address as the next hop instead of an interface. (CSCsi16162)

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)

The far-end fault optional facility is not supported on the GLC-GE-100FX SFP module.

The workaround is to configure aggressive UDLD. (CSCsh70244).

VLANs

These are the VLAN limitations:

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

The error message %DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND might appear for a switch stack under these conditions:

IEEE 802.1 is enabled.

A supplicant is authenticated on at least one port.

A new member joins a switch stack.

You can use one of these workarounds:

Enter the shutdown and the no shutdown interface configuration commands to reset the port.

Remove and reconfigure the VLAN. (CSCsi26444)

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)

In a mixed stack of Catalyst 3750 switches and Catalyst 3750-E switches, when the stack reloads, the Catalyst 3750-E might not become stack master, even it has a higher switch priority set.

The workaround is to check the flash. If it contains many files, remove the unnecessary ones. Check the lost and found directory in flash and if there are many files, delete them. To check the number of files use the fsck flash: command. (CSCsi69447)

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

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

If the switch has interfaces with automatic QoS for voice over IP (VoIP) configured and you upgrade the switch software to Cisco IOS Release 12.2(40)SE (or later), when you enter the auto qos voip cisco-phone interface configuration command on another interface, you might see this message:

AutoQoS Error: ciscophone input service policy was not properly applied
policy map AutoQoS-Police-CiscoPhone not configured

If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.

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:

CSCsi06399

When a RIP network and IP address are configured on an interface, a traceback error occurs after you enter the shutdown, no shutdown, switchport and no switchport interface configuration commands.

The workaround is to configure the RIP network and the IP address after you configure the interface.

CSCsi70454

The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.

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

Do not use a configuration file that is stored by or edited with Windows Notepad.

Manually add the character string end\n to the end of the file.

The workaround is to configure routed IPv4 multicast and IPv6 unicast traffic in different switch ports.

CSCsi71768

If you upgrade the software image from Cisco IOS Release 12.2(25)SEE2 to Cisco IOS Release 12.2(35)SE1, the IPv6 static routes are in the switch configuration but might not be in the routing table.

The workaround is to specify the egress interface on the IPv6 static route

CSCsj10198

When a per-port per-VLAN policy map (a hierarchical VLAN-based policy map) is attached to a VLAN interface, and you remove the child-policy policer from the policy map and then add it back, the policy map fails to re-attach to the same SVI

The workaround is to delete the child policy, which removes it from the parent policy. Then recreate the child policy (with the same or a different name) and reference it in the parent policy. The parent policy then successfully attaches to the SVI.

CSCsk09459 (Catalyst 3750-E switches)

When a switch stack boots up, one or more traceback messages may appear on the switch console when the switch stack has these conditions:

400 or more VLANs

Multicast or port-security feature enabled

CPU utilization percentage is very high

The workaround is to execute clear ip mds linecard [<num>| *] to re-trigger the multicast information download from Route Processor to Line Card. This should be executed after the VLAN database is in sync across the stack.

CSCsk65142

When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.

The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command.

CSCsk96058 (Catalyst 3750-E switches)

A stack member switch might fail to bundle Layer 2 protocol tunnel ports into a port channel when you have followed these steps:

1. You configure a Layer 2 protocol tunnel port on the master switch.

2. You configure a Layer 2 protocol tunnel port on the member switch.

3. You add the port channel to the Layer 2 protocol tunnel port on the master switch.

4. You add the port channel to the Layer 2 protocol tunnel port on the member switch.

After this sequence of steps, the member port might stay suspended.

The workaround is to configure the port on the member switch as a Layer 2 protocol tunnel and at the same time also as a port channel. For example:

Switch(config)# interface fastethernet1/0/11
Switch(config-if)# l2protocol-tunnel cdp
Switch(config-if)# channel-group 1 mode on

CSCsl02680

When the configuration file is removed from the switch and the switch is rebooted, port status for VLAN 1 and the management port (Fast Ethernet 0) is sometimes reported as up and sometimes as down, resulting in conflicts. This status depends on when you respond to the reboot query:

Would you like to enter the initial configuration dialog?

After a reboot if you wait until the Line Protocol status of VLAN 1 appears on the console before responding, VLAN 1 line status is always shown as down. This is the correct state.

The problem (VLAN 1 reporting up) occurs if you respond to the query before VLAN 1 line status appears on the console.

The workaround is to wait for approximately 1 minute after rebooting and until the VLAN 1 interface line status appears on the console before you respond to the query.

CSCsl64124 (Catalyst 3750-E switches)

After a stack bootup, the spanning tree state of a port that has IEEE 802.1x enabled might be blocked, even when the port is in the authenticated state. This can occur on a voice port where the Port Fast feature is enabled.

The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state.

CSCsl19426 (Catalyst 3560-E switches)

When SNMP is enabled on a Catalyst 3560E-12D or 3560E-12SD switch, an SNMP trap is not generated when a power-supply module is removed or inserted.

There is no workaround.

Resolved Caveats

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750-E Switches Only)" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1" section

"Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE" section

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6

CSCso75640

When MAC authentication bypass (MAB) authentication fails, a memory leak no longer occurs.

CSCsq89564

When a VLAN is assigned for IEEE 802.1x authentication and no VLAN is assigned for other types of authentication (such as user authentication or reauthentication), the 802.1x VLAN assignment no longer persists across subsequent authentication attempts.

CSCsr54797

When the switch uses HTTP (web-based) authentication, a memory leak no longer occurs after authorization and policy download.

CSCsx42798

A switch no longer displays processor memory-allocation failure messages under these conditions:

The switch is running IOS release 12.2(44)SE4 or 12.2(44)SE5.

Authentication, authorization, and accounting (AAA) is configured on the switch.

Memory in the primary processor pool is depleted.


Note If the hardware configuration is not a switch stack, AAA requests might fail and the switch might experience high CPU usage for the authentication manager process. In addition, if the hardware configuration is a switch stack and 802.1x, web authentication, or MAC address bypass (MAB) are configured, the switch software might reload after reporting the memory-allocation failure.

This is resolved in Cisco IOS 12.2(44)SE6 and later.


Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5

CSCsm27071

A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:

The configured feature may stop accepting new connections or sessions.

The memory of the device may be consumed.

The device may experience prolonged high CPU utilization.

The device may reload. Cisco has released free software updates that address this vulnerability.

Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml

CSCsv38166

The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.

The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.

This vulnerability does not apply to the Cisco IOS SCP client feature.

Cisco has released free software updates that address this vulnerability.

There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.

This advisory is posted at the following link:

http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.

CSCsr29468

Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.

Cisco has released free software updates that address this vulnerability.

Several mitigation strategies are outlined in the workarounds section of this advisory.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml

CSCsk64158

Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.

Cisco has released free software updates that address this vulnerability.

Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml.

CSCsd73245

Excessive IPRT-3-PATHIDX error messages no longer appear in the log file.

CSCsf10850

When configuring an IP SSH version 2 connection, you can no longer create an RSA key that is less than 768 bits.

CSCsk31907 (Catalyst 3560-E switches)

Debug messages no longer appear when you remove a Twingig converter SFP from the switch.

CSCsv13625 (Catalyst 3560-E switches)

When you remove a Twingig converter SFP from the switch, the link state of the unconnected port belonging to a same port ASIC no longer remains in an up state.

CSCsl47365 (Catalyst 3560-E switches)

TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.

CSCso22754 (Catalyst 3560-E switches)

An EAP-Success message is now sent to a supplicant after it is authenticated on a port.

CSCsq26873 (Catalyst 3560-E switches)

The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.

CSCsu10065 (Catalyst 3560-E switches)

IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.

CSCsu10229 (Catalyst 3560-E switches)

The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.

CSCsu40077 (Catalyst 3560-E switches)

The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).

CSCsu47056 (Catalyst 3560-E switches)

The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.

CSCsv04836

Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.

In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.

Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750-E Switches Only)

CSCsk31907

Debug messages no longer appear when you remove a Twingig converter SFP from the switch.

CSCsl47365

TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.

CSCso22754

An EAP-Success message is now sent to a supplicant after it is authenticated on a port.

CSCsq26873

The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.

CSCsu10065

IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.

CSCsu10229

The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.

CSCsu40077

The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).

CSCsu47056

The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.

CSCsu67705

Avaya IP phones now correctly authenticate on an 802.1x-enabled switch port.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3

CSCee55603

An SNMP access-control list (ACL) now works correctly on virtual routing and forwarding (VRF) interfaces.

CSCsl66074

Intermittently switch reloads no longer occur when IP helper addresses are configured on a VLAN.

CSCsm88601

When multiple voice-over-IP phones are connected to a switch or switch stack with MAC authentication bypass enabled, setting the IEEE 802.1x timeout period too low no longer causes a switch in single-host mode to authenticate the phones using MAC authentication bypass, except when other data packets are received before CDP packets.

CSCso72052

An end host no longer remains in the guest VLAN after an IEEE 802.1X authentication.

CSCso81660

The show interfaces command output for a switch stack now shows the correct values for the output drops.

CSCso87307

A switch no longer drops Cisco Group Management Protocol (CGMP) packets.

CSCsq27267

A switch stack can now send a VTP join message for a VLAN without access associated ports, but for which a Layer 3 VLAN interface exists without causing the VLAN to be pruned.

CSCsq71492

The switch no longer reloads with an address error if the TACACS+ server sends an authentication error when the access control system is configured and a timeout request occurs.

CSCsr20718

Layer 4 operations now work correctly for all port ranges in QoS policy maps.

CSCsr50978

A network loop or incorrect spanning-tree status no longer occurs when you enable cross-stack EtherChannel and connect customer edge devices across a Layer 2 protocol tunnel. The STP bridge protocol data units (BPDUs) now reach the remote end when they are received on an EtherChannel port that is not on the stack master.

CSCsr55949

When IEEE 802.1x port-based authentication is enabled on the switch, Extensible Authentication Protocol (EAP) notification packets from the supplicant are no longer discarded.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2

CSCsg91027 (Catalyst 3750-E switches)

When the logging event-spanning-tree interface configuration command is configured and logging to the console is enabled, a topology change no longer generates a large number of logging messages.

CSCsh70377

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

CSCsk53850 (Catalyst 3750-E switches)

If you enter the no ip vrf vrf-name global configuration command to delete a VPN routing/forwarding instance on the switch when routing is not enabled on the switch, the VRF instance is no longer held in the delete queue.

CSCsi01526

Traceback messages no longer appear if you enter the no switchport interface configuration command to change a Layer 2 interface that belongs to a port channel to a routed port.

CSCsi67680 (Catalyst 3750-E switches)

When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing is no longer disabled on the switch interfaces.

CSCsi73653 (Catalyst 3750-E switches)

Switch ports in the stack now detect new devices after a stack-master failover.

CSCsl76599

The switch no longer unexpectedly reloads while configured with IEEE 802.1x authentication and the MAC authentication bypass feature.

CSCsl93313

When you configure a port channel as trusted by entering the ip dhcp snooping trust interface configuration command, the configuration is no longer lost when the link goes from down to up.

CSCsl62630 (Catalyst 3750-E switches)

When you configure fallback bridging with redundant links on a switch stack, VLAN bridge STP now correctly blocks the SVIs and routed ports that lead to the redundant path. This works even if the physical ports configured on the bridge domain VLANs belong to the member switches in the stack.

CSCsl77063 (Catalyst 3750-E switches)

When you enable detection of Cisco IP phones by entering the switchport voice detect cisco-phone interface configuration command, the interface is no longer disabled if you connect a third-party IP phone is connected to the interface.


Note This command was designed to work with Cisco IP phones; you should not enable it on interfaces connected to third-party IP phones.


CSCsm08603 (Catalyst 3750-E switches)

This traceback error no longer appears when you enter the show aaa subscriber profile privileged EXEC command:

*Mar 2 01:50:41.127: %PARSER-3-BADSUBCMD: Unrecognized subcommand 10 in exec command 
'show aaa subscriber profile WORD' 
-Traceback= D003B4 D00AC8 C908A0 C2F040 C8CA18 CB8984 93B670 932338


Note In Cisco IOS Release 12.2(44)SE2 and later, the subscriber keyword is no longer supported. (The show aaa subscriber profile command is not supported, and you cannot configure the aaa subscriber profile command.)


CSCsm26985

An IP address can be assigned to a routed port that is up and also assigned to a routed port that is administratively down. If you remove the IP address from the down port, the switch no longer loses the hardware forwarding information.

CSCsm61718

A switch no longer unexpectedly reloads when you configure two or more authentication, authorization, and accounting (AAA) broadcast groups.

CSCso75848

The switch no longer experiences a memory leak during an HTTP core process.

CSCso07861

On a switch stack with multiple members, a switch now provides a timely response to an SNMP request on the BridgeMIB's object dot1dBaseNumPorts.

CSCsm26406

Enhanced IGRP (EIGRP) now works correctly when you enter the ip authentication key-chain eigrp interface configuration command.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1

CSCec51750

A router that is configured for HTTP and voice-based services no longer unexpectedly reloads due to memory corruption.

CSCsd45672

When AAA is enabled and you use the aaa group server radius group-name global configuration command to put the switch in server group configuration mode, entering the server-private command no longer causes the switch to reload.

CSCsh46990

The switch no longer reloads when you use the aaa authentication eou default group radius enable global configuration command to configure an EAP over UDP (EOU) method list.

CSCsl52535


Note This caveat applies to all 48-port Catalyst 3750-E and 3560-E switches: Catalyst 3750E-48TD, 3750E-48PD, 3750E-48PD, Full Power, 3560E-48TD, 3560E-48PD, and 3560E-48PD.


If more than 24 switch ports are configured with the same policy map, CPU_HOG traceback errors no longer occur when the switch is reloaded.

CSCsm41883

High CPU usage (greater than 90 percent) no longer occurs on the switch when you first connect a new device.

CSCsm70960

You can now use the interface range interface configuration command to configure IP source guard on member switches.

Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE

CSCsd01180

The switch no longer reloads when you use a Kron command scheduler routine to automatically copy configuration data using the Secure Copy Protocol (SCP). (Kron is a Cisco IOS utility for scheduling non-prompting CLI commands to execute at a later time.)

CSCse14774

When a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.

CSCsg58889 (Catalyst 3750-E switches)

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 no longer stops forwarding traffic if one or more physical ports in the EtherChannel are shut down.

CSCsg70630

A switch with the Dynamic ARP Inspection feature enabled no longer experiences the issue that triggered the display of buffer sharecount messages under certain patterns of ARP packet traffic.

CSCsg77818 (Catalyst 3750-E switches)

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

CSCsh37209 (Catalyst 3750-E switches)

When a stack master changeover event occurs, the backup interface no longer loses traffic. In previous releases, traffic loss occurred for up to 4 seconds under these conditions:

One of the two interfaces in the backup interface pair was an EtherChannel.

The EtherChannel interface was in a forwarding or an active state.

The member interface for the EtherChannel was not present on the next stack master switch.

A failure occurred on the switch stack master.

CSCsh74395

When a VLAN includes multiple MAC addresses, the number of MAC addresses shown in SNMP now matches the output of the show mac-address count vlan vlan-id privileged EXEC command.

CSCsi50367 (Catalyst 3750-E switches)

When changing a switch port access VLAN from static to dynamic or the reverse, this message no longer appears:

01:43:55: PSECURE: Assert failure: is_etherchnl(hwidb_or_null swidb)): 
../switch/psecure/psecure_ifc.c: 412: psecure_get_vlanid (l2a1-5) 01:43:55Traceback= 
804484 809604 802258 806904 70FC 8D70 5C97BC 6901DC 6903CC 9EF8D8 9E6CC4 (l2a1-5)  

CSCsi52707

This message no longer appears when you set an interface back to its default configuration by using the default interface configuration command, this message no longer appears:

%SM-4-STOPPED: Event 'mabAbort' ignored because the state machine is stopped: 
dot1x_auth_mab
    -Traceback= 1D2368 3C1BA8 3C1D40 3C16A8 9EF8D8 9E6CC4

CSCsi52914

When you configure two local source SPAN sessions and then delete these SPAN sessions, the switch allows the creation of new sessions and no longer displays this error message:

% Platform can support a maximum of 2 source sessions 

CSCsi63999

Changing the spanning tree mode from MSTP to other spanning modes no longer causes tracebacks.

CSCsi65551 (Catalyst 3750-E switches)

During master switch failover, a VLAN that has been error disabled on a port is no longer re-enabled after the master switch changeover.

CSCsi67680

When the switch has VRF interfaces configured and you disable unicast routing by entering the no ip routing global configuration command and then re-enable unicast routing, VRF routing now functions correctly over the VRF interface.

CSCsi77705

Broadcast storm control now works correctly on IEEE 802.1Q trunk ports.

CSCsi78737

The cpmCPURisingThreshold traps on the switch are no longer missing the cpmProcExtUtil5SecRev and cpmProcessTimeCreated trap components. Note that although the components were missing from the traps, the PROCESS MIB was still populating the objects.

CSCsi79504

OSPF hello packets now have the correct CoS value of 7.

CSCsi85257

A Cisco IP Phone now works correctly when it is connected to a port that is configured with CDP bypass and multidomain authentication (MDA).

CSCsi90852 (Catalyst 3560-E switches)

The interface between two 3560-E switches that are running the 12.2(35)SE2 software release with the TwinGig converter module installed and connected through the CAB-SFP-50CM cable no longer stays down when you disconnect and then reconnect one end of the cable, if you manually shut down the switch, or if one of the switches reloads.

CSCsj08561

When you enter the show interface status privileged EXEC command on the switch, a port no longer might show notconnect for an inline power port when the show power inline privileged EXEC command shows that the port is still delivering power.

CSCsj22678 (Catalyst 3750-E switches)

A significant delay no longer occurs when you remove an access control list (ACL) from a switch stack under these conditions:

A per-VLAN QoS, per-port policer policy map is attached to a large number of switched virtual interfaces (SVIs) in the stack.

The ACL to be removed is being used by the policy map.

There are three or more switches in the stack.

CSCsj22994

ACLs are now configured correctly when they contain ICMP codes 251 to 255.

CSCsj47067

If you upgrade from Cisco IOS Release 12.2(35)SE1 to Release 12.2(37)SE, a security violation no longer occurs when:

You enter the switchport port-security maximum 1 vlan access interface configuration command.

An IP phone with a PC behind it is connected to an access port with port security.

CSCsj52956 (Catalyst 3750-E switches)

The TxBufferFullDropCount no longer continuously increments on a switch or switch stack.

CSCsj53001

The Total- output-drops field in the show interfaces privileged EXEC command output now displays accurate ASIC drops.

CSCsj64882

When IGMP snooping is enabled, CGMP interoperability mode now works as it should when the upstream multicast router is set up correctly with PIM and IP CGMP.

CSCsj77933

If you enter a space before a comma in the define interface-range or the interface range global configuration command, the space before the comma is now saved in the switch configuration.

CSCsj87991

A switch configured for Link Layer Discovery Protocol (LLDP) now correctly reports the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes.

CSCsj90406

When VTP pruning is enabled, the switch no longer might experience high CPU usage (greater than 90 percent) for up to 20 minutes after the link comes up simultaneously on multiple trunk ports.

CSCsj99786

On a switch that supports fallback bridging, when a bridge-group is configured on some VLANs, non-IP traffic in the VLANs destined to a known MAC address are no longer flooded in the bridge-group.

CSCsk03224

When you are using AAA for Telnet and console authentication and login failure and success debugging is enabled, the username now shows correctly in the log.

CSCsk19926 (Catalyst 3750-E switches)

Traffic is now received on a member port in a switch stack under these conditions:

The port is in a cross-stack EtherChannel.

One or more of the master switch Cisco TwinGig Converter Module ports are in the cross-stack EtherChannel.

This member switch has been reloaded.

CSCsk25175

When the switch has VTP pruning and an RSPAN session configured, the RSPAN VLAN traffic is now correctly pruned as set up by the VTP pruning configuration.

CSCsk34118

On a switch with routed ports, when you configure MAC address-table aging time by entering the mac address-table aging-time time global configuration command and then enter the show running-config privileged EXEC command, the output no longer displays the aging time values for internal VLANs.

CSCsk38083

When UDLD is enabled on a Layer 2 interface, and the native VLAN for the port is not configured as a VLAN on the switch, UDLD no longer puts the port into an error-disabled state.

CSCsk62010

A switch no longer fails when you enter the show interfaces vlan vlan-id switchport privileged EXEC command.

CSCsk67520

If you enter the hostname global configuration command followed by a hostname that contains illegal characters, for example, one that appears to be an IP address, the switch now displays a warning message, but the specified hostname is configured.

CSCsk84233

A switch no longer fails under these conditions:

EIGRP routing is enabled.

The HSRP standby interface and the active interface are configured with the same IP address.

A switch that is connected to the HSRP standby interface fails.

CSCsk89616 (Catalyst 3750-E switches)

When port security is configured on a switch, a device MAC address is now correctly learned on that port. (In previous releases, a new device MAC address was not learned on a port-security enabled port, and the device MAC address was not added to the list of secure addresses.)

CSCsl01491 (Catalyst 3750-E switches)

The output of these show user EXEC commands now display the correct status of ports in a cross-stack EtherChannel bundle:

show etherchannel port

show etherchannel detail

CSCsl33304

Web authentication no longer stops working when IEEE 802.1X re-authentication is enabled and the re-authentication timer expires.

Documentation Updates

"Updates to the Software Configuration Guide" section

"Updates to the Command Reference" section

"Updates to the System Message Guide" section

"Updates to the Getting Started Guides" section

"Updates to the Hardware Installation Guide" section

"Updates to the Regulatory Compliance and Safety Information" section

Updates to the Software Configuration Guide

These are the updates to the Software Configuration Guide for the Catalyst 3750-E and Catalyst 3560-E switches:

This section was added to the "Preventing Unauthorized Access to Your Switch" section of the "Configuring Switch-Based Authentication" chapter:

You can also enable the login enhancements feature, which logs both failed and unsuccessful login attempts. Login enhancements can also be configured to block future login attempts after a set number of unsuccessful attempts are made. For more information, see the Cisco IOS Login Enhancements documentation at this URL:

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gt_login.html

If the switch is running the IP base feature set, you can configure complete EIGRP routing. However, the configuration is not implemented because the IP base feature set supports only EIGRP stub routing, as described in the "Configuring IP Unicast Routing" chapter of the software configuration guide.

After you have entered the eigrp stub router configuration command, only the eigrp stub connected summary command takes effect. Although the CLI help might show the receive-only and static keywords and you can enter these keywords, the switch running the IP base image always behaves as if the connected and summary keywords were configured.

In the "Multi-VRF CE Configuration Guidelines" section of the "Configuring IP Unicast Routing" chapter of the Catalyst 3750-E and Catalyst 3560-E Switch Software Configuration Guide, this guideline is incorrect:

You can configure 104 policies whether or not VRFs are configured on the switch or the switch stack.

This is the correct guideline:

You can configure up to 105 policies whether or not VRFs are configured on the switch or the switch stack.

This information is added to the "Using IEEE 802.1x Authentication with Per-User ACLs" section of "Configuring IEEE 802.1x Port-Based Authentication" chapter of the software configuration guide:

Per-user ACLs are supported only in single-host mode.

This information was added to the "Power over Ethernet Ports" section of the "Configuring Interface Characteristics" chapter:

In Cisco IOS Release 12.2(40)SE and earlier, each 10/100/1000 PoE port provides up to 15.4 W of power to the device. Cisco IOS Release 12.2(44)SE and later supports enhanced PoE. An enhanced PoE port can support any additional powered device that requires up to 20 watts.

This section was updated in the "Budgeting Power for Devices Connected to a PoE Port" section of thee "Configuring Interface Characteristics" chapter:

Beginning in privileged EXEC mode, follow these steps to configure amount of power budgeted to a powered device connected to a specific PoE port:

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

no cdp run

(Optional) Disable CDP.

Step 3 

interface interface-id

Specify the physical port to be configured, and enter interface configuration mode.

Step 4 

power inline consumption default wattage

or

power inline port maximum

Configure the power consumption of a powered device connected to a PoE port on the switch. The range for each device is 4000 to 15400 mW. The default is 15400 mW.

Configure enhanced PoE so that the maximum power supplied to a device (up to 20 W).

Step 5 

end

Return to privileged EXEC mode.

Step 6 

show power inline consumption default

Display the power consumption data.

Step 7 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

To return to the default setting, use the no power inline consumption default interface configuration command.

For information about the output of the show power inline consumption default privileged EXEC command, see the command reference for this release.

The"Configuring Embedded Event Manager" chapter was added to the software configuration guide. This chapter describes how to use the embedded event manager (EEM) to monitor and manage the Catalyst 3750 or 3560 switch and how to configure it. (For the Catalyst 3750 switch, the term switch refers to a standalone switch or a switch stack unless otherwise noted.)


Note For complete syntax and usage information for the commands used in this chapter, see the command reference for this release and the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3T. For complete configuration information, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.


This chapter consists of these sections:

Understanding Embedded Event Manager

Configuring Embedded Event Manager

Displaying Embedded Event Manager Information

Understanding Embedded Event Manager

The embedded event manager (EEM) monitors key system events and then acts on them though a set policy. This policy is a programmed script that you can use to customize a script to invoke an action based on a given set of events occurring. The script generates actions such as generating custom syslog or Simple Network Management Protocol (SNMP) traps, invoking CLI commands, forcing a failover, and so forth. The event management capabilities of EEM are useful because not all event management can be managed from the switch and because some problems compromise communication between the switch and the external network management device. Network availability is improved.if automatic recovery actions are performed without rebooting the switch,

Figure 1 shows the relationship between the EEM server, the core event publishers (event detectors), and the event subscribers (policies). The event publishers screen events and when there is a match on an event specification that is provided by the event subscriber. Event detectors notify the EEM server when an event occurs. The EEM policies then implement recovery based on the current state of the system and the actions specified in the policy for the given event.

Figure 1 Embedded Event Manager Core Event Detectors

These sections contain this conceptual information:

Event Detectors

Embedded Event Manager Actions

Embedded Event Manager Policies

Embedded Event Manager Environment Variables

Event Detectors

EEM software programs known as event detectors determine when an EEM event occurs. Event detectors are separate systems that provide an interface between the agent being monitored, for example SNMP, and the EEM polices where an action can be implemented. Event detectors are generated only by the master switch. CLI and routing processes also run only from the master switch.


Note On a Catalyst 3750 switch stack, the stack member switch does not generate events and does not support memory threshold notifications or IOSWdSysmon event detectors.


EEM allows these event detectors:

Application-specific event detector- Allows any EEM policy to publish an event.

IOS CLI event detector- Generates policies based on the commands entered through the CLI.

GOLD event detector- Publishes an event when a GOLD failure event is detected on a specified card and subcard.

Counter event detector-Publishes an event when a named counter crosses a specified threshold.

Interface counter event detector- Publishes an event when a generic Cisco IOS interface counter for a specified interface crosses a defined threshold. A threshold can be specified as an absolute value or an incremental value.For example, if the incremental value is set to 50 an event would be published when the interface counter increases by 50.

None event detector- Publishes an event when the event manager run CLI command executes an EEM policy. EEM schedules and runs policies on the basis on an event specification within the policy itself. An EEM policy must be manually identified and registered before the event manager run command executes.

Online insertion and removal event detector-Publishes an event when a hardware insertion or removal (OIR) event occurs.

Resource threshold event detector- Generates policies based on global platform values and thresholds. Includes resources such as CPU utilization and remaining buffer capacity. Applies only to the master switch.

SNMP event detector- Allows a standard SNMP MIB object to be monitored and an event to be generated when the object matches specified values or crosses specified thresholds.

Syslog event detector- Allows for screening syslog messages for a regular expression pattern match. The selected messages can be further qualified, requiring that a specific number of occurrences be logged within a specified time. A match on a specified event criteria triggers a configured policy action.

Timer event detector

Publishes events for these timers:

An absolute-time-of-day timer publishes an event when a specified absolute date and time occurs.

A countdown timer publishes an event when a timer counts down to zero.

A watchdog timer publishes an event when a timer counts down to zero. The timer automatically resets itself to its initial value and starts to count down again.

A CRON timer publishes an event by using a UNIX standard CRON specification to define when the event is to be published. A CRON timer never publishes events more than once per minute.

Watchdog event detector (IOSWDSysMon). This detector applies only to the master switch.

Publishes an event when one of these events occurs:

CPU utilization for a Cisco IOS process crosses a threshold.

Memory utilization for a Cisco IOS process crosses a threshold.

Two events can be monitored at the same time, and the event publishing criteria requires that one or both events cross their specified thresholds.

Embedded Event Manager Actions

EEM provides actions that occur in response to an event. EEM supports these actions:

Modifying a named counter.

Publishing an application-specific event.

Generating an SNMP trap.

Generating prioritized syslog messages.

Reloading the Cisco IOS software.

Reloading the switch stack. (Catalyst 3750 only)

Reloading the master switch in the event of a master switchover. If this occurs, a new master switch is elected.

Embedded Event Manager Policies

EEM can monitor events and provide information, or take corrective action when the monitored events occur or a threshold is reached. An EEM policy is an entity that defines an event and the actions to be taken when that event occurs.

There are two types of EEM policies: an applet or a script. An applet is a simple policy that is defined within the CLI configuration. It is a concise method for defining event screening criteria and the actions to be taken when that event occurs. Scripts are defined on the networking device by using an ASCII editor. The script is then copied to the networking device and registered with EEM.

You use EEM to write and implement your own policies using the EEM policy tool command language (TCL) script. When you configure a TCL script on the master switch and the file is automatically sent to the member switches. The user-defined TCL scripts must be available in the member switches so that if the master switch changes, the TCL scripts policies continue to work.

Cisco enhancements to TCL in the form of keyword extensions facilitate the development of EEM policies. These keywords identify the detected event, the subsequent action, utility information, counter values, and system information.

For complete information on configuring EEM policies and scripts, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.

Embedded Event Manager Environment Variables

EEM uses environment variables in EEM policies. These variables are defined in a EEM policy tool command language (TCL) script by running a CLI command and the event manager environment command. These environment variables can be defined in EEM:

User-defined variables

Defined by the user for a user-defined policy.

Cisco-defined variables

Defined by Cisco for a specific sample policy.

Cisco built-in variables (available in EEM applets)

Defined by Cisco and can be read-only or read-write. The read-only variables are set by the system before an applet starts to execute. The single read-write variable, _exit_status, allows you to set the exit status for policies triggered from synchronous events.

Cisco-defined environment variables and Cisco system-defined environment variables might apply to one specific event detector or to all event detectors. Environment variables that are user-defined or defined by Cisco in a sample policy are set by using the event manager environment global configuration command. You must defined the variables in the EEM policy before you register the policy.

For information about the environmental variables that EEM supports, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.

Configuring Embedded Event Manager

These sections contain this configuration information:

Registering and Defining an Embedded Event Manager Applet

Registering and Defining an Embedded Event Manager TCL Script

For complete information about configuring embedded event manager, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.

Registering and Defining an Embedded Event Manager Applet

Beginning in privileged EXEC mode, perform this task to register an applet with EEM and to define the EEM applet using the event applet and action applet configuration commands.


Note Only one event applet command is allowed in an EEM applet. Multiple action applet commands are permitted. If you do not specify the no event and no action commands, the applet is removed when you exit configuration mode.


 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

event manager applet applet-name

Register the applet with EEM and enter applet configuration mode.

Step 3 

event snmp oid oid-value get-type {exact | next} entry-op {gt | ge | eq | ne | lt | le} entry-val entry-val [exit-comb {or |and}] [exit-op {gt | ge | eq | ne | lt | le}] [exit-val exit-val] [exit-time exit-time-val] poll-interval poll-int-val

Specify the event criteria that causes the EEM applet to run.

(Optional) Exit criteria. If exit criteria are not specified, event monitoring is re-enabled immediately.

Step 4 

action label syslog [priority priority-level] msg msg-text

Specify the action when an EEM applet is triggered. Repeat this action to add other CLI commands to the applet.

(Optional) The priority keyword specifies the priority level of the syslog messages. If selected, you need to define the priority-level argument.

For msg-text, the argument can be character text, an environment variable, or a combination of the two.

Step 5 

end

Exit applet configuration mode and return to privileged EXEC mode.

This example shows the output for EEM when one of the fields specified by an SNMP object ID crosses a defined threshold:

Switch(config-applet)# event snmp oid 1.3.6.1.4.1.9.9.48.1.1.1.6.1 get-type exact 
entry-op lt entry-val 5120000 poll-interval 10 

These examples show actions that are taken in response to an EEM event:

Switch(config-applet)# action 1.0 syslog priority critical msg "Memory exhausted; 
current available memory is $_snmp_oid_val bytes" 

Switch (config-applet)# action 2.0 force-switchover 

Registering and Defining an Embedded Event Manager TCL Script

Beginning in privileged EXEC mode, perform this task to register a TCL script with EEM and to define the TCL script and policy commands.

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 1 

show event manager environment [all | variable-name]

(Optional) The show event manager environment command displays the name and value of the EEM environment variables.

(Optional) The all keyword displays the EEM environment variables.

(Optional) The variable-name argument displays information about the specified environment variable.

Step 2 

configure terminal

Enter global configuration mode.

Step 3 

event manager environment variable-name string

Configure the value of the specified EEM environment variable. Repeat this step for all the required environment variables.

Step 4 

event manager policy policy-file-name [type system] [trap]

Register the EEM policy to be run when the specified event defined within the policy occurs.

Step 5 

exit

Exit global configuration mode and return to privileged EXEC mode.

This example shows the sample output for the show event manager environment command:

Switch# show event manager environment all
No.  Name                          Value
1    _cron_entry                   0-59/2 0-23/1 * * 0-6
2    _show_cmd                     show ver
3    _syslog_pattern               .*UPDOWN.*Ethernet1/0.*
4    _config_cmd1                  interface Ethernet1/0
5    _config_cmd2                  no shut

This example shows a CRON timer environment variable, which is assigned by the software, to be set to every second minute, every hour of every day:

Switch (config)# event manager environment_cron_entry 0-59/2 0-23/1 * * 0-6 

This example shows the sample EEM policy named tm_cli_cmd.tcl registered as a system policy. The system policies are part of the Cisco IOS image. User-defined TCL scripts must first be copied to flash memory:

Switch (config)# event manager policy tm_cli_cmd.tcl type system

Displaying Embedded Event Manager Information

To display information about EEM, including EEM registered policies and EEM history data, see the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3T.

Unsupported Embedded Event Manager Commands

Privileged EXEC

event manager scheduler clear

event manager update user policy

show event manager detector

show event manager version

Global Configuration

event manager detector rpc

event manager directory user repository

Applet Configuration (config-applet)

event rpc

event snmp-notification

trigger (EEM)

Trigger Applet Configuration (config-applet-trigger)

attribute (EEM)

correlate

Event Trigger Configuration (config-event-trigger)

event owner

Updates to the Command Reference

These are updates to the command reference:

These descriptions were added to the Pair Status field of the show cable-diagnostics tdr command output:

Pair status

The status of the pair of wires on which TDR is running:

ImpedanceMis—The impedance is mismatched.

Short/Impedance Mismatched—The impedance mismatched or the cable is short.


The port maximum keywords were added to the power inline command. This is the update to the command reference:

power inline

Use the power inline interface configuration command on the switch stack or on a standalone switch to configure the power management mode on the Power over Ethernet (PoE) ports. Use the no form of this command to return to the default settings.

power inline {auto [max max-wattage] | never | police [action log] | port maximum | static [max max-wattage]}

no power inline {auto | never | police | port | static}

Syntax Description

auto

Enable powered-device detection. If enough power is available, automatically allocate power to the PoE port after device detection.

max max-wattage

(Optional) Limit the power allowed on the port. The range is 4000 to 15400 mW. If no value is specified, the maximum is allowed.

never

Disable device detection, and disable power to the port.

police [action log]

Enable policing of the real-time power consumption. For more information about these keywords, see the power inline police command.

static

Enable powered-device detection. Pre-allocate (reserve) power for a port before the switch discovers the powered device.

port maximum

Configure the maximum power level value (up to 20 W) for the port.


Defaults

The default is auto (enabled).

The maximum wattage is 15400 mW.

Command Default

Interface configuration

Command History

Release
Modification

12.2(35)SE2

This command was introduced.

12.2(44)SE

The port maximum keywords were added.


Usage Guidelines

This command is supported only on PoE-capable ports. If you enter this command on a port that does not support PoE, this error message appears:

Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# power inline auto
                  ^
% Invalid input detected at '^' marker.

In a switch stack, this command is supported on all ports in the stack that support PoE.

Use the max max-wattage option to disallow higher-power powered devices. With this configuration, when the powered device sends Cisco Discovery Protocol (CDP) messages requesting more power than the maximum wattage, the switch removes power from the port. If the powered-device IEEE class maximum is greater than the maximum wattage, the switch does not power the device. The power is reclaimed into the global power budget.


Note The switch never powers any class 0 or class 3 device if the power inline max max-wattage command is configured for less than 15.4 W.


If the switch denies power to a powered device (the powered device requests more power through CDP messages or if the IEEE class maximum is greater than the maximum wattage), the PoE port is in a power-deny state. The switch generates a system message, and the Oper column in the show power inline privileged EXEC command output shows power-deny.

Use the power inline static max max-wattage command to give a port high priority. The switch allocates PoE to a port configured in static mode before allocating power to a port configured in auto mode. The switch reserves power for the static port when it is configured rather than upon device discovery. The switch reserves the power on a static port even when there is no connected device and whether or not the port is in a shutdown or in a no shutdown state. The switch allocates the configured maximum wattage to the port, and the amount is never adjusted through the IEEE class or by CDP messages from the powered device. Because power is pre-allocated, any powered device that uses less than or equal to the maximum wattage is guaranteed power when it is connected to a static port. However, if the powered device IEEE class is greater than the maximum wattage, the switch does not supply power to it. If the switch learns through CDP messages that the powered device needs more than the maximum wattage, the powered device is shut down.


Note Cisco IOS Release 12.2(44)SE and later supports enhanced PoE. You can use the power inline port maximum interface configuration command to support a device with the maximum power level of 20 watts.


If the switch cannot pre-allocate power when a port is in static mode (for example, because the entire power budget is already allocated to other auto or static ports), this message appears: Command rejected: power inline static: pwr not available. The port configuration remains unchanged.

When you configure a port by using the power inline auto or the power inline static interface configuration command, the port autonegotiates by using the configured speed and duplex settings. This is necessary to determine the power requirements of the connected device (whether or not it is a powered device). After the power requirements have been 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 port reverts to the configured speed and duplex settings.

If a port has a Cisco powered device connected to it, you should not use the power inline never command to configure the port. A false link-up can occur, placing the port in an error-disabled state.

Examples

This example shows how to enable detection of a powered device and to automatically power a PoE port on a Catalyst 3750-E switch:

Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# power inline auto

This example shows how to configure a PoE port on a Catalyst 3560-E switch to allow a class 1 or a class 2 powered device:

Switch(config)# interface gigabitethernet0/2
Switch(config-if)# power inline auto max 7000

This example shows how to disable powered-device detection and to not power a PoE port on a Catalyst 3750-E switch:

Switch(config)# interface gigabitethernet1/0/2
Switch(config-if)# power inline never

This example shows how to configure a port to supply 20w to an attached device:

Switch(config-if)# power inline port maximum 20000
Switch(config-if)# power inline auto max ?
<15400-20000> milli-watts

You can verify your settings by entering the show power inline user EXEC command.

Related Commands

Command
Description

logging event power-inline-status

Enables the logging of PoE events.

show controllers power inline

Displays the values in the registers of the specified PoE controller.

show power inline

Displays the PoE status for the specified PoE port or for all PoE ports.


Updates to the System Message Guide

These are the updates to System Message Guide for the Catalyst 3750-E and Catalyst 3560-E switches:

Error Message    ACLMGR-4-UNLOADINGFSPAN Unloading[chars]session[dec][chars]feature

Explanation    The access control list (ACL) manager is unable to store the flow-based SPAN (FSPAN) configuration, and this feature has been temporarily disabled for the specified session. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.

Recommended Action    Specify an SDM template that allocates more system resources for ACLs, simplify the ACL, or use the same ACLs on multiple interfaces.

Error Message    ACLMGR-4-RELOADEDFSPAN Reloading [chars] session [dec] [chars] feature

Explanation    The access control list (ACL) manager can store the flow-based SPAN configuration for the specified session. One or more ACLs had previously been unloaded because of lack of hardware memory. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.

Recommended Action    No action is required.

Error Message    DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on 
[chars]

Explanation    The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.

Recommended Action    If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.

Error Message    EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will 
remain stand-alone. 

Explanation    The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.

Recommended Action    Ensure that the other ports in the bundle have the same configuration]

Error Message    ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface 
Fa0/7:Power given, but link is not up.

Explanation    The inline-power-controller reported an error on an interface.

Recommended Action    Enter the shutdown and no shutdown interface configuration commands on the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an electrostatic discharge (ESD) recovery mechanism.

Error Message    PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not 
be programmed into TCAM and are being covered by a less specific prefix

Explanation    A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.

Recommended Action    No action is required.

Error Message    PLATFORM_HCEF-3-ADJ: [chars]

Explanation    This message appears when an unsupported feature is configured on a switch running Cisco IOS Release 12.2(25)SE. [chars] is the error message.

Recommended Action    Determine if a generic routing encapsulation (GRE) tunnel or the ip cef accounting global configuration command are configured. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef accounting command is configured, remove it by using the no ip cef accounting global configuration command.


Note Cisco IOS Release12.2(25)SEB2 does not support the ip cef accounting command.


Error Message    PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes 
could not be programmed into TCAM and are being covered by a less specific prefix

Explanation    A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.

Recommended Action    No action is required.

Error Message    PLATFORM_SPAN-3-FEATUREMISMATCH:[chars] cannot be supported with the 
image running on switch [dec].

Explanation    A switch stack member software image does not support a specific flow-based SPAN (FSPAN) access control list (ACL) filter. [chars] is the FSPAN ACL filter that is not supported, and [dec] is the stack member number.

Recommended Action    Upgrade to an image that supports the FSPAN ACL filter.

Error Message    SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all Vlans  

Explanation    The interface has been added to all VLANs. [chars] is the added interface.

Recommended Action    No action is required.

Error Message    SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all Vlans  

Explanation    The interface has been deleted from all VLANs. [chars] is the deleted interface.

Recommended Action    No action is required.

Error Message    SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars]. 

Explanation    The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.

Recommended Action    No action is required.

Error Message    VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit. 

Explanation    The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.

Recommended Action    To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.

Error Message    VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response. 

Explanation    The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.

Recommended Action    Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.

Error Message    WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired. 

Explanation    The switch has acquired the specified web cache. [IP_address] is the web cache IP address.

Recommended Action    No action is required.

Error Message    WCCP-1-CACHELOST: Web Cache [IP_address] lost. 

Explanation    The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.

Recommended Action    Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.

Updates to the Getting Started Guides

These are the updates to the Getting Started Guides for the Catalyst 3750-E and Catalyst 3560-E switches:

This information should be included in the "Install and Connect to Devices in the 10-Gigabit Ethernet Slots" section:

When you install or remove the converter module, the mode on the switch changes from 10-Gigabit Ethernet to Gigabit Ethernet or the reverse. During this mode change, data traffic on the other switch uplink ports (X2 transceiver or SFP module ports) might temporarily stop.

When you install or remove an X2 transceiver or SFP module, traffic delay does not occur.

This information should be included in the "Troubleshooting Express Setup" section:

POST errors are usually fatal. Contact your Cisco technical support representative if your switch fails POST.

Updates to the Hardware Installation Guide

These are the updates for the Hardware Installation Guide for the Catalyst 3750-E and Catalyst 3560-E switches:

The "Mounting the Catalyst 3560E-12SD Switch on a Wall" section is incorrect. You cannot wall-mount the Catalyst 3560-12SD switch.

This information was added to the "Safety Warnings" section:


Caution To comply with the Telcordia GR-1089 NEBS standard, PoE or non-PoE 10/100/1000 Ethernet port cables that exit from either the left side or right side of the switch should be routed and tied to the nearest rack metal hardware.

Updates to the Regulatory Compliance and Safety Information

These are the updates to the Regulatory Compliance and Safety information for the Catalyst 3750-E and Catalyst 3560-E switches:

This Network Equipment-Building System (NEBS) compliance statement information was added to the Regulatory Standards Compliance section:

Regulatory Standards Compliance

This section includes all regulatory, safety, and EMC standards. The Catalyst 3750-E and Catalyst 3560-E switches are in compliance with national and international standards as described in Table 6.

Table 6 Regulatory Standards Compliance for the Catalyst 3750-E and 3560-E Switches 

Specification
Description

Regulatory Compliance

Products with the CE Marking are compliant with the 89/336/EEC and 73/23/EEC directives, which include the safety and EMC standards listed.

Safety Certifications

UL60950-1
C-UL to CAN/CSA 22.2 No.60950-1
TUV/GS to EN 60950-1
CB to IEC 60950-1 with all country deviations
AS/NZS 60950-1
CE Marking
NOM (through partners and distributors)
GOST
NEBS

Electromagnetic Compatibility Certifications

FCC Part 15 Class A
EN55022 Class A (CISPR22)
EN55024 (CISPR24)
CE
VCCI Class A
AS/NZS CISPR22 Class A
MIC
China EMC certifications
GOST
NEBS

Environmental

Reduction of Hazardous Substances (ROHS) 5

Noise Specifications

Office Product Spec: 48dBA at 30 degrees C (refer to ISO 7779)

Telco

CLEI code


For specific details about the years, revisions, and relevant amendments, refer to the applicable declaration of conformity available at:

http://tools.cisco.com/cse/prdapp/jsp/externalsearch.do?action=externalsearch&page=EXTERNAL_SEARCH&module=EXTERNAL_SEARCH.

Cautions and Regulatory Compliance Statements for NEBS

This section includes the cautions and regulatory compliance statements for the Network Equipment-Building System (NEBS) certification from the Telcordia Electromagnetic Compatibility and Electrical Safety - Generic Criteria for Network Telecommunications Equipment (A Module of LSSGR, FR-64; TSGR, FR-440; and NEBSFR, FR-2063) Telcordia Technologies Generic Requirements, GR-1089-CORE, Issue 4, June 2006 (see Table 7).

Table 7 NEBS Compliance Statements 

Attach an ESD-preventive wrist strap to your wrist and to a bare metal surface.


Caution To comply with the Telcordia GR-1089 NEBS standard for electromagnetic compatibility and safety, for Ethernet RJ-45 ports, use only shielded Ethernet cables that are grounded on both ends. In a NEBS installation, all Ethernet ports are limited to intrabuilding wiring.

Caution The intrabuilding ports of the equipment or subassembly is only suitable for connection to intrabuilding or unexposed wiring or cabling. The intrabuilding ports of the equipment or subassembly MUST NOT be metallically connected to interfaces that connect to the OSP or its wiring. These interfaces are designed for use only as intrabuilding interfaces (Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 4), and require isolation from the exposed OSP cabling. The addition of primary protectors is not sufficient protection in order to connect these interfaces metallically to OSP wiring.

Caution To comply with the Telcordia GR-1089 NEBS standard, PoE or non-PoE 10/100/1000 Ethernet port cables that exit from either the left side or right side of the switch should be routed and tied to the nearest rack metal hardware.

Products that have an AC power connection are intended for deployments where an external surge protective device (SPD) is used at the AC power service equipment as defined by the National Electric Code (NEC).

This product is designed for a common bonding network (CBN) installation.

This product can be installed in a network telecommunication facility or location where the NEC applies.

An electrical conducting path should exist between the product chassis and the metal surface of the enclosure or rack in which it is mounted or to a grounding conductor. Electrical continuity should be provided by using thread-forming type mounting screws that remove any paint or nonconductive coatings and establish a metal-to-metal contact. Any paint or other nonconductive coatings should be removed on the surfaces between the mounting hardware and the enclosure or rack. The surfaces should be cleaned and an antioxidant applied before installation.

The grounding architecture of this product is DC-isolated (DC-I).

DC-powered products have a nominal operating DC voltage of 48 VDC. Minimal steady state DC operating voltage is 40 VDC. Reference American National Standards Institute (ANSI) T1.315, Table 1.


Related Documentation

These documents provide complete information about the Catalyst 3750-E and Catalyst 3560-E switches and are available on Cisco.com:

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

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

These documents provide complete information about the switches:

Catalyst 3750-E Switch Getting Started Guide

Catalyst 3560-E Switch Getting Started Guide

Catalyst 3750-E and Catalyst 3560-E Switch Hardware Installation Guide

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

Release Notes for the Catalyst 3750-E and Catalyst 3560-E Switch

Catalyst 3750-E and Catalyst 3560-E Switch Software Configuration Guide

Catalyst 3750-E and Catalyst 3560-E Switch Command Reference

Catalyst 3750-E and Catalyst 3560-E Switch System Message Guide

Cisco Software Activation and Compatibility Document

Installation Notes for the Catalyst 3750-E, Catalyst 3560-E Switches, and RPS 2300 Power Supply Modules

Installation Notes for the Catalyst 3750-E and Catalyst 3560-E Switch Fan Module

Installation Notes for the Cisco TwinGig Converter Module

Cisco Redundant Power System 2300 Hardware Installation Guide

Cisco Redundant Power System 2300 Compatibility Matrix

Device manager online help (available on the switch)

These compatibility matrix documents are available from this Cisco.com site:

http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html

Cisco Gigabit Ethernet Transceiver Modules Compatibility Matrix

Cisco 100-Megabit Ethernet SFP Modules Compatibility Matrix

Cisco Small Form-Factor Pluggable Modules Compatibility Matrix

Compatibility Matrix for 1000BASE-T Small Form-Factor Pluggable Modules

For other information about related products, see these documents:

Getting Started with Cisco Network Assistant

Release Notes for Cisco Network Assistant

Network Admission Control Software Configuration Guide

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html