Guest

Cisco Catalyst 3560 Series Switches

Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(25)SED

  • Viewing Options

  • PDF (886.7 KB)
  • Feedback
Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(25)SED and Later

Table Of Contents

Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(25)SED and Later

Contents

System Requirements

Hardware Supported

Device Manager System Requirements

Hardware Requirements

Software Requirements

Cluster Compatibility

Upgrading the Switch Software

Finding the Software Version and Feature Set

Deciding Which Files to Use

Archiving Software Images

Upgrading a Switch by Using the Device Manager or Network Assistant

Upgrading a Switch by Using the CLI

Recovering from a Software Failure

Installation Notes

New Features

New Hardware Features

New Software Features

Minimum Cisco IOS Release for Major Features

Limitations and Restrictions

Cisco IOS Limitations

Configuration

Ethernet

Fallback Bridging

HSRP

IP

IP Telephony

Management

MAC Addressing

Multicasting

Power

QoS

Routing

SPAN and RSPAN

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

Trunking

VLAN

Device Manager Limitations

Important Notes

Switch Stack Notes

Cisco IOS Notes

Device Manager Notes

Open Caveats

Resolved Caveats

Resolved Caveats in Cisco IOS Release 12.2(25)SED1

Resolved Caveats in Cisco IOS Release 12.2(25)SED

Documentation Updates

Updates to the Software Configuration Guides

Updates to the Regulatory Compliance and Safety Information

Statement 361—VoIP and Emergency Calling Services do not Function if Power Fails

Related Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(25)SED and Later


Revised November 9, 2006

The Cisco IOS Release 12.2(25)SED runs on all Catalyst 3750, 3560, 2970, and 2960 switches and on Cisco EtherSwitch service modules.

The Catalyst 3750 switches and the Cisco EtherSwitch service modules support stacking through Cisco StackWise technology. The Catalyst 3560, 2970, and 2960 switches do not support switch stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.

These release notes include important information about Cisco IOS Release 12.2(25)SED and
Cisco IOS Release 12.2(25)SED1 and any limitations, restrictions, and caveats that apply to them. 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.

For the complete list of Catalyst 3750, 3560, 2970, and 2960 switch documentation and of Cisco EtherSwitch service module documentation, see the "Related Documentation" section.

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

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


Note For IPv6 capability on the Catalyst 3750 or 3560 switches or on Cisco EtherSwitch service modules, you must order the advanced IP services image upgrade from Cisco.


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

Cisco IOS Release 12.2(25)SED is based on Cisco IOS Release 12.2(25)S. Open caveats in Cisco IOS Release 12.2(25)S also affect Cisco IOS Release 12.2(25)SED, unless they are listed in the Cisco IOS Release 12.2(25)SED resolved caveats list. The list of open caveats in Cisco IOS Release 12.2(25)S is available at this URL:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122relnt/122srn.htm#wp2367913

Contents

This information is in the release notes:

"System Requirements" section

"Upgrading the Switch Software" section

"Installation Notes" section

"New Features" section

"Minimum Cisco IOS Release for Major Features" section

"Limitations and Restrictions" section

"Important Notes" section

"Open Caveats" section

"Resolved Caveats" section

"Documentation Updates" section

"Related Documentation" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

System Requirements

The system requirements are described in these sections:

"Hardware Supported" section

"Device Manager System Requirements" section

"Cluster Compatibility" section

Hardware Supported

Table 1 lists the hardware supported on Cisco IOS Release 12.2SE.

Table 1 Catalyst 3750, 3560, 2970, and 2960 Switches and Cisco EtherSwitch Service Modules Supported Hardware 

Switch
Description
Supported by Minimum Cisco IOS Release

Catalyst 3750-24FS

24 100BASE-FX ports and 2 SFP1 module slots

Cisco IOS Release 12.2(25)SEB

Catalyst 3750-24PS

24 10/100 PoE2 ports and 2 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3750-24TS

24 10/100 Ethernet ports and 2 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3750-48PS

48 10/100 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3750-48TS

48 10/100 Ethernet ports and 4 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3750G-12S

12 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3750G-16TD

16 10/100/1000 Ethernet ports and 1 XENPAK 10-Gigabit Ethernet module slot

Cisco IOS Release 12.2(18)SE

Catalyst 3750G-24PS

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

Cisco IOS Release 12.2(20)SE3

Catalyst 3750G-24T

24 10/100/1000 Ethernet ports

Cisco IOS Release 12.2(18)SE

Catalyst 3750G-24TS

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

Cisco IOS Release 12.2(18)SE

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 3560-24PS

24 10/100 PoE ports and 2 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3560-24TS

24 10/100 ports and 2 SFP module slots

Cisco IOS Release 12.2(20)SE3

Catalyst 3560-48PS

48 10/100 PoE ports and 4 SFP module slots

Cisco IOS Release 12.2(18)SE

Catalyst 3560-48TS

48 10/100 ports and 4 SFP module slots

Cisco IOS Release 12.2(20)SE3

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 2970G-24T

24 10/100/1000 Ethernet ports

Cisco IOS Release 12.2(18)SE

Catalyst 2970G-24TS

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

Cisco IOS Release 12.2(18)SE

Catalyst 2960-24TC

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

Cisco IOS Release 12.2(25)FX

Catalyst 2960-48TC

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

Cisco IOS Release 12.2(25)FX

Catalyst 2960-24TT

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

Cisco IOS Release 12.2(25)FX

Catalyst 2960-48TT

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

Cisco IOS Release 12.2(25)FX

Catalyst 2960G-24TC

24 10/100/1000BASE-T Ethernet ports and 4 of these are dual-purpose uplinks1 (four 10/100/1000BASE-T copper ports and four SFP module slots)

Cisco IOS Release 12.2(25)FX

NME-16ES-1G5

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

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-1G5

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

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

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

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

Cisco IOS Release 12.2(25)EZ

SFP modules (Catalyst 3750, 3560, and 2970)

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

100BASE-FX MMF7

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

 

Cisco IOS Release 12.2(25)FX

XENPAK modules8

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

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)

Supported on all software releases

1 SFP = small form-factor pluggable

2 PoE = Power over Ethernet

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

4 SFP = small form-factor pluggable

5 Cisco EtherSwitch service module

6 CWDM = coarse wavelength-division multiplexer

7 MMF = multimode fiber

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


Device Manager System Requirements

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

"Hardware Requirements" section

"Software Requirements" section

Hardware Requirements

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

