Release Notes for Catalyst 3750-X, and 3560-X Switches, Cisco IOS Release 15.0(2)EZ

Table Of Contents

Release Notes for Catalyst 3750-X, and 3560-X, Switches, Cisco IOS Release 15.0(2)EZ

Contents

System Requirements

Supported Hardware

Device Manager System Requirements

Hardware

Software

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 Software Features

New in Cisco IOS Release 15.0(2)EZ

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Cisco IOS Limitations

Address Resolution Protocol

Cisco Transceiver Modules and SFP Modules

Configuration

Diagnostics

EtherChannel

IEEE 802.1x Authentication

Multicasting

PoE or PoE+

QoS

RADIUS

Routing

Smart Install

SPAN and RSPAN

Spanning Tree Protocol

Stacking (Catalyst 3750-X )

Stack Power (Catalyst 3750-X only)

VLANs

TrustSec

Device Manager Limitations

Hardware Limitations

C3KX-SM-10G Network Module (Catalyst 3750-X and 3560-X only)

Important Notes

Switch Stack Notes

Control Plane Protection

Cisco IOS Notes

Device Manager Notes

Related Documentation

Obtaining Documentation and Submitting a Service Request

Release Notes for Catalyst 3750-X, and 3560-X, Switches, Cisco IOS Release 15.0(2)EZ

---

April, 2013

Cisco IOS Release 15.0(2)EZ and higher runs on Catalyst 3750-X, ,and Catalyst 3650-X, switches and on Cisco enhanced EtherSwitch service modules.

The Catalyst 3750-X and switch support stacking through Cisco StackWise Plus technology. The Catalyst 3750-X also supports StackPower. The Catalyst 3560-X switch and the Cisco enhanced EtherSwitch service modules do not support switch stacking.

Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack. Cisco enhanced EtherSwitch service modules switch supports the same features.

For more information, see the Deciding Which Files to Use and the "Related Documentation" section.

These release notes include important information about Cisco IOS release 15.0(2)EZ and higher, and later and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:

•If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.

•If your switch is on, use the show version privileged EXEC command. See the "Finding the Software Version and Feature Set" section.

•If you are upgrading to a new release, see the software upgrade filename for the software version. See the "Deciding Which Files to Use" section.

You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/web/download/index.html

Contents

•"System Requirements" section

•"Upgrading the Switch Software" section

•"Installation Notes" section

•"New Software Features" section

•"Limitations and Restrictions" section

•"Important Notes" section

•"Related Documentation" section

•"Obtaining Documentation and Submitting a Service Request" section

System Requirements

•"Supported Hardware" section

•"Device Manager System Requirements" section

•"Cluster Compatibility" section

•"CNA Compatibility" section

Supported Hardware

Table 1 Catalyst 3750-X and Catalyst 3560-X Supported Hardware 

