Guest

Cisco IOS 15.0SE

Release Notes for the Catalyst 3750, 3560, 2960-S, and 2960 Switches, Cisco IOS Release 15.0(1)SE and Later

  • Viewing Options

  • PDF (639.6 KB)
  • Feedback
Release Notes for the Catalyst 3750, 3560, 2960-S, and 2960 Switches, Cisco IOS Release 15.0(1)SE and Later

Table Of Contents

Release Notes for the Catalyst 3750, 3560, 2960-S, and 2960 Switches, Cisco IOS Release 15.0(1)SE and Later

Contents

System Requirements

Supported Hardware

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

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Cisco IOS Limitations

Configuration

Ethernet

EtherSwitch Modules

Fallback Bridging

HSRP

IP

IP Telephony

MAC Addressing

Management

Multicasting

Power

QoS

RADIUS

Routing

Smart Install

SPAN and RSPAN

Spanning Tree Protocol

Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)

Trunking

VLAN

Device Manager Limitations

Important Notes

Switch Stack Notes

Catalyst 2960-S Control Plane Protection

Cisco IOS Notes

Device Manager Notes

Open Caveats

Resolved Caveats

Caveats Resolved in Cisco IOS Release 15.0(1)SE3

Caveats Resolved in Cisco IOS Release 15.0(1)SE1

Caveats Resolved in Cisco IOS Release 15.0(1)SE

Documentation Updates

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Software Configuration Guides

Information Added to the "Administering the Switch" Chapter

Correction to the "Clustering Switches" Chapter

Correction to the "Configuring Network Security with ACLs" Chapter

Correction to the "Managing Switch Stacks" Chapter

Correction to the "Unsupported Commands" Chapter

Information Added to the "Configuring IEEE 802.1x Port-Based Authentication" Chapter

Update to the Catalyst 3750 Software Configuration Guide

Update to the Catalyst 3750 and 2960-S Software Configuration Guide

Updates to the Catalyst 2960 and 2960-S Software Configuration Guide

Correction to the "Configuring SDM Templates" Chapter

Correction: the "Configuring IPv6 ACLs" Chapter

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Command References

authentication event

dot1x supplicant controlled transient

Updates to the System Message Guides

New System Messages

Modified System Messages

Deleted System Messages

Updates to the Catalyst 2960 Hardware Installation Guide

Update to the Getting Started Guide

Update to the Catalyst 2960-S Switch Getting Started Guide

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for the Catalyst 3750, 3560, 2960-S, and 2960 Switches, Cisco IOS Release 15.0(1)SE and Later


Revised December 17, 2012

Cisco IOS Release 15.0(1)SE runs on Catalyst 3750, 3560, 2960-S, and 2960 switches and on Cisco EtherSwitch service modules.


Note Not all Catalyst 3750 and 3560 switches can run this release. These models are not supported in Cisco IOS Release 12.2(58)SE1 and later: WS-C3560-24TS, WS-C3560-24PS. WS-C3560-48PS, WS-C3560-48TS, WS-C3750-24PS, WS-C3750-24TS, WS-C3750-48PS, WS-C3750-48TS, WS-3750G-24T, WS-C3750G-12S, WS-C3750G-24TS, WS-C3750G-16TD. For ongoing maintenance rebuilds for these models, use Cisco IOS Release 12.2(55)SE and later (SE1, SE2, and so on).


The Catalyst 3750 switches and the Cisco EtherSwitch service modules support stacking through Cisco StackWise technology. The Catalyst 3560 and 2960 switches do not support switch stacking. Catalyst 2960-S does support 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 15.0(1)SE and any limitations, restrictions, and caveats that apply to the releases. 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

Upgrading the Switch Software

Installation Notes

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Important Notes

Open Caveats

Resolved Caveats

Documentation Updates

Obtaining Documentation and Submitting a Service Request

System Requirements

Supported Hardware

Device Manager System Requirements

Cluster Compatibility

CNA Compatibility

Supported Hardware

Table 1 Catalyst 3750 and Cisco EtherSwitch Service Modules Supported  

Switch
Description
Supported by Minimum Cisco IOS Release

Catalyst 3750G-24WS-S25

24 10/100/1000 PoE1 ports, 2 SFP2 module slots, and an integrated wireless LAN controller supporting up to 25 access points.

Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE

Catalyst 3750G-24WS-S50

24 10/100/1000 PoE ports, 2 SFP module slots, and an integrated wireless LAN controller supporting up to 50 access points

Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE

Catalyst 3750-24FS

24 100BASE-FX ports and 2 SFP module slots

Cisco IOS Release 12.2(25)SEB

Catalyst 3750G-24PS

24 10/100/1000 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3750G-24TS-1U

24 10/100/1000 Ethernet ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3750G-48PS

48 10/100/1000 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3750G-48TS

48 10/100/1000 Ethernet ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3750V2-24PS

24 10/100 PoE ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3750V2-24TS

24 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3750V2-48PS

48 10/100 PoE ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3750V2-48TS

48 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3750V2-24FS

24 SFP module slots and 2 SFP module slots

Cisco IOS Release 12.2(55)EY

NME-16ES-1G3

16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide

Cisco IOS Release 12.2(25)SEC

NME-16ES-1G-P4

16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide

Cisco IOS Release 12.2(25)EZ

NME-X-23ES-1G4

23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide

Cisco IOS Release 12.2(25)SEC

NME-X-23ES-1G-P4

23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide

Cisco IOS Release 12.2(25)EZ

NME-XD-24ES-1S-P4

24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide

Cisco IOS Release 12.2(25)EZ

NME-XD-48ES-2S-P4

48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide

Cisco IOS Release 12.2(25)EZ

1 PoE = Power over Ethernet

2 SFP = small form-factor pluggable

3 Cisco EtherSwitch service module


Table 2 Catalyst 3560 Switches Supported 

Switch
Description
Supported by Minimum Cisco IOS Release

Catalyst 3560-8PC

8 10/100 PoE ports and 1 dual-purpose port1 (one 10/100/1000BASE-T copper port and one SFP module slot)

Cisco IOS Release 12.2(35)SE

Catalyst 3560G-24PS

24 10/100 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3560G-24TS

24 10/100/1000 Ethernet ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3560G-48PS

48 10/100/1000 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3560G-48TS

48 10/100/1000 Ethernet ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3560-12PC Compact Switch

12 Ethernet 10/100 ports with PoE and 1 dual-purpose 10/100/1000 or SFP uplink

Cisco IOS Release 12.2(50)SE

Catalyst 3560V2-24PS

24 10/100 PoE ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3560V2-24TS

24 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3560V2-48PS

48 10/100 PoE ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3560V2-48TS

48 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

Catalyst 3560V2-24TS-SD

24 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(50)SE1

1 Each uplink port is considered a single interface with dual front ends (RJ-45 connector and SFP module slot). The dual front ends are not redundant interfaces, and only one port of the pair is active.


Table 3 Catalyst 2960, and 2960-S Switches Supported  

Switch
Description
Supported by Minimum Cisco IOS Release

Catalyst 2960-48PST-S

48 10/100 PoE ports, 2 10/100/1000 ports, and 2 SFP module slots

Cisco IOS Release 12.2(50)SE2

Catalyst 2960-24PC-S

24 10/100 PoE ports and 2 dual-purpose ports
(2 10/100/1000BASE-T copper ports and 2 SFP module slots)

Cisco IOS Release 12.2(50)SE2

Catalyst 2960-24LC-S

24 10/100 ports (8 of which are PoE) and 2 dual-purpose ports
(2 10/100/1000BASE-T copper ports and 2 SFP module slots)

Cisco IOS Release 12.2(50)SE2

Catalyst 2960-8TC-S

8 10/100 ports and 1 dual-purpose port3 (1 10/100/1000BASE-T copper port and1 SFP module slot)

Cisco IOS Release 12.2(46)SE

Catalyst 2960-48TT-S

48 10/100 ports and 1 10/100/1000 ports

Cisco IOS Release 12.2(46)SE

Catalyst 2960-48PST-L

48 10/100 PoE ports, 1 10/100/1000 ports and 2 SFP module slots

Cisco IOS Release 12.2(46)SE

Catalyst 2960-24-S

24 10/100 BASE-TX Ethernet ports

Cisco IOS Release 12.2(37)EY

Catalyst 2960-24TC-S

24 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots)

Cisco IOS Release 12.2(37)EY

Catalyst 2960-48TC-S

48 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots)

Cisco IOS Release 12.2(37)EY

Catalyst 2960PD-8TT-L

8 10/100 ports and 1 10/100/1000 port that receives power

Cisco IOS Release 12.2(44)SE

Catalyst 2960-8TC-L

8 10/100 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)

Cisco IOS Release 12.2(35)SE

Catalyst 2960G-8TC-L

7 10/100/1000 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)

Cisco IOS Release 12.2(35)SE

Catalyst 2960-24LT-L

24 10/100 ports, 8 of which are PoE, and 2 10/100/1000 ports

Cisco IOS Release 12.2(44)SE

Catalyst 2960-48TC-L

48 10/100BASE-TX Ethernet ports and 2 dual-purpose ports

Cisco IOS Release 12.2(25)FX

Catalyst 2960-24TC-L

24 10/100BASE-TX Ethernet ports and 2 dual-purpose ports

Cisco IOS Release 12.2(25)FX

Catalyst 2960-24PC-L

24 10/100 Power over Ethernet (PoE) ports and 2 dual-purpose ports (2 10/100/1000BASE-T copper ports and 2 small form-factor pluggable [SFP] module slots)

Cisco IOS Release 12.2(44)SE

Catalyst 2960-24TT-L

24 10/100BASE-T Ethernet ports and 2 10/100/1000BASE-T Ethernet ports

Cisco IOS Release 12.2(25)FX

Catalyst 2960-48TT-L

48 10/100BASE-T Ethernet ports 2 10/100/1000BASE-T Ethernet ports

Cisco IOS Release 12.2(25)FX

Catalyst 2960G-24TC-L

24 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots)

Cisco IOS Release 12.2(25)FX

Catalyst 2960G-48TC-L

48 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots)

Cisco IOS Release 12.2(25)SEE

Catalyst 2960S-48FPD-L1

48 10/100/1000 Power over Ethernet Plus (PoE+) ports (PoE budget of 740 W) and 2 SFP+2 module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-48LPD-L1

48 10/100/1000 PoE+ ports (PoE budget of 370 W) and 2 SFP+ module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-24PD-L1

24 10/100/1000 PoE+ ports (PoE budget of 370 W) and 2 SFP+ module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-48TD-L1

48 10/100/1000 ports and 2 SFP+ module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-24TD-L1

24 10/100/1000 ports and 2 SFP+ module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-48FPS-L1

48 10/100/1000 PoE+ ports (PoE budget of 740 W) and 4 SFP module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-48LPS-L1

48 10/100/1000 PoE+ ports (PoE budget of 370 W) and 4 SFP module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-24PS-L1

24 10/100/1000 PoE+ ports (PoE budget of 370 W) and 4 SFP module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-48TS-L1

48 10/100/1000 ports and 4 SFP module slots

Cisco IOS Release 12.2(53)SE1

Catalyst 2960S-24TS-L1

24 10/100/1000 ports and 4 SFP module slots

Cisco IOS Release 12.2(53)SE1

1 Support Cisco FlexStack technology.
2 SFP+ = 10 Gigabit fiber uplink.

Table 4 Other Supported Hardware 

Switch
Description
Supported by Minimum Cisco IOS Release

SFP modules (Catalyst 3750 and 3560)

1000BASE-CWDM1 , -LX, SX, -T, -ZX

100BASE-FX MMF2

Support for eight additional DWDM SFP optical modules. For a complete list of supported SFPs and part numbers, see the data sheet:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps5023/product_data_sheet0900aecd80371991.html

Cisco IOS Release 12.2(18)SE

Cisco IOS Release 12.2(20)SE

 

SFP modules (Catalyst 2960)

1000BASE-BX, -CWDM, -LX/LH, -SX, -ZX

100BASE-BX, FX, -LX

Cisco IOS Release 12.2(25)FX

 

XENPAK modules3

XENPAK-10-GB-ER, XENPAK-10-GB-LR, and XENPAK-10-GB-SR

Cisco IOS Release 12.2(18)SE

Redundant power systems

Cisco RPS 675 Redundant Power System

Cisco RPS 300 Redundant Power System (supported only on the Catalyst 2960 switch)

Cisco Redundant Power System 2300

Supported on all software releases

Supported on all software releases


Cisco IOS Release 12.2(35)SE and later

1 CWDM = coarse wavelength-division multiplexer

2 MMF = multimode fiber

3 XENPAK modules are only supported on the Catalyst 3750G-16TD switches.


Device Manager System Requirements

Hardware Requirements

Software Requirements

Hardware Requirements

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

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 switch, all standby command switches must be Catalyst 3750 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, the command reference, and the Cisco EtherSwitch service module feature guide.

CNA Compatibility

Cisco IOS 12.2(50)SE and later is only compatible with Cisco Network Assistant (CNA) 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

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

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 For Catalyst 3750 and 3560 switches and the Cisco EtherSwitch service modules, 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 image or IP services image) and does not change if you upgrade the software image.


You can also use the dir filesystem: privileged EXEC command to see the directory names of other software images that you might have stored in flash memory.

Deciding Which Files to Use

The upgrade procedures in these release notes describe how to perform the upgrade by using a combined tar file. This file contains 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 6 Cisco IOS Software Image Files 

Filename

Description

c3750-ipbasek9-tar.150-1.SE.tar