Table 2 Minimum Hardware Requirements 

Processor Speed
DRAM
Number of Colors
Resolution
Font Size

Intel Pentium II1

64 MB2

256

1024 x 768

Small

1 We recommend Intel Pentium 4.

2 We recommend 256-MB DRAM.


Software Requirements

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


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


Table 3 Supported Operating Systems and Browsers 

Operating System
Minimum Service Pack or Patch
Microsoft Internet Explorer 1
Netscape Navigator

Windows 98

None

5.5 or 6.0

7.1

Windows NT 4.0

Service Pack 6 or later

5.5 or 6.0

7.1

Windows 2000

None

5.5 or 6.0

7.1

Windows XP

None

5.5 or 6.0

7.1

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


Cluster Compatibility

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

When creating a switch cluster or adding a switch to a cluster, follow these guidelines:

When you create a switch cluster, we recommend configuring the highest-end switch in your cluster as the command switch.

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

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

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.

Upgrading the Switch Software

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

"Finding the Software Version and Feature Set" section

"Deciding Which Files to Use" section

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

"Upgrading a Switch by Using the CLI" section

"Recovering from a Software Failure" section

Finding the Software Version and Feature Set

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

You can use the show version privileged EXEC command to see the software version that is running on your switch. The second line of the display shows the version.


Note 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 [formerly known as the SMI] or IP services image [formerly known as the EMI]) and does not change if you upgrade the software image.


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

Deciding Which Files to Use

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

For the Catalyst 3750 and 3560 switches, Cisco IOS Release 12.2(25)SEA and earlier referred to the image that provides Layer 2+ features and basic Layer 3 routing as the standard multilayer image (SMI). The image that provides full Layer 3 routing and advanced services was referred to as the enhanced multilayer image (EMI).

Cisco IOS Release 12.2(25)SEB and later refers to the SMI as the IP base image and the EMI as the IP services image.

Cisco IOS Release 12.2(25)SEB and later refers to the Catalyst 2970 image as the LAN base image.

Table 4 lists the different file-naming conventions before and after Cisco IOS Release 12.2(25)SEB.

Table 4 Cisco IOS Image File Naming Convention 

Cisco IOS 12.2(25)SEA and earlier
Cisco IOS 12.2(25)SEB and later

c3750-i9-mz (SMI1 )

c3750-ipbase-mz

c3750-i9k91-mz (SMI)

c3750-ipbasek9-mz

c3750-i5-mz (EMI2 )

c3750-ipservices-mz

c3750-i5k91-mz (EMI)

c3750-ipservicesk9-mz

c3560-i9-mz (SMI)

c3560-ipbase-mz

c3560-i9k91-mz (SMI)

c3560-ipbasek9-mz

c3560-i5-mz (EMI)

c3560-ipservices-mz

c3560-i5k91-mz (EMI)

c3560-ipservicesk9-mz

c2970-i6l2-mz

c2970-lanbase-mz

c2970-i6k91l2-mz

c2970-lanbasek9-mz

1 SMI = standard multilayer image

2 EMI = enhanced multilayer image


Table 5 lists the filenames for this software release.


Note For IPv6 capability on the Catalyst 3750 or 3560 switch or on the Cisco EtherSwitch service modules, you must order the advanced IP services image upgrade from Cisco.


Table 5 Cisco IOS Software Image Files 

Filename

Description

c3750-ipbase-tar.122-25.SED1.tar

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

c3750-ipservices-tar.122-25.SED1.tar

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

c3750-ipbasek9-tar.122-25.SED1.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.122-25.SED1.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.

c3750-advipservicesk9-tar.122-25.SED1.tar

Catalyst 3750 advanced IP services image, cryptographic file, and device manager files.
This image has all the IP services image (formerly known as the EMI) features and the capability for unicast routing of IPv6 packets.
This image also runs on the Cisco EtherSwitch service modules.

c3560-ipbase-tar.122-25.SED1.tar

Catalyst 3560 IP base image file and device manager files.
This image has Layer 2+ and basic Layer 3 routing features.

c3560-ipservices-tar.122-25.SED1.tar

Catalyst 3560 IP services image and device manager files.
This image has both Layer 2+ and full Layer 3 routing features.

c3560-ipbasek9-tar.122-25.SED1.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.122-25.SED1.tar

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

c3560-advipservicesk9-tar.122-25.SED1.tar

Catalyst 3560 advanced IP services image, cryptographic file, and device manager files.
This image has all the IP services image (formerly known as the EMI) features and the capability for unicast routing of IPv6 packets.

c2970-lanbase.122-25.SED1.tar

Catalyst 2970 image file and device manager files.
This image has Layer 2+ features.

c2970-lanbasek9-tar.122-25.SED1.tar

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

c2960-lanbase-tar.122-25.SED.tar

Catalyst 2960 image file and device manager files.
This image has Layer 2+ features.

c2960-lanbasek9-tar.122-25.SED.tar

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

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/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html

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


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


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

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/ffun_r/ffrprt2/frf011.htm#wp1018426

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 5 to identify the file that you want to download.

Step 2 Download the software image file. If you have a SmartNet support contract, go to this URL, and log in to download the appropriate files:

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

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

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

To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3560 switch, click Catalyst 3560 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560 3DES Cryptographic Software.

To download the IP services image (formerly known as the EMI) or IP base image (formerly known as the SMI) files for a Catalyst 3750 switch, click Catalyst 3750 software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750 3DES Cryptographic Software.


Caution If you are upgrading a Catalyst 3750 or a Catalyst 2970 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.

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-25.SED.tar

You can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.


Recovering from a Software Failure

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

Installation Notes

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

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

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

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

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


Note If you are upgrading a Catalyst 3750 or a 2950 switch running Cisco IOS Release 12.1(11)AX, which uses the IEEE 802.1x feature, you must re-enable IEEE 802.1x after upgrading the software. For more information, see the "Cisco IOS Notes" section.



Note When upgrading or downgrading from Cisco IOS Release 12.2(18)SE, you might need to reconfigure the switch with the same password that you were using when running Cisco IOS Release 12.2(18)SE. This problem only occurs when changing from Cisco IOS Release 12.2(18)SE to any other release. (CSCed88768)


New Features

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

"New Hardware Features" section

"New Software Features" section

New Hardware Features

There are no new hardware features for this release. For a list of all supported hardware, see the "Hardware Supported" section.

New Software Features

This release contains these new switch features or enhancements (available in all software images unless otherwise noted):