Switch Model	Description	Supported by Minimum Cisco IOS Release
Catalyst 3560X-24T-E	24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3560X-48T-E	48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3560X-24P-E	24 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3560X-48P-E	48 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3560X-48PF-E	48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3560-X-24U-E	24 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3560-X-48U-E	48 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750X-24T-E	24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3750X-48T-E	48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3750X-24P-E	24 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Services feature se	12.2(53)SE2
Catalyst 3750X-48P-E	48 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3750X-48PF-E	48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 1100 W power supply; IP Services feature set	12.2(53)SE2
Catalyst 3750-X-24U-E	24 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750-X-48U-E	48 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750-X-12S-S	12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set	12.2(55)SE5
Catalyst 3750-X-24S-S	24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set	12.2(55)SE5
Catalyst 3750-X-12S-E	12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set	12.2(55)SE5
Catalyst 3750-X-24S-E	24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set	12.2(55)SE5
Catalyst 3750-X-24T-L	24 10/100/1000 Ethernet ports, StackWise Plus, 1 network module slot, 350 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3750-X-48T-L	48 10/100/1000 Ethernet ports, StackWise Plus, 1 network module slot, 350 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3750-X-24P-L	24 10/100/1000 PoE+1 ports, StackWise Plus, 1 network module slot, 715 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3750-X-48P-L	48 10/100/1000 PoE+2 ports, StackWise Plus, 1 network module slot, 715 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3750-X-48PF-L	48 10/100/1000 PoE+2 ports, StackWise Plus, 1 network module slot, 1100 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3750-X-24U-L	24 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750-X- 48U-L	48 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750-X-24T-S	24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3750-X-48T-S	48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3750-X-24P-S	24 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3750-X-48P-S	48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3750-X-48PF-S	48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 1100 W power supply; IP Base feature set1	12.2(53)SE2
Catalyst 3750-X-24U-S	24 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3750-X-48U-S	48 10/100/1000 UPOE ports (provides up to 60 W per port), StackWise Plus, StackPower, 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3560-X-24T-L	24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3560-X-48T-L	48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3560-X-24P-L	24 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3560-X-48P-L	48 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3560-X-48PF-L	48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; LAN Base feature set	12.2(53)SE2
Catalyst 3560-X-24U-L	24 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3560-X-48U-L	48 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100-W power supply	15.0(2)EZ
Catalyst 3560-X-24T-S	24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3560-X-48T-S	48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3560-X-24P-S	24 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3560-X-48P-S	48 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3560-X-48PF-S	48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; IP Base feature set	12.2(53)SE2
Catalyst 3560-X-24U-S	24 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100 W power supply	15.0(2)EZ
Catalyst 3560-X-48U-S	48 10/100/1000 UPOE ports (provides up to 60 W per port), 1 network module1 slot, 1100 W power supply	15.0(2)EZ
SFP Modules	100FX-SFP GE SFPLX/LH GE SFP SX 1000BASE-LX/LH 1000BASE-SX 1000BASE-ZX 1000BASE-BX10-D 1000BASE-BX10-U 1000BASE-T 100BASE-FX CWDM2 DWDM3 Note For a complete list of supported SFP modules, see the hardware installation guide or the data sheets at: http://www.cisco.com/en/US/products/ps10745/products_data_sheets_list.html	12.2(53)SE2
SFP+ Modules	SFP-10G-SR SFP-10G-LR SFP-10G-LRM SFP-H10GB CU1M SFP-H10GB CU3M SFP-H10GB CU5M	12.2(53)SE2
SFP+ Modules	SFP-10G-ER4	15.0(2)SE
Support for these SFP+ modules	Only version 02 (or later) of the CX15 cables are supported: SFP-H10GB-CU1M SFP-H10GB-CU3M SFP-H10GB-CU5M	12.2(53)SE2
SFP module patch cable6	CAB-SFP-50CM	12.2(53)SE2
Power supply modules	C3KX-PWR-1100WAC C3KX-PWR-715WAC C3KX-PWR-350WAC C3KX-PWR-440WDC C3KX-PSBAY-BLNK Note For power supply module descriptions and configurations supported on switch models, see the hardware installation guide.	12.2(53)SE2
C3KX-NM-10G 10-Gigabit Ethernet Network Module	Four SFP slots. Two slots support only 1-Gigabit SFP modules, two slots support either 1-Gigabit SFP or 10-Gigabit SFP+ modules.	12.2(53)SE2
C3KX-NM-1G 1-Gigabit Ethernet Network Module	Four 1-Gigabit SFP module slots.	12.2(53)SE2
C3KX-NM-10GT 10-Gigabit Ethernet Network Module	Two 10-Gigabit Ethernet (copper) ports. Note To configure the port speed to 1 Gigabit per second, use the hw-module switch global configuration command.	15.0(1)SE
eXpandable power system (XPS)	Cisco XPS 2200	12.2(55)SE1

1 PoE+ = Power over Ethernet, up to 30 W per port 2 CWDM = coarse wavelength-division multiplexer 3 DWDM = dense wavelength-division multiplexer 4 Only for Catalyst 3560-X and 3750-X switches 5 The CX1 cables are used with the OneX converters. 6 Only Catalyst 3560-X 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 be used in 1 Gigabit Ethernet SFP ports to connect two Catalyst 3560-X switches in a cascaded configuration. You can use the patch cable with the 10 G network module only on SFP ports 1 and 3 (not on SFP+ ports 2 and 4).

Table 2 Catalyst and Switches and Cisco Enhanced EtherSwitch Service Module 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 10 Gigabit Ethernet X2 ZR optical modules	Cisco IOS Release 12.2(35)SE2 Cisco IOS Release 12.2(40)SE Cisco IOS Release 12.2(50)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 SFP-10G-SR SFP-10G-LR For a complete list of supported SFPs and part numbers, see the data sheet: http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/product_data_sheet0900aecd805bbe67.html	Cisco IOS Release 12.2(35)SE2 Cisco IOS Release 12.2(53)SE
DOM4 support for these SFP modules.	X2-10GB-ER, X2-10GB-SR, X2-10GB-LR, X2-10GB-LRM, X2-10GB-ZR GLC-ZX-SM, GLC-BX-D, GLC-BX-U SFP-GE-S, SFP-GE-L, SFP-GE-Z All CWDM and DWDM SFP modules	Cisco IOS Release 12.2(46)SE
SFP module patch cable5	CAB-SFP-50CM	Cisco IOS Release 12.2(35)SE2
Supports OneX (CVR-X2-SFP10G) and these SFP+ modules	SFP-10G-SR= SFP-10G-LR= SFP-10G-LRM= Only version 02 or later CX16 cables support these SFP modules: SFP-H10GB-CU1M SFP-H10GB-CU3M SFP-H10GB-CU5M	12.2(53)SE
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
SM-D-ES2-487	48 10/100 ports, 2 SFP module slots	12.2(52)EX
SM-D-ES3-48-P7	48 10/100 ports with PoE, 2 SFP module slots	12.2(52)EX
SM-D-ES3G-48-P7	48 10/100/1000 with PoE, 2 SFP module slots	12.2(52)EX
SM-ES2-16-P7	15 10/100 ports with PoE, 1 10/100/1000 port with PoE	12.2(52)EX
SM-ES2-247	23 10/100 ports, 1 10/100/1000 port	12.2(52)EX
SM-ES2-24-P7	Layer 2-capable, 23 10/100 ports with PoE, 1 10/100/1000 port with PoE	12.2(52)EX
SM-ES3-16-P7	15 10/100 ports with PoE, 1 10/100/1000 port with PoE	12.2(52)EX
SM-ES3-24-P7	23 10/100 ports with PoE, 1 10/100/100 port with PoE	12.2(52)EX
SM-ES3G-16-P7	16 10/100/1000 ports with PoE	12.2(52)EX
SM-ES3G-24-P7	24 10/100/1000 ports with PoE	12.2(52)EX