Catalyst 3750 IP base cryptographic image and device manager files. This image has the Kerberos, SSH1 , Layer 2+, and basic Layer 3 routing features. This image also runs on the Cisco EtherSwitch service modules.

c3750-ipservicesk9-tar.150-1.SE.tar

Catalyst 3750 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features. This image also runs on the Cisco EtherSwitch service modules.

c3560-ipbasek9-tar.150-1.SE.tar

Catalyst 3560 IP base cryptographic image and device manager files. This image has the Kerberos, SSH, and Layer 2+, and basic Layer 3 routing features.

c3560-ipservicesk9-tar.150-1.SE.tar

Catalyst 3560 IP services cryptographic image and device manager files. This image has the Kerberos, SSH, Layer 2+, and full Layer 3 features.

c2960-lanbasek9-tar.150-1.SE.tar

Catalyst 2960 cryptographic image file and device manager files. This image has the Kerberos and SSH features.

c2960-lanlitek9-tar.150-1.SE.tar

Catalyst 2960 LAN lite cryptographic image file and device manager files.

c2960s-universalk9-tar.150-1.SE.tar

LAN Base and LAN Lite crypto image with device manager

1 SSH = Secure Shell.


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

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 6 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, then select the latest IOS release.

Download the image you identified in Step 1.


Caution If you are upgrading a Catalyst 3750 switch that is running a release earlier than Cisco IOS Release 12.1(19)EA1c, this release includes a bootloader upgrade. The bootloader can take up to 1 minute to upgrade the first time that the new software is loaded. Do not power cycle the switch during the bootloader upgrade.

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.

The /allow-feature-upgrade option allows installation of an image with a different feature set (for example, upgrade from the IP base image to the IP services image).

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/c3750-ipservices-tar.122-50.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

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. It also supplies 60 W power on ports without CDP/LLDP negotiations (for devices that do not support the required UPoE TLV). (Catalyst 2960-C and 3560- C switches)

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

Support for critical voice VLAN so that when authentication is enabled and the access control server is not available, traffic from the host tagged with the voice VLAN is put into the configured voice VLAN for the port.

See the "Documentation Updates" section.

Network Edge Access Topology (NEAT) enhancement to control access to the supplicant port during authentication.

See the "Documentation Updates" section.

SXP version 2, syslog messages and SNMP support for Cisco TrustSec Security Group Tag (SGT) Exchange Protocol (SxP) (Catalyst 3750 and 3560 only).

For more information about Cisco TrustSec, see the "SGT Exchange Protocol over TCP (SXP)" chapter in the Cisco TrustSec Switch Configuration Guide at this URL:
http://www.cisco.com/en/US/docs/switches/lan/trustsec/configuration/guide/sxp_config.html

Auto Smartport feature with improved device classification capabilities and accuracy, increased device visibility, and enhanced macro management. The device classifier is enabled by default, and can classify devices based on DHCP options. For more information, see the Auto Smartports Configuration Guide for this release.

Device Sensor - Scalable network embedded sensor features for identification and classification of devices on the network.

For more information on Device Sensor, see the Device Sensor Guide at this URL: http://www.cisco.com/en/US/docs/switches/lan/catalyst3750/software/release/15.0_1_se/
device_sensor/guide/sensor_guide.html

Minimum Cisco IOS Release for Major Features

Table 7 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, 2960-S, and 2960 switches and the Cisco EtherSwitch service modules.

Table 7 Catalyst 3750, and 3560, 2960-S and 2960 Switches and Cisco EtherSwitch Service Module Features and the Minimum Cisco IOS Release Required 

Feature
Minimum Cisco IOS Release Required
Catalyst Switch Support

Critical voice VLAN

15.0(1)SE

3750, 3560, 2960-S, 2960

NEAT enhancement to control access to the supplicant port

15.0(1)SE

3750, 3560, 2960-S, 2960

Cisco TrustSec SXP version 2, syslog messages, and SNMP support

15.0(1)SE

3750 and 3560

Auto Smartports improved device classification

15.0(1)SE

3750, 3560, 2960-S, 2960

Device Sensor

15.0(1)SE

3750, 3560

Built-in Traffic Simulator using Cisco IOS IP SLAs video operations

12.2(58)SE1

3750, 3560

Cisco Mediatrace support

12.2(58)SE1

3750, 3560

Cisco performance monitor

12.2(58)SE1

3750, 3560

EnergyWise Phase 2.5

12.2(58)SE1

3750, 3560, 2960-S, 2960

Smart logging

12.2(58)SE1

3750, 3560

Protocol storm protection

12.2(58)SE1

3750, 3560, 2960-S, 2960

VACL Logging

12.2(58)SE1

3750, 3560

Smart Install 3.0

12.2(58)SE1

3750, 3560, 2960-S, 2960

Auto Smartports enhancements to enable auto-QoS on a digital media player.

12.2(58)SE1

3750, 3560, 2960-S, 2960

Memory consistency check routines

12.2(58)SE1

2960-S

Call Home support

12.2(58)SE1

3750, 3560, 2960-S, 2960

NTP version 4

12.2(58)SE1

3750, 3560, 2960-S, 2960

DHCPv6 bulk-lease query and DHCPv6 relay source configuration

12.2(58)SE1

3750, 3560

NSF IETF mode for OSPFv2 and OSPFv3 (IP services image)

12.2(58)SE1

3750, 3560

RADIUS, TACACS+, and SSH/SCP over IPv6

12.2(58)SE1

3750, 3560, 2960-S, 2960

VRRP for IPv4

12.2(58)SE1

3750, 3560

IETF IP-MIB and IP-FORWARD-MIB(RFC4292 and RFC4293) updates

12.2(58)SE1

3750, 3560, 2960-S, 2960

Auto-QoS enhancements

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

Auto Smartport enhancements including global macros

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

Smart Install enhancements and new features

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

Port ACL improvements

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

CDP and LLDP location enhancements

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

Multi-authentication with VLAN assignment

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

Cisco TrustSec

12.2(55)SE

3750 and 3560

Memory-consistency check routines

12.2(55)SE

3750, 3560, 2975, 2960

Static routing support on SVIs

12.2(55)SE

2975, 2960, and 2960-S

MAC replace to end a session when a host disconnects from a port.

12.2(55)SE

3750, 3560,2975, 2960, 2960-S

DHCP snooping and Option 82 and LLPD-MED in LAN lite image

12.2(55)SE

2960 and 2960-S

Smart Install to allow a single point of management (director) in a network.

12.2(52)SE

3750, 3560,2975, 2960

Support for IP source guard on static hosts.

12.2(52)SE

3750, 3560,2975, 2960

AutoSmartPort enhancements (macro persistency, LLDP-based triggers, MAC address and OUI-based triggers, remote macros).

12.2(52)SE

3750, 3560,2975, 2960

RADIUS Change of Authorization (CoA).

12.2(52)SE

3750, 3560,2975, 2960

802.1x User Distribution for deployments with multiple VLANs.

12.2(52)SE

3750, 3560,2975, 2960

Critical VLAN with multiple-host authentication.

12.2(52)SE

3750, 3560,2975, 2960

Customizable web authentication enhancement to allow the creation of user-defined pages.

12.2(52)SE

3750, 3560,2975, 2960

Network Edge Access Topology (NEAT) to change the port host mode.

12.2(52)SE

3750, 3560,2975, 2960

VLAN-ID based MAC authentication.

12.2(52)SE

3750, 3560,2975, 2960

MAC move to allow hosts to move across ports on the same switch.

12.2(52)SE

3750, 3560,2975, 2960

3DES and AES with SNMPv3.

12.2(52)SE

3750, 3560,2975, 2960

Hostname support in the option 12 field of DHCPDISCOVER packets.

12.2(52)SE

3750, 3560,2975, 2960

DHCP Snooping enhancement for the circuit-id sub-option.

12.2(52)SE

3750, 3560,2975, 2960

Increased support for LLPD-MED

12.2(52)SE

3750, 3560,2975, 2960

LLPD-MED MIB and the CISCO-ADMISSION-POLICY-MIB.

12.2(52)SE

3750, 3560,2975, 2960

IPv6 QoS trust capability.

12.2(52)SE

3750, 3560

Cisco Medianet to enable intelligent services in the network infrastructure for video applications.

12.2(52)SE

3750, 3560

EEM 3.2 event detectors for Neighbor Discovery, Identity, and MAC-Address-Table.

12.2(52)SE

3750, 3560

Cisco EnergyWise Phase 2 to manage EnergyWise-enabled Cisco devices and non-Cisco end points running EnergyWise agents.

12.2(53)SE1

3750, 3560, 2960

Network Edge Access Topology (NEAT) with 802.1X switch supplicant, host authorization with CISP, and auto enablement

12.2(50)SE

3750, 3560, 2960

802.1x with open access

12.2(50)SE

3750, 3560, 2960

802.1x authentication with downloadable ACLs and redirect URLs

12.2(50)SE

3750, 3560, 2960

Flexible-authentication sequencing

12.2(50)SE

3750, 3560, 2960

Multiple-user authentication

12.2(50)SE

3750, 3560, 2960

Cisco EnergyWise Phase 1 to manage power usage over PoE devices.

12.2(50)SE

3750, 3560, 2960

Wired location service

12.2(50)SE

3750, 3560, 2960

CPU utilization threshold trap

12.2(50)SE

3750, 3560, 2960

Cisco IOS Configuration Engine (previously the Cisco IOS CNS agent)

12.2(50)SE

3750, 3560, 2960

LLDP-MED network-policy profile time, length, value (TLV)

12.2(50)SE

3750, 3560, 2960

RADIUS server load balancing

12.2(50)SE

3750, 3560, 2960

Auto Smartports Cisco-default and user-defined macros

12.2(50)SE

3750, 3560, 2960

SCP attribute support in the CONFIG_COPY MIB, CISCO-AUTH-FRAMEWORK-MIB, CISCO-MAC-AUTH-BYPASS MIBs, LLDP MIB

12.2(50)SE

3750, 3560, 2960

Intermediate System-to-Intermediate System (IS-IS) routing for Connectionless Network Service (CLNS) networks

12.2(50)SE

3750, 3560

Support for Embedded Event Manager Version 2.4.

12.2(50)SE

3750, 3560

IPv6 features in the IP services and IP base images: ACLs; DHCPv6 for the DCHP server, client, and relay device; EIGRPv6; HSRPv6; OSPFv3; RIP; Static routes

12.2(50)SE

3750, 3560

Stack troubleshooting enhancements

12.2(50)SE

3750

802.1x authentication with restricted VLANs

12.2(50)SE

2960

IP source guard

12.2(50)SE

2960

Dynamic ARP inspection

12.2(50)SE

2960

Generic message authentication support with SSH Protocol and compliance with RFC 4256

12.2(46)SE

3750, 3560, 2960

Generic message authentication support

12.2(46)SE

3750, 3560, 2960

Disabling MAC address learning on a VLAN

12.2(46)SE

3750, 3560, 2960

PAgP Interaction with Virtual Switches and Dual-Active Detection

12.2(46)SE

3750, 3560, 2960

DHCP server port-based address allocation

12.2(46)SE

3750, 3560, 2960

IPv6 default router preference (DRP)

12.2(46)SE

3750, 3560, 2960

Voice aware IEEE 802.1x and mac authentication bypass (MAB) security violation

12.2(46)SE

3750, 3560

Local web authentication banner

12.2(46)SE

3750, 3560

Support for the CISCO-NAC-NAD and CISCO-PAE MIBs

12.2(46)SE

3750, 3560

Excluding a port in a VLAN from the SVI line-state calculation

12.2(46)SE

3750, 3560

EOT and IP SLAs EOT static route support

12.2(46)SE

3750, 3560

Support for HSRP Version 2 (HSRPv2)

12.2(46)SE

3750, 3560

HSRP for IPv6 (advanced IP services image)

12.2(46)SE

3750, 3560

DHCP for IPv6 relay, client, server address assignment and prefix delegation (advanced IP services image)

12.2(46)SE

3750, 3560

Embedded event manager (EEM) (IP services image only)

12.2(46)SE

3750, 3560

Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA) (LAN base image only)

12.2(46)SE

2960

Monitoring real-time power consumption on a per-PoE port basis

12.2(46)SE

2960

IEEE 802.1x Authentication with ACLs and the RADIUS Filter-Id Attribute

12.2(46)SE

2960

IEEE 802.1x readiness check

12.2(44)SE

3750, 3560, 2960

DHCP-based autoconfiguration and image update

12.2(44)SE

3750, 3560, 2960

Configurable small-frame arrival threshold

12.2(44)SE

3750, 3560, 2960

HTTP and HTTP(s) support over IPV6

12.2(44)SE

3750, 3560, 2960

SNMP configuration over IPv6 transport

12.2(44)SE

3750, 3560, 2960

IPv6 stateless autoconfiguration

12.2(44)SE

3750, 3560, 2960

Flex Link Multicast Fast Convergence

12.2(44)SE

3750, 3560, 2960

Digital optical monitoring (DOM)

12.2(44)SE

3750, 3560

Source Specific Multicast (SSM) mapping

12.2(44)SE

3750, 3560

/31 bit mask support for multicast traffic

12.2(44)SE

3750, 3560

Configuration replacement and rollback

12.2(40)SE

3750, 3560, 2960

Link Layer Discovery Protocol Media Extensions (LLDP-MED)

12.2(40)SE

3750, 3560, 2960

Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6

12.2(40)SE

3750, 3560

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

12.2(40)SE

3750, 3560, 2960

Dynamic voice virtual LAN (VLAN) for MDA-enabled ports

12.2(40)SE