Restricted VLAN to provide limited services to users who are IEEE 802.1x-compliant, but do not have the credentials to authenticate through the standard IEEE 802.1x processes.

The QoS feature for hierarchical policy maps on each port. This means each defined class map can have a different policer.

Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP Version 6 (IPv6) multicast data to clients and routers in a switched network. (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules only)

IPv6 access control lists (ACLs). (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules only)

Access Switch Database Management (SDM) templates. (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules only)

Network Admission Control (NAC) features:

NAC Layer 2 IEEE 802.1x validation to validate the antivirus condition or posture of endpoint systems or clients before granting the devices network access by using IEEE 802.1x port-based authentication on the network edge.

NAC Layer 2 IP validation to validate the posture of endpoint systems or clients before granting the devices network access by using UDP on the network edge. (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules only)

IEEE 802.1x inaccessible authentication bypass. (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules only)

For more information about these NAC features, see these documents:

Configuring Network Admission Control feature module at this URL:
http://www.cisco.com/en/US/netsol/ns617/networking_solutions_sub_solution_home.html

Release Notes for Network Admission Control, Release 2.0 at this URL
http://www.cisco.com/en/US/netsol/ns617/networking_solutions_release_notes_list.html.

The Network Admission Control feature module at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/
products_feature_guide09186a008021650d.html

The Cisco IOS Security Command Reference, Release 12.3 at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/
products_command_reference_book09186a00801a7f8b.html

Minimum Cisco IOS Release for Major Features

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

Table 6 Catalyst 3750, 3560, 2970, 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

NAC Layer 2 IEEE 802.1x validation

12.2(25)SED

3750, 3560, 2970, and 2960

Cisco EtherSwitch service modules

NAC Layer 2 IP validation

12.2(25)SED

3750, 3560

Cisco EtherSwitch service modules

NAC IEEE 802.1x inaccessible authentication bypass

12.2(25)SED

3750, 3560

Cisco EtherSwitch service modules

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

Cisco EtherSwitch service modules

IEEE 802.1x inaccessible authentication bypass.

12.2(25)SED

3750, 3560

Cisco EtherSwitch service modules

IEEE 802.1x with restricted VLAN

12.2(25)SED

3750, 3560, 2970

Cisco EtherSwitch service modules

Budgeting power for devices connected to PoE ports

12.2(25)SEC

3750 and 3560

Cisco EtherSwitch service modules

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

12.2(25)SEC

3750, 3560, 2970

Cisco EtherSwitch service modules

Unique device identifier (UDI)

12.2(25)SEC

3750, 3560, 2970

Cisco EtherSwitch service modules

VRF-Lite (multi-VRF-CE). This feature is not supported in the IP base image. Although configuration is allowed in this release, we strongly recommend that you do not configure it. Beginning with Cisco IOS Release 12.2(35)SE, you will receive an error message if you configure the feature on the IP base image.

12.2(25)SEC

3750, 3560, 2970

Cisco EtherSwitch service modules

IEEE 802.1x with wake-on-LAN

12.2(25)SEC

12.2(25)SED

3750, 3560, 2970

Cisco EtherSwitch service modules

2960

Nonstop forwarding (NSF) awareness

12.2(25)SEC

3750 and 3560

Cisco EtherSwitch service modules

Configuration logging

12.2(25)SEC

12.2(25)SED

3750, 3560, 2970

Cisco EtherSwitch service modules

2960

Secure Copy Protocol

12.2(25)SEC

12.2(25)SED

3750, 3560, 2970

Cisco EtherSwitch service modules

2960

Cross-stack EtherChannel

12.2(25)SEC

3750

Cisco EtherSwitch service modules

Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP base image [formerly known as the SMI] only)

12.2(25)SEB

3750 and 3560

Support for IP source guard on private VLANs (IP base image [formerly known as the SMI] only)

12.2(25)SEB

3750 and 3560

Support for configuring an IEEE 802.1x restricted VLAN

12.2(25)SED

3750, 3560, 2970, 2960

IGMP leave timer

12.2(25)SEB

3750, 3560, 2970

IGMP snooping querier

12.2(25)SEA

12.2(25)FX

3750, 3560, 2970

2960

Advanced IP services

12.2(25)SEA

3750, 3560

Support for DSCP transparency

12.2(25)SE

12.2(25)FX

3750, 3560, 2970

2960

Support for VLAN-based QoS1 and hierarchical policy maps on SVIs2

12.2(25)SE

3750, 3560, 2970

Device manager

12.2(25)SE

12.2(25)FX

3750, 3560, 2970

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

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

12.2(25)SE

12.2(25)FX

3750, 3560, 2970

2960

Support for configuring private-VLAN ports on interfaces that are configured for dynamic ARP inspection (IP services image [formerly known as the EMI] only)

12.2(25)SE

3750 and 3560

Support for IP source guard on private VLANs (IP services image [formerly known as the EMI] only)

12.2(25)SE

3750 and 3560

Cisco intelligent power management to limit the power allowed on a port, or pre-allocate (reserve) power for a port.

12.2(25)SE

3750 and 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, 2970

2960

Dynamic ARP inspection (IP services image [formerly known as the EMI] only)

12.2(20)SE

3750 and 3560

Flex Links

12.2(20)SE

12.2(25)FX

3750, 3560, 2970

2960

Software upgrade (device manager or Network Assistant only)

12.2(20)SE

12.2(25)FX

3750, 3560, 2970

2960

IP source guard (IP services image [formerly known as the EMI] only)

12.2(20)SE

3750, 3560

Private VLAN (IP services image [formerly known as the EMI] only)

12.2(20)SE

3750, 3560

SFP module diagnostic management interface

12.2(20)SE

12.2(25)FX

3750, 3560, 2970

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

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.

This section contains these limitations:

"Cisco IOS Limitations" section

"Device Manager Limitations" section

Cisco IOS Limitations

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

"Configuration" section

"Ethernet" section

"Fallback Bridging" section

"HSRP" section

"IP" section

"IP Telephony" section

"MAC Addressing" section

"Management" section

"Multicasting" section

"QoS" section

"Routing" section

"SPAN and RSPAN" section

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

"Trunking" section

"VLAN" section

Configuration

These are the configuration limitations:

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

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, 3560, or 2970 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, 3560, or 2970 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)

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

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

(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 bps, 19200 bps, and 38400 bps) 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)