1 PoE = Power over Ethernet. 2 SFP = small form-factor pluggable 3 CWDM = coarse wavelength-division multiplexer 4 DOM = digital optical monitoring 5 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. 6 The CX1 cables are used with the OneX converter and are supported in Cisco IOS Release 12.2(53)SE and later. 7 Cisco enhanced EtherSwitch service module

Device Manager System Requirements

Hardware

Table 3 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

•Windows 2000, XP, Vista, and Windows Server 2003.

•Internet Explorer 6.0, 7.0, Firefox 1.5, 2.0 or later with JavaScript enabled.

The device manager verifies the browser version when starting a session and does not require a plug-in.

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-X switch, all standby command switches must be Catalyst 3750-X switches.

For additional information about clustering, see Getting Started with Cisco Network Assistant, Release Notes for Cisco Network Assistant, the Cisco enhanced EtherSwitch service module documentation, the software configuration guide, and the command reference.

CNA Compatibility

Cisco IOS 15.0(2)EZ will be supported in a future release of the Cisco Network Assistant. Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Cisco 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

•"Finding the Software Version and Feature Set" section

•"Deciding Which Files to Use" section

•"Archiving Software Images" section

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

•"Upgrading a Switch by Using the Device Manager or Network Assistant" 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 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

---

Note If you have a service support contract and order a software license or if you order a switch, you receive the universal software image and a specific software license. If you do not have a service support contract, such as a SMARTnet contract, download the IP base image from Cisco.com. For Catalyst 3750-X and 3560-X switches, this image has the IP base and LAN base feature sets.A Catalyst 3750-X or 3560-X switch running the LAN base feature set supports only 255 VLANs.

---

The switches running the universal software images can use permanent and temporary software licenses. See the "Cisco IOS Software Activation Conceptual Overview" chapter in the Cisco IOS Software Activation Configuration Guide:
http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/12.4T/csa_book.html

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.

Catalyst 3750-X and 3560-X switches running payload-encryption images can encrypt management and data traffic. Switches running nonpayload-encryption images can encrypt only management traffic, such as a Secure Shell (SSH) management session.

•Management traffic is encrypted when SSH, Secure Socket Layer (SSL), Simple Network Management Protocol (SNMP), and other cryptographic-capable applications or protocols are enabled.

•Data traffic is encrypted when MACsec is enabled.

For more information about Catalyst 3750-X and 3560-X software licenses and available images, see the Cisco IOS Software Installation Document on Cisco.com:
http://www.cisco.com/en/US/products/ps10745/products_installation_and_configuration_guides_list.html

Table 4 Software Images 

Image	Filename	Description
Catalyst 3750-X and Catalyst 3560-X switches
IP base without payload encryption	c3750e-ipbasek9npe-tar.150-2.EZ.tar c3560e-ipbasek9npe-tar.150-2.EZ.tar	Layer 2 and basic Layer 3 features, SSH1 , SSL2 , and SNMPv33 , and Kerberos IP base image, as well as LAN base image with Layer 2 features
IP base with payload encryption	c3750e-ipbasek9-tar.150-2.EZ.tar c3560e-ipbasek9-tar.150-2.EZ.tar	Layer 2 and basic Layer 3 features, SSH, SSL, SNMPv3, Kerberos, and MACsec4 IP base image, as well as LAN base image with Layer 2 features
Universal without payload encryption	c3750e-universalk9npe-tar.150-2.EZ.tar c3560e-universalk9npe-tar.150-2.EZ.tar	All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 LAN base, IP base, and IP services software licenses
Universal with payload encryption	c3750e-universalk9-tar.150-2.EZ.tar c3560e-universalk9-tar.150-2.EZ.tar	All the supported universal image features, Kerberos, SSH, SSL, SNMPv3, and MACsec LAN base, IP base, and IP services software licenses
Network services module software	c3kx-sm10g-tar.150-2.EZ.tar	Supports service-module-specific features. Image must be compatible with the IOS image. See the "Catalyst 3750-X and 3560-X Network Services Module Software" section on page 15.

