Release Notes for Catalyst 3750-E and 3560-E Switches, Cisco IOS Release 12.2(53)SE and Later
Available Languages
Table Of Contents
Release Notes for Catalyst 3750-E and 3560-E Switches, Cisco IOS Release 12.2(53)SE and Later
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(53)SE2
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(53)SE1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(53)SE
Updates to the Software Configuration Guide
Understanding TelePresence E911 IP Phone Support
Configuring TelePresence E911 IP Phone Support
Correction to the Software Configuration Guide
Updates to the Command Reference
Updates to the Cisco Software Activation and Compatibility Document
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 3560-E Switches, Cisco IOS Release 12.2(53)SE and Later
Revised July 28, 2010
Cisco IOS Release 12.2(53)SE and later runs on Catalyst 3750-E, Catalyst 3560-E switches, and Cisco enhanced EtherSwitch service modules.
The Catalyst 3750-E switches support stacking through Cisco StackWise Plus technology. The Catalyst 3560-E switches and the Cisco enhanced EtherSwitch service modules do not support switch stacking. Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
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(53)SE and later and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for your switch:
•
If you are installing a new switch, see the Cisco IOS release label on the rear panel of your switch.
•
•
You can download the switch software from this site (registered Cisco.com users with a login password):
http://www.cisco.com/cisco/web/download/index.html
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 and of Cisco enhanced EtherSwitch service module 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 3560-E Switches and Cisco Enhanced EtherSwitch Service Module 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
CWDM3For a complete list of supported SFPs and part numbers, see the data sheet at:
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/product_data_sheet0900aecd805bbe67.html
Cisco IOS Release 12.2(35)SE2
DOM4 support for these SFP modules.
X2-10GB-ER, X2-10GB-SR, X2-10GB-LR, X2-10GB-LRM, X2-10GB-ZR
GLC-ZX-SM, GLC-BX-D, GLC-BX-U
SFP-GE-S, SFP-GE-L, SFP-GE-Z
All CWDM and DWDM SFP modules
Cisco IOS Release 12.2(46)SE
SFP module patch cable5
CAB-SFP-50CM
Cisco IOS Release 12.2(35)SE2
Supports OneX (CVR-X2-SFP10G) and these SFP+ modules
SFP-10G-SR=
SFP-10G-LR=
SFP-10G-LRM=Only version 02 or later CX16 cables support these SFP modules:
SFP-H10GB-CU1M
SFP-H10GB-CU3M
SFP-H10GB-CU5M12.2(53)SE
C3K-PWR-1150WAC
1150-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-750WAC
750-W AC power supply module for PoE-capable switches
Supported on all software releases
C3K-PWR-265WAC
265-W AC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-PWR-265WDC
265-W DC power supply module for nonPoE-capable switches
Supported on all software releases
C3K-BLWR-60CFM
Fan module
Supported on all software releases
Redundant power system (RPS)
Cisco RPS 2300 RPS
Supported on all software releases
SM-D-ES2-487
48 10/100 ports, 2 SFP module slots
12.2(52)EX
SM-D-ES3-48-P7
48 10/100 ports with PoE, 2 SFP module slots
12.2(52)EX
SM-D-ES3G-48-P7
48 10/100/1000 with PoE, 2 SFP module slots
12.2(52)EX
SM-ES2-16-P7
15 10/100 ports with PoE, 1 10/100/1000 port with PoE
12.2(52)EX
SM-ES2-247
23 10/100 ports, 1 10/100/1000 port
12.2(52)EX
SM-ES2-24-P7
Layer 2-capable, 23 10/100 ports with PoE, 1 10/100/1000 port with PoE
12.2(52)EX
SM-ES3-16-P7
15 10/100 ports with PoE, 1 10/100/1000 port with PoE
12.2(52)EX
SM-ES3-24-P7
23 10/100 ports with PoE, 1 10/100/100 port with PoE
12.2(52)EX
SM-ES3G-16-P7
16 10/100/1000 ports with PoE
12.2(52)EX
SM-ES3G-24-P7
24 10/100/1000 ports with PoE
12.2(52)EX
1 PoE = Power over Ethernet.
2 SFP = small form-factor pluggable
3 CWDM = coarse wavelength-division multiplexer
4 DOM = digital optical monitoring
5 Only Catalyst 3560-E switches. The SFP module patch cable is a 0.5-meter, copper, passive cable with SFP module connectors at each end. The patch cable can connect two Catalyst 3560-E switches in a cascaded configuration.
6 The CX1 cables are used with the OneX converter and are supported in Cisco IOS Release 12.2(53)SE and later.
7 Cisco enhanced EtherSwitch service module
Device Manager System Requirements
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, Release Notes for Cisco Network Assistant, the Cisco enhanced EtherSwitch service module documentation, the software configuration guide, and the command reference.
CNA Compatibility
Cisco IOS 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.
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/kobayashi/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.
To download the universal software image files for a SM-D-ES2-48, SM-ES2-16-P, SM-ES2-24, or SM-ES2-24-P6 module, click Catalyst 2960SM software. To obtain authorization and to download the cryptographic software files, click Catalyst 2960SM 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
Support for OneX (CVR-X2-SFP10G) and for six new SFP+ modules. For more information, see the "Hardware Supported" section.
New Software Features
•
–
–
•
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 and to the Cisco enhanced EtherSwitch service modules:
•
•
•
•
•
•
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:
–
–
RADIUS
•
There is no workaround. (CSCta05071)
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)
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)
•
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 (CSCsk96058)•
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state. (CSCsl64124)
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)
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
Unless otherwise noted, these severity 3 Cisco IOS configuration caveats apply to both the Catalyst 3750-E and 3560-E switches:
•
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.
•
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 you configure an ACL and enter the access-group interface configuration command to apply it to an interface for web authentication, the output from the show epm session ip-address or show ip access_list interface interface-id privileged EXEC command does not show any web authentication filter ID.
There is no workaround.
•
On a switch running Cisco IOS release 12.2(46)SE, the output of the show interfaces privileged EXEC command shows 0 packets for port channel input and output rates.
The workaround is to reload the switch by entering the reload privileged EXEC command.
•
When VLAN Membership Policy Server (VMPS) is used to configure dynamic VLAN membership on a Catalyst 3750-E or 3560-E switch, hosts or PCs connected to IP phones are denied access to the network. The IP phone continues to operate correctly on the voice VLAN. This issue does not occur on Catalyst 3560 or 3750 switches.
The workaround is to manually clear the MAC addresses learned on the interface to force a new VMPS query on the next untagged packet received, which is most likely from the PC. Use the clear mac address-table dynamic interface [interface-id] privileged EXEC command.
•
SNMP requests on the stpxRSTPPortRoleTable object only return information for the stack master.
There is no workaround.
•
On switches running Cisco IOS release 12.2(50)SE3 running MAC authentication bypass with multidomain authentication (MDA, IP phones connected to a port might not be able to regain network connectivity in the VOICE domain if the session times out and all RADIUS servers are unreachable.
There is no workaround.
•
EnergyWise is enabled and you use the energywise level level recurrence importance importance at minute hour day_of_month month day_of_week interface configuration command to configure a recurring event on a switch. After the time changes from daylight savings time to standard time, the switch might
–
–
–
This occurs when the time change for the next year occurs after the time change for the current year.
Before the time change occurs, use one of these workarounds:
–
–
–
•
A switch that has at least one trunk port configured might fail when you configure more than 950 VLANS by using the vlan vlan-id global configuration command.
There is no workaround.
•
When you configure more than one EnergyWise domain in a Layer 2 broadcast domain, IP connectivity to the switch might be lost, high CPU usage might occur on the switch, and a broadcast storm might occur in the subnet.
The workaround is to configure only a single EnergyWise domain in the Layer 2 broadcast domain.
•
Orchestrator shows a previously discovered stack as `not checking in' and discovers a new previously unseen stack. This condition occurs when you remove the master of a switch stack, causing the remaining stack members to elect a new stack master, and, in turn, causing the EnergyWise IDs to change.
There is no workaround.
Resolved Caveats
•
•
•
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(53)SE2
•
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.
•
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.
•
A switch fails when you enter the energywise level 10 interface configuration command on a Power-over-Ethernet (PoE) port.
There is no workaround.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(53)SE1
•
The CISCO-RTTMON-MIB is not correctly implemented in this release.
•
A switch can fail when an SNMP process attempts to configure dot1x authentication when it is already configured.
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.
•
If you configure EnergyWise on a member switch and then restart it by entering the reload slot stack-member-number privileged EXEC command, the EnergyWise configuration is removed from the switch.
The workaround is to save the switch configuration by using the copy running-configuration startup-configuration privileged EXEC command and then restart the switch stack.
•
Modifying a prefix list that is configured as an inbound or outbound distribute-list causes the EIGRP peer to resynchronize.
•
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.
•
When you enter the no ip ftp passive global configuration command to allow all types of FTP connections on a switch running Cisco IOS Release 12.2(52)SE or 12.2(53)SE, FTP sessions could disable Telnet or console connections. Then you can no longer use the vty.
Workaround: When you cannot use the vty, restart the switch. To prevent FTP sessions from disabling Telnet or console connections, enter the ip ftp passive global configuration command.
•
A switch that runs Cisco IOS Release 12.2(53)SE can fail when you enable dot1x authentication.
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 upgrading from Cisco IOS 12.2(52)SE to Cisco IOS 12.2(53)SE, EIGRP hello packets are flooded on access ports of other subnets. This also occurs when pings are sent to the broadcast address of other subnets.
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(53)SE
•
The Network Time Protocol (NTP) might not synchronize when the switch is configured as an NTP client. These are the two possible workarounds:
–
–
•
On switches running Cisco IOS release 12.2(35)SE or later, connectivity issues might occur with these messages:
%SUPQ-4-CPUHB_RECV_STARVE: Still seeing receive queue stuck after throttlingThere is no workaround.
•
On a switch running Cisco IOS release 12.2(46)SE, the output of the show interfaces privileged EXEC command shows 0 packets for port channel input and output rates.
The workaround is to reload the switch by entering the reload privileged EXEC command.
•
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 threshold00: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 terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# service internalSwitch(config)# endSwitch# test rps resetAre you sure you want to reset the system? [yes/no]: yesSwitch# configure terminalSwitch(config)# no service internal•
On switches running Cisco IOS Release 12.2(50)SE3 running MAC authentication bypass with multidomain authentication (MDA), IP phones connected to a port might not be able to regain network connectivity in the VOICE domain if the session times out and all RADIUS servers are unreachable.
There is no workaround.
•
The output of the show inventory user EXEC command sometimes does not display all of the connected SFP modules. The EntitityMIB does not report these SFP modules.
This occurs intermittently on the 3560-48TS, C3560-48PS, and C3560G-48PS switches. There is no workaround.
•
If IEEE 802.1Q native VLAN tagging is enabled on a switch, PDUs sent from an EtherChannel in LACP mode are tagged.
There is no workaround.
•
When a BPDU guard is globally enabled on a switch and the access VLAN is a VLAN other than VLAN 1, BPDU guard does not run on a multiple VLAN access port.
The workaround is to enable BPDU guard on the port.
•
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 24 phones connected to PoE ports start at the same time, LLDP for power management fails.
The workaround is to start the phones one at a time. This might not work after a power outage or other power failure event.
•
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.
Documentation Updates
These sections provide updates to the product documentation:
•
•
•
•
•
•
Updates to the Software Configuration Guide
This section was added to the "Configuring IEEE 802.1x Port-Based Authentication" chapter:
Common Session ID
Authentication manager uses a single session ID (referred to as a common session ID) for a client no matter which authentication method is used. This ID is used for all reporting purposes, such as the show commands and MIBs. The session ID appears with all per-session syslog messages.
The session ID includes:
•
•
•
This example shows how the session ID appears in the output of the show authentication command. The session ID in this example is 160000050000000B288508E5:
Switch# show authentication sessionsInterface MAC Address Method Domain Status Session IDFa4/0/4 0000.0000.0203 mab DATA Authz Success 160000050000000B288508E5This is an example of how the session ID appears in the syslog output. The session ID in this example is also160000050000000B288508E5:
1w0d: %AUTHMGR-5-START: Starting 'mab' for client (0000.0000.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E51w0d: %MAB-5-SUCCESS: Authentication successful for client (0000.0000.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E51w0d: %AUTHMGR-7-RESULT: Authentication result 'success' from 'mab' for client (0000.0000.0203) on Interface Fa4/0/4 AuditSessionID 160000050000000B288508E5The session ID is used by the NAD, the AAA server, and other report-analyzing applications to identify the client. The ID appears automatically. No configuration is required.
This guideline was added to the "802.1x Authentication" section of the "Configuring IEEE 802.1x Port-Based Authentication" chapter.
•
Note
This section was added to the "Configuring IP Unicast Routing" chapter:
User Interface for VRF-Aware RADIUS
To configure VRF-Aware RADIUS, you must first enable AAA on a RADIUS server. This release supports the ip vrf forwarding vrf-name server-group configuration and the ip radius source-interface global configuration commands, as described in the Per VRF AAA Feature Guide at this URL:
http://www.cisco.com/en/US/docs/ios/12_2t/12_2t13/feature/guide/ftvrfaaa.html
This guideline was added to the "MSTP Configuration Guidelines" section of the "Configuring MSTP" chapter:
•
The "Configuring TelePresence E911 IP Phone Support" chapter was added.
Understanding TelePresence E911 IP Phone Support
You can use a Cisco IP phone as a user interface in a Cisco TelePresence System. See in Figure 1. In this configuration, the IP phone must always be on and available for emergency calls. If the power to the codec in the Cisco TelePresence System fails, is disrupted or if the codec fails, the IP phone is not available.
Figure 1 Phone-Codec-Switch Connection
Use the TelePresence E911 IP phone support feature to ensure that the IP phone is always on and available for emergency calls. When a CDP-enabled IP phone is connected to the codec through a switch, you can configure the switch to forward CDP packets from the IP phone only to the codec in the Cisco TelePresence System. The switch adds ingress-egress port pairs to the CDP forwarding table. An ingress-egress port pair is a one-to-one mapping between an ingress switch port connected to the IP phone and an egress switch port connected to the codec.
The IP phone and the codec communicate through the IP network. If power to the codec fails, is disrupted or if the codec fails, the IP phone is still connected to the IP network and is available for emergency calls.
The switch forwards all CDP packets received on the ingress port to the egress port. If multiple IP phones are connected to the codec through a single port on the switch, only one phone communicates with it through the IP network. This phone is usually the one that sent the first CDP packet received by the codec.
Figure 2 Phone-Switch-Codec Connection
Configuring TelePresence E911 IP Phone Support
•
•
Configuration Guidelines
•
•
Enabling TelePresence E911 IP Phone Support
Beginning in privileged EXEC mode:
Example
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# cdp forward ingress gigabitethernet2/0/1 egress gigabitethernet2/0/12Switch(config)# cdp forward ingress gigabitethernet2/0/1 egress gigabitethernet2/0/13Ingress interface already configuredSwitch(config)# cdp forward ingress gigabitethernet2/0/2 egress gigabitethernet2/0/12Egress interface already configuredSwitch(config)# cdp forward ingress gigabitethernet2/0/2 egress gigabitethernet2/0/13Switch(config)# endSwitch#*Mar 1 13:38:34.954: %SYS-5-CONFIG_I: Configured from console by consoleSwitch# show running-config | include cdpcdp forward ingress GigabitEthernet2/0/1 egress GigabitEthernet2/0/12cdp forward ingress GigabitEthernet2/0/2 egress GigabitEthernet2/0/13Switch# show cdp forwardIngress Egress # packets # packetsPort Port forwarded dropped-------------------------------------------------------------Gi2/0/1 Gi2/0/12 0 0Gi2/0/2 Gi2/0/13 0 0Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# no cdp forward ingress gigabitethernet2/0/1Switch(config)# endSwitch#*Mar 1 13:39:14.120: %SYS-5-CONFIG_I: Configured from console by consoleSwitch# show running-config | include cdpcdp forward ingress GigabitEthernet2/0/2 egress GigabitEthernet2/0/13Switch# show cdp forwardIngress Egress # packets # packetsPort Port forwarded dropped-------------------------------------------------------------Gi2/0/2 Gi2/0/13 0 0Switch#Correction to the Software Configuration Guide
There is no longer a restriction of eight authentications per port, as described in the "Multiple Authentication Mode" section of the "Configuring 802.1x-Based Port Authentication" chapter:
Note
Updates to the Command Reference
These commands were added
cdp forward
To specify the ingress and egress switch ports for CDP traffic, use the cdp forward global configuration command. To return to the default setting, use the no form of this command.
cdp forward ingress port-id egress port-id
no cdp forward ingress port-id
Syntax Description
ingress port-id
Specifies the switch port that receives the CDP packet from an IP phone.
egress port-id
Specifies the switch port that forwards the CDP packet to the Cisco TelePresence System.
Defaults
The default path for CDP packets through the switch is from any ingress port to the egress port connected to the Cisco Telepresence System.
Command Modes
Global configuration
Command History
Usage Guidelines
You must use only CDP-enabled phones with TelePresence E911 IP phone support.
You can connect the IP phone and codec in the Cisco TelePresence System through any two ports in a switch stack.
Examples
Switch# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Switch(config)# cdp forward ingress gigabitethernet2/0/1 egress gigabitethernet2/0/12Switch(config)# cdp forward ingress gigabitethernet2/0/2 egress gigabitethernet2/0/13Switch(config)# endSwitch# show running-config | include cdpcdp forward ingress GigabitEthernet2/0/1 egress GigabitEthernet2/0/12cdp forward ingress GigabitEthernet2/0/2 egress GigabitEthernet2/0/13Switch# show cdp forwardIngress Egress # packets # packetsPort Port forwarded dropped-------------------------------------------------------------Gi2/0/1 Gi2/0/12 0 0Gi2/0/2 Gi2/0/13 0 0Related Commands
show cdp forward
To display the CDP forwarding table, use the show cdp forward user EXEC command.
show cdp forward [entry | forward | interface interface-id | neighbor | traffic] [ | {begin | exclude | include} expression]
Syntax Description
Command Modes
Use EXEC
Command History
Usage Guidelines
The show cdp forward command output shows the number of CDP packets forwarded on each ingress-port- to-egress-port mapping and the statistics for forwarded and dropped packets.
Expressions are case sensitive. For example, if you enter | exclude output, the lines that contain output do not appear, but the lines that contain Output appear.
Examples
Switch# show cdp forwardIngress Egress # packets # packetsPort Port forwarded dropped-------------------------------------------------------------Gi2/0/2 Gi2/0/13 0 0Related Commands
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 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 DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action. AuditSessionID [chars]Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication. [chars] is the session ID.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-FAIL: Authentication failed for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation The authentication was unsuccessful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message %DOT1X-5-RESULT_OVERRIDE: Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars]Recommended Action The authentication result was overridden. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Explanation No action is required.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars]Explanation Authentication was successful. The first [chars] is the client ID, the second [chars] is the interface, and the third [chars] is the session ID.
Recommended Action No action is required.
Error Message DOT1X_SWITCH-5-ERR_ADDING_ADDRESS: Unable to add address [enet] on [chars] AuditSessionID [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. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, the first [chars] is the interface, and the second [chars] is the session ID.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Note
Error Message DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a primary VLAN to an IEEE 802.1x port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Use a different VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid secondary VLAN [dec] to PVLAN host 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host IEEE 802.1x port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the mode of the port so that it is no longer a PVLAN host port or use a valid secondary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN [dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN [dec] to non-PVLAN host 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port, which is not allowed. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the mode of the port so that it is configured as a private VLAN host port, or use a different VLAN that is not configured as a secondary VLAN.
Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 802.1x port [chars], which is configured as a SPAN destination AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port AuditSessionID [chars]Explanation Multi-Domain Authentication (MDA) host mode cannot start if the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port session ID.
Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN AuditSessionID [chars]Explanation An attempt was made to assign a data VLAN to an IEEE 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Change either the voice VLAN or the IEEE 802.1x-assigned VLAN on the interface so that they are not the same.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Explanation Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars]Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, the first [chars] is the port, and the second [chars] is the session ID.
Recommended Action Make sure the VLAN exists and is not shutdown or use another VLAN.
Deleted System Messages
These messages were deleted from the system message guide:
Error Message DOT1X-4-MEM_UNAVAIL: Memory was not available to perform the 802.1X action.Explanation The system memory is not sufficient to perform the IEEE 802.1x authentication.
Recommended Action Reduce other system activity to reduce memory demands.
Error Message DOT1X-5-SUCCESS: Authentication successful for client ([chars]) on Interface [chars]Explanation Authentication was successful. [chars] is the interface.
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. This message might appear if IEEE 802.1x is enabled. [enet] is the client MAC address, and [chars] is the interface.
Recommended Action If the hardware memory is full, remove some of the dynamic MAC addresses. If the client address is on another port, remove it from that port.
Note
Error Message DOT1X_SWITCH-5-ERR_INVALID_PRIMARY_VLAN: Attempt to assign primary VLAN [dec] to 802.1x port [chars]Explanation An attempt was made to assign a primary VLAN to an IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Use a different VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_INVALID_SEC_VLAN: Attempt to assign invalid secondary VLAN [dec] to PVLAN host 802.1x port [chars]Explanation An attempt was made to assign a nonsecondary VLAN to a private VLAN host IEEE 802.1x port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the mode of the port so that it is no longer a private VLAN host port, or use a valid secondary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_PRIMARY_VLAN_NOT_FOUND: Attempt to assign VLAN [dec], whose primary VLAN does not exist or is shutdown, to 802.1x port [chars]Explanation An attempt was made to assign a private VLAN whose primary VLAN does not exist or is shut down. [dec] is the VLAN, and [chars] is the port.
Recommended Action Make sure the primary VLAN exists and is not shut down. Verify that the private VLAN is associated with a primary VLAN.
Note
Error Message DOT1X_SWITCH-5-ERR_SEC_VLAN_INVALID: Attempt to assign secondary VLAN [dec] to non-PVLAN host 802.1x port [chars]Explanation An attempt was made to assign a secondary VLAN to a port that is not a private VLAN host port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the mode of the port so that it is configured as a private VLAN host port, or use a different VLAN that is not configured as a secondary VLAN.
Error Message DOT1X_SWITCH-5-ERR_SPAN_DST_PORT: Attempt to assign VLAN [dec] to 802.1x port [chars], which is configured as a SPAN destinationExplanation An attempt was made to assign a VLAN to an IEEE 802.1x port that is configured as a Switched Port Analyzer (SPAN) destination port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the SPAN configuration so that the port is no longer a SPAN destination port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_MDA_INACTIVE: Multi-Domain Authentication cannot activate because Data and Voice VLANs are the same on port [chars]Recommended Action Multi-Domain Authentication (MDA) host mode cannot start if the configured data VLAN on a port is the same as the voice VLAN. [chars] is the port.
Recommended Action Change either the voice VLAN or the access VLAN on the interface so that they are not the same. MDA then starts.
Error Message DOT1X_SWITCH-5-ERR_VLAN_EQ_VVLAN: Data VLAN [dec] on port [chars] cannot be equivalent to the Voice VLAN.Explanation An attempt was made to assign a data VLAN to an IEEE 802.1x port that is the same as the voice VLAN. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change either the voice VLAN or the IEEE 802.1x-assigned VLAN on the interface so that they are not the same.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INTERNAL: Attempt to assign internal VLAN [dec] to 802.1x port [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is used internally and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_INVALID: Attempt to assign invalid VLAN [dec] to 802.1x port [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is out of range. [dec] is the VLAN, and [chars] is the port.
Recommended Action Update the configuration to use a valid VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_NOT_FOUND: Attempt to assign non-existent or shutdown VLAN [dec] to 802.1x port [chars]Explanation An attempt was made to assign a VLAN to an IEEE 802.1x port, but the VLAN was not found in the VLAN Trunking Protocol (VTP) database. [dec] is the VLAN, and [chars] is the port.
Recommended Action Make sure that the VLAN exists and is not shut down, or use another VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_ON_ROUTED_PORT: Dot1x cannot assign a VLAN [dec] to a routed port [chars]Explanation An attempt was made to assign a VLAN to a supplicant on a routed port, which is not allowed. [dec] is the VLAN ID and [chars] is the port.
Recommended Action Either disable the VLAN assignment, or change the port type to a nonrouted port.
Error Message DOT1X_SWITCH-5-ERR_VLAN_PROMISC_PORT: Attempt to assign VLAN [dec] to promiscuous 802.1x port [chars]Explanation An attempt was made to assign a VLAN to a promiscuous IEEE 802.1x port, which is not allowed. [dec] is the VLAN, and [chars] is the port.
Recommended Action Change the port mode so that it is no longer a promiscuous port, or change the configuration so that no VLAN is assigned.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RESERVED: Attempt to assign reserved VLAN [dec] to 802.1x port [chars]Explanation An attempt was made to assign an invalid VLAN to an IEEE 802.1x port. The VLAN specified is a reserved VLAN and cannot be assigned to this port. [dec] is the VLAN, and [chars] is the port.
Recommended Action Assign a different VLAN.
Error Message DOT1X_SWITCH-5-ERR_VLAN_RSPAN: Attempt to assign RSPAN VLAN [dec] to 802.1x port [chars]. 802.1x is incompatible with RSPANExplanation This message means that remote SPAN should not be enabled on a VLAN with IEEE 802.1x-enabled. [dec] is the VLAN, and [chars] is the port.
Recommended Action Either disable remote SPAN configuration on the VLAN, or disable IEEE 802.1x on all the ports in this VLAN.
Error Message SW_VLAN-4-VTP_USER_NOTIFICATION: VTP protocol user notification: [chars].Explanation This message means that the VTP code encountered an unusual diagnostic situation. [chars] is a description of the situation.
Recommended Action Find out more about the error by using the show tech-support privileged EXEC command. 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.
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.html
SFP compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list
.htmlFor other information about related products, see these documents:
•
•
•
These documents have information about the Cisco enhanced EtherSwitch service modules:
•
•
http://www.cisco.com/en/US/docs/routers/access/interfaces/software/feature/guide/eesm_sw.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Obtaining Documentation and Submitting a Service Request" section.
CCDE, CCENT, CCSI, Cisco Eos, Cisco Explorer, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco TrustSec, 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, Flip Gift Card, and One Million Acts of Green 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 Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco 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. (1002R)
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.
© 2009-2010 Cisco Systems, Inc. All rights reserved.
Feedback