When a Catalyst 3750-12S switch boots up, ports 1, 2, 5, 6, 9, and 10 can become active before the Cisco IOS software loading process is complete. Packets arriving at these ports before the switch software is completely loaded are lost. This is a hardware limitation when the switch uses small form-factor pluggable (SFP) modules with copper connections.

The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links. (CSCeh70503)

Ethernet

These are the Ethernet limitations:

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 these switch ports:

Ports 3, 4, 7, 8, 11, 12, 15, 16, 19, 20, 23, and 24 of the Catalyst 3750G-24T and 3750G-24TS switches

Ports 3, 4, 7, 8, 11, 12, 15, 16, 19, and 20 of the Catalyst 2970G-24T and 2970G-24TS switches

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 Mbps instead of for 10/100 Mbps.

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)

Fallback Bridging

These are the fallback bridging limitations:

(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

This is the Hot Standby Routing Protocol (HSRP) limitation:

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

These are the IP limitations:

(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

These are the IP telephony limitations:

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)

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)

Management

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

MAC Addressing

This is the MAC addressing limitation:

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

Multicasting

These are the multicasting limitations:

(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 IG MP 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)

If IP routing is disabled and IP multicast routing is enabled on a switch running Cisco IOS Release 12.2(25)SED, IGMP snooping floods multicast packets to all ports in a VLAN.

The workaround is to enable IP routing or to disable multicast routing on the switch. You can also use the ip igmp snooping querier global configuration command if IP multicast routing is enabled for queries on a multicast router port. (CSCsc02995)

Power

These are the powers limitation for the Cisco EtherSwitch service modules:

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

These are the quality of service (QoS) limitations:

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)

Routing

These are the routing limitations:

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

SPAN and RSPAN

These are the SPAN and Remote SPAN (RSPAN) limitations.

(Catalyst 3750 or 3560 switches and 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 these switches (CSCdy72835):

3560-24PS

3560-48PS

3750-24PS

3750-48PS

3750-24TS

3750-48TS

3750G-12S

3750G-24T

3750G-24TS

3750G-16TD

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 these switches (CSCdy81521):

2970G-24T

2970G-24TS

3560-24PS

3560-48PS

3750-24PS

3750-48PS

3750-24TS

3750-48TS

3750G-12S

3750G-24T

3750G-24TS

3750G-16TD

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 these switches (CSCea72326):

2970G-24T

2970G-24TS

3560-24PS

3560-48PS

3750-24PS

3750-48PS

3750-24TS

3750-48TS

3750G-12S

3750G-24T

3750G-24TS

3750G-16TD

Cisco EtherSwitch service modules

(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 running Cisco IOS Release 12.1(14)EA1 and later, on Catalyst 3560 switches running Cisco IOS release 12.1(19)EA1 or later, 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)

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

These are the Catalyst 3750 and Cisco EtherSwitch service module switch stack limitations:

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 boot 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 Mbps egress interface, the ingress interface might drop more packets due to oversubscription if the egress interface is on a Fast Ethernet switch (such as a Catalyst 3750-24TS or 3750-48TS switch) than if it is on a Gigabit Ethernet switch (such as a Catalyst 3750G-24T or 3750G-24TS 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 (formerly known as the SMI) and the old stack master was running the IP services image (formerly known as the EMI).

Private VLAN is enabled or disabled on a switch stack, depending on whether or not the stack master is running the IP services image (formerly known as the EMI) or the IP base image (formerly known as the SMI):

If the stack master is running the IP services image (formerly known as the EMI), all stack members have private VLAN enabled.

If the stack master is running the IP base image (formerly known as the SMI), 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 (formerly known as the EMI) and the new stack master is running the IP base image (formerly known as the SMI). 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 (formerly known as the EMI) to IP base image (formerly known as the SMI) master switch change (or the reverse).

Before an IP services image (formerly known as the EMI)-to-IP base image (formerly known as the SMI) 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)

Trunking

These are the trunking limitations:

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

These are the VLAN limitations:

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)

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

These sections describe the important notes related to this software release for the Catalyst 3750, 3560, 2970, and 2960 switches and for the Cisco EtherSwitch service modules:

"Switch Stack Notes" section

"Cisco IOS Notes" section

"Device Manager Notes" section

Switch Stack Notes

These notes apply to switch stacks:

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

The Catalyst 3560 and 2970 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.

Cisco IOS Notes

These notes apply to Cisco IOS software:

The IEEE 802.1x feature in Cisco IOS Release 12.1(14)EA1 and later is not fully backward-compatible with the same feature in Cisco IOS Release 12.1(11)AX. If you are upgrading a Catalyst 3750 or a 2970 switch running Cisco IOS Release 12.1(11)AX that has IEEE 802.1x configured, you must re-enable IEEE 802.1x after the upgrade by using the dot1x system-auth-control global configuration command. This global command does not exist in Cisco IOS Release 12.1(11)AX. Failure to re-enable IEEE 802.1x weakens security because some hosts can then access the network without authentication.

The behavior of the no logging on global configuration command changed in Cisco IOS Release 12.2(18)SE and later. In Cisco IOS Release 12.1(19)EA and earlier, both of these command pairs disabled logging to the console:

the no logging on and then the no logging console global configuration commands

the logging on and then the no logging console global configuration commands

In Cisco IOS Release 12.2(18)SE and later, you can only use the logging on and then the no logging console global configuration commands to disable logging to the console. (CSCec71490)

In Cisco IOS Release 12.2(25)SEC for the Catalyst 3750, 3560, and 2970 switches and in Cisco IOS Release 12.2(25)SED for the Catalyst 2960 switch, the implementation for multiple spanning tree (MST) changed from the previous release. Multiple STP (MSTP) complies with the IEEE 802.1s standard. Previous MSTP implementations were based on a draft of the IEEE 802.1s standard.

Device Manager Notes

These notes apply to the device manager:

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

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.

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

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

ip http authentication {aaa | enable | local}

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

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

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

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

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show running-config

Verify your entries.

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

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

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

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

 
Command
Purpose

Step 1 

configure terminal

Enter global configuration mode.

Step 2 

ip http authentication {enable | local | tacacs}

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

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

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

tacacs—TACACS server is used.

Step 3 

end

Return to privileged EXEC mode.

Step 4 

show running-config

Verify your entries.

If you use Internet Explorer Version 5.5 and select a URL with a nonstandard port at the end of the address (for example, www.cisco.com:84), you must enter http:// as the URL prefix. Otherwise, you cannot launch the device manager.