1 SSH = Secure Shell 2 SSL = Secure Socket Layer 3 SNMPv3 = Simple Network Management Protocol Version 3 4 MACsec = MAC security standard

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.

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/prod/collateral/iosswrel/ps8802/ps6969/ps1835/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:
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.html

---

Note When you upgrade a switch, a microcode upgrade is started when the switch is reloaded for the first time. The switch may take unusually long to start.
We recommend that you download the software on the switch using the archive download-sw /force-ucode-reload or archive download-sw /upgrade-ucode privileged EXEC command to shorten the reload time of the switch. For more information about using these commands, see the archive download-sw command in the Catalyst 3750-X and Catalyst 3560-X Switch Command Reference, Cisco IOS Release 15.0(2)EX guide on Cisco.com: 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 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:

a. If you are a registered customer, go to this URL and log in:
http://www.cisco.com/cisco/web/download/index.html

b. Navigate to Switches > LAN Switches - Access

c. Navigate to your switch model.

d. Click IOS Software, and select the latest IOS release.

e. Download the image you identified in Step 1.

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/c3750x-universal-tar.122-55.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 recovery procedures, see the "Troubleshooting" chapter in the software configuration guide for this release.

Installation Notes

Use these methods to assign IP information to your switch:

•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 Software Features

New in Cisco IOS Release 15.0(2)EZ

•Cisco IOS Release 15.0(1)EZ on the Catalyst 3750-X and 3560-X switches is now certified under the Federal Information Processing Standard Publication 140-2 (FIPS 140-2) and the Common Criteria for Information Technology Security Evaluation standard (Common Criteria or CC) EAL 2+.

•Cisco IOS Release 15.0(2)EZ on the Catalyst 3750-X and 3560-X switches has been submitted for certification under FIPS 140-2 and Common Criteria compliance with the US Government, Security Requirements for Network Devices (pp_nd_v1.0), version 1.0, dated 10 December 2010.

---

Note The images for the Cisco IOS Release 15.0(2)EZ on the Catalyst 3750-X and 3560-X switches are FIPS certified. For information about using FIPS certified images, see the "Boot Loader Upgrade and Image Verification for the FIPS Mode of Operation" section in the "Assigning the Switch IP Address and Default Gateway" chapter of the software configuration guide..

---

FIPS 140-2 is a cryptographic-focused certification, required by many government and enterprise customers, which ensures the compliance of the encryption and decryption operations performed by the switch to the approved FIPS cryptographic strengths and management methods for safeguarding these operations. For more information, see the following links:

–The security policy document at: http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/1401val2011.htm#1657

–The installation notes at: http://www.cisco.com/en/US/products/ps10745/prod_installation_guides_list.html

Common Criteria is an international standard (ISO/IEC 15408) for computer security certification. This standard is a set of requirements, tests, and evaluation methods that ensures that the Target of Evaluation complies with a specific Protection Profile or custom Security Target. For more information, see the security target document at:
http://www.niap-ccevs.org/st/vid10488/.

•Supports the Universal Power over Ethernet (UPoE) feature. Sources up to 60 W of power (2X 30W) over both signal and spare pairs of the RJ-45 Ethernet cable based on IEEE802.3at standards. Automatically detects UPoE-compliant power devices and negotiates power up to 60 W by using Layer 2 power negotiation protocols, such as CDP or LLDP. (Catalyst 3560-X and 3750-X switches).

For more information on UPoE, see Chapter 15, "Configuring Interface Characteristics" section "Univeral Power over Ethernet" of the software configuration guide on Cisco.com.

•Supports reserved entries for IPv6 Security ACEs in Access, Default, Routing, and VLAN templates. You can use IPv6 FHS features such as RA Guard, DHCP Guard, and NDP snooping by using the entries reserved for IPv6 Security Aces.

•Support for Right-To-Use (RTU) licensing, which allows you to upgrade from one license level to another by entering commands in the command line interface without interacting with the Cisco Product License Registration portal.