3750, 3560

Internet Group Management Protocol (IGMP) helper

12.2(40)SE

3750, 3560

IP Service Level Agreements (IP SLAs)

12.2(40)SE

3750, 3560

IP SLAs EOT

12.2(40)SE

3750, 3560

Multicast virtual routing and forwarding (VRF) lite

12.2(40)SE

3750, 3560

SSM PIM protocol

12.2(40)SE

3750, 3560

VRF-aware support for HSRP, uRPF, ARP, SNMP, IP SLA, TFTP, FTP, syslog, traceroute, and ping

12.2(40)SE

3750, 3560

MLD snooping

12.2(40)SE

2960

IPv6 host

12.2(40)SE

2960

IP phone detection enhancement

12.2(37)SE

3750, 3560, 2960

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

12.2(37)SE

3750, 3560, 2960

PIM stub routing

12.2(37)SE

3750, 3560

Port security on a PVLAN host

12.2(37)SE

3750, 3560

VLAN aware port security option

12.2(37)SE

3750, 3560, 2960

Auto rendezvous point (auto-RP) for multicast

12.2(37)SE

3750. 3560

VLAN Flex Links load balancing

12.2(37)SE

3750, 3560, 2960

Web Cache Communication Protocol (WCCP)

12.2(37)SE

3750. 3560

Multidomain authentication (MDA)

12.2(35)SE

3750, 3560

Web authentication

12.2(35)SE

3750, 3560, 2960

MAC inactivity aging

12.2(35)SE

3750, 3560, 2960

Support for IPv6 with Express Setup

12.2(35)SE

3750, 3560

Generic online diagnostics

12.2(35)SE

3560

Stack MAC persistent timer and archive download enhancements

12.2(35)SE

3750

HSRP enhanced object tracking

12.2(35)SE

3750, 3560

OSPF and EIGRP Nonstop forwarding capability (IP services image only)

12.2(35)SE

3750

IPv6 router ACLs for inbound Layer 3 management traffic

12.2(35)SE

3750, 3560

Generic online diagnostics to test the hardware functionality of the supervisor engine

12.2(25)SEE

3750

DHCP Option 82 configurable remote ID and circuit ID

12.2(25)SEE

3750, 3560, 2960

EIGRP stub routing in the IP base image

12.2(25)SEE

3750, 3560

/31 bit mask support for unicast traffic

12.2(25)SEE

3750, 3560

Access SDM templates

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules

IPv6 ACLs

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules

IPv6 Multicast Listener Discovery (MLD) snooping

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules

QoS hierarchical policy maps on a port

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules

NAC Layer 2 IEEE 802.1x validation

12.2(25)SED

3750, 3560, 2960
Cisco EtherSwitch service modules

NAC Layer 2 IP validation

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules

IEEE 802.1x inaccessible authentication bypass.

12.2(25)SED

12.2(25)SEE

3750, 3560
Cisco EtherSwitch service module

2960

IEEE 802.1x with restricted VLAN

12.2(25)SED

3750, 3560, 2960
Cisco EtherSwitch service modules

Budgeting power for devices connected to PoE ports

12.2(25)SEC

3750, 3560
Cisco EtherSwitch service modules

Multiple spanning-tree (MST) based on the IEEE 802.1s standard

12.2(25)SEC

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules|
2960

Unique device identifier (UDI)

12.2(25)SEC

12.2(25)SED

3750, 3560
Cisco EtherSwitch service modules
2960

VRF Lite

12.2(25)SEC

3750, 3560
Cisco EtherSwitch service modules

IEEE 802.1x with wake-on-LAN

12.2(25)SEC
12.2(25)SED

3750, 3560
2960, Cisco EtherSwitch service modules

Nonstop forwarding (NSF) awareness

12.2(25)SEC

3750, 3560
Cisco EtherSwitch service modules

Configuration logging

12.2(25)SEC
12.2(25)SED

3750, 3560
2960, Cisco EtherSwitch service modules

Secure Copy Protocol

12.2(25)SEC
12.2(25)SED

3750, 3560
2960, Cisco EtherSwitch service modules

Cross-stack EtherChannel

12.2(25)SEC

3750
Cisco EtherSwitch service modules

Private-VLAN on interfaces configured for dynamic ARP inspection

12.2(25)SEB

3750, 3560

IP source guard on private VLANs

12.2(25)SEB

3750, 3560

IEEE 802.1x restricted VLAN

12.2(25)SED

3750, 3560, 2960

IGMP leave timer

12.2(25)SEB
12.2(25)SED

3750, 3560, 2960

IGMP snooping querier

12.2(25)SEA
12.2(25)FX

3750, 3560, 2960

Advanced IP services

12.2(25)SEA

3750, 3560

DSCP transparency

12.2(25)SE
12.2(25)FX

3750, 3560, 2960

VLAN-based QoS1 and hierarchical policy maps on SVIs2

12.2(25)SE

3750, 3560

Device manager

12.2(25)SE
12.2(25)FX

3750, 3560, 2960

IEEE 802.1Q tunneling and Layer 2 protocol tunneling

12.2(25)SE

3750, 3560

Layer 2 point-to-point tunneling and Layer 2 point-to-point tunneling bypass

12.2(25)SE

3750, 3560

SSL version 3.0 for secure HTTP communication (cryptographic images only)

12.2(25)SE
12.2(25)FX

3750, 3560, 2960

Private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP services image only)

12.2(25)SE

3750, 3560

IP source guard on private VLANs (IP services image only)

12.2(25)SE

3750, 3560

Cisco intelligent power management

12.2(25)SE

3750, 3560

IEEE 802.1x accounting and MIBs (IEEE 8021-PAE-MIB and CISCO-PAE-MIB)

12.2(20)SE
12.2(25)FX

3750, 3560, 2960

Dynamic ARP inspection

12.2(20)SE

3750, 3560

Flex Links

12.2(20)SE
12.2(25)FX

3750, 3560, 2960

Software upgrade (device manager or Network Assistant only)

12.2(20)SE
12.2(25)FX

3750, 3560, 2960

IP source guard

12.2(20)SE

3750, 3560

Private VLAN (IP services image only)

12.2(20)SE

3750, 3560

SFP module diagnostic management interface

12.2(20)SE
12.2(25)FX

3750, 3560, 2960

Switch stack offline configuration

12.2(20)SE

3750

Stack-ring activity statistics

12.2(20)SE

3750

Smartports macros

12.2(18)SE
12.2(25)FX

3750, 3560, 2960

Generic online diagnostics (GOLD)

12.2(25)SEE

3750

Flex Links Preemptive Switchover

12.2(25)SEE

3750, 3560, 2960

1 QoS = quality of service

2 SVIs = switched virtual interfaces


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

Device Manager Limitations

Cisco IOS Limitations

Unless otherwise noted, these limitations apply to the Catalyst 3750, and 3560, and 2960 switches and the Cisco EtherSwitch service modules:

Configuration

Ethernet

EtherSwitch Modules

Fallback Bridging

HSRP

IP

IP Telephony

MAC Addressing

MAC Addressing

Multicasting

Power

QoS

Routing

Smart Install

SPAN and RSPAN

Spanning Tree Protocol

Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)

Trunking

VLAN

Configuration

A static IP address might be removed when the previously acquired DHCP IP address lease expires.

This problem occurs under these conditions:

When the switch is booted up without a configuration (no config.text file in flash memory).

When the switch is connected to a DHCP server that is configured to give an address to it (the dynamic IP address is assigned to VLAN 1).

When an IP address is configured on VLAN 1 before the dynamic address lease assigned to VLAN 1 expires.

The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When the show interface privileged EXEC is entered on a port that is running IEEE 802.1Q, inconsistent statistics from ports running IEEE 802.1Q might be reported.

The workaround is to upgrade to Cisco IOS Release 12.1(20)EA1. (CSCec35100)

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When you change a port from a nonrouted port to a routed port or the reverse, the applied auto-QoS setting is not changed or updated when you verify it by using the show running interface or show mls qos interface user EXEC commands.

These are the workarounds:

1. Disable auto-QoS on the interface.

2. Change the routed port to a nonrouted port or the reverse.

3. Re-enable auto-QoS on the interface. (CSCec44169)

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

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

The DHCP snooping binding database is not written to flash memory or a remote file in any of these situations:

(Catalyst 3750 switch and Cisco EtherSwitch service modules) When the Network Time Protocol (NTP) is configured, but the NTP clock is not synchronized. You can check the clock status by entering the show NTP status privileged EXEC command and verifying that the network connection to the NTP server and the peer work correctly.

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The DHCP snooping database file is manually removed from the file system. After enabling the DHCP snooping database by configuring a database URL, a database file is created. If the file is manually removed from the file system, the DHCP snooping database does not create another database file. You need to disable the DHCP snooping database and enable it again to create the database file.

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The URL for the configured DHCP snooping database was replaced because the original URL was not accessible. The new URL might not take effect after the timeout of the old URL.

No workaround is necessary; these are the designed behaviors. (CSCed50819)

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When dynamic ARP inspection is enabled on a switch or switch stack, ARP and RARP packets greater than 2016 bytes are dropped by the switch or switch stack. This is a hardware limitation.

However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)

(Catalyst 3750 switches and Cisco EtherSwitch service modules) Dynamic ARP inspection log entries might be lost after a switch failure. Any log entries that are still in the log buffer (have not been output as a system message) on a switch that fails are lost.

When you enter the show ip arp inspection log privileged EXEC command, the log entries from all switches in the stack are moved to the switch on which you entered the command.

There is no workaround. (CSCed95822)

When port security is enabled on an interface in restricted mode and the switchport block unicast interface command has been entered on that interface, MAC addresses are incorrectly forwarded when they should be blocked

The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)

A traceback error occurs if a crypto key is generated after an SSL client session.

There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)

(Cisco EtherSwitch service modules) You cannot change the console baud rate by using the switch CLI. The console on the Cisco EtherSwitch service modules only supports three baud rates (9600 b/s, 19200 b/s, and 38400 b/s) and must be set at the bootloader prompt. The switch rejects a CLI command to change the baud rate.

To change the baud rate, reload the Cisco EtherSwitch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco EtherSwitch Service module console.

There is no workaround. (CSCeh50152)

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

(CSCsh12472 [Catalyst 3750 and 3560 switches])

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

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

A ciscoFlashMIBTrap message appears during switch startup. This does not affect switch functionality. (CSCsj46992)

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 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. (CSCsl02680) (Catalyst 3750 and 3560 switches)

A T-start error message appears after startup under these conditions:

Two-link ports on the same switch are connected with a crossover cable.

The switch is running Cisco IOS 12.2(50)SE3 or later.

The workaround is to connect the two ports with a straight-through cable. (CSCsr41271) (Catalyst 3750V2 and Catalyst 3560V2 PoE switches and Cisco Etherswitch service modules only)

If you enter the show tech-support privileged EXEC command after you enter the remote command {all | stack-member-number} privileged EXEC command, the complete output does not appear.

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

When authorization and accounting are enabled on the switch and you use the interface range command to change the configuration on a range of interfaces, the change might cause high CPU utilization and authentication failures.

The workaround is to disable authorization and accounting or to enter the configuration change for one interface at a time. (CSCsg80238, CSCti76748)

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.

Ethernet

(Cisco EtherSwitch service modules) Link connectivity might be lost between some older models of the Intel Pro1000 NIC and the 10/100/1000 switch port interfaces. The loss of connectivity occurs between the NIC and Gigabit Ethernet ports on the Cisco EtherSwitch service modules

These are the workarounds:

Contact the NIC vendor, and get the latest driver for the card.

Configure the interface for 1000 Mb/s instead of for 10/100 Mb/s.

Connect the NIC to an interface that is not listed here. (CSCea77032)

For more information, enter CSCea77032 in the Bug Toolkit at this URL:
http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl

(Cisco EtherSwitch service modules) When a Cisco EtherSwitch service module reloads or the internal link resets, there can be up to a 45-second delay in providing power to PoE devices, depending on the configuration. If the internal Gigabit Ethernet interface on a Cisco EtherSwitch service module connected to the router is configured as a switch port in access mode or in trunk mode, the internal link is not operational until it reaches the STP forwarding state. Therefore, the PoE that comes from the host router is also not available until the internal Gigabit Ethernet link reaches the STP forwarding state. This is due to STP convergence time. This problem does not occur on routed ports.

If the Cisco EtherSwitch service module is in access mode, the workaround is to enter the spanning-tree portfast interface configuration command on the internal Gigabit Ethernet interface. If the service module is in trunk mode, there is no workaround.

Traffic on EtherChannel ports is not perfectly load-balanced. Egress traffic on EtherChannel ports are distributed to member ports on load balance configuration and traffic characteristics like MAC or IP address. More than one traffic stream may map to same member ports based on hashing results calculated by the ASIC.

If this happens, uneven traffic distribution will happen on EtherChannel ports.

Changing the load balance distribution method or changing the number of ports in the EtherChannel can resolve this problem. Use any of these workarounds to improve EtherChannel load balancing:

for random source-ip and dest-ip traffic, configure load balance method as src-dst-ip

for incrementing source-ip traffic, configure load balance method as src-ip

for incrementing dest-ip traffic, configure load balance method as dst-ip

Configure the number of ports in the EtherChannel so that the number is equal to a power of 2 (i.e. 2, 4, or 8)

For example, with load balance configured as dst-ip with 150 distinct incrementing destination IP addresses, and the number of ports in the EtherChannel set to either 2, 4, or 8, load distribution is optimal.(CSCeh81991)

EtherSwitch Modules