Open Caveats

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

CSCea80105

When a Cisco IP Phone is connected to the switch, its MAC address is learned on both the port VLAN identification (PVID) and the voice VLAN identification (VVID). However, when the dynamic MAC addresses are either manually or automatically removed due to a topology change or enabling or disabling the port security or IEEE 802.1x feature, the Cisco IP Phone's MAC address will only be re-learned on the VVID. This occurs when the Cisco IP Phone is connected to a Cisco Catalyst 2970, 3560, or 3750 and the Cisco IP Phone is using software without the fix for CSCed84163.

When configured for a Voice VLAN, the phone sends untagged Cisco Discovery Protocol (CDP) packets and tagged voice packets. All frames from any devices connected to the Cisco IP Phone are sent tagged with the access VLAN ID. Catalyst 2970, 3560, and 3750 switches do not populate the secure address-table with the source MAC address from CDP packets.

The workaround is that when using Cisco IP Phones with the fix for CSCed84163 and port-security configured on the switchport, configure switches with one secure address for the phone, plus additional MAC addresses for any devices connected to the Cisco IP Phone.

CSCef84975 (Cisco EtherSwitch service modules)

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.

CSCeg09032

Open Shortest Path First (OSPF) routes might not appear in the routing table after a topology change if Incremental SPF (iSPF) is enabled.

The workaround is to disable iSPF.

CSCeg36369

A Catalyst ME 3750 running Release 12.1(14)AX2 fails to learn the source MAC address of a Cisco Discovery Protocol (CDP) frame when CDP is disabled on the port.

There is no workaround.

CSCeg44446

Policy-based routing (PBR) for IP Version 4 (IPv4) traffic is not available when you run IPv4 and IPv6 traffic on the switch. To run the IPv6 routing protocols on the switch, you need to use a Dual IPv4-IPv6 Switch Database Management (SDM) template. These SDM templates have no resource provisions for PBR.

There is no workaround.

CSCeh01250 (Cisco EtherSwitch service modules)

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.

CSCeh35595 (Cisco EtherSwitch service modules)

A duplex mismatch occurs when two Fast Ethernet interfaces that are directly connected on two EtherSwitch service modules are configured as both 100 Mbps 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.

CSCeh35693 (Cisco EtherSwitch service modules)

If two Cisco EtherSwitch service modules are directly connected through Fast Ethernet interfaces configured as both 100 Mbps and full duplex and as automatic speed and duplex settings, one interface might detect the other as a Cisco-powered device.

There is no workaround.

CSCeh52964 (Cisco EtherSwitch service modules)

When the router is rebooted after it is powered on (approximately once in 10 to 15 reboots), the Router Blade Communication Protocol (RBCP) between the router and the EtherSwitch service module might not be reestablished, and this message appears:

[date]: %Y88E8K-3-ILP_MSG_TIMEOUT_ERROR: GigabitEthernet1/0: EtherSwitch Service 
Module RBCP ILP messages timeout

The workaround is to reload the EtherSwitch service module software without rebooting the router. You can reload the switching software by using the reload user EXEC command at the EtherSwitch service module prompt or by using the service-module g slot_numer /0 reset privileged EXEC command at the router prompt.

CSCeh95744

If two or more switches in a stack of PoE switches restart at the same time and you enter the no switch stack-member-number provision global configuration command, this message appears on the console:

%Command not applied to switch x, remote error 

where x is the stack member number.

There is no workaround. This problem does not affect the switch functionality.

CSCei03743

If you use the no snmp-server enable traps stpx command, BRIDGE-MIB traps are disabled because BRIDGE-MIB traps are enabled when using the stpxNotification Enable object in the CISCO-STP-EXTENSIONS-MIB.

The workaround is to re-enable the BRIDGE-MIB traps by using the snmp-server enable traps stpx command.

CSCei35702

The Cross Stack UplinkFast feature is delayed by 30 seconds when all the interfaces on the root switch are configured with the no shutdown interface configuration command.

There is no workaround; this is the expected behavior.

CSCei63394

When an IEEE 802.1x restricted VLAN is configured on a port and a hub with multiple devices is connected to that port, no syslog messages are generated.

This is not a supported configuration. Only one host should be connected to an IEEE 802.1x restricted VLAN port.

CSCei69329

A switch in a stack of Catalyst 3750 switches might not participate in Master election due to the amount of time required to find a bootable image.

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

CSCei79428 (Catalyst 3750 switches)

When a switch running Cisco IOS image 12.2(25)SEA or later joins a stack running Cisco IOS 12.2(20)SE1 or earlier, the boot auto-copy-sw global configuration command might not work as expected. The new member switch might not be automatically upgraded or downgraded to the Cisco IOS image version that is running on the stack. If that happens, the new member switch is detected in a version mismatch state and is not operational.

The workaround is to follow the procedures displayed when the boot auto-copy-sw global configuration command fails. If another failure occurs, enter the archive download-sw privileged EXEC command on all switches in the stack.

CSCei80087

When configuring a hierarchical policy map, changes to the match criteria of the VLAN level class-map do not take effect until the policy map is detached and reapplied.

The workaround is to detach the policy map from the interface, make the VLAN-level changes, and reapply the policy map.

CSCin33082

If the distance of two or more static IP routes is changed in a particular order, some routes do not appear in the routing table.

The workaround is to use the clear ip route privileged EXEC command.

CSCsb54410

Static IGMP snooping group members are inconsistent across different members in a Catalyst 3750 switch stack after a stack reload or an individual member switch reload.

There is no workaround.

CSCsb56438

There is an extra index in the port table of the ciscoStpExtensions MIB that does not exist in the portCrossIndex MIB. For example, extra indexes like 1000-16/40 are seen in stpxRootGuardConfigEnabled displays that do not exist in portCrossIndex, and they appear during an SNMP walk operation.

There is no workaround.

CSCsb58462

When a stack of Catalyst 3750 switches running Release 12.2(25)SED are configured with a Layer 3 LACP EtherChannel, tracebacks are generated when a master switchover occurs.

The workaround is to enable the persistent stack-mac feature on the switch by entering the stack-mac persistent timer switch configuration command.

CSCsb59125 (Catalyst 3750 and 3560)

An IPv6 packet with options, that arrives on an interface with a destination MAC address assigned to another Layer 3 interface on the router is forwarded by the switch software. An IPv6 packet without options is forwarded in hardware only when the packet destination MAC address matches the MAC address assigned to an ingress Layer 3 interface.