•Support for IOS IPv6 Host mode, which is compliant with the IPv6 Ready Logo Phase-2 Core Protocols test suite. (LAN Base image for Catalyst 3750-X and 3560-X switches.

•Support for OSPFv3 fast convergence. The OSPFv3 link-state advertisements (LSA) and shortest path first (SPF) throttling feature provides a dynamic method to slow down link-state advertisement updates in OSPFv3 during times of network instability. This feature also allows faster OSPFv3 convergence by providing LSA rate limiting in milliseconds. For more information, see the Configuring IPv6 Unicast Routing chapter of the software configuration guide on Cisco.com. (Switches running the IP Base image)

•Change in the CLI option relating to OSPFv2 LSA rate limiting. The all keyword is now removed from the timers throttle lsa global configuration command.

•Support for OSPFv3 authentication with IPsec. You can now use the IPsec secure socket API to authenticate OSPF for IPv6 (OSPFv3) packets to ensure that the packets are not altered and resent to the switch. For more information, see the Configuring IPv6 Unicast Routing chapter of the software configuration guide on Cisco.com.

•Support for first hop security (FHS) in IPv6. We support the following functions: IPv6 snooping, IPv6 FHS binding, neighbor discovery protocol (NDP) address gleaning, IPv6 data address gleaning, IPv6 dynamic host configuration protocol (DHCP) address gleaning, IPv6 device tracking, neighbor discovery (ND) Inspection, IPv6 port-based access list, IPv6 DHCP guard, IPv6 router advertisement (RA) guard, IPv6 source guard. For more information, see the Configuring IPv6 Unicast Routing chapter of the software configuration guide on Cisco.com.

•Support for specifying the VLAN to be used for Smart Install Management. The vstack startup-vlan command has been added. For more information, see the command reference on Cisco.com.

•Support for IPv6 multicast routing (switches running the IP Services image). For more information, see the Implementing IPv6 Multicast chapter of the software configuration guide on Cisco.com.

•Support for configurable MAC authentication bypass (MAB). You can configure how MAB authentication is performed for client MAC address that deviate from the expected standard format or where the RADIUS configuration requires that the user name and password to differ. For more information, see the Configuring IEEE 802.1x Port-Based Authentication chapter in the software configuration guide on Cisco.com.

•Support for TrustSec Secure Group Access (SGA) - Secure Group Tagging (SGT) / Secure Group Access Control List (SGACL). For more information, see the Cisco TrustSec chapter in the software configuration guide. (Catalyst 3750-X and 3560-X switches)

•Support for IKEv2 and IPSecv3 protocols. (IP Base image for Catalyst 3750-X, 3560-X)

•Support for Resilient Ethernet Protocol (REP) is added for the IP Base package. REP is a Cisco proprietary protocol that provides an alternative to Spanning Tree Protocol (STP) to control network loops, handle link failures, and improve convergence time in ring topologies. REP controls a group of ports connected in a segment, ensures that the segment does not create any bridging loops, and responds to link failures within the segment. REP also supports VLAN load balancing. (IP Base image for Catalyst 3750-X, 3560-X)

•Support for stack power is now extended to the LAN Base license. (Catalyst 3750-X switch)

•Support for Cisco TrustSec SXP version 2, syslog messages, and SNMP support is now extended to the LAN Base license. (Catalyst 3560-X and 3750-X switches)

•Support for port security on Etherchannels. For more information, see the Configuring Port-Based Traffic Control chapter in the software configuration guide.

•Support for IP Source Guard on Etherchannels. For more information, see the Configuring DHCP and IP Source Guard chapter in the software configuration guide.

•Support for SFP-10G-ER (10GBASE-ER SFP+ transceiver module (SMF, 1550-nm, LC duplex connector). (Catalyst 3560-X and 3750-X switches)

Minimum Cisco IOS Release for Major Features

Table 5 lists the minimum software release after the first release of required to support the major features on the switches. The first release of the Catalyst 3750-X sand 3560-X switches was Cisco IOS Release 12.2(53)SE2).

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

Feature	Minimum Cisco IOS Release Required	Catalyst Switch Support
Critical voice VLAN	15.0(1)SE	3750-E, 3560-E 3750-X, 3560-X
NEAT enhancement to control access to the supplicant port	15.0(1)SE	3750-E, 3560-E 3750-X, 3560-X
Cisco TrustSec SXP version 2, syslog messages, and SNMP support	15.0(1)SE	3750-E, 3560-E 3750-X, 3560-X
Auto Smartports improved device classification	15.0(1)SE	3750-E, 3560-E 3750-X, 3560-X
Device Sensor	15.0(1)SE	3750-E, 3560-E 3750-X, 3560-X
Built-in Traffic Simulator using Cisco IOS IP SLAs video operations	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Cisco Mediatrace support	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Cisco performance monitor	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
EnergyWise Phase 2.5	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Smart logging	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Protocol storm protection	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
VACL Logging	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Smart Install 3.0	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Auto Smartports enhancements to enable auto-QoS on a digital media player.	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Memory consistency check routines	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Call Home support	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Support for 16 static routes on SVIs on the LAN Base feature set	12.2(58)SE1	3750-X, 3560-X
SDM template supporting more indirect routes	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
NTP version 4	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
DHCPv6 bulk-lease query and DHCPv6 relay source configuration	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Rolling stack upgrade	12.2(58)SE1	3750-X, 3750-C
NSF IETF mode for OSPFv2 and OSPFv3 (IP services feature set)	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
RADIUS, TACACS+, and SSH/SCP over IPv6	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
VRRP for IPv4	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
IETF IP-MIB and IP-FORWARD-MIB(RFC4292 and RFC4293) updates	12.2(58)SE1	3750-E, 3560-E 3750-X, 3560-X
Auto-QoS enhancements that add automatic configuration classification of traffic flow from video devices.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
AutoSmartports enhancements—support for global macros, last-resort macros, event trigger control, access points, EtherChannels, auto-QoS with Cisco Medianet, and IP phones.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
CDP and LLDP enhancements for exchanging location information with video end points.s.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
Smart Install enhancements including client backup files, zero-touch replacement for clients with the same product-ID, and automatic generation of the image_list file.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
Dynamic creation or attachment of an auth-default ACL on a port with no configured static ACLs.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
VLAN assignment on a port configured for multi-auth mode.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
EEM in IP base image.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
IP base support for OSPF routed access.	12.2(55)SE	3750-E, 3560-E 3750-X, 3560-X
Cisco TrustSec SXP.	12.2(55)SE 12.2(53)SE2	3750-E, 3560-E 3750-X, 3560-X

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.

Cisco IOS Limitations

•"Address Resolution Protocol" section

•"Cisco Transceiver Modules and SFP Modules" section

•"Configuration" section

•"EtherChannel" section

•"IEEE 802.1x Authentication" section

•"Multicasting" section

•"PoE or PoE+" section

•"QoS" section

•"RADIUS" section

•"Routing" section

•"SPAN and RSPAN" section

•"Spanning Tree Protocol" section

•"Stacking (Catalyst 3750-X )" section

•"Stack Power (Catalyst 3750-X only)" section

•"VLANs" section

•"TrustSec" section

Address Resolution Protocol

•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 Transceiver Modules and SFP Modules

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

•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

•If a half-duplex port running at 10 Mb/s receives frames with Inter-Packet Gap (IPG) that do not conform to Ethernet specifications, the switch might stop sending packets.

There is no workaround. (CSCec74610) (Catalyst 3750-X switches)

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

The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090)

