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(52)EX1
Cisco IOS Caveats Resolved in Cisco IOS Release 12.2(52)SE and Cisco IOS Release 12.2(52)EX
Update to the Software Configuration Guide
Correction to the Software Configuration Guide
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
Cisco IOS Release 12.2(52)SE and later runs on Catalyst 3750-E and Catalyst 3560-E switches. Cisco IOS Release 12.2(52)EX and later runs on 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(52)SE and any limitations, restrictions, and caveats that apply to it. Verify that these release notes are correct for 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 and of Cisco enhanced EtherSwitch service module documentation, see the “Related Documentation” section.
This information is in the release notes:
The system requirements are described in these sections:
Table 1 lists the hardware supported on this release.
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 PoE1 ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 Ethernet ports, 2 10-Gigabit Ethernet X2 module slots |
||
24 10/100/1000 PoE ports, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 370 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
48 10/100/1000 ports with 740 W of PoE, 2 10-Gigabit Ethernet X2 module slots |
||
12 SFP2 module slots, 2 10-Gigabit Ethernet X2 module slots |
||
X2-10GB-SR V02 or later |
Cisco IOS Release 12.2(35)SE2 |
|
Dual SFP X2 converter module to allow the switch to support SFP Gigabit Ethernet modules |
||
1000BASE-LX/LH For 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 |
||
DOM4 support for these SFP modules |
||
SFP module patch cable5 |
||
SM-D-ES2-48 6 |
||
SM-D-ES3-48-P 6 |
||
SM-D-ES3G-48-P 6 |
||
SM-ES2-16-P6 |
||
SM-ES2-24 6 |
||
SM-ES2-24-P 6 |
Layer 2-capable, 23 10/100 ports with PoE, 1 10/100/1000 port with PoE |
|
SM-ES3-16-P 6 |
||
SM-ES3-24-P 6 |
||
SM-ES3G-16-P 6 |
||
SM-ES3G-24-P 6 |
These sections describe the hardware and software requirements for using the device manager:
Table 2 lists the minimum hardware requirements for running the device manager.
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.
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.
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.
These are the procedures for downloading software. Before downloading software, read this section for important information:
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 Although the show version output always shows the software image running on the switch, the model name shown at the end of this display is the factory configuration and does not change if you upgrade the software license.
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.
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
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 Although you can copy any file on the flash memory to the TFTP server, it is time-consuming to copy all of the HTML files in the tar file. We recommend that you download the tar file from Cisco.com and archive it on an internal host in your network.
You can also configure the switch as a TFTP server to copy files from one switch to another without using an external TFTP server by using the tftp-server global configuration command. For more information about the tftp-server command, see the “Basic File Transfer Services Commands” section of the Cisco IOS Configuration Fundamentals Command Reference, Release 12.2, at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_command_reference_book09186a00800811e0.html
You can upgrade switch software by using the device manager or Network Assistant. For detailed instructions, click Help.
Note When using the device manager to upgrade your switch, do not use or close your browser session after the upgrade process begins. Wait until after the upgrade process completes.
This procedure is for copying the combined tar file to the switch. You copy the file to the switch from a TFTP server and extract the files. You can download an image file and replace or keep the current image.
To download software, follow these steps:
Step 1 Use Table 3 to identify the file that you want to download.
Step 2 Download the software image file. If you have a SmartNet support contract, go to this URL, and log in to download the appropriate files:
http://www.cisco.com/kobayashi/sw-center/sw-lan.shtml
To download the 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 Copy the image to the appropriate TFTP directory on the workstation, and make sure that the TFTP server is properly configured.
For more information, see Appendix B in the software configuration guide for this release.
Step 4 Log into the switch through the console port or a Telnet session.
Step 5 (Optional) Ensure that you have IP connectivity to the TFTP server by entering this privileged EXEC command:
For more information about assigning an IP address and default gateway to the switch, see the software configuration guide for this release.
Step 6 Download the image file from the TFTP server to the switch. If you are installing the same version of software that is currently on the switch, overwrite the current image by entering this privileged EXEC command:
The /overwrite option overwrites the software image in flash memory with the downloaded one.
The /reload option reloads the system after downloading the image unless the configuration has been changed and not saved.
For // location, specify the IP address of the TFTP server.
For / directory / image-name .tar, specify the directory (optional) and the image to download. Directory and image names are case sensitive.
This example shows how to download an image from a TFTP server at 198.30.20.19 and to overwrite the image on the switch:
You can also download the image file from the TFTP server to the switch and keep the current image by replacing the /overwrite option with the /leave-old-sw option.
You can assign IP information to your switch by using these methods:
These sections describe the new supported hardware and the new and updated software features provided in this release:
For a list of all supported hardware, see the “Hardware Supported” section.
http://www.cisco.com/en/US/prod/collateral/switches/ps5718/ps7077/product_data_sheet0900aecd805bbe67.html
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.
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:
Unless otherwise noted, these limitations apply to the Catalyst 3750-E and 3560-E switches and to the Cisco enhanced EtherSwitch service modules:
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)
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))
This is the Cisco Redundant Power System (RPS) 2300 limitation:
PLATFORM_ENV-1-RPS_ACCESS: RPS is not responding
No workaround is required because the problem corrects itself. (CSCsf15170)
These are the Cisco X2 transceiver module and SFP module limitations:
– Allow space between the switches when installing them.
– In a switch stack, plan the SFP module and cable installation so that uplinks in adjacent stack members are not all in use.
– Use long, small screwdriver to access the latch then remove the SFP module and cable. (CSCsd57938)
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 A268D8
No 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)
These are the EtherChannel limitations:
– The EtherChannel is a cross-stack EtherChannel with a switch stack at one or both ends.
– The switch stack partitions because a member reloads. The EtherChannel is divided between the two partitioned stacks, each with a stack master.
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:
– Enable the switch to recover from the error-disabled state.
– Enter the shutdown and the no shutdown interface configuration commands to enable the port.
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 879A58
These are the IEEE 802.1x authentication limitations:
Use one of these workarounds (CSCsd90495):
– Configure the port for single-host mode to prevent the extra MAC address from appearing in the MAC address table.
– Replace the NIC card with a new card.
– If the connected device is supposed to be unauthorized, the connected device might be authorized on the VLAN that is assigned to the critical port instead of to a guest VLAN.
– If the device is supposed to be authorized, it is authorized on the VLAN that is assigned to the critical port.
Use one of these workarounds (CSCse04534):
– Configure MAC authentication bypass to not use EAP.
– Define your network access profiles to not use MAC authentication bypass. For more information, see the Cisco Access Control Server (ACS) documentation.
The workaround is not use the VLAN assignment option. (CSCse22791)
These are the multicasting limitations:
– Multicast routing is enabled in the VLAN.
– The source IP address of the packet belongs to the directly connected network.
– The TTL value is either 0 or 1.
The workaround is to not generate multicast packets with a TTL value of 0 or 1, or disable multicast routing in the VLAN. (CSCeh21660)
– Multicast routing is enabled in the VLAN.
– The source IP address of the multicast packet belongs to a directly connected network.
– The packet is denied by the IP multicast boundary access-list configured on the VLAN.
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 port-channel is configured with member ports across different switches in the stack.
– When one of the member switches reloads.
– The member switch that is reloading has a high rate of IP IGMP joins arriving on the port-channel member port.
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)
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)
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 the default buffer size.
– Use the mls qos queue-set output qset-id buffers allocation1... allocation4 global configuration command to allocate the buffer size. The buffer space for each queue must be at least 10 percent. (CSCsx69718) (Catalyst 3750-E switches)
These are the routing limitations:
– The switch has 400 Open Shortest Path First (OSPF) neighbors.
– The switch has thousands of OSPF routes.
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)
These are the Catalyst 3750-E switch stack limitations:
unable to read config
message 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:
The workaround is to enter a shutdown interface configuration command followed by a no shutdown command on the port in the blocked state. (CSCsl64124)
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).
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)
– A supplicant is authenticated on at least one port.
– A new member joins a switch stack.
You can use one of these workarounds:
– Enter the shutdown and the no shutdown interface configuration commands to reset the port.
– Remove and reconfigure the VLAN. (CSCsi26444)
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)
This is the device manager limitation:
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
These sections describe the important notes related to this software release for the Catalyst 3750-E and 3560-E switches:
These notes apply to switch stacks:
These notes apply to Cisco IOS software:
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.
If this happens, enter the no auto qos voip cisco-phone interface command on all interface with this configuration to delete it. Then enter the auto qos voip cisco-phone command on each of these interfaces to reapply the configuration.
These notes apply to the device manager:
From Microsoft Internet Explorer:
1. Choose Tools > Internet Options.
2. Click Settings in the “Temporary Internet files” area.
3. From the Settings window, choose Automatically.
5. Click OK to exit the Internet Options window.
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.
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.
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:
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.
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:
The 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:
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.
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.
If you press the MODE button to enter Express Setup setup mode after the switch has received an IP address dynamically through DHCP, HTTP authentication with the default username and password cisco / cisco fails.
– Downgrade the image to 12.2(46)SE where there is no HTTP authentication.
– Use the console to perform initial configuration.
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.
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.
The switch fails when you use Cisco License Manager 3.0 to transfer software licenses between switches.
The workaround is to use the CLI commands to transfer software licenses.
The call in-progress feature, referred to as activity check, does not work.
The show energywise neighbors command output is incorrect.
After you use the energywise level 10 interface configuration command to power on a PoE port, the switch can fail while you configure EnergyWise.
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.
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.
In a stacked environment, IP ACLs are not applied to interfaces on member switches unless IP routing is enabled.
The workaround when applying IP ACLs to stack member interfaces is to enable IP routing on the stack master by entering the ip routing global configuration command.
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.
When a switch sends an ARP request to find the MAC address of the default gateway, the switch sends the request in the wrong VLAN. An ARP entry associating the MAC address with the wrong VLAN is added to the table.
The workaround is to use the no arp arpa global configuration command in all VLANs with IDs lower than the ID of the correct VLAN.
When VLAN-based quality of service (QoS) is enabled and then disabled on an interface by entering the mls qos vlan-based interface configuration command followed by the no version of the command, the port policy is not applied properly and could result in undefined behavior for packets matching the port policy.
The workaround is to remove the port policy by entering the no service-policy input policy-map-name interface configuration command and then reapply it to the interface.
If you enable 802.1Q native VLAN tagging by entering the vlan dot1q tag native global configuration command and then change the native VLAN ID on an ingress trunk port by entering the switchport trunk native vlan vlan-id interface command, untagged traffic is forwarded instead of being dropped.
The workaround is to use one of these methods:
– Enter a shutdown followed by a no shutdown interface configuration command on the trunk port.
– Disable and then reenable native VLAN tagging by entering the no vlan dot1q tag native global configuration command followed by the vlan dot1q tag native command.
If you repeatedly enter the show tech-support privileged EXEC command, the switch might leak memory and, in some cases, shut down.
The workaround is to reload the switch to clear the memory after repeated use of the show tech-support command.
When flow control is enabled on a port-channel interface and you enter the flowcontrol receive on interface configuration command, the bundle is not enabled after the switch restarts. The command appears in the port-channel interface running configuration but does not appear in the switch running configuration. A message such as this appears:
– To manually configure the port-channel interface, enter the flowcontrol receive on interface configuration command.
– To add the flow-control configuration to the interface after the switch restarts, use an EEM script similar to this:
For action 3, specify the port-channel interface.
In a VPN routing/forwarding (VRF) instance, a port channel is configured, and the default route is in the global routing table. If a link shuts down while the other links remain up, the port channel might not forward traffic.
– Enter the shutdown interface configuration command, and then enter the no shutdown interface command.
– In the VRF instance, configure the links in the port channel as Layer 2 access links, and configure a switch virtual interface (SVI).
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:
– Reload the switches in the EtherChannel into the channel group that you were not able to create.
– Use a new channel group number to bundle the physical interfaces in an EtherChannel.
– Reconfigure the EtherChannel before the master switch changeover.
If the host is in multiple-authentication (multiauth) mode and you configure the fallback authentication process as IEEE 802.1x or MAc authentication bypass, the per-user ACL does not work when the port uses web authentication as the fallback method and then uses 802.1x or MAC authentication bypass as the fallback method.
The workaround is to restart the switch.
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.
If an edge switch has this IEEE 802.1Q tunneling configuration:
The tunnel port might drop IGMP membership reports from hosts. Multicast traffic is not forwarded between customer sites.
When you have configured a login banner by entering the banner login c message c global configuration command and the switch reloads, the output of banner is missing a carriage return, making the format incorrect.
When you enable MAC address learning on a VLAN and then change the interface configuration (such as adding the VLAN to the list of VLANs allowed on a trunk), MAC address learning is not disabled on the interface. If you disable MAC address learning on the switch, high CPU utilization occurs when the local forwarding manager tries to ut does not learn MAC addresses.
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 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.
When remote neighbors change, the LLDP MIB does not properly update the remote neighbors.
The workaround is to clear the LLDP table by entering the clear lldp table privileged EXEC command.
These sections provide updates to the product documentation:
This section was added to the "Configuring IEEE 802.1x Port-Based Authentication" chapter:
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.
This example shows how the session ID appears in the output of the show authentication command. The session ID in this example is 160000050000000B288508E5:
This is an example of how the session ID appears in the syslog output. The session ID in this example is also160000050000000B288508E5:
The 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.
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 Multiple-authentication mode is limited to eight authentications (hosts) per port.
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.
These messages were added to the system message guide:
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-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-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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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.
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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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 This messages applies to switches running the IP base image.
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.
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 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 If you purchased your Catalyst 3750-E switch before May 1, 2009, your switch is covered by the Cisco 90-Day Limited Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English//901DEN__.html
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 If you purchased your Catalyst 3560-E switch before May 1, 2009, your switch is covered by the Cisco 90-Day Limited Hardware Warranty. For more information, see this document on Cisco.com:
http://www.cisco.com/en/US/docs/general/warranty/English//901DEN__.html
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:
These compatibility matrix documents are available from this Cisco.com site:
http://www.cisco.com/en/US/products/hw/modules/ps5455/products_device_support_tables_list.html
For 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/nm/hardware/installation/guide/eesm_hw.html
http://www.cisco.com/en/US/docs/routers/access/interfaces/software/feature/guide/eesm_sw.html
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.