There is no workaround.

CSCsb60164

When a Catalyst 3750 stack master fails or leaves the stack, a cross-stack EtherChannel in trunk mode running Link Aggregation Control Protocol (LACP) protocol might stop forwarding traffic on some VLANs.

The workaround is to enable the stack-mac persistent feature by using the stack-mac persistent timer global configuration command. You can also use the shutdown interface configuration command and then the no shutdown command on the EtherChannel interface.

CSCsb62432

If two VLANs are configured on the same switch (for example, VLAN 1 and VLAN 2) with an SVI configured in VLAN 1 and an external bridging device connected to the switch, traffic sent from VLAN 2 to the SVI in VLAN 1 is dropped.

The workaround is to configure a static MAC address for the SVI in the MAC address table of VLAN 2.

CSCsb72783 (Catalyst 2970 switches)

The output of the show controller utilization user EXEC command might incorrectly show a Gigabit interface at 100 percent utilization.

There is no workaround.

CSCsb74648

When a Cisco device configured for Network Admission Control and the EAP over UDP port number is changed from its default value and then changed back with the eou default switch configuration command, the port change does not take effect, and EAP over UDP sessions can remain in a hold state.

The workaround is to reset the EAP over UDP port number to its default value (0x5566) by using the eou port 21862 switch configuration command.

CSCsb75245

When you configure a Cisco IP Phone to use Network Admission Control, the CDP packet is delayed, and the phone is identified as an agentless host without an identity profile.

The workaround is to enter the eou initialize ip address switch configuration command to revalidate the host that CDP has learned.

CSCsb79198

During IEEE 802.1x authentication, a RADIUS server might download a per-user IP address access control list (ACL) or a MAC address ACL that is applied to the interface as part of the Access-Accept message. If the ACL is too large, the switch might not be able to apply it, and authentication fails and starts over.

The workaround is to reduce the size of the per-user ACL access control entries (ACEs) to less than 20 if ACLs are downloaded as part of IEEE 802.1x authorization.

CSCsb79318

if the re-authentication timer and re-authentication action is downloaded from the RADIUS server using the Session-Timeout and Termination-Action RADIUS attributes, the switch performs the termination action even when the port is not configured with the dot1x timeout reauth server global configuration command and uses the Termination-Action downloaded from a RADIUS server as part of IEEE 802.1x authorization.

The workaround is to remove the Termination-Action attribute from the IEEE 802.1x policy on the RADIUS server if dot1x timeout reauth server is not configured on the port.

CSCsb81023 (Catalyst 3750 switches)

A nonstackable EtherSwitch Service Module boots with this provisioned switch error message:

switch 1 provision NME-X-23ES-1G-P 
                ^ 
% Invalid input detected at '^' marker. 
Failed to generate persistent self-signed certificate. 
Secure server will use temporary self-signed certificate. 

This message is only informational.

CSCsb81283

MAC address notification traps do not work when port security is enabled on the interface.

The workaround is to disable port security on the interface.

CSCsb82422

The switch does not forward an IEEE802.1x request that has null credentials.

There is no workaround.

CSCsb86873

When the master switch in a stack of Catalyst 3750 switches is reloaded, all remarks that were part of individual access control entries (ACEs) appear as a list at the end of the ACL instead of appearing with their associated ACE entries.

There is no workaround.

CSCsb87895

Hierarchical per-VLAN policy-map police action does not work if there is no configured child policy-map in the first class-map.

The workaround is to add any child policy-map to the first class-map or to move the class-map so that it is not the first class-map in the policy-map.

CSCsb97234 (Catalyst 3750 switches)

When both IEEE 802.1x and standard per-user ACL are configured on a member switch in a switch stack, the switch fails when a supplicant tries to authenticate.

The workaround is to configure the standard ACL as an extended ACL.

CSCsb97454

When the cable connected to a Gigabit Ethernet port on a Catalyst 2970 switch is unplugged, under these conditions, the switch recalculates its port state and role on other ports:

The port is in the alternate state before the cable is unplugged.

The configured port speed is 100 Mbps.

The port is configured for full-duplex operation.

This port would have been chosen the root port if a speed of 100 Mbps had not been configured on the port.

Use one of these workarounds:

Configure the alternate (Gigabit Ethernet) port to autonegotiate speed.

Configure a specific path cost on the alternate port.

CSCsb97854

When a source port for a SPAN session has IEEE 802.1x enabled, Extensible Authentication Protocol over LAN (EAPOL) packets are not visible to the packet sniffing tool.

The workaround is to enable a voice VLAN on the SPAN source port.

CSCsc03400 (Catalyst 3750 switches)

When the master switch reloads one of the member switches, the interface of the member switch remains up, but the line protocol goes down. The MIB object returns this message: incorrect status.

There is no workaround.

CSCsc09411 (Catalyst 3750 switches)

When a member switch is reset and then reset again in less than 10 seconds, multicast users connected to the switch do not receive any multicast traffic from other VLANs or interfaces in the switch stack. Multicast users connected to other member switches in the same switch stack correctly receive multicast traffic. Reloading the member switch does not fix the problem.

The workaround is to use the clear ip mds linecard memberswitch privileged EXEC command on the member switch. You can also reload the master switch by using the reload slot masterswitch privileged EXEC command. When you use the show ip mds stats linecard privileged EXEC command, and the display shows the status of the member switch as reloading, this means that the problem has not been fixed.

Resolved Caveats

This section describes the caveats have been resolved in this release. Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules:

"Resolved Caveats in Cisco IOS Release 12.2(25)SED1" section

"Resolved Caveats in Cisco IOS Release 12.2(25)SED" section

Resolved Caveats in Cisco IOS Release 12.2(25)SED1

These caveats were resolved:

CSCeh43851 (Catalyst 3750, 3560, 2970 switches and Cisco EtherSwitch service modules)

The switch no longer drops IP packets with an encrypted TCP header or with a TCP header that is fragmented into two different Ethernet frames.

CSCsc41813 (Catalyst 3750, 3560, 2970 switches and Cisco EtherSwitch service modules)

A switch running Cisco IOS Release 12.2(25)SED might reload or display error messages when the user attempts to access the flash filesystem. This might occur when renumbering a switch in a stack, using the dir or copy commands on the flash filesystem, or changing boot configurations, such as boot system filename.

To avoid this problem, you can upgrade the switch software to Cisco IOS Release 12.2(25)SED1.