The workaround is to delete any unnecessary files in flash memory, delete the temporary files created as part of the failed upgrade, and try the MCU upgrade again. (CSCtd75400)

•Identity Services Engine (ISE) is not available on Catalyst 2000 series switches.

•The device-sensor accounting global configuration command is not available on Catalyst 2000 series switches.

Diagnostics

•(Catalyst 3750-X or 3560-X switches) When you enter the test cable-diagnostics tdr interface or the show cable-diagnostics tdr interface privileged EXEC command on an interface to determine the length of a connected cable, the cable length might be reported as N/A. This can occur when there is no link, a 10 Mb/s link, or a 100 Mb/s link, even though there are no cable faults. Cable length is reported correctly when a 1 Gb/s link is active on the interface.

The workaround to verify the cable length is to enter the commands when a Gigabit link is active on the interface or after disconnecting the far end of the cable. (CSCte43869)

EtherChannel

•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

•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

•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 or PoE+

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

•(Catalyst 3750-X or 3560-X switches) When a powered device (such as an IP phone) connected to a PoE+ port restarts and sends a CDP or LLDP packet with a power TLV, the switch locks to the power-negotiation protocol of that first packet. The switch does not respond to power requests from the other protocol. For example, if the switch is locked to CDP, it does not provide power to devices that send LLDP requests. If CDP is disabled after the switch has locked on it, the switch does not respond to LLDP power requests and can no longer power on any accessories.

The workaround is to turn the powered device off and then on again.

QoS

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

•If QoS is enabled on a switch and the switch has a high volume of incoming packets with a maximum transmission unit (MTU) size greater than 1512 bytes, the switch might reload.

Use one of these workarounds:

–Use the default buffer size.

–Use the mls qos queue-set output qset-id buffers allocation1 ... allocation4 global configuration command to allocate the buffer size. The buffer space for each queue must be at least 10 percent. (CSCsx69718) (Catalyst 3750-X switches)

•If you configure a large number of input interface VLANs in a class map, a traceback message similar to this might appear:

01:01:32: %BIT-4-OUTOFRANGE: bit 1321 is not in the expected range of 0 to 1024

There is no impact to switch functionality.

There is no workaround. (CSCtg32101)

RADIUS

•RADIUS change of authorization (COA) reauthorization is not supported on the critical auth VLAN.

There is no workaround. (CSCta05071)

Routing

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

Smart Install

•When upgrading switches in a stack, the director cannot send the correct image and configuration to the stack if all switches in the stack do not start at the same time. A switch in the stack could then receive an incorrect image or configuration.