A duplex mismatch occurs when two Fast Ethernet interfaces that are directly connected on two EtherSwitch service modules are configured as both 100 Mb/s and full duplex and as automatic speed and duplex settings. This is expected behavior for the PHY on the Cisco EtherSwitch service modules.

There is no workaround. (CSCeh35595)

Fallback Bridging

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) If a bridge group contains a VLAN to which a static MAC address is configured, all non-IP traffic in the bridge group with this MAC address destination is sent to all ports in the bridge group.

The workaround is to remove the VLAN from the bridge group or to remove the static MAC address from the VLAN. (CSCdw81955)

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) Known unicast (secured) addresses are flooded within a bridge group if secure addresses are learned or configured on a port and the VLAN on this port is part of a bridge group. Non-IP traffic destined to the secure addresses is flooded within the bridge group.

The workaround is to disable fallback bridging or to disable port security on all ports in all VLANs participating in fallback bridging. To remove an interface from a bridge group and to remove the bridge group, use the no bridge-group bridge-group interface configuration command. To disable port security on all ports in all VLANs participating in fallback bridging, use the no switchport port-security interface configuration command. (CSCdz80499)

HSRP

When the active switch fails in a switch cluster that uses HSRP redundancy, the new active switch might not contain a full cluster member list.

The workaround is to ensure that the ports on the standby cluster members are not in the spanning-tree blocking state. To verify that these ports are not in the blocking state, see the "Configuring STP" chapter in the software configuration guide. (CSCec76893)

IP

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The switch does not create an adjacent table entry when the ARP timeout value is 15 seconds and the ARP request times out.

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

When the rate of received DHCP requests exceeds 2,000 packets per minute for a long time, the response time might be slow when you are using the console.

The workaround is to use rate limiting on DHCP traffic to prevent a denial of service attack from occurring. (CSCeb59166)

IP Telephony

After you change the access VLAN on a port that has IEEE 802.1x enabled, the IP phone address is removed. Because learning is restricted on IEEE 802.1x-capable ports, it takes approximately 30 seconds before the address is relearned.

No workaround is necessary. (CSCea85312)

(Catalyst 3750 or 3560 PoE-capable switches and Cisco EtherSwitch service modules) The switch uses the IEEE classification to learn the maximum power consumption of a powered device before powering it. The switch grants power only when the maximum wattage configured on the port is less than or equal to the IEEE class maximum. This ensures that the switch power budget is not oversubscribed. There is no such mechanism in Cisco prestandard powered devices.

The workaround for networks with pre-standard powered devices is to leave the maximum wattage set at the default value (15.4 W). You can also configure the maximum wattage for the port for no less than the value the powered device reports as the power consumption through CDP messages. For networks with IEEE Class 0, 3, or 4 devices, do not configure the maximum wattage for the port at less than the default 15.4 W (15,400 milliwatts). (CSCee80668)

Phone detection events that are generated by many IEEE phones connected to the switch ports can consume a significant amount of CPU time if the switch ports cannot power the phones because the internal link is down.

The workaround is to enter the power inline never interface configuration command on all the Fast Ethernet ports that are not powered by but are connected to IP phones if the problem persists. (CSCef84975, Cisco EtherSwitch service modules only)

Some access point devices are incorrectly discovered as IEEE 802.3af Class 1 devices. These access points should be discovered as Cisco pre-standard devices. The show power inline user EXEC command shows the access point as an IEEE Class 1 device.

The workaround is to power the access point by using an AC wall adaptor. (CSCin69533)

The Cisco 7905 IP Phone is error-disabled when the phone is connected to wall power.

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

MAC Addressing

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When a MAC address is configured for filtering on the internal VLAN of a routed port, incoming packets from the MAC address to the routed port are not dropped. (CSCeb67937)

Management

CiscoWorks is not supported on the Catalyst 3750-24FS switch.

Multicasting

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) Nonreverse-path forwarded (RPF) IP multicast traffic to a group that is bridged in a VLAN is leaked onto a trunk port in the VLAN even if the port is not a member of the group in the VLAN, but it is a member of the group in another VLAN. Because unnecessary traffic is sent on the trunk port, it reduces the bandwidth of the port.

There is no workaround for this problem because non-RPF traffic is continuous in certain topologies. As long as the trunk port is a member of the group in at least one VLAN, this problem occurs for the non-RPF traffic. (CSCdu25219)

If the number of multicast routes and Internet Group Management Protocol (IGMP) groups are more than the maximum number specified by the show sdm prefer global configuration command, the traffic received on unknown groups is flooded in the received VLAN even though the show ip igmp snooping multicast-table privileged EXEC command output shows otherwise.

The workaround is to reduce the number of multicast routes and IGMP snooping groups to less than the maximum supported value. (CSCdy09008)

IGMP filtering is applied to packets that are forwarded through hardware. It is not applied to packets that are forwarded through software. Hence, with multicast routing enabled, the first few packets are sent from a port even when IGMP filtering is set to deny those groups on that port.

There is no workaround. (CSCdy82818)

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) When you use the ip access-group interface configuration command with a router access control list (ACL) to deny access to a group in a VLAN, multicast data to the group that is received in the VLAN is always flooded in the VLAN, regardless of IGMP group membership in the VLAN. This provides reachability to directly connected clients, if any, in the VLAN.

The workaround is to not apply a router ACL set to deny access to a VLAN interface. Apply the security through other means; for example, apply VLAN maps to the VLAN instead of using a router ACL for the group. (CSCdz86110)

(Catalyst 3750 switch stack) If the stack master is power cycled immediately after you enter the ip mroute global configuration command, there is a slight chance that this configuration change might be lost after the stack master changes. This occurs because the stack master did not have time to propagate the running configuration to all the stack members before it was powered down. This problem might also affect other configuration commands.

There is no workaround. (CSCea71255)

(Catalyst 3750 switches and Cisco EtherSwitch service modules) When you enable IP Protocol-Independent Multicast (PIM) on a tunnel interface, the switch incorrectly displays the Multicast is not supported on tunnel interfaces error message. IP PIM is not supported on tunnel interfaces.

There is no workaround. (CSCeb75366)

If an IGMP report packet has two multicast group records, the switch removes or adds interfaces depending on the order of the records in the packet:

If the ALLOW_NEW_SOURCE record is before the BLOCK_OLD_SOURCE record, the switch removes the port from the group.

If the BLOCK_OLD_SOURCE record is before the ALLOW_NEW_SOURCE record, the switch adds the port to the group.

There is no workaround. (CSCec20128)

When IGMP snooping is disabled and you enter the switchport block multicast interface configuration command, IP multicast traffic is not blocked.

The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.

There is no workaround. (CSCee16865)

Incomplete multicast traffic can be seen under either of these conditions:

You disable IP multicast routing or re-enable it globally on an interface.

A switch mroute table temporarily runs out of resources and recovers later.

The workaround is to enter the clear ip mroute privileged EXEC command on the interface. (CSCef42436)

After you configure a switch to join a multicast group by entering the ip igmp join-group group-address interface configuration command, the switch does not receive join packets from the client, and the switch port connected to the client is removed from the IGMP snooping forwarding table.

Use one of these workarounds:

Cancel membership in the multicast group by using the no ip igmp join-group group-address interface configuration command on an SVI.

Disable IGMP snooping on the VLAN interface by using the no ip igmp snooping vlan vlan-id global configuration command. (CSCeh90425)

Power

Non-PoE devices attached to a network might be erroneously detected as an IEEE 802.3af- compliant powered device and powered by the Cisco EtherSwitch service module.

There is no workaround. You should use the power inline never interface configuration command on Cisco EtherSwitch service module ports that are not connected to PoE devices. (CSCee71979)

When you enter the show power inline privileged EXEC command, the out put shows the total power used by all Cisco EtherSwitch service modules in the router. The remaining power shown is available for allocation to switching ports on all Cisco EtherSwitch service modules in the router.

To display the total power used by a specific EtherSwitch service module, enter the show power inline command on the router. This output appears:

Router# show power inline
PowerSupply   SlotNum.   Maximum   Allocated       Status
-----------   --------   -------   ---------       ------
INT-PS           0       360.000   121.000         PS1 GOOD   PS2 ABSENT 
Interface   Config   Device    Powered    PowerAllocated
---------   ------   ------    -------    -------------- 
Gi4/0       auto     Unknown  On        121.000 Watts 
 
   

This is not a problem because the display correctly shows the total used power and the remaining power available on the system. (CSCeg74337)

Entering the shutdown and the no shutdown interface configuration commands on the internal link can disrupt the PoE operation. If a new IP phone is added while the internal link is in shutdown state, the IP phone does not get inline power if the internal link is brought up within 5 minutes.

The workaround is to enter the shutdown and the no shutdown interface configuration commands on the Fast Ethernet interface of a new IP phone that is attached to the service module port after the internal link is brought up. (CSCeh45465)

QoS

Some switch queues are disabled if the buffer size or threshold level is set too low with the mls qos queue-set output global configuration command. The ratio of buffer size to threshold level should be greater than 10 to avoid disabling the queue.

The workaround is to choose compatible buffer sizes and threshold levels. (CSCea76893)

When auto-QoS is enabled on the switch, priority queuing is not enabled. Instead, the switch uses shaped round robin (SRR) as the queuing mechanism. The auto-QoS feature is designed on each platform based on the feature set and hardware limitations, and the queuing mechanism supported on each platform might be different. There is no workaround. (CSCee22591)

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

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The switch does not support tunnel interfaces for unicast routed traffic. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnel interfaces are supported for multicast routing.

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) A route map that has an ACL with a Differentiated Services Code Point (DSCP) clause cannot be applied to a Layer 3 interface. The switch rejects this configuration and displays a message that the route map is unsupported.

There is no workaround. (CSCea52915)

On a Catalyst 3750 or a Cisco EtherSwitch service module switch stack with a large number of switched virtual interfaces (SVIs), routes, or both on a fully populated nine-member switch stack, this message might appear when you reload the switch stack or add a switch to the stack:

%SYS-2-MALLOCFAIL: Memory allocation of 4252 bytes failed from 0x179C80, alignment 0
Pool: I/O Free: 77124  Cause: Memory fragmentation
Alternate Pool: None Free: 0  Cause: No Alternate pool
 
   

This error message means there is a temporary memory shortage that normally recovers by itself. You can verify that the switch stack has recovered by entering the show cef line user EXEC command and verifying that the line card states are up and sync.

No workaround is required because the problem is self-correcting. (CSCea71611)

(Catalyst 3750 switches and Cisco EtherSwitch service modules) A spanning-tree loop might occur if all of these conditions are true:

Port security is enabled with the violation mode set to protected.

The maximum number of secure addresses is less than the number of switches connected to the port.

There is a physical loop in the network through a switch whose MAC address has not been secured, and its BPDUs cause a secure violation.

The workaround is to change any one of the listed conditions. (CSCed53633)

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, when the director is connected between the client and the DHCP server and the server has options configured for image and configuration, then the client does not receive the image and configuration files sent by the DHCP server during an automatic upgrade. Instead the files are overwritten by the director and the client receives the image and configuration that the director sends.

Use one of these workarounds:

If client needs to upgrade using an image and configuration file configured in the DHCP server options, you should remove the client from the Smart Install network during the upgrade.

In a network using Smart Install, you should not configure options for image and configuration in the DHCP server. For clients to upgrade using Smart Install, you should configure product-id specific image and configuration files in the director. (CSCte99366)

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

(Cisco EtherSwitch service modules) An egress SPAN copy of routed unicast traffic might show an incorrect destination MAC address on both local and remote SPAN sessions. This limitation does not apply to bridged packets. The workaround for local SPAN is to use the replicate option. For a remote SPAN session, there is no workaround.

This is a hardware limitation and only applies to Cisco EtherSwitch service modules (CSCdy72835):

(Cisco EtherSwitch service modules) Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address. For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN, but instead the packet shows the MAC address of the RSPAN VLAN. For local SPAN packets with native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This problem does not appear with local SPAN when the encapsulation replicate option is used. This limitation does not apply to bridged packets. The workaround is to use the encapsulate replicate keywords in the monitor session global configuration command. Otherwise, there is no workaround.

This is a hardware limitation and only applies to Cisco EtherSwitch service modules (CSCdy81521):

(Cisco EtherSwitch service modules) During periods of very high traffic when two RSPAN source sessions are configured, the VLAN ID of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. If this occurs, packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN. This problem does not affect RSPAN destination sessions. The workaround is to configure only one RSPAN source session.

This is a hardware limitation and only applies to Cisco EtherSwitch service modules (CSCea72326):

(Catalyst 3750 or 3560 switches and Cisco EtherSwitch service modules) The egress SPAN data rate might degrade when fallback bridging or multicast routing is enabled. The amount of degradation depends on the processor loading. Typically, the switch can egress SPAN at up to 40,000 packets per second (64-byte packets). As long as the total traffic being monitored is below this limit, there is no degradation. However, if the traffic being monitored exceeds the limit, only a portion of the source stream is spanned. When this occurs, the following console message appears: Decreased egress SPAN rate. In all cases, normal traffic is not affected; the degradation limits only how much of the original source stream can be egress spanned. If fallback bridging and multicast routing are disabled, egress SPAN is not degraded.

There is no workaround. If possible, disable fallback bridging and multicast routing. If possible, use ingress SPAN to observe the same traffic. (CSCeb01216)

On Catalyst 3750 switches, Catalyst 3560 switches, or on Cisco EtherSwitch service modules, some IGMP report and query packets with IP options might not be ingress-spanned. Packets that are susceptible to this problem are IGMP packets containing 4 bytes of IP options (IP header length of 24). An example of such packets would be IGMP reports and queries having the router alert IP option. Ingress-spanning of such packets is not accurate and can vary with the traffic rate. Typically, very few or none of these packets are spanned.

