 Feedback
|
Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Catalyst 3750G Integrated Wireless LAN Controller Switch Software Compatibility
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Catalyst 3750, 3560, 2970, and 2960 switches
Catalyst 3750, 3560, and 2960 switches
Catalyst 3750 and 3560 Switches
Minimum Cisco IOS Release for Major Features
Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750 Switches Only)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
Updates to the Catalyst 3750, 3560, and 2960 Switch Software Configuration Guides
Updates to Only the Catalyst 3750 and 3560 Switch Software Configuration Guides
Understanding Embedded Event Manager
Embedded Event Manager Actions
Embedded Event Manager Policies
Embedded Event Manager Environment Variables
Configuring Embedded Event Manager
Registering and Defining an Embedded Event Manager Applet
Registering and Defining an Embedded Event Manager TCL Script
Displaying Embedded Event Manager Information
Applet Configuration (config-applet)
Trigger Applet Configuration (config-applet-trigger)
Event Trigger Configuration (config-event-trigger)
Correction to the Catalyst 2960 Software Configuration Guide
Update to the Catalyst 3750, 3560, and 2960 Command References
Updates to the System Message Guides
Updates to the Catalyst 3750, 3560, 2970, and 2960 Hardware Installation Guide
Update to the Regulatory Compliance and Safety Information for the Catalyst 2960 Switch
Statement 266—Switch Installation Warning
Updates to the Catalyst 3750 Getting Started Guide
Update to the Catalyst 3750 Switch Regulatory Compliance and Safety Information
Statement 377—Temperature of the Removed SFP Module Might be Hot
Statement 370—Attaching the Cisco RPS to the RPS Receptacle
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for the Catalyst 3750, 3560, 2970, and 2960 Switches, Cisco IOS Release 12.2(44)SE and Later
Revised September 9, 2009
Cisco IOS Release 12.2(44)SE and later runs on all Catalyst 3750, 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(44)SE and later and any limitations, restrictions, and caveats that apply to the releases. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
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/public/sw-center/sw-lan.shtml
This software release is part of a special release of Cisco IOS software that is not released on the same 8-week maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
Contents
This information is in the release notes:
•
•
•
System Requirements
The system requirements are described in these sections:
•
Hardware Supported
Table 1 lists the hardware supported on this release.
Table 1 Catalyst 3750, 3560, 2970, and 2960 Switches and Cisco EtherSwitch Service Modules Supported Hardware
Catalyst 3750G-24WS-S25
24 10/100/1000 PoE1 ports, 2 SFP2 module slots, and an integrated wireless LAN controller supporting up to 25 access points.
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE
Catalyst 3750G-24WS-S50
24 10/100/1000 PoE ports, 2 SFP module slots, and an integrated wireless LAN controller supporting up to 50 access points
Cisco IOS Release 12.2(25)FZ or Cisco IOS Release 12.2(35)SE
Catalyst 3750-24FS
24 100BASE-FX ports and 2 SFP module slots
Cisco IOS Release 12.2(25)SEB
Catalyst 3750-24PS
24 10/100 PoE 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-8PC
8 10/100 PoE ports and 1 dual-purpose port3 (one 10/100/1000BASE-T copper port and one SFP module slot)
Cisco IOS Release 12.2(35)SE
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-24-S
24 10/100 BASE-TX Ethernet ports
Cisco IOS Release 12.2(37)EY
Catalyst 2960-24TC-S
24 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots)
Cisco IOS Release 12.2(37)EY
Catalyst 2960-48TC-S
48 10/100BASE-T Ethernet ports and 2 dual-purpose ports (two 10/100/1000BASE-T copper ports and two SFP module slots)
Cisco IOS Release 12.2(37)EY
Catalyst 2960PD-8TT-L
8 10/100 ports and 1 10/100/1000 port that receives power
Cisco IOS Release 12.2(44)SE
Catalyst 2960-8TC-L
8 10/100 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)
Cisco IOS Release 12.2(35)SE
Catalyst 2960G-8TC-L
7 10/100/1000 Ethernet ports and 1 dual-purpose port (one 10/100/1000BASE-T copper port and one SFP module slot)
Cisco IOS Release 12.2(35)SE
Catalyst 2960-24LT-L
24 10/100 ports, 8 of which are PoE, and 2 10/100/1000 ports
Cisco IOS Release 12.2(44)SE
Catalyst 2960-48TC-L
48 10/100BASE-TX Ethernet ports and 2 dual-purpose ports
Cisco IOS Release 12.2(25)FX
Catalyst 2960-24TC-L
24 10/100BASE-TX Ethernet ports and 2 dual-purpose ports
Cisco IOS Release 12.2(25)FX
Catalyst 2960-24PC-L
24 10/100 Power over Ethernet (PoE) ports and 2 dual-purpose ports (2 10/100/1000BASE-T copper ports and 2 small form-factor pluggable [SFP] module slots)
Cisco IOS Release 12.2(44)SE
Catalyst 2960-24TT-L
24 10/100BASE-T Ethernet ports and 2 10/100/1000BASE-T Ethernet ports
Cisco IOS Release 12.2(25)FX
Catalyst 2960-48TT-L
48 10/100BASE-T Ethernet ports 2 10/100/1000BASE-T Ethernet ports
Cisco IOS Release 12.2(25)FX
Catalyst 2960G-24TC-L
24 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots)
Cisco IOS Release 12.2(25)FX
Catalyst 2960G-48TC-L
48 10/100/1000BASE-T Ethernet ports, including 4 dual-purpose ports (four 10/100/1000BASE-T copper ports and four SFP module slots)
Cisco IOS Release 12.2(25)SEE
NME-16ES-1G4
16 10/100 ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide
Cisco IOS Release 12.2(25)SEC
NME-16ES-1G-P4
16 10/100 PoE ports, 1 10/100/1000 Ethernet port, no StackWise connector ports, single-wide
Cisco IOS Release 12.2(25)EZ
NME-X-23ES-1G4
23 10/100 ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide
Cisco IOS Release 12.2(25)SEC
NME-X-23ES-1G-P4
23 10/100 PoE ports, 1 10/100/1000 PoE port, no StackWise connector ports, extended single-wide
Cisco IOS Release 12.2(25)EZ
NME-XD-24ES-1S-P4
24 10/100 PoE ports, 1 SFP module port, 2 StackWise connector ports, extended double-wide
Cisco IOS Release 12.2(25)EZ
NME-XD-48ES-2S-P4
48 10/100 PoE ports, 2 SFP module ports, no StackWise connector ports, extended double-wide
Cisco IOS Release 12.2(25)EZ
SFP modules (Catalyst 3750, 3560, and 2970)
1000BASE-CWDM5 , -LX, SX, -T, -ZX
100BASE-FX MMF6
Cisco IOS Release 12.2(18)SE
Cisco IOS Release 12.2(20)SE
SFP modules (Catalyst 2960)
1000BASE-BX, -CWDM, -LX/LH, -SX, -ZX
100BASE-BX, FX, -LX
Cisco IOS Release 12.2(25)FX
XENPAK modules7
XENPAK-10-GB-ER, XENPAK-10-GB-LR, and XENPAK-10-GB-SR
Cisco IOS Release 12.2(18)SE
Redundant power systems
Cisco RPS 675 Redundant Power System
Cisco RPS 300 Redundant Power System (supported only on the Catalyst 2960 switch)
Cisco Redundant Power System 2300
Supported on all software releases
Supported on all software releases
Cisco IOS Release 12.2(35)SE and later (not supported on Catalyst 2970 switches)
1 PoE = Power over Ethernet
2 SFP = small form-factor pluggable
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 Cisco EtherSwitch service module
5 CWDM = coarse wavelength-division multiplexer
6 MMF = multimode fiber
7 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
Table 2 lists the minimum hardware requirements for running the device manager.
Table 2 Minimum Hardware Requirements
233 MHz minimum1
512 MB2
256
1024 x 768
Small
1 We recommend 1 GHz.
2 We recommend 1 GB DRAM.
Software Requirements
Table 3 lists the supported operating systems and browsers for using the device manager. The device manager verifies the browser version when starting a session to ensure that the browser is supported.
Note
Table 3 Supported Operating Systems and Browsers
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:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, the command reference, and the Cisco EtherSwitch service module feature guide.
CNA Compatibility
Cisco IOS 12.2(44)SE is only compatible with Cisco Network Assistant (CNA) 5.0 and later. You can download Cisco Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
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
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
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
Table 5 Cisco IOS Software Image Files
Filename
c3750-ipbase-tar.122-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.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-44.SE6.tar
Catalyst 2970 image file and device manager files.
This image has Layer 2+ features.c2970-lanbasek9-tar.122-44.SE6.tar
Catalyst 2970 cryptographic image file and device manager files.
This image has the Kerberos and SSH features.c2960-lanbase-tar.122-44.SE6.tar
Catalyst 2960 image file and device manager files.
This image has Layer 2+ features.c2960-lanbasek9-tar.122-44.SE6.tar
Catalyst 2960 cryptographic image file and device manager files. This image has the Kerberos and SSH features.
c2960-lanlitek9-tar.122-44.SE6.tar
Catalyst 2960 LAN lite cryptographic image file and device manager files.
c2960-lanlite-tar.122-44.SE6.tar
Catalyst 2960 LAN lite image file and device manager files.
1 SSH = Secure Shell
Catalyst 3750G Integrated Wireless LAN Controller Switch Software Compatibility
The Catalyst 3750 Integrated Wireless LAN Controller Switch is an integrated Catalyst 3750 switch and Cisco 4400 series wireless LAN controller that supports up to 25 or 50 lightweight access points. The switch and the internal controller run separate software versions, which must be upgraded separately. If the image versions are not compatible, the wireless LAN controller switch could stop functioning. Table 6 is the compatibility matrix for Catalyst 3750 and wireless controller.
For information about this controller software release, see the Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Point, Release 4.0.x.0. For controller software upgrade procedure, see the Cisco Wireless LAN Controller Configuration Guide Release 4.0.
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
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:
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
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
Step 2
http://www.cisco.com/public/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
Step 3
For more information, see Appendix B in the software configuration guide for this release.
Step 4
Step 5
Switch# ping tftp-server-addressFor more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6
Switch# archive download-sw /overwrite /reload tftp:[[//location]/directory]/image-name.tarThe /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-44.SE.tarYou 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:
•
•
•
•
Note
Note
New Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
New Hardware Features
This release supports these new Catalyst 2960 switches:
•
•
•
For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
These sections describe the new software features for this release:
•
•
•
Catalyst 3750, 3560, 2970, and 2960 switches
This is the new feature for the Catalyst 3750, 3560, 2970, and 2960 switches:
IEEE 802.1x readiness check to determine the readiness of connected end hosts before configuring IEEE 802.1x on the switch
Catalyst 3750, 3560, and 2960 switches
These are the new features for the Catalyst 3750, 3560, 2970, and 2960 switches:
•
•
•
•
•
•
•
Catalyst 3750 and 3560 Switches
These are the new features for the Catalyst 3750 and 3560 switches:
•
•
•
Catalyst 2960 switch
These features were added to the Catalyst 2960 switch LAN Lite image:
•
•
Minimum Cisco IOS Release for Major Features
Table 7 lists the minimum software release required to support the major features of the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules.
Table 7 Catalyst 3750, 3560, 2970, and 2960 Switches and Cisco EtherSwitch Service Module Features and the Minimum Cisco IOS Release Required
IEEE 802.1x readiness check
12.2(44)SE
3750, 3560, 2970, 2960
DHCP-based autoconfiguration and image update
12.2(44)SE
3750, 3560, 2960
Embedded event manager (EEM) for device and system management
(IP services image only)12.2(40)SE
3750, 3560
Configurable small-frame arrival threshold
12.2(44)SE
3750, 3560, 2960
HTTP and HTTP(s) support over IPV6
12.2(44)SE
3750, 3560, 2960
Simple Network and Management Protocol (SNMP) configuration over IPv6 transport
12.2(44)SE
3750, 3560, 2960
IPv6 stateless autoconfiguration
12.2(44)SE
3750, 3560, 2960
Flex Link Multicast Fast Convergence
12.2(44)SE
3750, 3560, 2960
Digital optical monitoring (DOM)
12.2(44)SE
3750, 3560
Source Specific Multicast (SSM) mapping
12.2(44)SE
3750, 3560
/31 bit mask support for multicast traffic
12.2(44)SE
3750, 3560
Configuration replacement and rollback
12.2(40)SE
3750, 3560, 2960
Link Layer Discovery Protocol Media Extensions (LLDP-MED)
12.2(40)SE
3750, 3560, 2960
Support for Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6
12.2(40)SE
3750, 3560
Automatic quality of service (QoS) Voice over IP (VoIP)
12.2(40)SE
3750, 3560, 2960
Dynamic voice virtual LAN (VLAN) for multidomain authentication (MDA)-enabled ports
12.2(40)SE
3750, 3560
Internet Group Management Protocol (IGMP) helper
12.2(40)SE
3750, 3560
IP Service Level Agreements (IP SLAs)
12.2(40)SE
3750, 3560
IP SLAs EOT
12.2(40)SE
3750, 3560
Multicast virtual routing and forwarding (VRF) lite
12.2(40)SE
3750, 3560
SSM PIM protocol
12.2(40)SE
3750, 3560
VRF-aware support for these IP services: HSRP, uRPF, ARP, SNMP, IP SLA, TFTP, FTP, syslog, traceroute, and ping
12.2(40)SE
3750, 3560
MLD snooping
12.2(40)SE
2960
IPv6 host
12.2(40)SE
2960
IP phone detection enhancement
12.2(37)SE
3750, 3560, 2970, 2960
Link Layer Discovery Protocol (LLDP) and LLDP Media Endpoint Discovery (LLDP-MED)
12.2(37)SE
3750, 3560, 2970, 2960
PIM stub routing
12.2(37)SE
3750, 3560
Port security on a PVLAN host
12.2(37)SE
3750, 3560
VLAN aware port security option
12.2(37)SE
3750, 3560, 2970, 2960
Support for auto rendezvous point (auto-RP) for multicast
12.2(37)SE
3750. 3560
VLAN Flex Links load balancing
12.2(37)SE
3750, 3560, 2960
Web Cache Communication Protocol (WCCP)
12.2(37)SE
3750. 3560
Multidomain authentication (MDA)
12.2(35)SE
3750, 3560
Web authentication
12.2(35)SE
3750, 3560, 2960
MAC inactivity aging
12.2(35)SE
3750, 3560, 2960
Support for IPv6 with Express Setup
12.2(35)SE
3750, 3560
Generic online diagnostics to test the hardware functionality of the supervisor engine
12.2(35)SE
3560
Stack MAC persistent timer and archive download enhancements
12.2(35)SE
3750
HSRP enhanced object tracking
12.2(35)SE
3750, 3560
OSPF and EIGRP Nonstop forwarding capability (IP services image only)
12.2(35)SE
3750
IPv6 router ACLs for inbound Layer 3 management traffic in the IP base and IP services image
12.2(35)SE
3750, 3560
Generic online diagnostics to test the hardware functionality of the supervisor engine
12.2(25)SEE
3750
DHCP Option 82 configurable remote ID and circuit ID
12.2(25)SEE
3750, 3560, 2970, 2960
EIGRP stub routing in the IP base image
12.2(25)SEE
3750, 3560
/31 bit mask support for unicast traffic
12.2(25)SEE
3750, 3560
Access SDM templates
12.2(25)SED
3750, 3560
Cisco EtherSwitch service modules
IPv6 ACLs
12.2(25)SED
3750, 3560
Cisco EtherSwitch service modules
IPv6 Multicast Listener Discovery (MLD) snooping
12.2(25)SED
3750, 3560
Cisco EtherSwitch service modules
QoS hierarchical policy maps on a port
12.2(25)SED
3750, 3560, and 2970
Cisco EtherSwitch service modules
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
IEEE 802.1x inaccessible authentication bypass.
12.2(25)SED
12.2(25)SEE
3750, 3560
Cisco EtherSwitch service module
2960 and 2970
IEEE 802.1x with restricted VLAN
12.2(25)SED
3750, 3560, 2970, and 2960
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
12.2(25)SED
3750, 3560, and 2970
Cisco EtherSwitch service modules2960
Unique device identifier (UDI)
12.2(25)SEC
12.2(25)SED
3750, 3560, and 2970
Cisco EtherSwitch service modules
2960
VRF Lite
12.2(25)SEC
3750, 3560
Cisco EtherSwitch service modules
IEEE 802.1x with wake-on-LAN
12.2(25)SEC
12.2(25)SED
3750, 3560, 2970
2960, Cisco EtherSwitch service modules
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
2960, Cisco EtherSwitch service modules
Secure Copy Protocol
12.2(25)SEC
12.2(25)SED
3750, 3560, 2970
2960, Cisco EtherSwitch service modules
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, and 2960
IGMP leave timer
12.2(25)SEB
12.2(25)SED
3750, 3560, and 2970
2960
IGMP snooping querier
12.2(25)SEA
12.2(25)FX
3750, 3560, 2970, and 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, and 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, and 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, and 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, and 2960
Dynamic ARP inspection
12.2(20)SE
3750 and 3560
Flex Links
12.2(20)SE
12.2(25)FX
3750, 3560, 2970, and 2960
Software upgrade (device manager or Network Assistant only)
12.2(20)SE
12.2(25)FX
3750, 3560, 2970, and 2960
IP source guard
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, and 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, and 2960
Generic online diagnostics (GOLD)
12.2(25)SEE
3750
Flex Links Preemptive Switchover
12.2(25)SEE
3750, 3560, 2970, and 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
Unless otherwise noted, these limitations apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules:
•
•
•
•
•
Configuration
These are the configuration limitations:
•
This problem occurs under these conditions:
–
–
–
The workaround is to reconfigure the static IP address. (CSCea71176 and CSCdz11708)
•
•
1.
2.
3.
•
–
–
–
No workaround is necessary; these are the designed behaviors. (CSCed50819)
•
However, when dynamic ARP inspection is not enabled and a jumbo MTU is configured, ARP and RARP packets are correctly bridged in hardware. (CSCed79734)
•
The workaround is to configure the port for 10 Mb/s and half duplex or to connect a hub or a nonaffected device to the switch. (CSCed39091)
•
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)
•
The workaround is to enter the no switchport block unicast interface configuration command on that specific interface. (CSCee93822)
•
There is no workaround. This is a cosmetic error and does not affect the functionality of the switch. (CSCef59331)
•
To change the baud rate, reload the Cisco EtherSwitch service module with the bootloader prompt. You can then change the baud rate and change the speed on the TTY line of the router connected to the Cisco EtherSwitch Service module console.
There is no workaround. (CSCeh50152)
•
The workaround is to use switch ports other than those specified for redundancy and for applications that immediately detect active links. (CSCeh70503)
•
High CPU utilization can also occur with other conditions, such as when debug messages are logged at a high rate to the console.
Use one of these workarounds:
–
–
–
•
15:50:11: %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Port-channel1 (ifindex 1632) -Traceback= A585C B881B8 B891CC 2F4F70 5550E8 564EAC 851338 84AF0C 4CEB50 859DF4 A7BF28 A98260 882658 879A58
(CSCsh12472 [Catalyst 3750 and 3560 switches])
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
•
Ethernet
These are the Ethernet limitations:
•
–
–
–
These are the workarounds:
–
–
–
For more information, enter CSCea77032 in the Bug Toolkit at this URL:
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl
•
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.
•
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 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:
•
•
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:
•
•
IP Telephony
These are the IP telephony limitations:
•
•
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)
•
The workaround is to enter the power inline never interface configuration command on all the Fast Ethernet ports that are not powered by but are connected to IP phones if the problem persists. (CSCef84975, Cisco EtherSwitch service modules only)
•
•
The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)
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)
Management
CiscoWorks is not supported on the Catalyst 3750-24FS switch.
Multicasting
These are the multicasting limitations:
•
•
•
•
•
•
•
•
–
–
There is no workaround. (CSCec20128)
•
The switchport block multicast interface configuration command is only applicable to non-IP multicast traffic.
There is no workaround. (CSCee16865)
•
–
–
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:
–
–
•
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:
•
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)
•
Router# show power inlinePowerSupply SlotNum. Maximum Allocated Status----------- -------- ------- --------- ------INT-PS 0 360.000 121.000 PS1 GOOD PS2 ABSENTInterface Config Device Powered PowerAllocated--------- ------ ------ ------- --------------Gi4/0 auto Unknown On 121.000 WattsThis is not a problem because the display correctly shows the total used power and the remaining power available on the system. (CSCeg74337)
•
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:
•
•
Routing
These are the routing limitations:
•
•
•
%SYS-2-MALLOCFAIL: Memory allocation of 4252 bytes failed from 0x179C80, alignment 0Pool: I/O Free: 77124 Cause: Memory fragmentationAlternate Pool: None Free: 0 Cause: No Alternate poolThis 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)
•
–
–
–
The workaround is to change any one of the listed conditions. (CSCed53633)
•
The workaround is to use an IP address as the next hop instead of an interface.
(CSCsi16162 [Catalyst 3750 and 3560 switches])SPAN and RSPAN
These are the SPAN and Remote SPAN (RSPAN) limitations.
•
This is a hardware limitation and only applies to these switches (CSCdy72835):
–
–
–
–
–
–
–
–
–
–
–
•
This is a hardware limitation and only applies to these switches (CSCdy81521):
–
–
–
–
–
–
–
–
–
–
–
–
–
•
This is a hardware limitation and only applies to these switches (CSCea72326):
–
–
–
–
–
–
–
–
–
–
–
–
–
•
•
•
Stacking (Catalyst 3750 or Cisco EtherSwitch service module switch stack only)
These are the Catalyst 3750 and Cisco EtherSwitch service module switch stack limitations:
•
•
•
•
•
There is no workaround. (CSCed54150)
•
The workaround is to complete the MAC address update by entering the clear arp privileged EXEC command. (CSCed62409)
•
•
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):
–
–
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:
–
–
•
This is the expected behavior of the offline configuration (provisioning) feature. There is no workaround. (CSCee12431)
•
The workaround is to copy the bootable image to the parent directory or first directory. (CSCei69329)
•
The workaround is to assign a lower path cost to the forwarding port. (CSCsd95246)
•
This can but does not always occur during link flaps and does not last for more than a few milliseconds. This problem can happen for cross-stack EtherChannels with the mode set to ON or LACP.
There is no workaround. No manual intervention is needed. The problem corrects itself within a short interval after the link flap as all the switches in the stack synchronize with the new load-balance configuration. (CSCse75508)
•
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
•
–
–
–
You can use one of these workarounds:
–
–
Trunking
These are the trunking limitations:
•
•
•
•
VLAN
These are the VLAN limitations:
•
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
•
There is no workaround. (CSCed71422)
•
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)
•
The workaround is to configure the burst interval to more than 1 second. (CSCse06827, Catalyst 3750 switches only)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port. (CSCsi26392)
Device Manager Limitations
These are the device manager limitations:
•
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
These notes apply to switch stacks:
•
•
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
•
–
–
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)
•
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, check that there is network connectivity between the switch and the ACS. You should also check that the switch has been properly configured as an AAA client on the ACS
•
AutoQoS Error: ciscophone input service policy was not properly appliedpolicy map AutoQoS-Police-CiscoPhone not configuredIf this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
Device Manager Notes
These notes apply to the device manager:
•
•
•
•
•
From Microsoft Internet Explorer:
1.
2.
3.
4.
5.
•
Beginning in privileged EXEC mode, follow these steps to configure the HTTP server interface:
•
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:
•
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:
•
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:
–
–
•
A duplex mismatch occurs when two Fast Ethernet interfaces that are directly connected on two EtherSwitch service modules are configured as both 100 Mb/s and full duplex and as automatic speed and duplex settings. This is expected behavior for the PHY on the Cisco EtherSwitch service modules.
There is no workaround.
•
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 timeoutThe 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.
•
The switch might display tracebacks similar to these examples when a large number of IEEE 802.1x supplicants try to repeatedly log in and log out.
Examples:
Jan 3 17:54:32 L3A3 307: Jan 3 18:04:13.459: %SM-4-BADEVENT: Event 'eapReq' is invalid for the current state 'auth_bend_idle': dot1x_auth_bend Fa9
Jan 3 17:54:32 L3A3 308: -Traceback= B37A84 18DAB0 2FF6C0 2FF260 8F2B64 8E912C Jan 3 19:06:13 L3A3 309: Jan 3 19:15:54.720: %SM-4-BADEVENT: Event 'eapReq_no_reAuthMax' is invalid for the current ate 'auth_restart': dot1x_auth Fa4
Jan 3 19:06:13 L3A3 310: -Traceback= B37A84 18DAB0 3046F4 302C80 303228 8F2B64 8E912C Jan 3 20:41:44 L3A3 315: .Jan 3 20:51:26.249: %SM-4-BADEVENT: Event 'eapSuccess' is invalid for the current state 'auth_restart': dot1x_auth Fa9
Jan 3 20:41:44 L3A3 316: -Traceback= B37A84 18DAB0 304648 302C80 303228 8F2B64 8E912C
There is no workaround.
•
When IEEE 802.1x is globally disabled on the switch by using the no dot1x system-auth-control global configuration command, some interface level configuration commands, including the dot1x timeout and dot1x mac-auth-bypass commands, become unavailable.
The workaround is to enable the dot1x system-auth-control global configuration command before attempting to configure interface level IEEE 802.1x parameters.
•
If you enter the no ip vrf vrf-name global configuration command to delete a VPN routing/forwarding instance on the switch when routing is not enabled on the switch, the VRF instance is held in the delete queue. The VRF entry does not appear in the output when you enter the show running-config privileged EXEC command, but it is shown when you enter the show ip vrf privileged EXEC command. When a VRF instance is in the deleted queue, it is using one of the system's maximum allowable VRFs, and you cannot configure a new VRF with the same name.
The workaround is to enable IP routing on the switch by entering the ip routing global configuration. When you enable routing, the VRF is cleared from the deleted queue.
•
When you enter the boot host retry timeout global configuration command to specify the amount of time that the client should keep trying to download the configuration and you do not enter a timeout value, the default value is zero, which should mean that the client keeps trying indefinitely. However, the client does not keep trying to download the configuration.
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command.
•
A stack member switch might fail to bundle Layer 2 protocol tunnel ports into a port channel when you have followed these steps:
1. You configure a Layer 2 protocol tunnel port on the master switch.
2. You configure a Layer 2 protocol tunnel port on the member switch.
3. You add the port channel to the Layer 2 protocol tunnel port on the master switch.
4. You add the port channel to the Layer 2 protocol tunnel port on the member switch.
After this sequence of steps, the member port might stay suspended.
The workaround is to configure the port on the member switch as a Layer 2 protocol tunnel and at the same time also as a port channel. For example:
Switch(config)# interface fastethernet1/0/11Switch(config-if)# l2protocol-tunnel cdpSwitch(config-if)# channel-group 1 mode on•
When a RIP network and IP address are configured on an interface, a traceback error occurs after you enter the shutdown, no shutdown, switchport and no switchport interface configuration commands.
The workaround is to configure the RIP network and the IP address after you configure the interface.
•
In a mixed stack of Catalyst 3750 switches and Catalyst 3750-E switches, when the stack reloads, the Catalyst 3750-E might not become stack master, even it has a higher switch priority set.
The workaround is to check the flash. If it contains many files, remove the unnecessary ones. Check the lost and found directory in flash and if there are many files, delete them. To check the number of files use the fsck flash: command.
•
The configuration file used for the configuration replacement feature requires the character string end\n at the end of the file. The Windows Notepad text editor does not add the end\n string, and the configuration rollback does not work.
These are the workarounds. (You only need to do one of these.)
–
–
•
If you upgrade the software image from Cisco IOS Release 12.2(25)SEE2 to Cisco IOS Release 12.2(35)SE1, the IPv6 static routes are in the switch configuration but might not be in the routing table.
The workaround is to specify the egress interface on the IPv6 static route.
•
When a per-port per-VLAN policy map (a hierarchical VLAN-based policy map) is attached to a VLAN interface, and you remove the child-policy policer from the policy map and then add it back, the policy map fails to re-attach to the same SVI
The workaround is to delete the child policy, which removes it from the parent policy. Then recreate the child policy (with the same or a different name) and reference it in the parent policy. The parent policy then successfully attaches to the SVI.
•
The switch does not correctly update the entPhysicalChildIndex objects from the ENTITY-MIB, and some of the entPhysicalChildIndex entries are missing from the table. This adversely affects network management applications such as CiscoWorks CiscoView because they cannot manage the switch.
There is no workaround.
•
A switch configured for Link Layer Discovery Protocol (LLDP) might not correctly report the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes. System capabilities appear correctly, but the enabled capabilities are not identified if the switch is configured only as a Layer 2 switch.
There is no workaround.
•
When a switch stack boots up, one or more traceback messages may appear on the switch console when the switch stack has these conditions:
–
–
–
The workaround is to execute clear ip mds linecard [<num>| *] to re-trigger the multicast information download from Route Processor to Line Card. This should be executed after the VLAN database is in sync across the stack.
•
When the configuration file is removed from the switch and the switch is rebooted, port status for VLAN 1 and the management port (Fast Ethernet 0) is sometimes reported as up and sometimes as down, resulting in conflicts. This status depends on when you respond to the reboot query:
Would you like to enter the initial configuration dialog?
–
–
The workaround is to wait for approximately 1 minute after rebooting and until the VLAN 1 interface line status appears on the console before you respond to the query.
•
After a stack bootup, the spanning tree state of a port that has IEEE 802.1x enabled might be blocked, even when the port is in the authenticated state. This can occur on a voice port where the Port Fast feature is enabled.
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state.
Resolved Caveats
•
•
•
•
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE6
•
When MAC authentication bypass (MAB) authentication fails, a memory leak no longer occurs.
•
When a VLAN is assigned for IEEE 802.1x authentication and no VLAN is assigned for other types of authentication (such as user authentication or reauthentication), the 802.1x VLAN assignment no longer persists across subsequent authentication attempts.
•
When the switch uses HTTP (web-based) authentication, a memory leak no longer occurs after authorization and policy download.
•
A switch no longer displays processor memory-allocation failure messages under these conditions:
–
–
–
Note
This is resolved in Cisco IOS 12.2(44)SE6 and later.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE5
•
A switch no longer fails when a BGP peer flap occurs at the same time as a peer configuration policy is being modified.
•
Excessive IPRT-3-PATHIDX error messages no longer appear in the log file.
•
When configuring an IP SSH version 2 connection, you can no longer create an RSA key that is less than 768 bits.
•
RIP routes now correctly update when the maximum-paths 16 option is used.
•
The DHCP server can be configured to send DHCP Not Acknowledge (DHCPNAK) messages to unknown clients.
•
Symptoms: Several features within Cisco IOS software are affected by a crafted UDP packet vulnerability. If any of the affected features are enabled, a successful attack will result in a blocked input queue on the inbound interface. Only crafted UDP packets destined for the device could result in the interface being blocked, transit traffic will not block the interface.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the workarounds section of the advisory. This advisory is posted at the following link: http://www.cisco.com/warp/public/707/cisco-sa-20090325-udp.shtml.
•
TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.
•
A vulnerability in the handling of IP sockets can cause devices to be vulnerable to a denial of service attack when any of several features of Cisco IOS software are enabled. A sequence of specially crafted TCP/IP packets could cause any of the following results:
–
–
–
–
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory. The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-ip.shtml
•
An EAP-Success message is now sent to a supplicant after it is authenticated on a port.
•
When you apply the ip pim sparse mode and ip wccp web-cache redirect in configuration commands on a global table interface, traffic is now sent to multicast receivers.
•
Outgoing packets are no longer dropped from an interface with policy-based routing (PBR):
–
–
•
A switch now boots correctly after a software reload or power cycle. In previous releases, under some rare circumstances, the image would be truncated to zero bytes and the switch would not boot.
•
The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.
•
A switch with an IP PIM passive configuration entered no longer stops listening to an auto-rp group.
•
Cisco IOS software contains a vulnerability in multiple features that could allow an attacker to cause a denial of service (DoS) condition on the affected device. A sequence of specially crafted TCP packets can cause the vulnerable device to reload.
Cisco has released free software updates that address this vulnerability.
Several mitigation strategies are outlined in the workarounds section of this advisory.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090325-tcp.shtml
•
IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.
•
The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.
•
The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).
•
The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.
•
A PoE switch no longer stops delivering power in certain conditions when a PoE device is reconnected after a port has gone down.
•
You can now Telnet from the switch by using the hostname followed by a Virtual Routing and Forwarding (VRF) name.
•
The server side of the Secure Copy (SCP) implementation in Cisco IOS software contains a vulnerability that could allow authenticated users with an attached command-line interface (CLI) view to transfer files to and from a Cisco IOS device that is configured to be an SCP server, regardless of what users are authorized to do, per the CLI view configuration. This vulnerability could allow valid users to retrieve or write to any file on the device's file system, including the device's saved configuration and Cisco IOS image files, even if the CLI view attached to the user does not allow it. This configuration file may include passwords or other sensitive information.
The Cisco IOS SCP server is an optional service that is disabled by default. CLI views are a fundamental component of the Cisco IOS Role-Based CLI Access feature, which is also disabled by default. Devices that are not specifically configured to enable the Cisco IOS SCP server, or that are configured to use it but do not use role-based CLI access, are not affected by this vulnerability.
This vulnerability does not apply to the Cisco IOS SCP client feature.
Cisco has released free software updates that address this vulnerability.
There are no workarounds available for this vulnerability apart from disabling either the SCP server or the CLI view feature if these services are not required by administrators.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090325-scp.shtml.
•
Multiple Cisco products are affected by denial of service (DoS) vulnerabilities that manipulate the state of Transmission Control Protocol (TCP) connections. By manipulating the state of a TCP connection, an attacker could force the TCP connection to remain in a long-lived state, possibly indefinitely. If enough TCP connections are forced into a long-lived or indefinite state, resources on a system under attack may be consumed, preventing new TCP connections from being accepted. In some cases, a system reboot may be necessary to recover normal system operation. To exploit these vulnerabilities, an attacker must be able to complete a TCP three-way handshake with a vulnerable system.
In addition to these vulnerabilities, Cisco Nexus 5000 devices contain a TCP DoS vulnerability that may result in a system crash. This additional vulnerability was found as a result of testing the TCP state manipulation vulnerabilities.
Cisco has released free software updates for download from the Cisco website that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090908-tcp24.shtml.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE4 (Catalyst 3750 Switches Only)
•
A switch no longer fails when a BGP peer flap occurs at the same time as a peer configuration policy is being modified.
•
RIP routes now correctly update when the maximum-paths 16 option is used.
•
The DHCP server can be configured to send DHCP Not Acknowledge (DHCPNAK) messages to unknown clients.
•
TACACS+ authorization no longer fails on a device when an unknown TACACS+ attribute is received from the TACACS+ server.
•
An EAP-Success message is now sent to a supplicant after it is authenticated on a port.
•
A switch now boots correctly after a software reload or power cycle. In previous releases, under some rare circumstances, the image would be truncated to zero bytes and the switch would not boot.
•
The dot1x timeout reauth-period server interface configuration command now works correctly. In previous releases, the switch would reauthenticate correctly after the command was entered, but the switch would then reauthenticate every 10 minutes.
•
A switch with an IP PIM passive configuration entered no longer stops listening to an auto-rp group.
•
IPv6 MLD snooping now continues to work correctly after a switch in the stack reloads.
•
The cdpCacheAddress value now appears in a GLOBAL_UNICAST address.
•
The switch now correctly processes ingress traffic when a port is configured with a short 802.1x tx-period timer value (such as dot1x timeout tx-period 3).
•
The username is now properly logged when the remote command privileged EXEC command is used to configure a cluster member.
•
A PoE switch no longer stops delivering power in certain conditions when a PoE device is reconnected after a port has gone down.
•
Avaya IP phones now correctly authenticate on an 802.1x-enabled switch port.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE3
•
An SNMP access-control list (ACL) now works correctly on virtual routing and forwarding (VRF) interfaces.
•
Intermittently switch reloads no longer occur when IP helper addresses are configured on a VLAN.
•
When multiple voice-over-IP phones are connected to a switch or switch stack with MAC authentication bypass enabled, setting the IEEE 802.1x timeout period too low no longer causes a switch in single-host mode to authenticate the phones using MAC authentication bypass, except when other data packets are received before CDP packets.
•
An end host no longer remains in the guest VLAN after an IEEE 802.1X authentication.
•
A switch no longer drops Cisco Group Management Protocol (CGMP) packets.
•
A switch stack can now send a VTP join message for a VLAN without access associated ports, but for which a Layer 3 VLAN interface exists without causing the VLAN to be pruned.
•
The switch no longer reloads with an address error if the TACACS+ server sends an authentication error when the access control system is configured and a timeout request occurs.
•
Layer 4 operations now work correctly for all port ranges in QoS policy maps.
•
A network loop or incorrect spanning-tree status no longer occurs when you enable cross-stack EtherChannel and connect customer edge devices across a Layer 2 protocol tunnel. The STP bridge protocol data units (BPDUs) now reach the remote end when they are received on an EtherChannel port that is not on the stack master.
•
When IEEE 802.1x port-based authentication is enabled on the switch, Extensible Authentication Protocol (EAP) notification packets from the supplicant are no longer discarded.
•
When IP routing is enabled, the integrated Wireless LAN Controller (WLC) module no longer regularly resets.
•
In environments using Layer 2 IP Network Admission Control (NAC), long downloadable ACLs (dACLs) with source or destination Layer 4 ports no longer cause unpredictable events in which all traffic is dropped and URL redirects are not enforced.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE2
Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules:
•
Traceback messages no longer appear if you enter the no switchport interface configuration command to change a Layer 2 interface that belongs to a port channel to a routed port.
•
When you configure fallback bridging with redundant links on a switch stack, VLAN bridge STP now correctly blocks the SVIs and routed ports that lead to the redundant path. This works even if the physical ports configured on the bridge domain VLANs belong to the member switches in the stack.
•
The switch no longer unexpectedly reloads while configured with IEEE 802.1x authentication and the MAC authentication bypass feature.
•
When you enable detection of Cisco IP phones by entering the switchport voice detect cisco-phone interface configuration command, the interface is no longer disabled if you connect a third-party IP phone is connected to the interface.
Note
•
When you configure a port channel as trusted by entering the ip dhcp snooping trust interface configuration command, the configuration is no longer lost when the link goes from down to up.
•
This traceback error no longer appears when you enter the show aaa subscriber profile privileged EXEC command:
*Mar 2 01:50:41.127: %PARSER-3-BADSUBCMD: Unrecognized subcommand 10 in exec command'show aaa subscriber profile WORD'-Traceback= D003B4 D00AC8 C908A0 C2F040 C8CA18 CB8984 93B670 932338
Note
•
Enhanced IGRP (EIGRP) now works correctly when you enter the ip authentication key-chain eigrp interface configuration command.
•
An IP address can be assigned to a routed port that is up and also assigned to a routed port that is administratively down. If you remove the IP address from the down port, the switch no longer loses the hardware forwarding information.
•
A switch no longer unexpectedly reloads when you configure two or more authentication, authorization, and accounting (AAA) broadcast groups.
•
On a switch stack with multiple members, a switch now provides a timely response to an SNMP request on the BridgeMIB's object dot1dBaseNumPorts.
•
The switch no longer experiences a memory leak during an HTTP core process.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE1
Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules:
•
A router that is configured for HTTP and voice-based services no longer unexpectedly reloads due to memory corruption.
•
Cisco uBR10012 series devices automatically enable Simple Network Management Protocol (SNMP) read/write access to the device if configured for linecard redundancy. This can be exploited by an attacker to gain complete control of the device. Only Cisco uBR10012 series devices that are configured for linecard redundancy are affected.
Cisco has released free software updates that address this vulnerability. Workarounds that mitigate this vulnerability are available.
This advisory is posted at
http://www.cisco.com/warp/public/707/cisco-sa-20080924-ubr.shtml.
•
When AAA is enabled and you use the aaa group server radius group-name global configuration command to put the switch in server group configuration mode, entering the server-private command no longer causes the switch to reload.
•
Two crafted Protocol Independent Multicast (PIM) packet vulnerabilities exist in Cisco IOS software that may lead to a denial of service (DoS) condition. Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-multicast.shtml.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
•
A series of segmented Skinny Call Control Protocol (SCCP) messages may cause a Cisco IOS device that is configured with the Network Address Translation (NAT) SCCP Fragmentation Support feature to reload.
Cisco has released free software updates that address this vulnerability. A workaround that mitigates this vulnerability is available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sccp.shtml.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
•
Cisco IOS software configured for Cisco IOS firewall Application Inspection Control (AIC) with a HTTP configured application-specific policy are vulnerable to a Denial of Service when processing a specific malformed HTTP transit packet. Successful exploitation of the vulnerability may result in a reload of the affected device.
Cisco has released free software updates that address this vulnerability.
A mitigation for this vulnerability is available. See the "Workarounds" section of the advisory for details.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-iosfw.shtml.
•
The switch no longer reloads when you use the aaa authentication eou default group radius enable global configuration command to configure an EAP over UDP (EOU) method list.
•
A vulnerability exists in the Cisco IOS software implementation of Layer 2 Tunneling Protocol (L2TP), which affects limited Cisco IOS software releases.
Several features enable the L2TP mgmt daemon process within Cisco IOS software, including but not limited to Layer 2 virtual private networks (L2VPN), Layer 2 Tunnel Protocol Version 3 (L2TPv3), Stack Group Bidding Protocol (SGBP) and Cisco Virtual Private Dial-Up Networks (VPDN). Once this process is enabled the device is vulnerable.
This vulnerability will result in a reload of the device when processing a specially crafted L2TP packet.
Cisco has released free software updates that address this vulnerability.
Workarounds that mitigate this vulnerability are available in the "workarounds" section of the advisory.
The advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-l2tp.shtml.
•
A series of segmented Skinny Call Control Protocol (SCCP) messages may cause a Cisco IOS device that is configured with the Network Address Translation (NAT) SCCP Fragmentation Support feature to reload.
Cisco has released free software updates that address this vulnerability. A workaround that mitigates this vulnerability is available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sccp.shtml.
•
A Cisco IOS device may crash while processing an SSL packet. This can happen during the termination of an SSL-based session. The offending packet is not malformed and is normally received as part of the packet exchange.
Cisco has released free software updates that address this vulnerability.
Aside from disabling affected services, there are no available workarounds to mitigate an exploit of this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-ssl.shtml.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
•
Two crafted Protocol Independent Multicast (PIM) packet vulnerabilities exist in Cisco IOS software that may lead to a denial of service (DoS) condition. Cisco has released free software updates that address these vulnerabilities. Workarounds that mitigate these vulnerabilities are available.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-multicast.shtml.
•
Note
If more than 24 switch ports are configured with the same policy map, CPU_HOG traceback errors no longer occur when the switch is reloaded.
•
High CPU usage (greater than 90 percent) no longer occurs on the switch when you first connect a new device.
•
A switch no longer unexpectedly reloads when you configure the switch ports as dynamic ports by using the VLAN Membership Policy Server (VMPS).
•
You can now use the interface range interface configuration command to configure IP source guard on member switches.
•
The Cisco IOS Intrusion Prevention System (IPS) feature contains a vulnerability in the processing of certain IPS signatures that use the SERVICE.DNS engine. This vulnerability may cause a router to crash or hang, resulting in a denial of service condition.
Cisco has released free software updates that address this vulnerability. There is a workaround for this vulnerability.
NOTE: This vulnerability is not related in any way to CVE-2008-1447 - Cache poisoning attacks. Cisco Systems has published a Cisco Security Advisory for that vulnerability, which can be found at http://www.cisco.com/en/US/products/products_security_advisory09186a00809c2168.shtml.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-iosips.shtml.
•
Multiple vulnerabilities exist in the Session Initiation Protocol (SIP) implementation in Cisco IOS that can be exploited remotely to trigger a memory leak or to cause a reload of the Cisco IOS device.
Cisco has released free software updates that address these vulnerabilities. Fixed Cisco IOS software listed in the Software Versions and Fixes section contains fixes for all vulnerabilities addressed in this advisory.
There are no workarounds available to mitigate the effects of any of the vulnerabilities apart from disabling the protocol or feature itself, if administrators do not require the Cisco IOS device to provide voice over IP services.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20080924-sip.shtml.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(44)SE
Unless otherwise noted, these resolved caveats apply to the Catalyst 3750, 3560, 2970, and 2960 switches and the Cisco EtherSwitch service modules:
•
This error message no longer appears during authentication when a method list is used and one of the methods in the method list is removed:
AAA-3-BADMETHODERROR:Cannot process authentication method 218959117•
The switch no longer reloads when you use a Kron command scheduler routine to automatically copy configuration data using the Secure Copy Protocol (SCP). (Kron is a Cisco IOS utility for scheduling non-prompting CLI commands to execute at a later time.)
•
When you remove and reconfigure a loopback interface, it now appears in the ifTable.
•
If the switch is in VTP server mode and VLANs with IDs higher than 255 are created, DHCP snooping now works properly on these VLANs.
•
When a switch is connected to a third-party router through an EtherChannel and the EtherChannel is running in Link Aggregation Control Protocol (LACP) mode, the interfaces in the EtherChannel no longer fail after you enter the switchport trunk native vlan vlan-id interface configuration command to change the native VLAN from VLAN 1 (the default) to a different VLAN ID.
•
A switch no longer increments the receive-error counters, including CRC, FCS, symbol, and false carrier errors, after the connected device is reloaded or power cycled.
•
A switch with the Dynamic ARP Inspection feature enabled no longer experiences the issue that triggered the display of buffer sharecount messages under certain patterns of ARP packet traffic.
•
When a device is attached to a multidomain authentication (MDA)-enabled port that has an IEEE 802.1x guest VLAN configured but not MAC authentication bypass (MAB), if the switch obtains its MAC address from that port, the device is authenticated in the guest VLAN but appears as an IEEE 802.1x-authenticated device.
•
If IEEE 802.1x critical authentication is not enabled and the RADIUS authentication server is temporarily unavailable during a reauthentication, when the RADIUS server comes back up, MAC authentication bypass (MAB) does not authenticate a previously authenticated client.
•
When a stack master changeover event occurs, the backup interface no longer loses traffic. In previous releases, traffic loss occurred for up to 4 seconds under these conditions:
–
–
–
–
•
The snmpEngineBoots MIB object now increments when a Catalyst 3750 switch restarts.
•
When a VLAN includes multiple MAC addresses, the number of MAC addresses shown in SNMP now matches the output of the show mac-address count vlan vlan-id privileged EXEC command.
•
The dynamic MAC address is now removed from the interface when port security is configured on a PVLAN interface.
•
This message no longer appears when you set an interface back to its default configuration by using the default interface configuration command, this message no longer appears:
%SM-4-STOPPED: Event 'mabAbort' ignored because the state machine is stopped: dot1x_auth_mab-Traceback= 1D2368 3C1BA8 3C1D40 3C16A8 9EF8D8 9E6CC4•
When you configure two local source SPAN sessions and then delete these SPAN sessions, the switch allows the creation of new sessions and no longer displays this error message:
% Platform can support a maximum of 2 source sessions•
During switch configuration, this error message no longer appears:
00:07:17: platform assert failure: 0: ../src-hulc/src-common/hspan.c: 817: hspan_get_sasq_session 00:07:17: -Traceback= 503148 9218EC 922C8C 922040 923AB0 9242CC 927DD0 9186B0 918BA8 914714 CCADF0 CE73F0 9EF8D8 9E6CC4•
Changing the spanning tree mode from MSTP to other spanning modes no longer causes tracebacks.
•
During master switch failover, a VLAN that has been error disabled on a port is no longer re-enabled after the master switch changeover.
•
When unicast routing is disabled and then re-enabled, virtual routing and forwarding (VRF) routing is no longer disabled on the switch interfaces.
•
After a stack-master failover, switch ports in the stack now detect new devices. In previous releases, new devices connected to the switch ports after the failover were not detected.
•
Broadcast storm control now works correctly on IEEE 802.1Q trunk ports.
•
When you enter the show process cpu privileged EXEC command on a Catalyst 3750 model WS-C3750G-48PS, the LED process no longer causes high CPU usage.
•
The cpmCPURisingThreshold traps on the switch are no longer missing the cpmProcExtUtil5SecRev and cpmProcessTimeCreated trap components. Note that although the components were missing from the traps, the PROCESS MIB was still populating the objects.
•
OSPF hello packets now have the correct CoS value of 7.
•
A Cisco IP Phone now works correctly when it is connected to a port that is configured with CDP bypass and multidomain authentication (MDA).
•
When IPv6 unicast routing and IPv4 multicast routing are enabled on a switch, a group of consecutive ports no longer stops receiving frames when IPv6 unicast packets are unicast routed and IPv4 multicast packets are multicast routed on ports within the range of the affected consecutive ports.
•
When you enter the show interface status privileged EXEC command on the switch, a port no longer might show notconnect for an inline power port when the show power inline privileged EXEC command shows that the port is still delivering power.
•
A significant delay no longer occurs when you remove an access control list (ACL) from a switch stack under these conditions:
–
–
–
•
ACLs are now configured correctly when they contain ICMP codes 251 to 255.
•
The class of service (CoS) values of software-switched IPv6 packets are preserved. The switch no longer overwrites CoS values when software-forwarding an IPv6 packet.
•
If you upgrade from Cisco IOS Release 12.2(35)SE1 to Release 12.2(37)SE, a security violation no longer occurs when:
–
–
•
The TxBufferFullDropCount no longer continuously increments on a switch or switch stack.
•
The Total output drops field in the show interfaces privileged EXEC command output now displays accurate ASIC drops.
•
The multicast expansion descriptor (MED) is no longer misprogrammed for statically configured groups after you reload the switch.
•
When IGMP snooping is enabled, CGMP interoperability mode now works as it should when the upstream multicast router is set up correctly with PIM and IP CGMP.
•
MAC address-table move update (MMU) messages are now correctly sent if the active port that is configuring the per-VLAN flex link is down.
•
If you enter a space before a comma in the define interface-range or the interface range global configuration command, the space before the comma is now saved in the switch configuration.
•
When a switch is running the cryptographic IP services image, the output of the show ip wccp service-number detail privileged EXEC command output no longer shows unsupported features such as Generic Routing Encapsulation (GRE) redirection and hash assignment even though the switch does not support them.
•
The output of the show interfaces privileged EXEC command now shows correctly when you have removed the XENPAK module from the switch.
•
A switch configured for Link Layer Discovery Protocol (LLDP) now correctly reports the enabled switch capabilities in the LLDP type, length, and value (TLV) attributes.
•
When VTP pruning is enabled, the switch no longer might experience high CPU usage (greater than 90 percent) for up to 20 minutes after the link comes up simultaneously on multiple trunk ports.
•
On a switch that supports fallback bridging, when a bridge-group is configured on some VLANs, non-IP traffic in the VLANs destined to a known MAC address are no longer flooded in the bridge-group.
•
When you are using AAA for Telnet and console authentication and login failure and success debugging is enabled, the username now shows correctly in the log.
•
When you enter the show sdm prefer privileged EXEC command, the output is now the same as actual TCAM usage as specified in the documentation.
•
When the switch has VTP pruning and an RSPAN session configured, the RSPAN VLAN traffic is now correctly pruned as set up by the VTP pruning configuration.
•
A switch running several SSHv2 clients no longer fails if any of the SSH clients are terminated.
•
When you have upgraded the Cisco IOS image on a WS-C3750G-12S switch, the switch no longer enters a boot loop after the upgrade.
•
On a switch with routed ports, when you configure MAC address-table aging time by entering the mac address-table aging-time time global configuration command and then enter the show running-config privileged EXEC command, the output no longer displays the aging time values for internal VLANs.
•
When UDLD is enabled on a Layer 2 interface, and the native VLAN for the port is not configured as a VLAN on the switch, UDLD no longer puts the port into an error-disabled state.
•
A switch no longer fails when you enter the show interfaces vlan vlan-id switchport privileged EXEC command.
•
If you enter the hostname global configuration command followed by a hostname that contains illegal characters, for example, one that appears to be an IP address, the switch now displays a warning message, but the specified hostname is configured.
•
A switch no longer fails under these conditions:
–
–
–
•
When port security is configured on a switch, a device MAC address is now correctly learned on that port. (In previous releases, a new device MAC address was not learned on a port-security enabled port, and the device MAC address was not added to the list of secure addresses.)
•
The output of these show user EXEC commands now display the correct status of ports in a cross-stack EtherChannel bundle:
–
–
•
Web authentication no longer stops working when IEEE 802.1X re-authentication is enabled and the re-authentication timer expires.
Documentation Updates
•
•
•
•
•
•
•
•
Updates to the Catalyst 3750, 3560, and 2960 Switch Software Configuration Guides
These are updates to the software configuration guides:
•
Note
•
When you globally enable BPDU guard on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state), spanning tree shuts down Port Fast-enabled ports that receive BPDUs.
•
When you globally enable BPDU guard on ports that are Port Fast-enabled (the ports are in a Port Fast-operational state), spanning tree continues to run on the ports. They remain up unless they receive a BPDU.
•
When Cisco powered devices are connected to PoE ports, the switch uses Cisco Discovery Protocol (CDP) to determine the actual power consumption of the devices, and the switch adjusts the power budget accordingly. This does not apply to IEEE third-party powered devices.
This is the correct information:
When Cisco powered devices are connected to PoE ports, the switch uses Cisco Discovery Protocol (CDP) to determine the actual power consumption of the devices, and the switch adjusts the power budget accordingly. The CDP protocol works with Cisco powered devices and does not apply to IEEE third-party powered devices.
•
If the power supply is over-subscribed to by up to 20 percent, the switch continues to operate but its reliability is reduced. If the power supply is subscribed to by more than 20 percent, the short-circuit protection circuitry triggers and shuts the switch down.
•
•
Updates to Only the Catalyst 3750 and 3560 Switch Software Configuration Guides
These are updates for only the 3750 and 3560 software configuration guides:
•
You can also enable the login enhancements feature, which logs both failed and unsuccessful login attempts. Login enhancements can also be configured to block future login attempts after a set number of unsuccessful attempts are made. For more information, see the Cisco IOS Login Enhancements documentation at this URL:
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t4/feature/guide/gt_login.html
•
All protocols except IP (Version 4 and Version 6), Address Resolution Protocol (ARP), reverse ARP (RARP), LOOPBACK, Frame Relay ARP, and shared STP packets are fallback bridged.
•
After you have entered the eigrp stub router configuration command, only the eigrp stub connected summary command takes effect. Although the CLI help might show the receive-only and static keywords and the you can enter these keywords, the switch running the IP base image always behaves as if the connected and summary keywords were configured.
•
If no VRFs are configured, 104 policies can be configured.
This is the correct guideline:
If no VRFs are configured, up to 105 policies can be configured.
•
Per-user ACLs are supported only in single-host mode.
•
You can configure up to 8 service groups on a switch or switch stack and up to 32 clients per service group. WCCP maintains the priority of the service group in the group definition. WCCP uses the priority to configure the service groups in the switch hardware. For example, if service group 1 has a priority of 100 and looks for destination port 80, and service group 2 has a priority of 50 and looks for source port 80, the incoming packet with source and destination port 80 is forwarded by using service group 1 because it has the higher priority.
This is the correct information:
You can configure up to 8 service groups on a switch or switch stack and up to 32 cache engines per service group. WCCP maintains the priority of the service group in the group definition. WCCP uses the priority to configure the service groups in the switch hardware. For example, if service group 1 has a priority of 100 and looks for destination port 80, and service group 2 has a priority of 50 and looks for source port 80, the incoming packet with source and destination port 80 is forwarded by using service group 1 because it has the higher priority.
•
Before WCCP packets are redirected, the switch examines ACLs associated with all inbound features configured on the interface and permits or denies packet forwarding based on how the packet matches the entries in the ACL.
Note
•
This example shows how to configure SVIs and how to enable the web cache service with a multicast group list. VLAN 299 is created and configured with an IP address of 175.20.20.10. Gigabit Ethernet port 1 is connected through the Internet to the web server and is configured as an access port in VLAN 299. VLAN 300 is created and configured with an IP address of 172.20.10.30. Gigabit Ethernet port 2 is connected to the application engine and is configured as an access port in VLAN 300. VLAN 301 is created and configured with an IP address of 175.20.30.50. Fast Ethernet ports 3 to 6, which are connected to the clients, are configured as access ports in VLAN 301. The switch redirects packets received from the client interfaces to the application engine.
Note
•
Voice VLAN configuration is only supported on switch access ports; voice VLAN configuration is not supported on trunk ports.You can configure a voice VLAN only on Layer 2 ports.
Note
•
Note
This chapter consists of these sections:
–
–
–
Understanding Embedded Event Manager
The embedded event manager (EEM) monitors key system events and then acts on them though a set policy. This policy is a programmed script that you can use to customize a script to invoke an action based on a given set of events occurring. The script generates actions such as generating custom syslog or Simple Network Management Protocol (SNMP) traps, invoking CLI commands, forcing a failover, and so forth. The event management capabilities of EEM are useful because not all event management can be managed from the switch and because some problems compromise communication between the switch and the external network management device. Network availability is improved.if automatic recovery actions are performed without rebooting the switch,
Figure 1-1 shows the relationship between the EEM server, the core event publishers (event detectors), and the event subscribers (policies). The event publishers screen events and when there is a match on an event specification that is provided by the event subscriber. Event detectors notify the EEM server when an event occurs. The EEM policies then implement recovery based on the current state of the system and the actions specified in the policy for the given event.
Figure 1-1 Embedded Event Manager Core Event Detectors
These sections contain this conceptual information:
–
–
–
Event Detectors
EEM software programs known as event detectors determine when an EEM event occurs. Event detectors are separate systems that provide an interface between the agent being monitored, for example SNMP, and the EEM polices where an action can be implemented. Event detectors are generated only by the master switch. CLI and routing processes also run only from the master switch.
Note
EEM allows these event detectors:
–
–
–
–
–
–
–
–
–
–
–
Publishes events for these timers:
–
–
–
–
Watchdog event detector (IOSWDSysMon). This detector applies only to the master switch.
Publishes an event when one of these events occurs:
–
–
Two events can be monitored at the same time, and the event publishing criteria requires that one or both events cross their specified thresholds.
Embedded Event Manager Actions
EEM provides actions that occur in response to an event. EEM supports these actions:
–
–
–
–
–
–
–
Embedded Event Manager Policies
EEM can monitor events and provide information, or take corrective action when the monitored events occur or a threshold is reached. An EEM policy is an entity that defines an event and the actions to be taken when that event occurs.
There are two types of EEM policies: an applet or a script. An applet is a simple policy that is defined within the CLI configuration. It is a concise method for defining event screening criteria and the actions to be taken when that event occurs. Scripts are defined on the networking device by using an ASCII editor. The script is then copied to the networking device and registered with EEM.
You use EEM to write and implement your own policies using the EEM policy tool command language (TCL) script. When you configure a TCL script on the master switch and the file is automatically sent to the member switches. The user-defined TCL scripts must be available in the member switches so that if the master switch changes, the TCL scripts policies continue to work.
Cisco enhancements to TCL in the form of keyword extensions facilitate the development of EEM policies. These keywords identify the detected event, the subsequent action, utility information, counter values, and system information.
For complete information on configuring EEM policies and scripts, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Embedded Event Manager Environment Variables
EEM uses environment variables in EEM policies. These variables are defined in a EEM policy tool command language (TCL) script by running a CLI command and the event manager environment command. These environment variables can be defined in EEM:
–
Defined by the user for a user-defined policy.
–
Defined by Cisco for a specific sample policy.
–
Defined by Cisco and can be read-only or read-write. The read-only variables are set by the system before an applet starts to execute. The single read-write variable, _exit_status, allows you to set the exit status for policies triggered from synchronous events.
Cisco-defined environment variables and Cisco system-defined environment variables might apply to one specific event detector or to all event detectors. Environment variables that are user-defined or defined by Cisco in a sample policy are set by using the event manager environment global configuration command. You must defined the variables in the EEM policy before you register the policy.
For information about the environmental variables that EEM supports, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Configuring Embedded Event Manager
These sections contain this configuration information:
–
–
For complete information about configuring embedded event manager, see the Cisco IOS Network Management Configuration Guide, Release 12.4T.
Registering and Defining an Embedded Event Manager Applet
Beginning in privileged EXEC mode, perform this task to register an applet with EEM and to define the EEM applet using the event applet and action applet configuration commands.
Note
This example shows the output for EEM when one of the fields specified by an SNMP object ID crosses a defined threshold:
Switch(config-applet)# event snmp oid 1.3.6.1.4.1.9.9.48.1.1.1.6.1 get-type exact entry-op lt entry-val 5120000 poll-interval 10These examples show actions that are taken in response to an EEM event:
Switch(config-applet)# action 1.0 syslog priority critical msg "Memory exhausted; current available memory is $_snmp_oid_val bytes"Switch (config-applet)# action 2.0 force-switchoverRegistering and Defining an Embedded Event Manager TCL Script
Beginning in privileged EXEC mode, perform this task to register a TCL script with EEM and to define the TCL script and policy commands.
This example shows the sample output for the show event manager environment command:
Switch# show event manager environment allNo. Name Value1 _cron_entry 0-59/2 0-23/1 * * 0-62 _show_cmd show ver3 _syslog_pattern .*UPDOWN.*Ethernet1/0.*4 _config_cmd1 interface Ethernet1/05 _config_cmd2 no shutThis example shows a CRON timer environment variable, which is assigned by the software, to be set to every second minute, every hour of every day:
Switch (config)# event manager environment_cron_entry 0-59/2 0-23/1 * * 0-6This example shows the sample EEM policy named tm_cli_cmd.tcl registered as a system policy. The system policies are part of the Cisco IOS image. User-defined TCL scripts must first be copied to flash memory:
Switch (config)# event manager policy tm_cli_cmd.tcl type systemDisplaying Embedded Event Manager Information
To display information about EEM, including EEM registered policies and EEM history data, see the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3T.
•
Privileged EXEC
event manager scheduler clear
event manager update user policy
show event manager detector
show event manager version
Global Configuration
event manager detector rpc
event manager directory user repository
Applet Configuration (config-applet)
event rpc
event snmp-notification
trigger (EEM)
Trigger Applet Configuration (config-applet-trigger)
attribute (EEM)
correlate
Event Trigger Configuration (config-event-trigger)
event owner
Correction to the Catalyst 2960 Software Configuration Guide
Multi-domain authentication (MDA) is not supported on the Catalyst 2960 switch.
Update to the Catalyst 3750, 3560, and 2960 Command References
These are updates to the command references:
•
•
Note
•
Pair status
The status of the pair of wires on which TDR is running:
•
•
Updates to the System Message Guides
This section contains these system message guide updates:
New System Messages
These messages were added to all of the system message guides:
Error Message ACLMGR-3-INVALIDPARAM: Invalid [chars] [int] encounteredExplanation The access control list (ACL) manager has encountered an invalid parameter value. [chars] is the parameter name, and [int] is the parameter value.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the error by using the Output Interpreter. Use the Bug Toolkit to look for similar reported problems. If you still require assistance, open a case with the TAC, or contact your Cisco technical support representative, and provide the representative with the gathered information. For more information about these online tools and about contacting Cisco, see the "Error Message Traceback Reports" section.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.
Error Message PLATFORM_HCEF-3-ADJ: [chars]Explanation This message appears when an unsupported feature is configured on a switch running Cisco IOS Release 12.2(25)SE. [chars] is the error message.
Recommended Action Determine if a generic routing encapsulation (GRE) tunnel or the ip cef accounting global configuration command are configured. Only Distance Vector Multicast Routing Protocol (DVMRP) tunnels are supported. If the GRE tunnel is configured, remove the tunnel, or upgrade the switch software to a Cisco IOS release when the GRE feature is needed. If the ip cef accounting command is configured, remove it by using the no ip cef accounting global configuration command.
Note
Error Message PLATFORM_IPv6_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixExplanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ipv6 unicast retry route privileged EXEC command lists the failed prefixes.
Recommended Action No action is required.
Error Message PLATFORM_UCAST-6-PREFIX: One or more, more specific prefixes could not be programmed into TCAM and are being covered by a less specific prefixExplanation A more specific prefix could not be programmed into Ternary Content Addressable Memory (TCAM) and is covered by a less specific prefix. This could be a temporary condition. The output of the show platform ip unicast failed route privileged EXEC command lists the failed prefixes.
Recommended Action No action is required.
Error Message SPANTREE-6-PORTADD_ALL_VLANS: [chars] added to all VlansExplanation The interface has been added to all VLANs. [chars] is the added interface.
Recommended Action No action is required.
Error Message SPANTREE-6-PORTDEL_ALL_VLANS: [chars] deleted from all VlansExplanation The interface has been deleted from all VLANs. [chars] is the deleted interface.
Recommended Action No action is required.
Error Message SW_VLAN-6-VTP_DOMAIN_NAME_CHG: VTP domain name changed to [chars].Explanation The VLAN Trunking Protocol (VTP) domain name was changed through the configuration to the name specified in the message. [chars] is the changed domain name.
Recommended Action No action is required.
These messages were added to the Catalyst 3750 and 3560 system message guides:
Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.Explanation The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.
Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Error Message PLATFORM_WCCP-4-SDM_MISMATCH: WCCP requires sdm template routingExplanation The switch database management (SDM) routing template is not specified on the switch.
Recommended Action Specify the SDM routing template to be used. Enter the sdm prefer routing global configuration command, and then enter the reload privileged EXEC command to reload the switch.
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP address.
Recommended Action No action is required.
Error Message WCCP-1-CACHELOST: Web Cache [IP_address] lost.Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.
Changed System Messages
The error explanation and action has changed for these system messages:
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone.Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Recommended Action Ensure that the other ports in the bundle have the same configuration.
Error Message ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface Fa0/7:Power given, but link is not up.
Note
Explanation The inline-power-controller reported an error on an interface.
Recommended Action Enter the shutdown and no shutdown interface configuration commands on the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an electrostatic discharge (ESD) recovery mechanism.
Updates to the Catalyst 3750, 3560, 2970, and 2960 Hardware Installation Guide
Cisco Ethernet Switches are equipped with cooling mechanisms, such as fans and blowers. However, these fans and blowers can draw dust and other particles, causing contaminant buildup inside the chassis, which can result in a system malfunction.
You must install this equipment in an environment as free as possible from dust and foreign conductive material (such as metal flakes from construction activities).
These standards provide guidelines for acceptable working environments and acceptable levels of suspended particulate matter:
–
–
–
This applies to all Cisco Ethernet switches except for these compact models:
–
–
–
Update to the Regulatory Compliance and Safety Information for the Catalyst 2960 Switch
This warning applies to the Catalyst 2960 24- and 48-port switches:
Statement 266—Switch Installation Warning
Updates to the Catalyst 3750 Getting Started Guide
The Express Setup configuration windows were updated in the getting started guide. This is the complete procedure:
Running Express Setup
When you first set up the switch, you should use Express Setup to enter the initial IP information. This enables the switch to connect to local routers and the Internet. You can then access the switch through the IP address for further configuration.
To run Express Setup:
Update to the Catalyst 3750 Switch Regulatory Compliance and Safety Information
The warning was added to both the Catalyst 3750 Switch Regulatory Compliance and Safety Information for the Catalyst 3750 Switch and the Catalyst 3750 Switch Hardware Installation Guide:
Statement 377—Temperature of the Removed SFP Module Might be Hot
This warning replaces Statement 100C:
Statement 370—Attaching the Cisco RPS to the RPS Receptacle
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:
•
•
•
•
These documents provide complete information about the Catalyst 3750 switches and the Cisco EtherSwitch service modules:
•
•
•
•
•
•
•
These documents provide complete information about the Catalyst 3750G Integrated Wireless LAN Controller Switch and the integrated wireless LAN controller and are available at cisco.com:
•
•
•
•
These documents provide complete information about the Catalyst 3560 switches:
•
•
•
•
•
•
These documents provide complete information about the Catalyst 2970 switches:
•
•
•
•
•
•
These documents provide complete information about the Catalyst 2960 switches and are available on Cisco.com:
•
•
•
•
•
•
•
•
For other information about related products, see these documents:
•
•
•
•
•
•
•
•
•
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
–
–
–
–
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
This document is to be used in conjunction with the documents listed in the "Update to the Catalyst 3750 Switch Regulatory Compliance and Safety Information" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0908R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 200-2009 Cisco Systems, Inc. All rights reserved.