CSCsc43656 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

The MAC address tables in a switch stack are now synchronized correctly when member ports are configured with sticky secure MAC addresses.

Resolved Caveats in Cisco IOS Release 12.2(25)SED

These caveats were resolved:

CSCef37624 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

You can now ping a Layer 3 interface when switch clustering is enabled.

CSCef94884 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

Disabling OSPFv3 no longer causes a memory leak.

CSCeg09013 (Catalyst 3750-12S switches)

When the switch boots up, ports 1, 2, 5, 6, 9, and 10 can become active before the Cisco IOS software loading process is complete. Packets arriving at these ports before the switch software is completely loaded are no longer lost.

CSCeg60445 (Catalyst 3750 switches and EtherSwitch service modules)

SNMP polling for CiscoEnvMonSupplyStatusDescr, which gives power supply status, now supplies accurate information.

CSCeh08767 (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules)

If the bgp suppress-inactive command was toggled, the Border Gateway Protocol (BGP) table showing version numbers for prefixes that BGP could not install in the RIB would increase constantly. This no longer occurs.

CSCeh15112 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

The show dot1x all privileged EXEC command now displays IEEE 802.1x information about the ports on all switches in a stack.

CSCeh32563 (Cisco EtherSwitch service modules)

When using the VLAN Query Protocol (VQP), the switch now continues to send queries to the primary VMPS server after receiving an unsolicited response from a backup VMPS server.

CSCeh37831 (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules)

The storm-control feature now works properly, even when the multicast MAC destination address and the multicast IP destination address are not mapped correctly.

CSCeh50492 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

When an existing root port fails, and the new root port is located on a different member of the switch stack, traffic to the old root port is no longer lost during the cross-stack UplinkFast change between root ports.

CSCeh80716

The switch can now access the SNMP MIBs with double indexing, regardless of special characters used in the community string.

CSCeh83713

Interfaces that have port security and violation mode protect enabled no longer stop forwarding packets when their secure address maximum has been reached.

CSCeh89700

Error messages are no longer generated when writing the extended crash information file.

CSCeh93103

You can no longer configure ports with different settings for speed, duplex, and trunking mode in the same EtherChannel.

CSCeh96039 (Catalyst 3750 and 3560 switches and Cisco EtherSwitch service modules)

When a switch is configured with both IEEE 802.1Q and Layer 2 Protocol tunneling, it no longer receives traffic from unauthorized VLANs through the Layer 2 Protocol tunnel.

CSCei06960

You can now use the no snmp-server host [ip] [ver] [2c] [word] udp-port port number global configuration command to delete the snmp-server host [ip] [ver] [2c] [word] udp-port port number configuration.

CSCei61732

Cisco IOS may permit arbitrary code execution after exploitation of a heap-based buffer overflow vulnerability. Cisco has included additional integrity checks in its software, as further described below, that are intended to reduce the likelihood of arbitrary code execution.

Cisco has made free software available that includes the additional integrity checks for affected customers.

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

CSCsb60087 (Catalyst 3750 switches and Cisco EtherSwitch service modules)

Whe two or more stacks of Catalyst 3750 switches are connected through an EtherChannel port and the port gets an IGMP leave messages for a nonexisting group, a storm of IGMP leave messages is no longer sent between Catalyst 3750 switch stacks.

CSCsb75533

A Catalyst 2970 switch running Release 12.2(25)SEB1 and a vendor type of cevPortGigBaseLX does not display the SNMP table entAliasMappingTable.

Documentation Updates

These sections has this information:

"Updates to the Software Configuration Guides" section

"Updates to the Regulatory Compliance and Safety Information" section

Updates to the Software Configuration Guides

This information is incorrect in the "Configuring IPv6 MLD Snooping" chapter of the software configuration guides for the Catalyst 3750 and 3560 switches:

When the advanced IP services image is installed on the Catalyst 3750 or 3560 switch, you can use Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP version 6 (IPv6) multicast data to clients and routers in a switched network. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.


Note To use IPv6, the switch or stack master must be running the advanced IP services image and you must configure the dual IPv4 and IPv6 Switch Database Management (SDM) template on the switch. You select the template by entering the sdm prefer dual-ipv4-and-ipv6 {default | vlan} [desktop] global configuration command.


This is the correct information:

You can use Multicast Listener Discovery (MLD) snooping to enable efficient distribution of IP version 6 (IPv6) multicast data to clients and routers in a switched network on the Catalyst 3750 or 3560 switch. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.


Note To use IPv6, you must configure the dual IPv4 and IPv6 Switch Database Management (SDM) template on the switch. You select the template by entering the sdm prefer dual-ipv4-and-ipv6 {default | vlan} [desktop] global configuration command.


Updates to the Regulatory Compliance and Safety Information

This information was added to the Regulatory Compliance and Safety Information for the Catalyst 3750, 3560, 2970, and 2960 switches:

Statement 361—VoIP and Emergency Calling Services do not Function if Power Fails

Warning


Voice over IP (VoIP) service and the emergency calling service do not function if power fails or is disrupted. After power is restored, you might have to reset or reconfigure equipment to regain access to VoIP and the emergency calling service. In the USA, this emergency number is 911. You need to be aware of the emergency number in your country. Statement 361

Waarschuwing

Voice over IP (VoIP)-service en de service voor noodoproepen werken niet indien er een stroomstoring is. Nadat de stroomtoevoer is hersteld, dient u wellicht de configuratie van uw apparatuur opnieuw in te stellen om opnieuw toegang te krijgen tot VoIP en de noodoproepen. In de VS is het nummer voor noodoproepen 911. U dient u zelf op de hoogte te stellen van het nummer voor noodoproepen in uw land.

Varoitus

Voice over IP (VoIP) -palvelu ja hätäpuhelupalvelu eivät toimi, jos virta katkeaa tai sen syötössä esiintyy häiriöitä. Kun virransyöttö on taas normaali, sinun täytyy mahdollisesti asettaa tai määrittää laitteisto uudelleen, jotta voisit jälleen käyttää VoIP-palvelua ja hätäpuhelupalvelua. Yhdysvalloissa hätänumero on 911. Selvitä, mikä on omassa kotimaassasi käytössä oleva hätänumero.

Attention

Le service Voice over IP (VoIP) et le service d'appels d'urgence ne fonctionnent pas en cas de panne de courant. Une fois que le courant est rétabli, vous devrez peut-être réinitialiser ou reconfigurer le système pour accéder de nouveau au service VoIP et à celui des appels d'urgence. Aux États-Unis, le numéro des services d'urgence est le 911. Vous devez connaître le numéro d'appel d'urgence en vigueur dans votre pays.