There is no workaround. (CSCeb23352)

Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol (PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local SPAN session. The workaround is to use the monitor session session_number destination {interface interface-id encapsulation replicate} global configuration command for local SPAN. (CSCed24036)

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 or Cisco EtherSwitch service module switch stack only)

If the stack master is immediately reloaded after adding multiple VLANs, the new stack master might fail. The workaround is to wait a few minutes after adding VLANs before reloading the stack master. (CSCea26207)

If the console speed is changed on a stack, the configuration file is updated, but the baud rate is not. When the switch is reloaded, meaningless characters might appear on the console during bootup before the configuration file is parsed and the console speed is set to the correct value. If manual bootup is enabled or the startup configuration is deleted after you change the console speed, you cannot access the console after the switch reboots.

There is no workaround. (CSCec36644)

If a switch is forwarding traffic from a Gigabit ingress interface to a 100 Mb/s egress interface, the ingress interface might drop more packets due to oversubscription if the egress interface is on a Fast Ethernet switch than if it is on a Gigabit Ethernet switch.

There is no workaround. (CSCed00328)

If a stack member is removed from a stack and either the configuration is not saved or another switch is added to the stack at the same time, the configuration of the first member switch might be lost.

The workaround is to save the stack configuration before removing or replacing any switch in the stack. (CSCed15939)

When the switchport and no switchport interface configuration commands are entered more than 20,000 times on a port of a Catalyst 3750 switch or on a Cisco EtherSwitch service module, all available memory is used, and the switch halts.

There is no workaround. (CSCed54150)

In a private-VLAN domain, only the default private-VLAN IP gateways have sticky ARP enabled. The intermediate Layer 2 switches that have private VLAN enabled disable sticky ARP. When a stack master re-election occurs on one of the Catalyst 3750 or Cisco EtherSwitch service module default IP gateways, the message IP-3-STCKYARPOVR appears on the consoles of other default IP gateways. Because sticky ARP is not disabled, the MAC address update caused by the stack master re-election cannot complete.

The workaround is to complete the MAC address update by entering the clear arp privileged EXEC command. (CSCed62409)

When a Catalyst 3750 switch or Cisco EtherSwitch service module is being reloaded in a switch stack, packet loss might occur for up to 1 minute while the Cisco Express Forwarding (CEF) table is downloaded to the switch. This only impacts traffic that will be routed through the switch that is being reloaded.

There is no workaround. (CSCed70894)

Inconsistent private-VLAN configuration can occur on a switch stack if a new stack master is running the IP base image and the old stack master was running the IP services image.

Private VLAN is enabled or disabled on a switch stack, depending on whether or not the stack master is running the IP services image or the IP base image:

If the stack master is running the IP services image, all stack members have private VLAN enabled.

If the stack master is running the IP base image, all stack members have private VLAN disabled.

This occurs after a stack master re-election when the previous stack master was running the IP services image and the new stack master is running the IP base image. The stack members are configured with private VLAN, but any new switch that joins the stack will have private VLAN disabled.

These are the workarounds. Only one of these is necessary:

Reload the stack after an IP services image to IP base image master switch change (or the reverse).

Before an IP services image-to-IP base image master switch change, delete the private-VLAN configuration from the existing stack master. (CSCee06802)

Port configuration information is lost when changing from switchport to no switchport modes on Catalyst 3750 switches.

This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)

When connected to the router through an auxiliary port in a session to a Cisco EtherSwitch service module, the service module session fails when you enter the shutdown and the no shutdown interface configuration commands on the service module router interface.

These are the workarounds:

Reload the router.

Connect to the router through the console port, and open a session to the service module. (CSCeh01250) (Cisco EtherSwitch service modules)

If one switch in a stack of Catalyst 3750 switches requires more time than the other switches to find a bootable image, it might miss the stack master election window. However, even if the switch does not participate in the stack master election, it will join the stack as a member.

The workaround is to copy the bootable image to the parent directory or first directory. (CSCei69329)

When the path cost to the root bridge is equal from a port on a stacked root and a port on a non stack root, the BLK port is not chosen correctly in the stack when the designated bridge priority changes. This problem appears on switches running in PVST, Rapid-PVST, and MST modes.

The workaround is to assign a lower path cost to the forwarding port. (CSCsd95246)

When a stack of 3750 switches is configured with a Cross-Stack EtherChannel and one of the physical ports in the EtherChannel has a link-up or a link-down event, the stack might transmit duplicate packets across the EtherChannel. The problem occurs during the very brief interval while the switch stack is adjusting the EtherChannel for changing conditions and adapting the load balance algorithm to the new set of active physical ports.

This can but does not always occur during link flaps and does not last for more than a few milliseconds. This problem can happen for cross-stack EtherChannels with the mode set to ON or LACP.

There is no workaround. No manual intervention is needed. The problem corrects itself within a short interval after the link flap as all the switches in the stack synchronize with the new load-balance configuration. (CSCse75508)

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 being entered, 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)

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)

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)

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

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) (Catalyst 3750 switch)

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) (Catalyst 3750 and 2960-S switches)

Trunking

The switch treats frames received with mixed encapsulation (IEEE 802.1Q and Inter-Switch Link [ISL]) as frames with FCS errors, increments the error counters, and the port LED blinks amber. This happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame to an IEEE 802.1Q trunk interface.

There is no workaround. (CSCdz33708)

IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the output interface for the multicast route entry assigned to the multicast group and an interface in VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is forwarding in VLAN Y, even though the port has no group membership in VLAN Y.

There is no workaround. (CSCdz42909).

If a Catalyst 3750 switch stack is connected to a designated bridge and the root port of the switch stack is on a different switch than the alternate root port, changing the port priority of the designated ports on the designated bridge has no effect on the root port selection for the Catalyst 3750 switch stack.

There is no workaround. (CSCea40988)

For trunk ports or access ports configured with IEEE 802.1Q tagging, inconsistent statistics might appear in the show interfaces counters privileged EXEC command output. Valid IEEE 802.1Q frames of 64 to 66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not counted on the interface statistics.

There is no workaround. (CSCec35100).

VLAN

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)

(Catalyst 3750 or 3560 switches) A CPUHOG message sometimes appears when you configure a private VLAN. Enable port security on one or more of the ports affected by the private VLAN configuration.

There is no workaround. (CSCed71422)

(Catalyst 3750) When you apply a per-VLAN quality of service (QoS), per-port policer policy-map to a VLAN Switched Virtual Interface (SVI), the second-level (child) policy-map in use cannot be re-used by another policy-map.

The workaround is to define another policy-map name for the second-level policy-map with the same configuration to be used for another policy-map. (CSCef47377)

When dynamic ARP inspection is configured on a VLAN, and the ARP traffic on a port in the VLAN is within the configured rate limit, the port might go into an error-disabled state.

The workaround is to configure the burst interval to more than 1 second. (CSCse06827, Catalyst 3750 switches only)

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)

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)

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)

Important Notes

Switch Stack Notes

Catalyst 2960-S Control Plane Protection

Catalyst 2960-S Control Plane Protection

Device Manager Notes

Switch Stack Notes

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

Catalyst 3560 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 switches running Cisco IOS Release 12.2(25)SEB are compatible with Cisco EtherSwitch service modules running Cisco IOS Release 12.2(25)EZ. Catalyst 3750 switches and Cisco EtherSwitch service modules can be in the same switch stack. In this switch stack, the Catalyst 3750 switch or the Cisco EtherSwitch service module can be the stack master.

Catalyst 2960-S Control Plane Protection

Catalyst 2960-S 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

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, check that there is network connectivity between the switch and the ACS. You should also check 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

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

The Legend on the device manager incorrectly includes the 1000BASE-BX SFP module.

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.

Open Caveats

Unless otherwise noted, these caveats apply to the Catalyst 3750, 3560, 2960-S, and 2960 switches and to Cisco EtherSwitch service modules:

CSCtg35226 (Catalyst 3750 switches)

Cisco Network Assistant displays the LED ports with a light blue color for all switches in a stack that have the Catalyst 3750G-48PS switch as part of the stack.

There is no workaround.

CSCtj97806 (Catalyst 3750 and 3560 switches)

Mediatrace does not report statistics on the initiator under these conditions:

The responder is a mixed switch stack with a Catalyst 3750 as the master switch

The ingress interface on the responder from the initiator is on a member switch.

The workaround is to ensure that the mediatrace ingress and egress connections are on the stack master or to configure a Catalyst 3750-E or 3750-X as the stack master and then reload the switch stack.

CSCtl32991

Unicast EIGRP packets destined for the switch are sent to the host queue instead of to the higher priority routing protocol queue.


Note This does not occur when packets are routed through the switch to another destination.


There is no workaround.

CSCto70539 (Catalyst 2960-S)

The Ethernet management port on the Catalyst 2960-S switch might not behave normally if the port is set to 100 Mb/s and full duplex.

The workaround is to set the Ethernet management port and the device to which it is connected to auto speed and auto duplex.

CSCtq35006

On a switch stack, when an IP phone connected to a member switch has its MAC address authorized using the critical voice VLAN feature, if a master changeover occurs, the voice traffic is dropped. Drop entries for the IP phone appear in the MAC address table management (MATM) table. This occurs because the switch initially drops the voice traffic before reauthenticating critical voice VLAN traffic. The dropped entries are removed when critical voice VLAN authentication occurs.

There is no workaround. The dropped entries are removed when the IP phone is reauthenticated.

CSCtq39377

Port security violations might be ignored when Auto Smartports is enabled and a Smartport macro is applied to a secure port. This behavior occurs because IOS sensor (part of Auto Smartports) sets the host mode to multiple-authentication (multi-host mode) and enables 802.1x in the host access table. In multi-host mode, if the same MAC address in the same VLAN is seen on another port, then it is not allowed. Therefore the packet does not reach port-security module to create the violation.

The workaround is to enter the no macro auto monitor global configuration command to globally disable the IOS sensor (Auto Smartports) feature.

CSCtq81500

When an IP phone is authenticated on a switch port that is running Multidomain authentication (MDA) in the voice VLAN, the switch might experience high CPU usage after continued attempts to re-authenticate a phone that does not have a valid password configuration. Re-authentication can be triggered by:

Expiration of the authentication timer

Entering the dot1x re-authenticate interface interface-id privileged EXEC command

The workaround to clear the problem:

Enter the shutdown interface command followed by the no shutdown interface configuration command.

Initialize the interface by entering the dot1x initialize interface interface-id privileged EXEC command.

Correct the password on the phone.

To prevent the situation:

Do not use periodic re-authentication for the voice domain.

When manually clearing authentications, use the clear authentication session privileged EXEC command instead of the dot1x re-authenticate interface command.

CSCtr07908

The image archive download process does not work if there is an update directory in flash memory, which occurs if a previous download was interrupted or failed.

The workaround is to delete the update directory from the flash memory before executing the archive download-sw privileged EXEC command.

CSCtr16643 (Catalyst 2960-S)

When TCP packets in the same VLAN are sent from one switch to another, ACL deny logs appear, even though the ACL is applied on the switch virtual interface (SVI).

The workaround, to stop the messages, is to configure IP unreachables by entering the ip unreachables interface configuration command on the SVI or routed port.

CSCtr87645

ASP now uses a device classifier, which determines the type of device that is connected to the switch. As a result, ASP has no control over the protocol type that is used to detect the device. Therefore, the protocol detection controls are deprecated. When you enter the macro auto global control detection command, the protocol does not show up in the running configuration; however, the filter-spec command is shown in the output.

There is no workaround. To see the deprecated commands, enter the show running config deprecated global and interface configuration command.

CSCtt11621

When the dot1x default interface configuration command is entered, access control for hosts is disabled and the values for the following commands are reset to their default values: authentication host-mode, authentication timer reauthenticate, and authentication port-control.

The workaround is to avoid using the dot1x default command and reset the 802.1x port parameters individually. Another workaround is to enter the dot1x default command, and then reconfigure the incorrectly changed values.

CSCtw33903 (all: 3560, 3750, 3750-E, 3560-E, 3750-X, 3560-X, 2960, 2960-S)

This problem occurs when the Enterprise Policy Manager (EPM) for a device connected to an interface is authorized in closed mode and no policies are configured or downloaded. If no port ACL is configured, the auth-default access control list (ACL) is applied to the switch. If another device is connected to this device, restricted VLAN (authentication event interface configuration command) is enabled on the port. The Application Control Engine (ACE) is not configured to permit traffic originating from the connected device, and IP packets are dropped.

The workaround is to configure a port ACL to allow IP traffic for the specific IP range for the connected devices on the interface.

CSCtw42349

This problem occurs when a supplicant device is connected to a switch through a main device, and the interface is enabled with authentication, port security and IP source guard (IPSG). The main and supplicant devices are configured with sticky MAC addresses. In this case, if the port is shut down, traffic originating from the supplicant is dropped.

The workaround is to disable port security on the port.

Resolved Caveats

Caveats Resolved in Cisco IOS Release 15.0(1)SE3

Caveats Resolved in Cisco IOS Release 15.0(1)SE1

Caveats Resolved in Cisco IOS Release 15.0(1)SE

Caveats Resolved in Cisco IOS Release 15.0(1)SE3

CSCtj48387

A router running as a Layer 2 Tunneling Protocol (L2TP) Network Server (LNS) halts with DHCP-related errors. This problem occurs when DHCP is enabled and sessions receive DHCP information from a RADIUS server.

