 Feedback
|
Table Of Contents
Device Manager System Requirements
Finding the Software Version and Feature Set
Upgrading a Switch by Using the Device Manager or Network Assistant
Upgrading a Switch by Using the CLI
Recovering from a Software Failure
Minimum Cisco IOS Release for Major Features
Cisco Redundant Power System 2300
Cisco X2 Transceiver Modules and SFP Modules
Stacking (only Catalyst 3750-E Switch Stack)
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE5
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE4
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE
Updates to the Cisco Software Activation and Compatibility Document
Updates to the Software Configuration Guide
Updates to the Command Reference
Updates to the System Message Guide
Update to the Getting Started Guides
Obtaining Documentation and Submitting a Service Request
Release Notes for Catalyst 3750-E and Catalyst 3560-E Switches, Cisco IOS Release 12.2(50)SE and Later
Revised October 21, 2010
Cisco IOS Release 12.2(50)SE and later runs on all Catalyst 3750-E and Catalyst 3560-E switches.
The Catalyst 3750-E switches support stacking through Cisco StackWise Plus technology. The Catalyst 3560-E switches do not support switch stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
In Cisco IOS Release 12.2(50)SE1 and earlier, the Catalyst 3750-E and 3560-E switches support only the universal software images.
In Cisco IOS Release 12.2(50)SE2and later, the Catalyst 3750-E and 3560-E switches support the universal and IP base software images.
For more information, see the Deciding Which Files to Use and the "Documentation Updates" section.
These release notes include important information about Cisco IOS Release 12.2(50)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
You can download the switch software from this site (registered Cisco.com users with a login password):
http://tools.cisco.com/support/downloads/go/MDFTree.x?butype=switches
This software release is part of a special release of Cisco IOS software that is not released on the same maintenance cycle that is used for other platforms. As maintenance releases and future software releases become available, they will be posted to Cisco.com in the Cisco IOS software area.
For the complete list of Catalyst 3750-E and Catalyst 3560-E switch documentation, see the "Related Documentation" section.
Contents
This information is in the release notes:
•
•
•
•
•
•
•
System Requirements
The system requirements are described in these sections:
•
•
Hardware Supported
Table 1 lists the hardware supported on this release.
Table 1 Catalyst 3750-E and Catalyst 3560-E Switches Supported Hardware
Cisco Catalyst 3750E-24TD
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48TD
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-24PD
24 10/100/1000 PoE1 ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48PD
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3750E-48PD
Full Power48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-24TD
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48TD
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-24PD
24 10/100/1000 PoE ports, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48PD
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-48PD
Full Power48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(35)SE2
Cisco Catalyst 3560E-12D
12 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(40)EX
Cisco Catalyst 3560E-12SD
12 SFP2 module slots, 2 10-Gigabit Ethernet X2 module slots
Cisco IOS Release 12.2(44)SE
Cisco X2 transceiver modules
X2-10GB-SR V02 or later
X2-10GB-LR V03 or later
X2-10GB-ER V02 or later
X2-10GB-CX4 V03 or later
X2-10GB-LX4 V03 or later
X2-10GB-LRM
10 Gigabit Ethernet X2 ZR optical modulesCisco IOS Release 12.2(35)SE2
Cisco IOS Release 12.2(40)SE
Cisco IOS Release 12.2(50)SECisco TwinGig Converter Module
Dual SFP X2 converter module to allow the switch to support SFP Gigabit Ethernet modules
Cisco IOS Release 12.2(35)SE2
SFP modules
1000BASE-LX/LH
1000BASE-SX
1000BASE-ZX
1000BASE-BX10-D
1000BASE-BX10-U
1000BASE-T
100BASE-FX
CWDM3Cisco IOS Release 12.2(35)SE2
Cisco IOS Release 12.2(50)SEDOM4 support for these SFP modules
X2-10GB-ER, X2-10GB-SR, X2-10GB-LR, X2-10GB-LRM, X2-10GB-ZR
GLC-ZX-SM, GLC-BX-D, GLC-BX-U
SFP-GE-S, SFP-GE-L, SFP-GE-Z
All CWDM and DWDM SFP modules
Cisco IOS Release 12.2(46)SE
SFP module patch cable5
CAB-SFP-50CM
Cisco IOS Release 12.2(35)SE2
C3K-PWR-1150WAC
1150-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-750WAC
750-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-265WAC
265-W AC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-PWR-265WDC
265-W DC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-BLWR-60CFM
Fan module
Supported on all software releases
Redundant power system (RPS)
Cisco RPS 2300 RPS
Supported on all software releases
1 PoE = Power over Ethernet.
2 SFP = small form-factor pluggable
3 CWDM = coarse wavelength-division multiplexer
4 DOM = digital optical monitoring
5 Only Catalyst 3560-E switches. The SFP module patch cable is a 0.5-meter, copper, passive cable with SFP module connectors at each end. The patch cable can connect two Catalyst 3560-E switches in a cascaded configuration.
Device Manager System Requirements
These sections describe 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
These are the supported operating systems and browsers for the device manager:
•
•
The device manager verifies the browser version when starting a session, and it does not require a plug-in.
Cluster Compatibility
You cannot create and manage switch clusters through the device manager. To create and manage switch clusters, use the command-line interface (CLI) or the Network Assistant application.
When creating a switch cluster or adding a switch to a cluster, follow these guidelines:
•
•
•
For additional information about clustering, see Getting Started with Cisco Network Assistant and Release Notes for Cisco Network Assistant (not orderable but available on Cisco.com), the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
Upgrading the Switch Software
These are the procedures for downloading software. Before downloading software, read this section for important information:
•
•
•
•
•
Finding the Software Version and Feature Set
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.
Table 3 lists the filenames for this software release.
Table 3 Cisco IOS Software Image Files
Filename
c3750e-ipbase-tar.122-50.SE4.tar1
Catalyst 3750-E IP base image and device manager files. This image has Layer 2+ and basic Layer 3 routing features.
c3750e-universal-tar.122-50.SE4.tar
Catalyst 3750-E universal image and device manager files. This image has all the supported features that are enabled by the installed software license.
c3750e-ipbasek9-tar.122-50.SE4.tar1
Catalyst 3750-E IP base cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, Layer 2+, and basic Layer 3 routing features.
c3750e-universalk9-tar.122-50.SE4.tar
Catalyst 3750-E universal cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, SNMPv3, and supported universal image features.
c3560e-ipbase-tar.122-50.SE4.tar1
Catalyst 3560-E IP base image and device manager files. This image has Layer 2+ and basic Layer 3 routing features.
c3560e-universal-tar.122-50.SE4.tar
Catalyst 3560-E universal image and device manager files. This image has all the supported features that are enabled by the installed software license.
c3560e-ipbasek9-tar.122-50.SE4.tar1
Catalyst 3560-E IP base cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, Layer 2+, and basic Layer 3 routing features.
c3560e-universalk9-tar.122-50.SE4.tar
Catalyst 3560-E universal cryptographic image and device manager files. This image has the Kerberos, SSH, SSL, and SNMPv3, and supported universal image features.
1 These images are available only for Cisco IOS Release 12.2(50)SE3 and later.
The universal software images support multiple feature sets. Use the software activation feature to deploy a software license and to enable a specific feature set. For information about software activation, see the Cisco Software Activation and Compatibility Document on Cisco.com:
http://www.cisco.com/en/US/products/ps7077/products_installation_and_configuration_guides_list.html
Archiving Software Images
Before upgrading your switch software, make sure that you have archived copies of the current Cisco IOS release and the Cisco IOS release from which you are upgrading. You should keep these archived images until you have upgraded all devices in the network to the new Cisco IOS image and until you have verified that the new Cisco IOS image works properly in your network.
Cisco routinely removes old Cisco IOS versions from Cisco.com. See Product Bulletin 2863 for more information:
http://www.cisco.com/en/US/products/sw/iosswrel/ps5187/prod_bulletin0900aecd80281c0e.html
You can copy the bin software image file on the flash memory to the appropriate TFTP directory on a host by using the copy flash: tftp: privileged EXEC command.
Note
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 universal software image files for a Catalyst 3750-E switch, click Catalyst 3750-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3750-E 3DES Cryptographic Software.
To download the universal software image files for a Catalyst 3560-E switch, click Catalyst 3560-E software. To obtain authorization and to download the cryptographic software files, click Catalyst 3560-E 3DES Cryptographic Software.
Step 3
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/c3750e-universal-tar.122-50.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:
•
•
•
•
New Features
These sections describe the new supported hardware and the new and updated software features provided in this release:
•
•
New Hardware Features
For a list of all supported hardware, see the "Hardware Supported" section.
New Software Features
These are the new software features for this release:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
The advanced IP services software license is now end-of-sale (EOS) and end-of-life (EOL). For more information, see http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/eol_c51_519629.html
Minimum Cisco IOS Release for Major Features
Table 4 lists the minimum software release (after the first release) required to support the major features of the Catalyst 3750-E and Catalyst 3560-E switches. Features not listed are supported in all releases.
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-E and 3560-E switches:
•
•
•
•
•
•
Access Control List
These are the access control list (ACL) limitations:
•
There is no workaround. (CSCse33114)
•
The workaround is to block traffic from the specific MAC address by using the mac address-table static mac-addr vlan vlan-id drop global configuration command. (CSCse73823)
Address Resolution Protocol
This is an Address Resolution Protocol limitation:
•
The workaround is to set the burst interval to more than 1 second. We recommend setting the burst interval to 3 seconds even if you are not experiencing this problem.(CSCse06827))
Cisco Redundant Power System 2300
This is the Cisco Redundant Power System (RPS) 2300 limitation:
•
PLATFORM_ENV-1-RPS_ACCESS: RPS is not respondingNo workaround is required because the problem corrects itself. (CSCsf15170)
Cisco X2 Transceiver Modules and SFP Modules
These are the Cisco X2 transceiver module and SFP module limitations:
•
•
•
•
–
–
–
•
•
Configuration
These are the configuration limitations:
•
There is no workaround. (CSCec74610) (Catalyst 3750-E switches)
•
PLATFORM_RPC-3-MSG_THROTTLED: RPC Msg Dropped by throttle mechanism: type 0, class 51, max_msg 128, total throttled 984323
-Traceback= 6625EC 5DB4C0 5DAA98 55CA80 A2F2E0 A268D8No workaround is necessary. Under normal conditions, the switch generates this notification when snooping the next ARP packet. (CSCse47548)
•
The workaround is to not configure VLANs with protected ports as part of a fallback bridge group. (CSCsg40322)
When a switch port configuration is set at 10 Mb/s half duplex, sometimes the port does not send in one direction until the port traffic is stopped and then restarted. You can detect the condition by using the show controller ethernet-controller or the show interfaces privileged EXEC commands.
The workaround is to stop the traffic in the direction in which it is not being forwarded, and then restart it after 2 seconds. You can also use the shutdown interface configuration command followed by the no shutdown command on the interface. (CSCsh04301)
•
The workaround is to enter the switchport access vlan dynamic interface configuration command separately on each port.(CSCsi26392)
•
The workaround is to use the session stack-member-number privileged EXEC command. (CSCsz38090) (Catalyst 3750-E switches)
EtherChannel
These are the EtherChannel limitations:
•
–
–
The EtherChannel ports are put in the suspended state because each partitioned stack sends LACP packets with different LACP Link Aggregation IDs (the system IDs are different). The ports that receive the packets detect the incompatibility and shut down some of the ports. Use one of these workarounds for ports in this error-disabled state:
–
–
The EtherChannel ports are put in the error-disabled state because the switches in the partitioned stacks send STP BPDUs. The switch or stack at the other end of the EtherChannel receiving the multiple BPDUs with different source MAC addresses detects an EtherChannel misconfiguration.
After the partitioned stacks merge, ports in the suspended state should automatically recover. (CSCse33842)
•
No workaround is necessary. The problem corrects itself after the link-up or link-down event. (CSCse75508)
•
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 879A58There is no workaround. (CSCsh12472)
IEEE 802.1x Authentication
These are the IEEE 802.1x authentication limitations:
•
Use one of these workarounds (CSCsd90495):
–
–
•
–
–
Use one of these workarounds (CSCse04534):
–
–
•
The workaround is not use the VLAN assignment option. (CSCse22791)
Multicasting
These are the multicasting limitations:
•
–
–
–
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
•
–
–
–
There is no workaround. (CSCei08359)
•
The workaround is to not send RPF-failed multicast traffic, or make sure that the source IP address of the RPF-failed packet is reachable. (CSCsd28944)
•
There is no workaround. (CSCsd45753)
•
•
–
–
–
The workaround is to disable the IGMP snooping throttle limit by using the no ip igmp max-groups number interface configuration command and then to reconfigure the same limit again. (CSCse39909)
PoE
These are the power-over-Ethernet (PoE) limitations:
•
•
The workaround is to enable PoE and to configure the switch to recover from the PoE error-disabled state. (CSCsf32300)
•
There is no workaround. (CSCsg20629)
QoS
These are the quality of service (QoS) limitations:
•
There is no workaround. (CSCeh18677)
•
There is no workaround. (CSCsc63334)
•
The workaround is to use a different name for the interface-level policy map. (CSCsd84001)
•
There is no workaround. (CSCsd72001)
•
•
Use one of these workarounds:
–
–
Routing
These are the routing limitations:
•
–
–
The workaround is to reduce the number of OSPF neighbors to 200 or less. (CSCse65252)
•
The workaround is to not send traffic to unknown destinations. (CSCse97660)
SPAN and RSPAN
This is the SPAN and Remote SPAN (RSPAN) limitation.
•
There is no workaround. This is a hardware limitation. (CSCei10129)
•
The workaround is to configure aggressive UDLD. (CSCsh70244).
VLANs
These are the VLAN limitations:
•
The workaround is to enter the shut and no shut interface configuration commands on the port to reset the authentication status. (CSCsf98557)
•
–
–
–
You can use one of these workarounds:
–
–
•
The workaround is to always enter a non zero value for the timeout value when you enter the boot host retry timeout timeout-value command. (CSCsk65142)
Stacking (only Catalyst 3750-E Switch Stack)
These are the Catalyst 3750-E switch stack limitations:
•
unable to read configmessage appears.The workaround is to wait a few seconds and then to reenter the write memory privileged EXEC command. (CSCsd66272)
•
The workaround is to use the logging monitor global configuration command to set the severity level to block the low-level messages on the stack member consoles. (CSCsd79037)
•
The workaround is to avoid traffic congestion on the stack ring. (CSCsd87538)
•
The workaround is to reboot the new member switch. Use the remote command all show run privileged EXEC command to compare the running configurations of the stack members. (CSCsf31301)
•
The workaround is to delete files in the flash memory to create more free space. (CSCsg30073)
•
The workaround is to check the flash. If it contains many files, remove the unnecessary ones. Check the lost and found directory in flash and if there are many files, delete them. To check the number of files use the fsck flash: command. (CSCsi69447)
•
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state. (CSCsl64124)
Device Manager Limitations
This is the device manager limitation:
•
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Important Notes
These sections describe the important notes related to this software release for the Catalyst 3750-E and 3560-E switches:
•
Switch Stack Notes
These notes apply to switch stacks:
•
•
•
Cisco IOS Notes
These notes apply to Cisco IOS software:
•
00:02:57: %RADIUS-4-RADIUS_DEAD: RADIUS server 172.20.246.206:1645,1646 is not responding.If this message appears, make sure that there is network connectivity between the switch and the ACS. You should also make sure that the switch has been properly configured as an AAA client on the ACS.
•
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.
•
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:
The device manager uses the HTTP protocol (the default is port 80) and the default method of authentication (the enable password) to communicate with the switch through any of its Ethernet ports and to allow switch management from a standard web browser.
If you change the HTTP port, you must include the new port number when you enter the IP address in the browser Location or Address field (for example, http://10.1.126.45:184 where 184 is the new HTTP port number). You should write down the port number through which you are connected. Use care when changing the switch IP information.
•
Open Caveats
This section describes the open caveats with possible unexpected activity in this software release. Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to the Catalyst 3750-E and 3560-E switches:
•
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 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
upand sometimes asdown, resulting in conflicts. This status depends on when you respond to the reboot query:
Would you like to enter the initial configuration dialog?–
down. This is the correct state.–
up) occurs if you respond to the query before VLAN 1 line status appears on the console.The workaround is to wait for approximately 1 minute after rebooting and until the VLAN 1 interface line status appears on the console before you respond to the query.
•
When you use the ipv6 address dhcp interface configuration command on an interface that is configured in router mode, other addresses on the prefix associated with the new address might not be accessible.
The workaround is to use the ipv6 address dhcp interface configuration command on an interface that is configured in host mode, or configure a static route to the prefix through the interface.
•
On switches running Cisco IOS Release 12.2(44)SE or 12.2(46)SE, when you enter the show mvr interface interface-id members privileged EXEC command to see status of an MVR port, an MVR member port that is not connected always shows as ACTIVE.
The workaround is to use the show mvr interface interface-id or the show mvr members privileged EXEC command. These command outputs show the correct status of an MVR port.
•
The show mvr members privileged EXEC command output does not include STATIC INACTIVE members. When a static port becomes ACTIVE, it appears in the output as expected.
There is no workaround.
•
When you enter the mvr vlan vlan-id global configuration command to create an MVR VLAN and enable MVR on the switch by entering the mvr global configuration command, if you enter the show mvr interface interface-id members privileged EXEC command, the output shows the MVR groups on the interface. However, if you enable MVR first and then create the MVR VLAN, the MVR groups are not displayed correctly.
The workaround, if the groups are not displaying correctly, is to create the MVR VLAN before enabling MVR. The configuration then displays correctly.
•
A switch running Cisco IOS Release 12.2(46)SE might lose packets for up to 30 seconds when a link fails. This occurs in some multiple spanning-tree (MST) topologies.
There is no workaround.
•
When software is reloaded on a switch stack master that has port security enabled, the switch stack might crash.
There is no workaround.
•
When a port is configured for single host mode, and the re-authentication timer value is less than 100, if the access control server (ACS) is configured with a per-user access control list (ACL), multiple changes to the stack master might cause the display of empty access-lists for the port.
The workaround is to enter a shutdown and then a no shutdown interface configuration command on the interface.
•
If the switch stack software is reloaded while the ACS is unreachable, a port configured with a critical VLAN might become error disabled, and a message similar to the one shown below appears on the switch console:
*Mar 3 01:10:13.423: %PM-4-ERR_DISABLE_VP: security-violation error detected on Fa8/0/7, vlan 3000.The workaround is to enter a shutdown and then a no shutdown interface configuration command on the interface.
•
After a PC connected to a switch in a stack is awakened by a Wake-on-LAN packet and authorized by MAC authentication bypass, a traceback message appears indicating a VLAN error.
No workaround is necessary because the message does not affect switch functionality.
•
Following a stack reload, a port that is configured for single-host mode and is connected to a PC and an IP phone becomes error-disabled on the access VLAN.
There is no workaround.
•
When EnergyWise is enabled and you reload member switches while leaving the stack master up, you might see a console traceback message similar to this:
Feb 12 22:08:45: %INTERFACE_API-3-NOADDSUBBLOCK: The HWIDB subblock named ENERGYWISE was not added to GigabitEthernet4/0/49-Traceback= F943C8 F94B14 344E08 17D97E0 668798 A736B0 A73FB8 A743C8 BBAC28 BB16F8.This message is benign and does not cause any issues other than traceback.
No workaround is required because the message does not affect functionality, but you can avoid console messages by reloading the master switch as well as the member switches.
•
When a switch stack is running 802.1x single host mode authentication and has filter-ID or per-user policy maps applied to an interface, these policies are removed if a master switchover occurs. Even though the output from the show ip access-list privileged EXEC command includes these ACLs, the policies are not applied.
The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface.
•
When an interface on the stack master is a member of an EtherChannel and the channel group number is removed before a master switch changeover, you can not use the same group number when you recreate the EtherChannel after the changeover.
These are possible workarounds:
–
–
–
•
The switch unexpectedly reloads when copying a configuration file from a remote server or from flash memory containing logging file flash:
The workaround is to enter the logging file flash:filename global configuration command to configure logging to flash instead of copying to flash.
•
When EnergyWise Phase 1 is enabled on a switch that has unconnected interfaces, a memory leak might occur over several days. To verify this, use the show process memory sorted holding | i energy wise privileged EXEC command.
The workaround is to disable EnergyWise on the switch.
•
When periodic port-based reauthentication is enabled and a new stack master is elected, the stack does not reauthenticate a connected client.
The workaround is to enter the dot1x re-authenticate interface interface-id privileged EXEC command to reauthenticate the client.
•
When a redirect URL is configured for a client on the authentication server and a large number of clients are authenticated, high CPU usage could occur on the switch.
There is no workaround.
Resolved Caveats
•
•
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE5
•
A vulnerability in the Internet Group Management Protocol (IGMP) version 3 implementation of Cisco IOS Software and Cisco IOS XE Software allows a remote unauthenticated attacker to cause a reload of an affected device. Repeated attempts to exploit this vulnerability could result in a sustained denial of service (DoS) condition. Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100922-igmp.shtml.
Note: The September 22, 2010, Cisco IOS Software Security Advisory bundled publication includes six Cisco Security Advisories. Five of the advisories address vulnerabilities in Cisco IOS Software, and one advisory addresses vulnerabilities in Cisco Unified Communications Manager. Each advisory lists the releases that correct the vulnerability or vulnerabilities detailed in the advisory. The table at the following URL lists releases that correct all Cisco IOS Software vulnerabilities that have been published on September 22, 2010, or earlier:
http://www.cisco.com/warp/public/707/cisco-sa-20100922-bundle.shtml
Individual publication links are in "Cisco Event Response: Semiannual Cisco IOS Software Security Advisory Bundled Publication" at the following link:
http://www.cisco.com/web/about/security/intelligence/Cisco_ERP_sep10.html
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE4
•
Authentication, authorization, and accounting (AAA) fails, preventing authentication and requiring you to recover your password. For example, when you enter the aaa authentication login default group tacacs line global configuration command, AAA fails.
There is no workaround.
•
When you use an access control server (ACS) to enable command authorization, the ACS does not process a copy command ending with a colon (for example, scp:, ftp:, tftp:, flash:).
This problem affects authentication, authorization, and accounting (AAA) authorization:
–
–
To workaround is to either deny or permit the copy command without entering any arguments on the ACS.
•
The CISCO-RTTMON-MIB is not correctly implemented in this release.
There is no workaround.
•
After you have entered the snmp-server ifindex persist global configuration command on a stacked Catalyst 3750 switch that is running Cisco IOS Release 12.2.(50)SE, the switch fails and sends this error message:
platform assert failure: hwidb->snmp_if_index == ifIndex: ../src-hulc/src-common/hpm_idbman.c: 1772: hpm_register_idb_with_snmp (Switch-4)
-Traceback=There is no workaround. A Catalyst 3750 switch that is running Cisco IOS Release 12.2.(50)SE does not support the snmp-server ifindex persist global configuration command.
•
On a switch that is configured for quality of service (QoS), a memory leak occurs when a small portion (about 90 bytes) of the processor memory is not released by the HRPC QoS request handler process.
There is no workaround.
•
When an RPS 2300 redundant power supply is connected to a Catalyst3750-E or 3560-E switch and the switch boots up, these messages might appear:
00:01:08: %PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL: RPS power supply A temperature has reached critical threshold
00:01:08: %PLATFORM_ENV-1-RPS_PS_THERMAL_CRITICAL: RPS power supply B temperature has reached critical thresholdThe root cause of the problem is that when a switch connected to the RPS 2300 is powered up, voltage changes on the switch to RPS communication bus could cause the RPS to erroneously accept commands as data to be written, which corrupts internal data and causes false alarms.
The workaround is to reset the RPS by entering this command sequence:
Switch# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Switch(config)# service internal
Switch(config)# end
Switch# test rps reset
Are you sure you want to reset the system? [yes/no]: yes
Switch# configure terminal
Switch(config)# no service internal
•
Packet loss and output drops occur on the egress interface for routed multicast traffic.
This problem occurs when multiple S,G entries time out at the same time and then are re-established at the same time, when multiple Protocol Independent Multicast (PIM) neighbors time out at the same time and then are re-established at the same time, or when multiple high-volume multicast streams are routed through multiple Layer-3 interfaces.
Use one of these workarounds:
–
–
•
When you use Auto Smartports macros on an interface that is connected to an Cisco IP phone, the the quality of service (QoS) configuration for that interface is not completed.
The workaround is to enter the no mls qos vlan-based interface configuration command, and then enable QoS for voice over IP (VoIP) by entering the auto qos voip cisco-phone interface configuration command.
•
When two switch stacks are connected, when the stack master fails, and when another switch becomes the stack master, convergence is delayed under these conditions:
–
–
–
The workaround is to not use the EtherChannel LACP mode. Use the EtherChannel on mode to force ports to join an EtherChannel without negotiations.
•
A switch can fail when an SNMP process attempts to configure dot1x authentication when it is already configured.
There is no workaround.
•
When a switch stack is configured with DHCP snooping enabled on the host VLAN, hosts connected to the stack master receive bootp packets, but the a packet might not be forwarded to the end hosts connected to stack member switches. The behavior depends on which interface in the stack received the packet.
The workaround is to disable DHCP snooping for the affected VLAN.
•
After you have entered the authentication control-direction in interface configuration command on an authenticator switch port, authentication is successful and the port is in the authorized state. However, another switch that functions as the supplicant cannot pass any traffic over the trunk except for traffic on the native VLAN.
The workaround is to enter the no authentication control-direction interface configuration command on the authenticator port, and then enter the shutdown interface configuration command followed by the no shutdown interface configuration command to trigger a new authentication.
•
After you have entered the authentication host-mode multi-auth interface configuration command and have changed the access VLAN, MAC authentication bypass (MAB) does not work and authentication fails.
The workaround is to enter the shutdown interface configuration command followed by the no shutdown interface configuration command.
•
When the system memory is low, a watchdog timeout occurs, and the switch fails.
The workaround is to enter the show memory privileged EXEC command or show processes memory privileged EXEC command and stop any memory leaks.
•
When you use IEEE 802.1x authentication with web authentication and an HTTP page opens, the switch redirects the user to an HTTP login page, not a HTTPS login page.
The workaround is to remove the custom banner.
•
In a switch stack, when the SNMP vlan change (vmMembershipEntry) MIB is sent to a member switch other than the stack master, line protocol and notification flapping occurs.
There is no workaround.
•
A switch enters a loop in which it continues to fail after it first has failed while starting, and then has failed again while attempting to recover. This failure loop occurs only after you have entered the archive upload-sw privileged EXEC command to write the configuration to a remote server using Secure Copy Protocol (SCP) and when the connection to the remote server is configured for spanning-tree PortFast.
The workaround is to not use SCP to write to the remote server. Use File Transfer Protocol (FTP) or Trivial File Transfer Protocol (TFTP).
•
A memory leak occurs when there is a stuck in active (SIA) state condition for an Enhanced Interior Gateway Routing Protocol (EIGRP) route.
There is no workaround.
•
A switch does not receive SNMP trap and inform messages from the correct interface after you have entered the snmp-server trap-source loopback0 and snmp-server source-interface informs loopback0 global configuration commands.
There is no workaround.
•
When the no mac address-table static mac-addr vlan vlan-id interface interface-id global configuration command is used to remove a dynamically learned MAC address, the switch fails under these conditions:
–
–
There is no workaround.
•
When you have configured an output service policy, performing an SNMPWALK on cportQosStatistics causes loops.
There is no workaround.
•
Traffic received on a member interface of a cross-stack EtherChannel is dropped from a switch stack. This intermittently occurred in previous releases after a stack reloaded.
There is no workaround.
•
After all member ports are brought up on a switch stack, MAC authentication bypass (MAB) authenticates the stack master ports but not any member switch ports. The symptom occurs after you have entered both the switchport port-security interface configuration command and the dot1x control-direction interface configuration command on the stack interfaces.
The workaround is to enter either the no switchport port-security interface configuration command or the no dot1x control-direction interface configuration command on the stack interfaces.
•
A memory leak occurs on a device that uses Enhanced Interior Gateway Routing Protocol (EIGRP) when the external routes are being exchanged.
The workaround is to stabilize the network to minimize the impact of external route advertisement.
•
When you enter the dot1x pae interface configuration command on a switch access port and then enable an access list in the inbound direction on an ingress switched virtual interface (SVI), the access list does not work, allowing all packets to pass.
The workaround is to enable the access list in the outbound direction on the egress SVI.
•
When you enter the no spanning-tree etherchannel guard misconfig global configuration command, enter the write memory privileged EXEC command, and then restart the switch, the spanning-tree etherchannel guard misconfig global configuration command is saved instead of the no form of this command.
There is no workaround.
•
An IP phone loses network connectivity under these conditions:
–
–
A call is placed using the IP phone. After approximately 5 minutes, network connectivity to the phone is lost.
The workaround is to statically configure the MAC address of the IP phone on the authenticator switch.
•
After you have entered the snmp-server host informs global configuration command to enable SNMP informs on a switch, the switch might fail if you enter the show snmp pending user EXEC command.
There is no workaround. Do not enter the show command when SNMP informs are enabled.
•
A Remote Switched Port Analyzer (RSPAN) does not detect IPv6 multicast packets on an RSPAN destination port.
There is no workaround.
•
A switch fails when you enter the show ip ospf interface user EXEC command and then stop the command output at the this line:
Backup Designated router (ID) xx.x.x.x, Interface address xx.x.x.xThe failure occurs when the Backup Designated Router (BDR) neighbor of the switch is shut down while you press Enter or the spacebar to advance the command output.
When the switch fails, it sends this error message:
Unexpected exception to CPUvector 2000, PC = 261FC60There is no workaround.
•
On a switch that has one port configured as a Switched Port Analyzer (SPAN) source port, a memory leak occurs when a Power-over-Ethernet (PoE) port link goes up and down.
There is no workaround.
•
On a switch that is configured for IP routing and that is running Cisco IOS Release 12.2(50)SE or later, Cisco Express Forwarding (CEF) can use a large amount of memory. The IP RIB Update process uses about 2000 bytes for each prefix that CEF uses.
There is no workaround. You can reduce the memory use by reducing the number of routes the switch processes.
•
After you have entered the logging filter global configuration command on a switch to specify a syslog filter module to be used by the Embedded Syslog Manager (ESM), processes logging many system messages retain increasing amounts of processor memory.
The workaround is to enter the no logging filter global configuration command.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE3
•
Memory allocation errors no longer occur when the Cisco Express Forwarding (CEF) consistency checkers have been enabled. The CEF consistency checkers have been enabled by default. They can also be enabled by using these global configuration commands:
cef table consistency-check ipv4
cef table consistency-check ipv6
•
A switch no longer fails when you enter the configure replace privileged EXEC command, and a banner is already present in the switch configuration.
•
You can now query the bgpPeerTable MIB for VPN/VRF interfaces.
•
Cisco IOS Software contains a vulnerability that could allow an attacker to cause a Cisco IOS device to reload by remotely sending a crafted encryption packet. Cisco has released free software updates that address this vulnerability. This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tls.shtml.
•
The output of the show ip ssh privileged EXEC command no longer displays SSH Enabled - version 2.99. Instead, a correct SSH version (1.5, 1.99 or 2.0) now appears.
•
A switch no longer fails when a host moves from a dynamically assigned VLAN to a configured VLAN.
•
A switch configured with 802.1x and port security on the same ports no longer might inappropriately put the ports into an error-disabled state.
•
Moving a PC between two IP Phones without disconnecting either phone from the switch no longer triggers a port-security violation.
•
A port security violation error no longer occurs when MAC address sticky learning is enabled on a port and a CDP is enabled on a connected IP Phone.
•
A Telnet, Secure Shell (SSH), or console session on the switch no longer fails when you use the show file systems EXEC command or when you access the remote file system, flashn: (where n is the switch number).
•
Third-party IP phones now automatically power up when reconnected to enabled PoE ports on the switch.
•
If a large number of clients in a switch stack use MAC authentication bypass to authenticate at the same time, the clients are no longer in the unauthorized state when
–
–
–
–
•
Re-authentication now occurs on a port under these conditions:
–
–
–
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Cisco IOS devices that are configured for Internet Key Exchange (IKE) protocol and certificate based authentication are vulnerable to a resource exhaustion attack. Successful exploitation of this vulnerability may result in the allocation of all available Phase 1 security associations (SA) and prevent the establishment of new IPsec sessions.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml
•
Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent webpage.
There are no workarounds that mitigate this vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml
•
The switch now changes the time in an EnergyWise recurrence event when the local time changes to daylight saving time.
•
The switch no longer fails when you use the vacant-message line configuration command.
•
When IEEE 802.1x multiple authentication mode is configured on a port, two PCs have been authenticated, and the first PC is disconnected, the second PC now receives and forwards traffic on the port.
•
If a link failure occurs on a secondary edge port, preemption now occurs after the link comes up.
•
A switch running Cisco IOS Release 12.2(50)SE or later no longer might unexpectedly restart when Auto Smart Ports is enabled and the switch is configured for SSH or the HTTP secure server is enabled by entering the ip http secure-server global configuration command.
•
For Catalyst 3750-E and 3560-E switches and power supplies, the show env all command output no longer shows Failure-Fan after you upgrade your software from Cisco IOS Release 12.2(46)SE to Cisco IOS Release 12.2(50)SE3.
•
When open1x authentication and MAC authentication bypass are enabled on a port, an IP phone is connected to the port, and DHCP snooping is enabled on the switch, DHCP traffic is now forwarded on the voice VLAN before open 1x authentication times out and the switch uses MAC authentication bypass to authorize the port.
•
The switch no longer reloads when you enter several key strokes while in interface-range configuration mode.
•
If MAC authentication bypass is enabled and the RADIUS server is not available, the switch now tries to re-authenticate a port after a server becomes available.
•
When VPN routing and forwarding (VRF) is configured on the stack master, communication no longer fails after the stack master has shut down.
•
A memory leak no longer occurs when Cisco Network Assistant is polling the switch and the ip http server or ip http-secure-server global configuration command is enabled.
•
If you are configuring Flexible Authentication Ordering with web authentication on a switch port and the switch uses 802.1x to authenticate the host, Address Resolution Protocol (ARP) now works properly.
•
A trunk port no longer goes into the error-disabled state when the trunk port's native VLAN is in a suspended state or is not configured on the switch itself.
•
The Layer 2 Protocol Tunneling (L2PT) drop-threshold protocol no longer continues to drop traffic after it is removed from the switch configuration.
•
If you enable automatic server testing through the radius-server host ip-address [test username name] global configuration command, the switch no longer sends requests to the RADIUS server if the server is not available.
•
SNMP queries to the Bridge-MIB now operate on switch stacks with five or more stack members and a large number of active ports.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE1
•
If the connection to a primary AAA server fails, the backup server is now queried for login access.
•
When a TCP packet with all flags set to zero (at the TCP level) is sent to a remote router, the remote (destination) router no longer returns an ACK/RST packet back to the source of the TCP segment.
•
The switch now accepts an encrypted secret password.
•
The switch no longer runs out of memory when an smnpwalk, snmpget, or snmpbulkwalk is run on the CISCO-ENERGYWISE-MIB.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(50)SE
•
When loopback interfaces are configured, this error message no longer appears when a stack member is loading:
%COMMON_FIB-3-FIBIDBINCONS2•
When STP is disabled on the stack, the Hot Standby Router Protocol (HSRP) hello packets now pass through the switch stack when the stack is connected to two routers through cross-stack EtherChannels.
•
The server no longer attempts re-authentication every ten minutes when a switch is configured with the dot1x timeout reauth-period server interface configuration command.
•
The following message no longer appears when configuring an access list with large logical operation units (LOUs):
*Mar 1 00:10:29.296 UTC: %ACLMGR-2-NOVMR: Cannot create VMR data structures for accesslist aclvlan42outAdditionally tracebacks are no longer seen when applying some ACLs.
•
Traffic is now forwarded to the interfaces that are configured with static multicast MAC addresses after the switch is reloaded.
Note
•
If the switch uses 802.1x authentication with VLAN assignment, it no longer uses the VLAN assignment with different authorization attempts, such as user authentication or re-authentication.
•
When keepalive is disabled on an interface, the interface is no longer put in an error-disabled state when it receives keepalive packets.
•
The Switched Port Analyzer (SPAN) destination port no longer detects IPv6 multicast packets from a VLAN that is not being monitored by SPAN.
•
This message no longer appears in the log during the system bootup on a switch that is running
Cisco IOS 12.2(50)SE:%COMMON_FIB-3-FIBIDBINCONS2•
A switch stack is connected to Switch 1 and Switch 1 in the spanning-tree topology:
–
Switch 1 is the root bridge.
Port 1/0/1 is in the forwarding state.
–
Port 3/0/1 is in the blocking state.
If you enter the stack-mac persistent timer 5 global configuration command to set the time period to 5 minutes before the stack MAC address changes to that of the new stack master and then power off Switch 1, port 3/0/1 no longer takes 5 minutes to move from the blocking state to the forwarding state.
•
When SFP ports are configured as status multicast router ports, IPv6 Multicast Listener Discovery (MLD) snooping now works after the switch reloads.
•
The Set TxPortFifo SRR Failed message no longer appears when you enter both the srr-queue bandwidth shape 200 0 2 200 and the priority-queue out interface configuration commands on the same interface.
•
The switch no longer reloads when the Forwarding Information Base (FIB) adjacency table is added.
•
A DHCP client connected to 10 Gigabit ports 0/5-9 or Gigabit Ethernet ports 0/9-16 on a Catalyst 3650 switch model WS-C3560-12D can now get an IP address when DHCP snooping is enabled on both the switch and the client VLAN.
•
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.
•
If a TwinGig Converter Module is removed from the switch, the link state of unconnected X2 ports that belong to the same port ASIC no longer are reported as Up.
•
After upgrading the switch software from IOS Release 12.2(25) SED1 to IOS Release 12.2(25) SEE4, you can now ping a switch virtual interface (SVI) from an isolated VLAN.
•
A Cisco IP Phone connected to a Catalyst switch no longer becomes unauthorized when it transitions from the data authorization domain to the voice authorization domain.
•
A switch running SNMP no longer fails after a reload when interface fa0 is assigned a DHCP address.
•
A switch port configured for IGMP snooping no longer loses its group membership when the port receives a query comes from an upstream device that is not configured for IGMP snooping.
•
A switch configured with class-based policies that are applied and active on at least one interface no longer might reload or display CPU hog messages during SNMP polling for the ciscoCBQosMIB.
•
When you have entered the vlan dot1q tag native global configuration command to configure a switch to tag native VLAN frames on 802.1Q trunk ports, and you configure a new voice VLAN on an access port, the MAC address of a connected PC is now correctly relearned.
•
You no longer see this message on a stack when spanning-tree loopguard is globally enabled: %SPANTREE-2-LOOPGUARD_BLOCK: Loop guard blocking port StackPort1 on VLAN0001.
•
When monitoring a 10 Gb/s interface or a port channel with a 10 Gb/s interface, the SNMP counters ifHCInOctets and ifHCOutOctets no longer randomly increase by a large amount.
•
When a switch virtual interface (SVI) is configured as unnumbered and is pointing to a loopback interface, the switch no longer fails when the SVI receives a packet.
•
When LLDP is enabled and a voice VLAN is configured, the L2 Priority and DSCP Value fields in the LLDP type, length, and value descriptions (TLVs) are now correctly marked to give the voice traffic the correct DSCP and Layer 2 priority.
•
Switch ports no longer attempt authentication at the interval configured for the port security timer instead of the configured IEEE 802.1x timer.
•
The switch now performs unequal-cost load balancing.
•
When the master switch in a Catalyst 3750 switch stack initiates an auto-copy process to automatically upgrade member switch images, the upgrade now succeeds when a member switch is in a version mismatch state.
Documentation Updates
These sections provide updates to the product documentation:
•
•
•
•
Updates to the Cisco Software Activation and Compatibility Document
In Cisco IOS Release 12.2(50)SE1 and earlier, the Catalyst 3750-E and 3560-E switches support only the universal software images.
In Cisco IOS Release 12.2(50)SE2 or later, the Catalyst 3750-E and 3560-E switches support the universal and IP base software images.
•
•
Updates to the Software Configuration Guide
•
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
In the "Configuring Interface Characteristics" chapter.
•
Note
•
In the "Show Commands for Interfaces" table, the purpose of the show env rps privileged EXEC command is to display whether a redundant power system (RPS) is connected to the switch as follows:
–
–
–
Updates to the Command Reference
debug authentication
Use the debug authentication privileged EXEC command to enable debugging of the authentication settings on an interface. Use the no form of this command to disable debugging.
debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
no debug authentication {all | errors | events | sync | feature [all] [acct] [auth_fail_vlan] [auth_policy] [autocfg] [critical] [dhcp] [guest_vlan] [mab_pm] [mda] [multi_auth] [switch_pm] [switch_sync] [vlan_assign] [voice] [webauth] [all | errors | events]}
Syntax Description
Defaults
Authentication debugging is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The undebug authentication command is the same as the no debug authentication command.
On stacking switches, when you enable debugging, it is enabled only on the stack master.
To enable debugging on a stack member, you can start a session from the stack master by using the session switch-number privileged EXEC command and then entering the debug authentication command at the command-line prompt of the stack member. You also can use the remote command stack-member-number line privileged EXEC command on the stack master switch to enable debugging on a stack member.
Related Commands
Updates to the System Message Guide
This section contains the system message guide updates.
New System Messages
These messages were added to the system message guide:
Error Message ACLMGR-2-NOVMR: Cannot generate hardware representation of access list [chars]Explanation There are insufficient resources available to create a hardware representation of the ACL. A lack of available logical operation units or specialized hardware resources can cause this problem. Logical operation units are needed for a TCP flag match or a test other than eq (ne, gt, lt, or range) on TCP, UDP, or SCTP port numbers.
Recommended Action Modify the ACL configuration to use fewer resources, or rename the ACL with a name or number that alphanumerically precedes the other ACL names or numbers.
Error Message ACLMGR-4-UNLOADINGFSPAN Unloading[chars]session[dec][chars]featureExplanation The access control list (ACL) manager is unable to store the flow-based SPAN (FSPAN) configuration, and this feature has been temporarily disabled for the specified session. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.
Recommended Action Specify an SDM template that allocates more system resources for ACLs, simplify the ACL, or use the same ACLs on multiple interfaces.
Error Message ACLMGR-4-RELOADEDFSPAN Reloading [chars] session [dec] [chars] featureExplanation The access control list (ACL) manager can store the flow-based SPAN configuration for the specified session. One or more ACLs had previously been unloaded because of lack of hardware memory. The first [chars] is the type of FSPAN session: either vlan-based FSPAN for a VLAN FSPAN session or port-based FSPAN for a port FSPAN session. [dec] is the session number, and the second [chars] is the type of traffic being filtered: MAC, IPv4, or IPv6.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars]Explanation The client MAC address could not be added to the MAC address table because the hardware memory is full or the address is a secure address on another port. [enet] is the supplicant MAC address, and [chars] is the interface. This message might appear if the IEEE 802.1x feature is enabled.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, manually remove it from that port.
Error Message EC-5-CANNOT_BUNDLE1: Port-channel [chars] is down, port [chars] will remain stand-alone.Explanation The aggregation port is down. The port remains standalone until the aggregation port is up. The first [chars] is the EtherChannel. The second [chars] is the port number.
Recommended Action Ensure that the other ports in the bundle have the same configuration]
Error Message ILPOWER-3-CONTROLLER_PORT_ERR:Controller port error, Interface Fa0/7:Power given, but link is not up.Explanation The inline-power-controller reported an error on an interface.
Recommended Action Enter the shutdown and no shutdown interface configuration commands on the affected interfaces. Upgrade to Cisco IOS Release12.1(14)EA1 or later, which provides an electrostatic discharge (ESD) recovery mechanism.
Error Message %PAGP_DUAL_ACTIVE-3-OBJECT_CREATE_FAILED: Unable to create [chars]Explanation The switch cannot create the specified managed object. [chars] is the object name.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-RECOVERY_TRIGGER: PAgP running on [chars] informing virtual switches of dual-active: new active id [enet], old id [enet]Explanation Port Aggregation Protocol (PAgP) received a new active ID on the specified interface, which means that all virtual switches are in a dual-active scenario. The interface is informing virtual switches of this, which causes one switch to go into recovery mode. [chars] is the interface. The first [enet] is the new active ID. The second [enet] is the ID that it replaces.
Recommended Action No action is required.
Error Message %PAGP_DUAL_ACTIVE-3-REGISTRY_ADD_ERR: Failure in adding to [chars] registryExplanation The switch could not add a function to the registry. [chars] is the registry name.
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 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_SPAN-3-FEATUREMISMATCH:[chars] cannot be supported with the image running on switch [dec].Explanation A switch stack member software image does not support a specific flow-based SPAN (FSPAN) access control list (ACL) filter. [chars] is the FSPAN ACL filter that is not supported, and [dec] is the stack member number.
Recommended Action Upgrade to an image that supports the FSPAN ACL filter.
Error Message %PM-6-EXT_VLAN_ADDITION: Extended VLAN is not allowed to be configured in VTP CLIENT mode.Explanation The switch did not add a VLAN in VTP client mode.
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 in the system message guides.
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.
Error Message VQPCLIENT-2-TOOMANY: Interface [chars] shutdown by active host limit.Explanation The system has shut down the specified interface because too many hosts have requested access to that interface. [chars] is the interface name.
Recommended Action To enable the interface, remove the excess hosts, and enter the no shutdown interface configuration command.
Error Message VQPCLIENT-3-VLANNAME: Invalid VLAN [chars] in response.Explanation The VLAN membership policy server (VMPS) has specified a VLAN name that is unknown to the switch. [chars] is the VLAN name.
Recommended Action Ensure that the VLAN exists on the switch. Verify the VMPS configuration by entering the show vmps privileged EXEC command.
Error Message WCCP-5-CACHEFOUND: Web Cache [IP_address] acquired.Explanation The switch has acquired the specified web cache. [IP_address] is the web cache IP address.
Recommended Action No action is required.
Error Message WCCP-1-CACHELOST: Web Cache [IP_address] lost.Explanation The switch has lost contact with the specified web cache. [IP_address] is the web cache IP address.
Recommended Action Verify the operation of the web cache by entering the show ip wccp web-cache privileged EXEC command.
Deleted System Messages
These messages were deleted from the system message guide:
Error Message ACLMGR-2-NOVMR: Cannot create VMR data structures for access list [chars].Error Message %VQPCLIENT-2-INITFAIL: Platform-specific VQP initialization failed. QuittingError Message %VQPCLIENT-2-IPSOCK: Could not obtain IP socketError Message %VQPCLIENT-7-NEXTSERV: Trying next VMPS [IP_address]Error Message %VQPCLIENT-7-PROBE: Probing primary server [IP_address]Error Message %VQPCLIENT-2-PROCFAIL: Could not create process for VQP. QuittingError Message %VQPCLIENT-7-RECONF: Reconfirming VMPS responsesError Message %VQPCLIENT-2-SHUTDOWN: Interface [chars] shutdown by VMPSError Message %VQPCLIENT-3-THROTTLE: Throttling VLAN change on [chars]Update to the Getting Started Guides
The warranty section in the Catalyst 3750-E Switch Getting Started Guide and the Catalyst 3560-E Switch Getting Started Guide has changed. These are the updated sections.
Catalyst 3750-E Switch Getting Started Guide
Catalyst 3750-E switches are covered by the Cisco Limited Lifetime Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/LH2DEN__.html
Note
http://www.cisco.com/en/US/docs/general/warranty/English//901DEN__.html
Catalyst 3560-E Switch Getting Started Guide
Catalyst 3560-E switches are covered by the Cisco Limited Lifetime Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English/LH2DEN__.html
Note
http://www.cisco.com/en/US/docs/general/warranty/English//901DEN__.html
Related Documentation
These documents provide complete information about the Catalyst 3750-E and Catalyst 3560-E switches and are available on Cisco.com:
http://www.cisco.com/en/US/products/ps7077/tsd_products_support_series_home.html
http://www.cisco.com/en/US/products/ps7078/tsd_products_support_series_home.html
These documents provide complete information about the switches:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
http://www.cisco.com/en/US/products/hw/modules/ps5455/prod_installation_guides_list.htmlSFP compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list
.htmlFor other information about related products, see these documents:
•
•
•
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htmlSubscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Obtaining Documentation and Submitting a Service Request" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