The workaround is to use an on-demand upgrade to upgrade switches in a stack by entering the vstack download config and vstack download image commands. (CSCta64962)

•When you upgrade a Smart Install director to Cisco IOS Release 12.2(55)SE but do not upgrade the director configuration, the director cannot upgrade client switches.

When you upgrade the director to Cisco IOS Release 12.2(55)SE, the workaround is to also modify the configuration to include all built-in, custom, and default groups. You should also configure the tar image name instead of the image-list file name in the stored images. (CSCte07949)

•Backing up a Smart Install configuration could fail if the backup repository is a Windows server and the backup file already exists in the server.

The workaround is to use the TFTP utility of another server instead of a Windows server or to manually delete the existing backup file before backing up again. (CSCte53737)

•In a Smart Install network with the backup feature enabled (the default), the director sends the backup configuration file to the client during zero-touch replacement. However, when the client is a switch in a stack, the client receives the seed file from the director instead of receiving the backup configuration file.

The workaround, if you need to configure a switch in a stack with the backup configuration, is to use the vstack download config privileged EXEC command so that the director performs an on-demand upgrade on the client.

–When the backup configuration is stored in a remote repository, enter the location of the repository.

–When the backup file is stored in the director flash memory, you must manually set the permissions for the file before you enter the vstack download config command. (CSCtf18775)

•If the director in the Smart Install network is located between an access point and the DHCP server, the access point tries to use the Smart Install feature to upgrade even though access points are not supported devices. The upgrade fails because the director does not have an image and configuration file for the access point.

There is no workaround. (CSCtg98656)

•When a Smart Install director is upgrading a client switch that is not Smart Install-capable (that is, not running Cisco IOS Release 12.2(52)SE or later), the director must enter the password configured on the client switch. If the client switch does not have a configured password, there are unexpected results depending on the software release running on the client:

–When you select the NONE option in the director CLI, the upgrade should be allowed and is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.

–When you enter any password in the director CLI, the upgrade should not be allowed, but it is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.

There is no workaround. (CSCth35152)

SPAN and RSPAN

•When the RSPAN feature is configured on a switch, CDP packets received from the RSPAN source ports are tagged with the RSPAN VLAN ID and forwarded to trunk ports carrying the RSPAN VLAN. When this happens, a switch that is more than one hop away incorrectly lists the switch that is connected to the RSPAN source port as a CDP neighbor.

This is a hardware limitation. The workaround is to disable CDP on all interfaces carrying the RSPAN VLAN on the device connected to the switch. (CSCeb32326)

•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 workaround is to configure aggressive UDLD. (CSCsh70244).

•(Catalyst 3650-X and 3750-X switches) When you enter the show monitor privileged EXEC command the monitor source port output is incorrect. This situation occurs only if the monitor source port(s) is a pluggable Gigabit module and you set any source port combination, except when just using a single Gigabit port on the pluggable module as the source port.

This is a cosmetic issue and the workaround is to use the show platform monitor session privileged EXEC command to display the correct source ports. (CSCtn67868)

Spanning Tree Protocol

•CSCtl60247

When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.

There is no workaround.

Stacking (Catalyst 3750-X )

•When a switch stack is running 802.1x single host mode authentication and has filter-ID or per-user policy maps applied to an interface, these policies are removed if a master switchover occurs. Even though the output from the show ip access-list privileged EXEC command includes these ACLs, the policies are not applied.

The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface. (CSCsx70643)

•Where there is a mixed hardware stack with Catalyst 3750-X or 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-X or 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-X or 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-X or 3750-E switches, when the stack reloads, the Catalyst 3750-X or 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)

•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 (CSCsk96058)

•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. (CSCsl64124)

•When the switch stack is in the HSRP active state and a master changeover occurs, you cannot ping the stack by using an HSRP virtual IP address.

There is no workaround. (CSCth00938)

Stack Power (Catalyst 3750-X only)

•When a power stack has been configured in redundant mode, which is not the default, and then split by either removing cables or disabling StackPower ports, the newly created power stack has the same mode as the former power stack, but this is not shown in the configuration file.

The workaround when you are forming power stack topologies if the power stack mode is not the default (power sharing), you should also configure the power stack mode on the new power stacks by entering the mode redundant power-stack configuration command. (CSCte33875)

VLANs

•If the number of VLANs times the number of trunk ports exceeds the recommended limit of 13,000, the switch can fail.

The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)

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

•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. (CSCsk65142)

•When many VLANs are configured on the switch, high CPU utilization occurs when many links are flapping at the same time.

The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)

TrustSec

The following guidelines and limitations apply to configuring Cisco TrustSec SGT and SGACL on the Catalyst 3750-X switch:

•You cannot statically map an IP-subnet to an SGT. You can only map IP addresses to an SGT. When you configure IP address-to-SGT mappings, the IP address prefix must be 32.