There is no workaround.

CSCtk12589 (Catalyst 2960-S)

When the switch starts, multiple instances of this error message appear on the console:

Yeti2S88gMdioWr:Unknown status for write operation

The workaround is to restart the switch.

CSCtl60151

The switch might occasionally reload after experiencing a CPU overload, regardless of what process is overloading the CPU.

There is no workaround.

CSCts50508

When authentication is enabled on an open port (for example, when moving from no authentication to authentication port-control auto), Address Resolution Protocol (ARP) and DHCP traffic is dropped.

The workaround is to use the shutdown configuration interface command to disable the port and then use the no shutdown configuration interface command to enable the port. You also can use the clear mac-address-table command to clear the MAC address table.

CSCts74537

After reloading the switch, Switched Port Analyzer (SPAN) traffic does not arrive at the SPAN destination port.

The workaround is to delete the SPAN configuration and reapply it.

CSCtt04584 (Catalyst Switch 3560)

On a virtual routing and forwarding (VRF) interface, IP multicast traffic is not forwarded after using the clear ip mroute vrf command.

There is no workaround.

CSCtu09817(Catalyst Switches 3560 v2, 3750 v2 and 2960-S)

When a power supply fails or loses power, the redundant power supply (RPS) (750 W or 1150 W) does not provide Power over Ethernet (PoE) for the powered devices.

There is no workaround.

CSCtx05704 (Catalyst Switches 3750 and 3750 v2)

After a rolling stack upgrade, Address Resolution Protocol (ARP) entries are in the INCOMPLETE state.

There is no workaround.

CSCtx47330 (Catalyst Switches 3750, 3750 v2, and 2960-S)

After resetting a four-member stacked switch that includes a four-port Gigabit Ethernet network module, Gigabit Ethernet ports do not work.

There is no workaround.

CSCtx90729 (Catalyst 2960-S)

The switch halts on start up if power was lost during a previous front-end microcode update.

There is no workaround.

CSCty96049

Cisco IOS Software contains a vulnerability that could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition. An attacker could exploit this vulnerability by sending a single DHCP packet to or through an affected device, causing the device to reload.

Cisco has released free software updates that address this vulnerability. A workaround that mitigates this vulnerability is available. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120926-dhcp

Caveats Resolved in Cisco IOS Release 15.0(1)SE1

CSCth62705

CPU usage in the switch is high when you configure an EtherChannel and add new domain members or EnergyWise-capable endpoints with a different EnergyWise domain to an existing domain.

The workaround is to disable the port channel where the high CPU usage is seen.

CSCtq75612

If you combine two switches in a FlexStack configuration and set the password for the master switch, the change is not reflected in the show run command after you log out of the switch and log in again.

There is no workaround.

CSCtr28857

A vulnerability in the Multicast Source Discovery Protocol (MSDP) implementation of Cisco IOS Software and Cisco IOS XE Software could allow a remote, unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition.

Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-msdp

CSCtr31957

When the ipc_check_qtime_process() processes a message from the Inter-Process Communication (IPC) message table, it might be interrupted by the acknowledgement for that message. In this situation, the message becomes invalid because the interrupt handler returns that message to the message cache, and the switch crashes because it still attempts to access that message.

There is no workaround.

CSCtr49064

The Secure Shell (SSH) server implementation in Cisco IOS Software and Cisco IOS XE Software contains a denial of service (DoS) vulnerability in the SSH version 2 (SSHv2) feature. An unauthenticated, remote attacker could exploit this vulnerability by attempting a reverse SSH login with a crafted username. Successful exploitation of this vulnerability could allow an attacker to create a DoS condition by causing the device to reload. Repeated exploits could create a sustained DoS condition.

The SSH server in Cisco IOS Software and Cisco IOS XE Software is an optional service, but its use is highly recommended as a security best practice for the management of Cisco IOS devices. Devices that are not configured to accept SSHv2 connections are not affected by this vulnerability.

Cisco has released free software updates that address this vulnerability. This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-ssh

CSCtr75161

When you configure a web authentication profile with an access control list (ACL) policy on a switch, and also configure port ACL, the port ACL is applied to a host when it falls back to the web ACL.

There is no workaround. To retain the functionality, you can downgrade to Cisco IOS Release 12.2(55)SE.

CSCtr79386 - (Catalyst Switch 3750)

When you enable Dynamic Host Configuration Protocol (DHCP) snooping, the incoming traffic exhausts the I/O memory and the switch crashes.

The workaround is to disable DHCP snooping.

CSCtr91106

A vulnerability exists in the Cisco IOS Software that may allow a remote application or device to exceed its authorization level when authentication, authorization, and accounting (AAA) authorization is used. This vulnerability requires that the HTTP or HTTPS server is enabled on the Cisco IOS device.

Products that are not running Cisco IOS Software are not vulnerable.

Cisco has released free software updates that address these vulnerabilities.

The HTTP server may be disabled as a workaround for the vulnerability described in this advisory.

This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20120328-pai

CSCts36715

When a client connection to the web server fails, with each subsequent attempt the HTTP proxy server process is stuck and a new HTTP proxy server is created. To see these processes, enter the show processes command. When the number of processes reach the limit specified in the ip admission http proxy interface configuration command, all subsequent web authentications fail.

The workaround is to reload the switch.

CSCts52797 (Catalyst Switch 2960)

A Catalyst 2960 with 64Mb of DRAM might display low memory on the console after you upgrade the switch to 12.2(58)SE or later.

The workaround is to limit the memory that is used by different features on the switch if this release is required. You can reduce memory usage by minimizing the number of trunk ports and VLANs in use on the switch.

CSCts88664

During local web authentication, the switch crashes and reboots if the user enters his or her credentials and logs in instantly.

The workaround is to enter the user credentials and log in after a pause of 4-5 seconds.

CSCtt16051

Cisco IOS Software contains a vulnerability in the Smart Install feature that could allow an unauthenticated, remote attacker to cause a reload of an affected device if the Smart Install feature is enabled. The vulnerability is triggered when an affected device processes a malformed Smart Install message on TCP port 4786.

Cisco has released free software updates that address this vulnerability. There are no workarounds to mitigate this vulnerability.

This advisory is available at the following link:

http://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/
cisco-sa-20120328-smartinstall

CSCtt18020

The router reloads unexpectedly. This issue is seen when you log in to the router using SSH.

The workaround is to log in to the router using Telnet.

CSCtu09846

The switch crashes when users are redirected using central web authentication.

The workaround is to disable central web authentication.

Caveats Resolved in Cisco IOS Release 15.0(1)SE

CSCti30313 (Catalyst 2960 and 2960-S switches)

The output from the show sd

m prefer lanbase-routing privileged EXEC command shows some incorrect values. The corrected values are:

number of IPv4 unicast routes:                    4.25K should be: 0.75K
    number of directly-connected IPv4 hosts:        4K  should be: 0.75K
    number of indirect IPv4 routes:                 0.256    should be 16
 
   

There is no workaround.

CSCtj83964 (Catalyst 3750 and 3560 switches)

On a switch running Protocol-Independent Multicast (PIM) and Source Specific Multicast (SSM), multicast traffic might not be sent to the correct port after the switch reloads.

The workaround is to enter the clear ip route privileged EXEC command or reconfigure PIM and SSM after a reload.

CSCtl51859

Neighbor discovery fails for IPv6 hosts connected to the switch when the IPv6 MLD snooping feature is enabled globally on the switch.

The workaround is to disable IPv6 MLD snooping on the switch.

CSCtl81217 (Catalyst 3750 and 3560)

When a switch is using a DHCP server to assign IP addresses and an interface on the switch has RIP enabled, if the switch reloads, the interface loses some RIP configuration (specifically RIP authentication mode and RIP authentication key-chain). This does not happen when the IP address is statically configured on the interface. The problem occurs only when you configure RIP before an IP address is assigned by the DHCP server.

There is no workaround, but you can use an embedded event manager (EEM) script to add the interface configuration commands on the interface:

ip rip authentication mode

ip rip key-chain

CSCto10165

A vulnerability exists in the Smart Install feature of Cisco Catalyst Switches running Cisco IOS Software that could allow an unauthenticated, remote attacker to perform remote code execution on the affected device.

Cisco has released free software updates that address this vulnerability.

There are no workarounds available to mitigate this vulnerability other than disabling the Smart Install feature.

This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20110928-smart-install.shtml.

CSCtq01926

When you configure a port to be in a dynamic VLAN by entering the switchport access vlan dynamic interface configuration command on it, the switch might reload when it processes ARP requests on the port.

The workaround is to configure static VLANs for these ports.

CSCtq86035 (Catalyst 2960-S)

The switch might reload when you insert a USB flash device (also known as a thumb drive or a USB key) into the switch USB Type A port.

The workaround is to not insert a USB flash device into the USB Type A port.

Documentation Updates

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Software Configuration Guides

Update to the Catalyst 3750 Software Configuration Guide

Updates to the Catalyst 2960 and 2960-S Software Configuration Guide

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Command References

Updates to the System Message Guides

Updates to the Catalyst 2960 Hardware Installation Guide

Update to the Getting Started Guide

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Software Configuration Guides

Information Added to the "Administering the Switch" Chapter

In the "Administering the Switch" chapter, this information was added to the "NTP Version 4"section:

You can disable NTP packets from being received on routed ports and VLAN interfaces. You cannot disable NTP packets from being received on access ports. For details, see the "Disabling NTPv4 Services on a Specific Interface" section of the "Implementing NTPv4 in IPv6" chapter of the Cisco IOS IPv6 Configuration Guide, Release 12.4T.

Correction to the "Clustering Switches" Chapter

In the "Candidate Switch and Cluster Member Switch Characteristics" section of the "Clustering Switches" chapter, the requirements should include:

The ip http server global configuration command must be configured on the switch.

Correction to the "Configuring Network Security with ACLs" Chapter

The "Creating a Numbered Extended ACL" section of the "Configuring Network Security with ACLs" chapter has an error. Contrary to the note in this section, ICMP echo-replies can be filtered.

Correction to the "Managing Switch Stacks" Chapter

The "Master Election" section of the "Managing Switch Stacks" chapter in the Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 12.2(58)SE has an error. The fourth factor (highest uptime) is not considered by the Catalyst 2960-S switches.

Correction to the "Unsupported Commands" Chapter

The "Miscellaneous" section of the "Unsupported Commands" chapter should include the logging discriminator global configuration command.

Information Added to the "Configuring IEEE 802.1x Port-Based Authentication" Chapter

Configuring Critical Voice VLAN

When an IP phone connected to a port is authenticated by the access control server (ACS), the phone is put into the voice domain. If the ACS is not reachable, the switch cannot determine if the device is a voice device. If the server is unavailable, the phone cannot access the voice network and therefore cannot operate.

For data traffic, you can configure inaccessible authentication bypass, or critical authentication, to allow traffic to pass through on the native VLAN when the server is not available. If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is enabled, the switch grants the client access to the network and puts the port in the critical-authentication state in the RADIUS-configured or the user-specified access VLAN. When the switch cannot reach the configured RADIUS servers and new hosts cannot be authenticated, the switch connects those hosts to critical ports. A new host trying to connect to the critical port is moved to a user-specified access VLAN, the critical VLAN, and granted limited authentication.

With this release, you can enter the authentication event server dead action authorize voice interface configuration command to configure the critical voice VLAN feature. When the ACS does not respond, the port goes into critical authentication mode. When traffic coming from the host is tagged with the voice VLAN, the connected device (the phone) is put in the configured voice VLAN for the port. The IP phones learn the voice VLAN identification through CDP (Cisco devices) or through LLDP or DHCP.

You can configure the voice VLAN for a port by entering the switchport voice vlan vlan-id interface configuration command.

This feature is supported in multidomain and multi-auth host modes. Although you can enter the command when the switch in single-host or multi-host mode, the command has no effect unless the device changes to multidomain or multi-auth host mode.

Beginning in privileged EXEC mode, follow these steps to configure critical voice VLAN on a port and enable the inaccessible authentication bypass feature.

 
Command
Purpose

Step 1 

configure terminal

Enters global configuration mode.

Step 2 

radius-server dead-criteria time time tries tries

Sets the conditions that are used to decide when a RADIUS server is considered unavailable or down (dead).

The range for time is from 1 to 120 seconds. The switch dynamically determines a default seconds value between 10 and 60 seconds.

The range for tries is from 1 to 100. The switch dynamically determines a default tries parameter between 10 and 100.

Step 3 

radius-server deadtime minutes

(Optional) Sets the number of minutes during which a RADIUS server is not sent requests. The range is from 0 to 1440 minutes (24 hours). The default is 0 minutes.

Step 4 

radius-server host ip-address [acct-port udp-port] [auth-port udp-port] [test username name [idle-time time] [ignore-acct-port] [ignore-auth-port]] [key string]

Configures the RADIUS server parameters:

acct-port udp-port—Specifies the UDP port for the RADIUS accounting server. The range for the UDP port number is from 0 to 65536. The default is 1646.

auth-port udp-port—Specifies the UDP port for the RADIUS authentication server. The range for the UDP port number is from 0 to 65536. The default is 1645.

Note You should configure the UDP port for the RADIUS accounting server and the UDP port for the RADIUS authentication server to nondefault values.

test username nameEnables automatic testing of the RADIUS server status, and specifies the username to be used.

idle-time time—Sets the interval of time in minutes after which the switch sends test packets to the server. The range is from 1 to 35791 minutes. The default is 60 minutes (1 hour).

ignore-acct-portDisables testing on the RADIUS-server accounting port.

