Release Notes for Catalyst 3750-X and 3560-X Switches, Cisco IOS Release 15.2(1)E 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
New in Cisco IOS Release 15.2(1)E
Minimum Cisco IOS Release for Major Features
Cisco Transceiver Modules and SFP Modules
Stacking (Catalyst 3750-X Switch Stack only)
Stack Power (Catalyst 3750-X only)
Caveats Resolved in Cisco IOS Release 15.2(1)E2
Caveats Resolved in Cisco IOS Release 15.2(1)E1
Caveats Resolved in Cisco IOS Release 15.2(1)E
Obtaining Documentation and Submitting a Service Request
Cisco IOS Release 15.2(1)E and later runs on Catalyst 3750-X and Catalyst 3650-X switches and on Cisco enhanced EtherSwitch service modules.
The Catalyst 3750-X switch supports stacking through Cisco StackWise Plus technology and also supports StackPower. The Catalyst 3560-X 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 “Related Documentation” section.
These release notes include important information about Cisco IOS release 15.2(1)E and higher, and later 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://www.cisco.com/cisco/web/download/index.html
24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Services feature set |
||
48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Services feature set |
||
24 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Services feature set |
||
48 10/100/1000 PoE+ 2 ports, 1 network module slot, 715 W power supply; IP Services feature set |
||
48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; IP Services feature set |
||
24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Services feature set |
||
48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Services feature set |
||
24 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Services feature se |
||
48 10/100/1000 PoE+ 2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Services feature set |
||
48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 1100 W power supply; IP Services feature set |
||
12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set |
||
24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Base feature set |
||
12 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set |
||
24 SFP module slots, StackWise Plus, StackPower, 1 network module slot, 350-W power supply; IP Services feature set |
||
24 10/100/1000 Ethernet ports, StackWise Plus, 1 network module slot, 350 W power supply; LAN Base feature set |
||
48 10/100/1000 Ethernet ports, StackWise Plus, 1 network module slot, 350 W power supply; LAN Base feature set |
||
24 10/100/1000 PoE+1 ports, StackWise Plus, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+2 ports, StackWise Plus, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+2 ports, StackWise Plus, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set |
||
48 10/100/1000 Ethernet ports, StackWise Plus, StackPower, 1 network module slot, 350 W power supply; IP Base feature set |
||
24 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set |
||
48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 715 W power supply; IP Base feature set |
||
48 10/100/1000 PoE+2 ports, StackWise Plus, StackPower, 1 network module slot, 1100 W power supply; IP Base feature set1 |
||
24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set |
||
48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; LAN Base feature set |
||
24 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; LAN Base feature set |
||
48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set |
||
48 10/100/1000 Ethernet ports, 1 network module slot, 350 W power supply; IP Base feature set |
||
24 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; IP Base feature set |
||
48 10/100/1000 PoE+2 ports, 1 network module slot, 715 W power supply; IP Base feature set |
||
48 10/100/1000 PoE+2 ports, 1 network module slot, 1100 W power supply; IP Base feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Base feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Base feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Services feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Services feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; LAN Base feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Base feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Base feature set |
||
24 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Services feature set |
||
48 10/100/1000 Universal PoE ports, EEE support, 1 network module slot, 1100 W power supply; IP Services feature set |
||
100FX-SFP 1000BASE-LX/LH Note For a complete list of supported SFP modules, see the hardware installation guide or the data sheets at: |
||
SFP-10G-SR |
||
SFP-10G-ER4 |
||
Only version 02 (or later) of the CX15 cables are supported: |
||
SFP module patch cable6 |
||
C3KX-PWR-1100WAC Note For power supply module descriptions and configurations supported on switch models, see the hardware installation guide. |
||
Four SFP slots. |
||
Two 10-Gigabit Ethernet (copper) ports. Note To configure the port speed to 1 Gigabit per second, use the hw-module switch global configuration command. |
||
The device manager verifies the browser version when starting a session and 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 15.2(1)EE will be supported in a future release of the Cisco Network Assistant. Cisco IOS 12.2(35)SE2 and later is only compatible with Cisco Network Assistant 5.0 and later. You can download Cisco Network Assistant from this URL:
http://www.cisco.com/pcgi-bin/tablebuild.pl/NetworkAssistant
For more information about Cisco Network Assistant, see the Release Notes for Cisco Network Assistant on Cisco.com.
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.
If you have a service support contract and order a software license or if you order a switch, you receive the universal software image and a specific software license. If you do not have a service support contract, such as a SMARTnet contract, download the IP base image from Cisco.com. For Catalyst 3750-X and 3560-X switches, this image has the IP base and LAN base feature sets.
Note A Catalyst 3750-X or 3560-X switch running the LAN base feature set supports only 255 VLANs.
The switches running the universal software images can use permanent and temporary software licenses. See the “Cisco IOS Software Activation Conceptual Overview” chapter in the Cisco IOS Software Activation Configuration Guide :
http://www.cisco.com/en/US/docs/ios/csa/configuration/guide/12.4T/csa_book.html
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.
Catalyst 3750-X and 3560-X switches running payload-encryption images can encrypt management and data traffic. Switches running nonpayload-encryption images can encrypt only management traffic, such as a Secure Shell (SSH) management session.
For more information about Catalyst 3750-X and 3560-X software licenses and available images, see the Cisco IOS Software Installation Document on Cisco.com:
http://www.cisco.com/en/US/products/ps10745/products_installation_and_configuration_guides_list.html
Layer 2 and basic Layer 3 features, SSH9, SSL10, and SNMPv311, and Kerberos IP base image, as well as LAN base image with Layer 2 features |
||
Layer 2 and basic Layer 3 features, SSH, SSL, SNMPv3, Kerberos, and MACsec12 IP base image, as well as LAN base image with Layer 2 features |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 |
||
All the supported universal image features, Kerberos, SSH, SSL, SNMPv3, and MACsec |
||
Layer 2 features, SSH, SNMPv3, and Kerberos For these service modules: SM-D-ES2-48, SM-ES2-16-P, SM-ES2-24, and SM-ES2-24-P6. |
||
All the supported universal image features, Kerberos, SSH, SSL, and SNMPv3 IP base and IP services software licenses For these service modules: SM-D-ES3-48-P, SM-D-ES3G-48-P, SM-ES3-16-P, SM-ES3-24-P, SM-ES3G-16-P, and SM-ES3G-24-P. |
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.
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/prod/collateral/iosswrel/ps8802/ps6969/ps1835/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 :
http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_t1.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:
a. If you are a registered customer, go to this URL and log in:
http://www.cisco.com/cisco/web/download/index.html
b. Navigate to Switches > LAN Switches - Access
c. Navigate to your switch model.
d. Click IOS Software, and select the latest IOS release.
e. Download the image you identified in Step 1.
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.
Use these methods to assign IP information to your switch:
– Binding Table Recovery Mechanism - The binding table recovery mechanism enables the binding table to recover from a device reboot.
– Prefix Guard - This feature works within the IPv6 Source Guard feature, enabling the device to deny traffic originated from nontopologically correct addresses.
– Destination Guard - This feature works with IPv6 neighbor discovery to ensure that the device performs address resolution only for those addresses that are known to be active on the link.
– Neighbor Discovery Multicast Suppress - This is an IPv6 snooping feature that runs on a switch or a wireless controller and is used to reduce the amount of control traffic necessary for proper link operations.
– Lightweight DHCPv6 Relay Agent - This feature allows relay agent information to be inserted by an access node that performs a link-layer bridging (non-routing) function.
– IPv6 Duplicate Address Detection (DAD) Proxy - This feature is a subset of Neighbor Discovery Multicast Supress. This takes care of detecting duplicate address in scenarios where end hosts cannot communicate with each other.
– TrustSec Security Group Name Download
PMK
password inside the switch.– (LAN Base) Updated ICMP RFCs 4291, 4443, 3484, 2526, 4861, 4862, 5095, 4007, and 3513.
– (LAN Base) Support for UDP MIB (RFC 4113) and TCP MIB (RFC 4022).
– Generate SNMP trap when EIGRP neighbor is down.
– Support for EIGRP wide metrics.
– OSPFv3 External Path Preference
– OSPFv3 Router Max-metric Router LSA
– Support for OSPFv3 Prefix Suppression.
– Support for OSPFv3 Area Filter/DC Ignore.
– Creating global IPv6 entries for unsolicited NA.
– Option to configure exponential backoff for NS timer used in NUD.
– Support for 4-byte BGP ASN numbers.
– BGP support for malformed attribute error handling.
– BGP support for Cisco-BGP-MIBv2.
– BGP support for graceful shutdown.
– BGP support for VRF dynamic route leaking (for VRF lite).
Table 4 lists the minimum software release after the first release of required to support the major features on the switches. The first release of the Catalyst 3750-X and 3560-X switches was Cisco IOS Release 12.2(53)SE2).
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.
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)
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)
For more information, see http://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst3750x_3560x/software/release/15-2_1_e/configuration/guide/scg3750x/sw8021x.html#wp1188021
The workaround is to use modules with serial numbers that are not in the specified range. (CSCsh59585)
– 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)
The workaround is to configure aggressive UDLD. (CSCsh70244).
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 delete any unnecessary files in flash memory, delete the temporary files created as part of the failed upgrade, and try the MCU upgrade again. (CSCtd75400)
The workaround to verify the cable length is to enter the commands when a Gigabit link is active on the interface or after disconnecting the far end of the cable. (CSCte43869)
– 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
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)
– 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)
There is no workaround. (CSCsd60647)
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)
The workaround is to turn the powered device off and then on again.
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)
There is no workaround. (CSCsg79627)
– 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-X switches)
– 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)
The workaround is to use an on-demand upgrade to upgrade switches in a stack by entering the vstack download config and vstack download image commands. (CSCta64962)
When you upgrade the director to Cisco IOS Release 12.2(55)SE, the workaround is to also modify the configuration to include all built-in, custom, and default groups. You should also configure the tar image name instead of the image-list file name in the stored images. (CSCte07949)
The workaround is to use the TFTP utility of another server instead of a Windows server or to manually delete the existing backup file before backing up again. (CSCte53737)
There is no workaround. (CSCtg98656)
– When you select the NONE option in the director CLI, the upgrade should be allowed and is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.
– When you enter any password in the director CLI, the upgrade should not be allowed, but it is successful on client switches running Cisco IOS Release 12.2(25)SE through 12.2(46)SE, but fails on clients running Cisco IOS Release 12.2(50)SE through 12.2(50)SEx.
This is a hardware limitation. The workaround is to disable CDP on all interfaces carrying the RSPAN VLAN on the device connected to the switch. (CSCeb32326)
There is no workaround. This is a hardware limitation. (CSCei10129)
This is a cosmetic issue and the workaround is to use the show platform monitor session privileged EXEC command to display the correct source ports. (CSCtn67868)
When a switch or switch stack running Multiple Spanning Tree (MST) is connected to a switch running Rapid Spanning Tree Protocol (RSTP), the MST switch acts as the root bridge and runs per-VLAN spanning tree (PVST) simulation mode on boundary ports connected to the RST switch. If the allowed VLAN on all trunk ports connecting these switches is changed to a VLAN other than VLAN 1 and the root port of the RSTP switch is shut down and then enabled, the boundary ports connected to the root port move immediately to the forward state without going through the PVST+ slow transition.
The workaround it to enter a shutdown and then a no shutdown interface configuration command on the interface. (CSCsx70643)
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 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)
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)
There is no workaround. (CSCth00938)
The workaround is to reload the switch stack after the VRF configuration is changed. (CSCtn71151)
The workaround when you are forming power stack topologies if the power stack mode is not the default (power sharing), you should also configure the power stack mode on the new power stacks by entering the mode redundant power-stack configuration command. (CSCte33875)
The workaround is to reduce the number of VLANs or trunks. (CSCeb31087)
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)
The workaround is to remove unnecessary VLANs to reduce CPU utilization when many links are flapping. (CSCtl04815)
The following guidelines and limitations apply to configuring Cisco TrustSec SGT and SGACL on the Catalyst 3750-X switch:
When port-to-SGT mapping is configured on a port, an SGT is assigned to all ingress traffic on that port. There is no SGACL enforcement for egress traffic on the port.
The workaround is to completely remove the IP SLA Video Operation and configure again without VRF. (CSCuf39077)
The workaround is to click Yes when you are prompted to accept the certificate. (CSCef45718)
Catalyst 3750-X and 3560-X switches internally support up to 16 different control plane queues. Each queue is dedicated to handling specific protocol packets and is assigned a priority level. For example, STP, routed, and logged packets are sent to three different control plane queues, which are prioritized in corresponding order, with STP having the highest priority. Each queue is allocated a certain amount of processing time based on its priority. The processing-time ratio between low-level functions and high-level functions is allocated as 1-to-2. Therefore, the control plane logic dynamically adjusts the CPU utilization to handle high-level management functions as well as punted traffic (up to the maximum CPU processing capacity). Basic control plane functions, such as the CLI, are not overwhelmed by functions such logging or forwarding of packets.
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.
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 caveats apply to Catalyst 3750-X and 3560-X switches:
In a Smart Install network, when the director is connected between the client and the DHCP server and the server has options configured for image and configuration, then the client does not receive the image and configuration files sent by the DHCP server during an automatic upgrade. Instead the files are overwritten by the director and the client receives the image and configuration that the director sends.
– If client needs to upgrade using an image and configuration file configured in the DHCP server options, you should remove the client from the Smart Install network during the upgrade.
– In a network using Smart Install, you should not configure options for image and configuration in the DHCP server. For clients to upgrade using Smart Install, you should configure product-id specific image and configuration files in the director.
If you install 10/100/1000BASE-TX or 100BASE-FX SFPs in the SFP+ module ports (port 2 or port 4), the ports are put in an error disabled state. These SFPs are not supported in the SFP+ ports.
Cisco Network Assistant displays the LED ports with a light blue color for all switches in a stack that have the Catalyst 3750G-48PS switch as part of the stack.
Mediatrace does not report statistics on the initiator under these conditions:
– The responder is a mixed switch stack with a Catalyst 3750 as the master switch
– The ingress interface on the responder from the initiator is on a member switch.
The workaround is to ensure that the mediatrace ingress and egress connections are on the stack master or to configure a Catalyst 3750-X as the stack master and then reload the switch stack.
When running EIGRP on the switch, unicast EIGRP packets are not sent to the higher priority routing protocol queue when destined for the switch, but are sent to the host queue. This situation occurs when EIGRP is running on the switch and packets are sent to the switch. This situation does not impact EIGRP packets sent between routers through the switch.
When you enter the copy running-config startup config privileged EXEC command on the switch, the running configuration is not always saved to the startup configuration on the first attempt.
There is no workaround. If you wait for a few minutes, the configuration is saved when the switch attempts it again.
NetFlow traffic export fails when the source interface IP address and destination IP address are on different subnets.
On a switch stack, when an IP phone connected to a member switch has its MAC address authorized using the critical voice VLAN feature, if a master changeover occurs, the voice traffic is dropped. Drop entries for the IP phone appear in the MAC address table management (MATM) table. This occurs because the switch initially drops the voice traffic before reauthenticating critical voice VLAN traffic. The dropped entries are removed when critical voice VLAN authentication occurs.
There is no workaround. The dropped entries are removed when the IP phone is reauthenticated.
When you configure port-based QoS with an ACL by using the ACL range option, problems can occur if you have also configured mls qos trus t on the interface.
The workaround is to match traffic by using the single port equal (eq) option or to not configure mls qos trust on the interface.
A seed switch is connected to a RADIUS server either directly or through a trunk port. A non-seed switch authenticates with the RADIUS server through the seed switch, based on the credential information defined in the RADIUS server. Cisco TrustSec (CTS) parameters must be configured on both the seed switch and the non-seed switch trunk interfaces.
Although the non-seed switch is authenticated and authorized to connect to the network, supplicant devices connected to the non-seed switch might be unable to connect to the network, under these circumstances:
– CTS caching is enabled on the seed switch and not enabled on the non-seed switch.
– The seed switch reported the 802.1x role of the non-seed switch CTS trunk as authenticator in multi-host mode.
– The non-seed switch reported this CTS trunk as the 802.1x authenticator role in single host mode and as supplicant.
The workaround is to reduce the reauthentication time on the seed switch, or enter the shutdown interface configuration command, followed by the no shutdown interface configuration command on the seed switch CTS trunk interface.
When a switch stack member configured for RMON statistics collection is not booted up with the master switch, the RMON collection configuration is missing from the stack running-config. To prevent this situation from occurring, all stack switches configured for the RMON statistics collection must be booted up with the other stack members and master switch at the same time.
ASP now uses a device classifier, which determines the type of device that is connected to the switch. As a result, ASP has no control over the protocol type that is used to detect the device. Therefore, the protocol detection controls are deprecated. When you enter the macro auto global control detection command, the protocol does not show up in the running configuration; however, the filter-spec command is shown in the output.
There is no workaround. To see the deprecated commands, enter the show running config deprecated global and interface configuration command.
RIP hellos get triplicated as they exit a dot1q-tunnel interface. This situation occurs specifically when a dot1q-tunnel configuration is applied.
Monitored SPAN traffic is not sent to the SPAN destination when TrustSec MACsec is enabled on the SPAN source interface.
A stack power member switch that does not have a PSU connected in Slot A or Slot B might fail during a Cisco IOS upgrade.
The workaround is to ensure that each stack member has at least one PSU connected. Alternatively, you can download and install the Cisco IOS image using the archive download-sw /force-ucode-reload privileged EXEC command.
After a master switchover on a switch stack, IPV6 multicast routing fails.
The workaround is to avoid configuring IPv6 multicast routing on larger stacks. We recommend enabling IPv6 multicast routing on stacks with five or fewer members.
The following message may be erroneously displayed during the boot up process.
The global power inline consumption default 15400 command fails to restrict the power consumption of a PoE+ port 15.4 W.
The workaround is to use the power inline consumption 15400 command in interface configuration mode.
When QoS is disabled on a port, the occurrence of IP fragments might cause packets to be dropped on Queue 1.
The workaround is to enable QoS and tweak the buffer thresholds.
In a switch stack, multicast traffic can be lost for up to 60 seconds when the master switch is reloaded. Because the platform does not suppaort multicast non-stop-forwarding (NSF), the time before traffic reconvergence after a switchover can vary.
Errors occur when configuring Cisco Trust Security (CTS) MACsec on the C3KX-SM-10G network service module.
The workaround is to use the default command in CTS manual interface configuration mode to clear the interface, and then reapply the configuration.
On reloading the stack master, the supplicants with Filter-ID lose connectivity.
The workaround is to use dACL instead of Filter-ID. For supplicants with Filter-ID, there would be loss of connectivity until a new session is established.
Unable to send or receive any data traffic from the uplink service module C3KX-SM-10G, when GE-100FX SFP is used on the module.
This problem occurs when creating a 3750X stack with Cisco TrustSec (CTS) link that connects to the Catalyst 4000 series switch.
Configure the Catalyst 4000 series switch as a non-seed switch. Connect few phones or PCs, authenticate them with Dot1x/MAB/Webauth, and then allow all the sessions to remain active. After a couple of days of longevity, if you perform master switchover for 5-6 times, huge memory leak occurs.
The workaround is to either ignore the memory leak or reboot the switch to clear the memory leak. The memory leak that occurs is false and hence there is no memory consumption.
IPv6 access-list counters do not increment when a policymap associated with a classmap that matches an IPv6 ACL is applied to a physical interface and matching traffic is sent.
System crashes if you remove EnergyWise SNMP proxy configuration immediately after configuring it.
The workaround is to wait for some time after configuring EnergyWise SNMP proxy, and then remove the configuration to avoid a crash.
If the stack master is reloaded, supplicant switches with Filter-ID Access Control Lists (ACLs) lose their connectivity.
The workaround is to use Downloadable ACLs (DACLs) instead of Filter-ID ACLs.
When a Catalyst 3750-X or 3560-X UPoE switch is connected to another 3750-X or 3560-X UPoE switch and one of them is reloaded, the speed is negotiated to 100Mbps. The workaround is to restart the interface (using the shutdown and no shutdown interface configuration command) after the switch is reloaded. Alternatively, configure the speed manually to 1000Mbps after the switch is reloaded.
A Dynamic ACL with a remark statement is not pushed from ISE to client and authorization either fails or is unauthorized.
The workaround is to remove the remark statement from the DACL.
The switch resets during normal network operation due to a malformed Multicast Domain Name service (mDNS) packet.
If login quiet-mode is configured, the switch resets when you enter the no login block-for command.
Provided an HTTP server is enabled on a switch, a vulnerability exists in Cisco IOS switches where the remote, non-authenticated attacker can cause Denial of Service (DoS) by reloading an affected device. An attacker can exploit this vulnerability by sending a special combination of crafted packets.
When Dynamic ARP Inspection (DAI) is enabled over port channel, it stops processing the Address Resolution Protocol (ARP) packets.
The workaround is to set up a direct link between the access switch and the DHCP server.
Cisco TrustSec (CTS) feature is not supported on the switch.
Security Group Access Control List (SGACL) with log option set on the switch does not print syslogs.
Cisco TrustSec Security Group Tag Exchange Protocol (CTS-SXP) is missing on the switch.
When you enable either the device-sensor accounting or the access-session accounting attributes command, the accounting request is not sent from the switch to the radius (ISE) Server.
The workaround is to not enable device-sensor accounting. The user accounting message will not carry the device-sensor attributes to the ISE.
VRRPv3 is not available on the switch in Cisco IOS Release 15.2(1)E.
VRRPv3 is made available from Cisco IOS Release 15.2(1)E1.
The match input-interface interface-id-list class-map configuration command does not recognize multiple interfaces to be matched.
A Preboot Execution Environment (PXE) enabled host is unable to boot properly when IP Source Guard is configured on the switch.
An interoperability issue occurs between MSTP and RSTP. An access port on the MSTP boundary switch and trunk port on RSTP boundary is not a supported design. Aloop is created when the interoperability occurs between the access port on the MST boundary switch and trunk port on the RSTP boundary.
IP Telephony Design (IPDT) on the master switch does not update new VLAN ID after 802.1x authentication.
The workaround is to disable open access to the port by entering the no authentication open command and then allow traffic only after a successful 802.1x authentication. Add a short lease DHCP server on the default access VLAN for the clients to obtain a different IP address on default access VLAN and dynamic VLAN.
If you connect the C3KX-SM-10G uplink module to switches by using the Flex Links configuration, the MAC and FLCD flapping notifications are generated between the active and backup interface.
When manually running on-demand diagnostic tests on a stack member using the diagnostic start switch number test all interface configuration command, the TestPortAsicRingLoopback test fails arbitrarily.
The workaround is to run only the TestPortAsicRingLoopback test ( diagnostic start switch number test 4 interface configuration command) on the stack member. Isolate the stack member and then run the diagnostic start switch number test all interface configuration command on the rest of the stack.
When the show mac address-table interface gigabitethernet privileged EXEC command is entered, all interfaces are replicated with the same command.
The interface status shows that the port is up, and duplex and speed are set to auto, even though link negotiation is disabled (when using the speed nonegotiate interface configuration command).
The workaround is to restart the interface using the shutdown and no shutdown interface configuration command.
When the SNMP is polled, the entPhysicalContainedIn object displays the value 0 for FRULink Container. The SNMP cannot be queried from the CLI with a no repetition value as 0.
Internal VLANs are displayed when the show snmp mib ifmib ifindex command is entered or the SNMP is queried for the ipMIB object.
The workaround is to check if the displayed VLANs are internal and then to hide them.
When AAA is configured, the following message is displayed when entering the enable command:
Password required, but none set
The workaround is to enter the aaa authentication enable default enable global configuration command.
If macros are used for device classification, the CISCO_LAST_RESORT_EVENT macro is triggered on the switch inexplicably.
If a new member is added to the switch stack, a Topology Change Notification (TCN) flood is triggered on the network.
In multicast mode, Web Cache Communication Protocol (WCCP) ISY packets are not received by the cache engine.
The workaround is to use unicast mode.“Open Caveats” section
With DHCP address conflict resolution enabled (by using the ip dhcp conflict resolution global configuration command), the switch stops operating when the clear ip dhcp conflict command is entered.
User documentation in HTML format includes the latest documentation updates and might be more current than the complete book PDF available on Cisco.com.
with complete information about the switch are available from these Cisco.com sites:
Catalyst 3750-X
http://www.cisco.com/en/US/products/ps10745/tsd_products_support_series_home.html
Catalyst 3560-X
http://www.cisco.com/en/US/products/ps10744/tsd_products_support_series_home.html
These documents provide complete information about the switches:
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.html
For other information about related products, see these documents:
These documents have information about the Cisco enhanced EtherSwitch service modules:
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.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.