Warnung

Bei einem Stromausfall oder eingeschränkter Stromversorgung funktionieren VoIP-Dienst und Notruf nicht. Sobald die Stromversorgung wieder hergestellt ist, müssen Sie möglicherweise die Geräte zurücksetzen oder neu konfigurieren, um den Zugang zu VoIP und Notruf wieder herzustellen. Die Notrufnummer in den USA lautet 911. Wählen Sie im Notfall die für Ihr Land vorgesehene Notrufnummer.

Avvertenza

Il servizio Voice over IP (VoIP) e il servizio per le chiamate di emergenza non funzionano in caso di interruzione dell'alimentazione. Ristabilita l'alimentazione, potrebbe essere necessario reimpostare o riconfigurare l'attrezzatura per ottenere nuovamente l'accesso al servizio VoIP e al servizio per le chiamate di emergenza. Negli Stati Uniti, il numero di emergenza è 911. Si consiglia di individuare il numero di emergenza del proprio Paese.

Advarsel

Tjenesten Voice over IP (VoIP) og nødanropstjenesten fungerer ikke ved strømbrudd. Etter at strømmen har kommet tilbake, må du kanskje nullstille eller konfigurere utstyret på nytt for å få tilgang til VoIP og nødanropstjenesten. I USA er dette nødnummeret 911. Du må vite hva nødnummeret er i ditt land.

Aviso

O serviço Voice over IP (VoIP) e o serviço de chamadas de emergência não funcionam se houver um corte de energia. Depois do fornecimento de energia ser restabelecido, poderá ser necessário reiniciar ou reconfigurar o equipamento para voltar a utilizar os serviços VoIP ou chamadas de emergência. Nos EUA, o número de emergência é o 911. É importante que saiba qual o número de emergência no seu país.

¡Advertencia!

El servicio de voz sobre IP (VoIP) y el de llamadas de emergencia no funcionan si se interrumpe el suministro de energía. Tras recuperar el suministro es posible que deba que restablecer o volver a configurar el equipo para tener acceso a los servicios de VoIP y de llamadas de emergencia. En Estados Unidos el número de emergencia es el 911. Asegúrese de obtener el número de emergencia en su país.

Varning!

Tjänsten Voice over IP (VoIP) och larmnummertjänsten fungerar inte vid strömavbrott. Efter att strömmen kommit tillbaka måste du kanske återställa eller konfigurera om utrustningen för att få tillgång till VoIP och larmnummertjänsten. I USA är det här larmnumret 911. Du bör ta reda på det larmnummer som gäller i ditt land.

 


Related Documentation

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

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

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

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

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

http://www.cisco.com/en/US/products/hw/modules/ps2797/
products_feature_guide09186a0080415bae.html

You can order printed copies of documents with a DOC-xxxxxx= number from the Cisco.com sites and from the telephone numbers listed in the "Obtaining Documentation" section.

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

Catalyst 3750 Switch Software Configuration Guide (order number DOC-7816180=)

Catalyst 3750 Switch Command Reference (order number DOC-7816181=)

Catalyst 3750 Switch System Message Guide (order number DOC-7816184=)

Catalyst 3750 Switch System Message Guide (order number DOC-7816184=)

Device manager online help (available on the switch)

Catalyst 3750 Switch Hardware Installation Guide (not orderable but available on Cisco.com)

Catalyst 3750 Switch Getting Started Guide (order number DOC-7816663=)

Regulatory Compliance and Safety Information for the Catalyst 3750 Switch (order number DOC-7816664)

These documents provide complete information about the Catalyst 3560 switches:

Catalyst 3560 Switch Software Configuration Guide (order number DOC-7816404=)

Catalyst 3560 Switch Command Reference (order number DOC-7816405=)

Catalyst 3560 Switch System Message Guide (order number DOC-7816406=)

Device manager online help (available on the switch)

Catalyst 3560 Switch Hardware Installation Guide (not orderable but available on Cisco.com)

Catalyst 3560 Switch Getting Started Guide (order number DOC-7816660=)

Regulatory Compliance and Safety Information for the Catalyst 3560 Switch (order number DOC-7816665)

These documents provide complete information about the Catalyst 2970 switches:

Catalyst 2970 Switch Software Configuration Guide (order number DOC-7816182=)

Catalyst 2970 Switch Command Reference (order number DOC-7816183=)

Catalyst 2970 Switch System Message Guide (order number DOC-7816185=)

Device manager online help (available on the switch)

Catalyst 2970 Switch Hardware Installation Guide (not orderable but available on Cisco.com)

Catalyst 2970 Switch Getting Started Guide (order number DOC-7816685=)

Regulatory Compliance and Safety Information for the Catalyst 2970 Switch (order number DOC-7816686=)

These documents provide complete information about the Catalyst 2960 switches:

Catalyst 2960 Switch Software Configuration Guide (order number DOC-7816881=)

Catalyst 2960 Switch Command Reference (order number DOC-7816882=)

Catalyst 2960 Switch System Message Guide (order number DOC-7816883=)

Device manager online help (available on the switch)

Catalyst 2960 Switch Hardware Installation Guide (not orderable but available on Cisco.com)

Catalyst 2960 Switch Getting Started Guide (order number DOC-7816879=)

Regulatory Compliance and Safety Information for the Catalyst 2970 Switch (order number DOC-7816880=)

For other information about related products, see these documents:

Getting Started with Cisco Network Assistant (not orderable but available on Cisco.com)

Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com)

Cisco Small Form-Factor Pluggable Modules Installation Notes (order number DOC-7815160=)

Cisco CWDM GBIC and CWDM SFP Installation Note (not orderable but available on Cisco.com)

Cisco RPS 300 Redundant Power System Hardware Installation Guide (order number DOC-7810372=)

Cisco RPS 675 Redundant Power System Hardware Installation Guide (order number DOC-7815201=)

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Product Documentation DVD

Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.

The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:

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

Ordering Documentation

Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

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

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can send comments about Cisco documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

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

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

Emergencies — security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

Nonemergencies — psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

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

http://www.cisco.com/techsupport

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

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


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

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

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

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

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

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

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

Definitions of Service Request Severity

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

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

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

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

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

http://www.ciscopress.com

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

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

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

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

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

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

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

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