ignore-auth-portDisables testing on the RADIUS-server authentication port.

For key string, specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server.

Note Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon.

You can also configure the authentication and encryption key by using the radius-server key {0 string | 7 string | string} global configuration command.

Step 5 

interface interface-id

Specifies the port to be configured and enters interface configuration mode.

Step 6 

authentication event server dead action {authorize | reinitialize} vlan vlan-id

Configures a critical VLAN to move hosts on the port if the RADIUS server is unreachable:

authorize—Moves any new hosts trying to authenticate to the user-specified critical VLAN.

reinitialize—Moves all authorized hosts on the port to the user-specified critical VLAN.

Step 7 

switchport voice vlan vlan-id

Specifies the voice VLAN for the port. The voice VLAN cannot be the same as the critical data VLAN configured in Step 6.

Step 8 

authentication event server dead action authorize voice

Configures critical voice VLAN to move data traffic on the port to the voice VLAN if the RADIUS server is unreachable.

Step 9 

end

Returns to privileged EXEC mode.

Step 10 

show authentication interface interface-id

(Optional) Verifies your entries.

This example shows how to configure the inaccessible authentication bypass feature and configure the critical voice VLAN:

Switch(config)# radius-server dead-criteria time 30 tries 20
Switch(config)# radius-server deadtime 60
Switch(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 test username 
user1 idle-time 30 key abc1234
Switch(config)# interface gigabitethernet 1/0/1
Switch(config)# radius-server deadtime 60
Switch(config-if)# authentication event server dead action reinitialicze vlan 20
Switch(config-if)# switchport voice vlan
Switch(config-if)# authentication event server dead action authorize voice
Switch(config-if)# end

Network Edge Access Topology (NEAT) Enhancement

NEAT can control traffic exiting the supplicant switch port during the authentication period. When you connect a supplicant switch to an authenticator switch that has BPDU guard enabled, the authenticator port could be error-disabled if it receives a Spanning Tree Protocol (STP) bridge protocol data unit (BPDU) packets before the supplicant switch has authenticated. Beginning with Cisco IOS Release 15.0(1)SE, you can control traffic exiting the supplicant port during the authentication period. Entering the dot1x supplicant controlled transient global configuration command temporarily blocks the supplicant port during authentication to ensure that the authenticator port does not shut down before authentication completes. If authentication fails, the supplicant port opens. Entering the no dot1x supplicant controlled transient global configuration command opens the supplicant port during the authentication period. This is the default behavior.

We strongly recommend using the dot1x supplicant controlled transient command on a supplicant switch when BPDU guard is enabled on the authenticator switch port with the spanning-tree bpduguard enable cinterface configuration command.


Note If you globally enable BPDU guard on the authenticator switch by using the spanning-tree portfast bpduguard default global configuration command, entering the dot1x supplicant controlled transient command does not prevent the BPDU violation.


Update to the Catalyst 3750 Software Configuration Guide

In the "Managing Switch Stacks" chapter, this information is added.

In a mixed stack that has Catalyst 3750-X, Catalyst 3750-E, and Catalyst 3750 switches, we recommend that a Catalyst 3750-X switch be the master and that all stack members run Cisco IOS Release 12.2(53)SE2 or later. The Catalyst 3750 image is on the Catalyst 3750-X and 3750-E switches to simplify switch management.

To upgrade the stack, use the archive download-sw privileged EXEC command to download images to the master. For example, use the archive download-sw /directory tftp://10.1.1.10/ c3750-ipservicesk9-tar.122-55.SE1.tar c3750e-universalk9-tar.122-55.SE1.tar command to specify a directory, following the command with the list of tar files to download for the members.

The c3750-ipservicesk9-tar.122-55.SE1.tar is for the Catalyst 3750 members.

The c3750e-universalk9-tar.122-55.SE1.tar is for the Catalyst 3750-X and 3750-E members.

You can display the file list that is in the flash memory:

Switch# dir flash: c3750e-universalk9-tar.122-55.SE1
Directory of flash:/c3750e-universalk9-tar.122-55.SE1/
 
   5  -rwx   14313645   Mar 1 1993 00:13:55 +00:00   C3750e-universalk9-tar.122-55.SE1.tar
   6   drwx  5632       Mar 1 1993 00:15:22 +00:00   html
 443  -rwx   444        Mar 1 1993 00:15:58 +00:00   info
 444  -rwx   14643200   Mar 1 1993 00:04:32 +00:00   c3750-ipservicesk9-tar.122-55.SE1.tar
 
   

Update to the Catalyst 3750 and 2960-S Software Configuration Guide

In the "Displaying the Spanning-Tree Status" section of the "Configuring STP" chapter, this note should appear:


Note In a switch stack, the spanning-tree process reports both physical stack ports in a stack member as one logical port.


Updates to the Catalyst 2960 and 2960-S Software Configuration Guide

Correction to the "Configuring SDM Templates" Chapter

In the "Configuring SDM Templates" chapter, the LAN base routing template has incorrect values. The corrected values are:

number of IPv4 unicast routes:                    4.25K should be: 0.75K
    number of directly-connected IPv4 hosts:        4K  should be: 0.75K
    number of indirect IPv4 routes:                 0.256    should be 16

Correction: the "Configuring IPv6 ACLs" Chapter

The "Configuring IPv6 ACLs" chapter was omitted in error from the Catalyst 2960 and 2960-S Switches Software Configuration Guide, Release 12.2(58)SE. You can find the missing information in the "Configuring IPv6 ACLs" chapter in the Catalyst 3750 Switch Software Configuration Guide, Release 12.2(58)SE.

Updates to the Catalyst 3750, 3560, and 2960 and 2960-S Command References

These commands have been revised or added:

authentication event

dot1x supplicant controlled transient

authentication event

To set the actions for specific authentication events on the port, use the authentication event interface configuration command. To return to the default settings, use the no form of the command.

authentication event {fail [retry retry count] action {authorize vlan vlan-id | next-method}} | {no-response action authorize vlan vlan-id} | {server {alive action reinitialize} | {dead action {authorize {vlan vlan-id | voice} | reinitialize vlan vlan-id}}

no authentication event {[fail | no-response | {server {alive} | {dead [action {authorize {vlan vlan-id | voice} | reinitialize vlan}] }

Syntax Descriptionno authentication event {fail [action[authorize vlan vlan-id | next-method] {| retry {retry count}]} {no-response action authorize vlan vlan-id} {server {alive action reinitialize} | {dead action [authorize | reinitialize vlan vlan-id]}}

action

Configures the required action for an authentication event.

alive

Configures the authentication, authorization, and accounting (AAA) server alive actions.

authorize

Authorizes the VLAN on the port.

dead

Configures the AAA server dead actions.

fail

Configures the failed-authentication parameters.

next-method

Moves to next authentication method.

no-response

Configures the nonresponsive host actions.

reinitialize

Reinitializes all authorized clients.

retry

Enables retry attempts after a failed authentication.

retry count

Number of retry attempts from 0 to 5.

server

Configures the actions for AAA server events.

vlan

Specifies the authentication-fail VLAN.

vlan-id

VLAN ID number from 1 to 4094.

voice

Specifies that if the traffic from the host is tagged with the voice VLAN, the device is placed in the configured voice VLAN on the port.


Defaults

No event responses are configured on the port.

Command Modes

Interface configuration

Command History

Release
Modification

12.2(53)SE2

This command was introduced.

15.0(1)SE

The voice keyword was added.


Usage Guidelines

Use this command with the fail, no-response, or event keywords to configure the switch response for a specific action.

For authentication-fail events:

If the supplicant fails authentication, the port is moved to a restricted VLAN, and an EAP success message is sent to the supplicant because it is not notified of the actual authentication failure.

If the EAP success message is not sent, the supplicant tries to authenticate every 60 seconds (the default) by sending an EAP-start message.

Some hosts (for example, devices running Windows XP) cannot implement DHCP until they receive an EAP success message.

The restricted VLAN is supported only in single host mode (the default port mode). When a port is placed in a restricted VLAN, the supplicant MAC address is added to the MAC address table. Any other MAC address on the port is treated as a security violation.

You cannot configure an internal VLAN for Layer 3 ports as a restricted VLAN. You cannot specify the same VLAN as a restricted VLAN and as a voice VLAN.

Enable re-authentication with restricted VLANs. If re-authentication is disabled, the ports in the restricted VLANs do not receive re-authentication requests.

To start the re-authentication process, the restricted VLAN must receive a link-down event or an Extensible Authentication Protocol (EAP) logoff event from the port. If a host is connected through a hub:

The port might not receive a link-down event when the host is disconnected.

The port might not detect new hosts until the next re-authentication attempt occurs.

When you reconfigure a restricted VLAN as a different type of VLAN, ports in the restricted VLAN are also moved and stay in their currently authorized state.

For no-response events:

If you enable a guest VLAN on an IEEE 802.1x port, the switch assigns clients to a guest VLAN when it does not receive a response to its Extensible Authentication Protocol over LAN (EAPOL) request/identity frame or when EAPOL packets are not sent by the client.

The switch maintains the EAPOL packet history. If another EAPOL packet is detected on the port during the lifetime of the link, the guest VLAN feature is disabled. If the port is already in the guest VLAN state, the port returns to the unauthorized state, and authentication restarts. The EAPOL history is cleared.

If the switch port is moved to the guest VLAN (multihost mode), multiple non-IEEE 802.1x-capable clients are allowed access. If an IEEE 802.1x-capable client joins the same port on which the guest VLAN is configured, the port is put in the unauthorized state in the RADIUS-configured or user-configured access VLAN, and authentication restarts.

You can configure any active VLAN except a Remote Switched Port Analyzer (RSPAN) VLAN, a primary private VLAN, or a voice VLAN as an IEEE 802.1x guest VLAN. The guest VLAN feature is supported only on access ports. It is not supported on internal VLANs (routed ports) or trunk ports.

When MAC authentication bypass is enabled on an IEEE 802.1x port, the switch can authorize clients based on the client MAC address if IEEE 802.1x authentication times out while waiting for an EAPOL message exchange. After detecting a client on an IEEE 802.1x port, the switch waits for an Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address.

If authorization succeeds, the switch grants the client access to the network.

If authorization fails, the switch assigns the port to the guest VLAN if one is specified.

For more information, see the "Using IEEE 802.1x Authentication with MAC Authentication Bypass" section in the "Configuring IEEE 802.1x Port-Based Authentication" chapter of the software configuration guide.

For server-dead events:

When the switch moves to the critical-authentication state, new hosts trying to authenticate are moved to the critical-authentication VLAN (or critical VLAN). This applies whether the port is in single-host, multiple-host, multi-auth, or MDA mode. Authenticated hosts remain in the authenticated VLAN, and the reauthentication timers are disabled.

If a client is running Windows XP and the critical port to which the client is connected is in the critical-authentication state, Windows XP might report that the interface is not authenticated.

If the Windows XP client is configured for DHCP and has an IP address from the DHCP server and a critical port receives an EAP-Success message, the DHCP configuration process might not re-initiate.

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

Examples

This example shows how to configure the authentication event fail command:

Switch(config-if)# authentication event fail action authorize vlan 20
 
   

This example shows how to configure a no-response action:

Switch(config-if)# authentication event no-response action authorize vlan 10
 
   

This example shows how to configure a server-response action:

Switch(config-if)# authentication event server alive action reinitialize
 
   

This example shows how to configure a port to send both new and existing hosts to the critical VLAN when the RADIUS server is unavailable. Use this command for ports in multiple authentication (multi-auth) mode or if the voice domain of the port is in MDA mode:

Switch(config-if)# authentication event server dead action authorize vlan 10
 
   

This example shows how to configure a port to send both new and existing hosts to the critical VLAN when the RADIUS server is unavailable and if the traffic from the host is tagged with the voice VLAN to put the host in the configured voice VLAN on the port. Use this command for ports in multiple-host or multiauth mode:

Switch(config-if)# authentication event server dead action reinitialize vlan 10
Switch(config-if)# authentication event server dead action authorize voice

Related Commands

Command
Description

authentication control-direction

Configures the port mode as unidirectional or bidirectional.

authentication fallback

Configures a port to use web authentication as a fallback method for clients that do not support IEEE 802.1x authentication.

authentication host-mode

Sets the authorization manager mode on a port.

authentication open

Enables or disables open access on a port.

authentication order

Sets the order of authentication methods used on a port.

authentication periodic

Enables or disables reauthentication on a port.

authentication port-control

Enables manual control of the port authorization state.

authentication priority

Adds an authentication method to the port-priority list.

authentication timer

Configures the timeout and reauthentication parameters for an 802.1x-enabled port.

authentication violation

Configures the violation modes that occur when a new device connects to a port or when a new device connects to a port after the maximum number of devices are connected to that port.

show authentication

Displays information about authentication manager events on the switch.


dot1x supplicant controlled transient

To control access to an 802.1x supplicant port during authentication, use the dot1x supplicant controlled transient command in global configuration mode. To open the supplicant port during authentication, use the no form of this command

dot1x supplicant controlled transient

no dot1x supplicant controlled transient

Syntax Description

This command has no arguments or keywords.

Defaults

Access is allowed to 802.1x supplicant ports during authentication.

Command Modes

Global configuration

Command History

Release
Modification

15.0(1)SE

This command was introduced.


Usage Guidelines

In the default state, when you connect a supplicant switch to an authenticator switch that has BPCU guard enabled, the authenticator port could be error-disabled if it receives a Spanning Tree Protocol (STP) bridge protocol data unit (BPDU) packets before the supplicant switch has authenticated. Beginning with Cisco IOS Release 15.0(1)SE, you can control traffic exiting the supplicant port during the authentication period. Entering the dot1x supplicant controlled transient global configuration command temporarily blocks the supplicant port during authentication to ensure that the authenticator port does not shut down before authentication completes. If authentication fails, the supplicant port opens. Entering the no dot1x supplicant controlled transient global configuration command opens the supplicant port during the authentication period. This is the default behavior.

We strongly recommend using the dot1x supplicant controlled transient command on a supplicant switch when BPDU guard is enabled on the authenticator switch port with the spanning-tree bpduguard enable cinterface onfiguration command.


Note If you globally enable BPDU guard on the authenticator switch by using the spanning-tree portfast bpduguard default global configuration command, entering the dot1x supplicant controlled transient command does not prevent the BPDU violation.


Examples

This example shows how to control access to 802.1x supplicant ports on a switch during authentication:

Switch(config)# dot1x supplicant controlled transient

Related Commands

Command
Description

cisp enable

Enables Client Information Signalling Protocol (CISP) on a switch so that it acts as an authenticator to a supplicant switch.

dot1x credentials

Configures the 802.1x supplicant credentials on the port.

dot1x pae supplicant

Configures an interface to act only as a supplicant.


Updates to the System Message Guides

New System Messages

Error Message    IP-3-SBINIT: Error initializing [chars] subblock data structure. 
[chars]

Explanation    The subblock data structure was not initialized. [chars] is the structure identifier.

Recommended Action    No action is required.

Error Message    VLMAPLOG-6-ARP: vlan [dec] (port [chars]) denied arp ip [inet] -> 
[inet], [dec] packet[chars]

Explanation    A packet from the virtual LAN (VLAN) that matches the VLAN access-map (VLMAP) log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.

Recommended Action    No action is required.

Error Message    VLMAPLOG-6-L4: vlan [dec] (port [chars]) denied [chars] [inet]([dec]) 
-> [inet]([dec]), [dec] packet[chars]

Explanation    A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [chars] is the protocol, the first [inet] is the source IP address, the second [dec] is the source port, the second [inet] is the destination IP address, the third [dec] is the destination port, the fourth [dec] denotes the number of packets, and the third [chars] represents the letter "s" to indicate more than one packet.

Recommended Action    No action is required.

Error Message    VLMAPLOG-6-IGMP: vlan [dec] (port [chars]) denied igmp [inet] -> [inet] 
([dec]), [dec] packet[chars]

Explanation    A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Group Management Protocol (IGMP) message type, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.

Recommended Action    No action is required.

Error Message    VLMAPLOG-6-ICMP: vlan [dec] (port [chars]) denied icmp [inet] -> [inet] 
([dec]/[dec]), [dec] packet[chars]

Explanation    A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the first [inet] is the source IP address, the second [inet] is the destination IP address, the second [dec] is the Internet Control Message Protocol (ICMP) message type, the third [dec] is the ICMP message code, the fourth [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.

Recommended Action    No action is required.

Error Message    VLMAPLOG-6-IP: vlan [dec] (port [chars]) denied ip protocol=[dec]  
[inet] -> [inet], [dec] packet[chars]

Explanation    A packet from the VLAN that matches the VLMAP log criteria was detected. The first [dec] is the VLAN number, the first [chars] is the port name, the second [dec] is the protocol number, the first [inet] is the source IP address, the second [inet] is the destination IP address, the third [dec] denotes the number of packets, and the second [chars] represents the letter "s" to indicate more than one packet.

Recommended Action    No action is required.

Error Message    HARDWARE-2-PSU_THERMAL_WARNING: PSU [chars] temperature has reached 
warning threshold

Explanation    The switch power supply unit (PSU) temperature sensor value has reached the warning level. The external temperature is high. [chars] is the power supply.

Recommended Action    Reduce the temperature in the room. (The switch functions normally until the temperature reaches the critical level.)

Error Message    HARDWARE-1-PSU_THERMAL_CRITICAL: PSU [chars] temperature has reached 
critical threshold

Explanation    The switch PSU temperature sensor value has reached the critical level, and the switch cannot function normally. The external temperature is very high. [chars] is the power supply.

Recommended Action    Immediately reduce the room temperature.

Error Message    HARDWARE-5-PSU_THERMAL_NORMAL: PSU [chars] Temperature is within the 
acceptable limit

Explanation    The switch PSU temperature sensor value is within normal limits. [chars] is the power supply.

Recommended Action    No action is required.

Error Message    HARDWARE-2-THERMAL_WARNING: Temperature has reached warning threshold

Explanation    The switch temperature sensor value has reached the warning level. The external temperature is high.

Recommended Action    Reduce the room temperature. (The switch functions normally until the temperature reaches the critical level.)

Error Message    AUTHMGR-7-STOPPING: Stopping '[chars]' for client [enet] on Interface 
[chars] AuditSessionID [chars]

Explanation    The authentication process has been stopped. The first [chars] is the authentication method, [enet] is the Ethernet address of the host, the second [chars] is the interface for the host, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    AUTHMGR-7-NOMOREMETHODS: Exhausted all authentication methods for 
client ([chars]) on Interface [chars] AuditSessionID [chars]

Explanation    All available authentication methods have been tried. The first [chars] is the client identifier, the second [chars]s is the interface for the client, and the third [chars] is the session ID.

Recommended Action    No action is required.

Modified System Messages

Error Message    AUTHMGR-5-MACMOVE: MAC address ([enet]) moved from Interface [chars] 
to Interface [chars]

Explanation    The client moved to a new interface but did not log off from the first interface. [enet] is the MAC address of the client, the first [chars] is the earlier interface, and the second [chars] is the newer interface.

Recommended Action    No action is required.

Error Message    AUTHMGR-5-MACREPLACE: MAC address ([enet]) on Interface [chars] is 
replaced by MAC ([enet])

Explanation    A new client has triggered a violation that caused an existing client to be replaced. The first [enet] is the first client, [chars] is the interface, the second [enet] is the new client.

Recommended Action    No action is required.

Error Message    EOU-6-IDENTITY_MATCH: IP=[inet]| PROFILE=EAPoUDP| POLICYNAME=[chars]| 
AUDITSESSID=[chars]

Explanation    The router has found the specifed host under the Extensible Authentication Protocol over User Datagram Protocol (EAPoUDP) identity profile. [inet] is the host IP address, the first [chars] is the enforced policy, and the second [chars] is the session ID.

Recommended Action    If you do not want the host to be exempt from authentication, remove its entry from the EAPoUDP identity profile.

Error Message    EOU-5-RESPONSE_FAILS: Received an EAP failure response from AAA for 
host=[inet]| AUDITSESSID=[chars]

Explanation    The router received an EAP failure response from authentication, authorization, and accounting (AAA). The host credentials were not validated. [inet] is the host, and [chars] is the session ID.

Recommended Action    Check for causes of unsuccessful AAA validation of host credentials.

Error Message    EOU-6-SESSION: IP=[inet]| HOST=[chars]| Interface=[chars]| 
AUDITSESSID=[chars]

Explanation    An entry for the host was created or deleted on the specified interface. [inet] is the host IP address, the first [chars] is the host identifier, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    EOU-4-VERSION_MISMATCH: HOST=[inet]| Version=[dec]| 
AUDITSESSID=[chars]

Explanation    A mismatch in the EAPoUDP versions was detected from the host. [inet] is the host identifier, [dec] is the EAPoUDP version, and [chars] is the session ID.

Recommended Action    Check EAPoUDP versions on peers.

Error Message    EOU-6-POSTURE: IP=[inet]| HOST=[chars]| 
Interface=[chars]|AUDITSESSID=[chars]

Explanation    The posture validation status for the host. [inet] is the host IP address, the first [chars] is the host identfier, the second [chars] is the host interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    EOU-6-AUTHTYPE: IP=[inet]| AuthType=[chars]| AUDITSESSID=[chars]

Explanation    The authentication type for the host. [inet] is the host IP address, the first [chars] is the authentication type, and the second [chars] is the session ID.

Recommended Action    No action is required.

Error Message    EOU-4-UNKN_EVENT_ERR: UNKNOWN Event for  HOST=[inet]| Event=[dec]| 
AUDITSESSID=[chars]

Explanation    Unknown message for the EAPoUDP process. [inet] is the host identifier, [dec] is the event identifier, and [chars] is the session ID.

Recommended Action    File a DDTS with Cisco.

Error Message    EOU-5-AAA_DOWN: AAA unreachable. METHODLIST=[chars]| HOST=[inet]| 
POLICY=[chars].| AUDITSESSID=[chars]

Explanation    The AAA servers defined by the method list cannot be reached by the host and the applied policy. The first [chars] is the method list identifer, [inet] is the host identifier, the second [chars] is the policy, and the third [chars] is the session ID.

Recommended Action    Check the possible causes for unreachable AAA servers.

Error Message    MAB-5-FAIL: Authentication failed for client ([chars]) on Interface 
[chars] AuditSessionID [chars]

Explanation    Authentication was unsuccessful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Error Message    MAB-5-SUCCESS: Authentication successful for client ([chars]) on 
Interface [chars] AuditSessionID [chars]

Explanation    Authentication was successful. The first [chars] is the client, the second [chars] is the interface, and the third [chars] is the session ID.

Recommended Action    No action is required.

Deleted System Messages

Error Message    IP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry: [inet], hw: 
[enet] by hw: [enet]\n", MSGDEF_LIMIT_FAST

Explanation    Multiple stations are configured with the same IP address in a private VLAN. (This could be a case of IP address theft.) [inet] is the IP address that is configured, the first [enet] is the original MAC address associated with the IP address, and the second [enet] is the MAC address that triggered this message.

Recommended Action    Change the IP address of one of the two systems.

Updates to the Catalyst 2960 Hardware Installation Guide

Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.

You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).

This applies to all Cisco Ethernet switches except for these compact models:

Catalyst 2960-8TC switch—8 10/100BASE-T Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)

Catalyst 2960G-8TC switch—7 10/100/100BASE-T Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)

Update to the Getting Started Guide

When you launch Express Setup, you are prompted for the switch password. Enter the default password, cisco. The switch ignores text in the username field. Before you complete and exit Express Setup, you must change the password from the default password, cisco.

Update to the Catalyst 2960-S Switch Getting Started Guide

This correction applies to the French, Italian, German, Spanish, Japanese, and simplified Chinese versions of the getting started guide:

In the "Unpacking the Switch" section, four number-8 Phillips flat-head screws (48-0655-01) are included with the switch.

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.

These documents provide complete information about the Catalyst 3750, 3560, 2975, 2960-S and 2960 switches and the Cisco EtherSwitch service modules and are available at Cisco.com:

http://www.cisco.com/en/US/products/hw/switches/ps5023/tsd_products_support_series_home.html

http://www.cisco.com/en/US/products/hw/switches/ps5528/tsd_products_support_series_home.html

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

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

These documents provide complete information about the Catalyst 3750 switches and the Cisco EtherSwitch service modules:

Catalyst 3750 Switch Software Configuration Guide

Catalyst 3750 Switch Command Reference

Catalyst 3750, 3560, 3550, 2975, 2970, 2960, and 2960-S Switch System Message Guide

Catalyst 3750 Switch Hardware Installation Guide

Catalyst 3750 Getting Started Guide

Catalyst 3750 Integrated Wireless LAN Controller Switch Getting Started Guide

Regulatory Compliance and Safety Information for the Catalyst 3750 Switch

These documents provide complete information about the Catalyst 3750G Integrated Wireless LAN Controller Switch and the integrated wireless LAN controller and are available at cisco.com:

Catalyst 3750 Integrated Wireless LAN Controller Switch Getting Started Guide

Release Notes for Cisco Wireless LAN Controller and Lightweight Access Point, Release 4.0.x.0

Cisco Wireless LAN Controller Configuration Guide, Release 4.0

Cisco Wireless LAN Controller Command Reference, Release 4.0

These documents provide complete information about the Catalyst 3560 switches:

Catalyst 3560 Switch Software Configuration Guide

Catalyst 3560 Switch Command Reference

Catalyst 3750, 3560, 3550, 2975, 2970, 2960, and 2960-S Switch System Message Guide

Catalyst 3560 Switch Hardware Installation Guide

Catalyst 3560 Switch Getting Started Guide

Regulatory Compliance and Safety Information for the Catalyst 3560 Switch

These documents provide complete information about the Catalyst 2960 and 2960-S switches and are available on Cisco.com:

Catalyst 2960 and 2960-S Switch Software Configuration Guide

Catalyst 2960 and 2960-S Switch Command Reference

Catalyst 3750, 3560, 3550, 2975, 2970, 2960, and 2960-S Switch System Message Guide

Catalyst 2960-S Switch Hardware Installation Guide

Catalyst 2960-S Switch Getting Started Guide

Catalyst 2960 Switch Hardware Installation Guide

Catalyst 2960 Switch Getting Started Guide

Catalyst 2960 Switch Getting Started Guide—available in English, simplified Chinese, French, German, Italian, Japanese, and Spanish

Regulatory Compliance and Safety Information for the Catalyst 2960 and 2960-S Switch

For other information about related products, see these documents:

Smart Install Configuration Guide

Auto Smartports Configuration Guide

Cisco EnergyWise Configuration Guide

Getting Started with Cisco Network Assistant

Release Notes for Cisco Network Assistant

Cisco RPS 300 Redundant Power System Hardware Installation Guide

Cisco RPS 675 Redundant Power System Hardware Installation Guide

For more information about the Network Admission Control (NAC) features, see the Network Admission Control Software 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

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.