•If a port is configured in Multi-Auth mode, all hosts connecting on that port must be assigned the same SGT. When a host tries to authenticate, its assigned SGT must be the same as the SGT assigned to a previously authernticated host. If a host tries to authenticate and its SGT is different from the SGT of a previously authenticated host, the VLAN port (VP) to which these hosts belong is error-disabled.

•Cisco TrustSec enforcement is supported only on up to eight VLANs on a VLAN-trunk link. If there are more than eight VLANs configured on a VLAN-trunk link and Cisco TrustSec enforcement is enabled on those VLANs, the switch ports on those VLAN-trunk links will be error-disabled.

•The switch cannot assign an SGT based on SXP listening; it can only forward the SXP bindings through the SXP protocol.

•Port-to-SGT mapping can be configured only on Cisco TrustSec links (that is, switch-to-switch links). Port-to-SGT mapping cannot be configured on host-to-switch links.

When port-to-SGT mapping is configured on a port, an SGT is assigned to all ingress traffic on that port. There is no SGACL enforcement for egress traffic on the port.

•SGT/SGACL is supported on Cisco Catalyst 3750-X and 3650-X series switches with all network uplink modules: C3KX-NM-1G, C3KX-NM-10G, C3KX-NM-10GT and C3KX-SM-10G. The C3KX-SM-10G is only required for MACsec on the uplinks.

Device Manager Limitations

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

Hardware Limitations

C3KX-SM-10G Network Module (Catalyst 3750-X and 3560-X only)

•NetFlow Data Export (NDE) fails when the IP address specified by the destination keyword belongs to a network that is connected to the Ethernet management port (FastEthernet0) on the switch.

There is no workaround. (CSCtt05810)

•Cisco Trust Security (CTS) MACsec cannot be configured on the C3KX-SM-10G service module until the POST test has been completed. Wait approximately 45 seconds after the module is inserted before you configure CTS MACsec on the port. (CSCuc20819)

Important Notes

•"Switch Stack Notes" section

•"Control Plane Protection" section

•"Cisco IOS Notes" section

•"Device Manager Notes" section

Switch Stack Notes

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

•The Catalyst 3560-X switch 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.

Control Plane Protection

Catalyst 3750-X, , and 3560-X switches internally support up to 16 different control plane queues. Each queue is dedicated to handling specific protocol packets and is assigned a priority level. For example, STP, routed, and logged packets are sent to three different control plane queues, which are prioritized in corresponding order, with STP having the highest priority. Each queue is allocated a certain amount of processing time based on its priority. The processing-time ratio between low-level functions and high-level functions is allocated as 1-to-2. Therefore, the control plane logic dynamically adjusts the CPU utilization to handle high-level management functions as well as punted traffic (up to the maximum CPU processing capacity). Basic control plane functions, such as the CLI, are not overwhelmed by functions such logging or forwarding of packets.

Cisco IOS Notes

•Unlike other platforms, the response to an Energywise query on a Catalyst 3750-X or 3560-X is the actual switch power consumption and not a fixed number.

•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, 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

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

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

Related Documentation

User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.

with complete information about the switch are available from these Cisco.com sites:

Catalyst 3750-X
http://www.cisco.com/en/US/products/ps10745/tsd_products_support_series_home.html

Catalyst 3560-X
http://www.cisco.com/en/US/products/ps10744/tsd_products_support_series_home.html

These documents provide complete information about the switches:

•Release Notes for the Catalyst 3750-X and Catalyst 3560-X

•Catalyst 3750-X and 3560-X Switch Software Configuration Guide

•Catalyst 3750-X and 3560-X Switch Command Reference

•Cisco IOS Software Installation Document.

•Catalyst 3750-X and 3560-X Switch Getting Started Guide

•Catalyst 3750-X and 3560-X Switch Hardware Installation Guide

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

•Installation Notes for the Catalyst 3750-X and 3560-X Switch Power Supply Modules

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

•Installation Notes for the Catalyst 3750-X and 3560-X Switch Network Modules

•Auto Smartports Configuration Guide

•Cisco EnergyWise Configuration Guide

•Smart Install Configuration Guide

•Information about Cisco SFP, SFP+, and GBIC modules is available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.html

SFP 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

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

These documents have information about the Cisco enhanced EtherSwitch service modules:

•Connecting Cisco Enhanced EtherSwitch Service Modules to the Network:
http://www.cisco.com/en/US/docs/routers/access/interfaces/nm/hardware/installation/guide/eesm_hw.html

•Cisco Enhanced EtherSwitch Service Modules Configuration Guide:
http://www.cisco.com/en/US/docs/routers/access/interfaces/software/feature/guide/eesm_sw.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

---

This document is to be used in conjunction with the documents listed in the "Obtaining Documentation and Submitting a Service Request" section.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2011-2013 Cisco Systems, Inc. All rights reserved.